110-09-28

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

210-09-28

Distributed Software Development

310-09-28

Software Patterns Project Plan

Shaibal BaruaAntonio Moreno Borras

Joanne Chevalier

410-09-28

Introduction• Why a project plan ?

– A plan for• Describe the policies for Software Patterns project

– Scope• Development model• Deliverables • Communication• Milestones• Activity Plan• Team members roles in the project• Project risks

Development Model• The DSD project is

related to the student project PG POSE in Paderborn

• We will get all specifications and have to follow those specifications

• We will use Iterative development Model

510-09-28

Final ProductFinal Product

PlanningPlanning

DesignDesignEvaluationEvaluation

RequirementsRequirements

DevelopmentDevelopmentTestTest

DeliverablesDeliverable DateProject plan document 2010-10-01

Requirements Definition document 2010-10-01

Design Description document 2010-10-08

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

2011-01-14

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

609/28/10

Communication

• Adobe Connect• Skype• Email • Doodle• Google Docs

710-09-28

Milestones

809/28/10

Presen tatio n D ateProject plan presentation 2010-09-28

Requirements Definition presentation 2010-10-05Design Description presentation 2010-10-05

Alpha prototype 2010-10-26

Beta prototype 2010-11-16

Release candidate 2010-12-14

Final project presentation 2011-01-11

Activity Plan

910-09-28

Team Members RolesNam e University Team Role

A n d re B a c k o fe n U P B P ro je c t s p e c if ic a tio n , Q u a l i ty a s s u ra n c e , In te g ra tio n

A d n a n B is e r U P B P ro je c t s p e c if ic a tio n , Q u a l i ty a s s u ra n c e , In te g ra tio n

D e n n is N o b e l U P B P ro je c t s p e c if ic a tio n , Q u a l i ty a s s u ra n c e , In te g ra tio n

M a rie C h ris tin P la te n iu s U P B P ro je c t s p e c if ic a tio n , Q u a l i ty a s s u ra n c e , In te g ra tio n

J a n S c h m a lo r U P B P ro je c t L e a d e r, P ro je c t s p e c i fic a tio n , Q u a l ity a s s u ra n c e , In te g ra t io n

A n to n io M o re n o B o rra s M D H D e v e lo p e r, B a c k u p a n d M a in te n a n c e

S h a ib a l B a ru a M D H Te a m L e a d e r, D e v e lo p e r

J o a n n e C h e v a lie r M D H D e v e lo p e r, D o c u m e n ta tio n

J a s e n k o R a m lja k F E R R e q u ire m e n ts s p e c if ic a tio n , S V N M a n a g e r

Iv ic a P a đ e n F E R D e v e lo p e r, Te s tin g

M a rk o V i ta s F E R Te a m L e a d e r, D e v e lo p e r

S tip e G rb ić F E R D e v e lo p e r

Project Risks

• Deadline delays• Misunderstandings• Problems of Communication • Bad organizing• Lack of knowledge on tools and technology

1110-09-28

Thank You