INDIVIDUAL PROJECT

ON
WEB BASED FOR FISHA CAR BROKER SYSTEM
SUBMITTED
IN PARTIAL FULLFILMENT OF THE REQUIRMENTS FOR
THE INDIVIDUAL PROJECT IN BACHELOR OF SCIENCE
IN
INFORMATION TECNOLOGY

BY
Nejat Fentaw ---------------ENG/R/1522/03
Advisor: Yibeltal Tefera
Sunday, June 29, 2014

Page i
Web based for Fisha car broker system
 Declaration

The Project is my own and has not been presented for a degree and/or course project in
any other university and all the sources of material used for the project have been duly
acknowledged.

------------------------------------- ---------------------------------------------

Name Signature

School: School of Computing and Electrical Engineering

Program: INFORMATION TECHNOLOGY

Project subject: Web based Fisha Car Broker System in

Bahir Dar

This is to certify that I have read this project and that in my opinion it is fully adequate,
in scope and quality, as a project for the course individual project.

------------------------------------- ---------------------------------------------

Name of Advisor Signature

Examining committee members signature Date

1. Examiner 1 ……………………. ………………..

2. Examiner 2 …………………….. ……………….

It is approved that this project has been written in compliance with the formatting rules
laid down by the school of the university.

Page ii
Web based for Fisha car broker system
Abbreviation and acronyms

UC – Use Case

PHP – Hyper Text Preprocessor

MySQL– My Structured Query Language

BDU – Bahir Dar University

HTML – Hyper Text Markup Language

Page iii
Web based for Fisha car broker system
 Acknowledgment
I take this opportunity to express my sincere thanks to worker of fisha broker system for their
kind permission for allowing me to undergo project work and for giving me whole hearted co-
operation for completing the project work. Also I have thankful to my advisor instructor Yibeltal
Tafere because he helps and guide me to complete this project confidentially.
Finally I express my gratitude to all those who directly or indirectly helped me in completion of
my project.

Page iv
Web based for Fisha car broker system
Contents
Abstract .............................................................................................................................................1
Chapter One.......................................................................................................................................2
1.1 Background...............................................................................................................................2
1.2 Introduction..............................................................................................................................2
1.3Objective of the project..............................................................................................................2
1.3.1 General objective ................................................................................................................2
1.3.2 Specific objective ................................................................................................................2
1.4 Scope of the project ..................................................................................................................3
1.5 Methodology ............................................................................................................................3
1.6 Existing system..........................................................................................................................4
1.7 Statement of problem ...............................................................................................................4
1.8 Proposed System.......................................................................................................................4
1.9 Benefit of the project ................................................................................................................4
CHAPTER TWO ...................................................................................................................................5
2.1 Requirements ...........................................................................................................................5
2.1.1 User requirement................................................................................................................5
2.1.2Functional requirement........................................................................................................5
2.1.3 Nonfunctional requirements................................................................................................6
2.2 Use case diagram ......................................................................................................................7
2.2.3 Use case description............................................................................................................9
2.3 Analysis model ........................................................................................................................23
2.3.1 Activity diagram................................................................................................................23
2.3.2 Sequence diagram.............................................................................................................38
CHAPTER THREE ...............................................................................................................................49
3.1 System Design.........................................................................................................................49
3.1.1 Deployment Diagram ........................................................................................................49
3.1.3 Class diagram....................................................................................................................52
3.2 User Interface (UI) Design ........................................................................................................53
3.3 Algorithm Design ........................................................................................................................60
Bibliography.....................................................................................................................................62

Page v
Web based for Fisha car broker system
Appendix A.......................................................................................................................................62
Conclusion....................................................................................................................................63

List of table
Table 1 Use case description Login. .....................................................................................................9
Table 2 Use case description View Car Information. ............................................................................10
Table 3 Use case description Register Supplier. ..................................................................................11
Table 4 Use case description Upload Car. ..........................................................................................12
Table 5 Use case description Delete supplier. .....................................................................................13
Table 6 Use case description View comment. ....................................................................................14
Use case description View Report. .....................................................................................................15
Table 7 Use case description Delete Car. ............................................................................................16
Table 8 Use case description Logout. .................................................................................................17
Table 9 Use case description Send comment. ....................................................................................18
Table 10 Use case description Search Supplier. ..................................................................................19
Table 11 Use case description Search Car ..........................................................................................20
Table 12 Use case description Update Car ........................................................................................21
Table 13 Use case description Order Car ............................................................................................22

List of figure
Figure 4 Activity Diagram- Logout ....................................................................................................24
Figure 5 Activity Diagram- View Car Information.................................................................................25
Figure 6 Activity Diagram- Delete Supplier Information .....................................................................26
Figure 7 Activity Diagram- Search Supplier Information .....................................................................27
Activity Diagram- Send Comment ......................................................................................................28
Activity Diagram- View Comment ......................................................................................................31
Figure 9 Activity Diagram- Upload Car ...............................................................................................31

Page vi
Web based for Fisha car broker system
Figure 10 Activity Diagram- Update Price..........................................................................................33
Figure 11 Activity Diagram- Register Supplier....................................................................................34
Figure 14 Activity Diagram- Generate Report ...................................................................................37
Figure 15 Login sequence diagram ....................................................................................................38
Figure 16 Send comment sequence diagram ......................................................................................39
View information sequence diagram..................................................................................................40
Figure 17 Update price sequence diagram ........................................................................................41
Figure:- View comment sequence diagram .........................................................................................42
Figure 18 Register supplier sequence diagram ...................................................................................43
Figure 19:-Delete supplier sequence diagram.....................................................................................44
Figure 20:view comment sequence diagram.......................................................................................45
Figure 21:-Search supplier sequence diagram.....................................................................................46
Figure 22:-Delete car sequence diagram ............................................................................................47
Figure 23:-Upload car sequence diagram ...........................................................................................48

List of user interface

User interface 1 Home ......................................................................................................................53
User interface 2 Login form...............................................................................................................54
User interface 3 Register supplier ......................................................................................................55
User interface 4 User view Toyota car................................................................................................56
User interface 5 user write comment .................................................................................................57
User interface 6 View comment.........................................................................................................58
User interface 7 View report .............................................................................................................59

Page viii
Web based for Fisha car broker system
Abstract

Traveling is a large growing business in Ethiopia and other countries. Car broker system deals
with maintenance of records of details of each supplier and customers. It also includes
maintenance of information like schedule of each car.

I observed the working of the car broker system and after going through it, I get to know that
there are many operations, which they have to do manually. It takes a lot of time and causes
many errors. Due to this, sometimes a lot of problems occur and they were facing many disputes
with customers. To solve the above problem, and further maintaining records of items, car
availability for customers, price of car and other things, I am offering this proposal of car broker
system.

By using this software, customer can order car to buy from any part of the world, through
telephone lines, via internet. This project provides and checks all sorts of constraints so that user
does give only useful data and thus validation is done in an effective way.

Page 1
Web based for Fisha car broker system
Chapter One

1.1 Background
Ethiopia has many personal brokers that are trains traditionally. The old-style broker system of
the country was wasteful and lack of full information to buy and sell car. Customer and providers
are lost their time, money and labor force to get the broker. Fiseha was beginning in 1995 EC to
lead his family. He starts without initial capital and still guides his life by negotiate customer
with seller. Now, he has office to communicate customer.

1.2 Introduction
Currently, Web based system are especially identified as a way to increase business systems; in
this document we will be exploited for the implementation of online Fisha car broker system.
The main target of the proposed online broker system collects information from seller and allows
customer to search and get information. For this purpose, the broker or the system receives the
car information from seller. The main objective of this project is developing a web based online
broker system and advertises the car information of the seller.

1.3Objective of the project

1.3.1 General objective

The main objectives of the project is developing a web based system for Fisha car broker system

1.3.2 Specific objective

 Designing interfaces that customer can use the system online.
 Design and build a particular model of this proposed system.
 Designing application that implements server-architecture.
 Implement the proposed system.

Page 2
Web based for Fisha car broker system
1.4 Scope of the project

 The scope of this project is developing web based system for Fiseha car broker system.
The system capable to introduce to the customer in every area where internet is available.

1.5 Methodology

Method

 Literature Review
 Data collection
 Observation

Tools

 Notepad++
 Wampserver:-
 Microsoft office:
 Adobe Shoppe
 Microsoft office Visio 2003:-
 Dreamweaver:-For editing the code

Page 3
Web based for Fisha car broker system
1.6 Existing system
 He communicates only by phone.
 This not easy for customer and seller to get information about the car
 He uses a face to face communication only.
 He works service is done manually.

1.7 Statement of problem

 Customer takes long time to seller and the broker

 Lack of direct known information about the car:
 Killing time to get the broker to communicate with. Seller or the customer.
 Customers and seller can’t get service easily.
 Takes many cost, time and human resource.

1.8 Proposed System

 Change the existing system in to online system
 The proposed system is online broker system which enhances manual system and
 Gives service to all users when internet is available only.
 Correct online information for available places
 generate report
 Allows the system to every information about the description of the car

1.9 Benefit of the project

 Availability of car with description timely.

 To make good broker system
 To satisfy the customer and supplier

Page 4
Web based for Fisha car broker system
CHAPTER TWO

2.1 Requirements

2.1.1 User requirement

User requirements are requirement that is used to add further detail to the business
requirements. They are called user requirements because they are from a user’s
perspective and the focus of user requirement describe tasks the user must be able to
accomplish in order to fulfill the stated business requirements

2.1.2Functional requirement
Functional requirements are statements of services that used to capture the intended
behavior of the system. This behavior may be expressed as services, tasks or functions the
system is required to perform.
 The System shall accept user and it locates to page.
 The System shall allow to Customer seller cars based on their interest
 The System shall allow supplier and customer to view the car information.
 The System shall allow Customer and seller can be view the available car with their
description
 The System shall allow view the car information
 The System shall register car with their description
 The System shall allow the seller to upload their information
 The System shall allow generating report.
 The System shall accept the following required information from the user to create
account. Last name, First name, User Name, Password, ID, authentication type (job type).
 The System shall allow the customer to login.
 The System shall allow seller to login.
 The System shall allow head of the registered to delete item.
 The System shall allow users to logoff after the session ends.
 The system shall allow display error messages whenever the user is inserted invalid
username and password.
Page 5
Web based for Fisha car broker system
2.1.3 Nonfunctional requirements

Non-functional requirements are requirements that define the overall qualities or

attributes of the resulting system. Non-functional requirements place restrictions on the
system, the development process, and specify external constraints that the system must
meet. It would not directly concern with specific service delivered by the system to the
users. Constraints on the services or functions offered by the system such as timing constraints,
constraints on the development process, standards. Also include quality of the system

 The system shall run on Window XP, Window 7 and Windo w 8

 The system shall response user request with in 3 second.

 The system shall not fail more than two times per month

 The system shall be familiar to the user within one hour training

Page 6
Web based for Fisha car broker system
2.2 Use case diagram

Car broker system

view car
View Order
delete car
search car

update Car

order car

upload car

comment
costomer

login

logout
Supplier

register supplier

view commment

manager View Report

delete supplier
search supplier

Figure 1 Use case diagram

Page 7
Web based for Fisha car broker system
 List of actor and Use case
 Customer
 View car
 Search car
 Order car
 Comment
 Supplier
 View order
 Upload car
 Update car
 Delete car
 Login
 Logout
 Manager
 Register supplier
 View comment
 View report
 Delete supplier
 Search supplier
 Login
 Logout

Page 8
Web based for Fisha car broker system
2.2.3 Use case description

Table 1 Use case description Login.

Use case name Login

Actor Supplier and manager

Description: The user enters authorized username and password in order to

access the system.

Precondition The user should have username and password.

Basic course of action User action System action

1. Open login page. 2. Display the login page with

login form.
3. Enter the authorized username
and password in the login form. 5. Check the authorized
username and password.
4. Click on logout button
6. If the username and password
8. End use case. is correct login in the system.

Alte rnative course of action 7. If the username and password is incorrect back to step 3, 4 a nd 5
basic course of action.

Page 9
Web based for Fisha car broker system
Table 2 Use case description View Car Information.

Use case name View Car Information

Actor Customer

Description: The customer view information about the car.

Precondition The user must open the car web page.

Basic course of action User action System action

1. Click on car Category 2 .Display the selected car

drop down menu and Category page.
select the car mark like
Toyota, BMW...

3. End use case.

Alte rnative course of action

Page 10
Web based for Fisha car broker system
Table 3 Use case description Register Supplie r.

Register Supplie r
Use case name

Actor Manager

Description: The manager register new supplier in the system.

Precondition The manager must login in the system.

Basic course of action User action System response

1. Login in the system. 3. Display the register supplier

page with register form.
2. Open the register
supplier page. 6. Check all the filled
information.
4. Fill the appropriate
register information on 7. If the filled information is
the form. correct Save the filled
information in the system
5. Click on register database.
button.

9. End use case.

Alte rnative course of action 8. If the form is not filled correctly the system display error
message and back to step4, 5 and 6 of basic course of action.

Page 11
Web based for Fisha car broker system
Table 4 Use case description Upload Car.

Use case name Upload Car

Actor Supplier

Description: The supplier upload car.

Precondition The supplier must login in the system

Basic course of action User action System action

1. Login in the system. 3. Display upload page with

upload car form.
2. Open upload page.
6. If the filled information is
4. Fill the appropriate valid the system uploads the car
information on upload car form. information in the system
database.
5. Click on upload button.

8. End use case.

Alte rnative course of action 7. If the filled information is invalid the system display error
message and back to step 4, 5 and 6 basic course of action.

Page 12
Web based for Fisha car broker system
Table 5 Use case description Delete supplier.

Use case name Delete supplie r

Actor Manager

Description: The manager deletes the supplier’s information.

Precondition The manager must login in the system.

Basic course of action User action System response

1. Login in the system. 3. Display Delete supplier page

with search form.
2. Open Delete supplier page.
6. Searches the saved supplier
4. Enter the supplier Id number information from the system
on the form. database.

5. Clicks on search button. 7. If the supplier information is

found the system displays the
9. Click delete button. privies supplier information with
delete button.
11. Click on yes/no button.
10. The system asks the manager
14. End use case. the correctible of his/her action.

12. If the manager answer is yes

the system delete the supplier
information from the database
and display successful message.
Alte rnative course of action 8. If the supplier information is not found the system displays the
error message and back to step 4, 5 and 6 basic course of action.

13. If the manager answer is no the system back to step 5, 6 and 7

basic course of action.
Page 13
Web based for Fisha car broker system
Table 6 Use case description View comment.
Use case name Vie w comment

Actor Manager

Description: The manager view comments that sanded by customers and supplier.

Precondition The manager must login in the system

Basic course of action User action System action

1. Login in the system. 3. Display the comments page.

2. Open comments page.

4. End use case.

Alte rnative course of action

Page 14
Web based for Fisha car broker system
Use case description View Report.
Use case name Vie w Report

Actor Manager

Description: The manager view Reports order by customers.

Precondition The manager must login in the system

Basic course of action User action System action

1. Login in the system. 3. Display the report page.

2. Open report page.

4. End use case.

Alte rnative course of action

Page 15
Web based for Fisha car broker system
Table 7 Use case description Delete Car.
Use case name Delete Car

Actor Supplier

Description: The Supplier deletes the car information.

Precondition The supplier must login in the system.

Basic course of action User action System action

1. Login in the system. 3. Display Delete car page with

search form.
2. Open Delete car page.
6. Searches the saved car
4. Enter the car Id number, type information from the system
or on the form. database.

5. Clicks on search button. 7. If the car information is found

the system displays the privies
9. Click delete button. car information with delete
button.
11. Click on yes/no button.
10. The system asks the supplier
14. End use case. the correctible of his/her action.

12. If the supplier answer is yes

the system delete the car
information from the database
and display successful message.
Alte rnative course of action 8. If the car information is not found the system displays the error
message and back to step 4, 5 and 6 basic course of action.

13. If the supplier answer is no the system back to step 5, 6 and 7

basic course of action.
Page 16
Web based for Fisha car broker system
Table 8 Use case description Logout.

Use case name Logout

Actor Manager and supplier

Description: When the user logouts when he/she wants to exit from the system.

Precondition The users must login in the system.

Basic course of action User action System action

1. Click on logout button 3. Display the login page.

3. End use case.

Alte rnative course of action

Page 17
Web based for Fisha car broker system
Table 9 Use case description Send comment.
Use case name Send comment

Actor Customer and supplier

Description: The Customer and suppliers ends comment or Feedback about

the car to the manager.

Precondition The Customer and supplier must open the bank web page

Basic course of action User action System action

1. Open the comment page. 2. Display Comment page.

3. Enter his/her name and email 6. Display the

address. acknowledgement message.

4. Enter his/her comment. 7. If the name, email address

and comment correctly filled
5. Click on send button. the system send the comment
to the manager.
9. End use case.
Alte rnative course of action 8. If his/her name or email address is invalid format display error
message and return to step 3, 4 and 5.

9. If he/she does not write comment display error message and

back to step 4, 5 and 6 basic course of action.

Page 18
Web based for Fisha car broker system
Table 10 Use case description Search Supplier.
Use case name Search Supplier

Actor manager

Description: The manager searches the supplier information.

Precondition The manager must login in the system.

Basic course of action User action System action

1. Login in the system. 3. Display the search supplier

page with the search form.
2. Open search page.
6. The system searches supplier
4. Enter the Id number of information from the system
supplier on the search form. database.

5. Click on search button 7. If the supplier information is

found the system display the
9. End use case. supplier information.
Alte rnative course of action 8. If the supplier information is not found the system display an
error message and back to step 4, 5 and 6 basic course of action.

Page 19
Web based for Fisha car broker system
Table 11 Use case description Search Car
Use case name Search Car

Actor customer

Description: The customer searches the car information.

Precondition The customer must login in the system.

Basic course of action User action System action

1. Open search page. 2. Display the search supplier

page with the search form.
3. Enter the Id number of car on
the search form. 6. The system searches car
information from the system
5. Click on search button database.

9. End use case. 7. If the car information is found

the system display the car
information.
Alte rnative course of action 8. If the car information is not found the system display an error
message and back to step 4, 5 and 6 basic course of action.

Page 20
Web based for Fisha car broker system
Table 12 Use case description Update Car
Use case name Update Car

Actor Supplier

Description: The supplier updates the car information.

Precondition The supplier must login in the system.

Basic course of action User action System action

1. Login in the system. 3. Display Update car page with

search form.
2. Open Update car page.
6 Search the car Id on the system
4. Enter the car Id. database.

5. Click on search button. 7. If supplier car Id is found

display the car information with
9. Update the car information. update form.

10. Click on update button. 11. Update the car information.

12. End use case.

Alte rnative course of action 8. If car Id is not found display error message and back to step 4, 5
and 6 basic course of action.

Page 21
Web based for Fisha car broker system
Table 13 Use case description Order Car
Use case name Orde r Car

Actor customer

Description: The customer Order the car.

Precondition The customer must view cars.

Basic course of action User action System action

1. View the car information 3. Displays the car Order page

with the Order form.
2. Click Order Button
6) If the field information is
4. File the appropriate correct send the field
information in the order form. information to supplier and
display successful message.
5. Click on Order button

Alte rnative course of action 7) If the field information is incorrect display error message and
back to step 3, 4, 5 and 6 basic course of action..

Page 22
Web based for Fisha car broker system
2.3 Analysis model

2.3.1 Activity diagram

The Activity diagram can help to describe the flow of control of the target system, such as
exploring complex business rule and operations, describing the user case also the business
process.

Login
AD #1

Open Login page

Enter user name and password

[Incorrect]
The system check user name and password

[Correct]

Successfully Login

Figure 2 Activity Diagram- Login.

Page 23
Web based for Fisha car broker system
 Logout
AD#2

The user clicks the log out button

Logout successfully

Figure 3 Activity Diagram- Logout

Page 24
Web based for Fisha car broker system
 View car information
AD #3

open the car home page

open car information page

Figure 4 Activity Diagram- View Car Information

Page 25
Web based for Fisha car broker system
 Delete supplier
AD#4

Login in the system

Open delete supplier page

Enter the supplier Id number

[Found]

Delete supplier

[Not found]

Ask the correctblity of the manager action

[Yes]

Successfully deletede

Figure 5 Activity Diagram- Delete Supplier Information

Page 26
Web based for Fisha car broker system
 Search supplier
AD #5

Login in the system

Open the search supplier page

[Not found] Fille the Appropriat information in the form

System check the filled information on the database

[Found]

Successfully search

Figure 6 Activity Diagram- Search Supplier Information

Page 27
Web based for Fisha car broker system
 Send comment
AD #6

Open Comment page

Enter his/her Name, Email address and comment on the form

[Not Filled]

The system check the required filleds are filled

[Filled]

The comment send to the manager successfully

Activity Diagram- Send Comment

Page 28
Web based for Fisha car broker system
 Delete Car
AD#7

Login in the system

Open delete car page

Enter the car Id number or type

[Found]

Delete car

[Not found]

Ask the correctblity of the supplier action

[Yes]

Successfully deletede

Figure 7 Activity Diagram- Delete Car

Page 29
Web based for Fisha car broker system
 View comment
AD#8

Login in the system

Open comment page

Read comments

Page 30
Web based for Fisha car broker system
Activity Diagram- View Comment

upload Car
AD#9

Login in the system

Open upload page

[Not found]
Fill the appropriate information on deposit form with car type and id number

[Found]

Enter the upload car

Successfully uploaded

Figure 8 Activity Diagram- Upload Car

Page 31
Web based for Fisha car broker system
 View Riport
AD#8

Login in the system

Open Riport page

Print Riport

Page 32
Web based for Fisha car broker system
 Update Car
AD#10

Login in the system

Opne Update car page

[Not found] Enter car id

[Found]

Update the car information

Successfully update

Figure 9 Activity Diagram- Update Price

Page 33
Web based for Fisha car broker system
 Register Supplier
AD#11

Login in the system

Open the register supplier page

[Not found] Fille the new supplier information on the form

The system checks all information filled correctly

[Found]

New supplier registered successfuly

Figure 10 Activity Diagram- Register Supplier

Page 34
Web based for Fisha car broker system
 Search car
AD #12

Open the search car page

Fille the Appropriat information in the form

[Not found]

System check the filled information on the database

[Found]

Successfully search

Figure 11 Activity Diagram- Search Car

Page 35
Web based for Fisha car broker system
 Order car
AD #13

Open the order car page

Fille the Appropriat information in the form

[Not found]

System check the filled information on the database

[Found]

Successfully ordered

Figure 12 Activity Diagram- Order Car

Page 36
Web based for Fisha car broker system
 View Report
AD#14

login in the system

Open Riport page

manager can see all sold cars

Downloade riport for sold cars

Figure 13 Activity Diagram- Generate Report

Page 37
Web based for Fisha car broker system
 2.3.2 Sequence diagram

Login User<<Actor>> Home page<<UI>> Login page <<UI>> Database

SD #1

Open ()
{The user open login page}

Enters user name and passwordl ()

{Enter user name and password}

{The system found the user name and password Search()

and the role of user}

[If found]Open()
{If the user name and password found open home page}

{If not found try again}

[Not found]Try again()

Figure 14 Login sequence diagram

Page 38
Web based for Fisha car broker system
 Send comment
SD #2 Customerr<<actor>> Home page<<UI>> Comment<<UI>> Database

Open()
{The customer open home page} Open()

Fill form()
{Fill his/her name,email address and
coment/feedback}

{If the customer fill correctlly [If correct]Send()

the comment send to database}
[If incorrect]try again()

{If the customer not fill correctlly

try again}

Figure 15 Send comment sequence diagram

Page 39
Web based for Fisha car broker system
View information
SD #3

Customer<<actor>> Home page<<UI>> Car information page<<UI>>

Open()
{Open home page}
Open()
{Open Car information page}

View information sequence diagram

Page 40
Web based for Fisha car broker system
 Update Car
SD #4 Supplier<<Actor>> Home page<<UI>> Update price<<UI>> Database

Login()
{The Supplier login in the system}

{Open update car page} Open()

Fill form()
{Enter car id}

{The system search the filled information} Search()

{If the filled information found

display the updat car} [If found]display update form()

{The supplier update the car} Update()

Chenge()
{The system chenges the information}
[If not found]try again()
{If the filled information not found try again}

Figure 16 Update price sequence diagram

Page 41
Web based for Fisha car broker system
 View comment
SD #5
Manager<<Actor>> Home page<<UI>> View comment<<UI>>

Login()
{The manager login in the system}
Open()
{Open view comment page}

Figure:- View comment sequence diagram

Page 42
Web based for Fisha car broker system
 Register Supplier
SD#6

manager<<Actor>> Home page<<UI>> register supplier<<UI>> Database

{The Manager Login()

login in the system}

Open()
{Open register supplier page}

Fill form
{Fille the appropriat information
on the form}
{The system check the filled Check()
information}

{If the filled information

is correct save the information [If correct]Save()
in system database}
{If the filled information [If incorrect]try again()
is incorrect the system displaye
error message}

Figure 17 Register supplier sequence diagram

Page 43
Web based for Fisha car broker system
Figure 19:-Delete supplier sequence diagram

Delete supplier
SD#7

manager<<Acter>> homepage<<UI>> delete supplier<<UI>> database

Login()
{The manager Login in the system}
Open()

{Open delete supplier page}

Fill form()
{Enter supplier id number}
Search()

{The system search suplier id number}

[If found]Display supplier information()
{If the supplier information found
display supplier information}

Delete()
{click on delete button}
Delete()
{The system delete on the database}

{If not found display error [If not found]try again()

message and try again}

Page 44
Web based for Fisha car broker system
Figure 20:view comment sequence diagram

View comment
SD #5
Manager<<Actor>> Home page<<UI>> View comment<<UI>>

Login()
{The manager login in the system}
Open()
{Open view comment page}

Page 45
Web based for Fisha car broker system
Figure 21:-Search supplier sequence diagram

Search supplier
SD#9 manager<<Actor>> hompage<<UI>> search page<<UI>> database

Login()
{The manager login in the system}

Open()
{Open Search page}
Fill form()
{Enter supplier Id number}
Search()
{The system search supplier information}
[If found]Display supplier information()
{If the supplier information found
displaye the supplier information}

[If not found]try again()

{If not found try again}

Page 46
Web based for Fisha car broker system
Figure 22:-Delete car sequence diagram

Delete Car
SD#10

supplier<<Acter>> homepage<<UI>> delete car<<UI>> database

Login()
{The supplier Login in the system}
Open()

{Open delete car page}

Fill form()
{Enter car id number or type}
Search()

{The system search car id number or type}

[If found]Display car information()
{If the car information found
display car information}

Delete()
{click on delete button}
Delete()
{The system delete on the database}

{If not found display error [If not found]try again()

message and try again}

Page 47
Web based for Fisha car broker system
Figure 23:-Upload car sequence diagram

upload Car supplierr<<Actor>> Home page<<UI>> upload page<<UI>> Database

SD#11

{the supplier login to the system} Login()

Open()
{open the upload page}

{Enter the appropriat information in the form Fill the form

and upload the car image}
upload

Page 48
Web based for Fisha car broker system
 CHAPTER THREE

3.1 System Design

3.1.1 Deployment Diagram

A Deployment Diagram depicts how the deployable units of the system applications,
components, and data stores are assigned to various nodes, as well as how the nodes
communicate with each other and with devices. It’s useful both as a map of your system and as a
means for studying the load across your System.

Server Applicatio

Web Browser
HTTP
Fisha Car Broker
Firefox
System

Appache
CometBird
MySQL

Google Chrom

Opera Mini

JDBC

Device

Printer

Figure 18 Deployment Diagram

Page 49
Web based for Fisha car broker system
3.1.2 Architectural Design
It is the architecture that determines the type of interactions that the components are going to
have. The architecture that this work uses is client/server based architecture. In this type of
architecture the server is responsible to receive a request from the client and respond to the
request, whereas the client is responsible to interact with that of the users of the system. The
server parts of this work are of two types. The first type is a web server, which is responsible to
receive browsers’ request through http protocol and responds accordingly. Whereas the second
type of server is a database server, which is responsible to provide the requested database
services to the web server. The database server is generally responsible for modification and
insertion of data to the database. It can only communicate with the web server. The client side is
web browser and printer. The web browser which receives requests from the user of the system
and responds to the request by communicating with the web server. The printer used to print the
send and the deposit information to customers. If the user has a request on data, the browser
passes the request to the web server then the web server pass the request to the database server.

Page 50
Web based for Fisha car broker system
 Browsers
Printer

Internet
HTTP

Database

MySQL

Web Server

Apache

Page 51
Web based for Fisha car broker system
3.1.3 Class diagram

Person
-Lname : string
-Fname : string
-Address : string
-Sex : char
-PhoneNO : string
-ID : string
-Account : string

Supplier Search, Register, Delete

-UserName : string 1..*

1..1
-Password : string
+Search()
Customer +Update() Manager
+Upload() -UserName : string
+comment() -Passwod : string
+Comment()
+Order()
+Generate Repo()
+Search() 0..1
1..* 1..1 +view()
+View()
+Search()
Upload, Delete, Update Price.

0..1 +Delete()
0..* +Register() 1

Send Send Has Has

1
0..1
Login
Comment -Type : string
-Time to contact : string 1..1
-Password : string
-Massage : string -UserName : string
-Name : string Car -Role : string
-Email : string
0..1 -Price : float
-Brand : string
-Marck : string
1..*
-CarID : string
-Address : string
1..*

Order, Search View

0..*

Figure 19 Class diagram

Page 52
Web based for Fisha car broker system
3.2 User Interface (UI) Design

User interface 1 Home

Page 53
Web based for Fisha car broker system
User interface 2 Login form

Page 54
Web based for Fisha car broker system
User interface 3 Register supplier

Page 55
Web based for Fisha car broker system
User interface 4 User view Toyota car

Page 56
Web based for Fisha car broker system
User interface 5 user write comment

Page 57
Web based for Fisha car broker system
User interface 6 View comment

Page 58
Web based for Fisha car broker system
User interface 7 View report

Page 59
Web based for Fisha car broker system
3.3 Algorithm Design

Pseudo code is one type of representation method by using English like structure. In this part I
try to represent some algorithm of the operations which listed in class diagram by using English
like structure Pseudo code.

 Pseudo code for Search car

Variable (plateNo)

If(variable is valid)

Then

Available car Displayed

Otherwise

Displays “There is no such car”

Endif

End

 Pseudo code for Suppliers registration

Method name = register Suplier

Begin

Variables (SupId, SupfName, SuplName, sex,age, address,Account, phoneNo)

If(variables are valid)

Then

Page 60
Web based for Fisha car broker system
Display”Successfully registered”

Otherwise

Displays “invalid inputs”

Endif

End

 Pseudo code for login

Method name = login

Begin

Variables (username, password)

If(variables are valid)

Then

“New page displayed”

Otherwise

Displays “invalid inputs”

Endif

End

Page 61
Web based for Fisha car broker system
 Bibliography

 James Rumbaugh, Irar Jacobson, Grady Booch. December 1998.unified modeling language
reference manual. Harlow: England
 Wiki books .about the system analysis and design. Retrieved from.
http://en.wikibooks.org/wiki/Systems_Analysis_and_Design/Introduction
 Introduction to software development .About sequence diagram retrieved from.
http://www.visual-paradigm.com/solution/sequencediagram/
 Software development and professional practice. About ER diagram retrieved
from.http://creately.com/blog/diagrams/er-diagrams-tutorial/

Appendix A

Some Questions that asked during requirement gathering by interview.

1. How and when your organization established?
2. What is the objective of this organization?
3. What is mission and vision of your organization?
4. Who are the users of this organization?
5. Is the users of your organization has category?
6. If yes what is the role of each categories?
7. How does the current system works?
a. Is it manual?
b. Is it computerized?
c. Is semi computerized?
8. What are the procedures or steps involved when customers to buy car?
9. What is rule or qualification that your organization expect from the customers?

Page 62
Web based for Fisha car broker system
 Conclusion
This document states the design level approach for the project fisha car broker system. After
giving basic information about what the system is, the document briefly describes the problem
and the solution of the system to visualize better understanding for system developer. In other
words this document introduces the technical details of fisha car broker system..

In the first part of the document, the major functions needed to develop a car broker system. are
stated. Later on, these major functions and their sub-functions are visualized with the use case
diagrams. Finally user interfaces are described.

Page 63
Web based for Fisha car broker system