1. Introduction (omitted) 2, project overview
2.1, the purpose, scale and objective (omitted)
2.2, Project Delivery Workpiece A) Programs and Data included in the product. B) SDP03 project development plan SDR01 demand specifications SDD01 architecture design manual SDD02 component design manual SDD03 database design manual SDT01 test plan SDT02 test case SDI01 User Operator SDI02 Installation Maintenance Manual SDI03 Training Manual
2.3, plan evolution
Serial number
Plan
version
Note
1
Program preliminary draft written according to project proposals or bidding programs
0.1
Any changes to this version will not produce a new public version number unless confirmed as subsequent versions.
2
Version by the customer's initial confirmation
0.7
Subsequent versions can be generated, such as: 0.7.1
2
Reprinted version according to the first demand research and overall design
0.9
Subsequent versions can be generated, such as: 0.9.1
3
Finally confirmed the software development content and the version after quality requirements
1.0
For the project acceptance baseline version.
3
If the demand or design changes in small scale and affect the project acceptance, you can generate a new release version number.
1.0.1
The version number is incremented in turn
4
If you need a major demand or design change and affect the project acceptance, a new auxiliary version number can be generated.
1.1
The version number is incremented in turn
5
In case of conceptual or functional major changes, it may affect the positioning and market prospects of this project, you can generate new main versions.
2.0
The version number is incremented in turn
6
If it is not satisfied with the above conditions, the version number can be determined according to the above principles, and the basis and details of the change will be described in detail.
3, project organization
3.1, organizational structure
The project adopts project manager responsibility system, set up project groups, development groups, vesses, and technical support groups.
3.2, external contact
Projects are responsible for project director and project manager. Among them, the project director is responsible for communicating with the customer unit leadership, the project manager is responsible for the connection between the specific business unit.
4, management process
4.1, project estimation
This project will be invested in 10 people to participate in project management, development. It is expected to complete in 4 months, total 40 people, calculated according to 3000 yuan / monthly, production cost is 40 × 3000 = 120,000, management cost = production cost × 30% = 36,000, total cost = production cost management cost = 156,000.
In the trial operation stage, this project will invest 6 people participation. It is expected to be completed in 3 months. Total 18 months, according to 3000 yuan / people, production cost is 18 × 3000 = 54,000, management cost = production cost × 30% = 16,200, total cost = production cost management fee = 70, 200 final project cost = 156,000 70, 200 = 226, 200
At present, the cost and progress estimate of the project is mainly based primarily on the experience of the planners. During the development of this project, the project needs to be re-estimated after each iteration is completed.
4.2. Project Plan This project will be divided into three product packages of A, B, and C according to the product requirements and time schedule requirements, task nature and existing human resources. 2.1.1 Working Segmentation Structure (WBS) 4.2.1.2 Main Milestones and Realizing Standards Projects Establishment Project Leading Group and Project Working Group Release BETA Edition Product Try Operation Acceptance User Acceptance Project Expert Group Check 4. 2.1.3 Important release points and demonstration A B bag beta version A B package official version C package official version A B C package official version 4.2.2, iterative target (omitted) 4.2.3, release version number Description:
version number
name
Description
0.1
Demonstration version
Provide early feasibility evaluation to customers and quality inspection departments
0.7
alpha version
Provide system integration testing to quality inspections
0.7.x
Alpha version patch
Patch version released according to the test situation
0.9
beta version
Provide user trial and test
0.9.x
β version patch
Patch version released according to user usage
1.0
formal edition
Final completed version
4.2.4, project schedule
time
event
February 16, 2005
Established project leadership group and project work group
On February 18, 2005, the first customer demand A feature meeting (customer office leaders, business personnel)
February 22, 2005
Hold the Second Customer Demand A Topic Conference (customer office business personnel participate)
February 24, 2005
User confirms A product package requirements, release A product package β version needs
February 23, 2005
Held the first customer demand B special meeting (the customer base is leading, business personnel participate)
February 25, 2005
Hold the second customer demand B special meeting (customer base sales business personnel participation)
March 02, 2005
Publish a product package programming program, release Beta version of Internet Government website
March 08, 2005
Users confirm that B product package needs, release B product package β version needs
March 24, 2005
Complete a product package α version of the program, complete the B product package programming program
March 31, 2005
Publish a product package α version of the product.
April 29, 2005
Publish a product package β version program. Publish B product package β version
May 06, 2005
Publish a, B product package β version products
May 09, 2005
Training, customer first trial
May 23, 2005
Project trial operation
August 09, 2005
Post a, B, and C product package official version of the product.
August 22, 2005
Project trial operation acceptance
August 25, 2005
Project user acceptance
September 05, 2005
Project expert group inspection
4.2.5, project resource allocation
4.2.5.1, personnel equipping plan
The main participants of the project is 12 people
Project undertake person in charge: 1 person, that is, project director, responsible for negotiating, coordinated, and information communication with customer direct projects.
Project management person in charge: 1 person, the project manager, has a number of large and medium-sized project management implementation experience. The manager of the Company is personally served. Project Technical Manager: 1 person, has many years of software system development analysis and design experience, independent technical organization, design, management of multiple large and medium-sized software applications, and has a number of mature and stable software application products development successful experience.
The project technical manager is part of the project management person in charge.
System Analysis Designers: 2 people, advanced system analysis designers, have multiple software product development, analysis design experience of software application projects.
Advanced programmers: 2 people, many years of program development experience, extremely proficient in database and related procedures.
Senior programmers are partly determined by system analysts.
Programmer: 3 people, multi-year program development experience.
Software Tester: 2 people, multi-year software system test experience
Documentant: 1 person, professional technical document compiler, have multiple software products and project related technical documentation preparation experience.
Art: 1 person
Technical support staff: 2 people, with multi-year software project technical support experience.
Technical support staff is part of the software tester.
Training teacher: 1 person
