Author: [Project Manager/Technical Lead]
Email: [Email address for Scope Document contact]
Team: [For example caDSR, EVS, caGRID, and so on.]
Contract: [Contract number]
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services
Sign off |
Date |
Role |
CBIIT or Stakeholder Organization |
Reviewer's Comments (If disapproved indicate specific areas for improvement.) |
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The purpose of this document is to collect, analyze, and define high-level needs for and designed features of the [Product or Component Name x.x]. The focus is on the functionalities proposed by the stakeholders and target users to make a better product. The use case documents show in detail how the features meet these needs.
Note
Use the sub-headings that you need for details of your Design Scope, Solution Architecture, and Implementation Requirements. Delete the ones you do not need, along with this note.
Design Scope
GForge items
One heading for each item, to include functional and non-functional requirements and bug fixes.
Use cases
Links to available documents.
Related requirements
One heading for each item.
Solution Architecture
Proposed technical solution to satisfy the requirements.
Cross product dependencies
Include a link to the Core Product Dependency Matrix.
Changes in technology
Include any new dependencies in the Core Product Dependency Matrix and summarize them here.
Assumptions
List any assumptions.
Risks
List any risks.
Detailed Design
Specify how the solution architecture will satisfy the requirements. This should include high level descriptions of program logic (for example in structured English), identifying container services to be used, and so on.
Implementation Requirements
Training and documentation requirements
One heading for each item.
Download center changes
List the needed changes.
