需求分析文档模板Requirements-Specification-Template
YourProject Requirements SpecificationVersion 1.01/29/2022 1:39:00 PMUse this Requirements Specification template to document the requirements for your product or service, including priority and approval. Tailor the specification to suit your project, organizing the applicable sections in a way that works best, and use the checklist to record the decisions about what is applicable and what isnt.The format of the requirements depends on what works best for your project.This document contains instructions and examples which are for the benefit of the person writing the document and should be removed before the document is finalized.To regenerate the TOC, select all and press F9.Table of Contents1. EXECUTIVE SUMMARY2LIProject Overview21.2Purpqse and Scope of this Specification22. PRODUCT/SERVICE DESCRIPTION22.1Product context22.2User characteristics22.3Assumptions32.4Cqnstraints32.5Dependencies33. REQUIREMENTS33.1functional Requirements43.2User |nterface Requirements53.3Usability53.4Performance53.4.1Capacity53.4.2Availability53.4.3Latency53.5Manageability/Maintainability53.5.1Monitoring53.5.2Maintenance63.5.3Operations63.6System |nterface/|ntegration63.6.1Network and Hardware Interfaces63.6.2Systems Interfaces63.7Security73.7.1Protection73.7.2Authorization and Authentication?3.8Data Management73.9Standards compliance73.10pQRTABILITY84. USER SCENARIOS/USE CASES85. DELETED OR DEFERRED REQUIREMENTS86. REQUIREMENTS CONFIRMATION/STAKEHOLDER SIGN-OFF9APPENDIX9Appendix A.Definitions, Acronyms, and Abbreviations9Appendix b.references9appendix Requirements traceability matrix9APPENDIX DQrGANIZING THE REQUIREMENTS111. Executive Summary1.1 Project OverviewDescribe this project or product and its intended audience, or provide a link or reference to the project charter.1.2 Purpose and Scope of this SpecificationDescribe the purpose of this specificationand its intended audience. Include a description of what is within the scope what is outside of the scope of these specifications. For example:In scopeThis document addresses requirements related to phase 2 of Project A: modification of Classification Processing to meet legislative mandate ABC. modification of Labor Relations Processing to meet legislative mandate ABC.Out of ScopeThe following items in phase 3 of Project A are out of scope: modification of Classification Processing to meet legislative mandate XY Z. modification of Labor Relations Processing to meet legislative mandate XYZ.2. Product/Service DescriptionIn this section, describe the general factors that affect the product and its requirements. This section should contain background information, not state specific requirements .2.1 Product ContextHow does this product relate to other products? Is it independent and self-contained? Does it interface with a variety of related systems? Describe these relationships or use a diagram to show the major components of the larger system, interconnections, and external interfaces.2.2 User CharacteristicsCreate general customer profiles for each type of user who will be using the product. Profiles should include: Student/faculty/staff/other experience technical expertise other general characteristics that may influence the product2.3 AssumptionsList any assumptions that affect the requirements, for example, equipment availability, user expertise, etc.For example, a specific operating system is assumed to be available; if the operating system is not available, the Requirements Specification would then have to change accordingly.2.4 ConstraintsDescribe any items that will constrain the design options, including parallel operation with an old system audit functions access, management and security criticality of the application system resource constraints other design constraints 2.5 DependenciesList dependenciesthat affect the requirements. Examples: This new product will require a daily download of data from X, Module X needs to be completed before this module can be built.3. Requirements Describe all system requirements in enough detail for designers to design a system satisfying the requirements and testers to verify that the system satisfies requirements. Organize these requirements in a way that works best for your project. See Appendix DAppendix D, Organizing the Requirements for different ways to organize these requirements. Describe every input into the system, every output from the system, and
收藏
编号：347329199
类型：共享资源
大小：25.44KB
格式：DOCX
上传时间：2023-03-14
10
金贝
- 关 键 词：
-
需求
分析
文档
模板
Requirements
Specification
Template
- 资源描述：
-
[YourProject] Requirements Specification
Version 1.0
1/29/2022 1:39:00 PM
Use this Requirements Specification template to document the requirements for your product or service, including priority and approval. Tailor the specification to suit your project, organizing the applicable sections in a way that works best, and use the checklist to record the decisions about what is applicable and what isn't.
The format of the requirements depends on what works best for your project.
This document contains instructions and examples which are for the benefit of the person writing the document and should be removed before the document is finalized.
To regenerate the TOC, select all
and press F9.
Table of Contents
1. EXECUTIVE SUMMARY2
LIProject Overview2
1.2Purpqse and Scope of this Specification2
2. PRODUCT/SERVICE DESCRIPTION2
2.1Product context2
2.2User characteristics2
2.3Assumptions3
2.4Cqnstraints3
2.5Dependencies3
3. REQUIREMENTS3
3.1functional Requirements4
3.2User |nterface Requirements5
3.3Usability5
3.4Performance5
3.4.1Capacity5
3.4.2Availability5
3.4.3Latency5
3.5Manageability/Maintainability5
3.5.1Monitoring5
3.5.2Maintenance6
3.5.3Operations6
3.6System |nterface/|ntegration6
3.6.1Network and Hardware Interfaces6
3.6.2Systems Interfaces6
3.7Security7
3.7.1Protection7
3.7.2Authorization and Authentication?
3.8Data Management7
3.9Standards compliance7
3.10pQRTABILITY8
4. USER SCENARIOS/USE CASES8
5. DELETED OR DEFERRED REQUIREMENTS8
6. REQUIREMENTS CONFIRMATION/STAKEHOLDER SIGN-OFF9
APPENDIX9
Appendix A.Definitions, Acronyms, and Abbreviations9
Appendix b.references9
appendix Requirements traceability matrix9
APPENDIX DQrGANIZING THE REQUIREMENTS11
1. Executive Summary
1.1 Project Overview
Describe this project or product and its intended audience, or provide a link or reference to the project charter.
1.2 Purpose and Scope of this Specification
Describe the purpose of this specificationand its intended audience. Include a description of what is within the scope what is outside of the scope of these specifications. For example:
In scope
This document addresses requirements related to phase 2 of Project A:
• modification of Classification Processing to meet legislative mandate ABC.
• modification of Labor Relations Processing to meet legislative mandate ABC.
Out of Scope
The following items in phase 3 of Project A are out of scope:
• modification of Classification Processing to meet legislative mandate XY Z.
• modification of Labor Relations Processing to meet legislative mandate XYZ.
2. Product/Service Description
In this section, describe the general factors that affect the product and its requirements. This section should contain background information, not state specific requirements .
2.1 Product Context
How does this product relate to other products? Is it independent and self-contained? Does it interface with a variety of related systems? Describe these relationships or use a diagram to show the major components of the larger system, interconnections, and external interfaces.
2.2 User Characteristics
Create general customer profiles for each type of user who will be using the product. Profiles should include:
• Student/faculty/staff/other
• experience
• technical expertise
• other general characteristics that may influence the product
2.3 Assumptions
List any assumptions that affect the requirements, for example, equipment availability, user expertise, etc.For example, a specific operating system is assumed to be available; if the operating system is not available, the Requirements Specification would then have to change accordingly.
2.4 Constraints
Describe any items that will constrain the design options, including
• parallel operation with an old system
• audit functions
• access, management and security
• criticality of the application
• system resource constraints
• other design constraints
2.5 Dependencies
List dependenciesthat affect the requirements. Examples:
• This new product will require a daily download of data from X,
• Module X needs to be completed before this module can be built.
3. Requirements
• Describe all system requirements in enough detail for designers to design a system satisfying the requirements and testers to verify that the system satisfies requirements.
• Organize these requirements in a way that works best for your project. See Appendix DAppendix D, Organizing the Requirements for different ways to organize these requirements.
• Describe every input into the system, every output from the system, and展开阅读全文
金锄头文库所有资源均是用户自行上传分享，仅供网友学习交流，未经上传用户书面授权，请勿作他用。
