Software Project Management plan

April 28, 2015 recorder: Ning

This group mainly discusses the software project management plan, and obtains the following molding documents.

Software Project management Program: Chocolate lovers Anonymous

The program for developing a software product that is anonymously organized by chocolate enthusiasts is prepared by a group of five people, five of whom are: Ning (team leader), Renee, Li Ning, June, Chaoxiao.

1 Introduction

1.1 Project Overview

1.1.1  intentions, categories and objectives. The goal of this project is to develop a software product that can help chocolate lovers anonymously organize the processing of data. This product allows customers to add and remove changes to member information, provider information, and service information. The product will perform the required calculations in these areas and generate the necessary reports and checklists for all forms.

1.1.2  assumptions and limitations. The following restrictions are included:

The final deadline must be met (i.e., the course setting check).

The product must be reliable.

The structure must be open in order to add additional functionality.

The product must be user-friendly.

1.1.3  projects can be delivered to use. the entire product contains a user manual that will be delivered before the course is checked.

1.1.4  Schedule and Budget overview. the cycle and staffing requirements for each workflow are as follows:

Demand flow (one months, five team members)

Analysis Flow (one months, five team members)

Design flow (one months, five team members)

Implement flow and test flow (total two months, five team members)

The total development time period is five months.

1.2 the evolution of the project management plan. all changes in the project management plan must be approved by the teacher before the experiment. All modifications must be documented to keep the project management plan correct and updated.

2  references. All products will be in accordance with the book on the Chocolate Anonymous project requirements.

3 definitions and terminology. chocan--Chocolate Lovers Anonymous, Chocan is our customer.

4  Project organization.

4.1  external interface. the project was completed by members of the group. Teachers will be regularly reported to report progress and discuss possible changes and adjustments.

4.2  internal structure. The development team includes Ning (group leader), Renee, Li Ning, June, Chaoxiao.

4.3 rules and responsibilities. because the group is a democratic group, all the relevant details will be discussed and agreed upon and implemented in the relevant context.

5 Management Process Planning

5.1 Start Plan

5.1.1  estimate plan. the entire development time is estimated to be five months. These figures are determined through a whole group of discussions and are determined by the progress of the project.

5.1.2  personnel planning. The team's five members will be progressing throughout the project cycle.

5.1.3  Resource Acquisition plan. all necessary hardware, software, and Umlet tools are available for this project. The product will eventually be delivered to the teacher and can be run on the laptop.

5.1.4  Project Personnel training program. No additional staff training is required for this project.

5.2 work plan.

5.2.1~2 work activities and timesheet assignments.

1th Month (completed) communicate with the teacher to determine the needs.

The 2nd month (completed) generates a software project management plan and reviews the software project management plan.

3rd month, build design products, review design products.

4th, 5 months, implement and review each class, unit test, and document. Integrate each class, perform integration testing, product testing, and review documentation.

5.2.3  resource allocation. Five group members work alone on the products assigned to them. Team members meet once a week to discuss issues and progress. Report to the teacher once a month.

5.2.4  budget allocations. the project does not cover budgetary issues.

5.3  control Plan. any major changes that affect milestones or budgets must be approved by the teacher and documented. Let everyone test the results of other people's work and ensure the fairness of the test.

Each meeting, the team members to return their current work progress and problems. Let the teacher decide whether the work is done according to the specification document and project management plan. The members of the team have to speak up immediately when they encounter any problems.

5.4  Risk management Plan . The risk factors and tracking mechanisms are described below:

This new product is not available for comparison with existing products. Therefore, the product cannot run in parallel with the software that already exists. Therefore, the product should be extensively tested.

Assuming that the client is unfamiliar with the computer, special attention needs to be paid to communicating with the teacher in the analysis flow. The product should be as user-friendly as possible.

There can always be a major design error, so extensive testing should be done in the design flow. Also, each team member tests its own code product and then tests the code of the other team members.

The product must meet specific storage requirements and response times. Because the product size is not very large, so this is not the main problem.

5.5  Project Stop plan . Not applicable here.

6 Technical process planning.

6.1  process Model. use a unified process.

6.2  methodologies, tools and techniques . The workflow will follow the unified process. The product will be used C++,java, database.

6.3  Infrastructure Planning . The product will be developed using several software that runs on a PC under Windows.

6.4  Product Acceptance Plan . The product acceptance by the teacher is carried out according to the procedure of the unification process.

7 Support process Planning.

7.1 Configure the management plan. for all products, CVS will be used throughout the entire process.

7.2 test Plan. the test flow that executes the unified process.

7.3 document Planning. Generate documents according to the rules of the unified process.

7.4~5 Quality assurance Plan and inspection and audit plan. team members will test the code with each other. The last five people conducted the extended product test together.

7.6 Problem resolution plan. Any questions that the team members face will be discussed and asked by the teacher.

7.7  Sub-contractor management plan . Not applicable here.

7.8 Process Improvement Plan. all activities will be carried out in accordance with the requirements of the textbook.

8  additional plans. No.

Software Project Management plan