1. ONAP Software Architecture
October 19, 2017

2. What are the goals of a focus on Software Architecture?
NOT addressing
Functional capability of platform (i.e. use cases, network services, etc.)
Models (already have a modeling project)
Functional architecture (roles of controllers, orchestration approaches, etc.)
Hoping to address
Consistency of implementation across projects
Elimination of different version/types of same capability (ex: TOSCA parsers)
More common capabilities
Improvements in meeting Platform Maturity requirements (formerly known as Carrier Grade Requirements or S3P)
Common approaches for platform maturity (ex: clustering strategy)
Leveraging software architecture skills across projects

3. Initial Plan to address Software Architecture Concerns
Understand the Problem
Recommend a Solution Approach
Possibilities:
Software Architecture Coordinator that works with PTLs and Use Case, Security & Architecture Subcommittees
Software Architecture Subcommittee consisting of software architects
No Software Architecture coordinator or subcommittee – can be handled by projects and existing subcommittees
Technology
Project
Survey
Skills
Maturity
Recommendation to the TSC by December F2F
All projects self-assess; PTL interviews for MVP projects
Initial evaluation done via task force under Architecture Subcommittee