"Ten Steps to software Requirements" reading notes two

"Ten Steps to software Requirements" reading notes two

This time, "the software needs ten steps to go" after three, respectively, "method", "Planning chapter", "Development article".

Method Article :

1. The mission of the methodological approach to demand engineering is to show the structure and law of the problem.

2. Analysis and calculation method is one of the essential differences between demand planning method and traditional demand analysis method. Analysis and calculation including system support capacity calculation and business development capability calculation

3. Structured Analysis Method (aka SA) method is the method used in the book's Business Modeling, System modeling and system modeling in demand planning.

4. Object-oriented analysis method in demand analysis This book uses the object-oriented analysis method as the use case analysis and the function requirement analysis method

5. Demand Unified Mode method demand Unified mode method and the idea of software design mode is the same, it is also a model to classify the requirements of most software systems.

6. Requirements management tools enable document-to-reality consistency, track the status of each requirement, establish a chain of relationships with software development activities, and more

7. Requirements formal Description method formal requirements Specification (formal specification) means that the requirement model of the system is constructed with strict mathematical knowledge and symbols, which makes the demand model more rigorous, non-ambiguity and easy to infer.

8. Problem-oriented demand analysis method The demand analysis method oriented to problem domain (PD) is a new requirement analysis method. Compared with the method of structured requirement analysis and object-oriented requirement analysis, the style of demand modeling is obviously different.

Planning Chapter

1. The thinking of demand planning and process demand planning work is oriented to "whole business, full information, whole system", using the analytic synthesis, inductive deduction logic method to organize the business logic model of organization and object, and make systematic planning based on the business logic model.

2. Business Research Business Research is to learn from scientific research methods to restore a complete, accurate and logical business landscape through data research and field research

3. Application Modeling application modeling includes business modeling, System modeling, and system modeling

4. System planning system planning is based on the organizational structure of business research, business matters, the size of business data and user expectations of business objectives, and combined with the results of application modeling to support this scale and application of information systems to form the content of a plan

5. Analysis and calculation analysis calculation including system support capacity calculation and business development capability calculation

6. The Report preparation Requirements Planning report is not only the basis of demand development work, but also the guidance document of software development work, or the foundation of the next information construction

7. Planning Review Planning Review is a task to examine the requirements planning report, which is an inspection of the completeness, accuracy, rationality and regularity of the work results in the demand planning stage.

Development articles

1. Demand development thinking and process demand development work is "technology as the core, business as the assistant" as the guiding ideology, in order to say clearly the software system "do what" software requirements specification as the goal

2. Demand acquisition here the demand and the traditional requirements of the project needs to get the most difference, one is not with the customer face contact to obtain the demand, second, only need to take the work of demand planning as the first source of demand acquisition

3. Demand analysis needs analysis work is divided into analysis and synthesis of two parts of the work. The analysis work is to find out the internal connection and possible contradiction between the demand information, and the comprehensive work is to remove these contradictions to establish the function of the software system and the logical model of the data.

4. Planning requirements for software requirements are composed of business requirements, user requirements, and system requirements. And these requirements are in the process documentation, if these documents as a grain of pearls, then we need a line to wear them into a pearl necklace, the line of the Pearl to wear is the software requirements specification

5. Requirements Verification Requirements Verification is strictly a test software Requirements specification, which is the last activity of demand development, is a complete inspection of the previous or stage work results

The problem is the gap between ideal and reality, the goal is a signpost between the ideal and the reality, the question decision scope, the goal decision depth.

A class of users facing the information system and solving certain problems or some problems are the salient features of the application. The application modeling, which is composed of three modeling of business modeling, System modeling and system modeling, is the intermediate process from business system to information system, is the bridge between business system and information system, and its basic method is mapping of business and system. Business is a holistic understanding of the components of a business system, and the system function is a holistic understanding of the components of information systems, one by one of which correspond but not simply. Business domains and subsystems are one-to-one mappings, business matters and functional modules are single-to-many, business issues and functional modules are single-to-many, and the business view and basic tables are a pair of more.

Demand Planning report is not only the basis of open demand work, but also the guidance document of software development work, or the foundation of the next information construction.

"Ten Steps to software Requirements" reading notes two