CT2 BRD/SRS Template
From UG
| Line 64: | Line 64: | ||
===== User Guides ===== | ===== User Guides ===== | ||
===== Log(s) Accessibility ===== | ===== Log(s) Accessibility ===== | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
== Technical Design & Solution == | == Technical Design & Solution == | ||
=== Mock ups === | === Mock ups === | ||
| + | === Technology Stack === | ||
| + | === Architecture === | ||
=== Technical Diagrams (Flow Chart, Sequence, UML, Systems Architecture, Technical Architecture, Data Architecture, etc..)=== | === Technical Diagrams (Flow Chart, Sequence, UML, Systems Architecture, Technical Architecture, Data Architecture, etc..)=== | ||
=== Web / Application (New/Modified classes, methods, etc..) === | === Web / Application (New/Modified classes, methods, etc..) === | ||
=== Database (DDL changes - new/modified tables, indexes, stored procedures, etc..) === | === Database (DDL changes - new/modified tables, indexes, stored procedures, etc..) === | ||
=== Configuration (Config File changes)=== | === Configuration (Config File changes)=== | ||
| - | === EDI Message(s) | + | === External Interfaces (EDI Message(s)) === |
Revision as of 14:47, 6 April 2012
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.>
