Car Sales Statistics - DOC
Description
Car Sales Statistics document sample
Document Sample


Car Rental Administration
May 2009 version 1.1
by
Class 1q
Per S Laursen &
Susanne Ruge
Roskilde Business Academy
Roskilde Business Academy – DMU Spring 2009
Table of contents
Table of contents ....................................................................................................................... 2
1. Inception phase ................................................................................................................. 3
1.1. Purpose...................................................................................................................... 3
1.2. Overview of activities ............................................................................................... 3
1.3. Elicit stakeholders requests ....................................................................................... 3
1.4. Find Actors and Use Cases ....................................................................................... 3
1.5. Structure the Use Case Diagram ............................................................................... 5
1.6. Detail a Use Case ...................................................................................................... 5
2. Elaboration phase, iteration E1 ......................................................................................... 6
2.1. Overview of activities ............................................................................................... 6
2.2. Develop the domain model ....................................................................................... 6
2.3. Architectural analysis................................................................................................ 8
2.4. Use case analysis....................................................................................................... 9
2.5. GUI Design ............................................................................................................... 9
2.6. Use case design ......................................................................................................... 9
2.6.1. System Sequence Diagrams .............................................................................. 9
2.6.2. Operation contracts ......................................................................................... 10
2.7. Class Design............................................................................................................ 10
2.7.1. Sequence Diagrams ......................................................................................... 10
2.7.2. Design Class Diagram..................................................................................... 11
2.7.3. Start up ............................................................................................................ 11
2.8. Coding of classes .................................................................................................... 12
Susanne Ruge & Per S Laursen Page 2 of 12
Roskilde Business Academy – DMU Spring 2009
1. Inception phase
1.1. Purpose
The purpose of Inception phase is to state the system requirements and the boundary of the
system, find the actors and use cases.
1.2. Overview of activities
We will do the following activities:
Elicit stakeholders requests
Find actors and Use Cases
Structure the Use Case Diagram
Detail a Use Case
(Revise project plan & risk list
Develop iteration plan for Elaboration, E1)
1.3. Elicit stakeholders requests
The users at the Car Rental are Customer, Sales Manager, Salesman, Serviceman,…..
A customer search for cars for rent based upon certain criteria.
The Sales Manager uses the system to register cars, make statistics etc.
The …………
Bla, bla, bla
1.4. Find Actors and Use Cases
Primary Actors:
Sales Manager
Salesman
Serviceman
Customer
……..
Use Cases:
UC1: Register Car
UC2: Register Customer
UC3: Check In Car
UC4: Check Out Car
Susanne Ruge & Per S Laursen Page 3 of 12
Roskilde Business Academy – DMU Spring 2009
UC5: Register Contract
UC6: …
……
Susanne Ruge & Per S Laursen Page 4 of 12
Roskilde Business Academy – DMU Spring 2009
1.5. Structure the Use Case Diagram
Here we present the use case diagram which shows the interaction between actors and use
cases. Bla, bla, bla (tell about this use case diagram)
Use case diagram here
1.6. Detail a Use Case
Here we detail the use case which we have chosen to be the first to work on in our project.
The use case is described fully dressed (partly).
Bla, bla, bla (tell about this use case)
UC1: Register Car
Scope: Next generation IT application for car rental businesses.
Level: User goal
Primary actor: Manager
Stakeholders and Interests:
Manager: Wants fast, reliable registration of car information. Wants to be able to register cars
before they arrive at the company.
Salesman: Wants the right information about the cars in the rental system.
Sales Manager: Wants to know information about the cars.
Preconditions: Manager authenticated and identified.
Success guarantee: Car is saved.
Main success scenario:
1. Need for registration of car occurs.
2. Manager starts new car registration.
3. Manager enters car information (regNo, regDate, model, brand, type, color, price)
4. System saves Car.
5. System presents car information.
Alternative scenarios:
bla, bla, bla
Susanne Ruge & Per S Laursen Page 5 of 12
Roskilde Business Academy – DMU Spring 2009
2. Elaboration phase, iteration E1
2.1. Overview of activities
We will do the following activities:
….
Develop the domain model
Architectural analysis
Use case analysis
Use case design
GUI Design
Plan coding
Coding of classes
Unit testing
(Revise project plan & risk list
Develop iteration plan for Elaboration, E2)
2.2. Develop the domain model
The classes in our domain model are based on the use case RegisterCar.
(tell about the classes, attributes and structures)
Domain model here
Susanne Ruge & Per S Laursen Page 6 of 12
Roskilde Business Academy – DMU Spring 2009
Susanne Ruge & Per S Laursen Page 7 of 12
Roskilde Business Academy – DMU Spring 2009
2.3. Architectural analysis
The architecture in our system consists of 3 layers. On top we have all the GUIs, below we
have our collections/controllers and at the bottom the model classes.
Susanne Ruge & Per S Laursen Page 8 of 12
Roskilde Business Academy – DMU Spring 2009
2.4. Use case analysis
To help make the domain model, we do use case analysis. By looking at our use cases we are
able to make the classes, associations and finding the attributes. Between the class …. and
the class…. we chose the structure composition because an object in class … cannot exist
without an object in class …. Bla, bla, bla
2.5. GUI Design
This is how we have decided that our GUIs should look like:
GUI-design here
This design we think is easy to use and therefore very user-friendly. Bla, bla, bla. The above
GUI is a template which we intend to follow when designing the other GUIs.
2.6. Use case design
In use case design we do the System Sequence Diagrams (SSD) and the Operation Contracts
for the use case Register Car.
2.6.1. System Sequence Diagrams
UC1: Register Car
Susanne Ruge & Per S Laursen Page 9 of 12
Roskilde Business Academy – DMU Spring 2009
2.6.2. Operation contracts
Here we show the Operation Contracts for the use case Register Car. We show the ones that
change the domain model.
2.7. Class Design
The SSDs and operation contracts shows the system from a real-world point of view.
In class design we move into the world of software.
Here we show - by doing sequence diagrams and design class diagram - the design of our
software.
Bla, bla, bla (tell about how you did it using GRASP-Patterns)
2.7.1. Sequence Diagrams
Sequence diagram here
Susanne Ruge & Per S Laursen Page 10 of 12
Roskilde Business Academy – DMU Spring 2009
2.7.2. Design Class Diagram
By looking at the object design in our sequence diagram we are able to transform this into the
design class diagram. The Design Class Diagram shows the classes, their attributes and
operations (signatures). Also the relationships between our classes are shown.
(tell about how you did it using guidelines from Larman)
Design class diagram here
2.7.3. Start up
Sequence diagram + design class diagram (revised)
Susanne Ruge & Per S Laursen Page 11 of 12
Roskilde Business Academy – DMU Spring 2009
2.8. Coding of classes
Plan coding
Code
Unit testing
Code here
(explain your code)
Susanne Ruge & Per S Laursen Page 12 of 12
Related docs
Get documents about "