□ Where do I start to make a good software? → Investigation of customer needs;
□ Which link determines the value of a piece of software? → Analysis and design of the
software ; □ What is the basis for the successful completion of the software development? → Efficient project management;
□ The main role of software development? → Customers, software project managers, requirements engineers, development engineers, and test engineers; to
complete a software system, it is necessary to have corresponding analysis and design methods, project management methods, and the division and collaboration of roles in different stages of the process.
The successful completion of software requires efficient collaboration among the five core roles of customers, software project managers, requirements engineers, development engineers, and test engineers. One of the foundations of this collaboration is a high degree of consistency in the understanding and approval of the "requirements analysis and software design" documents. These five roles have their own focus on the content of the document, such as
1. Customers who raise requirements : can clearly express their needs, and can confirm whether the raised requirements are understood and correctly reflected in the design document during analysis and design;
2. Software project manager : How to establish an effective project plan, implementation process, resource matching, deliverable template, acceptance criteria and other matters before the project starts, and can achieve the three major goals of project management (quality, schedule, cost) );
3. Requirements engineer : How to efficiently investigate requirements, understand requirements, analyze requirements, and design requirements, how to accurately convert customers' original requirements into system functions that need to be developed, and make documents easy to pass to subsequent development engineers;
4. Development engineer : how to quickly understand the requirement document, check and judge the correctness and feasibility of the requirement document. Accurately converting requirements documents into technical documents is an important guarantee for the success of later development;
5. Test engineer : How to quickly understand the requirements, compile use case scripts that can verify whether the completed system meets the requirements specifications and technical design, and confidently give the judgment results;
The important intersection between the above five roles is the requirements document. Therefore, the requirements document must establish a common language and expression standards, so that the five parties can communicate, transmit, confirm, and accept not only qualitatively, but also quantitatively.
When it comes to software engineering, you may immediately think of software development history, theories, concepts, university textbooks, etc., thinking that software engineering is not knowledge used to support actual software development. "Dahua Software Engineering—Requirements Analysis and Software Design" is a practical analysis and design tool book. It integrates theories, methods, tools, and standards. Provide a set of "methods and standards" for accurate communication and transmission between engineers and engineers.
1. The characteristics of the book
1. Graphicalization
This book divides software engineering into different stages and levels, and provides corresponding reference standard graphics in different stages and levels. Graphical expressions can significantly improve work efficiency and product quality. The graphics used in this book are "natural graphics" expressions. Graphics are the "common language" for correct and rapid communication between five roles, including customers, and it can be done without special training.
The book provides about 480 color and practical graphics.
Figure 1-1 Color printing of the entire book
Figure 1-2 gives detailed descriptions and use cases for each model diagram
2. Standardization
This book has developed a standardized way from graphic expression to text description. Achieve seamless transfer and inheritance between requirements engineers and development engineers. All deliverables are not only qualitative but also quantitative. All deliverables have theories, methods, templates, and standards.
Figure 2-1 The standardized knowledge system in the book
Figure 2-2 Standard model of common analysis and architecture
Figure 2-3 Common drawing standard symbols
3. Engineering
connects the various links of software realization in accordance with the engineering model, so that the design process and design data of the software industry can be operated in accordance with the process just like the construction industry and manufacturing industry, and support project managers to efficiently manage and achieve project management. Three goals.
Figure 3 Standard operating procedure of software engineering
4. Logic Line
From the beginning of the demand investigation to the application design, the whole book always takes "logic" as the main line of guidance for analysis and design, allowing readers to understand knowledge in accordance with logical thinking, and at the same time present the design results in a logical expression. Ensure that the results of analysis and design-requirements documents meet the requirements of software engineers, but also allow customers to understand, confirm, and sign.
Figure 4 Description of the logic line running through the book
Second, the composition of the book
"Big Talk Software Engineering—Requirements Analysis and Software Design"
This book pursues the engineering work of software analysis and design process, so the content in the book is arranged in accordance with the actual work flow of software engineers, as shown in Figure 3. The process is the main line, and the knowledge, methods, tools, standards, etc. required for analysis and design are linked to the relevant nodes of the process, which is convenient for readers to understand, inquire, and quote.
The book is divided into 6 chapters and 22 chapters
□The first chapter: basic knowledge, the basic theories and concepts required for analysis and design;
□The second chapter: requirements engineering, including the pre-investigation preparation content, investigation methods, record templates, and analysis methods , Compilation of requirements specifications, etc.;
□Part 3: Design engineering-summary design part, system planning, design concept, system main line, architecture planning, function planning, data planning, etc.;
□Part 4: Design engineering-detailed design Part, optimize and detailed design for the customer’s business content (process, interface, data, etc.);
□Part 5: Design Engineering-Application Design Part, plan for the application content of the system (prototype, operation, permissions, etc.), Detailed design;
□Chapter 6: Design Engineering-Integrated Design, designing the customer value, management value, business verification, and application verification of the system;
□Appendix: Ability improvement training: logical thinking methods and logical expressions for readers Methods, etc. for training;
3. List of books
The author has been engaged in needs analysis and design training for more than 20 years, and he can conduct collective training for enterprises, and individual book buyers can participate in the "Dahua Communication Group" for direct communication (see the preface of the book for the address of the communication group).