Requirements

1. All ONAP projects that commit code to a repository are subject to an architectural review.
2. ONAP projects that do not plan to participate in a release are still subject to architectural review, if they plan to commit code to a repository.
3. All projects should assume that they require an architectural review.  The decision about whether a review is required will be made by the architectural subcommittee and not by the project.
4. Projects may choose not to participate in a review. However, the architectural subcommittee will report review status to the TSC, and review participation may influence whether the TSC approves a project to move forward at a milestone.  In addition project review status will be published in the release notes.

Process

1. Release contents/requirements approved by TSC at M1.
2. Project PTLs must request a review bye email from the chair of the arch subcommittee and receive a JIRA ticket.
   1. The JIRA issue must be documented in the arch review task for the M1 milestone epic for each project.
   2. Projects that are not participating in the release should are still required to request a review if they intent to commit code during the period of the release.
3. The project PTL must complete two forms and add links to the forms in a comment to the project arch review JIRA ticket:
   1. Component Architecture Description Form
   2. Functional Architecture Description Form
4. The arch subcommittee schedules a review with the project PTL
5. Arch Subcommittee review
   1. PTL presents the project, including the submitted forms
   2. The arch subcommittee reviews the changes and asks the PTL questions
   3. The subcommittee may approve the project at that point, or ask for changes, or additional information