What functionality of each group people will get Customer Sales Agent Sales Manager National Manager Managing Director

Function for Customer Customer (Webpage) –Register new customer information –Create a booking by: Select Rental location Select Car type Select Date of booking Select Duration of booking –View the submitted booking –Modify the submitted booking –Cancel the submitted booking

Function for Sales Agent Sales Agents –Manage Car-Out: View booking information Calculate and display rental price Update car out record –Manage Car-in: View booking information Update car in record –Serve Customer Register new customer Create/View/Modify/Cancel booking for the customer Verify customer documents

Function for Sales Manager View report for their rental store ONLY –Daily breakdown report –Weekly breakdown report

Function for National Manager View report for particular rental store –Daily breakdown report –Weekly breakdown report View report for their responsible country

Function for Managing Director View report for particular rental store –Daily breakdown report –Weekly breakdown report View report for particular country View report for the entire company

A sample on 3 tier structure / implementation In 3-tier architectures, there is a logical separation of presentation, business and data into separate layers Data Tier: manages the data Presentation Tier: controls what a user sees and can do with the system Business Tier (middle tier): controls business logic

Business Tier The business tier contains the core functionality of our system –Business rules –Work flow It provides controlled access to data It enables validation and processing of data input The business tier will be defined using classes. A collection of classes (library) will be deployed as components. (in deployment diagram)

A sample on Deployment diagram using UML > :webserver {OS=Solaris} Customer Booking :Application <Windows form> > :ApplicationServer {OS=Solaris} CustomerFacade SalesAgentFacade Booking Car Web Service > :DBServer {OS=Solaris} CompanyDB > {vendor= Oracle} JDBC RMI

A sample case on ERD database design Customer Purchase Booking 1n Car Reserved 1n Employee 1 Handle n To Other Part To Other Part

A sample on Case diagram using UML Customer Register customer Create booking View booking Modify booking Cancel booking

A sample on Class diagram using UML User Class Customer Class SalesAgents Class SalesManager Class NationalManager Class ManagingDirector Class username, password