123-04-20

• These materials are prepared only for the students enrolled in

the course Distributed Software Development (DSD) at the

Department of Computer Science and Engineering,

University of Mälardalen, Västerås, Sweden and at the Faculty

of Electrical Engineering and Computing, University of Zagreb,

Croatia (year 2010/2011).

• For all other purposes, authors’ written permission is needed!

• The purpose of these materials is to help students in better

understanding of lectures in DSD and not their replacement!

NOTICE!

223-04-20

Distributed Software Development

323-04-20

Public Transportation System”PTS”

Omar T. Jaradat

Project Overview

• Development methodology

• Deliverables 

• Communication

• Milestones 

• Activity plan

• Financial plan

• Project risks

423-04-20

PTS development methodology

• PTS will use Agile ”UP” methodology.• Incremental release-based development.

523-04-20

Why using AUP?

• AUP supports Incremental release-based development.

• The AUP applies agile techniques including:

1. Test driven development.

2. Agile Modeling

• Tool independence You can use any toolset that

you want with the Agile UP.

623-04-20

Deliverables

• PTS development process depends on three iterative releases

• In addition to the traditional planned deliverables PTS has three more.

• Releases V1.0, V2.0 and V3.0

723-04-20

Deliverables (Cont.)

823-04-20

To Output Planned week

Promised week

Late +/-

Delivered week Rem

Steering Group

&Customer

Project plan document 40 40 0 40 On Time

Steering Group

&Customer

Requirements Definition document

40 40 0 40 On Time

Steering Group

&Customer

Design Descriptiondocument

41 41 N/A N/A N/A

Customer PTS First Release v1.0 44 44 N/A N/A N/A

Customer PTS First Release v2.0 46 46 N/A N/A N/A

Customer PTS First Release v3.0 48 48 N/A N/A N/A

Deliverables (Cont.)

923-04-20

To Output Planned week

Promised week Late +/- Delivered

week Rem

Steering Group

&Customer

Acceptance test plan50 50 N/A N/A N/A

Steering Group

&Customer

Test report2 2 N/A N/A N/A

Steering Group

&Customer

Final Project Report, final versions of existing 

documents, other project-related documentation(as negotiated with the

customer)

2 2 N/A N/A N/A

Steering Group

&Customer

Final product (installation, source code, etc.)

2 2 N/A N/A N/A

Customer

(*)

Final Report 10 10 N/A N/A N/A

Communication strategy

1023-04-20

Milestones

• PTS has five main milestones:

1.Requirements analysis charts and diagrams - week 43

2.PTS First Release v1.0 – week 44

3.PTS First Release v2.0 – week 46

1123-04-20

Milestones (Cont.)

4. Evaluation Report “after creating prototype model” – week 46

5. PTS First Release v3.0 – week 48

6. System architecture and design structure – week 50

1223-04-20

Activity plan

1323-04-20

Financial plan

1423-04-20

Activity Volume (days) Cost Rem.

Project preparations~10 Priceless

Requirements analysis & definition ~10 Priceless

Requirements Prototype ~8 Priceless

Design System Architecture ~12 Priceless

System Implementation ~43 Priceless

Testing ~25 Priceless

Documentation ~15 Priceless

System Delivery ~5 Priceless

Project risks

1523-04-20

Possibility scenario Risk Preventive action

HighUmple language still new

and the Occasional bugs are very possible.

Stuck with some unsolvable bugs which

will late the whole project workflow.

Manual editing the generated code from Umple but after

having permission from project sponsor.

High

Umple language still new and the missing or

incomplete features is something expected.

Changing the model design which can affect on the other parts and this requires redesign

process.

Design separated modules and units based in Object

oriented modeling methodologies to avoid any

unneeded affection.

Low

Bad Timeline estimation due to some unexpected

technical or normal issuesExceeding the

estimated timeline.

Timeline should be reviewed weekly or at least every two

weeks by the Project Manager and the Steering

group.

Project risks (Cont.)

1623-04-20

Possibility scenario Risk Preventive action

Medium

The project team members

feel that they can not

communicate efficiently.

Team is scattered

Expand Communications

Plan

Low SVN troubles

Losing the contents or

bad subversion actions.

Always have a backups and

save all project relevant

Low Sickness absence

One or more members

get sick and quit the

project for a while

Increase the working hours

for the rest team members

to make up

Questions ...

1723-04-20