Part of My Graduation Project

-1-
GazaAl Azhar University
FACULTY OF ENGINEERING AND

INFORMATION TECHNOLOGY
FINAL FYP I REPORT
ELECTRONIC MARKET WEBSITE
MOTASEM MOHAMMED KURRAZ

-2-
Chapter 1
Introduction
1.1 Introduction.
1.2 Definition.
1.3 The project's description.
1.4 Customers features.
1.5 Companies features.
1.6 Project objectives.
1.7 Project's requirements.
1.8 Time table for project stages.
-3-
1.1 Introduction:
E-markets have been a topic of high interest in the academic

community during the past twenty years. In other point, The
Internet has quickly become one of the most popular port key
for products advertising and market trade resources. As a link to
the global community, it has revolutionized the way traders
could join and set commerce deals.
So unlike traditional methods which are usually restricted by

the everyday public centers and personally presence in markets
to set up commerce deals, Online trading have current and
active databases that cover all categories and items of several
shops and markets in a specific region.
Online trading sites have passed the issue of landscape for

both buyer and the market owner seller. These sites allows for
immediate real-time interaction and 24 x 7 shopping and trading
activity.
The market owner can post an item in as little as 20 minutes

on an online market site and start receiving orders in response
immediately. Typically, electronic market is not only much
faster on average 70% than traditional trading methods, Also
Costs less for either the market owner to advertise his own
business individually by traditional methods or for the buyer that
goes shopping in traditional way.
On the other hand with online trading sites, buyer customers

are able to access item lists and product categories of several
markets in locations they may not otherwise have learned of
and can reach them immediately with the click of a mouse.
-4-
1.2 Definition:
Our project's idea can be defined as an interface between

goods, market owners and the customers who are looking for
a these goods to make their orders.
The idea is to make a database that includes main

information about brand items and the commerce operation
members either buying customers or selling companies and
sort them in a suitable way to make the operation easier and
faster.
Our website Converts usual commerce operation in to an

interesting process, and helps all sides of this operation to
have their specific aim of it.
Also produces services for Customers by enabling them

to browse goods and categories , search item lists and make
orders in easiest and fastest way.
Our website also produces an advertising area where the

member could display an advertising banner for a symbolic
price.
1.3 The project's description:
The website allows companies (Market Owners) to post their

items lists and products in public for a percentage fee for orders
implemented through this site, Also allows customers to order
items through the website and pay for each of their orders
separately.
The website also have an advertisement area for people who

wants to publish their advertisements in a good commerce vista
and make those advertisements become more viewable and
common for the public.
-5-
1.4 Customers features:
People who browse the site in order to buy items displayed

on it and to register they need :
An interface that will help them to register by adding
their personal information.
Online personal profile update that will help them also
to edit their personal information if they found
something wrong or update if they want to add new
information.
Search item listings that will make the ordering
operation more easier for them by searching in specific
lists and categories for items which will save time and
effort.
Automatic access upon registration when the customer
finish the registration and write all the needed
information the site will automatically open all the
available items and categories that is listed in the site .
1.5 Companies features:
People who announce for their markets and goods in our

website so they can find buyers for their services and to register
they need:
Items posting interface that will help them to post their
offered item lists in the item categories and.
Online item and item lists edit that will help them to
rewrite the information if they found they have posted
something wrong and if they want to add new
information and items to their lists.
Online personal profile update that will help them also
to edit their personal information if they found
something wrong or update if they want to add new
information.
Postings and searches which means that they
announce for their markets and searching for good
buyers in the same time.
-6-
1.6 Project objectives:
The project main objectives are:

Make commerce operation more easier and specific.
Make announcements for goods and items more easier
and specific.
Matching between customers and commerce deals will
be the main purpose of our project.
Finding the best offers among various companies and
markets that are selling items that allows the customer
to have more choices for even items or prices.
Providing a very good commerce vista for market
owners and companies to post their services and
advertisements in.
Provide fixable user interface to make marketing more
easily.
The ability to search in the database for a specific
product or specific company.
Provide sufficient information about the product is
supported by picture.
Build a categorized product portfolio with high quality
products.
Succeed together with our Business Partners.
Reduce the Shopping Time for the customer with the
nowadays quick life style.
-7-
Chapter 2
System analysis and design
2.1 Reviews of related literatures & applications
2.2 Business requirements
2.2.1 Business actor list
2.2.2 Glossary
2.2.3 Business use case list
2.2.4 Business use case details
2.2.5 Business use case communication diagrams
2.2.6 Business use case activity diagrams
2.3 System requirements
2.3.1 Functional requirements
2.3.2 Non functional requirements
2.3.3 System actor list
2.3.4 System use case list
2.3.4.1 Visitor use case list
2.3.4.2 Customer use case list
2.3.4.3 Company use case list
2.3.4.4 Advertiser use case list
2.3.4.5 Assistant use case list
2.3.4.6 Administrator use case list
2.3.5 System use case details
2.3.5.1 Visitor use case details
2.3.5.2 Customer use case details
2.3.5.3 Company use case details
2.3.5.4 Advertiser use case details
2.3.5.5 Assistant use case details
2.3.5.6 Administrator use case details
2.3.6 System use case survey
2.3.7 Use case diagrams
2.3.8 Communication diagrams
2.3.9 Sequence diagrams
-8-
2.4 User interface sketches
2.1 Reviews of related literatures & applications

Electronic markets are defined according to the traditional
market paradigm defines it : it is the structure that coordinate the
flow of materials or services, through supply and demand forces,
as well as through external transactions between different
individuals and firms.
Market forces determine the design, price, quantity and
target delivery schedule for a given product, which will serve as
input into another process.
Then we could obtain that The definition of electronic
markets has been initially based on the characteristics of traditional
markets.
In the influential paper of 'Malone et al' (1987), the buyer of
the good or service compares its many possible sources, and
makes a choice based on the best combination of these attributes.
Another prevailing definition, which has a more technological
focus, was given by 'Bakos' (1991) that said : an electronic market
place is an organizational information system that allows the
participating buyers and sellers to exchange information about
prices and product offerings.
As 'Bakos' (1991) notes, this definition of e-markets has a
narrower, System oriented focus in comparison to the more
general definition of 'Malone et al' (1987) which refers to an e-
market as the corresponding governance mechanism.
Main Classification of Electronic commerce
First Classification
1. Electronic commerce that is conducted between
businesses is referred to as business-to-business or B2B,
B2B can be open to all interested parties (e.g. commodity
exchange) or limited to specific, pre-qualified participants
(private electronic market).
2. Electronic commerce that is conducted between
businesses and consumers, on the other hand, is referred
to as business-to-consumer or B2C, This is the type of
-9-
electronic commerce conducted by companies such as (

Amazon.com ).
3. Electronic commerce that which allows consumers to sell
goods to other consumers Consumer-to-Consumer or
C2C Example of a C2C is e-bay ( http://www.ebay.com ) .
Second Classification
1. Buyer-oriented : which e-markets mainly aggregate
buyers, allowing them to also aggregate their expenditure,
to reduce administration costs, to facilitate global
sourcing. Example of a buyer-oriented e-market is On
Sale (http://www.onsale.com) .
2. Seller-oriented : which e-markets concentrate on bringing
multiple sellers together into a central catalogue and
product information repository, in order to allow them
achieve higher visibility and conduct trade with as many
buyers as possible. Examples of seller-oriented e-markets
include aggregators such as e-steel (http://www.e-
steel.com).
Electronic commerce is generally considered to be the sales

aspect of E-business. It also consists of the exchange of data to
facilitate the financing and payment aspects of the business
transactions.
Online shopping is a form of electronic commerce where the buyer
is directly online to the seller's computer usually via the internet.
There is no intermediary service So The sale and purchase
transaction is completed electronically and interactively in real-time
such as Amazon.com for new books. If an intermediary is present,
then the sale and purchase transaction is called electronic
commerce such as (eBay.com ) .
- 10 -
1.2 Business requirements
1.2.1 Business actor list
Buyer: The person who has money and wants to buy

commodity.
Seller: The supplier who owns the goods and wants to sell
them.
Accounting department: The staff of employees take the
products fees and the price of procurement and performs
accounting operations.
Marketer: Is the person who wishes the buyer to buy
commodity and also gives buyer the information about
commodity.
Department manager: The person who is responsible for
specific part of the center such as department of clothes
and department of electronics.
General manager: Person who prepares and develops
plans for the shopping center also supervises on
operations in the accounting department and other
departments.
Coordinator: Person who helps customer to find what they
want.
- 11 -
1.2.2Glossary
E-Market Glossary
Term Definition
Catalog (Business object) Contains description about the product and

goods in the shopping center and it may be
contain the price of those items and products .
Commodity (Business object) The product and good available in the shopping
center and the customer wants to get this
product.
Department Manager The shopping center is divided into many

(Business object, Business department such as department for clothes and
actor) department for electronics and for each of these
departments there is a manager who's
responsible for this department and all operations
happens within it.
Advertisement(Business The activity of attracting public attention to a

object) product or business ,this advertisement may be
in the radio or TV or newspaper or other media.
Shopping Cart (Business The products and goods bought by the customer
object) from the shopping center.
Accountant (Business object, The accounting employee who manages

Business actor) accounting.
Invoice of Purchasing Calculation of the number of items and the price

(Business object) of each item and the total price of all item.
1.2.3 Business Use Case List

B1: Sell commodity: Buyer choose commodity and ask for
details and price of this commodity from coordinator after
that he pays money for accounting department.
B2: The purchase transaction: This transaction done by
the general manager of shopping center that is between
him and the supplier of commodity to provide the center
with the needs of the buyer.
- 12 -
B3: Prepare invoice of purchasing: This invoice is prepared

for buyer After he pays for the product at accounting
department that shows number of items and the price of
each one and the total price .
B4: Preparation invoice of sales: This invoice is prepared
for the department manager every end of the day by the
accountant department , that shows sales in the current
day and Explains to the manager number of items sold
from the market.
B5: Promotion of goods: This task is done by marketer to
describe the product for the buyer and to show him the
advantages of it.
B6: Determine the sales prices: After the general manager
is done with the purchase transaction of the supplier that
determine the price of Each item.
B7: Inventory of stock: This task takes place once every
specific period done by accountant to determine the
number of items that have been sold from the shopping
center and the items in the stoke .
B8: Determine the shopping center needs: This task done
by department manager after the end the day the
coordinator determine the available commodity and others
which are not available and which is needed in shopping
center.
B9: Recording purchases and sales: The accountant
makes record for every commodity bought or sold from
shopping center.
B10: General manager identify jobs and tasks: The general
manager in the shopping center identifies the duties of
each employee in the center and tasks of him for and also
determines the salary for each employee, And monitors
the performance of the functions of every employee in the
center as well.
B11: The discount on invoice of purchasing: After the
buyer buys commodity and goes to the accountant
department to pay for it, It is checked if the price of
commodity satisfies the terms of discount, And if it does
- 13 -
the accountant makes discount for the invoice in

purchasing of this buyer.
B12: Receiving the goods: Coordinator receives the goods
that general manager bought for shopping center and
distribute it in specific departments thought out in shopping
center.
B13: Distribute product: when other markets or restaurants
want to buy some commodity from the shopping center,
The coordinator prepares their orders, And the distributer
conducts this orders to these markets or restaurants.
1.2.4 Business use case details
B11: The discount on invoice of purchasing.

1. Buyer explains to the coordinator which type of
commodity he wants.
2. Coordinator shows the buyer in which department he
could find this commodity.
3. Buyer selects the specific commodity he wants from the
department in shopping center and put it in the shopping
cart.
4. Buyer goes to the accounting department to pay the fees
of purchasing.
5. Accountant determines the purchases for buyer and the
price of this purchase.
6. Accountant makes the invoice of purchasing.
7. Accountant checks the invoice of purchasing If it satisfies
the discount terms, Accountant makes discount and if it
doesn't satisfy the discount terms he dont change
anything.
8. Buyer takes the invoice of purchasing and pays the
purchasing fees.
B13: Distribute product.

1. The manager receives calls from markets or restaurants
explaining order they want.
2. The manager asks the coordinator to find out if this order
is available in the shopping center or not .
- 14 -
3. If the order is found and available, the coordinator

prepares the order.
4. The accountant makes invoice of purchasing for this
order.
5. The distributer conducts this order to ordered market or
restaurant.
6. The distributer takes fees of the order from the market or
restaurant.
7. If the order is not available in the shopping center the
manager cancels the contacts the market or restaurant
and cancels it.
1.2.5 Business use case communication diagrams
1.2.5.1 Communication diagram for use case B11:
Figure 2.2.5.1: Communication diagram for use case B11: The discount on Invoice of Purchasing.
1.2.5.2 Communication diagram for use case B13:
Figure 2.2.5.2: Communication diagram for use case B13: Distribute product.
- 15 -
1.2.6 Business use case activity diagrams

1.2.6.1 Activity diagram for use case B11:
Figure 2.2.6.1: activity diagram for use case B11: the discount on Invoice
Purchasing.
- 16 -
1.2.6.2 Activity diagram for use case B13: Distribute product
Figure 2.2.6.2: Activity diagram for use case B13: Distribute product
- 17 -
1.3 System requirements:

1.3.1 Functional requirements
System helps the customer to do his own shopping in a
appropriate and quick manner.
System helps the market owner to do selling and advertising
for his market and product items in an appropriate manner.
System helps the web members to join one to three mail list.
System helps the users of the web to view advertisements,
market categories and items.
System helps users of the web to access help and support
reports.
Communication between users with administrator should be
reliability and done correct.
Help tools that is available to the administrator managing ,
should be efficient.
The system must authorize each user according to his
permission.
The system should provide correct information for each user
and administrator.
The system must authenticate each user can access to the
system.
The system should response in reality way to particular
request from client with correct result (under specification of
system).
1.3.2 Non-Functional Requirement:

Availability: this system is available and accessible on 24*7
with achieved performance.
Reliability: this system keeps the consistency and
integration of every transaction.
Manageability: it offers the ability to manage the resources
of the system to allow availability
Flexibility: the ability to add new items, markets and
advertisements .
Capacity: the system able to operate many tasks and many
user transaction at one time.
- 18 -
Security: The ability to prevent an unauthorized user to

access data, also provides authentication to limit user with
some permissions.
Maintainability: the system will be able to be maintained
and developed in the future and technical support is
available.
Cost: It is low by compare with previous traditional with cost,
time and effort.
Accuracy: The accuracy will be very high because of the
computerized system.
Usability: It is available anytime and anywhere.
1.3.3 System actor list

Visitor : Is the person how views 'O6lob' website without
being a member.
Customer : Is the person who registered for a membership
to be able to make shopping orders through 'O6lob' website .
Company : Is the person who registered for a membership
to be able to present his services through 'O6lob' website .
Advertiser : Is the person who registered for a membership
in 'O6lob' website in order to post an advertisement .
Assistant : Is the coordinator of 'O6lob' website.
Administrator : Is the owner of 'O6lob' website, He is the
person who can enter to administrator's page that allows him
to use 'O6lob' websites control panel to do anything in the
website.
1.3.4 System use case list

1.3.4.1 Visitor use case list
U1. Visitor registration.
U2. Visitor view category.
U3. Visitor view item.
U4. Visitor view company.
U5. Visitor search for item ,company.
U6. Visitor read about us.
U7. Visitor read help & support.
- 19 -
U8. Visitor view contact us.

U9. Visitor send E-Mail to website assistant.
U10. Visitor view posted advertisement.
U11. Visitor view vote.
1.3.4.2 Customer use case list

U1: Customer log in the system by user name and
password.
U2: Customer log out.
U3: Customer view personal profile.
U4: Customer add personal information.
U5: Customer update personal information.
U6: Customer add delivery address.
U7: Customer remove delivery address.
U8: Customer view order.
U9: Customer add order.
U10: Customer remove order.
U11: Customer edit order.
U12: Customer charge order balance.
U13: Customer choose order delivery address.
U14: Customer submits purchase order.
U15: Customer view category.
U16: Customer view item.
U17: Customer view company.
U18: Customer search for item ,company.
U19: Customer read about us.
U20: Customer read help & support.
U21: Customer view contact us.
U22: Customer send E- Mail to the website assistant.
U23: Customer view posted advertisement.
U24: Customer view vote.
U25: Customer vote.
1.3.4.3 Company use case list

U1: Company log in the system by user name and
password.
U2: Company log out.
- 20 -
U3: Company view personal profile.

U4: Company add personal information.
U5: Company update personal information.
U6: Company add item list.
U7: Company view item list.
U8: Company add items to item list.
U9: Company update item list.
U10: Company remove item list.
U11: Company view purchases.
U12: Company view category.
U13: Company view item.
U14: Company view company.
U15: Company search for item ,company.
U16: Company read about us.
U17: Company read help & support.
U18: Company view contact us.
U19: Company send E- Mail to the website assistant.
U20: Company view posted advertisement.
U21: Company view vote.
U22: Company vote.
1.3.4.4 Advertiser use case list

U1: Advertiser Log in the system by user name and
password.
U2: Advertiser Log out.
U3: Advertiser view personal profile.
U4: Advertiser add personal information.
U5: Advertiser update personal information.
U6: Advertiser view advertisement list.
U7: Advertiser request to add advertisement.
U8: Advertiser request to remove advertisement.
U9: Advertiser view category.
U10: Advertiser view item.
U11: Advertiser view company.
U12: Advertiser search for item ,company.
U13: Advertiser read about us.
U14: Advertiser read help & support.
- 21 -
U15: Advertiser view contact us.

U16: Advertiser send E- Mail to the website assistant.
U17: Advertiser view posted advertisement.
U18: Advertiser view vote.
U19: Advertiser vote.
1.3.4.5 Assistant use case list

U1: Assistant log in the system by user name and
password.
U2: Assistant log out.
U3: Assistant view personal profile.
U4: Assistant add personal information.
U5: Assistant update personal information.
U6: Assistant view pending orders in system.
U7: Assistant remove implemented orders.
U8: Assistant remove expired orders in system.
U9: Assistant send un-implemented order notification to
customer.
U10: Assistant view company account balance.
U11: Assistant view pending advertisement list.
U12: Assistant post pending advertisement.
U13: Assistant reject pending advertisement.
U14: Assistant view posted advertisement.
U15: Assistant remove posted advertisement.
U16: Assistant send E-mail to user (Customer ,Company
,Advertiser ,Administrator).
U17: Assistant view category.
U18: Assistant view item.
U19: Assistant view company.
U20: Assistant make several searches in system ( Item, ).
U21: Assistant read about us.
U22: Assistant read help & support.
U23: Assistant view contact us.
U24: Assistant view vote.
U25: Assistant vote.
1.3.4.6 Administrator use case list

- 22 -
U1: Administrator log in the system by user name and

password.
U2: Administrator log out.
U3: Administrator update own account.
U4: Administrator approve pending users in system.
U5: Administrator view user's personal profile in system.
U6: Administrator remove user from system.
U7: Administrator view category.
U8: Administrator add category.
U9: Administrator update category.
U10: Administrator view item.
U11: Administrator view item list.
U12: Administrator update item list.
U13: Administrator remove item list.
U14: Administrator make backup
U15: Administrator restore database.
U16: Administrator view pending orders in system.
U17: Administrator remove implemented orders.
U18: Administrator remove expired orders in system.
U19: Administrator send un-implemented order notification
to customer.
U20: Administrator view company account balance.
U21: Administrator view pending advertisement list.
U22: Administrator post pending advertisement.
U23: Administrator reject pending advertisement.
U24: Administrator view posted advertisement.
U25: Administrator remove posted advertisement.
U26: Administrator add about us article.
U27: Administrator update about us article.
U28: Administrator view about us article.
U29: Administrator add contact us information.
U30: Administrator update contact us information.
U31: Administrator view contact us information.
U32: Administrator add help & support reports.
U33: Administrator update help & support reports.
U34: Administrator view help & support reports.
U35: Administrator add voting question.
- 23 -
U36: Administrator update voting question.

U37: Administrator view voting question.
U38: Administrator send E-mail to User (Customer,
Company, Advertiser, Assistant).
U39: Administrator Make several searches in system (Item,
User, ).
1.3.5 System use case details

1.3.5.1 Visitor use case details
V1: Visitor registration.

Use case name Registration.
Participate actor Visitor.
Flow of events 1. Visitor runs registration instruction.
2. System represents a form containing some fields (user name,
password, phone number, e-mail, country and city).
3. Visitor chooses from a list what kind of user to be registered as
(Customer , Company, Advertiser).
4. Visitor fills required fields and submits.
5. System checks the submitted information.
6. System adds inserted data to database if there are no problems.
7. System acknowledges the Visitor.
Entry condition Visitor accesses the registration page.
Exit condition Visitor received an positive acknowledgement, or an explanation
indicating why the transaction could not be processed.
V2: Visitor view category.

Use case name View category.
Flow of events 1. Visitor runs access category page instruction.
2. System checks category table in data base for the required data.
3. System presents a drop down list that contains categories.
4. Visitor choose category from the list.
5. System transfers Visitor to the category's page.
Entry condition Visitor access view category page.

Exit condition Visitor received an acknowledgement or an explanation indicating why
the transaction could not be processed.
V3: Visitor view item.

- 24 -
Use case name View item.

Flow of events 1. Visitor runs access items page instruction.
2. System transfer Visitor to items page.

3. Visitor choose an item from the list.
4. System checks information from item table in the data base.
5. System represents a form contains item's information.
Entry condition Visitor access view item.
Exit condition Visitor received an acknowledgement, or an explanation indicating why
V4: Visitor view company.

Use case name View company.
Flow of events 1. Visitor runs access companies page instruction.
2. System transfer Visitor to companies page.
3. Visitor chooses a company from the list.
4. System transfer Visitor to the chosen company's page.

Entry condition Visitor access view company page.
V5: Visitor search for item ,company.

Use case name Search for item.
Flow of events 1. Visitor runs search instruction.
2. System presents a field and drop down list contains search type
(item, company).
3. Visitor fills out the field and select search type (item).
4. System checks the field and reply with a notification if anything

goes wrong.
5. System checks if the search key is in the item table in database.
6. System gets data from item table.
7. System presents a form contains item's information.
Entry condition Visitor access search page.

Use case name Search for company.

- 25 -
Flow of events 1. Visitor runs search instruction.
(item, company).
3. Visitor fills out the field and select search type (company).

goes wrong.
5. System checks if the search key is in company table in database.
6. System transfers Visitor to Company's page.
Entry condition Visitor access search page.

V6: Visitor read about us.

Use case name Read about us.
Flow of events 1. Visitor runs read about us instruction.
2. System checks about us table for the required data.
3. System represents a form containing the required about us.
Entry condition Visitor access view about us page.
V7: Visitor read help & support.

Use case name Read Help & Support.
Flow of events 1. Visitor runs help & support instruction.
2. System checks help & support table for the required data.
3. System represents a form containing the required help & support.
Entry condition Visitor access the Help & Support page.

V8: Visitor view contact us.

Use case name View contact us.
Flow of events 1. Visitor runs contact us instruction.
2. System checks contact us table for the required data.
3. System represents a form containing the required contact us
information.
Entry condition Visitor access view contact us page.
V9: Visitor send E-Mail to website assistant.

- 26 -
Use case name Send E-Mail to website assistant.

Anticipated actor Visitor.
Flow of events 1. Visitor runs contact site's assistant instruction.
2. System presents a form containing some fields (sender e-mail, subject,

message details).
3. Visitor fills out the required fields and submits.
4. System checks for assistant's e-mail address is in email table in

database.
5. System send message to the assistant's address.
6. Visitor receives an acknowledgement.
Entry condition Visitor access contact site's assistant page.

V10: Visitor view posted advertisement.

Use case name View posted advertisement.
Flow of events 1. Visitor runs access advertisement page instruction.
2. System transfer Visitor to advertisement page.
Entry condition Visitor access view advertisement page.

V11: Visitor view vote.

Use case name View vote.
Anticipated actor Visitor.
Flow of events 1. Visitor runs access vote page instruction.
2. System transfer Visitor to vote page.
Entry condition Visitor access view voting.

2.3.5.2 Customer use case details

C1: Customer log in the system by user name and password.
Use case name Log in.
Anticipated actor Customer.
Flow of events 1. Customer accesses the website.
2. System replies by showing the login form containing two fields (user
name, password).
3. Customer fills the required fields (user name, password) and submits.
- 27 -
4. System checks if the submitted information (user name, password) are

right according to Customers information in the database.
5. System acknowledges the Customer.
6. System transfers Customer to the website home page.
7. System starts Customers session.
Entry condition Customer accesses the website.
Exit condition Customer received an acknowledgement, or an explanation indicating
why the transaction could not be processed.
C2: Customer log out.

Use case name Log out.
Flow of events 1. Customer runs logout instruction.
2. System removes all permissions from the Customer.
3. System acknowledges Customer that he has been logged out.
4. System ends Customers session.
5. System transfers Customer to the website login page.
Entry condition Customer runs log out.
C3: Customer view personal profile.

Use case name View personal profile page.
Flow of events 1. Customer runs access personal profile page instruction.
2. System transfer Customer to personal profile page.
Entry condition Customer accesses personal profile page.

C4: Customer add personal information.

Use case name Add personal information.
Flow of events 1. Customer runs personal information instruction.
2. System represents a form with some fields (First name, Last name,
gender, Date of birth, mobile phone, phone number, country, city, marital statues).
3. Customer fills the required fields and submits.
4. System checks the entered information .
5. System adds data to the database if there are no problems.
6. System acknowledges Customer that his information has been

submitted.
7. System transfers Customer to the personal profile page.

- 28 -
Entry condition Customer accesses add personal information page.

Exit condition Customer received an acknowledgement, or received an explanation
indicating why the transaction could not be processed
C5: Customer update personal information.

Use case name Update personal information.
Flow of events 1. Customer runs personal information instruction.
2. System represents a form with some fields (First name, Last name, and
gender, Date of birth, mobile phone, phone number, country, city, marital status).
3. Customer edits fields and submits.
4. System checks the information if there are no problems.
5. System overwrites data in data base.
6. System acknowledges Customer that his information has been

updated.
Entry condition Customer accesses update personal information page.

why the transaction could not be processed
C6: Customer add delivery address.

Use case name Add delivery address information.
Flow of events 1. Customer runs delivery information instruction.
2. System represents a form with some fields (Delivery address #1 ,

Delivery address #2 , ).
3. Customer fills fields and submits.
5. System adds data to data base.
6. System acknowledges Customer that his delivery address

information has been added.
Entry condition Customer access add delivery address information page.

C7: Customer remove delivery address.

Use case name Remove delivery address information.
- 29 -
Flow of events 1. Customer runs delivery information instruction.

2. System represents a form with some fields (Delivery address #1 ,
Delivery address #2 , ).
3. Customer edits fields and submits.
4. System checks the information if there is at least one address
listed & and if there are no problems.
6. System acknowledges Customer that his delivery address
information has been updated.
7. System transfers Customer to the personal profile page..
Entry condition Customer access remove delivery address information page.
C8: Customer view order.

Use case name View order.
Flow of events 1. Customer runs access order's page instruction.
2. System transfer Customer to order's page.
Entry condition Customer access view order page.

C9: Customer add order.

Use case name Add order.
Flow of events 1. Customer runs add order instruction.
2. System represents a form contains a list of companies registered

in system and their item lists includes items (in check boxes) that is all
distributed among item categories .
3. Customer choose wanted items and submits.
4. System checks the information submitted.
5. If there aren't any problems, system acknowledges Customer that

his order has been submitted.
6. System inserts data to the database.
7. Customer received an acknowledgement explains order & it's total

balance.
Entry condition Customer access add order page.

C10: Customer remove order.

- 30 -
Use case name Remove order.

Flow of events 1. Customer runs remove order instruction.
2. If there aren't any problems, System checks that the order is in the
data base.
3. System represents a form containing the order's information.
4. Customer removes the order and submits.
5. System removes the order from order table in the data base and
acknowledges Customer that his order has been removed.
6. System transfers Customer to website home page.
Entry condition Customer access remove order page.

C11: Customer edit order.

Use case name Edit order.
Flow of events 1. Customer runs edit order instruction.
2. System represents a form contains a list of companies registered

in system and their item lists includes items (in check boxes) that is all
distributed among item categories .
3. Customer edits on ordered items and submits.
4. System checks the information.
6. System acknowledges Customer his order has been updated.
7. System transfers Customer to the website home page.
Entry condition Customer access edit order page.

C12: Customer charge order balance.

Use case name Charge order balance.
Flow of events 1. Customer accesses order's page instruction.
2. Customer runs charge order balance instruction.
3. System checks information in the data base if there are no

problems.
- 31 -
4. System represents a form contains a list of order items with price

of each one and the total price of the whole order .
Entry condition Customer access charge order balance page.

C13: Customer choose order delivery address.

Use case name Choose order delivery address.
Flow of events 1. Customer accesses order's page instruction.
2. System transfer Customer to order page.
3. Customer runs choose delivery address instruction.
4. System checks information in the data base if there are no

problems.
5. System represents a form contains a list of delivery addresses of

the Customer .
6. Customer choose one of the delivery addresses for the order to be

delivered at.
7. Customer received an acknowledgement explains the order &

delivery address.
Entry condition Customer access choose order delivery address page.

C14: Customer submit purchase order.

Use case name Submit purchase order.
Flow of events 1. Customer runs submit purchase order instruction.
2. Customer submit purchasing his order.
3. Customer received an acknowledgement explains the order and

the expiry information.
Entry condition Customer access submit purchase order page.

C15: Customer view category.

Participate actor Customer.
Flow of events 1. Customer runs access category page instruction.
- 32 -
4. Customer choose category from the list.
5. System transfers Customer to the category's page.
Entry condition Customer access view category page.

Exit condition Customer received an acknowledgement or an explanation indicating
C16: Customer view item.

Flow of events 1. Customer runs access items page instruction.
2. System transfer Customer to items page.

3. Customer choose an item from the list.
Entry condition Customer access view item.
C17: Customer view company.

Flow of events 1. Customer runs access companies page instruction.
2. System transfer Customer to companies page.
3. Customer chooses a company from the list.
4. System transfer Customer to the chosen company's page.

Entry condition Customer access view company page.
C18: Customer search for item ,company.

Flow of events 1. Customer runs search instruction.
(item, company).
3. Customer fills out the field and select search type (item).

goes wrong.
- 33 -
Entry condition Customer access search page.


Flow of events 1. Customer runs search instruction.
(item, company).
3. Customer fills out the field and select search type (company).

goes wrong.
6. System transfers Customer to Company's page.
Entry condition Customer access search page.

C19: Customer read about us.

Flow of events 1. Customer runs read about us instruction.
Entry condition Customer access view about us page.
C20: Customer read help & support.

Flow of events 1. Customer runs help & support instruction.
Entry condition Customer access the Help & Support page.

- 34 -
C21: Customer view contact us.

Flow of events 1. Customer runs contact us instruction.
information.
Entry condition Customer access view contact us page.
C22: Customer send E- Mail to the website assistant.

Flow of events 1. Customer runs contact site's assistant instruction.

message details).
3. Customer fills out the required fields and submits.

database.
6. Customer receives an acknowledgement.
Entry condition Customer access contact site's assistant page.

C23: Customer view posted advertisement.

Flow of events 1. Customer runs access advertisement page instruction.
2. System transfer Customer to advertisement page.
Entry condition Customer access view advertisement page.

C24: Customer view vote.

Flow of events 1. Customer runs access vote page instruction.
- 35 -
2. System transfer Customer to vote page.
Entry condition Customer access view voting.

C25: Customer vote.

Use case name Vote.
Flow of events 1. Customer runs the vote instruction.
2. System represents a form containing vote question and its choices.
3. Customer answers the question and selects his vote.
4. System checks if Customer has voted for the question before.
5. System acknowledge Customer if the operation is successful or

not.
6. System applied Customers vote to the database.
7. System sends Customer an acknowledgement.
Entry condition Customer access voting question.

2.3.5.3 Company use case details
P1: Company log in the system by user name and password.

Anticipated actor Company.
Flow of events 1. Company accesses the website.
name, password).
3. Company fills the required fields (user name, password) and submits.
right according to Companys information in the database.
5. System acknowledges the Company.
6. System transfers Company to the website home page.
7. System starts Companys session.
Entry condition Company accesses the website.
Exit condition Company received an acknowledgement, or an explanation indicating
P2: Company log out.

- 36 -

Flow of events 1. Company runs logout instruction.
2. System removes all permissions from the Company.
3. System acknowledges Company that he has been logged out.
4. System ends Companys session.
5. System transfers Company to the website login page.
Entry condition Company runs log out.
P3: Company view personal profile.

Flow of events 1. Company runs access personal profile page instruction.
2. System transfer Company to personal profile page.
Entry condition Company accesses personal profile page.

P4: Company add personal information.

Flow of events 1. Company runs personal information instruction.
2. System represents a form with some fields (Company name ,owner's

First name, owner's Last name, owner's mobile phone, owner's phone number
,Company's phone number, Company's address, Owner's address ,country, city,
Category type).
3. Company fills the required fields and submits.
6. System acknowledges Company that his information has been

submitted.
7. System transfers Company to the personal profile page.
Entry condition Company accesses add personal information page.

Exit condition Company received an acknowledgement, or received an explanation
P5: Company update personal information.

Flow of events 1. Company runs personal information instruction.
2. System represents a form with some fields (Company name ,owner's

- 37 -
First name, owner's Last name, owner's mobile phone, owner's phone number
,Company's phone number, Company's address, Owner's address ,country, city,
Category type).
3. Company edits fields and submits.
6. System acknowledges Company that his information has been

updated.
7. System transfers Company to the personal profile page.
Entry condition Company accesses update personal information page.

P6: Company add item list.

Use case name Add item list.
Flow of events 1. Company runs add item list instruction.
2. System represents a form contains some fields (item-list name, item-list

category, item-list number).
3. Company fills the information then submits.
5. If there aren't any problems, System acknowledges Company that

item list has been submitted.
7. Company received an acknowledgement.
Entry condition Company accesses add item list page.

P7: Company view item list.

Use case name View item list.
Flow of events 1. Company accesses item list's page.
2. System transfer Company to item list's page the contains the list
including its items.
Entry condition Company accesses item list's page.

- 38 -
P8: Company add items to item list.

Use case name Add items to items to item list.
Flow of events 1. Company runs add items instruction.
2. System represents a form contains a drop down list of item-lists

added by Company.
3. Company chooses an item list.
4. System represents a form contains some fields (item name, item price,
item number, item description , ).
5. Company fills the fields and submits.

his items has been added.
Entry condition Company access add items to item list page.

P9: Company update item list.

Use case name Update item list.
Flow of events 1. Company runs update item list instruction.
2. System represents a form contains a drop down of item-lists added

by Company.
3. Company chooses an item list.
5. Company edits on the fields and submits.

the item list has been updated.
8. System overwrites data in the database.
Entry condition Company accesses update item list page.

- 39 -
P10: Company remove item list.

Use case name Remove item list.
Flow of events 1. Company accesses item list's page.
2. System transfer Administrator to item list's page the contains the

list including its items.
3. Company runs remove item list instruction.
4. If there are no problems ,System checks for data in data base and
removes it.
5. Company receives an acknowledgement.
Entry condition Company accesses remove item list's page.

P11: Company view purchases.

Use case name View purchases.
Participate actor Company.
Flow of events 1. Company runs view total purchases instruction.
2. System checks required information in data base.
3. System presents a form contains list of orders sold by the

Company with info of each order (items, total price, order date, ).
Entry condition Company accesses view purchases page.

Exit condition Company received an acknowledgement or an explanation indicating
P12: Company view category.

Flow of events 1. Company runs access category page instruction.
4. Company choose category from the list.
5. System transfers Company to the category's page.
Entry condition Company access view category page.

Exit condition Company received an acknowledgement or an explanation indicating
P13: Company view item.

- 40 -

Flow of events 1. Company runs access items page instruction.
2. System transfer Company to items page.

3. Company choose an item from the list.
Entry condition Company access view item.
P14: Company view company.

Flow of events 1. Company runs access companies page instruction.
2. System transfer Company to companies page.
3. Company chooses a company from the list.
4. System transfer Company to the chosen company's page.

Entry condition Company access view company page.
P15: Company search for item ,company.

Flow of events 1. Company runs search instruction.
(item, company).
3. Company fills out the field and select search type (item).

goes wrong.
Entry condition Company access search page.


- 41 -
Flow of events 1. Company runs search instruction.
(item, company).
3. Company fills out the field and select search type (company).

goes wrong.
6. System transfers Company to Company's page.
Entry condition Company access search page.

P16: Company read about us.

Flow of events 1. Company runs read about us instruction.
Entry condition Company access view about us page.
P17: Company read help & support.

Flow of events 1. Company runs help & support instruction.
Entry condition Company access the Help & Support page.

P18: Company view contact us.

Flow of events 1. Company runs contact us instruction.
information.
Entry condition Company access view contact us page.
- 42 -
P19: Company send E- Mail to the website assistant.

Flow of events 1. Company runs contact site's assistant instruction.

message details).
3. Company fills out the required fields and submits.

database.
Entry condition Company access contact site's assistant page.

P20: Company view posted advertisement.

Flow of events 1. Company runs access advertisement page instruction.
2. System transfer Company to advertisement page.
Entry condition Company access view advertisement page.

P21: Company view vote.

Flow of events 1. Company runs access vote page instruction.
2. System transfer Company to vote page.
Entry condition Company access view voting.

P22: Company vote.

Use case name Vote.
Flow of events 1. Company runs the vote instruction.

- 43 -
3. Company answers the question and selects his vote.
4. System checks if Company has voted for the question before.
5. System acknowledge Company if the operation is successful or

not.
6. System applied Companys vote to the database.
7. System sends Company an acknowledgement.
Entry condition Company access voting question.

2.3.5.4 Advertiser use case details

D1: Advertiser Log in the system by user name and password.
Anticipated actor Advertiser.
Flow of events 1. Advertiser accesses the website.
name, password).
3. Advertiser fills the required fields (user name, password) and submits.
right according to Advertisers information in the database.
5. System acknowledges the Advertiser.
6. System transfers Advertiser to the website home page.
7. System starts Advertisers session.
Entry condition Advertiser accesses the website.
Exit condition Advertiser received an acknowledgement, or an explanation indicating
D2: Advertiser Log out.

Flow of events 1. Advertiser runs logout instruction.
2. System removes all permissions from the Advertiser.
3. System acknowledges Advertiser that he has been logged out.
4. System ends Advertisers session.
5. System transfers Advertiser to the website login page.
Entry condition Advertiser runs log out.
D3: Advertiser view personal profile.

Flow of events 1. Advertiser runs access personal profile page instruction.
- 44 -
2. System transfer Advertiser to personal profile page.
Entry condition Advertiser accesses personal profile page.

D4: Advertiser add personal information.

Flow of events 1. Advertiser runs personal information instruction.
gender, Date of birth, mobile phone, phone number, country, city).
3. Advertiser fills the required fields and submits.
6. System acknowledges Advertiser that his information has been

submitted.
7. System transfers Advertiser to the personal profile page.
Entry condition Advertiser accesses add personal information page.

Exit condition Advertiser received an acknowledgement, or received an explanation
D5: Advertiser update personal information.

Flow of events 1. Advertiser runs personal information instruction.
gender, Date of birth, mobile phone, phone number, country, city).
3. Advertiser edits fields and submits.
6. System acknowledges Advertiser that his information has been

updated.
7. System transfers Advertiser to the personal profile page.
Entry condition Advertiser accesses update personal information page.

D6: Advertiser view advertisement list.

- 45 -
Use case name View advertisement list.

Flow of events 1. Advertiser runs advertisement list's instruction.
2. System transfer Advertiser to advertisement list's page.
Entry condition Advertiser accesses advertisement list's page.

D7: Advertiser request to add advertisement.

Use case name Request to add advertisement.
Flow of events 1. Advertiser runs add advertisement instruction.
2. System represents a form with some fields (advertisement information:

cost, advertisement image, period , advertisement description, ).
3. Advertiser fills the fields and submits.
5. If there aren't any problems, System acknowledges Advertiser that

his advertisement is pending to be approved by the site
administration.
7. Advertiser received an acknowledgement.
Entry condition Advertiser accesses add advertisement page.

D8: Advertiser request to remove advertisement.

Use case name Request to remove advertisement.
Flow of events 1. Advertiser accesses advertisement list's page.
2. System transfer Advertiser to advertisement list's page.
3. Advertiser runs remove advertisement instruction.
4. System checks advertisement data in data base.
5. If there aren't any problems, system acknowledges Advertiser that

his remove request is pending to be approved by the site
administration.
Entry condition Advertiser accesses remove advertisement page.

D9: Advertiser view category.

- 46 -

Participate actor Advertiser.
Flow of events 1. Advertiser runs access category page instruction.
4. Advertiser choose category from the list.
5. System transfers Advertiser to the category's page.
Entry condition Advertiser access view category page.

Exit condition Advertiser received an acknowledgement or an explanation indicating
D10: Advertiser view item.

Flow of events 1. Advertiser runs access items page instruction.
2. System transfer Advertiser to items page.

3. Advertiser choose an item from the list.
Entry condition Advertiser access view item.
D11: Advertiser view company.

Flow of events 1. Advertiser runs access companies page instruction.
2. System transfer Advertiser to companies page.
3. Advertiser chooses a company from the list.
4. System transfer Advertiser to the chosen company's page.

Entry condition Advertiser access view company page.
D12: Advertiser search for item ,company.

Flow of events 1. Advertiser runs search instruction.
(item, company).
3. Advertiser fills out the field and select search type (item).

- 47 -
goes wrong.
Entry condition Advertiser access search page.


Flow of events 1. Advertiser runs search instruction.
(item, company).
3. Advertiser fills out the field and select search type (company).

goes wrong.
6. System transfers Advertiser to Company's page.
Entry condition Advertiser access search page.

D13: Advertiser read about us.

Flow of events 1. Advertiser runs read about us instruction.
Entry condition Advertiser access view about us page.
D14: Advertiser read help & support.

Flow of events 1. Advertiser runs help & support instruction.
Entry condition Advertiser access the Help & Support page.

- 48 -
D15: Advertiser view contact us.

Flow of events 1. Advertiser runs contact us instruction.
information.
Entry condition Advertiser access view contact us page.
D16: Advertiser send E- Mail to the website assistant.

Flow of events 1. Advertiser runs contact site's assistant instruction.

message details).
3. Advertiser fills out the required fields and submits.

database.
6. Advertiser receives an acknowledgement.
Entry condition Advertiser access contact site's assistant page.

D17: Advertiser view posted advertisement.

Flow of events 1. Advertiser runs access advertisement page instruction.
2. System transfer Advertiser to advertisement page.
Entry condition Advertiser access view advertisement page.

D18: Advertiser view vote.

Flow of events 1. Advertiser runs access vote page instruction.
2. System transfer Advertiser to vote page.

- 49 -
Entry condition Advertiser access view voting.

D19: Advertiser vote.

Use case name Vote.
Flow of events 1. Advertiser runs the vote instruction.
3. Advertiser answers the question and selects his vote.
4. System checks if Advertiser has voted for the question before.
5. System acknowledge Advertiser if the operation is successful or

not.
6. System applied Advertisers vote to the database.
7. System sends Advertiser an acknowledgement.
Entry condition Advertiser access voting question.

2.3.5.5 Assistant use case details

S1: Assistant log in the system by user name and password.
Anticipated actor Assistant.
Flow of events 1. Assistant accesses the website.
name, password).
3. Assistant fills the required fields (user name, password) and submits.
right according to Assistants information in the database.
5. System acknowledges the Assistant.
6. System transfers Assistant to the website home page.
7. System starts Assistants session.
Entry condition Assistant accesses the website.
Exit condition Assistant received an acknowledgement, or an explanation indicating
S2: Assistant log out.

Flow of events 1. Assistant runs logout instruction.
2. System removes all permissions from the Assistant.
3. System acknowledges Assistant that he has been logged out.
4. System ends Assistants session.
- 50 -
5. System transfers Assistant to the website login page.

Entry condition Assistant runs log out.
S3: Assistant view personal profile.

Flow of events 1. Assistant runs access personal profile page instruction.
2. System transfer Assistant to personal profile page.
Entry condition Assistant accesses personal profile page.

S4: Assistant add personal information.

Flow of events 1. Assistant runs personal information instruction.
gender, Date of birth, mobile phone, phone number, country, city, marital statues).
3. Assistant fills the required fields and submits.
6. System acknowledges Assistant that his information has been

submitted.
7. System transfers Assistant to the personal profile page.
Entry condition Assistant accesses add personal information page.

Exit condition Assistant received an acknowledgement, or received an explanation
S5: Assistant update personal information.

Flow of events 1. Assistant runs personal information instruction.
2. System represents a form with some fields (First name, Last name, and
gender, Date of birth, mobile phone, phone number, country, city, marital status).
3. Assistant edits fields and submits.

- 51 -
6. System acknowledges Assistant that his information has been

updated.
7. System transfers Assistant to the personal profile page.
Entry condition Assistant accesses update personal information page.

S6: Assistant view pending orders in system.

Use case name View pending orders in system.
Flow of events 1. Assistant runs view pending orders instruction.
2. System transfers Assistant to pending orders list page.
3. Assistant choose pending order from the list.
4. System response by presenting a form contains the order & its

information (items , total price , Assistant , time , supplier company , ).
Entry condition Assistant accesses pending orders list.

S7: Assistant remove implemented orders.

Use case name Remove implemented orders.
Flow of events 1. Assistant accesses pending orders list page.
2. Assistant choose an order from the list.
3. System response to Assistant by presenting a form contains the

order & its information (items , total price , Customer , time , supplier company
, expiry date , ).
4. Assistant checks the order expiry and payment information then

contacts delivery employee to implement the order.
5. Assistant marks the order and submit..
6. System removes the order from pending orders list if there are no
problems.
7. Customer receives an acknowledgment.
8. Company receives an acknowledgment.
9. Assistant receives an acknowledgment.
Entry condition Assistant accesses pending orders list page.

- 52 -
S8: Assistant remove expired orders in system.

Use case name Remove expired orders in system.
Flow of events 1. Assistant runs view expired orders instruction.
2. System transfers Assistant to expired orders page (that contains a list

of pending orders passed their expiry date).
3. Assistant choose an order from the list.

order & its information (items , total price , Customer, time , supplier company
, expiry date , ).
5. Assistant mark order and submit remove instruction.
6. System remove order data from data base ,if there are no
problems.
Entry condition Assistant accesses expired orders page.

S9: Assistant send un-implemented order notification to

customer .
Use case name Send un-implemented order notification to Assistant.
Flow of events 1. Assistant accesses pending orders page.
2. Assistant choose pending order from the list.

order & its information (items , total price , Customer , time , supplier company
, ).
4. Assistant runs send Assistant notification instruction.
5. Systems checks Assistant contact e-mail data from data base.
6. If there are no problems ,System sends an email to Assistant's e-

mail address contains the order's details including expiry
information.
7. Assistant receives an acknowledgement.
Entry condition Assistant accesses pending orders list page.

- 53 -
S10: Assistant view company account balance.

Use case name View company account balance.
Flow of events 1. Assistant runs view Company's account balance instruction.
2. System presents a form with drop down list contains all registered
companies in the system.
3. Assistant choose a Company from the list and runs charge account
balance instruction.
4. System checks information in the data base ,if there are no

problems.
5. System represents a form contains list of orders done by the

Company with info of each order ( items, total price, order date, ).
Entry condition Assistant accesses Company's account balance page.

S11: Assistant view pending advertisement list.

Use case name View pending advertisement list.
Flow of events 1. Assistant runs view pending advertisements instruction.
2. System transfers Assistant to pending advertisements page.
3. Assistant choose an advertisement from the list.

advertisement & its information.
Entry condition Assistant accesses pending advertisements page.

S12: Assistant post pending advertisement.

Use case name Post pending advertisement.
Flow of events 1. Assistant runs post/reject pending advertisement instruction.
3. Assistant mark an advertisement and submits (POST) instruction

if the advertisement fits the policy conditions .
4. System adds the advertisement to the data base, If there are no

- 54 -
problems.
5. Advertiser receives an acknowledgment.
Entry condition Assistant accesses post pending advertisement page.

S13: Assistant reject pending advertisement

Use case name Reject pending advertisement.
Flow of events 1. Assistant runs post/reject pending advertisement instruction.
3. Assistant mark an advertisement and submits (Reject) instruction

if the advertisement does not fit the policy conditions .
4. System removes the advertisement from the list, If there are no

problems.
Entry condition Assistant accesses reject pending advertisement page.

S14: Assistant view posted advertisement.

Participate actor Assistant.
Flow of events 1. Assistant runs access advertisement page instruction.
2. System transfer Assistant to advertisement page.
Entry condition Assistant access view advertisement page.

S15: Assistant remove posted advertisement.

Use case name Remove posted advertisement .
Flow of events 1. Assistant runs remove advertisement instruction.
2. System represents a form contains a list of posted advertisements.
3. Assistant mark the advertisement to remove and submits.
4. System removes the advertisement from data base, If there aren't

- 55 -
any problems,
5. System acknowledges Advertiser that his advertisement has been

removed.
6. System acknowledges Assistant.
Entry condition Assistant accesses remove posted advertisement page.

S16: Assistant send E-mail to user (Customer ,Company

,Advertiser ,Administrator).
Use case name Send E-Mail to user.
Flow of events 1. Assistant runs contact user instruction.
2. System presents a form containing some fields (sender e-mail, receiver

e-mail, subject, message details & title ) & a drop down list contains user
types (Admin, Customer , advertiser , company).
3. Assistant fills out the required fields and submits.
4. System checks the entered e-mail address in email of the

receptionist user in database according to the chosen user type.
5. System send message to the specific address if there are no

problems.
6. Assistant receives an acknowledgement.
Entry condition Assistant accesses contact user page.

S17: Assistant view category.

Flow of events 1. Assistant runs access category page instruction.
4. Assistant choose category from the list.
5. System transfers Assistant to the category's page.
Entry condition Assistant access view category page.

Exit condition Assistant received an acknowledgement or an explanation indicating why
- 56 -
S18: Assistant view item.

Flow of events 1. Assistant runs access items page instruction.
2. System transfer Assistant to items page.

3. Assistant choose an item from the list.
Entry condition Assistant access view item.
S19: Assistant view company.

Flow of events 1. Assistant runs access companies page instruction.
2. System transfer Assistant to companies page.
3. Assistant chooses a company from the list.
4. System transfer Assistant to the chosen company's page.

Entry condition Assistant access view company page.
S20: Assistant make several searches in system ( Item,User , ).

Use case name Search for several objects in system.
Flow of events 1. Assistant runs search instruction.
2. System presents a field (for the search key) and drop down list (contains
searching type).
3. Assistant fills out the search key field & select search type (item,
User , ) from the list.

goes wrong.
5. System checks if the search key is in the specific table in

database.
6. System gets data from data base.
7. System presents a form containing the desired information.
Entry condition Assistant accesses search page.

S21: Assistant read about us.

- 57 -

Flow of events 1. Assistant runs read about us instruction.
Entry condition Assistant access view about us page.
S22: Assistant read help & support.

Flow of events 1. Assistant runs help & support instruction.
Entry condition Assistant access the Help & Support page.

S23: Assistant view contact us.

Flow of events 1. Assistant runs contact us instruction.
information.
Entry condition Assistant access view contact us page.
S24: Assistant view vote.

Flow of events 1. Assistant runs access vote page instruction.
2. System transfer Assistant to vote page.
Entry condition Assistant access view voting.

S25: Assistant vote.

Use case name Vote.
Flow of events 1. Assistant runs the vote instruction.
- 58 -
3. Assistant answers the question and selects his vote.
4. System checks if Assistant has voted for the question before.
5. System acknowledge Assistant if the operation is successful or

not.
6. System applied Assistants vote to the database.
7. System sends Assistant an acknowledgement.
Entry condition Assistant access voting question.

2.3.5.6 Administrator use case details

A1: Administrator log in the system by user name and password.
Anticipated actor Administrator.
Flow of events 1. Administrator accesses the website.
name, password).
3. Administrator fills the required fields (user name, password) and
submits.
right according to Administrators information in the database.
5. System acknowledges the Administrator.
6. System transfers Administrator to the website home page.
7. System starts Administrators session.
Entry condition Administrator accesses the website.
Exit condition Administrator received an acknowledgement, or an explanation indicating
A2: Administrator log out.

Flow of events 1. Administrator runs logout instruction.
2. System removes all permissions from the Administrator.
3. System acknowledges Administrator that he has been logged out.
4. System ends Administrators session.
5. System transfers Administrator to the website login page.
Entry condition Administrator runs log out.
A3: Administrator update own account.

Use case name Update own account.
- 59 -

Flow of events 1. Administrator runs update account instruction.
2. System represents a form with some fields (user name , password).
3. Administrator edits fields and submits.
6. System acknowledges Administrator that his account has been

updated.
Entry condition Administrator accesses update account page.

A4: Administrator approve pending users in system.

Use case name Approve pending users in system.
Flow of events 1. Administrator runs view pending users (customer, company, advertiser,
Assistant ) instruction.
2. System transfers Administrator to pending users list page.
3. Administrator chooses a user from the list.
4. Administrator marks the user and run submit instruction.
5. System adds data in to data base if there are no problems.
6. System removes the user from pending list.
7. User receives an acknowledgment.
8. Administrator receives an acknowledgment.
Entry condition Administrator accesses pending users page.

Exit condition pending users in system received an acknowledgement, or an
explanation indicating why the transaction could not be processed.
A5: Administrator view user's personal profile in system.

Use case name View User's personal profile.
Flow of events 1. Administrator runs user's (customer, company, advertiser, Assistant )
personal profile page instruction.
2. System check the database for the user's information.
3. System represents a form with some fields includes user

information (id, username, ... ).
Entry condition Administrator accesses User's personal profile.

- 60 -

A6: Administrator remove user from system.

Use case name Remove User
Anticipated actor Administrator
Flow of events 1. Administrator accesses user's personal profile page.
2. Administrator runs remove User instruction.
3. If there aren't any problems, system checks that the User is in
the data base.
4. Administrator submits removing the User.
5. System deletes the User from User table in the data base and
acknowledges Administrator that this User has been removed.
Entry condition Administrator access deletes User's information.
A7: Administrator view category.

Participate actor Administrator.
Flow of events 1. Administrator runs access category page instruction.
4. Administrator choose category from the list.
5. System transfers Administrator to the category's page.
Entry condition Administrator access view category page.

Exit condition Administrator received an acknowledgement or an explanation indicating
A8: Administrator add category.

Use case name Add category.
Flow of events 1. Administrator runs add category instruction.
2. System represents a form contains some fields (category name,

category number, category description , ).
3. Administrator fills the information then submits.
5. If there aren't any problems, System acknowledges Administrator

that his category has been submitted.

- 61 -
7. Administrator received an acknowledgement .
Entry condition Administrator access add category page.

A9: Administrator update category.

Use case name Update category.
Flow of events 1. Administrator runs update category instruction.
2. System represents a form contains a drop down of categories .
3. Administrator choose category.
4. System represents a form contains some fields (category name,

category number, category description , ).
5. Administrator edit the fields and submits.

that his item list has been updated.
9. Administrator received an acknowledgement.
Entry condition Administrator access update category page.

A10: Administrator view item.

Flow of events 1. Administrator runs access items page instruction.
2. System transfer Administrator to items page.

3. Administrator choose an item from the list.
Entry condition Administrator access view item.
A11: Administrator view item list.

Use case name View item list.
Flow of events 1. Administrator accesses item list's page.

- 62 -
Entry condition Administrator accesses item list's page.

A12: Administrator update item list.

Use case name Update item list.
Flow of events 1. Administrator runs update item list instruction.
2. System represents a form contains a drop down of item-lists.
3. Administrator chooses an item list.
5. Administrator edits on the fields and submits.

that the item list has been updated.
Entry condition Administrator accesses update item list page.

A13: Administrator remove item list.

Use case name Remove item list.
Flow of events 1. Administrator accesses item list's page.

3. Administrator runs remove item list instruction.
4. If there are no problems ,System checks for data in data base and
removes it.
5. Administrator receives an acknowledgement.
Entry condition Administrator accesses remove item list's page.

- 63 -
A14: Administrator make backup and restore database.

Use case name Make backup file.
Flow of events 1. Administrator runs make backup instruction.
2. System checks the information , then make a backup of data base

and download backup file on the Administrator device.

that the backup file has been saved on his device.
Entry condition Administrator accesses make backup file.

A15: Administrator restore database.

Use case name Restore data base.
Flow of events 1. Administrator runs restore data base instruction.
2. System checks the information, then asks the Administrator to

determine the location of the restore file on the administrator's
device.
3. System check the file type and location.
4. If there aren't any problems, System start restoring the data base.
5. System acknowledges Administrator that the data base has been

restored.
Entry condition Administrator restore data base.

A16: Administrator view pending orders in system.

Use case name View pending orders in system.
Flow of events 1. Administrator runs view pending orders instruction.
2. System transfers Administrator to pending orders list page.
3. Administrator choose pending order from the list.
4. System response by presenting a form contains the order & its

information (items , total price , customer , time , supplier company , ).
Entry condition Administrator accesses pending orders list.

- 64 -
A17: Administrator remove implemented orders.

Use case name Remove implemented orders.
Flow of events 1. Administrator accesses pending orders list page.
2. Administrator choose an order from the list.
3. System response to Administrator by presenting a form contains

the order & its information (items , total price , Customer , time , supplier
company , expiry date , ).
4. Administrator checks the order expiry and payment information

then contacts delivery employee to implement the order.
5. Administrator marks the order and submit..
6. System removes the order from pending orders list if there are no
problems.
Entry condition Administrator accesses pending orders list page.

A18: Administrator remove expired orders in system.

Use case name Remove expired orders in system.
Flow of events 1. Administrator runs view expired orders instruction.
2. System transfers Administrator to expired orders page (that contains a

list of pending orders passed their expiry date).
3. Administrator choose an order from the list.

the order & its information (items , total price , Customer, time , supplier
company , expiry date , ).
5. Administrator mark order and submit remove instruction.
6. System remove order data from data base ,if there are no
problems.
Entry condition Administrator accesses expired orders page.

- 65 -

A19: Administrator send un-implemented order notification to

customer.
Use case name Send un-implemented order notification to Administrator.
Flow of events 1. Administrator accesses pending orders page.
2. Administrator choose pending order from the list.

the order & its information (items , total price , Customer , time , supplier
company , ).
4. Administrator runs send Administrator notification instruction.
5. Systems checks Administrator contact e-mail data from data base.
6. If there are no problems ,System sends an email to Administrator's

e-mail address contains the order's details including expiry
information.
Entry condition Administrator accesses pending orders list page.

A20: Administrator view company account balance.

Use case name View company account balance.
Flow of events 1. Administrator runs view Company's account balance instruction.
2. System presents a form with drop down list contains all registered
companies in the system.
3. Administrator choose a Company from the list and runs charge

account balance instruction.
4. System checks information in the data base ,if there are no

problems.
5. System represents a form contains list of orders done by the

Company with info of each order ( items, total price, order date, ).
Entry condition Administrator accesses Company's account balance page.

A21: Administrator view pending advertisement list.

- 66 -
Use case name View pending advertisement list.

Flow of events 1. Administrator runs view pending advertisements instruction.
2. System transfers Administrator to pending advertisements page.
3. Administrator choose an advertisement from the list.

the advertisement & its information.
Entry condition Administrator accesses pending advertisements page.

A22: Administrator post pending advertisement.

Use case name Post pending advertisement.
Flow of events 1. Administrator runs post/reject pending advertisement instruction.
3. Administrator mark an advertisement and submits (POST)

instruction if the advertisement fits the policy conditions .
4. System adds the advertisement to the data base, If there are no

problems.
Entry condition Administrator accesses post pending advertisement page.

A23: Administrator reject pending advertisement.

Use case name Reject pending advertisement.
Flow of events 1. Administrator runs post/reject pending advertisement instruction.
3. Administrator mark an advertisement and submits (Reject)

instruction if the advertisement does not fit the policy conditions .
4. System removes the advertisement from the list, If there are no

problems.
Entry condition Administrator accesses reject pending advertisement page.

- 67 -

A24: Administrator view posted advertisement.

Flow of events 1. Administrator runs access advertisement page instruction.
2. System transfer Administrator to advertisement page.
Entry condition Administrator access view advertisement page.

A25: Administrator remove posted advertisement.

Use case name Remove posted advertisement .
Flow of events 1. Administrator runs remove advertisement instruction.
2. System represents a form contains a list of posted advertisements.
3. Administrator mark the advertisement to remove and submits.
4. System removes the advertisement from data base, If there aren't

any problems,
5. System acknowledges Advertiser that his advertisement has been

removed.
6. System acknowledges Administrator.
Entry condition Administrator accesses remove posted advertisement page.

A26: Administrator add about us article.

Use case name Add about us article .
Flow of events 1. Administrator runs add about us instruction.
2. System responses by presenting a form contains fields to add

about us information.
3. Administrator fills out the about us field and submits.
4. System checks the submitted data.
5. System adds the about us to data base, if there is no problem.
6. Administrator receives an acknowledgment from system.
Entry condition Administrator accesses add about us page.

- 68 -

A27: Administrator update about us article.

Use case name Update about us article.
Flow of events 1. Administrator runs update about us instruction.
2. System checks if the about us information is in the data base or

not if so show the contents in the fields.
3. System response by presenting a form contains information.
4. Administrator edits on the required field to be updated.
5. System check the data.
6. System updates about us data in data base, If there is no

problem.
Entry condition Administrator accesses update about us page.

A28: Administrator view about us article.

Use case name Read about us article.
Flow of events 1. Administrator runs read about us instruction.
Entry condition Administrator access view about us article page.
A29: Administrator add contact us information.

Use case name Add contact us information .
Flow of events 1. Administrator runs add contact us instruction.
2. System response by presenting a form contains fields to add

contact us information.
3. Administrator fills out the contact us field and submit.
4. System check the submitted data.
5. System will add the contact us to data base, if there is no

- 69 -
problem.
Entry condition Administrator accesses add contact us information page.

A30: Administrator update contact us information.

Use case name Update contact us information.
Flow of events 1. Administrator runs update contact us instruction.
2. System checks if the contact us information is in the data base or

not if so show the contents in the fields.
4. Administrator edits on the required field to be updated.
6. System will update contact us data in data base, If there is no

problem.
Entry condition Administrator accesses update contact us information page.

A31: Administrator view contact us information.

Use case name View contact us information.
Flow of events 1. Administrator runs contact us instruction.
information.
Entry condition Administrator access view contact us information page.
A32: Administrator add help & support reports.

Use case name Add help and support reports.
Flow of events 1. Administrator runs add help and support instruction.
2. System response by presenting a form contains two fields (question,

detail).
3. Administrator fills out question and detail fields and submit.

- 70 -
4. System checks the submitted data.
5. System will add new help and support to data base, if there is no
problem.
Entry condition Administrator accesses add help and support reports page.
A33: Administrator update help & support reports.

Use case name Update help and support reports.
Flow of events 1. Administrator runs update help and support instruction.
2. System checks if the help and support is in the data base or not if
so show the contents in the fields.
4. Administrator edits on the required fields to be updated.
6. System will update help and support data in data base, If there is
no problem.
Entry condition Administrator accesses update help and support reports page.
A34: Administrator view help & support reports.

Use case name Read Help & Support reports.
Flow of events 1. Administrator runs help & support instruction.
Entry condition Administrator access the Help & Support reports page.
A35: Administrator add voting question.

Use case name Add voting question.
Flow of events 1. Administrator runs add vote instruction.
- 71 -
2. System response by presenting a form contains some ( question,

choices).
3. Administrator fills out the required fields.
4. System checks the input.
5. System response by presenting the vote chart.
6. System will add data to the data base, if there is no problem.
Entry condition Administrator accesses add voting question page.

A36: Administrator update voting question.

Use case name Update vote question.
Flow of events 1. Administrator runs Update vote instruction.
2. System checks for required data from data base.
3. System response by presenting a form contains some ( question,

choices).
4. Administrator edits the required fields and submit .
5. System adds updates to data base, if there is no problem.
6. Administrator receives an acknowledgment from system his update

has been submitted.
Entry condition Administrator accesses Update voting question page.

A37: Administrator view vote.

Flow of events 1. Visitor runs access vote page instruction.
2. System transfer Visitor to vote page.
Entry condition Administrator access view voting.

A38: Administrator send E-mail to User (Customer, Company,

Advertiser, Assistant).
Use case name Send E-Mail to user.
- 72 -

Flow of events 1. Administrator runs contact user instruction.
2. System presents a form containing some fields (sender e-mail, receiver

e-mail, subject, message details & title ) & a drop down list contains user
types (assistant, Customer , advertiser , company).
3. Administrator fills out the required fields and submits.
4. System checks the entered e-mail address in email of the

receptionist user in database according to the chosen user type.
5. System send message to the specific address if there are no

problems.
Entry condition Administrator accesses contact user page.

A39: Administrator Make several searches in system (Item ,User ,

).
Use case name Search for several objects in system.
Flow of events 1. Administrator runs search instruction.
2. System presents a field (for the search key) and drop down list (contains
searching type).
3. Administrator fills out the search key field & select search type
(item, User , ) from the list.

goes wrong.
5. System checks if the search key is in the specific table in

database.
6. System gets data from data base.
7. System presents a form containing the desired information.
Entry condition Administrator accesses search page.

2.3.6 System use case survey
When Visitor accesses the main page of 'O6lob' website, This

gives him the ability to view category(V2), View item(V3), View
company(V4) that is registered in the site and also be able to view
all posted advertisments(V10), Search for item or a company(V5),
- 73 -
Access other several pages like about us (V6), Help & support(V7),
Contact us(V8) and vote(V11).
This activities attract and force the web site visitor to think about
registering(V1) in the system, Or to send an E-Mail to website
assistant(V9) asking for more information.
After the visitor registers(V1) the user have a user name and
password to access his own account by logging in the system.
The Customer use his user name and password to log in and
access his own account in the website(C1),The system then
makes the customer able to view his personal profile(C3), Add
personal information(C4), And update his personal
information(C5), Also the customer can add delivery address
information(C6) and remove them(C7).
Customer is able to view order(C8), Add order(C9), Remove
order(C10), Or edit on order(C11) as he wants it to be , Then
charges order balance(C12) to have the total price of this order
and payment information after choosing delivery address(C13) for
the order to be delivered to, Then submits the purchasing
order(C14).
Customer obviously can view category(C15), View item(C16), View
company(C17), Search for an item or a company(C18), Read
about us(C19), Read help & support page(C20), View contact
us(C21), Contacting the assistant by sending E- Mail(C22), View
posted advertisements(C23), View vote(C24) and finally vote in the
published voting question(C24).
After that Customer logs out(C2) from the system after finishing
his operations in it that ends his session and redirect him to log in
page.
Also registered company uses his user name and password to log
in and access own account in the website(P1), The system then
makes the company able to view his personal profile(P3), Add
personal information(P4), And update his personal information(P5),
Also company can add item list(P6), View item list(P7) and stard
adding items in this list(P8), Update items in list(P9) and remove
them from list(P10).
Company can check up and view purchases of items ordered and
sold(P11).
- 74 -
Company also views category(P12), View item(P13), View

company(P14), Search for an item or a company(P15), Read
about us(P16), Read help & support page(P17), View contact
us(P18), Contacting the assistant by sending E- Mail(P19), View
posted advertisements(P20), View vote(P21) and finally vote in the
published voting question(P22).
After that company logs out(P2) from the system after finishing his
operations in it that ends session and redirect him to log in page.
Advertiser can use his user name and password to log in and
access own account in the website(D1), The system then makes
the company able to view his personal profile(D3), Add personal
information(D4), And update his personal information(D5).
Advertiser accesses to view his advertisement list that's posted by
him(D6) and to add new advertisement he send a request to the
administration of the web site to add an advertisement (D7), Or
send request to remove advertisement he has previously
posted(D8).
Advertiser even can view category(D9), View item(D10), View
company(D11), Search for an item or a company(D12), Read
about us(D13), Read help & support page(D14), View contact
us(D15), Contacting the assistant by sending E- Mail(D16), View
posted advertisements(D17), View vote(D18) and finally vote in the
published voting question(D19).
After that Advertiser logs out(D2) from the system after finishing
his operations in it that ends session and redirect him to log in
page.
Assistant can use his user name and password to log in and
access own account in the website(S1), The system then makes
the company able to view his personal profile(S3), Add personal
information(S4), And update his personal information(S5).
View pending orders in system(S6), Remove implemented orders
that is no more needed in the system (S7), Remove expired orders
that have passed its expiry date from the system(S8), Send un-
implemented order notification to customer to notify him that his
order has not been implemented for some reason(S9), View
- 75 -
company account balance that includes all orders sold for this
company(S10), View pending advertisement requests from the
advertiser(S11), Post pending advertisement on the site if it
satisfies the policies(S12), Reject pending advertisement if it
doesnt(S13), View posted advertisement(S14), Remove posted
advertisement(S15), Send E-mail to any user(S16) and finally
Make several searches in system(S20).
Assistant even can view category(S17), View item(S18), View
company(S19), Read about us(S21), Read help & support
page(S22), View contact us(S23), View vote(S24) and vote in the
published voting question(S25).
After that assistant logs out(S2) from the system after finishing his
operations in it that ends session and redirect him to log in page.
Administrator uses his user name and password to log in and

access own account in the website(A1), The system then makes
the company able to view and access all website transactions
including his jobs.
Administrator can update own account(A3), Approve pending
users in system that are recently registered(A4), View user's
personal profiles(A5), Remove user from system(A6), View items
category(A7), Add category(A8), Update category(A9), Also view
items that added by company(A10), View item list(A11), Make
updates on the item list(A12), Even remove item list(A13), Make
backup of the system to avoid any loss in case of failure(A14),
Restore the database from computer(A15), View pending orders in
system(A16), Remove implemented orders that is no more needed
in the system (A17), Remove expired orders that have passed its
expiry date from the system(A18), Send un-implemented order
notification to customer to notify him that his order has not been
implemented for some reason(A19), View company account
balance that includes all orders sold for this company(A20), View
pending advertisement requests from the advertiser(A21), Post
pending advertisement on the site if it satisfies the policies(A22),
Reject pending advertisement if it doesnt(A23), View posted
advertisement(A24), Remove posted advertisement(A25), Send E-
- 76 -
mail to any user(A38) and finally Make several searches in

system(A39).
Administrator adds about us article(A26), Update about us
article(A27), View about us(A28), Add contact us (A29), Update
contact us (A30), View contact us(A31), Add help & support (A32),
Update help & support (A33), Read help & support page(A34),
Add voting question (A35), Update voting question(A36) and view
vote(A37) .
After that administrator logs out(A2) from the system after finishing
his operations in it that ends session and redirect him to log in
page.
2.3.7 Use case diagrams

- 77 -
Figure 2.3.7.1: Visitor Use Case Diagram

- 78 -
Figure 2.3.7.2: Customer Use Case Diagram

- 79 -
Figure 2.3.7.3: Company Use Case Diagram

- 80 -
Figure 2.3.7.4: Advertiser Use Case Diagram

- 81 -
- 82 -
Figure 2.3.7.5: Assistant Use Case Diagram

- 83 -
Figure 2.3.7.6: Administrator Use Case Diagram

- 84 -
2.3.8 Communication diagrams
2.3.8.1 Visitor use case realization
Figure 1: Use Case Realization for V1: Visitor registration.
Figure 2: Use Case Realization for V2: Visitor view category.

- 85 -
Figure 3: Use Case Realization for V3: Visitor view item.
Figure 4: Use Case Realization for V4: Visitor view company.
Figure 5: Use Case Realization for V5: Visitor search for item ,company.
- 86 -
Figure 6: Use Case Realization for V6: Visitor read about us.
Figure 7 Use Case Realization for V7: Visitor read about us.
Figure 8: Use Case Realization for V8: Visitor view contact us.
- 87 -
Figure 9: Use Case Realization for 9 Visitor send E-Mail.
Figure 10: Use Case Realization for V10: view posted advertisement.
Figure 11: Use Case Realization for V11: Visitor view vote.
- 88 -
2.3.8.2 Customer use case realization
Figure 12: Use Case Realization for C1: Customer log in.
Figure 13: Use Case Realization for C2: Customer log out.
Figure 14: Use Case Realization for C3: view personal profile.
- 89 -
Figure 15: Use Case Realization for C4: add personal information.
Figure 16: Use Case Realization for C5: update personal information.
Figure 17: Use Case Realization for C6: add delivery address.
- 90 -
Figure 18: Use Case Realization for C7: remove delivery address.
Figure 19: Use Case Realization for C8: Customer view order.
Figure 20: Use Case Realization for C9: Customer add order
- 91 -
Figure 21: Use Case Realization for C10: remove order
Figure 22: Use Case Realization for C11: Customer edits order
- 92 -
Figure 23: Use Case Realization for C12: charge order balance
Figure 24: Use Case Realization for C13: choose order delivery address.
2.3.8.3 Company use case realization
Figure 25: Use Case Realization forP6: Company add item list.
- 93 -
Figure 26: Use Case Realization forP7: Company view item list
Figure 27: Use Case Realization forP8: add items to item list
Figure 28: Use Case Realization for P9: update item list
- 94 -
Figure 29: Use Case Realization for P10: remove item list
Figure 30: Use Case Realization forP11: view purchases

- 95 -
2.3.8.4 Advertiser use case realization
Figure 31: Use Case Realization forD7: request to add advertisement
Figure 32: Use Case Realization forD8: request to remove advertisement

- 96 -
2.3.8.5 Assistant use case realization
Figure 33: Use Case Realization for S6: Assistant view pending orders in
system
Figure 34: Use Case Realization for S7: Assistant remove implemented orders
Figure 35: Use Case Realization for S8: Assistant remove expired orders in
system.
- 97 -
Figure 36: Use Case Realization for S9: send un-implemented order notification
to customer.
Figure 37: Use Case Realization for S10: view company account balance.
- 98 -
Figure 38: Use Case Realization for S11: Assistant view pending advertisement
list.
Figure 39: Use Case Realization for S12: Assistant post pending
advertisement.
Figure 40: Use Case Realization for S13: Assistant reject pending
advertisement.
- 99 -
Figure 41: Use Case Realization for S14: Assistant remove posted
advertisement.
2.3.8.6 Administrator use case realization
Figure 42: Use Case Realization for A8: Administrator add category.
- 100 -
Figure 43: Use Case Realization for A9: Administrator update category.
Figure 44: Use Case Realization for A17: remove implemented orders
Figure 45: Use Case Realization for A18: remove expired orders
- 101 -
Figure 46: Use Case Realization for A19: send un-implemented order
notification to customer.
Figure 47: Use case realization for A20: view company account balance.

Part of My Graduation Project

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Part of My Graduation Project

Cargado por

Copyright:

Formatos disponibles

-1-

GazaAl Azhar University

FACULTY OF ENGINEERING AND

FINAL FYP I REPORT

ELECTRONIC MARKET WEBSITE

MOTASEM MOHAMMED KURRAZ

E-markets have been a topic of high interest in the academic

So unlike traditional methods which are usually restricted by

Online trading sites have passed the issue of landscape for

The market owner can post an item in as little as 20 minutes

On the other hand with online trading sites, buyer customers

Our project's idea can be defined as an interface between

The idea is to make a database that includes main

Our website Converts usual commerce operation in to an

Also produces services for Customers by enabling them

Our website also produces an advertising area where the

1.3 The project's description:

The website allows companies (Market Owners) to post their

The website also have an advertisement area for people who

1.4 Customers features:

People who browse the site in order to buy items displayed

1.5 Companies features:

People who announce for their markets and goods in our

1.6 Project objectives:

The project main objectives are:

2.4 User interface sketches

2.1 Reviews of related literatures & applications

Main Classification of Electronic commerce

electronic commerce conducted by companies such as (

Electronic commerce is generally considered to be the sales

1.2 Business requirements

1.2.1 Business actor list

Buyer: The person who has money and wants to buy

Catalog (Business object) Contains description about the product and

Department Manager The shopping center is divided into many

Advertisement(Business The activity of attracting public attention to a

Accountant (Business object, The accounting employee who manages

Invoice of Purchasing Calculation of the number of items and the price

1.2.3 Business Use Case List

B3: Prepare invoice of purchasing: This invoice is prepared

the accountant makes discount for the invoice in

1.2.4 Business use case details

B11: The discount on invoice of purchasing.

B13: Distribute product.

3. If the order is found and available, the coordinator

1.2.5 Business use case communication diagrams

1.2.5.1 Communication diagram for use case B11:

1.2.5.2 Communication diagram for use case B13:

1.2.6 Business use case activity diagrams

1.2.6.2 Activity diagram for use case B13: Distribute product

1.3 System requirements:

1.3.2 Non-Functional Requirement:

Security: The ability to prevent an unauthorized user to

1.3.3 System actor list

1.3.4 System use case list

U8. Visitor view contact us.

1.3.4.2 Customer use case list

1.3.4.3 Company use case list

U3: Company view personal profile.

1.3.4.4 Advertiser use case list

U15: Advertiser view contact us.

1.3.4.5 Assistant use case list

1.3.4.6 Administrator use case list

U1: Administrator log in the system by user name and