Joke Collection Website - Joke collection - What is the working mechanism and methodology of IT supervision in the demand analysis stage of project construction?

What is the working mechanism and methodology of IT supervision in the demand analysis stage of project construction?

1. Positioning of demand stage supervision

In principle, respect the project management and project analysis capabilities of the contractor, and carry out specific tasks in a manner that does not go in-depth or interfere with the contractor's work. Autonomy is the main focus, but if during the project cooperation process it is discovered that there are large gaps and deficiencies in the project management and project analysis capabilities of Chinasoft, in order to ensure the success and smooth development of the project, the internal supervision must strengthen the project management capabilities and project Analytical ability, and the ability to adhere to methods and means of absorption, assimilation, and implementation in specific operations.

2. The progress of demand analysis and the grasp of the role of supervision

Needs analysis is the beginning of a project and the cornerstone of project construction. In previous failed construction projects, 80% It is caused by unclear demand analysis. Therefore, one of the key factors for the success of a project is the degree of grasp of demand analysis. The overall risk of the project is specifically manifested in unclear demand analysis and unreasonable business processes. Users are not accustomed to or unwilling to use the contractor's software, or it is difficult to use it, resulting in project failure. Therefore, as a third-party supervision company, it is necessary to remind the contractor and client of the importance of demand analysis and use necessary means and methods to conduct demand research. At the same time, the supervisor should also conduct in-depth specific demand research. Only in this way can we truly grasp the needs and directions of users, and have a say in future function definition and development scope.

2.1. Why should the consulting supervisor focus on monitoring demand analysis?

Due to the particularity of the project and the broadness of industry coverage, as well as the high risk of demand analysis, the entire In the software development cycle, the importance of demand analysis is self-evident. Demand analysis is indeed difficult to do. This is basically due to the following reasons:

(1) Customer The requirements cannot be explained clearly; (2) the requirements themselves change frequently; (3) analysts or customers have misunderstandings.

2.1.1 Customers cannot clearly explain their needs

Some customers only have a vague sense of their needs, and of course they cannot explain their specific needs. For example, many departments, agencies, and units across the country are building application systems and networks. Most of the client's leaders and office staff do not know the use of computer networks; they lack experts and knowledge in systematic IT construction. At this time, software system analysts will be asked to imagine requirements for them. There is a certain degree of subjectivity in project requirements, which creates potential risks for project construction.

2.2.2 The demand itself changes frequently

Based on past historical experience, as the customer’s understanding of information construction and the integration of its own business level improve, there will be changes in different stages. New requirements and demand changes are put forward for the needs of the project over time. In fact, no software in history has changed its requirements less than three times, so we must accept the fact that "demand will change", so we must take precautions when conducting demand analysis. In the future, try your best to analyze clearly which are stable needs and which are volatile needs. In order to build the core of the software on stable requirements while leaving room for changes when designing the system. The consulting supervisor plays an intermediate, fair and impartial role in defining the functions of the demand analysis, so it must also participate in the preparation of the demand analysis in order to assist the client and the contractor in defining "what to do" and "what not to do" ” system functional boundaries.

2.1.3 Analysts or customers have misunderstandings

It is impossible for software system analysts to be all-rounders, let alone experts in the industry. Different analysts may have different understandings of the needs expressed by customers. If the analysts understand it wrongly, it may lead to futile development work in the future. I remember a joke: "An alien spy lurked to the earth to spy on intelligence, and he wrote a report to his boss: "The one who dominates the earth is car. They drink gasoline and roll on four wheels. It has a loud voice and its eyes can emit bright lights at night. ...What’s interesting is that there are parasites called ‘people’ living in the car, and these parasites completely control the car.

'"So the specificity of analysts' knowledge will also cause misunderstandings and failures in demand analysis. At this time, the consulting and supervision company must base its research plan on actual project needs and remind the contractor to strengthen business understanding and pay attention to communication skills.

2.2 How does the consulting supervision company conduct needs analysis

Needs analysis does not start with clues like detective reasoning. You should first understand the macro issues and then understand the details.

An application software system (denoted as S) may cover a wide range of areas and can be classified according to different problem domains (denoted as D). Each problem domain corresponds to a software subsystem.

S =. { D1, D2, D3,… Dn }

Problem domain Di consists of several problems (denoted as P), and each problem corresponds to a software component in the subsystem.

Di = {P1, P2, P3,…Pm}

Problem Pj has several behaviors (or functions, denoted as F), and each behavior corresponds to the implementation interface in the software component.

Pj = { F1, F2, F3,… Fk }

The requirements specification written according to the structure of Figure 4.1 is suitable for leaders who only want to understand the macro requirements and technicians who need to understand the details. . Two issues should be paid attention to when writing a requirement specification:

(1) It is best to annotate "why" for each requirement, so that programmers can understand the nature of the requirement so that they can choose the most appropriate technology. To realize this requirement.

(2) The requirement description must not be ambiguous, let alone inconsistent. If there is ambiguity or inconsistency, the requirement must be reanalyzed.

2.3 Consulting supervision company demand analysis methodology

Based on past engineering experience, it is basically believed that the demand analysis work method should be positioned in the "three stages" (also known as the "three-step method")

First of all: "Interview style", this stage is an interview style communication with the leadership and business personnel of the specific user side. The main purpose is basically to understand the specific needs and trends of our users from a macro perspective. It is best to establish good communication channels and methods for specific functional departments and committees and bureaus with specific, practical and objective information about the existing organizational structure, business processes, hardware environment, software environment, and existing operating systems. Can designate the interface person for this project.

Means of implementation: interviews, survey forms

Output results: survey reports, business process reports

The third stage: "Confirmation", this stage is based on the results of the above two stages, carrying out specific process refinement and confirmation of data items. At this stage, the contractor must provide a prototype system and clear business process reports and data item tables. , and can clearly describe the business flow design goals of the system to users. Users can provide feedback by reviewing business process reports and data item tables; operating the DEMO system provided by the contractor, and review the reports that have been accepted. , Document signature and confirmation.

Implementation means: visit (review, confirmation), submit business process report, data item table; prototype demonstration system

Output results: demand analysis report, data items, business process report, Feedback on the prototype system (the latter three can be unified into the demand analysis report and submitted to the user and supervisor for confirmation and archiving)

Generally speaking, the three stages of demand analysis are indispensable in demand research. Ignoring an important part, the implementation and adoption of the three stages or three-step method also provides a guarantee of project success for both users and contractors. Of course, in the process of system construction, especially after adopting the iterative development model, the work of demand analysis will continue. In the later stage of demand improvement, it is basically in the next two stages.

For more information about engineering/service/purchasing tender document writing and production to improve the bid winning rate, you can click on the official website customer service at the bottom for free consultation: /#/?source=bdzd