"Demand Engineering--software modeling and analysis" second impressions

Recently the teacher talked about the project's prospects and scope, as well as the stakeholder analysis, just read this chapter.

Before the start of a project, the first thing we need to consider is why we should start the project, that is, what is the goal of this project?

The goal of the project is the business requirements of the system. In many cases, stakeholders can articulate the business needs of the system, and the motivation of the project can be defined by arranging and interviewing the stakeholders. In many cases, however, the stakeholders are unable to express their business needs, or the business needs expressed are not clear enough. Therefore, to find out the business requirements of the system, we should start from the user's question. To analyze the stakeholder's problem, we must first clarify the problem, make them clear, become suitable for analysis. This process begins with the question and the relevant background description.

The problem is generally raised by a single stakeholder, so before discussing it with all stakeholders, agree on the issue itself and reach a consensus. The specific approach is to describe the problem in a standardized format and identify it among the stakeholders. The issue of consensus was a matter of unanimity, but the question of coherence was not necessarily a clear one. The clarity of the problem requires that they have two characteristics that are easy to understand and can indicate the direction of the solution.

It is only when the stakeholders encounter problems in the real world that they try to introduce software systems to achieve certain purposes, so they are deeply impressed with the problem. The issues that need to be explored in order to identify business needs are high-level issues, which are related to organizational strategic objectives, interest distribution, policy planning, business processes, and so on. Those issues related to the specifics of the business are not high-level issues.

In order to derive the business demand from the high-level problem, some analysis of the problem is necessary. In the problem analysis process, you can also determine the system's high-level solutions and system features based on the problem, which can help answer the second question at the start of the project-"What the project intends to do".

Depending on the system's high-level solution and system characteristics, you can define the context of the system and establish the system boundary. This will be the starting point for the demand analysis activity.

Business requirements, high-level solutions, and system features should be documented and defined as project foreground and scope documents. The foreground describes the role of the product and the final function, which unifies all stakeholders in one direction. The scope indicates that the current project is to address which part of the product's long-term planning, the scope declares that it defines the line of demand for the project.

"Demand Engineering--software modeling and analysis" second impressions