Data room Charging System Project Development Plan

Project Development Plan (GB856T--88) 1 Introduction 1.1 writing a project development plan is the first preliminary plan to be made when developing a project, you need to have a rough understanding of the conditions required for the entire project development process. The intended readers of the Project Development Plan include users, developers, managers, and analysts. 1.2 Background

Project Development Plan (GB856T--88) 1 Introduction 1.1 writing a project development plan is the first preliminary plan to be made when developing a project, you need to have a rough understanding of the conditions required for the entire project development process. The intended readers of the Project Development Plan include users, developers, managers, and analysts. 1.2 Background

Project Development Plan (GB856T--88)

1 Introduction 1.1 Writing Purpose

A project development plan is a preliminary plan for determining the project to be developed. You need to have a rough understanding of the conditions required during the entire project development process. The intended readers of the Project Development Plan include users, developers, managers, and analysts.

1.2 Background

Note:

A. Name of the software system to be developed: Data Center Charging System

B. Author: Professor mi Xinjiang

Developers: 10 students

User: all teachers and students of Langfang Normal University

Computing Center or computer network for the software: Library Reading Room, Data room

C. The relationship between the software system and other systems or institutions: VB development and SQL sever2008 database storage.

1.3 definition 1.4 references

List useful references, such:

A. Software Engineering Zhang haifan people's post and telecommunications Press

B. Feasibility Analysis Report

C. approved plans and tasks of the project, contracts, and approvals from higher authorities;

D. Other published files belonging to this project;

E. Documents and materials referenced everywhere in this document, including the software development standards to be used. List the title, document number, publication date, and publishing unit of these documents, and describe the source of these documents: SQL entry

2 Project Overview 2.1 work content

Analysis, planning, coding, testing, and maintenance

2.2 Main participants

Analysts: they have strong communication and presentation skills, need to communicate with users, and understand the needs of users.

Planners: have a holistic view and have a general control over the entire software development.

Coders: they have a certain degree of coding capability and are neat and tidy. Code execution and readability

Testers: they have a certain degree of coding capability, which is higher than the encoding personnel level and can find out system problems.

Maintenance Personnel: competent code personnel are allowed.

2.3 product 2.3.1 Program

Installation Program .exe	Installer file
Microsoft Visual basic 6.0	Programming Language
SQL sever 2008	Storage Program
User Operation Manual	Guide the user 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 schedule	Including personnel responsibilities and project progress
Database Design Specification	Describes the database design process and overview.
User Operation Manual	Introduction and use of software

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.

User services provided	Definition	Start date	Term
Training and Installation	Provides pre-use training for users and provides help when users need it.	After Software Delivery	Depends on the situation
Maintenance	Provide technical support to users at any time	Test Complete	5 years
Operation Support	Provides software security assurance and helps users with problems	After Software Delivery	5 years

2.3.4 non-handed Products

Requirement Analysis specification, system design specification, and data description document

Records of compiled documents such as special definitions and comments

Test Analysis Specification

2.4 Acceptance Criteria

A. after the project is completed, the project will be handed over to the technical personnel for acceptance. The functional, performance, and documentation of the program will be checked first to check whether the program meets the user's needs. After the project is accepted, it will be handed over to the user;

B. users use new programs, and Users fill in user experience feedback to developers.

2.5 deadline for project completion

It takes up to 60 days to complete the project.

2.6 approver and approval date of the plan

Approved by: Professor mi Xinjiang; approved:

3 Implementation Plan 3.1 decomposition 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.

A requirement analysis: first, the requirement analysis personnel should communicate with the user, sort out the user's requirements, and then distribute the prepared user requirements and feasibility analysis reports to the system developers.

B. design: the designer plans the project based on the user requirements collected by the requirement analysis personnel and writes the project development plan.

C implementation: the coding personnel code according to user requirements and the Project Development Plan, and write relevant data description documents.

D. test: The tester obtains the relevant documents, such as the feasibility analysis report, and prepares the test and analysis report;

Emaintenance: participate in system maintenance and user training, and distribute User Manual

Stages	Owner	Participant
Requirement Analysis	Xu lingbo	Xu lingbo
Design	Xu lingbo	Xu lingbo
Implementation	Xu lingbo	Xu lingbo
Test	Xu lingbo	Xu lingbo
Maintenance	Xu lingbo	Xu lingbo
Document Preparation	Xu lingbo	Xu lingbo
Document review	Wang huaying	Wang huaying and Xu lingbo
Print Distribution	Xu lingbo	Xu lingbo
User Training	Xu lingbo	Xu lingbo
Software Installation	Xu lingbo	Xu lingbo

3.2 contact person

Describe the personnel responsible for interface work and their responsibilities, including:

A. the liaison officer responsible for 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 same contract owner of the project.

3.3 Progress

	Scheduled Start Date	Completion date	Required resources
Requirement Analysis		2013/11/03	Student cooperation Survey
Software Design			Network
Coding implementation			PC, Network
System Test			Tester
Delivery and Operation			IDC PC
Training			User
System Installation		2013/12/02	IDC PC

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.

Personnel	Quantity	Budget
Requirement Analysis	2	2000
Project Plan	1	1000
Encoding	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 entire project one by one, and point out the impacts of these problems on the project.

	Key Issues	Technical difficulties	Risks	Impact
Requirement Analysis	At this stage, it is very important for analysts to communicate with users about their needs. Do users clearly express feasible requirements, which can be correctly expressed by analysts and transmitted to planners and developers in the form of documents?
Project Plan	Whether the scheduler can analyze the report based on requirements to make a logical analysis, and use existing tools, such as data flow, to design a full picture of the system, which is highly risky, moreover, they have high requirements on the professionalism and standardization of planners.
Encoding	The coding staff can get the requirement analysis report and project plan report, which can better interpret the requirements and requirements, and have high requirements on the professionalism and comprehension of the coding staff, therefore, communication between them is also very important. At the same time, the system must be readable and normative.
Test	Testers require much higher levels than coding personnel, so as to detect system errors and vulnerabilities and be good at using various testing methods. More problems need to be tested in a short time, perform a deep mining test on the System
Maintenance	System maintenance personnel can be code personnel

4. Supported Conditions

Describes the various conditions and facilities required to support the development of the project.

Personnel: The personnel used in various stages must have a high level of professionalism and will write normative documents. In addition to the personnel with very high requirements, other personnel can communicate with each other.

Device: common PC

Capital: various network, printer, site, paper and other conditions

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.

VB development environment, SQL Sever 2008 database storage, and computer hardware

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.

Demand analysis stage: clearly express the needs and conditions;

Project Development Plan: develop and design a reasonable model together with the scheduler to build a system prototype.

Operation and Maintenance stage: You need to fill in the user experience report after use, and then report it to the maintenance personnel to improve and optimize the system together with the maintenance personnel.

4.3 conditions provided by external entities

The time for work and completion by contractors of external entities, including the conditions and time required for provision by external entities, is listed on an item-by-item basis.

The system is relatively small and does not need to be outsourced.

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).

System A does not need to develop contract-based plans

B. developer training plan: developers should be trained. If necessary, the feasibility analysis report and project development plan should be understood, and the development system language should be reinforced.

C testing plan: suitable test cases should be developed. Testers should be skilled in using black boxes or white boxes for testing, and perform more comprehensive tests on the system, which should be devastating.

D. security and confidentiality plan: developers must sign confidentiality agreements to keep users' privacy or data confidential and some developed documents kept by the initiators. System users set different Permissions

E quality assurance plan: After the system is completed and tested by testers, this plan ensures that there are no obvious errors that will be handed over to users.

F configuration management plan: the plan is allocated by analysts.

G user training plan: before the system is handed over to the user, some operation training, security training, error handling, and user manual should be handed over to the user, and problems should be solved at any time for the user

H system installation plan: install the system on the target computer and ensure that there are no errors or incompatibility. No problem with remote release