"Requirements Engineering-software modeling and Analysis" reading notes 3

After reading "Requirements Engineering-software modeling and Analysis," the first three parts, I have a preliminary understanding of software requirements, in the subsequent reading I began the fourth part of the book, the need for documentation and validation, in this and part of the reading I began to understand the requirements of the writing specifications of the document, This part is equally important in software requirements.

"Requirements Engineering-software modeling and analysis" in the requirements of the documentation and verification of the main two parts, respectively, is the requirements specification and requirements validation, in the requirements Specification document is described in the requirements Specification document is a core element of the requirements specification activity, to understand the requirements specification activities, It is necessary to clarify the reasons for the documentation, the type of requirement Specification document, the reader of the requirement Specification document, the descriptive means of the requirement specification document, etc. The reason we write requirements specification documents on the one hand, a clear, clear, structured document can better deliver software requirements information and solutions to all developers. Documents can be consistently repeated to the requirements of the information to the developer, the effect is better, can be more accurate to the developer of information. On the other hand, documents can expand people's knowledge and memory ability. In a complex system, the content of information is not fully mastered by any one person. Written documents can not only be able to remember the ability of the forest people, but also effective records. Many different types of hydrangea specification documents can be produced in the process of requirement development. In the information description language can be divided into non-formal language, semi-formal language, formal language. In the writing requirements Specification, template selection and use is equally important, writing templates to choose carefully, to use the standard template, the developer of the project according to their own development of the standard template for building materials adjustment and customization, organize their own software Requirements Specification template. Requirements Specification document writing should pay attention to the contents of the organization, expression and details of the description. A good demand specification document features to be correct, unambiguous, completeness, consistency, importance-and stability classification, can be verified, modifiable, can be tracked. The specification writing of the requirement document can make the software less detours in the future, can develop the customer's demand according to the document, can make the software development more smoothly. In the requirement analysis, the document writing is an important step, its importance is that the quality of the document can directly affect the development of the project speed and the development of software. So in the document writing, we must standardize the writing, the specification of the requirements of the document can reflect the quality of a developer, good development habits.

The verification and validation of requirements in requirements verification is more to ensure the quality of 澶 from the perspective of software engineering. Requirements validation includes activities to determine the following: The software Requirements specification correctly describes the expected system behavior and characteristics, system requirements or other sources to obtain software requirements, requirements are complete and high quality, there is a consistent view of demand, demand for the continuation of product design, Construction and testing provide a sufficient basis. The best type of formal technical review is called Review, and the review of requirements documentation is the most advanced software quality technology available. In order to understand the actual meaning of verification and diagnosis, it is necessary to understand the system validation meaning in the framework of software engineering. In the process of demand analysis, we need to constantly collate, analyze, pay attention to every detail, determine the boundaries of the system. Set up a good model, if you encounter new problems, to timely collation of the records. Comprehensive application of demand analysis technology. Not only do you need to read extensively for each technology, but you need to do a lot of practice. The complete correctness of the software engineering development process is expected to be impossible, and there will always be some small deviations and errors, so it is very important to verify and revise in the FA.

After a long period of reading "demand engineering-software modeling and Analysis" This book has helped me a lot, the book system of software needs to be introduced in detail, as a textbook the advantages of this book is that its knowledge point comparison system, clarity in reading may be a little boring, But his knowledge of the coverage is very rich. In the reading I have a certain understanding of the requirements analysis of the software, whether it is the needs of the acquisition, demand analysis or the writing of the requirements of the document has given me a lot of inspiration, let me in the need to analyze this aspect of more knowledge. Demand analysis is an important step in the software development process, want to do a good job of software needs analysis must be done, in the needs of each step is also very important, every step of the activities are to be taken seriously, demand acquisition, demand analysis, documentation and verification of each step is an essential step in demand, do a good job needs to do software.

"Requirements Engineering-software modeling and Analysis" reading notes 3