CT2 BRD/SRS Template

From UG

(Difference between revisions)
Jump to: navigation, search
Line 69: Line 69:
===== Log(s) Accessibility =====
===== Log(s) Accessibility =====
==== Testing Requirements ====
==== Testing Requirements ====
 +
==== Security Requirements ====
== Technical Design & Solution ==
== Technical Design & Solution ==

Revision as of 16:44, 6 April 2012


Contents

Mantis

<Mantis Number(s) & Link>

Project Overview

<Executive summary of business objective(s), high level project deliverables, project vision, all stakeholders, etc..>

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>

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)>

Personal tools