...

It illustrates 5 stages that the Architecture teams are concerned with, the Functional Architecture requirements, to component architecture reviews and architecture improvements.

FUNCTIONAL ARCHITECTURE - The functional architecture is the high-level architecture overview diagram for all of ONAP. This was the Functional Architecture diagram on May 16, 2019:

Image Added

COMPONENT ARCHITECTURE - The component architecture are the platform components. Examples of platform components are SO, A&AI, CCSDK, SDN-C. Each release there may be architecture impacts from the platform components

REQUIREMENTS ARCHITECTURE - These are architecture impacts coming from the requirements and use case work in a release that may impact the functional architecture, platform architecture, or may need architectural guidance.

ARCHITECTURE ENHANCEMENTS - Architecture enhancements are secondary architectural enhancements that are worked during a release. These may include documentation enhancements, landing page enhancements, architecture component description work, flow descriptions and process work (this wiki page!)

Some key things the happen at the milestones:

M0 - Functional Architecture Proposals, Component Architecture Proposals, Functional Requirements Architecture Proposals

M1 - Functional Architecture Review, Component Architecture Requirements, Functional Requirements Architecture Requirements, Architecture Enhancements Proposals

M2 - Component Architecture Reviews & Base-line, Functional Requirements Architecture Review & base-line, Architecture Enhancements Reviews

...

The Functional Architecture on May 16, 2019:

Release Planning (legacy)

Frankfurt Release M3 API Freeze Milestone ChecklistImage Removed

Use Case Teams Process

• MO

  • ARCHITECTURE SUB-COMMITTEE - The following are M0 activities with the Architecture Sub-committee
    
    • #1 FUNCTIONAL ARCHITECTURE - The
    • #2 COMPONENT ARCHITECTURE - The
    • #3 REQUIREMENTS ARCHITECTURE - The
    • #4 ARCHITECTURE ENHANCEMENTS - The
  • USE CASE TEAMS - The Use Case Teams prepare their proposals.
    • #1: BUSINESS DRIVER TEMPLATE - The Use Case Teams should develop their business driver template and consider their purpose and business impact for their use case. This would detail the executive summary, business impact, business markets, financial impacts and management and strategy. The template for the business driver case can be found here: Business Driver Template for Use Cases
    • #2: REQUIREMENTS SUB-COMMITTEE - Develop their proposals for the release which focus on defining their business imperatives.  When ready, the Team needs to present their business drivers and requirements to the requirements sub-committee. The presentation are given to the Requirements Sub-committee: Requirements subcommittee
    • #3: REQUIREMENTS RELEASE TRACKING - After making a presentation to the Requirements sub-committee. Their requirements would then be put into the release proposed functional requirements page. An example for Release 7 (GuiLin) is at this wiki: Guilin release - functional requirements proposed list
    • #4: USE CASE DEFINITIONS - The team can then use the Use Case Template to fill out more details about their Use Case. The use Case Template can be found here: Use Case Tracking Template
    • #5: INTENTION TO PARTICIPATE - Teams can indicate their corporate intention to participate
    • #6: RELEASE TRACKING - Each release has a release tracking page. The page can be found here: Release Planning
    • #7: PROJECT SUBMISSION, PROPOSAL, PLANNING - The TSC coordinates the project submission, proposal and planning. A project submission, the intention to participate is announced. The TSC reviews and provides its disposition on all submitted projects proposal. In Project Planning closure, the submissions from all of the new projects have been submitted in wiki their Release Planning materials. These are also tracked on the Release Planning page.

• WIKI LINKS References for the Use Case Teams at M0

  WIKI LINKS REFERENCE AT M0
  M0	Description	Wiki Link
  1	Business Driver Template	Business Driver Template for Use Cases
  2	Requirements S/C	Requirements subcommittee
  3	Functional Requirements Proposals	Guilin release - functional requirements proposed list
  4	Use Case Tracking Template	Use Case Tracking Template
  6	Release Tracking page	Release Planning
  Mod	Modeling Release Planning Page	ONAP R6 Modeling High Level Requirements
  Arc	Architecture Reference Architecture	Architecture

  
  

• Modeling team - At MO the Modeling S/C does MODEL PLANNING. The planning develops into “High Level Info-model Requirements”. These High level info-model requirements fall into 3 categories:
  
  • #1: NEW USE CASES - items from the expected Use Cases in the release (Scope of modeling, continuing, introducing, standards updates). The Use Case Teams should engage the modeling team to propose new requirements into their release planning page.
  • #2: REFINING EXISTING MODEL - Refining Existing info-model that has not made it to the information model. Previously designs that need to be added into information model.
  • #3: FORWARD LOOKING WORK (FLW) - Modeling future forward looking requirements.

• Architecture - The team members should be aware of any updates to the current release's reference model.f
• PTL- High level release scope from PTLs (understand from PTL which ONAP components are expected to have updates)
• PTL - The Use Case teams should attend the PTL planning meetings if there are expected to be requirements impacts for your use case. It is also where the Release Planning page is developed by the PTL team.

...