Software Requirements Best Practices read the note one

This book mainly starts with the main problems and difficulties in the practice of software requirement, points out the main methods of the transformation, and then explains the task, main points and concrete means of demand development activities such as requirement definition, demand acquisition, requirement analysis and modeling, writing protocol and requirement verification. The operational points of demand management activities including demand baselines, change management and demand tracking are also described.

Software project implementation process, will encounter a lot of problems, and some even many projects can not achieve the desired goal, the root of these problems is the software requirements practice. "It's too hard to do software in China!" Customers even their own needs are not clear! "This kind of complaining is often told by software requirements," he said. Demand failure is also due to incomplete demand, lack of user participation, unrealistic user expectations, frequent changes in demand, and so on. In many software projects, users are always unable to participate effectively in the project, and the active participation awareness and the benefits are proportional to, in order to allow users to participate in, to fully study the different user representatives of the focus, the interest point. Communication on the project will generally lead to the problem of miscommunication, the effective way to solve this problem is to retell in a timely manner. While the demand of customers is magnified, it is necessary for demand analysts to control the demand effectively. The essence of demand is that business analysis is not a technical analysis, and it is necessary to construct appropriate business scenarios. The problem of demand has always been a great disturbance, which needs to be through appearance, analysis essence and experience.

In the information systems, embedded systems, software products and other different angles have the corresponding needs of work, which can provide a practical and effective view of the demand analyst. To more scientifically analyze the different software requirements, we need to choose different clues according to different projects. A process is a key clue to the requirements view of the online things processing system. In the information system, the current idea of demand development advocates from the user's scene, from the business process starting from the horizontal perspective. In the embedded system, the specific usage scenario is the main clue of the demand, and for the user-oriented embedded system, the behavioral analysis is the main point, the embedded system for the specific device, the external interface and the event analysis are the main points, and the SOFTWARE Product classification is different from the online transaction processing system and the management Information system. A software project corresponds to a software product.

Software requirements can be defined as "business knowledge + problem list + other factors" based on experience. Three levels of demand: business requirements, user requirements, and software requirements. Business requirement is a high-level goal of enterprise/organization to software system, which is the goal of software system, which is embodied in two aspects of problem and opportunity, and is the product of requirement definition. User requirement refers to what the user needs to accomplish by using the software, how to complete the demand, that is, user demand is the product of demand capture. Software requirements, also known as system requirements, are the product of demand analysis and modeling. A good standard of demand includes: completeness, fidelity, priority, early intervention in technology, etc. Demand engineering includes two areas of demand development and demand management, the focus of demand development is to develop high-quality requirements specification, the focus of demand management is to ensure that the development of software to meet the requirements.

Requirements definition is to determine the macro-demand of the project, that is, define the business requirements of the project, that is, clear objectives and scope. Problem analysis is the process of understanding real-world problems and user needs and proposing solutions that address these multifaceted aspects, define the problem correctly, and then look for solutions to the problem, but when determining a solution, be sure to consider whether it will cause new problems. After the problem is defined, the next step is to analyze the problem behind the problem, that is, to find the source of the problem, and then you can identify the people associated with the project. At this stage of the requirement definition, it is very important to define the scope of the system, generally using the context diagram to determine the scope of the system, that is, the top-level diagram in the flow chart, the entire development system is understood as a black box, identify the external participants and systems and their interaction. Scope is involved in things, objects, boundaries are the boundaries of the human and system responsibilities. You can then display the Subject field content through the Business Events list and the report list. Business events are divided into external events (events from outside the system, System contributor initiation), and internal events (triggering within the system).

At present, these contents of this book are covered by the teacher's knowledge in class, a deeper understanding of those lessons in the more focused knowledge, through a case learned to think about the way and solve the problem. The software requirements process is important and relates to the success and failure of a project. It is important to identify software requirements, especially business requirements, user requirements, and system requirements, and to define a good context diagram, identify the boundaries of the system, and each business event.

Software Requirements Best Practices read the note one