CT2 BRD/SRS Template
From UG
(Difference between revisions)
| Line 2: | Line 2: | ||
== Mantis == | == Mantis == | ||
| - | ''<Mantis Number & Link>'' | + | ''<Mantis Number(s) & Link>'' |
== Project Overview == | == Project Overview == | ||
| Line 17: | Line 17: | ||
=== 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, market conditions, external vendors/partners, etc..>'' |
== Assumptions / Constraints == | == Assumptions / Constraints == | ||
| Line 25: | Line 25: | ||
''<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... === |
| - | === Business Requirement 2 === | + | === Business Requirement 2... === |
=== Business Requirement 3... === | === Business Requirement 3... === | ||
| - | === Business Process Flow 1 === | + | === Business Process Flow 1... === |
| - | === Business Process Flow 2 === | + | === Business Process Flow 2... === |
=== Business Process Flow 3... === | === Business Process Flow 3... === | ||
| Line 50: | Line 50: | ||
=== CyberTrax2 Client Application === | === CyberTrax2 Client Application === | ||
| + | ==== User Interface Requirements ==== | ||
| + | ==== Reporting Requirements ==== | ||
| + | ==== User Access / Security Requirements ==== | ||
| + | ==== Logging Requirements ==== | ||
| + | ==== Group / Master Requirements ==== | ||
| + | ==== Filtering Requirements ==== | ||
| + | ==== Archiving Requirements ==== | ||
| + | |||
| + | === Non-Functional Requirements === | ||
| + | ==== Performance Requirements ==== | ||
| + | ==== Support / Maintenance Requirements ==== | ||
| + | ===== User Guides ===== | ||
| + | ===== Log(s) Accessibility ===== | ||
| + | |||
| + | == Technical Requirements == | ||
| + | === Technology Stack === | ||
| + | === External Interfaces === | ||
| + | === Architecture === | ||
| + | |||
| + | == Technical Design & Solution == | ||
| + | === Mock ups === | ||
| + | === Technical Diagrams (Flow Chart, Sequence, UML, Systems Architecture, Technical Architecture, Data Architecture, etc..)=== | ||
| + | === Web / Application (New/Modified classes, methods, etc..) === | ||
| + | === Database (DDL changes) === | ||
Revision as of 14:39, 6 April 2012
Contents |
Mantis
<Mantis Number(s) & 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, market conditions, external vendors/partners, 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.>
