123-04-21
• 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 2009/2010).
• 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-21
Distributed Software Development
323-04-21
Project Plan of transfoREMES
by transfoREMES team
Supervisor: Aneta Vulgarakis
423-04-21
Table Of Contents
• Development methodology
• Milestones
• Deliverables
• Activity plan
• Financial plan
• Project risks
523-04-21
Development methodology
Reference : Rick D. Craig : Systematic Software Testing, Artech House , 2002
• Using waterfall model– simple way of planning & control
• necessary, because distributed project• 100% validated
– static requirements – save much time
• easy concept
623-04-21
Deliverables & Milestones
14.09.2009 13.01.2010
01.10.2009 01.11.2009 01.12.2009 01.01.2010
03.10.2009Requirements
(all Team members)
29.09.2009Project plan
(Project leader)
09.10.2009Project design
(all team members)
16.11.2009Translation rules
(Implementation group 1)
30.11.2009Implementation
(Implementation group 2)
07.12.2009GUI
(Implementation group 3)
11.12.2009Testing & debugging
(Test team)
13.01.2010Final presentation
(Project leader)
723-04-21
Activity plan
823-04-21
Financial plan – part 1
923-04-21
Financial plan – part 2C os t per c ateg ory
0
20000
40000
60000
80000
100000
120000
Ko
sten
in
SE
K
R eihe1
R eihe1 18900 25200 84000 27300 113400
R equirement analys is and
s pec ific ation and
S ys tem des ign and s pec ific ation
ImplementationTes ting and debugging
Mis c ellaneous *
* Miscellaneous costs consist of project preparation, documentation, final presentation and conferences
1023-04-21
Project risks
• Missing of deadlines – ca. 15%– Planning well & control with week reports
• Team member is leaving – ca. 8% – Good documentation, sharing information
• Miscommunication – ca. 6%– All communication is written into MoM and posted in Google
Group• SVN trouble & losing local data
– Ca. 5%– Regular backup to safe location & SVN
1123-04-21
Any Questions?
Many thanks for your attention
Top Related