The first version of the projectplan

Here comes our first estimation of the projectplan:

Project Plan

Team description

Responsibility Person Description

Main contact Erik c05esm, 070−2923332

Backup contact Eva c06een, 070−6735644

Other contact Peter c05psl, 070−2870297

Other contact Lovisa c04lpn, 070−6035086

Responsible for Documents Lovisa Will make sure documents are written.

Responsible for Coding Peter Will make sure all code gets written.

Responsible for Web page Erik Will make sure the homepage is updated.

Responsible for Oral Report Peter Will make sure the oral presentation is good.

Responsible for GUI Eva Will make sure the GUI is user friendly.

Responsible for Testing Erik Will make sure the system get tested.

Required Resources

1. Access to computers

2. Access to a CVS system

3. Access to the Sun Java Wireless Toolkit CLDC

4. Access to a program used to create an architectural diagram

5. 20 hours per week and person

6. Eventually a cellular phone for testing

Chosen approach

The chosen process is a modified version of the Waterfall model, with a recursive

step between coding and testing, and an ongoing documents phase. It borrows the

risk analysis from the spiral model.

Schedule

1. Week 50

1.1 Become familiar with the software.

1.2 Get hold of an CVS system.

1.3 Templates for reports created.

1.4 Homepage created and updated.

1.5 Get hold of a Gobby system.

1.6 Requirements specification written.

1.7 Risk analysis written.

1.8 First meeting done.

1.9 Individual time sheets written, compiled and sent to TA.

1.10 Requirements specification should have been verified.

2. Week 51

2.1 All code shall be planned.

2.2 The GUI shall be planned.

2.3 Comments to every part of the code shall be written.

2.4 Code should be divided between group members.

2.5 Risk analysis should be updated for current week.

2.6 Homepage should be updated.

2.7 At least one more meeting should have taken place.

3. Week 52

3.1 This week nothing is planned due to holidays.

4. Week 01

4.1 All code should be written.

4.2 All tests should be done.

4.3 System should be validated.

4.4 Homepage should be updated.

5. Week 02

5.1 The Manual should be written.

5.2 Final report should be done and handed in.

5.3 Homepage should be updated.

6. Week 03

6.1 Oral report should be prepared for,

6.2 Oral report should been presented.