Summary of requirements

Requirements include 3 levels: business needs, user needs, development needs

General flow of requirements analysis:

1. Business people define preliminary documents in the business language, including business requirements and user requirements

2. Developers read the requirements document and communicate fully with the business people, eliminating ambiguity, defining boundaries, and perfecting demand logic

3. Developers define development requirements from a development perspective and define matching test cases as necessary

Agile development advocates face-to-head communication to efficiently understand requirements and use use case cards to record requirements. I think the demand analysis first to learn Chinese, a simple sentence may not be simple, may need to expand the analysis, dug out behind the hidden prerequisites and branching path, after repeated confirmation to obtain the correct and accurate demand. When the requirements cannot be determined on the spot, special labeling of TBD (to be determined) is required to cause focus and orderly analysis and determination of the next step.

Agile development embraces change, which is not afraid of the need to change much, because it has a coping method. The method is the user's strong participation and daily iteration, the whole development process is open to the user, the user needs to be present, every moment has the software that can be run for users, any changes in the user's ideas and development of any changes can be two-way quick to know, so that flowers into the fruit, fruit as soon as possible mature.

Requirements are also non-functional, can be categorized from development quality and quality of operation, development quality is the most important is maintainability and testability, the quality of the operation of the most important is performance, as well as the ability to configure, the status of the monitoring, and security.

Maintainability first requires readability, followed by the need for easy modification, easy to expand. The way to do this is to extract the reusable and potentially flexible parts of the process and strive for excellence.

Testability refers to the ease with which the function is verified, and the ease with which the bug is measured, and the ease with which the performance data is obtained. Common test types are unit tests (white box), Integration Testing (black box), performance testing (external performance under different loads). A high standard of software requires a 100% coverage of the product code for the test code.

Maintainability and testability often consistently require interface-oriented programming, agile development is also test-driven development, and first-write testing drives programmers to interface-oriented programming, and I hope my new team can adopt this approach.

The 2 common metrics for performance are throughput and response time, often requiring a minimum requirement for throughput and a maximum response time, and a baseline configuration for development requirements, that is, what kind of hardware configuration to achieve this goal.

The configuration includes the modification and the effective of the system parameters, the replacement of the module, the switch of the strategy, etc.

The monitoring of the State refers to the ability to gain input and output from the system, the load data of the current system, the recording and notification of abnormal information, etc.

Security refers to the integrity and privacy of data that is not allowed to be exposed, including the use of secure transport protocols, encryption, and signatures.

Summary of requirements