1 / 17

Distributed Software Development - Map Schematization Application

This project overview presentation discusses the assignment of creating an application for schematizing a map, including features, work distribution, team communication, requirements, design, and acknowledgements.

vangi
Download Presentation

Distributed Software Development - Map Schematization Application

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. Adis Mustedanagić Zhixiang Gao Final presentation

  4. Project overview • Assignment • Create an application for schematizing a map • A schematic map cares only for relative, not absolute relations between points of interest Schematize

  5. Gantt chart

  6. Work hours per team member Total: 747.95 hours

  7. Work hours per week Beta Alpha RC Final

  8. Work distribution GUI Dominik Martin Adis FER Ramesh Pavel Zhixiang MDH Drawing tools Algorithm Testing

  9. Team communication review • Weekly official meetings • Frequent informal communication • 95% of the total communication during the project • Mainly used for communication with supervisors, teachers and our SCORE customer

  10. Requirements • We were not given a set of fixed requirements, but a set of guidelines and possible features • Interoperability with other software • Google maps • Usability requirements etc. • One requirement was however set in stone before the actual work began: “A basic and robust application is preferred over a feature-rich and buggy one.”

  11. Application features • Draw a new map, or trace over an imported image (local or url) • Save project for later work • Toolbar with drawing (route, station) and common tools (edit, undo) • Algorithm control tools • Save output as an image for work in other software

  12. Design and architecture • Java application based on Model-View-Controller design pattern

  13. SCORE • Latest customer feedback • Basic requirements have been met • The application needs a bit polishing • The other stuff • A whole lot of additional documentation during finals and holidays • A bit more work on the application once the course ends

  14. Demo

  15. Acknowledgements Our supervisor, Ana Petričić For guidance during the project development Our customer, Michal Young For initial project assignment, and feedback during development Dr. Martin Nöllenburg For his thesis, and showing us the JUNG2 lib which were used as a starting ground

  16. Final slide • And of course, many thanks to the teachers and everyone else on the course for their help during project development • Questions

  17. Plan C • We are confident that our application will work, therefore this section intentionally left blank

More Related