...

• RCx (Runtime Compliance)
  

  • ARCHITECTURE SUBCOMMITTEE at RC0/RC1/RC2 -
    
    • #A RELEASE CERTIFICATION - The API reviewed were the ones that were tested by the integration teams. The high-level requirements drive the low-level requirements. They would drive test cases. Test cases are run, if they pass and there is something that is wrong with the requirements/epics/user stories, the test cases don't change and then re-test happens. The feedback with a problem they need to make sure that problems are also notified in the architecture sub-committee.
    • #B NEXT RELEASE ARCHITECTURE FOCUS - Discussions are happening around what the focus of the Architecture efforts for the next release are happening. For example at the end of R7 the Architecture sub-committee was discussing aligning the Platform component wiki pages, and also the next steps for the Architecture flow diagrams that were started in R4.
    • #4 ARCHITECTURE ENHANCEMENTS (Architecture Base-lined) - Architecture enhancements are secondary architectural enhancements that are worked during a release. These may include architecture portal landing page enhancements, architecture component description work, and process work. Because the teams are fully engaged trying to meeting delivery deadlines, the Architecture enhancements are fully self-contained activities within the Architecture sub-committee they can continue to evolve during M3, M4 and RCx. For example, suggestions for common templates can be discussed in this time frame. This also sets the stage for making the focus of the next release more coherent.
    • 
      
  • Use Case Engagement -
    • API - Uxnent pagesSync - Any major changes arising from the Use Case teams can be socialized to the architecture sub-committee at this point. They can then be addressed in the next release if necessary or action can be taken in the current release.
  • Components (PTL) Engagement -
    • Axions - Upd

...

• • • Sync - Any major changes arising from the Use Case teams can be socialized to the architecture sub-committee at this point. They can then be addressed in the next release if necessary or action can be taken in the current release.

ARCHITECTURE ARTIFACTS

• The following summarizes the artifacts of the Architecture Subcommittee

• 
  

  Topic	Description
  Functional Architecture	The following diagram is an example of the functional architecture: Image Modified This is one of the main outputs of the Architecture Sub-committee.
  Component Architectures	The component architecture pages capture the architecture per component. The R7 component wikis can be found here: ONAP Architecture Component Description - Guilin-R7
  Architecture Portal Page	The Architecture Portal page can be found here: https://safratech.net/onapdocs/ The page looks like this: Image Modified

...

ROLES –

...

ARCHITECTURE SUB-

...

COMMITTEE

• The following table shows some of the key roles within the Architecture Sub-committee
  

• 
  

  Role	Description
  Chair	The Architecture Chair coordinates the Architecture work and sets a vision for the sub-committee.

  
  

SUPPORTING LINKS & DOCUMENTS

...