CT2 BRD/SRS Template
From UG
(15 intermediate revisions not shown) | |||
Line 1: | Line 1: | ||
[[Category:Spec Templates]] | [[Category:Spec Templates]] | ||
- | == | + | == Mantis == |
- | + | ''<Mantis Number(s) & Link>'' | |
- | == | + | == Project Overview == |
- | + | ''<Executive summary of business justification(s), business objective(s), high level project deliverables, project vision, all stakeholders, etc..>'' | |
- | === 2. | + | === 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 specific business requirement.>'' | ||
+ | |||
+ | === CyberTrax2 Internal Application === | ||
+ | ''<Identify all functional requirements for CT2 Internal Application>'' | ||
+ | ==== User Interface Requirements ==== | ||
+ | ==== Reporting Requirements ==== | ||
+ | ==== User Access / Security Requirements ==== | ||
+ | ==== Logging Requirements ==== | ||
+ | ==== Group / Master Requirements ==== | ||
+ | ==== Filtering Requirements ==== | ||
+ | ==== Archiving Requirements ==== | ||
+ | |||
+ | === CyberTrax2 Client Application === | ||
+ | ''<Identify all functional requirements for CT2 Client Application>'' | ||
+ | ==== User Interface Requirements ==== | ||
+ | ==== Reporting Requirements ==== | ||
+ | ==== User Access / Security Requirements ==== | ||
+ | ==== Logging Requirements ==== | ||
+ | ==== Group / Master Requirements ==== | ||
+ | ==== Filtering Requirements ==== | ||
+ | ==== Archiving Requirements ==== | ||
+ | |||
+ | === Non-Functional Requirements === | ||
+ | ''<Identify all non-functional requirements for both CT2 Client Application and CT2 Internal Application>'' | ||
+ | ==== Performance Requirements ==== | ||
+ | ==== Capacity Requirements ==== | ||
+ | ==== Support / Maintenance Requirements ==== | ||
+ | ===== User Guides ===== | ||
+ | ===== Training ===== | ||
+ | ===== Log(s) Accessibility ===== | ||
+ | ==== Testing Requirements ==== | ||
+ | ==== Security Requirements ==== | ||
+ | |||
+ | == Technical Design & Solution == | ||
+ | === Mock ups === | ||
+ | ''<Include mock-ups of UI changes, report changes, etc..>'' | ||
+ | === Technology Stack & Architecture === | ||
+ | ''<Include changes to existing Technology Stack & Architecture - new libraries, updated library versions, new software/hardware, new interfaces, etc..>'' | ||
+ | === Technical Diagrams (Flow Chart, Sequence, UML, Systems Architecture, Technical Architecture, Data Architecture, etc..)=== | ||
+ | ''<Include architecture diagrams and flow charts>'' | ||
+ | === Web / Application (New/Modified classes, methods, etc..) === | ||
+ | ''<List new or modified classes and methods>'' | ||
+ | === Database (DDL changes - new/modified tables, indexes, stored procedures, etc..) === | ||
+ | ''<Summarize database changes>'' | ||
+ | === Configuration (Config File changes)=== | ||
+ | ''<Summarize config changes>'' | ||
+ | === Logging (Log File changes)=== | ||
+ | ''<Summarize Log File changes and locations>'' | ||
+ | === External Interfaces (EDI Message(s), external vendors) === | ||
+ | ''<Identify any new external interfaces. Include sample request and reply along with field definitions. Include Source/Target server(s)/webservice(s) and functional accounts. If this is a modification of an existing EDI message, include samples of current message(s) and new message(s)> '' |
Current revision as of 20:38, 9 April 2012
[edit] Mantis
<Mantis Number(s) & Link>
[edit] Project Overview
<Executive summary of business justification(s), business objective(s), high level project deliverables, project vision, all stakeholders, etc..>
[edit] Project Scope
<Identify in-scope and out-of-scope items>
[edit] Project Dependencies
<Identify internal and external dependencies to the project>
[edit] High-Level Timelines
<High-level milestone dates>
[edit] Risks
<Identify internal and external risks to the project: schedule, resources, technical, business, cost, market conditions, external vendors/partners, etc..>
[edit] Assumptions / Constraints
<Identify all assumptions and constraints for this project>
[edit] Business Requirements
<List each business requirement under a separate heading. Also include process flows (UML, Sequence Diagrams, Swimlane, Flow chart, etc..) as applicable>
[edit] Business Requirement 1...
[edit] Business Requirement 2...
[edit] Business Requirement 3...
[edit] Business Process Flow 1...
[edit] Business Process Flow 2...
[edit] Business Process Flow 3...
[edit] 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 specific business requirement.>
[edit] CyberTrax2 Internal Application
<Identify all functional requirements for CT2 Internal Application>
[edit] User Interface Requirements
[edit] Reporting Requirements
[edit] User Access / Security Requirements
[edit] Logging Requirements
[edit] Group / Master Requirements
[edit] Filtering Requirements
[edit] Archiving Requirements
[edit] CyberTrax2 Client Application
<Identify all functional requirements for CT2 Client Application>
[edit] User Interface Requirements
[edit] Reporting Requirements
[edit] User Access / Security Requirements
[edit] Logging Requirements
[edit] Group / Master Requirements
[edit] Filtering Requirements
[edit] Archiving Requirements
[edit] Non-Functional Requirements
<Identify all non-functional requirements for both CT2 Client Application and CT2 Internal Application>
[edit] Performance Requirements
[edit] Capacity Requirements
[edit] Support / Maintenance Requirements
[edit] User Guides
[edit] Training
[edit] Log(s) Accessibility
[edit] Testing Requirements
[edit] Security Requirements
[edit] Technical Design & Solution
[edit] Mock ups
<Include mock-ups of UI changes, report changes, etc..>
[edit] Technology Stack & Architecture
<Include changes to existing Technology Stack & Architecture - new libraries, updated library versions, new software/hardware, new interfaces, etc..>
[edit] Technical Diagrams (Flow Chart, Sequence, UML, Systems Architecture, Technical Architecture, Data Architecture, etc..)
<Include architecture diagrams and flow charts>
[edit] Web / Application (New/Modified classes, methods, etc..)
<List new or modified classes and methods>
[edit] Database (DDL changes - new/modified tables, indexes, stored procedures, etc..)
<Summarize database changes>
[edit] Configuration (Config File changes)
<Summarize config changes>
[edit] Logging (Log File changes)
<Summarize Log File changes and locations>
[edit] External Interfaces (EDI Message(s), external vendors)
<Identify any new external interfaces. Include sample request and reply along with field definitions. Include Source/Target server(s)/webservice(s) and functional accounts. If this is a modification of an existing EDI message, include samples of current message(s) and new message(s)>