Project implementation plan and overall design report
(
Outline
)
Introduction1. Compile the purpose description to compile the project implementation plan and overall design report, and indicate the intended readers. 2. background description: (1) Name of the software system to be developed. (2) the submitter, developer, user, and computing center or computer network that implements the software. (3) The relationship between the software system and other systems or institutions. 3. Define the definition of the specialized terms used in this document and the original phrase of the foreign letter group. 4. the reference materials list the useful reference materials, such as: (1) approved plans and tasks of the project, contracts, and approvals from higher authorities. (2) Other published documents of this project. (3) 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.
Project 2 Overview1. The work content briefly describes the main work to be carried out in the development of this project. 2. The main participants will briefly describe the main personnel involved in the development of the project, including their technical skills. 3. The product (1) program lists the name of the program to be handed over to the user, the programming language used, and the media form of the storage program, and references the relevant files by reference, the functions and capabilities are described one by one. (2) list the names and key points of each file to be handed over to the user. (3) Non-handed products indicate the products (documents or even some procedures) that the developer group should hand over to the unit but do not need to hand over to users ). 4. Acceptance Criteria for the products to be handed over above, the acceptance criteria shall be described one by one or referenced materials. 5. The latest deadline for project completion
3. Implementation Plan1. decomposition of work tasks and division of labor for the work that needs to be completed in project development, from requirement analysis, design, implementation, to testing, etc, specify the owner and participants of each task. 2. For requirement analysis, design, coding implementation, testing, and handover, the Schedule specifies the scheduled start date and completion date for each task, specify the order of completion of each task and the symbolic event (the so-called "Milestone") that represents the completion of each task "). Clarify in the following form.
| Phase |
Overall Design |
Detailed Design |
Coding implementation |
Test |
Acceptance and handover |
| Schedule |
1------4 |
5------17 |
17------24 |
25-------29 |
29-------31 |
3. Key issues list key issues, technical difficulties and risks that may affect the success or failure of the entire project one by one, and point out the impacts of these problems on the project.
5. Interface Design 4. User Interface Description the commands provided to users, their syntax structure, and corresponding response information. 5. External Interfaces indicate that the arrangement of all interfaces between the system and the outside world includes interfaces between the software and hardware, and interfaces between the system and various supporting software. 6. The internal interface describes the arrangement of interfaces between various system elements in the system.
Six-run Design1. The combination of operation modules indicates the combination of different operation modules caused by different external operation controls on the system. It indicates the internal modules and supporting software for each operation. 2. Operation Control describes each method and procedure of external operation control. 3. Running time indicates that the combination of each running module will take up the time of various resources.
Seven System Data Structure DesignSoftware design is not involved. 1. Key points of the logical structure design are the names and identifiers of each data structure used in the system, and the identifiers, definitions, lengths and or table relationships. 2. The key points of the physical structure design are the storage requirements for each data item in each data structure used in the system, access Method, access unit, physical access relationships (indexes, devices, storage areas), design considerations, and confidentiality conditions. 3. Relationship between data structures and programs:
| Procedure 1 |
Procedure 2 |
...... |
Program m |
| Data Structure 1 |
√ |
| Data Structure 2 |
√ |
√ |
| ...... |
| Data structure N |
√ |
√ |
