1 10-10-05 • 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!
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
110-10-05
• 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!
210-10-05
Distributed Software Development
310-10-05
Public Transportation SystemProduct Line
Augustin Petrović, Manish Kungwani
410-10-05
Overview
• Requirements Definition (Augustin Petrović)
– Requirements description– Use cases– Requirement dependencies
• Design Description (Manish Kungwani)
– Project Scope– Software Architecture
510-10-05
Requirements description(Non-functional requirements)
• Product line– 3 or 4 instances with at least one based on real
public transportation system
• Use of agile process• Model-driven development
– Umple
• Test-driven development
610-10-05
Requirements description(Functional requirements)
• Definition of domain entities– Atoms and atomic functions
• Schedules and timetables• Passenger assistance• Actual timing and vehicle position tracking• Emergency and exception handling
– Vehicle rerouting and replacement
• Future development
710-10-05
Use cases(Domain atoms)
810-10-05
Use cases(Schedules, actual timing and passenger assistance)
910-10-05
Use cases(Exception and emergency handling)
1010-10-05
Requirement dependencies
1110-10-05
Project Scope
• The Core of the Product Line• Storage Mechanism• User Interface:
– Simulations and Results– Passenger Access
• Not in the system:– Vehicle Tracking Module– Hardware Modules
1210-10-05
Software Architecture• Layered Architecture• Replaceable And Independent Layers• Somewhat Factory method pattern• No environmental specifics• Component Interaction will be instance specific• We will use:
- Umple- Java- Eclipse
10-10-05
Thank You!
Any Questions or Queries?
10-10-05
Related Documents
