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

1
NOTICE!

• 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 2005/2006).
• 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!

2
Progress Project
ProCom_at_MdHProject Plan
3
Index

• Development methodology
• Deliverables
• Milestones
• Activity plan
• Financial plan
• Project risks

4
Development Methodology
Spiral SDLC Model

• Estimates (i.e. schedule, etc.) get more
  realistic as work progresses, because important
  issues are discovered earlier.
• It is more able to cope with the changes that
  software development generally entails.
• Software engineers (who can get restless with
  protracted design processes) can get their hands
  in and start working on a project earlier.

5
Development Methodology
Prototype 1
Prototype 2
Prototype 3
Final Release

• Prototype1Code generation for PROSAVE component
• Prototype 2 Code Generation for PROSYS component
• Prototype 3Code Generation for GLUE Code
• Final release Ready to be delivered to the
  customer

6
Deliverables(1)
To Output Planned week Promised week Late /- Delivered week Remarks
Steering group, Project Team members Project Vision Document W38 W38 0 W38
Project Team members Project Description document WK39 WK39
Steering Group, Customer Project Description document WK40 WK40
Steering group,Cutomer Project Description presentation WK40 WK40
Project Team member Requirements Description document WK39
Steering group,Cutomer Requirements Description document WK40
Project Team members Design Description document WK40
Steering Group Design Description document WK41
Steering Group,Cutomer Requirements and Design Description Presentation WK41
7
Deliverables(2)
Customer Project Status presentation WK44
Steering Group, Project Team Member Design Description documents (revised) WK46
Customer Project Status presentation WK47
Steering Group, Project Team Member Design Description documents (revised) WK 50
Steering group, Project Team members Acceptance Test Plan document WK48
Steering group,Cutomer Acceptance Test Plan document WK49 WK50
Steering group, Project Team members Test Report WK01
Steering Group Test report WK02 WK02
Project Team members Final Project Report document WK01
Customer, Steering group Final Project report document WK01 WK02
Customers, Steering group Final Project Presentation WK02 WK02
Steering group, Project Team members Summary Week Report WK38- 02
Steering group, Project Team members Minutes of Meetings WK38-02
Steering group, Project Team members Technical Documents WK38-02
8
Milestones
Id MilestoneDescription Responsible Finished week Finished week Finished week Finished week Metr. Rem.
Id MilestoneDescription Responsible Plan Forecast Forecast Actual Metr. Rem.
Id MilestoneDescription Responsible Plan Week /- Actual Metr. Rem.
M001 Project Vision presented PG WK38
M002 Project Description Presented PG,BB WK40
M003 Learning PROCOM model PG,MA,IA,PP,PZ WK39
M003 Requirements analysis and definition PG,BB,PZ WK40
M004 Design Mapping Identification BB,PP,IA WK41
M005 Project design version 1 delivered IF, LL, AP WK41
M006 First Prototype demonstrated (Code generation implemented for PROSAVE component) PG,PP,PZ,MA WK44
M007 Design mapping for PROSYS component. BB,IA,MA,PG WK45
M008 Project Design Document version 2 delivered BB,IA,PP,PG WK46
M009 Second Prototype demonstrated (Code generation implemented for PROSYS component ) PG,PP,PZ,MA WK47
M010 Identify Possibility of GLUE CODE Generation BB,IA,PG,PP WK48
M011 Acceptance Test Plan Presented PG,MA,IA WK49
M012 Final Design Document Delivered BB,IA,PP,PG WK50
M013 Third Prototype demonstrated (Implementation of code generation for GLUE CODE) PG,PP,PZ,MA WK51
M009 Completion of Testing PZ,IA,PG WK01
M010 User Documentation MA,PZ,IA WK01
M010 Final product demonstrated and delivered PG,PP,MA,IA,PZ WK02
M011 Final Project Report delivered PG WK02
9
Activity plan
Activity W38 W39 W40 W41 W42 W43 W44 W45 W46 W47 W48 W49 W50 W51 W52 W1 W2
Project Preparations                                  
Requirements Analysis Definition                                  
Tools Design                                  
Tool Implementation                                  
Integration of modules in tools                                  
Testing                                  
Troubleshooting                                  
Documentation                                  
Final Release                                  
10
Financial plan
Activity Volume (days) Cost Remarks
Project management and Preparation 14 22400 8 hour per day per person
Team Documentation (know how) 20 16000
Project Documentation and Presentation 6 9600
Requirement Analysis and Gathering 10 16000
Tool Design 28 33600
Implementation 32 62400
Testing 18 28800
Planned effort (man-days) Man-day cost Planned project cost (100)
128 1600 SEK 179200 SEK
11
Project risks
Possibility Risk Preventive action
Competency of the Team. Medium Reading and understanding ProCom model. Proof of concepts for the targeted implementation.
Is the size of team adequate Medium Uniform distribution of work in team
Hardware Failure Low Backup Peripheral support
Unavailability of the members of development team Low Rescheduling of working days and increasing working hours per day.
Change in requirements Medium Continuous update must be carried out to satisfy the requirements
Development of wrong functionalities Medium Continuous testing and analysis of development artifacts.
Customer communication problems Medium Establish meeting with the customer to understand the requirement. If meeting is not possible then email is use as an option for finalizing requirements.
Problems in Integration of the Plug-in Medium Rigorous testing should be done just after the development of plug-in.
Wrong design of the mapping High Establish various testing scenarios to test the developed prototype based on the design.
12
Questions?