1. 12015-09-13 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!

2. 22015-09-13 Distributed Software Development

3. 32015-09-13 NRTRDE Processing System Project Plan (2009- 2010) Vijaya Krishna Cherukuri

4. 42015-09-13 Development Methodology Requirements are frozen Ideally should be waterfall model Complexities foreseen in database design Sashimi model - Waterfall model with feedback Courtesy : http://www.acidaes.com/SWM.htm Image source: http://images.google.com/ http://images.google.com/

5. Deliverables ToOutputPlanned weekPromised week Customer Team members Steering group Project plan 3940 Customer Team members Steering group Requirements Definition document 3940 Customer Team members Steering group Design Description document 4041 Customer Team members Steering group Use case specification document 4041 Customer Team members Steering group Test strategy document 4849 Customer Team members Steering group Acceptance Test Plan document 4950 Customer Team members Steering group Final Project Report document and packaged product 522 52015-09-13 Image source: http://images.google.com/ http://images.google.com/

6. Milestones 62015-09-13 Id Milestone Description Planned weekActual week M001 Project Vision presentation 39 M002 Project plan preparation and presentation 3940 M003 Requirements Definition document 3940 M004 Design Description document 4041 M005 Prototype and Implementation presentation 4142 M006 Test Strategy and Acceptance Test Plan 4850 M007 Final Project Report document, presentation 522 Image source: http://images.google.com/ http://images.google.com/

7. Activity Plan 72015-09-13 Activity W 39 W 40 W 41 W 42 W 43 W 44 W 45 W 46 W 47 W 48 W 49 W 50 W 51 W 52 W1W1 Project preparations Requirements analysis & definition Design Description Document Use case Document Implementation Implementation presentation and prototyping Testing Acceptance testing preparation Documentation Final Product, report and presentation Image source: http://images.google.com/ http://images.google.com/

8. Risks 82015-09-13 Risk Possibility EffectPreventive action Team member leaves project LowCritical Team reorganization. Maintain pleasant working atmosphere. Our system is not functional before deadline Medium Catastrophic Use incremental model and accomplish primary functionality early. Be prepared to work overtime. Take the help of experts. We cannot understand requirements MediumCritical Develop a good communication with the customer. Be sure to understand his answers and make sure that he understood our questions. Give the customer our user requirements draft to check it once again. If possible prepare a flow chart explaining all the functionalities. Requirements will change LowSerious Be in touch with the customer. Try to be flexible, make system modules to be independent to each other. Also select the design method that accommodate requirements change easily Image source: http://images.google.com/ http://images.google.com/

9. Risks (contd..) 92015-09-13 Risk Possibility EffectPreventive action Technical problems with SVN LowSerious Assign a person to take care of SVN. Take regular backups. Also maintain working folders as local copies in your machines. Communication problems MediumCatastrophic Assign a person to take care of inter team communication. Use several communication tools and have regular and weekly meetings. Populate the contact details in Google groups. Design oversightsMediumCritical Spend more time on design itself. Go back to requirements if needed. TechnologyLowCriticalTechnology must fit to our project. We have to play with technology experience of team members and also consider technology maturity. Image source: http://images.google.com/ http://images.google.com/

10. Financial Plan 102015-09-13 ActivityVolume (days)Cost (in $) Project preparation 71400 Requirements analysis & definition 81600 Design Description Document 81600 Use case Document 4800 Implementation 5010000 Implementation presentation and prototyping 61200 Testing 408000 Acceptance testing preparation 61200 Documentation 102000 Final Product, report and presentation 61200 Planned effort (man- days) Man-day cost Planned project cost (100%) 145200$29000 Image source: http://images.google.com/ http://images.google.com/