Sistema Reserva Veiculo (Bom)

8/20/2019 Sistema Reserva Veiculo (Bom)

1/56

Group MembersNAME

IDNONesredin Idris

1035/2001 Yonas Engida

Advisor !or"u #$

%ebruar& 0'( 2012

)A*I+ DA+

,NI-E+.IY

Indusria roe I

ar +en and Onine +eservaion .&sem

IN.I,E O%

.7oo o8 ompuing and Eeria

Engineering

%or )udge ar +en 9)+: )a7ir;Dar


2/56

A"no


3/56

Table of ContentsList of figures..................................................................................................................................4

List of Tables..................................................................................................................................5

Abbreviations.................................................................................................................................6Chapter 1: Introduction................................................................................................................71.1. Background ..................................................................................................................................7

1.1.1. Background of the organization....................................................................................71.1.2. Mission and Vision of the organization.........................................................................7

1.2. Existing System.......................................................................................................................... ..81.2.1. Existing system function................................................................................................81.2.2. Problems in existing system...........................................................................................8

1.3. Proposed System..........................................................................................................................91.4. Project Scope...............................................................................................................................91.5. Objective of the Project ................................................................................................................9

1.5.1. General Objective..........................................................................................................91.5.2. Specific Objective..........................................................................................................9

1.6. Methodology............................................................................................................................... .91.6.1. Data gathering methods................................................................................................91.6.2. Design Method .............................................................................................................10

Chapter 2: System Features........................................................................................................112.1. User Requirement ............................................................................................................... .......11

2.1.1. Functional Requirement ..............................................................................................112.1.2. Non-Functional Requirements.....................................................................................13

2.2. System Requirement ...................................................................................................................142.2.1. Use-Case Diagram......................................................................................................142.2.2. Use-case Description...................................................................................................15

2.3. Analysis Model...........................................................................................................................222.3.1. Activity Diagram..........................................................................................................222.3.2. Sequence Diagram (SD)..............................................................................................31

3. Introduction.............................................................................................................................383.1. Deployment Diagram................................................................................................................. 383.2. Architectural Design..................................................................................................................393.2.1. Class Diagram.......................................................................................................................393.3. User Interface (UI) Design........................................................................................................ 403.4. Data Structure Design................................................................................................................45

3.4.1. Entity Relationship Diagram (ERD)............................................................................453.4.2. Entity Description........................................................................................................463.4.3. Relational schema........................................................................................................473.4.4. ormali!ation..............................................................................................................483.4.5. Physical data model(PDM).........................................................................................49

3.5 Algorithm Design............................................................................................................................51

References.....................................................................................................................................54

Appendix A...................................................................................................................................55Questions asked during requirement elicitation using interview..................................... ..............55

Appendix B...................................................................................................................................56

3


4/56

List of guresFigure 1 Use case diagram.......................................................................14Figure 2: Activity Diagram - Login.............................................................22Figure 3: Activity Diagram - Reserve a Vehice..........................................23

Figure 4: Activity Diagram - Rent Registration..........................................24Figure !: Activity Diagram - Vehice Registration......................................2!Figure ": Activity Diagram # $earch Vehice..............................................2"Figure %: Activity Diagram # U&date Vehice..............................................2%Figure ': Activity Diagram - Vie( Vehice..................................................2'Figure ): Activity Diagram - U&date Rent..................................................2)Figure 1*: Activity Diagram - +ance Reservation.....................................3*Figure 11: $e,uence Diagram - Login........................................................31Figure 12 $e,uence Diagram - Vehice Reservation.................................32Figure 13: $e,uence Diagram - Rent Registration.....................................32Figure 14: $e,uence Diagram - Vehice Registration.................................33Figure 1!: $e,uence Diagram - $earch Vehice.........................................33Figure 1": $e,uence Diagram - U&date Vehice........................................34

Figure 1%: $e,uence Diagram - Vie( Vehice............................................3!Figure 1': $e,uence Diagram - +ance Reservation..................................3!Figure 1): $e,uence Diagram - U&date Rent............................................3"Figure 2*: $e,uence Diagram - Vie( Reservation.....................................3%Figure 21: $e,uence Diagram - enerate Re&ort......................................3%Figure 22: De&oyment Diagram................................................................3'Figure 23: +ass Diagram...........................................................................3)Figure 24: U/ - 0ome..................................................................................4*Figure 2!: U/ - Reservation........................................................................41Figure 2": U/ - Vie( Vehice.......................................................................42Figure 2%: Vehice Registration..................................................................43Figure 2': U/ - Rent Registration...............................................................44Figure 2): U/ - $earch Vehice....................................................................44

Figure 3*: ntity Reationshi& Diagram RD...........................................4!Figure 31: Reationa a&&ing...................................................................4%

4


5/56

List of Tables5a6e 1: Use +ase - Login...........................................................................1!5a6e 2: Use +ase - Reserve Vehice..........................................................1!5a6e 3: Use +ase - Rent Registration........................................................1"

5a6e 4: Use +ase - Vehice Registration....................................................1%5a6e !: Use +ase - $earch Vehice............................................................1'5a6e ": Use +ase - U&date Vehice...........................................................1'5a6e %: Use +ase # Vie( Vehice...............................................................1)5a6e ': Use +ase - U&date Rent...............................................................1)5a6e ) Use case - +ance Reservation......................................................2*5a6e 1*: Use +ase - Vie( Reservation......................................................2*5a6e 11: Use +ase - enerate Re&ort.......................................................215a6e 12: Use +ase # Logout......................................................................215a6e 13: ntity Descri&tion.......................................................................4"5a6e 14: 7ormai8ation 5a6es..................................................................4'5a6e 1!: 9D - m&oyee 5a6e................................................................4)5a6e 1": 9D - +ustomer 5a6e................................................................4)

5a6e 1% 9D - +ustomer/no 5a6e...........................................................4)5a6e 1': 9D - Vehice 5a6e....................................................................!*5a6e 1): 9D - Reservation 5a6e.............................................................!*5a6e 2*: 9D - Rent 5a6e........................................................................!*

5


6/56

Abbreviations )+ > )udge +en ar

UC – USE CASE

ERD – Entity Relationship Diagram

UI – User Interface AD- Activity Diagram

SD – Sequence Diagram

PDM – Physical Data Model

6


7/56

Chapter 1: Introduction

1. Introduction

This chapter of the project document which provides a general introduction about theindustrial project. The chapter contains and describes about background of the organization,existing system functions and problems.

This chapter also describes about the proposed system, objective including the general andspecific objectives of the project, as well as the methodologies the we used for data gathering,analysis and design.

1.1.;ac


8/56

1.2.=isting $ystem

1.2.1. =isting system unction

Budget !ar Rental BR!" organization gives car rental service for both foreign and localcustomers. This organization carries out its daily work by providing' their service to thecustomers using manually system. The organization uses a manual system for reserving,renting, register and to keep record of all the rental activities and customer information. thedetailed existing system functions are listed as follows4 *

+uring vehicle reservation the customers reserve a vehicle by making a phonecall to the organization' otherwise he5she is expected to go to the organization tomake reservation.

+uring renting a vehicle the customer personal information, payments status andrent agreements are filled in the car rent agreement form/ppendix B"' in order to hold legal contract between the customer and organization for renting thevehicle.

The organization normal work time schedule is from 6472am 8 0422pm' thereforethe organization gives services for ten and half hours a day. The organization makes a general report about the rented vehicles once at the end

of the month and generates a report.

1.2.2. 9ro6ems in e=isting systemThe existence system has a number of problems in the working procedure for the organizationand customers. These problems are4 *

6. +uring reservation a customer reserve a vehicle on phone or expected to go to theorganization for reserving. This has its own problem in the business sector.

The organization phone may be busy or may not work when customer is callingto make reservation.

9t may be difficult to customers to get the phone number or the location of theorganization.

The customers may be resulted to unnecessary extra expense and waste their time.

Their may accrue duplicated reservation of the same vehicle. The organization may not be able to serve many customers. The customers may not get service of the organization -15: twenty four hours a

day and seven days a week" and limiting their service to local domain only.

-. +uring renting a vehicle, the customer information and contract made between themare filled in a form. The contract form made between the customer and organization may be difficult

to find incase of misplacing or disappearing due to massive collection of data.

7. +uring generating monthly report. ;hen generating report, it takes time and it may not be easy to manage and

analysis the monthly work due to massive collection of data and the generatedreport may not be accurate.

8


9/56


10/56


11/56

Chapter 2: System eatures

2. Introduction

This chapter of the project document which provides a system features of the project. Thischapter contains and described about unctional re=uirement,


12/56

Log in

67. The system should allow manager to login to the system using their username and password.

61. The system should allow staff to login to the system using their username and password.

6. The system shall allow the manager to create new user account.60. The system shall allow manager to change account password.6:. The system shall allow staff to change account password.6. The system shall allow staff to logout.6. The system shall allow manager to logout.

Vehicle

-2. The system should allow staff to register new vehicles.-6. The system shall allow staff to select vehicles in the list.--. The system shall allow customer to select vehicles in the list.-7. The system shall allow staff to ?earch vehicles by specific record.

-1. The system shall allow customer staff to ?earch vehicles by specific record.-. The system shall allow staff to update information of the vehicle in need of modification.-0. The system shall allow staff to display all lists of vehicle.-:. The system shall allow staff to display all available vehicle.-. The system shall allow customer to display all available vehicle.-. The system shall allow staff to display all rented vehicle.72. The system shall allow staff to display all off duty vehicles.

Rent

76. The system shall allow staff to register customers into rental list.7-. The system shall allow staff to update about customer rent record details in the rental list.77. The system shall be able to save all changes made on the customer rent list.

71. The system shall allow staff to select customer rent record by specific search category.7. The system shall allow staff to search rent record of customers using specific categories.70. The system shall allow staff to display customers, who rent vehicles.7:. The system shall allow staff to display all customers rent record7. The system must provide printable summary for successful committed rent.

12


13/56

2.1.2. 7on-Functiona Re,uirements

Introduction &on*functional re=uirements, as the name suggests, are re=uirements that are not directly

concerned with the specific services delivered by the system to its users. They may relate toemergent system properties such as reliability, response time, and store occupancy.

/lternatively, they may define constraints on the system implementation such as the

capabilities of 95$ devices or the data representations used in interfaces with other systems. &on*functional re=uirements, such as performance, security, or availability, usually specify or

constrain characteristics of the system as a whole. .

Usability

The system provides a help and support menu in all interfaces for the user to

interact with the system. The user can use the system by reading help and support.

Security

The system provides username and password to prevent the system fromunauthorized access.

The staffsC password must be greater than eight characters.

Performance

The system response time for every instruction conducted by the user must notexceed more than a minimum of 62 seconds.

The system should have high performance rate when executing userCs input andshould be able to provide response with in a short time span usually 2 second for highly complicated task and -2 to - seconds for less complicated task.

vailability

The system should always be available for access at -1 hours, : days a week. /lsoin the occurrence of any major system malfunctioning, the system should beavailable in 6 to - working days, so that business process is not severely affected.

13


14/56

2.2.$ystem Re,uirement

2.2.1. Use-+ase Diagram

14Figure 1 Use case diagram


15/56

2.2.2. Use-case Descri&tion1. Use-case Login

Table 1: Use Case - Login

3recondition !ustomer wants to reserve a vehicle and reservation details about

customer have to be entered.3ost*condition !ustomers reserve successfully

Basic course of User ction System Response

15


16/56

/ction 6. The customer wants to reserve avehicle.

-. The customer clicks reservation

page.1. The customer enters the

following information customer full name, 9+53assport &o,!ountry, %obile number andselects vehicle plate number,3ickup date D return date"

. The customer clicks reserve button to reserve.

. The customer accepts thereservation and clicks /ccept.

!. The system prompts thecustomer to fill a reservationform .

0. The system checks all re=uiredinformation had been filled and

the date entered dates are valid:. The system presents informationto accept or decline the rental/greement.. The system shows the customerthat the reservation has beencompleted, and presents thecustomer a reservationconfirmation number.62.

Basic course of/ction

User ction System Response

6. The customer wants to take thereserved vehicle.-. The staff open rent page.1.The staff enters >ull name,

&ationality, !ountry, !ity,

9dentification &umber, 3hone, 3late

&o, +own 3ayment, +aily 3rice, Rent+ate, Return +ate, Total Rent +ay,

Total 3ayment, Refund. The staff clicks on rent button.

7. The system displays a formto be filled out for renting thevehicle.1. The system prompts to enterthe following information. 0. The system verifies that basic fields have been filledout.:. The system displayssuccessful rent summary. ull name, &ationality, country, !ity, 9d53assport, 3hone, !ar 3late

16


17/56

course of/ction

&o, +own 3ayment, 3rice5day, Rent +ate, Return date and Total 3aymentthis fields are not filled out system goes back or returns to step 1 of basiccourse of /ction. To fill invalid field.

.Vehicle Registration

Table 4: Use Case - Vehicle Registration

detail descriptions about the Aehicle such as condition, %odel, Brand,fuel type, &umber of sits and amount of price per day.

3recondition &ew vehicle 3urchased

3ost*condition &ew Aehicle information stored successfully.


User ction System Response6. The staff wants to add a new vehicle-. The staff re=uests add new vehicleform page.1. The staff enters the followinginformation in the form.

Aehicle Brand, Aehicle Type, Aehicle

%odel, >uel Type, 3late &umber, &umber of ?its, !ondition, 3rice per

day. The staff clicks or presses on thesave or insert button.

7. The system response ordisplays a form to be filled outfor vehicle registration.0. The system verifies that thefields have been filled outcorrectly.:. The system displays asuccessfully stored message tothe employee..


18/56

". Search Vehicle

Table 5: Use Case - Search Vehicle

6. The user wants to update vehicleinformation.-. ?earch vehicle by plate number.1. The staff enters updateinformation of vehicle.. The employee click on update button.

7. The system will display allinformation about the vehicle.0. The system successfully updatesinformation in to database.:.


19/56

". Vie# Vehicle

Table 7: Use Case – View Vehicle

3riority %edium

/ctor ?taff and customer +escription This use case allows staff and customer to view or display all vehicles

with their detail description about the vehicle.

3recondition Aehicle Rent, Reserve

3ost*condition Aiews all vehicles


User ction System Response 6. The staff or !ustomer wantsview vehicle.

-. The staff or customer click onview vehicles button.

7. The system retrieves allinformation about the vehicles.

1.

incase when there is a need for editing3recondition &eed to !hange information3ost*condition ?uccessful


20/56

1%. &ancel Reservation

Table 9 Use case - Cancel Reservation

reservation.-. The staff re=uests the

reservation 3age.1. Then on reservation page the

employee clicks view button.

7. The system responds the re=uested

page.. The system puts on view or

displays all reservation informationto the employee.

0.


21/56

12. 'enerate Report

Table 11: Use Case - Generate Report

about the renting information of a month.3recondition %anager wants to see report3ost !ondition Henerate monthly Report 9nformationBasic !ourse of/ction

User ction System Response6. The %anager wants to generate report.-. The %anager clicks rent pages.. Then on the rent page the %anager specifies

the month and then clicks on the generate button.

7. The system respondsthe re=uested page.

:.

accomplishing their work.3recondition

6. The ?taff ormanager wants tolog out

-. The ?taff ormanager clicks thelog out button

7. The system responds to the re=uestedaction.

1. The system displays a message that the?taff or manager logged out from thesystem.

.


22/56

2.3.Anaysis ode

2.3.1. Activity Diagram

/n activity diagram is a variation of a state machine in which the states represent the performance of actions or sub activities and the transitions are triggered by the completion of the actions or sub activities. 9t represents a state machine of a procedure itself.

1. )ctivity *iagram - Login

22

Figure 2: Activity Diagram - Login


23/56

2. )ctivity *iagram + Reserve a Vehicle

23

Figure 3: Activity Diagram - Reserve a Vehicle


24/56

(. )ctivity *iagram + Rent registration

24

Figure 4: Activity Diagram - Rent Registration


25/56

4. )ctivity *iagram + Vehicle registration

25

Figure 5: Activity Diagram - Vehicle Registration


26/56

. )ctivity *iagram + Search Vehicle

26

Figure 6: Activity Diagram – Search Vehicle


27/56

,. )ctivity *iagram + Update Vehicle

27

Figure 7: Activity Diagram – Update Vehicle


28/56

!. )ctivity *iagram + Vie# Vehicle

28

Figure 8: Activity Diagram - View Vehicle


29/56

". )ctivity *iagram + Update Rent

29

Figure 9: Activity Diagram - Update Rent


30/56

$. )ctivity *iagram + &ancel Reservation

30

Figure 10: Activity Diagram - Cancel Reservation


31/56

2.3.2. $e,uence Diagram $D

/ sequence #iagram shows an interaction arranged in time se=uence. 9n particular, it

shows the instances participating in the interaction by their ElifelinesG and the stimuli thatthey arranged in time se=uence. 9t does not show the associations among the objects.

?awyer 9. a."

1. Seuence *iagram + Login

31

Figure 11: Sequence Diagram - Login


32/56

2. Seuence *iagram + Vehicle Reservation

(. Seuence *iagram + Rent Registration

32

Figure 12; Sequence Diagram - Vehicle Reservation

Figure 13: Sequence Diagram - Rent Registration


33/56

.a?( usomer

!"C: #atabase

4. Seuence *iagram + Vehicle Registration

. Seuence *iagram + Search Vehicle

33

Figure 14: Sequence Diagram - Vehicle Registration

Figure 15: Sequence Diagram - Search Vehicle


34/56


35/56

!. Seuence *iagram + Vie# Vehicle

". Seuence *iagram + &ancel Reservation

35

Figure 17: Sequence Diagram - View Vehicle

Figure 18: Sequence Diagram - Cancel Reservation


36/56

$. Seuence *iagram + Update Rent

36

Figure 19: Sequence Diagram - Update Rent


37/56

1%. Seuence *iagram + Vie# Reservation

11. Seuence *iagram + 'enerate Report

37

Figure 20: Sequence Diagram - View Reservation

Figure 21: Sequence Diagram - Generate Report


38/56

#hapter $hree% S&S$'( )'SI*+

3. $ntro#uction

This chapter of the project document which provides a system design of this project. Thischapter contains and describes about deployment diagram, architectural design, user interfacedesign, data structure design and algorithm design.

3.1.De&oyment Diagram

+eployment diagrams show the configuration of run*time processing elements and the

software components, processes, and objects that live on them. ?oftware component instancesrepresent run*time manifestations of code units.

38

Figure 22: Deployment Diagram


39/56


40/56

3.3.User /nterace U/ DesignUser interface is the external part of the system which is used to access and interact withthe system easily.

,-UI /ome Page

40

Figure 24: UI - Home


41/56

,0- UIReservation

These is the external user interface for reserving vehicle, the customers prompt to filltheir >ull name, &ationality, %obile &umber and after filling personal informationthey prompt to select the vehicle type, 3ick up date and Return date.

41


42/56

,#- UI View Vehicle

This is the user interface for the user after logged in to the system. The


43/56

,)-UIVehicle Registration

This is the user interface re=uire username and password to access the system. The


44/56

,'- UIRent Registration

,- UI Search Vehicle

44

Figure 28: UI - Rent Registration

Figure 29: UI - Search Vehicle


45/56


46/56

3.4.2. Entity Description

In here we provide a description of entities with all their attributes. Describing entity name,business definition for the entities and there attribute and domain.

Table 13: Entity Description

Entity Name Business definitionEmployee This entity is responsible to store Employee information in the database.Customer Attribute stores customers’ details information in the database, in order to

identify the customer.Vehicle This entity is stores the information of the vehicle in the database.Reservation This stores information about the reservations made by a customer.Rent This stores rental information of the vehicle, payments

46


47/56

3.4.3. Relational schema

'mployee

'mpI

>name %name @name !ountry !ity Res3hone %obile&umbe

r

?alary (ire+ate Responsiblity ('(PI)

#ustomer

#ustomerI >name %name @name 9dentification&umber &ationality !ountry !ity %obile&umber

Vehicle

Plate+umbe

r

Brand Type %odel ?eatJuantity >uelType !ondition +aily3rice '(PI)

Reservation

ReservationI Reservation+ate 3ickup+ate Return+ate 3& !9+

Rent

ntI Rent+at

e

Return+at

e

TotalRent+a

y

+ailyRental>e

e

>uel3rovidedB

y

>uel!harg

e

+own3aymen

t

Total3ai

d

Refun

d

3

&

!9

+

#9

+

RS

)

Figure 31: Relational Mapping

47


48/56

3.4.4. ormali!ation

&ormalization is a process that aims at achieving better designed relational database schemasthrough the user of semantic information given by >unctional dependencies and 3rimary keys,

&ormalization process takes a relational schema through a series of tests to certify whether it

satisfies conditions. The schemas that satisfy certain condition are said to be in a given

E&$R%/@ >$R%C and unsatisfied schema are decomposed by breaking up their attributesinto smaller relations that posses desirable properties. &ormalization allows us to organize

data that it allows fast access and reduced space. Elmasri% "UD&'E&S *"

D&&+&SE S,SE'S- 23).

'mployee

Table 14: Normalization Tables

#mp9

d

nam

e

(nam

e

Lnam

e

#ountr

y

#it

y

ResPhon

e

(obile+umbe

r

Salar

y

/ire)at

e

Responsiblit

y

%#%39+

#ustomer

!ustomer9d name (name Lname Ientification+umber +ationality #ountry #ity

#ustomer3Info

!ustomer9d (obile +umber

Vehicle

3late&umber 0ran

$ype (oel Seat4uantity uel$ype #onition )ailyPrice #%39+

Reservation

Reservation9

d

Reservation)at

e

Pic5up)at

e

Return)at

e

P+ #I)

Rent

Rent)at Return)at $otalRent)a )ailyRentale uelProvie0 uel#harg )ownPaymen $otalPai Refun P #I 'I

48


49/56

e e y e y e t + ) )

3.4.!. 9hysica data mode9D

Table 15: PDM - Employee Table

Table &ame 'mployeettribute )ata type Length $ype of attribute

#mp9d Aarchar 2 3rimary Key>name Aarchar 2%name Aarchar 2@name Aarchar 2

!ountry Aarchar 2!ity Aarchar 2Res3hone int%obile&umber int?alary float(ire+ate +ateResponsiblity Aarchar 2%#%39+ Aarchar 2 >oreign key

Table 16: PDM - Customer Table

Table &ame #ustomerttribute )ata type Length $ype of attribute!ustomer9d Aarchar 2 3rimar y Key>name Aarchar 2%name Aarchar 2@name Aarchar 2!ountry Aarchar 2!ity Aarchar 2 &ationality Aarchar 29dentification&umber

Aarchar 2

Table 17 PDM - CustomerInfo Table

Table &ame #ustomerInfottribute )ata type Length $ype of attribute!ustomer9d Aarchar 2 >oreign Key%obile&umber int 3rimary Key

49


50/56

Table 18: PDM - Vehicle Table

Table &ame Vehiclettribute )ata type Length $ype of attribute3late&umber Aarchar 2 3rimary KeyBrand Aarchar 2Type Aarchar 2%odel Aarchar 2 &umberof?eat int>uelType Aarchar 62

!ondition Aarchar -2+aily3rice float#%39+ varchar 2 >oreign Key

Table 19: PDM - Reservation Table

Table &ame Reservationttribute )ata type Length $ype of attributeReservation9d Aarchar 2 3rimary KeyReservation+at

e

+ate

3ickup+ate +ateReturn+ate +ate3& varchar 2 >oreign Key!9+ Aarchar 2 >oreign Key

Table 20: PDM - Rent Table

Table &ame Rentttribute )ata type Length $ype of attributeRent9d varchar 2 3rimary keyRent+ate +ateReturn+ate +ateTotalRent+ay int 62+ailyRent>ee int 62>uel3rovidedBy

varchar 72

>uel!harge varchar 62

50


51/56

+own3ayment >loat 62Total paid >loat 62Refund >loat 623& varchar 2 >oreign Key!9+ Aarchar 2 >oreign Key

R?9+ Aarchar 2 >oreign Key

3.! Agorithm Design In this part we describe the algorithm of the operations or methods which found in classdiagram using Pseoudocode. Pseoudocode is one type of algorithm representation method byusing English language.

Pseoudocode reserving vehicle

Steps/procedureMethod name=reserve vehicle

BeginVariables -plate number -pickup date -reservation date -reservation id -customer id

If (*variables are valid*) Then

Add to table reserve (plate number, pickup date, reservation date, reservation id

customer id) Otherwise

Display “the inputs are invalid!” Endif

Display “the conformation number”End

Pseoudocode for rent vehicleSteps/procedureMethod name=rent vehicleBegin

Variables -plate number -rent date -total paid -return date -refund -total rent day -rent id - daily rent fee -customer id

-fuel provided by -employee id -down payment

If (*variables are valid*)Then

51


52/56

Add to table rent (rent date, total paid, return date ,refund, total rent day, rent id,daily rent fee, customer id, fuel provided by, employee id, down payment)Otherwise

Display “the inputs are invalid!”Endif

End

Pseoudocode employee for registration

Steps/procedure

Method name=employee registrationBegin Variable - full name -address -employee id

-user name -passwordIf (*inputs are valid*)

Then Add to table employee (full name, address, employee id, user name, password) Otherwise

Display “inputs are not valid try again!”Endif

End

Pseoudocode register vehicleSteps/procedureMethod name=register vehicle

BeginVariables-brand-model

-plate number -number feat -fuel type -condition -daily price

If (*variables are valid*)Then

Add to table vehicle (brand, model, plate number, number feat, fuel type, condition,Daily price)

OtherwiseDisplay “inputs are invalid”

Endif End

52


53/56

Pseoudocode for loginSteps/procedure

Method name=login

Begin Variables:-username -password

If (*inputs are valid*)(*select the previous username and password from database and compare with entered*)

If username = entered username and Password = entered password(*go to login page*)

OtherwiseDisplay “login error!”

EndifOtherwise

Display “inputs are invalid try again!”

Endif End

53


54/56

ReerencesElimasir. (3343). database. azxa.Elmasri, R.

FUNDAMENTALS OF DATABASE SYSTEMS. (2003). jacobson, G. i. (2003). Applying use cases. Sawyer, I. a. Requirement Engineering a good Practice. Sawyer, S. &. Requirement Enginering. Will, T. (2009). SSD.

54


55/56

Appendi$ A

%uestions as&ed during re'uirement elicitationusing intervie(Q1. What makes your organization different from other organization who rents a car?Q2. What is the objectives of your organization?Q3. What is the mission of your organization?Q4. How many branches does your organization have?Q5. How many employees do you have?Q6. How does your current system work? A. Is it manual? B. is it computerized?

C. is it semi computerized?Q7. If your answer for question number 6 is choice “b” or “c” what computer applications do

you use?Q8. How many cars do you have?Q9. What kinds of car models do you have?Q10.What is the procedures or steps when a customer rents a car?Q11.What qualifications are expected from a customer who wants to rent a car?Q12.Where do you keep customer and rental information’s?Q13.How do you keep track of which cars are rented and which are not?Q14.How many cars a client can rent at a time?Q15. How do you generate customer and rental information’s?

55


56/56

Appendi$ !

Sistema Reserva Veiculo (Bom)

Documents

Transcript of Sistema Reserva Veiculo (Bom)