Software project plan preparation policy
The purpose of software project plan is to develop a reasonable implementation of software engineering and management software projects. The software project plan has focused on estimating the work to be implemented, establishing the necessary commitments and defining a work plan.
The purpose of software project plan is to develop a reasonable implementation of software engineering and management software projects. The software project plan has focused on estimating the work to be implemented, establishing the necessary commitments and defining a work plan. Includes the following points:
1. Work documentation that will be used to prepare software project plans and tracking software projects.
2. For the implementation of the implementation of the implementation of the documentation.
3. Relevant organizations or individuals recognize their commitments to the software project.
4. Specify the software project person in charge responsible for implementing the commitment of the software project and develops the software development plan for the project.
5. Make sure there is a documentation in the software project and is recognized.
6. The software development plan should specify the division of staff and clear responsibility.
7. Plan for appropriate resources and funds needed for software projects.
8. Training for the Software Project heads, software engineers and other related personnel to prepare relevant personnel to their responsibilities.
9. Establish a related software project group and related program demonstration group.
10. Software project groups and related program demonstration teams participate in all project plan preparations throughout the project life.
11. Review according to the commitment of senior management or enterprise external institution software projects in writing.
12. It is clearly divided into pre-defined, scalable software life cycles.
13. Software development plans to develop projects in writing.
14. Plan a software project documentation.
15. Determine the software items need to establish and maintain the controlled software products.
16. Estimate the size of the software product (or change in software product size) in accordance with written processes.
17. Estimates the workload and cost of software projects in accordance with written processes.
18. Estimation of key computer resources needed to project in writing in writing.
19. Get the software development schedule of the project in writing.
20. Identify, evaluate software risks related to cost, resources, progress, and project technology, and documentation.
21. Software engineering mechanisms and support tools preparing the project.
22. Record the software plan to prepare data.
23. Develop and use metrics to determine the status of the software plan activity.
24. Regularly reviewed software project plan activities regularly with senior management.
25. Review the software project plan activity with software project administrators in regular and event-driven methods.
26. Reviewing and reviewing software project plan activities and working products with software quality assurance staff and document the results.
