...
- Architecture - The Architecture team should be aware of any major updates coming from the requirements & use case teams. If there is architectural impact arising from your use case or requirements comprising your use case, you can make presentations at the Architecture sub-committee meetings. Changes may include impacts to the functional architecture, or platform architecture.
- #1 ARCHITECTURE PROPOSALS - Teams must make Architecture sub-committee presentations following the template: R7 Guilin Architecture Review (template) - functional requirements
#1a REQ link to ARCH-Jira link
Steps to Link Description Link your REQ Jira to the ARCH-jira - Before a requirement may be reviewed by the arch subcommittee, the requirement must be documented in JIRA (REQ), and the REQ reference must be submitted when requesting an arch review.
- After the arch review subcommittee has completed its review and made a determination, please add an issue link to the REQ issue for your review.
- Navigate to your requirement issue in JIRA (REQ)
- Select edit
- Scroll down until you find the "Linked Issues" field (see attachment)
- Make sure that the link type is "Is blocked by" (see attachment)
- Add the JIRA reference for your arch review (ONAPARC) to the "issue" field. (see attachment)
- Click the "Update" button.
- #2: PROCEDURE - Schedule presentations with the Architecture sub-committee Project Architectural Review Requirements and Process (Draft)
- PTL - The Use Case teams should engage the PTLs to inform them that the requirements in the use cases may have impact to their particular platform component. This can be done via attending the individual component meetings or coordinated at the Use Case Realization calls. Often, the platform components each have a release planning page as well.
...