1 / 16

NOTICE!

NOTICE!.

jmabie
Download Presentation

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. EzFare-Transport4You2 An intelligent public transportation manager 2010/09/21

  4. Requirement Definition & Project Design

  5. Overview • General requirement • Functional and Non Functional Requirements • Use cases • Sequence diagram • Architecture of the System

  6. General Requirement • Develop a system that unifies the services a public transport system offers and allows the user to interact with them using his mobile phone • Different Payment methods • Suggestion to improving the route. • Alert specigic users for any inconvinience

  7. Functional Requirement • Enable users to register and view information via Web application • Tracking the user’s usual routes • Recognizing when the user enters or exits the vehicle • Notifying user of changes in routes or traffic problems

  8. Functional Requirement • Enable secure payment channels • Enable multiple payment options • Allow defining of custom traffic grids and various Public transportation models • Allow visualization of collected data • Allow customization of existing parameters • Report to police

  9. Non-Functional Requirement • Primary Non-functional requirements • Usability and an intuitive User interface • Safety and security of all user information and money transactions • Interoperability • Secondary Non-functional requirements • Availability • performance

  10. Use cases

  11. Use Cases Continue….

  12. Sequence Diagram

  13. Architecture Diagram

  14. Future Work • Commercial use • Improve user interface • Add more customization options as per requirements of the Public transportation system. • Supporting different mobile application platform

More Related