1. Reasons for proposing the project
2. Environmental background of the project
3. Analysis of project advantages (resources, technology, talents, management, etc.). )
4、? Feasibility of project operation
5、? Analysis of uniqueness and innovation of the project
Purpose: What are the functions after development, what functions should be realized, what needs and desires should be satisfied, and what benefits will be brought to people.
3. Significance: from the aspects of importance and necessity, benefits brought by project development and future development prospects.
Extended data:
1, project start-up stage
Do a good job of demand analysis in the early stage. As a bridge between the customer and the project team, the system architect should communicate well with the customer and understand the business, so as to lay a good business foundation for the next system design. Generally, the method is to go to the customer for on-the-spot questionnaire, investigation and communication.
When the system architect describes the functions that the system should realize to the customer, he enters the system design after reaching an understanding with the customer. In the design stage, architects can't set up system components at will just to realize the business. At this time, we should not only consider the function of the system, but also consider the performance and expansibility of the system.
When all the components are designed, it can be announced that the basic model of the system has been successfully built. At this time, it is necessary to test the model with examples. When the business requirements and performance requirements of the system meet the needs of customers, enter the next stage; if not, continue this stage.
At this stage, it is foreseeable that the implementation of the system will encounter some technical difficulties in the future. At this time, it is necessary to extract the technical difficulties and mark the priority, so that programmers can investigate these technical difficulties and provide corresponding solutions.
It is worthwhile to make great efforts at this stage, because spending one or two days now can avoid spending ten days or even more in the future. After the system blueprint and system design drawings are completed, the project is announced to enter the start-up stage.
2. Project planning stage
At this stage, what we need to do is to complete the project schedule, the formation of personnel, the setting of system environment, the risk analysis of the project, the language used in development and the coding convention of the code. These can basically be set through the system architecture described in the system design.
3. Project implementation stage
At this stage, coding and testing are the main tasks. The concrete realization of components in the system design drawing compiled by programmers. The code written should meet the requirements in the coding convention. To prevent mistakes, programmers can check each other's code. A good coding method is test-driven development.
After writing the code, the programmer has to test it himself and submit it after the test has passed. In order to track the progress of the project, a meeting should be held before the end of work every day. At the meeting, the completion progress of the day's work, problems encountered and solutions should be recorded.
4. Project delivery stage
Large-scale projects are generally delivered in installments. When a module is completed, it will be delivered. Only then will the customer dare to sign the acceptance form. The delivery action will be delayed until the last functional module is completed.
Deliverables delivered at this stage should be delivered according to the list listed in the requirements analysis above. Generally speaking, the deliverables are user manual, software code and compiled operating system.
Baidu Encyclopedia-Project Development