CT2 BRD/SRS Template
From UG
(Difference between revisions)
| Line 2: | Line 2: | ||
== Mantis == | == Mantis == | ||
| - | <Mantis Number & Link> | + | ''<Mantis Number & Link>'' |
== Project Overview == | == Project Overview == | ||
| - | <Executive summary of business objective(s), high level project deliverables, project vision> | + | ''<Executive summary of business objective(s), high level project deliverables, project vision>'' |
=== Project Scope === | === Project Scope === | ||
| - | <Identify in-scope and out-of-scope items> | + | ''<Identify in-scope and out-of-scope items>'' |
=== Project Dependencies === | === Project Dependencies === | ||
| - | <Identify internal and external dependencies to the project> | + | ''<Identify internal and external dependencies to the project>'' |
=== High-Level Timelines === | === High-Level Timelines === | ||
| - | <High-level milestone dates> | + | ''<High-level milestone dates>'' |
=== Risks === | === Risks === | ||
| - | <Identify internal and external risks to the project: schedule, resources, technical, business, cost, etc..> | + | ''<Identify internal and external risks to the project: schedule, resources, technical, business, cost, etc..>'' |
== Assumptions / Constraints == | == Assumptions / Constraints == | ||
| - | <Identify all assumptions and constraints for this project> | + | ''<Identify all assumptions and constraints for this project>'' |
== Business Requirements == | == Business Requirements == | ||
| - | <List each business requirement under a separate heading. Also include process flows (UML, Sequence Diagrams, Swimlane, Flow chart, etc..) as applicable> | + | ''<List each business requirement under a separate heading. Also include process flows (UML, Sequence Diagrams, Swimlane, Flow chart, etc..) as applicable>'' |
=== Business Requirement 1 === | === Business Requirement 1 === | ||
| Line 31: | Line 31: | ||
=== Business Requirement 3... === | === Business Requirement 3... === | ||
| - | === Process Flow 1 === | + | === Business Process Flow 1 === |
| - | === Process Flow 2 === | + | === Business Process Flow 2 === |
| - | === Process Flow 3... === | + | === Business Process Flow 3... === |
== Functional/Non-Functional Requirements == | == Functional/Non-Functional Requirements == | ||
| - | <Identify all functional and non-functional requirements. Maintain | + | ''<Identify all functional and non-functional requirements. Maintain standard headings. If a specific requirement is not required, note as Not Applicable. Each functional requirement must trace back to a business requirement.>'' |
| - | === | + | === CyberTrax2 Internal Application === |
| + | ==== User Interface Requirements ==== | ||
| + | ==== Reporting Requirements ==== | ||
| + | ==== User Access / Security Requirements ==== | ||
| + | ==== Logging Requirements ==== | ||
| + | ==== Group / Master Requirements ==== | ||
| + | ==== Filtering Requirements ==== | ||
| + | ==== Archiving Requirements ==== | ||
| + | |||
| + | === CyberTrax2 Client Application === | ||
Revision as of 14:11, 6 April 2012
Contents |
Mantis
<Mantis Number & Link>
Project Overview
<Executive summary of business objective(s), high level project deliverables, project vision>
Project Scope
<Identify in-scope and out-of-scope items>
Project Dependencies
<Identify internal and external dependencies to the project>
High-Level Timelines
<High-level milestone dates>
Risks
<Identify internal and external risks to the project: schedule, resources, technical, business, cost, etc..>
Assumptions / Constraints
<Identify all assumptions and constraints for this project>
Business Requirements
<List each business requirement under a separate heading. Also include process flows (UML, Sequence Diagrams, Swimlane, Flow chart, etc..) as applicable>
Business Requirement 1
Business Requirement 2
Business Requirement 3...
Business Process Flow 1
Business Process Flow 2
Business Process Flow 3...
Functional/Non-Functional Requirements
<Identify all functional and non-functional requirements. Maintain standard headings. If a specific requirement is not required, note as Not Applicable. Each functional requirement must trace back to a business requirement.>
