Brief Discussion on "User Demand Manual" template
After communicating with customers, consult a series of requirements and analysis work such as business materials, it is necessary to organize user needs in time and establish a demand document. In this paper, the author practical and relevant information gives a requirements specification template format, hoping to play a valuable role, with you for further discussion.
XXXX project user needs instruction manual
File status:
[√] draft
Officially released
[] Is modifying the file ID: Project No.XXX-RD-RF No.XXX Current version: x.y author:
Completion Date: Year-Month-Day
About other properties of the document can also add such as the required person in charge, the product version number, the associated document number, etc.
Version history
Version / Status Author Participant Start Date Remarks
table of Contents
0. document describes ·············································· ················ 40.1 documentation purposes ······························· ······························· 40.2 document scope ················ ·············································· 40.3 audience · ·················································· ··········· 40.4 reference documents ···································· ···································································································· ··········································· 41. products ??? ·················································· ········· 52 product-oriented user groups ·································· ···························· 53. the product should follow the standard or specification ············· ················································· 54 .Similar products
5. Product functional requirements of ··········································· ··················· 55.0 functional requirements classification ·························· ·············································································· ·················································· ·············································································· ························· 66 non-functional requirements of products ················· ············································· 66.1 user interface requirements · ·················································· ··········· 66.2 hardware and software environment needs ·································· ···························· 66.3 product quality requirements ·················· ········································································································································································································································································································· ·················································· ········· 6 Appendix A:
0. Documentation
0.1 Document purpose
0.2 Documentation
0.3 reader object
0.4 Reference documentation
Tip: List all the references (including informal publications) of this document, the format is as follows:
[Number identifier] author, literature name, publishing unit (or home unit), date
E.g:
[P1-MF] AUTHOR, metrody development specification, institution name, date
0.5 Terminology and Abbreviation Explanation
Abbreviation, terminology
Explanation
...
Product introduction
Product introduction Mainly explains product features, use, project background, etc.
2. Product User Group
(1) Describe the characteristics of users (customers, end users) facing this product,
(2) Describe the product to their use, the benefits, the possible purchase ratio
3. Cooperative products
Reference basis
4. Products should follow standards or specifications
Explain what standards, norms or business rules should be followed by this product
5. Functional needs of products
5.0 Functional Demand Classification
Tip: The functional demand is first roughly divided. The symbols such as Feature A, Function A.1 in the table below should be replaced with a meaningful name.
Function category
Subfunction
Feature A Function A.1 Function A.2 ... Feature B Function B.1 Function B.2 ... ...
5.N function (characterization) n
5.n.m function n.m
Function Description:
......
6. Non-functional demand for products
6.1 User Interface Demand
Demand name
Detailed requirements
...
6.2 Software and Hardware Environmental Demand
Demand name
Detailed requirements
...
6.3
Product quality needs
Main quality attribute
Detailed requirements
Correctness
Robust
reliability
operation efficiency
Ease of use
Friendliness
safety
Scalability
compatibility
portability
...
6.n
Other needs
Appendix A:
