Software Requirement Mode reading notes three

Through the one months of reading, I finally read the "Software requirements mode" This book, the first two reading notes have introduced the book of several models, before the basic requirements, information demand mode, data entity demand mode, user function demand mode. This is the performance demand model, adaptive demand mode, access control demand mode and business demand model.

The performance requirements pattern includes five performance demand modes: Impact time (how much time the system needs to complete a request), dynamic capacity (how many things the system can handle simultaneously), throughput (Rate of system processing time), Static capacity (how many types of annoying entities the system can hold) and availability (when the system is available to the user and how reliable).

When we define a certain aspect of performance, if he is worthy of definition, consider the definition carefully, and if it is not, omit it. In the process of doing the requirements often meet performance problems: 1. Writing is easy to equate to implementation difficulties. 2. We define a complete run or just software. 3. What part of the system does the performance indicator apply to? 4. Avoid arbitrary performance indicators. 5. How much impact does the performance factor have on the system? 6. How can I measure the actual performance? 7. When will the performance indicators be met? 8. Define a performance indicator in each of the requirements. 9. If the performance metrics do not reach what to do. In the specific analysis of the five demand patterns, there are individual considerations and processing steps.

Adaptive demand patterns often help to generate robust systems and meet specific goals. But some applicability is expensive to use. This includes 6 aspects: scalability (ready to handle increased business capacity), scalability (easy to insert additional software), installation (ease of installation), non-narrowness (avoid restricting installation elsewhere), diversity (while supporting multiple companies, currencies, etc.), Multi-lingual (multi-lingual user interface supported). The software will slowly grow older and, in constant modification, exert additional pressure on the system architecture. So refactoring, conscious grooming software, can be seen as an effort to slow down the aging process. The process of degradation can be slowed down more effectively. Scalability is an applicability that helps extend the lifespan of your software. Applicability is the basis of the system design color, and the applicability requirements and performance requirements have a complex relationship. The suitability requirements mainly affect the nature of the software, and performance requirements primarily affect the hardware required, paying particular attention to the long-term and short tradeoffs between adaptability and performance.

Access control consists of 3 main activities: 1. Make the system aware of the person (user registration) 2. Confirm that the user is a dubbing person (user authentication) 3. Control what users can do and see (User authorization). Access control demand mode is the only relevant security requirements model, but for the requirements analysis of access control, include: User category, User details (identity details, authentication information, facts, choices, access rights), registration process, password, user authentication and confirmation, permissions and so on.

The business demand model includes fee/tax and multi-organizational single-member (business structure, office, company, etc.) multi-organizational unit requirements include: cell type name, cell type definition, parent unit type, feature, expected number of instances, and additional access control, unit identifier, etc. Fee/Tax requirements include: name, basis, origin, condition, when to levy, payer, payee, determining factors of the rate, system responsibility, reference. Additional information may include special circumstances and factors, human intervention, and the rationale for the amount of the fee.

After reading this book, I have made great progress, the 37 patterns described in the book provide a framework for writing software requirements in specific situations. I have a deep understanding of what information needs to be included in a detailed description of each of these patterns, reminders of common pitfalls, and additional requirements that need to be considered. Whether using traditional analytic methods or agile methods, you can learn how to use the patterns of requirements to write consistent, effective requirements for successful software development. I learned from: identifying interfaces, technologies, and documentation requirements between systems. Define detailed information requirements, including archiving, data types, and data entities. Specifies the availability, capacity, scalability, extensibility, and ease-of-use of the system. Define access controls, including user registration, authentication, and authorization. Specify the requirements for queries, reports, calculation formulas, and fees and taxes. The most important thing is to learn how to write your own demand pattern.

Software Requirement Mode reading notes three