1 / 15

NOTICE!

NOTICE!.

carrie
Télécharger la présentation

NOTICE!

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Distributed Software Development

  3. Zhixiang Gao and Pavel Chen Project Plan

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

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

  6. Methodology Design by Feature Design by Feature Build by Feature Build by Feature Add label – Nov 7, 2010 • JUnit • SVN update • SVN commit • Add label • Add station • Allow import

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

  8. FDD - Roles

  9. 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 • Email communication

  10. Team Organization Schedule Project Vision Design Description Delivery on 10.5 Project Plan Delivery on 10.1 Implementation Feature List Alpha 10.27 Overall Model Design Integration Acceptance Test Plan Delivery on 12.10 Plan Revision Test Report Delivery on 1.8 Beta 11.17 Final 1.12 Final Project Report Delivery on 1.14 RC 12.15 Requirements Definition Delivery on 10.1 Documentation User Manual Installation Guide Delivery on 1.14

  11. Schedule

  12. Project Risks Miscommunication Beyond the deadline Members follow up the schedule strictly. Communicate when a problem happens. Document important information. Lack of technical competence Members should help each other. Study and study! Loss of team member Version control problem Every team member should be aware of other members’ responsibility. 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. Lack of human resources

  13. Project Risks

  14. Financial Plan WE ARECOSTLESSANDPRICELESS Total man-day: 154 (€ 200/day) Total cost: €30800

  15. Thanks for the attentionQuestions?

More Related