Project Development Plan (GB856T--88)
1 Introduction 1.1 Purpose of writing
A project development plan is a preliminary plan that is first done to identify the project to be developed. There is a relatively general understanding of the conditions required for the entire development process of the project. Project development plan intended for readers, developers, managers, and analysts.
1.2 Background
Description
A. Name of the software system to be developed: Computer room charge system
B. Proposed by: Professor Mi Nue-jiang
Developers: 10-period students
User: All teachers and students of Langfang Normal University
The computing center or computer network that implements the software: library reading room. Room
C. The main interaction between the software system and other systems or other institutions: VB Development, SQL sever2008 database storage.
1.3 Definition 1.4 References
Make a list of useful references. Such as:
A. Software project Zhang Haifan People's post and telecommunications press
B. Feasibility Analysis Report
C. Approved planning tasks and contracts, and approval of the higher authorities of the project.
D. Other published documents belonging to this item.
E. Documents and information referenced throughout this document, including the software development standards to be used.
The title, document number, date of publication and publication Unit of these documents are listed, indicating the source of these documents: Getting Started with SQL
2 Project Overview 2.1 work Content
Analysis, planning, coding, testing, maintenance
2.2 Main participants
Analysts: with strong communication skills, need to communicate with users. And clearly express the needs of users
Planners: Have a holistic view. Have a general grasp of the entire software development
Coding personnel: With a certain degree of coding ability. And the coding specification is neat. Code is run and readable.
Test personnel: With a certain degree of coding ability. is higher than the level of the coding personnel, can find the system problem
Maintenance personnel: Able to have coding personnel competent.
2.3 Product 2.3.1 Program
Computer room charge system installation program. exe |
installation program Files |
Microsoft Visual Basic 6.0 |
Programming languages |
SQL Sever 2008 |
Stored programs |
User manual Manual |
Guide users to use the program |
2.3.2 File
Software Maintenance Manual |
Including software system description, program module description, operating environment, software process description, easy to maintain software. |
Project Progress Chart |
Mainly includes the personnel's responsibility and the project progress |
Database Design Manual |
Main description of the design process and summary of the database |
User manual Manual |
Software Introduction and usage instructions |
2.3.3 Service
List the services to be provided to users, such as training installation, maintenance, and execution support, by setting the start date, the level of support provided, and the duration of the service.
User Services Provided |
Defined |
Start date |
Term |
Training Installation |
Pre-use training for users and help users when they need it |
After software delivery |
Depends on the situation |
Maintenance |
Provide technical support to users at any time |
Test complete |
5 years |
Execution support |
Security for software, failure to help users |
After software delivery |
5 years |
2.3.4 non-handover of products
Requirements Analysis Manual, system design Manual, data description document
Documenting the compilation of special definitions, stares, etc. in writing
Test Analysis Manual
2.4 Acceptance criteria
A. The project is completed first by the technical staff for acceptance. First, the function, performance, documentation, etc. of the program are checked. To see if the user's needs, when the acceptance of the user after passing;
B. Users to use the new program, real users fill in the user experience feedback to the developer.
2.5 deadline for completion of the project
The project needs 45 days to complete, up to 60 days
2.6 Approver and approval date of the plan
Approved by: Professor Mi Nue-jiang; Ratification Date: 2013-11-01
3 Implementation Plan 3.1 Breakdown of work tasks and division of Personnel
For the project development needs to complete the work, from the requirements analysis, design, implementation, testing until maintenance. Include the preparation of documents, approval, printing, distribution work, user training work. Software installation work, according to the level of decomposition, indicating the person responsible for each task and participants.
A demand analysis: first by the needs of the analysis of personnel and users to communicate, the user's needs are collated, and then the collated user needs and feasibility analysis report distributed to the system developers.
B Design: The designer makes the project plan according to the user requirements collected by the requirement analyst, and writes the project development plan.
C Implementation: Coding personnel according to user needs, as well as project development plan to encode, write the relevant data documentation
D Test: Test personnel to obtain relevant documents such as feasibility Analysis report, to test and write test analysis report;
E Maintenance: Participation and system maintenance. and user training. Distribute the user manual at the same time
Each stage |
Head |
Participation in the People |
Demand analysis |
Ankylitis Bo |
Ankylitis Bo |
Design |
Ankylitis Bo |
Ankylitis Bo |
Realize |
Ankylitis Bo |
Ankylitis Bo |
Test |
Ankylitis Bo |
Ankylitis Bo |
Maintenance |
Ankylitis Bo |
Ankylitis Bo |
Document preparation |
Ankylitis Bo |
Ankylitis Bo |
Document review |
Wang Huaying |
Wang Huaying, Ankylitis bo |
Print distribution |
Ankylitis Bo |
Ankylitis Bo |
User training |
Ankylitis Bo |
Ankylitis Bo |
Software Installation |
Ankylitis Bo |
Ankylitis Bo |
3.2 Interface Personnel
Describe the people responsible for the interface and their responsibilities, including:
A. The interface person responsible for this project and the user:
B. Responsible for the project and the management agencies of the unit, such as contract planning management Department, Financial department, Quality Management department and other interface personnel.
C. The interface person responsible for the unit responsible for the contract of the project.
3.3 Progress
|
Scheduled start date |
Finish date |
Resource requirements |
Demand analysis |
2013/11/01 |
2013/11/03 |
Student Cooperation Survey |
Software Design |
2013/11/04 |
2013/11/06 |
Internet |
Encoding implementation |
2013/11/07 |
2013/11/17 |
Pc. Internet |
System test |
2013/11/18 |
2013/11/20 |
Test personnel |
Delivery execution |
2013/11/25 |
2013/11/27 |
Computer room PC |
Training |
2013/11/28 |
2013/11/30 |
Use people |
System Installation |
2013/12/01 |
2013/12/02 |
Computer room PC |
3.4 Budget
List the services required for this development project (including the number and time of personnel) and the budget of the funds (including Office, travel, machine, data, communications equipment, rental of special equipment, etc.) and sources.
Personnel |
Number |
Funding budget |
Demand analysis |
2 |
2000 |
Project plan |
1 |
1000 |
Coding |
2 |
2000 |
Test |
2 |
2000 |
Maintenance |
2 |
2000 |
3.5 Key issues
List the key issues, technical difficulties and risks that can affect the success or failure of the project, and point out the impact of these issues on the project.
|
Key issues |
Technical difficulties |
Risk |
Effect |
Demand analysis |
This phase of the communication between the analyst and the user is very important, whether the user will be able to understand the needs of the expression, the analyst can correctly express. Delivered as a document to planners and developers |
Project plan |
Can the planners analyze a logical, based on the needs Analysis report? and using some existing tools, such as data flow, to design a system picture. There is a greater risk and a higher degree of professionalism and regulatory requirements for planners |
Coding |
The coder Gets the requirement analysis report and the project plan report. For the needs and requirements of the more good interpretation of the code for the professional and understanding of the requirements of high, and because of the bad coding staff. So the communication between the communication is also very important. At the same time system to be with very good readability and normative |
Test |
Test personnel require a higher level than the number of people coding. This talent discovers system errors and vulnerabilities and is adept at using a variety of test methods. In a short time to test a lot of other problems, the system of deep excavation test |
Maintenance |
System maintenance personnel can be coders |
4 Support conditions
Describe the various conditions and facilities required to support the development of this project.
Personnel: All stages of the use of personnel need to have a higher professional quality, will write normative documents, in addition to the requirements of high personnel, other personnel have a certain degree of communication and communication skills
Equipment: Ordinary PC Machine
Funds: Various network, printer, site, paper and other conditions
4.1 Computer system Support
Lists the computer system support required for development and execution, including computers, peripherals, communication devices, simulators, compiled (or compiled) programs, operating systems, data management packages, data storage capabilities, and test support capabilities. The requirements for the date of arrival and the time of use are given by item.
VB development environment. SQL Sever 2008 Database storage, and computer hardware
4.2 Work to be undertaken by the user
List the jobs and deadlines that need to be borne by the user. Includes user-provided conditions and time of delivery.
Requirements Analysis Phase: understand the requirements and conditions required to express;
Project Development Plan: Develop a reasonable model together with the planners to build a prototype of the system
Perform maintenance phase: Users are required to fill in the User Experience report after use. Then feedback to the maintenance staff. Optimize the system in good condition with maintenance personnel
4.3 conditions provided by the outside unit
A list of the work to be undertaken by the contractor and the time of completion, including the conditions to be provided by the outside unit and the time provided.
The system is relatively small, this does not need to outsource
5 highlights of the thematic plan
Explain the key points of each project plan (such as sub-contract plan, developer Training Plan, test plan, security plan, quality assurance plan, configuration management plan, user training plan, system installation plan, etc.) that need to be developed.
A system does not require a sub-contract plan
B Developer Training Program: To develop training for developers, such as the need to understand feasibility analysis reports and project development plans, and the need for intensive learning of the development system language.
C Test Plan: To develop a suitable test example, test personnel to skilled use of black box or white box test, for the system to conduct a more comprehensive test, to carry out a destructive test.
D Security Plan: For developers to sign a confidentiality agreement, the privacy or data of the user is confidential, and some of the developed documents are held by the author. System users set different permissions
E Quality Assurance Program: This was done after the system was completed and tested by the test staff. Make sure there are no obvious errors to be used by the user
F Configuration Management plan: This has the analyst to coordinate the allocation
G User training Program: Before the system is handed over to the user, some operational training, security training, error handling, and user manual will be given to the user. At the same time for users to solve this problem at any time
H System Installation Plan: Install the system on the target computer. and the guarantee is not error, or incompatible. No problem with offsite publishing
Computer room charge System--project development plan book