Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

TypeDescriptionPrerequisiteReview / ApprovalNotes
FeatureA change that impacts multiple components.
Requirements Subcommittee (M2)
Arch Subcommittee (M2)
Impacted PTLs (M2)

SpecificationA change that impacts a single component.
Impacted PTLs (M2)
Use CaseThe application of one or more components of ONAP to provide a specific end user solution.
Requirements Subcommittee (M2)
Arch Subcommittee (M2)
Impacted PTLs (M2)

Best PracticeA software development practice, that is broadly applicable, but applied to new code only (Example:  use Python 3 interpreter)Socialization with PTLs and general consensusPTLs (nlt M1)
TSC (M1)

Global RequirementA software development practice, that is broadly applicable, applied to ALL code (Example:  use Python 3 interpreter)Previously approved as a Best Practice
Socialization with PTLs and general consensus
PTLs (nlt M1)
TSC (M1)

  • No labels