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

Project Plan

Zhixiang Gao and Pavel Chen

423-04-20

Project Overview

• Software to assist in schematic map generation

• Standalone application

• Possible extension in future

Methodology

• Feature Driven Development (FDD)– Agile methodology– Introduced in 90’s– Consists of 5 activities– Driven from a “features” perspective

523-04-20

Methodology

623-04-20

- Add label- Add station- Allow import

Add label – Nov 7, 2010 - JUnit- SVN update- SVN commit

Why FDD?

• Requirements are uncertain

• Timeframe is short

• Need in continuous integration

• Need in robust software

• OOP with Java

723-04-20

FDD - Roles

823-04-20

Task\Role (Person)

Project and Development Manager (ZG)

Chief Architect

(AM)

Chief Programmers

(MV, PC)

Class Owners (DP, RN)

Domain Experts (MY, AP)

Overall model   X X   X

Feature list   X X   X

Plan by feature X   X X  

Design by feature X X X X  

Build by feature X X X X  

Communication

• Synchronous communication – Weekly all hands meeting (video/voice

meeting via Skype)– Face to face meeting on each side– IM chat 

• Asynchronous communication– Google Group discussions– Email communication

923-04-20

Schedule

1023-04-20

Team Organization

Requirements Definition

Delivery on 10.1

Feature ListPlan Revision

ImplementationIntegrationAcceptance

Test PlanDelivery on

12.10

Test ReportDelivery on

1.8

Final Project Report

Delivery on 1.14

Documentation

Project Vision

Project PlanDelivery on 10.1

Design DescriptionDelivery on 10.5 Overall Model

Design

User Manual Installation GuideDelivery on 1.14

Alpha10.27 Beta

11.17 RC12.15

Final1.12

Schedule

Project Risks

Beyond the deadline

Miscommunication

Lack of human resources Version control problem

Lack of technical competence

Loss of team member

Members should help each other. Study and study!

Members follow up the schedule strictly.

Communicate when a problem happens. Document important

information.

Members follow the SVN policy.

Backup data periodically.

Plan well and everyone completes/submits

work on time. Assign the tasks

according to team member’s skills.

Every team member should be aware

of other members’ responsibility.

Project RisksPossibility Risk Preventive action

High Beyond the deadline Members follow up the schedule strictly.

High Miscommunication Communicate when a problem happens. Document important information.

Medium Lack of technical competence Members should help each other. Play one’s strength and improve weaknesses.

Medium Version control problem Members follow the SVN policy. Backup data periodically.

Low Lack of human resources Plan well and everyone completes/submits work on time. Assign the tasks according to team member’s skills.

Low Loss of team member Every team member should be aware of other members’ responsibility.

1323-04-20

Financial PlanActivity Volume (days) Cost

Project preparation 3€ 600

Requirement analysis 15€ 3000

Design specification 8€ 1600

Architecture and interface design 8€ 1600

Implementation 25€ 5000

System integration 5€ 1000

Test 20€ 4000

Information gathering 10€ 2000

Documentation 30€ 6000

Presentation preparation 5€ 1000

Meeting 10€ 2000

Study 10€ 2000

Team management 5€ 1000

Total man-day: 154 (€ 200/day) Total cost: € 30800

WE ARE

COSTLESS AND

PRICELESS

Thanks for the attention

Questions?

1523-04-20