Académique Documents
Professionnel Documents
Culture Documents
Planning Document
Software Requirements Document (SRD)
Sample Template
Instructions:
Please elaborate on each subject. You may use your own document(s) instead of
this sample template.
If a topic is not applicable to your software, please enter Not Applicable.
Please submit this document with the Beta software submittal at the latest.
Software Name:
Author:
Date:
Revision History:
Revision #:
Date:
ii
1.1.1
Introduction
Product Description: Describes why the software (or upgrade) is being developed, lists
the most important features and capabilities, and what it is intended to accomplish.
1.1.2
Team Members
List the names, titles, and roles of the project team members.
1.2
Assumptions
Assumptions are statements about future situations, beyond the control of the project,
whose outcome influence the success of a project. Identify basic assumptions upon which
the specific software requirements depend such that if the assumptions change, the
requirements also change. Assumptions include:
1.3
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:
1.4
1.5
1.5.1
System Context
Specify whether the software is totally self-contained or is a component of a larger
software package. Describe the functions of each component and identify the
respective interfaces
1.7
Describe the environments the proposed system requires; such as: test, development,
production, etc. Modes could consist of recovery, standby, outage, debug, etc.
1.8
User Characteristics
Describe those characteristics of the end users that have an effect on the specific
requirements of the software. Some items to consider include:
1.9
Provide a descriptive example of how the system may be used as operational scenarios
(i.e., normal, operation, disaster mode, etc.) without describing how it would be designed.
5.5
Functional Requirements
Interface Requirements
Data Management
Describe the data management requirements for the system, including the primary data
sources and repositories. Also describe the data retention, archival, and warehousing.
1.9.4
Describe the non-functional requirements; do not state how these requirements will be
satisfied.
1.10
Security - describe the requirements for application system security controls; such
as authentication and authorization
1.11
Describe the schedule for review meetings, the description of the reviews, and the
pass/fail criteria.
1.13.1
Training
SQA Requirements
Change Control: Describes how changes to the project scope are controlled, and
who approves these.
1.15
Test Plan
Description: If the developer's approach to testing is already documented in the
Quality Plan, that description is referenced here. Otherwise, the processes to be
used are described. The following Test Plan sections contain a project-specific
description of testing for this project.
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.
Testing Tasks to be Performed: This list enables management to make decisions
on the resources and time needed for testing. Also includes the responsible
individuals or organizations.
Testing Schedule:
Includes tasks and major milestones. Milestone examples are start and end of module or
system tests, system builds, test script creation, and regression testing. These dates are
integrated into the master project schedule.
1.17
Documentation Plan
1.18
Describes how the software product and associated deliverables will be accepted by EPRI
and specific end-users, and how the software will be placed into full operation. See the
EPRI software product requirements for additional required usability elements.
Installation: Describes the planned method for installation: done by the user
independently, done by customer company internal IT services, done by an
external contractor. Specifies the handling of such items as data transfer from
prior releases, and the presence of software elements from prior releases.
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.
1.18.1
Appendices
As needed and may include Document References, V&V report references, etc.