IT610 –Object-oriented System Analysis
Southern New Hampshire University
Dr. Philip Funk
March 28h, 2012
Prepared by: Abdelhak Halloum Chen Lin
Table of contents
Table of contents
1.Background of organization2
2.Vision or statement of purpose2
5.1.Use case1: Register car3
5.2.Use Case2: Check availability5
5.3.Use Case3: Complete payment7
6.1. Register car10
1. Background of organization
Easy & Quick Car Leasing Service (EQCLS) offer the opportunity for clients to
lease a new car or a used car from various dealers supporting car leasing business
whether in a short or long term. In additional, EQCLS help the customers make the best
available choice based on their quest through the analyses system.
Car leasing business is a convenient way for people to drive a nice car without huge cost.
However, most people possibly make the mistake of rushing into things, without even
considering and comparing the information the dealers offered. They most often are
attracted by enticing advertisements shown on TV or in the other Medias. Moreover,
without the support of professional analysis, the client is hard to make a perfect decision
from thousands of cars for leasing.
2. Vision or statement of purpose
EQCLS have a complete database including large vehicle information from
various dealers. The customer just need to enter the quest that what kind of car they want
to drive, how much they expect to pay for the leasing, how long they will lease, and
what’s their location. The analysis system will make a suggest car list for the customer to
choose after combining the basic information the customer offered with some dealership
tip such as capitalized cost, cap cost reduction and interest rate to calculate the relative
3. Event list
The dealer registers the car to the system.
The customer reserves available vehicle from the system.
The customer completes payment.
5. Use cases
Our project has 3 use cases:
UC1: Register the car to the system.
UC2: Reserve available vehicle from the system
UC3: Complete payment
5.1 Use case1: Register car
Primary Actor: Dealer
Stakeholders and Interests: Dealer: Wants fast, reliable registration of car information. Description:The dealer starts new car registration. The dealer enters the car’s information into the system. The system will response a confirmation when the registration is finished. Preconditions: Dealer authenticated and identified.
Postconditions: Car is saved into the system.
Main Success Scenario
Actor Action| System Response|
1. Start new car registration| |
2. Enter the car’s information| 3. Save car4. Present a confirmation | Extensions (or Alternate Flows)
Step2 If the Dealer enters the car’s information incorrect: 1. The dealer will delete the incorrect information.
2. Use case runs to the step 2.
3. Credit card
5.2 Use Case2: Check availability
Primary Actor: Customer
Stakeholders and Interests:
Customer—has interest in choosing a good car with good price.
Dealer—has interest in leasing car as much as he can.
Description:The customer enters the request about the car to the system. The customer
receives a suggestion car list. After checking availability, the customer chooses a car
from the suggestion car list. The customer makes a reservation and gets the reservation
Preconditions: The dealer...