Software requirements Ten steps to reading notes 1

Starting today to read software requirements Ten steps to this book, the Book of software needs research divided into 10 steps, two stages. The main problems in the book are: difficult problem, performance problem, category problem, divide problem, relationship problem, idea problem, status problem. Mainly for these common easy-out problems, the author to explain and analyze and face these problems should be how to do, from which we solve the problem of the truth.

Demand planning is the biggest bright spot in the new generation of demand engineering, its work is the business, object and information system as the research object, the use of scientific research, system architecture design, information resource planning method, the development of a systematic, scientific, forward-looking demand planning results. The results of demand planning include situation analysis, business system analysis, object system analysis and so on. It lays a solid foundation for demand acquisition in demand development. The principle of demand planning is "business qualitative, quantitative, fixed details, system qualitative, quantitative, fixed macro". This book is composed of principle, knowledge, method, application and organization.

We know that different levels of demand reflect the details from different angles to varying degrees. In the new generation of software requirements engineering, the emphasis on software requirements analysis is based on a new business background and the macro design of information systems to expand the user needs and system requirements analysis. Such software requirements really take care of all the risks involved in the software development process, including customers, users, demand analysts, developers, testers, project managers, and all aspects of the attention and consensus reached in the software requirements are described. We need to take the "heavy business, heavy system" as an important concept of the new generation of software requirements engineering. and re-positioning software requirements and the use of logic method is the software needs to be complete, accurate, clear, change controllable and so on. Software requirements are divided into business and information planning, user requirements analysis and system requirements analysis. Software requirements have both content features and formal features, and different features are the objectives of different software requirements. Software requirements are composed of 3 phases of business requirements and information planning, user requirements analysis and system requirements analysis. The user requirements specification focuses on specific roles for which the business activity is translated into a description of the specific operational behavior and visual behavior that is based on the software tool. The key to the new requirement planning is the problem, the business, the system three kinds of elements. Ask questions, find the root cause, find the crux of the problem we often say in the direction, positioning, fixed point. In the software development process, the requirement risk can not be neglected and omitted, any error (whether understanding or programming) may bring the risk that cannot be underestimated.

Software requirements Ten steps to reading notes 1