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

As the new semester begins, new readings are also being developed. In many of the teacher's recommended books I chose this "requirements Engineering-software modeling and analysis." First of all, as our textbook this book should have a detailed introduction to software requirements, and as a textbook to believe that its knowledge theory has a certain system structure, for me to read just right. In the beginner stage I am not very familiar with software requirements engineering, can be said to be a blank sheet, reading this book just can enrich my basic theoretical knowledge. At the same time as a textbook I have this book in hand, reading is very convenient. In a word, I began to study this book for a number of reasons.

"Requirements Engineering-software modeling and Analysis" This book is divided into five parts, this phase I mainly browse the introduction and demand acquisition, probably understand from the point of view of software requirements Engineering, take the demand development process as the main line, a complete description of demand acquisition, demand analysis, demand verification, demand specification and demand management requirements engineering activities. Software requirement is located in the initial stage of software engineering, and it is an important independent working stage in the development of SW system, which provides the work foundation for the software engineering follow-up stage, which is very important to the success of the project. With the increasing of the scale of software system and the increasing complexity, the traditional demand technology based on demand analysis has not been able to meet the requirements of the development of modern software in time, and the complete demand engineering project came into being. Demand engineering is a phase of activity that is proposed by developers to further advance into the understanding of software project requirements processing activities. From a developer's perspective, this book focuses on practical techniques and methods, systematically introduces the latest developments in demand engineering, and promotes the integration of theories, methods and technologies in the field of demand engineering. In the system of the introduction of requirements engineering, the use of some examples to my understanding of the requirements of the project further deepened. "Requirements Engineering-software modeling and analysis" began with the introduction of software development, and software development is gradually written to the production of demand engineering. The basis, means and process of software realization of its function is realistic in the user domain, that is, the software system is based on the understanding of its real environment, through the influence of some aspects of reality, or change the communication mode of various parts of reality, finally achieve some purpose or solve some problems. Application-based software is generally used by ordinary users as an Application object, so it also requires the convenience of use. The simulation of functions and the convenience of use only require the feasibility of the technology used. Unlike tool-based software, application-based software is often not generic, they are customized for a specific application environment, and the simulation of the environment is its main concern. The definition of demand engineering in the book: Demand engineering is the sum of all requirements processing activities, which collects information, analyzes problems, integrates ideas, records requirements and verifies their correctness, and ultimately the desired effect of the interaction of the hard software with its environment. It starts from the root of the software requirement, discusses the software requirement in the software engineering system, let me understand the function and significance of the requirement engineering, clarifies the source and whereabouts of the software requirement, and explains how the software demand can be produced based on the problems in the real world. The book emphasizes that pure tool-oriented software for ordinary users is the primary success criterion for functional usefulness, and that some overly complex functions will lose some practicality because of their flexibility, thus being resisted by users. Ordinary user technical capacity is limited, so the operation of the requirements of the main use of convenience, in the use of the premise of the pursuit of the use of high efficiency. It is not necessary to realize the usefulness of the function and the convenience of use, and to utilize the common feasible technology. Effectiveness is the main focus of this kind of software, can be used effectively can occupy a place. Different criteria and concerns determine the three types of softwareIt will be different in production. ,In particular, there are distinct objectives in the analysis phase: purely tool-based software for professional users usually performs software analysis after a certain concept or technical innovation, the main purpose of the analysis phase is to make full use of the innovative advantages of the ingenious functional arrangements The main purpose of the analysis of pure tool-based software for ordinary users is to make the tradeoff of the scheme. The knowledge in the book makes me understand that software is the first demand, according to the needs of the corresponding functions.

"Demand engineering-software modeling and analysis" for beginners to help a lot, in the book from the source of demand, explained the content, objectives, role and significance of demand engineering, and introduced the requirements of the project's activity framework, outlining the requirements of the main activities and practices in the project, so I have a preliminary understanding of the requirements of the project. In the Requirements Acquisition section, the requirements acquisition activities of demand engineering are described, including the content, tasks, results and practices of the acquired activities, as well as how to determine the prospects and scope of the project for the requirements acquisition. This paper discusses how to choose the source of acquiring the demand, gives the method of acquiring the demand, and introduces the preliminary knowledge of the model driving method in demand engineering with the background of demand acquisition. The book uses a lot of theoretical knowledge to introduce the analysis of demand engineering, let me to the requirements of the project gradually added, while the book also quoted some classic examples to analyze, in the analysis of the examples let us understand the theoretical knowledge more thoroughly. Through the study analysis can let the theory knowledge apply in the actual opening method.

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