© Team Hockey The Electric Car Rental Project Client: Rotations Team Hockey Ryan Allen Paul Crum...
-
Upload
homer-briggs -
Category
Documents
-
view
216 -
download
0
Transcript of © Team Hockey The Electric Car Rental Project Client: Rotations Team Hockey Ryan Allen Paul Crum...
© Team Hockey
The Electric Car Rental Project Client: Rotations
Team HockeyRyan AllenPaul CrumKen GergesRyan HorneJim Jamieson
© Team Hockey
Our Charter
Rotations is a nationwide rental car service that is planning on starting a new business geared toward city customers.
The electric cars will be provided at one location for drop off in another.
Our goal is to take their existing systems and integrate them, thus making the processes more automatic instead of manual.
© Team Hockey
Current Architecture at Rotations
1. Customer calls on the cell phone to find a car close to where she is.
2. The service checks GPS for customer location and determines closest location
3. The service reserves a car at this location
4. The service charges the customer’s credit card
5. The service informs the customer and gives a time and mileage allowance
6. The customer picks up the car and drives to desired location
7. The car is tracked via GPS, directions given if needed, and problems if any dealt with
© Team Hockey
Electric Car Rental – New LOB
We are using middleware
solutions to integrate Rotations
applications and systems to better
facilitate their business practices.
© Team Hockey
Proposed Workflow Models
Workflow models map the flow of informationThey manage the movement of data
and the invocation of processes in the correct and proper order.
© Team Hockey
Our Workflow Models
1. Reserve a Car 2. Pick up a Car a. Uses Credit Card Check I. Credit card on file b. Insurance 3. Return a Car
a. Pay for a reservation4. Change a Reservation5. Cancel a Reservation6. Perform Preventive Maintenance on a
Car 7. Move a car
© Team Hockey
Go To ClerksDesk
CustomerArrived AtLocation
Enters Customer InfoTo Access Account
ClerkFound
Request CarStatus Update
Gets Paperwork andKeys
SystemUpdated
Actor: Customer Actor: Clerk
Actor: Clerk
Actors: Customer andClerk
Customer Leaves
EndRequest
Actor: Customer
InfoSubmitted
Access CustomerAccount
AccountAccessed
Actor: AMS
Retrieve ReservedCar Info
Actor: AMS
Car InfoRetrieved
Perform Steps to FinalizeTransaction
StatusUpdate
UpdateRequest
Update CarStatus
Actor: BRS
Paperworkand KeysReceived
Paperworkand Keys
Receive Paperwork andKeys
Actor: Customer
End CustomerSession
Car PickedUp
CustomerLeft
Actor: AMS and Clerk
End Session
Actor: AMS
SessionEnded
Check CarStatus
CarAvailable
Car NotAvailable
Check forAlternate Car
NotifyCustomer
CarFound
CustomerNotified
Actors: AMS
Decides
DeclinesOffer
AcceptsOffer
CarSearch
Locate NearestCar
Actor: AMS
Terminate Session
SessionTerminated
Actor: Clerk and BRS
Actor: Customer
Car NotFound
Give Customer GiftCertificate
CertificateGiven
Team Hockey:Workflow Model for
Pick up a Car
Insurance CheckVerified
Insurance
Check CreditCard
FileSaved
Check ForInsurance
InsuranceCheck
Actor: Clerk
Actor: Clerk
Actor: AMS
Actor: Clerk
Actor: Clerk
Process RequestAccessRequest
Actor: AMS
© Team Hockey
AccountAccessed
Check for CreditCard on file
CreditCard
Search
Search For CreditCard On File
No CreditCard
FoundNotify Cusomter
CreditCardfound
SearchResults
Return SearchResults
OptionOffered
Decides
Create CreditCard On File
Notify CustomerCustomerNotified
CustomerNotified
Offer New CreditCard Option
NewCreditCard
Choosen
Use Old CreditCard
CreditCard On
FileSaved
NewCreditCard
Old CreditCard
Choosen
Create New File forCredit Card
Actor: Clerk
New CreditCard On File
Request
Use New CreditCard
Team Hockey:Workflow Model forCredit Card Check
Save ApprovalStatus In Credit
Card On File
RequestSent
Request CreditCard Approval
InsufficientFundsReceive Credit
Card Request
Old CreditCard On
File
SufficientFunds
RequestReceived
Check SpendingLimit
Check For TimelinessOf Payments
Confirmed
FileSaved
NotConfirmed
Rejects CreditCard
CreditCard
Rejected
Accepts CreditCard
ConfirmationMessage
Return SuccessfulApproval Status
ApprovedCreditCard
Actor: Clerk Actor: AMS
Actor: AMS
Actor: ClerkActor: ClerkActor: Customer
Actor: Clerk
Actor: Clerk
Actor: Clerk
Actor: Clerk
Actor: ACT Actor: ACT
Actor: ACT
Actor: ACT
Actor: ACT
Actor: ACT
Actor: CAM
© Team Hockey
Get Credited Card Infofrom Customer
Created FileRequest
SentSend Request To CreateNew File for Credit Card
FileCreated
Enter Info IntoCredit Card On File
InfoReceived
InfoSubmission
Request
Info Sent To BeRecorded
InfoRecorded
Confirm Credit CardNumber
ConfirmationRequest SentDetermine Validity
Not Valid
Valid
Delete Credit CardFile
New CreditCard
Credit CardOn FileSaved
Actor: Clerk Actor: AMS Actor: Clerk Actor: Clerk
Actor: Credit CardCompany
Team Hockey:Workflow Model for
Paying for ReservationCredit Card Check: Create
Credit Card on File
New CreditCard On File
Request
Actor: AMS
Actor: AMS
Actor: Credit CardCompany
Save Credit CardInfo
Actor: CAM
Process SaveRequest
Actor: AMS
Send SaveRequest
© Team Hockey
DeclineOffer
Offer CompanyInsurance
Customer DecisionInsuranceOffered
Check ForCustomerInsurance
InsuranceCheck
CustomerDoes Not
HaveInsurance
CustomerHas
Insurance
ReservationCanceled
AcceptOffer
Verify Insurance
Process ChargeRequest
Update VerificationOf Insurance
InsuranceVerified
CreditCard
Charged
InvalidInsurance
CancelReservation
Send ChargeRequest
RequestSend
GrandTotal ForInsurance
CalculateInsurance Subtotal
SubtotalCalculated
TaxesCalculated
Calculate TaxesAdd Taxes To
Subtotal
UpdatedInsurance
Update VerificationOf Insurance
VerifiedInsurance
Send ChargeMessage
MessageSent
Receive ChargeMessage
MessageReceived
Give CustomerReceipt
Receipt Sign ReceiptSignedReceipt
InsuranceUpdateRequest
Save Update
Actor: Clerk
Actor: Clerk
Actor: Clerk
Save VerificationStatus
Actor: Customer
Actor: ACT
Actor: ACTActor: ACTActor: ACTActor: Credit CardCompany
Actor: CAMActor: Clerk
Actor: Credit CardCompany
Actor: ACT Actor: ClerkActor: Customer
Actor: AMS
Actor: CAM
Team Hockey:Workflow Model for
Insurance
Send NotificationOf Successful
Save
SuccessfulUpdate
Actor: AMS
NotificationReceived
NotificationSent
Actor: Clerk
VerifiedInsurance
Send NotificationOf Successful
Save
VerificationSaved
Actor: AMS
NotificationReceived
NotificationSent
Actor: Clerk
© Team Hockey
NAME: AMS -> BRSAsset Management System -> Reservations SystemWorkflow
Name:Task Name: Information passed: Communication
Model/Type:Communication
Frequency:
Reserve a Car process Retrieve Reserved Car Information
Request all reserved car information created by customer
Synchronous Real time
Reserve a Car process Reserves Car Customer reserves car Synchronous Real time
CustomerInfo
Retrieved
Retrieve ReservedCar Info
Actor: BRS And DAM
Process RequestRetrievalRequest
Actor: DAM And BRS
Reserves Car
Actor: BRS
CarReserved
Update Reservation
Actors: BRS
SystemUpdated
CustomerReservation
Update CustomerAccount
CustomerAccountUpdated
Actor: AMS
1.
1.
2.
2.
Integration Requirements
© Team Hockey
Proposed Technology Choices
Distributed Object Computing Middleware
Message-Oriented Middleware Presentation Middleware
© Team Hockey
ACT
AMS
CAM
ACQ
AAM
BRS
DAM
MTS
PTS
PAM
DOCM
DOCM
DOCM
MOM
MOM
MOM
DOCM andPresentationmiddleware
DOCM
MOM
DOCM
Proposed Architecture
© Team Hockey
Methodology for Implementation
We will follow the 12-step methodology. Understanding the enterprise Making sense of the data Making sense of the processes Identifying the application interfaces Identifying business events Identifying data transformation scenarios Mapping information movement Applying technology Testing Considering performance Defining value Creating maintenance procedures
© Team Hockey
Methodology for Implementation
We chose this strategy, because it is a very in-depth solution and outlines all the necessary steps that are needed when doing any integration project.
Each of the major steps in our methodology are outlined in our project plan so we are certain that these steps are completed in a time
© Team Hockey
Proposed Project Plan
1 Understanding the Enterprise 2 Making Sense of the Data 3 Making Sense of the Processes 4 Identifying the Application Interfaces 5 Identiying Business Events 6 Identifying Data Transformation Scenarios 7 Mapping Information Movement 8 Applying Technology 9 Testing 10 Considering Performance 11 Defining the Value 12 Creating Maintenance Procedures
© Team Hockey
Critical Path