In principle, the contractor's project management and project analysis ability should be respected, and the specific work should not be in-depth and not interfere with the contractor's autonomy. However, if there is a big gap and deficiency in the process of project cooperation, in order to ensure the smooth development of the project, the supervisor must strengthen the ability of project management and project analysis, and adhere to the methods and means of absorption, assimilation and implementation in specific operations.
2. The role of schedule demand analysis and supervision.
Demand analysis is the beginning of a project and the cornerstone of project construction. 80% of failed projects in the past were caused by unclear demand analysis. Therefore, one of the key factors for the success of the project is the degree of grasping the demand analysis. The overall risk of the project is manifested in unclear demand analysis and unreasonable business process. Users are not used to or unwilling to use the contractor's software, or it is difficult to use it, which leads to the failure of the project. Therefore, as a third-party supervision company, we must remind contractors and customers of the importance of demand analysis and take necessary means and methods to conduct demand research. At the same time, the supervisor should also go deep into the specific demand survey. Only in this way can we truly grasp the needs and direction of users and have a say in the future functional 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 wide coverage of the industry, as well as the high risk of requirements analysis, the importance of requirements analysis in the whole software development cycle is self-evident, and the difficult things are really difficult to do, which are basically caused by the following reasons:
(1) The customer is not clear about the demand; (2) The demand itself often changes; (3) Analysts or customers have misunderstood.
2. 1. 1 The customer cannot explain the requirements clearly.
Some customers just have a vague feeling about the demand, and of course they can't tell the specific demand clearly. For example, many departments, institutions and units across the country are building application systems and networks, and most of the leaders and office workers at the client are not aware of the use of computer networks; Lack of systematic IT construction experts and knowledge. At this time, software system analysts will be asked to imagine requirements for them. There is a certain subjectivity in the project demand, which lays a potential risk for the project construction.
2.2.2 The demand itself is constantly changing.
According to the past historical experience, with customers' understanding of information construction and improvement of their own business level, they will put forward new requirements and changes to the requirements of the project at different stages and periods. In fact, there is no software whose requirements have changed less than three times in history, so we should accept the fact that "requirements will change", so we should nip in the bud when analyzing requirements, and try our best to analyze which requirements are stable and which are variable. In order to design the system, the core of the software is based on stable requirements, while leaving room for change. The consulting supervisor plays an intermediary, fair and just role in defining the function of demand analysis, so he must also participate in the preparation of demand analysis, thus helping customers and contractors define the system function boundary of "what to do" and "what not to do".
2. 1.3 The analyst or customer misunderstood.
Software system analysts can't all be generalists, let alone experts in the industry. Different analysts may have different understandings of the needs expressed by customers. If the analyst understands it wrong, it may lead to the waste of future development work. I remember a joke that "an alien spy sneaked into the earth to spy on information, and it wrote a report to the boss:" Cars dominate the earth. They drink gasoline and roll on four wheels. Loud voice, eyes can shoot strong light at night. ..... Interestingly, there is a kind of parasite called' human' living in the car, and these parasites completely control the car. Therefore, the specificity of analyst's knowledge will also lead to misunderstanding and failure of demand analysis. At this time, it is necessary to consult the supervision company according to the actual project demand research plan to remind the contractor to strengthen business understanding and pay attention to communication skills.
2.2 consulting supervision company how to conduct demand analysis
Requirements analysis does not start with clues like detective reasoning. We should understand the macro issues first, and then the details.
An application software system (labeled S) can cover a large area and can be classified into different problem domains (labeled D), and each problem domain corresponds to a software subsystem.
S = { D 1，D2，D3，… Dn }
The problem domain Di consists of several problems (denoted as p), each of which corresponds to a soft component in the subsystem.
Di = { P 1，P2，P3，… Pm }
The problem Pj has several behaviors (or functions, denoted as F), and each behavior corresponds to the implementation interface in the software component.
Pj = { F 1，F2，F3，… Fk }
The requirement specification written according to the structure of Figure 4. 1 is suitable for leaders who only want to know the macro requirements and technicians who need to know the details. When writing the requirements specification, we should also pay attention to two issues:
(1) It is best to indicate "why" for each requirement, so that programmers can understand the essence of the requirement and choose the most appropriate technology to implement it.
(2) The demand statement must not be ambiguous, let alone inconsistent. If there is ambiguity or inconsistency, this requirement should be re-analyzed.
2.3 consulting supervision company demand analysis methodology
According to the past engineering experience, it is basically believed that the working method of demand analysis should be positioned in "three stages" (also known as "three-step method").
First of all: "interview", this stage is to communicate with the leaders and business personnel of specific users. The main purpose is basically to understand the specific needs and trends of our users from a macro perspective, and to understand the existing organizational structure, business processes, hardware environment, software environment, existing operating systems and other specific practical and objective information. Establish good communication channels and methods, and it is best to designate the interface person of this project according to specific functional departments and committees.
Means of realization: interviews and questionnaires.
Outputs: investigation report and business process report.
The third stage: "confirmation", according to the results of the above two stages, specific process refinement and data item confirmation are carried out. At this stage, the contractor must provide a prototype system, a clear business process report and data list, and can clearly describe the business process design objectives of the system to users. Users can view business process reports and data item tables; Operate the demonstration system provided by the contractor to provide feedback and sign the audited reports and documents.
Means of implementation: visit (review and confirm) and submit business process report and data item list; Prototype demonstration system
Output: requirement analysis report, data item, business process report and prototype system feedback (the latter three can be unified in the requirement analysis report and submitted to users and supervisors for confirmation and filing).
Generally speaking, the three stages of demand analysis are an important part of demand research. The implementation and adoption of three-stage or three-step method also ensures the success of the project for users and contractors. Of course, in the process of system construction, especially after adopting the iterative development mode, the requirements analysis will continue, and it is basically in the last two stages in the later requirements improvement.
For more information about project/service/procurement bidding, and to improve the winning rate, please click on the bottom of official website Customer Service for free consultation:/#/? source=bdzd