NOTICE These materials are prepared only for the

  • Slides: 10
Download presentation
NOTICE! • These materials are prepared only for the students enrolled in the course

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 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! 6/10/2021 1

Distributed Software Development 6/10/2021 2

Distributed Software Development 6/10/2021 2

Vijaya Krishna Cherukuri NRTRDE Processing System Project Plan (2009 - 2010) 6/10/2021 3

Vijaya Krishna Cherukuri NRTRDE Processing System Project Plan (2009 - 2010) 6/10/2021 3

 • • Requirements are frozen Ideally should be waterfall model Complexities foreseen in

• • 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 6/10/2021 4 Image source: http: //images. google. com/ Development Methodology

Customer Team members Steering group Customer Team members Steering group 6/10/2021 Output Planned week

Customer Team members Steering group Customer Team members Steering group 6/10/2021 Output Planned week Promised week Project plan 39 40 Requirements Definition document Design Description document Use case specification document Test strategy document Acceptance Test Plan document Final Project Report document and packaged product 39 40 40 41 48 49 49 50 52 2 Image source: http: //images. google. com/ To Deliverables 5

Milestones Milestone Description Planned week Actual week M 001 Project Vision presentation 39 39

Milestones Milestone Description Planned week Actual week M 001 Project Vision presentation 39 39 M 002 Project plan preparation and presentation Requirements Definition document 39 40 M 004 Design Description document 40 41 M 005 Prototype and Implementation presentation Test Strategy and Acceptance Test Plan 41 42 48 50 52 2 M 003 M 006 M 007 6/10/2021 Final Project Report document, presentation Image source: http: //images. google. com/ Id 6

Activity W 39 W W 40 41 W 42 W W W 43 44

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

Effect Preventive action Team member leaves Low project Critical Team reorganization. Maintain pleasant working

Effect Preventive action Team member leaves Low project Critical Team reorganization. Maintain pleasant working atmosphere. Our system is not functional before deadline Catastrophic Use incremental model and accomplish primary functionality early. Be prepared to work overtime. Take the help of experts. Risk Possibility Medium We cannot understand requirements Medium Critical Requirements will change Low Serious 6/10/2021 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. 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 8 Image source: http: //images. google. com/ Risks

Risk Possibility Effect Preventive action Technical problems with SVN Low Serious Assign a person

Risk Possibility Effect Preventive action Technical problems with SVN Low Serious Assign a person to take care of SVN. Take regular backups. Also maintain working folders as local copies in your machines. Communication problems Medium Catastrophic Design oversights Medium Critical Technology Low Critical 6/10/2021 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. Spend more time on design itself. Go back to requirements if needed. Technology must fit to our project. We have to play with technology experience of team members and also consider technology maturity. 9 Image source: http: //images. google. com/ Risks (contd. . )

Financial Plan Volume (days) Cost (in $) Project preparation 7 1400 Requirements analysis &

Financial Plan Volume (days) Cost (in $) Project preparation 7 1400 Requirements analysis & definition 8 1600 Design Description Document 8 1600 Use case Document 4 800 Implementation 50 10000 6 1200 Testing 40 8000 Acceptance testing preparation 6 1200 Documentation 10 2000 Final Product , report and presentation 6 1200 Implementation presentation and prototyping Planned effort (mandays) Man-day cost Planned project cost (100%) 145 200$ 29000 6/10/2021 Image source: http: //images. google. com/ Activity 10