Project development plan sunsnow8 Column

The purpose of preparing a project development plan is to use files, recording the arrangements made for the person in charge of various work during the development process, the development progress, the required budget, the required software and hardware conditions, etc, to carry out and check the development of this project in accordance with this plan. The compilation requirements are as follows:
1 Introduction
1.1 Writing Purpose
Describe the purpose of writing the project development plan and point out the intended readers.
1.2 Background
Note:
A. Name of the software system to be developed;
B. the submitter, developer, user, and computing center or computer network that implements the software;
C. Basic relationships between the software system and other systems or institutions.
1.3 Definition
Lists the definitions of specialized terms used in this document and the original phrases of the foreign acronyms.
1.4 references
List useful references, such:
A. approved plans and tasks or contracts and approvals from higher authorities for this project;
B. Other published documents of the project;
C. Documents and materials referenced everywhere in this document, including the software development standards to be used. Lists the titles, document numbers, publication dates, and publishing units of these documents, indicating the source of these documents.
2 Project Overview
2.1 work content
Briefly describe the main work to be done in the development of this project.
2.2 Main participants
Briefly describe the main personnel involved in the development of this project, including their technical level.
2.3 Products
2.3.1 Program
Lists the names of programs to be handed over to the user, the programming languages used, and the media form of the stored programs, and describes their functions and capabilities one by referencing relevant files.
2.3.2 File
Lists the names and key points of each file to be handed over to the user.
2.3.3 Service
Lists the services to be provided to users, such as training, installation, maintenance, and operation support. The start date, level of support provided, and service period should be specified one by one.
2.3.4 non-handed Products
It indicates that the development team should hand over the products (documents or even some programs) to the unit but not to the users ).
2.4 Acceptance Criteria
For the products and services that shall be handed over above, the acceptance criteria shall be described or referenced individually.
2.5 Delayed Use of project completion personnel
2.6 approver and approval date of the plan
3. Implementation Plan
3.1 separation of work tasks and division of labor
For all the work to be completed during project development, from requirement analysis, design, implementation, testing to maintenance, including document preparation, approval, printing, distribution, and user training, software Installation, etc. It is divided into layers to specify the owner and participants of each task.
3.2 contact person
Describe the personnel responsible for interface work and their responsibilities, including:
A. Responsible for the interface staff of the project and the user;
B. Liaison officers responsible for the project and management institutions of the Organization, such as contract planning management departments, financial departments, and quality management departments;
C. Responsible for the interface personnel of the project and the contracting units.
3.3 Progress
Provides pre-jobs for requirement analysis, design, coding implementation, testing, handover, training and installation. Set the start date, completion date, and required resources, specify the order of completion of each work task, and characterize the symbolic events of completion of each work task (the so-called "Milestone ").
3.4 budget
List the labor services required by the development project one by one (including the number and time of Personnel) and the budget (including office expenses, travel expenses, server hours, data fees, rental of communication equipment and dedicated equipment) and sources of funds.
3.5 Key Issues
List the key issues, technical difficulties, and risks that can affect the success or failure of the entire project one by one, and point out the impacts of these problems on the project.
4. Supported Conditions
Describes the various conditions and facilities required to support the development of the project.
4.1 Support for computer systems
Lists the computer system support required during development and operation, including computers, peripheral devices, communication devices, simulators, compilation (or compilation) one by one) programs, operating systems, data management packages, data storage capabilities, and test support capabilities. The requirements for the arrival date and time of use are provided one by one.
4.2 work to be undertaken by users
List the work to be undertaken by the user and the completion period one by one. Including the conditions to be provided by the user and the time of provision.
4.3 conditions provided by external entities
The time for work and completion by contractors of external entities, including the conditions and time for submission, to be provided by external entities.
5 main points of the topic plan
Describes various special plans (such as contract plan, developer training plan, test plan, security and confidentiality plan, quality assurance plan, configuration management plan, and user training plan) to be developed during the development of this project., system installation plan, etc).