Uploaded image for project: 'Release Requirements'
  1. Release Requirements
  2. REQ-1

ONAP Requirement Template

    XMLWordPrintable

Details

    • Epic
    • Status: To Do
    • High
    • Resolution: Unresolved
    • None
    • Istanbul Release
    • None
    • ONAP Requirements Template
    • 4

    Description

      Before editing please read instructions here.

       Description of Use Case / Requirement:

       

       

      Owners (one of these should be the Assignee - use @ notation):

       

      Link to HLD/LLD (if any):

       

      Dependency Relationships with Other Projects:

       

      Project (ONAP Component #1) IMPACT: TO/C

      • Impact Type: TO/C (Test Only/Code)
      • Company Engagement: xyz
      • Resources: xyz (People)
      • Support Status: S/P/N (Supported/Partially supported/Not supported)
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      Project (ONAP Component #2) IMPACT: TO/C

      • Impact Type: TO/C (Test Only/Code)
      • Company Engagement: xyz
      • Resources: xyz (People)
      • Support Status: S/P/N (Supported/Partially supported/Not supported)
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

        

      Integration Leads (use @ notation): 

       
       

       

      Attachments

        Issue Links

          # Subject Branch Project Status CR V

          Activity

            People

              Unassigned Unassigned
              dmcbride David McBride
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: