• 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!

(Mass Observation)

Distributed Software Development

Contents

• Overview• Development Methodology• Deliverables• Communication• Milestones• Activity Plan• Financial Plan• Project Risks

Project Overview

OE: Observation Event

ObserversObservation

event

Consumers

How is theclimate in Vasteras today

Initiator

Development Methodology

• Iterative development• Application to be divided

into modules which would be simultaneously developed. Hence it is best to go with iterative model as it would reduce integration problems.

• Parallel approach for web page development.

DeliverablesDeliverables Date

Project plan document 2010-10-01

Requirements Definition document 2010-10-01

Design Description document 2010-10-08

Weekly Reports (Team Member to PL) Every Friday

Summary Week Report (PL to Supervisor) Every Monday

Minutes of Meeting During project

Technical documents, Project policies etc. During project

Revisions of existing documents On major changes

Acceptance test plan 2010-12-10

Test report 2011-01-10

Final Project Report, final versions of existing documents, other project-related documentation(as negotiated with the customer)

2011-01-14

Final product (installation, source code, etc.) 2011-01-14

Communication

• Voice/Video Conference

• Weekly Meetings

• Emails

• Google Group

• DSD Project website

Milestones

Milestones Planned Date (Week)

Project Vision 2010-09-21 (Week 38)

Project Plan 2010-09-28 (Week 39)

Requirements Definition 2010-10-05 (Week 40)

Alpha Prototype 2010-10-26 (Week 43)

Beta Prototype 2010-11-16 (Week 46)

Release Candidate 2010-12-14 (Week 50)

Final Project Presentation 2011-01-11 (Week 02)

Activity Plan

Financial Plan

Planned effort (man-days)

Man-day costPlanned project

cost (100%)

170 $ 150 $ 25500

Activity Volume (days) Cost ($)

  Project Preparation  5 $ 750

  Requirement Analysis and Definition  10 $ 1500

  Project Design  10 $ 1500

  Implementation  40 $ 6000

  Testing  35 $ 5250

Documentation 60 $ 9000

Final Delivery and Presentation 10 $ 1500

Project RisksPossibility Risk Preventive Action

Architecture Drift Medium Brainstorming the pros and cons of a design

and technology selected before implementing.

Lack of Required Skills Medium Distribution of work based on skills of a

team member. Continuous research.

Unavailability of a member Medium Thorough and good documentation.

Meetings to ensure that each member is having an idea of what other is

doing.

Crashes and Outages Medium Regular Backups.