The DISCOVER phase is completed during the software requirements, that is, the feasibility study is completed, the company decides to carry out the project / product
Afterwards, the Define phase of the software demand is entered. DEFINE phase includes the following things:
1) Analyze the risk of the project, write project risk control reports. In China, this report is equivalent to a furnish, document writing
Let's put it there; why, because the control risk needs cost, the domestic boss doesn't want cost, and always wants only
Is Money & Money.2) Clear the functional requirements of the project, the demand document of the project. The functional demand document may not only one, maybe each subsystem has a separate demand document; uncertain functional requirements
You should use TBD to sign; functional requirements documentation may include data dictionary. Functional requirements should be made by the project's development manager
The project, but I am involved, the demand document is done by the small soldiers, huh, huh, because the functional demand document is too trivial,
When the official doesn't do this little thing that has no sense of accomplishment. Of course, the functional demand document for some projects is to sign the user.
Such document companies will pay more attention. 3) Establishing a demand tracking matrix requires track matrix, which should be completed and tracked by the development manager of the project, starting soft in me.
When a part, a senior programmer tells me that the demand track matrix is from the project.
Configure managers to do, harm me for a while; later think about, the needs tracking matrix will guide
Later development, the writing personnel should also be the development manager. 4) The review of the evaluation function needs of functional requirements should be initiated by the project manager, industry experts and customers participate in the meeting, discussed in the form of meeting,
Review Notes.
