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!

Distributed Software Development

Project Plan Zhixiang Gao and Pavel Chen

Project Overview Software to assist in schematic map generation Standalone application Possible extension in future

Methodology Feature Driven Development (FDD) –Agile methodology –Introduced in 90’s –Consists of 5 activities –Driven from a “features” perspective

Design by Feature Build by Feature Methodology Design by Feature Build by Feature Develop an Overall Model Build Feature List Plan by Feature Design by Feature Build by Feature Add label -Add station -Allow import Add label – Nov 7, JUnit -SVN update -SVN commit

Why FDD? Requirements are uncertain Timeframe is short Need in continuous integration Need in robust software OOP with Java

FDD - Roles Task\Role (Person) Project and Development Manager (ZG) Chief Architect (AM) Chief Programmers (MV, PC) Class Owners (DP, RN) Domain Experts (MY, AP) Overall model XX X Feature list XX X Plan by featureX XX Design by featureXXXX Build by featureXXXX

Communication Synchronous communication –Weekly all hands meeting (video/voice meeting via Skype) –Face to face meeting on each side –IM chat Asynchronous communication –Google Group discussions – communication

Schedule Team Organization Requirements Definition Delivery on 10.1 Feature List Plan Revision Implementation IntegrationAcceptance Test Plan Delivery on Test Report Delivery on 1.8 Final Project Report Delivery on 1.14 Documentation Project Vision Project Plan Delivery on 10.1 Design Description Delivery on 10.5 Overall Model Design User Manual Installation Guide Delivery on 1.14 Alpha Beta RC Final 1.12

Schedule

Project Risks Beyond the deadline Miscommunication Lack of human resources Version control problem Lack of technical competence Loss of team member Members should help each other. Study and study! Members follow up the schedule strictly. Communicate when a problem happens. Document important information. Members follow the SVN policy. Backup data periodically. Plan well and everyone completes/submits work on time. Assign the tasks according to team member’s skills. Every team member should be aware of other members’ responsibility.

Project Risks PossibilityRiskPreventive action HighBeyond the deadlineMembers follow up the schedule strictly. HighMiscommunicationCommunicate when a problem happens. Document important information. MediumLack of technical competenceMembers should help each other. Play one’s strength and improve weaknesses. MediumVersion control problemMembers follow the SVN policy. Backup data periodically. LowLack of human resourcesPlan well and everyone completes/submits work on time. Assign the tasks according to team member’s skills. LowLoss of team memberEvery team member should be aware of other members’ responsibility

Financial Plan ActivityVolume (days)Cost Project preparation 3 € 600 Requirement analysis 15 € 3000 Design specification 8 € 1600 Architecture and interface design 8 € 1600 Implementation 25 € 5000 System integration 5 € 1000 Test 20 € 4000 Information gathering 10 € 2000 Documentation 30 € 6000 Presentation preparation 5 € 1000 Meeting 10 € 2000 Study 10 € 2000 Team management 5 € 1000 Total man-day: 154 (€ 200/day) Total cost: € WE ARE COSTLESS AND PRICELESS

Thanks for the attention Questions?