Case study of 5 million + 1 h law in Software Project Demand Survey

From: http://www.cioage.com/art/200909/85777.htm

For software demand research activities, although I have written three related demand management articles, we should consider the overall demand management process from the perspective of the introduction of CMM (II) basic Requirements management kPa activities
This section describes how to carry out the demand management plan activities before the Demand Survey. In a failed project, identify the critical points in the process of standardizing and managing software requirements and the model architecture associated with requirements (refer to the previously written
History of CMM demand management practices, requirement management plan from the CMM perspective, and how to use CRC model to determine requirements). For a long time, I feel like I have been experimenting with several projects.
The demand management of software should have a certain degree of foundation and experience. However, with the guidance and help of the Project Manager in Singapore, further research on software requirements
Understanding and understanding of the layer; summed up the 5 W + 1 h Law in the Demand Survey. Here we will describe some of our processes and experiences, hoping to share and discuss them with colleagues.

Project Background: a medium-sized enterprise information project. Party B's project manager is a senior project management with PMP certificate.
Personnel. Party A's project manager is a Singapore project manager with rich project implementation and management experience.
Personnel. (What needs to be supplemented here is how foreign personnel can use their own experience and skills to allow Party B to fully accept the survey conflicts)

Project member:
Party A: outsourcing project manager and outsourcing project management
Personnel
Party B: Project Manager, system analyst, and interface maker

Work content: Activities in the project demand stage. For system requirements, both parties can reach an agreement with the end user. Party A serves as the outsourcing manager, it mainly follows up and accepts the project progress and results of Party B's project team to ensure that the project completes the expected tasks within the expected time.

Process description: after the project is started, Party B's project manager provides a detailed requirement survey schedule, a list of results in the survey phase, and a list of interface results"
From the perspective of the Plan, Party B's project manager plan is really perfect. In the business demand survey activities with users, Party B not only records the existing business processes of users, including the current process
Restrictions, procedures and other aspects, but also for the user to plan the future system process, is indeed a good start. However, when Party B submits the requirement analysis documents and interfaces at the stage, it finds that there are two types
We cannot combine the requirement analysis document with the interface. At this time, the project manager of Party B explained that the document is more detailed than the interface, so there are some differences in understanding between the two. However, Party
I think it is a bit difficult, but because we are also unfamiliar with the details of the user process, we cannot raise specific questions until one day, after Party B carries out user demand activities with Party B, Party B's project manager
In terms of questions, we finally understand why they made such a document and interface.

First, Party B's project manager has no sequence of questions to users. Our so-called sequence is whether the logic of the project manager is clear. Besides asking about the current process, the most important introduction Project (New Software System)
The Project Manager of Party B only records the process, limitations, and requirements described by the user. In this way, Party B's project manager is in the Analysis and Planning Department
There is no clear purpose and direction when it comes to unified requirements. here we need to introduce the first W law-Why law. Why is why users introduce systems and introduce new information systems to users.
How can we achieve a final result in overall work efficiency? Why's law requires the project manager to be clear at the beginning of the requirement. This project aims to improve the user's work efficiency and improve inter-department
Collaboration mechanism, accelerating system services that respond to customers, and enhancing the competitiveness of enterprises. With such a why introduction, the Project Manager can clarify what kind of systems the user ultimately wants to provide to them.
In terms of system positioning and establishment, there is a clear final goal.

Secondly, with an overall goal, we should start with the requirements of various business processes and introduce the second W law-What law. What is the purpose of this system? What is implemented? Party B
The Project Manager divides the system into functional modules based on the business process problems, process limitations, and system problems to be solved, gradually clarify module process requirements and functional requirements
Requirement and structure requirement. The introduction of what law can help us understand the initial requirements of the system.

Thirdly, introduce the three, four, and five laws-who, when, and where law. This stage is actually the demand refinement stage. Based on what's law, users of the subdivision system need
Analysis of who, at what time, at what stage can or must be performed on this function, combined with the previous what law, clarify the division of the system's process stages, record and analyze the details of system function implementation.
The use case diagram can be used as the basis for the design of the next stage.

Finally, the so-called 1 h law-how law is how to implement the system. Based on the previous why, what, who, when, and where, we have established
A very good basic framework of system requirements, how to analyze system requirements based on these user requirements, how to analyze the requirements and specifications and design and implementation in the next stage is how
Accomplish the system.

The 5 W + 1 h law was introduced in the demand phase to ensure the accuracy of the system requirements to a certain extent, it also enables the project manager or requirement analysis personnel to carry out demand mining and research in a very orderly and organized manner.
Activities, this arrangement is also very clear to the user, know how to work with the project staff. Afterwards, at our suggestion, Party B improved its work style and clarified some work sequences. However, in the final document
Handed in, Party B's project manager has been modifying the format and content of the requirement document to cater to our needs, without retaining the class analysis that should be included in the requirement analysis from rough to fine, it also causes
There are many deterministic factors, and the design work in the future is not smooth. After such calculation, we hope to conduct other analysis and discussion on these problems in the future outsourcing management.