1.Description:
l Setting:
We are a software company who designs software for customers with particular requirements. Now ,we receive a task that we will build a software for traffic control in the city of Harbin.
l Goal:
We will build a software in reasonable time and with limited resources with which the traffic managers can coordinate and control the time planning of the traffic signal lights and the monitoring devices in each road, adjust the transportation flow and the moving cars in time ,monitor the behaviors which break the rules and the regulation ,make the sum of the parking times and the parking time of the moving vehicles smallest,reduce the traffic accident efficiently ,ensure the benefits of the road transportation in the city of Harbin .
l Outcome:
1. We will build the software successfully which will meets the requirements of the customers and it will run the function of traffic control perfectly .
2. The software will have good user experience and UI design is beautiful.
3. The software will run stably and strongly and it will not break down easily.
2.Assumption:
l Preparatory phase assumptions:
1. Project staff resources will be available when and as they are needed.
2. Traffic warden resources will be available to train project staff with Traffic management knowledge.
3. Required hardware resources will be available when and as they are needed.
4. Whole traffic information of the city of Harbin will be available.
5. Plenty of money and time.
l Development phase assumptions:
1. Understanding of the requirements is quite correct.
2. Newly-presented problems on the roads will be quickly integrated into the developing system.
3. Systems components will be integrated with minimum rework.
l Testing phase assumptions:
1. All of the situations and test cases will be well tested to guarantee the minimum error radio.
2. Detected errors will be resolved in a timely manner.
3. Ample historical date will be available to be used to test the security level of the system.
l Formal operation phase assumptions:
1. Error-free operational cycle will be long enough to control the traffic effectively.
2. Experts will be available when a fatal error emerged.
3.Roles and their interests:
1. Department of Transportation:
Customer,put forward demand , pay for software, management Harbin‘s whole traffic control system.
Want to spend the least money in the shortest period of time to get the satisfactory software.
2. Representative of Transportation:
One of human resources provided by customers. Employed by the Department of Transportation. Responsible for project communication, put forward demand, help consummate the demand and software. Irregular monitoring the progress of the project. Acceptance of the project.
Want to obtain better software, and lower costs.
3. Software Company Project Leader:
Senior management, software company directors Employment, is responsible for communicating with customers to establish needs, revise demand, coordination of resources, and demand to analysts.
Hope as soon as possible to complete the software, ensure the security of data and access.
4. Project needs analysts:
Employed by Software Company, responsible for analyzing the needs of established software development tasks, feedback needs feasibility, difficult and time-consuming to the project leader. Give software development tasks to the architect.
Fully meet customer requirements as simple as possible.
5. Software architect:
Employed by Software Company. Responsible for the software task decomposition, established a software development framework, decompose the task into modules. Give framework to the project manager.
Trying to define a clear standard modules and the structure of the software have a certain degree of portability and scalability.
6. Project Manager:
Middle managers, hired by the software company. Responsible for the management of software development. Distribution software development tasks, coordination developers.
Management team, coordination of resources, time supervision software development process.
Allow developers to work more efficiently, the rational allocation of tasks.
7. Developers:
Hired by Software Company, is responsible for implementing the assigned modules, code review and unit testing.
Trying to achieve with a minimum of code modules, reducing the number of bug.
8. Testers:
Employment by the software company is responsible for system testing.
Hope as much as possible to check out all the bugs.
9. Signal control administrator:
Software users, the people who actually use the software, hired by the Department of Transportation.
Wish to use the software easily . Want to do things by operating the software instead of their own to do a lot more.
4.WBS of the project:
![](https://img-my.csdn.net/uploads/201210/12/1350050602_4007.jpg)
PS:If you can't identify the picture above clearly ,please enlarge it.
5.Effort estimation for the work packages:
Task Number | Work Packages | Effort Estimation | Dependencies |
1.1.1 | Determining the development cycle | 2 | |
1.1.2 | Determining the capital investment | 2 | |
1.1.3 | Determining the development scale | 1 | |
1.2.1 | Determining the related responsibilities people | 3 | 1.1.1,1.1.2,1.1.3 |
1.2.2 | Traffic control knowledge training | 3 | 1.1.1,1.1.2,1.1.3 |
1.2.3 | Traffic and road information research in the city of Harbin | 7 | 1.1.1,1.1.2,1.1.3 |
2.1.1 | Determining the requirements of the functions of the traffic control software | 15 | 1.2.1,1.2.2,1.2.3 |
2.1.2 | Determining the safety and the stability requirements of the software | 2 | 1.2.1,1.2.2,1.2.3 |
2.2 | Demands archive management | 4 | 2.1.1,2.1.2 |
3.1.1 | Determining the code style | 1 | 2.2 |
3.1.2 | Determining the comments style | 1 | 2.2 |
3.1.3 | Determining the documents style | 1 | 2.2 |
3.2.1 | Features modular design | 20 | 3.1.1,3.1.2,3.1.3,3.3 |
3.2.2 | Database design | 10 | 3.1.1,3.1.2,3.1.3,3.3 |
3.2.3 | UI design | 10 | 3.3 |
3.3 | Determining the development model | 1 | 2.2 |
4.1 | Coding | 25 | 3.2.1,3.2.2 |
4.2 | Code review | 10 | 4.1 |
5.1 | Unit testing | 5 | 4.2 |
5.2.1 | Test whether the traffic functions are complete | 3 | 5.1 |
5.2.2 | Testing whether the robustness and the security meets the requirements of the software | 3 | 5.1 |
5.3.1 | Test whether the user manual is complete | 1 | 5.1,3.2.3 |
5.3.2 | Test whether the development documents are complete | 1 | 5.1,3.2.3 |
6.1 | User manual delivery | 1 | 5.2.1.5.2.2,5.3.1,5.3.2 |
6.2 | Put software on-line | 1 | 6.1,6.3 |
6.3 | Training the operators of the traffic Departments in Harbin | 2 | 5.2.1.5.2.2,5.3.1,5.3.2 |
6.CPA of the project:
We can draw the picture of the MPM below:
PS:If you can't identify the picture above clearly ,please enlarge it.
From the MPM,we can compute the critical paths:
Start ->1.1.1(Determining the development cycle) or 1.1.3(Determining the development scale)
->1.2.3(Traffic and road information research in the city of Harbin)
->2.1.1(Determining the requirements of the functions of the traffic control software)
->2.2(Demands archive management)
->3.1.1(Determining the code style) or 3.1.2(Determining the comments style) or 3.1.3(Determining the documents style) or 3.3(Determining the development model)
->3.2.1(Features modular design)
->4.1(Coding)
->4.2(Code review)
->5.1(Unit testing)
->5.2.1(Test whether the traffic functions are complete) or 5.2.2(Testing whether the robustness and the security meets the requirements of the software)
->6.3(Training the operators of the traffic Departments in Harbin)
->6.2(Put software on-line)
->End
7.Risk estimation:
1. Requirement Risks
Risks | Risk Description | Category |
Data supply from Traffic Department is not in time or precise. | Data what is necessary in project is offered with some mistakes; The data about roads that is under construction is not offered in time. | 2 |
Members of the project are lack of actual cognition about the data. | Members of the project team are not acquainted enough with the meaning of data; Developer deal with data in quite different ways. | 1 |
2. Relative Risks
Risks | Risk Description | Category |
Division of work is not properly. | The department in authority separates the whole project improperly. | 3 |
Lack of technical support from Traffic department. | The traffic department sends no expert in traffic control to help with project. | 3 |
3. Management Risks
Risks | Risk Description | Category |
Making incomplete plans. | Plans in project can’t cover the entire period of the project. | 2 |
The department which is on authority but not the decision-maker commands team. | The non-technical advice from authority blocks the progress of the project. | 1 |
Developer makes unrealistic promise. | Developer gets wrong estimation of the amount of code or they specify a inappropriate deadline. | 3 |
4. Technical Risks
Risks | Risk Description | Category |
Members of project are lack of training about whole project. | Members of project do not get enough training about whole project so that technical staff communicates with non-technical one difficultly. | 2 |
Members of project have little experience on method of Traffic Control. | Developer deal with actual problem in improper way when building the software. | 3 |
Reuse software with potential bugs. | The bug from reused software is difficult to be resolved. | 1 |