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

Compare with Current View Page History

« Previous Version 10 Next »

BUSINESS DRIVER

This section describes Business Drivers needs.

Executive Summary - (Give a short description of your Use Case, the "Executive 2 min elevator pitch", this describes the "WHAT")

Business Impact - (This is the Business Impact which describes why this use case is important from a business perspective, this describes the "WHY").

Business Markets - (This is the marketing analysis, which can include but not limited to applicable markets, domains, marketing projections, this can describe the "WHERE").

Funding/Financial Impacts - (The Funding requirements and Financial impacts can describe the financial savings, or CAPEX, OPEX impacts for a Use Case).

Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)


Use Case Contacts & Team

Timo Perala

Samuli Kuusela

DEVELOPMENT IMPACTS

List of PTLs:Approved Projects

*Each Requirement should be tracked by its own User Story in JIRA 


Test Cases and Status


#Test CaseStatus
1There should be a test case for each item in the sequence diagram

NOT YET TESTED

2create additional requirements as needed for each discreet step

COMPLETE

3Test cases should cover entire Use Case

PARTIALLY COMPLETE

 Test Cases should include enough detail for testing team to implement the test

 FAILED

  • No labels