The demand statement is the most critical output in the demand stage. Our Testing Department colleagues often complain that some projects still do not know what the system is going to do at the end of the requirement statement, test cases cannot be written. I think many of us, especially those with little work experience, are confused about what to write in the requirement manual, even if they can
RUP
Some terms are often not understood. I will write down my experience and post it on my blog. On the one hand, I will summarize myself, and on the other hand, I hope to discuss it with you and improve it together.
In my opinion, the requirement specification should first describe the background, function overview, system boundaries, relationships with other systems, and operating environment requirements of the system. Each function of the target system is described in detail. The following four elements need to be clearly described: 1,
Business Flow of this function, 2,
Business Rules of this function 3,
Operation Interface of this function 4,
Business entity involved in this function
Business Process:
The Business Process describes the procedure of this function and the roles involved in each step. We recommend that you use an activity diagram and text to describe the business process.
Business Rules:
Business Rules refer to some constraints in the business process, including front-end interface validation rules and background business logic rules. Business Rules are generally described in text. We recommend that you describe the business rules one by one for each operation in the business flow chart.
Operation interface:
The operating interface is the layout and elements of the operating interface that the user faces after the system is built. Some users prefer
Visio
Draw a prototype interface. I suggest using
Html
Prototype. Use
Html
There are two benefits. First,
Lifelike. The interface and operation mode of the prototype system are very similar to those of the real system after acceptance. In this way, users can easily gain an intuitive understanding of the system, and provide more accurate suggestions at the demand stage, which can greatly reduce the uncertainty of the demand. Second,
Use
Html
The prototype can be used directly in the coding phase, which reduces the workload and makes the product and demand deviation not very large.
Business Entity
A business entity refers to the forms, data, and other objects that are operated in each link of a business flow. The demand stage clarifies the attributes of business entities and business entities, which is very helpful for subsequent database design. The Requirement Specification clearly states the "four elements". In fact, it makes the following clear: what is the business processing process? What are the business handling conditions? What interface does the operator use to handle the business? What data is operated at the end of the system and what forms are generated?
Based on the four requirements, the directory structure of the requirement specification is generally like this. 1.
Introduction
1.1
Purpose
1.2
Range
1.3
Project Background
1.4
Definition of main business terms and terms
1.5
References
2.
Requirement Overview
2.1
Current User System
2.2
Target System
2.3
Relationships with other systems
2.4
Border Definition
2.6
Overview of system function models
2.8
Requirements on the running environment of the target system
3.
Detailed requirements
3.1
Function Name 1
3.1.1
Business Process
3.1.2
Business Rules
3.1.3
Business Interface
3.1.4
Business Entity
3.2
Feature 2
3.2.1
Business Process
3.2.2
Business Rules
3.2.3
Business Interface
3.2.4
Business Entity
4.
Interface with other systems
5.
Performance Requirements
5.1
Running Performance
5.2
Maintainability
5.3
Portability
5.4
Troubleshooting requirements
5.5
Events Not Allowed
6.
Appendix
