Professional Documents
Culture Documents
Requirements Specifications Template: Epri Software Development Process
Requirements Specifications Template: Epri Software Development Process
Requirements Specifications Template: Epri Software Development Process
This document is intended to be a guide to capture the work completed from the Concept
phase through the Requirements phase of the development process following the EPRI
Software Development Process.
Instructions:
1.0 Introduction.........................................................................................................1
2.0 Team Members....................................................................................................1
3.0 Assumptions, Constraints, Schedule and Design................................................1
3.1 Assumptions....................................................................................................1
3.2 Constraints.......................................................................................................2
3.3 Schedule...........................................................................................................2
4.0 General System Description................................................................................2
4.1 System Context................................................................................................2
4.2 System Environments and Modes...................................................................2
4.3 User Characteristics.........................................................................................2
4.4 Operational Scenarios......................................................................................3
4.5 Standards, Procedures, and Processes Used in this Project.............................3
5.0 Functional Requirements....................................................................................3
6.0 Interface Requirements........................................................................................3
7.0 Data Management...............................................................................................3
8.0 Non-Functional / Operational Requirements......................................................3
8.1 Security, Availability, Reliability, Recoverability and Business Continuity. .3
8.2 Maintenance and Support................................................................................4
8.3 Performance, Capacity and Scalability............................................................4
8.4 Technical Reviews, Audits, and Walk-Through..............................................4
9.0 SQA Requirements...............................................................................................4
9.1 Quality Plan.....................................................................................................4
9.2 Test Plan..........................................................................................................5
9.3 Testing Schedule:.............................................................................................5
9.4 Documentation Plan.........................................................................................5
9.5 Delivery, Installation, and Acceptance............................................................6
10.0 Appendices.......................................................................................................6
Software Requirements Document (SRD)
Sample Template
1.0 Introduction
Product Description:
This section should also summarize the decision to develop software of a particular type.
For many software types, certain sections are not applicable.
3.2 Constraints
Constraints are conditions outside the control of the project that limit the design
alternatives. Describe any high level items that limit the developer's options for designing
the software such as:
Standards (including hardware and software) Imposed on the Solution
Schedule
Budget
Preferred Software Programming Language(s)
Requirements Specifications Template
3.3 Schedule
Tasks: Schedule of Tasks for Developing each Deliverable Item. Additional
schedule items may be needed to manage the project as work progresses.
Reliability - Reliability is the probability that the system will be able to process
work correctly and completely without being aborted.
Testing Description: Describes how the developer plans for and executes testing,
both incrementally during development and for the entire product before delivery
to EPRI. Test objectives and responsibilities are given for all testing levels, such
as testing of modules, unit testing, and integration testing.
Defect Tracking: Describes how the developer tracks and resolves software
defects.
Testing Approach: A general overview of the plan for testing the entire system is
given here. Included are how each major group of software features will be tested,
major testing activities, techniques, and testing tools to be used.
Usability: Describes items that will ensure the user-friendliness of the software.
Acceptance: Describe the acceptance criterion for the system to be deployed into
the production environment.
10.0 Appendices
As needed and may include Document References, V&V report references, etc.