Table of Contents

Chapter one.................................................................................................................................................3
1. Introduction...........................................................................................................................................3
1.1 Background of the organization.....................................................................................................3
1.2 Statement of the problem.................................................................................................................4
1.3 Objective of the study......................................................................................................................4
1.3.1 General Objective.......................................................................................................................4
1.3.2 Specific objectives.....................................................................................................................5
1.4 Methodology of the project...............................................................................................................5
1.4.1 Data collection............................................................................................................................5
1.4.2 System development methodology............................................................................................6
1.5 System implementation tool..........................................................................................................7
1.6 Scope and limitation of the project..................................................................................................7
1.6.1 Scope........................................................................................................................................7
1.6.2 Limitation..............................................................................................................................8
1.7 Significant of the project....................................................................................................................8
1.8 Feasibility Analysis:.........................................................................................................................9
1.8.1 Economic feasibility....................................................................................................................9
Cost:...................................................................................................................................................10
1.8.2 Technical feasibility...................................................................................................................10
1.8.3 Operational feasibility...............................................................................................................10
1.8.4 Schedule feasibility.................................................................................................................11
1.9 Gantt chart.....................................................................................................................................11
1.10 Management Issue.......................................................................................................................12
1.10.1 Team Configuration and Management................................................................................12
1.11 Communication plan....................................................................................................................13
Chapter two...............................................................................................................................................14
2 System Specific Requirement and System Analysis................................................................................14
Requirement specifications........................................................................................................................14
2.1 Existing system................................................................................................................................14

1
 2.1.1 User Requirements Specifications............................................................................................14
2.1.2 System Analysis.........................................................................................................................14
2.1.3 Process of existing system........................................................................................................14
2.2 Limitations and weakness of the system in use...............................................................................15
2.3 Class responsibility collaboration..................................................................................................16
2.3.1 Actor class...............................................................................................................................16
2.3.2 Business class...........................................................................................................................19
2.4 Identify Actors...............................................................................................................................20
2.5 Use case modeling...........................................................................................................................21
2.6 User inter face prototyping...........................................................................................................27
2.7 User interface flow diagram............................................................................................................29
2.8 Supplementary specification.........................................................................................................30
2.8.1 Business rule.............................................................................................................................30
Business rule is the rule that our system must be fulfilled while accessed........................................30
2.8.2 Functional Requirements........................................................................................................31
2.8.3 Non- functional requirements..................................................................................................31
 Minor and major errors in the system shall be handled by the system.......................................32
2.8.4 Constraints..............................................................................................................................32
2.9 Activity diagram...............................................................................................................................32
Chapter three............................................................................................................................................38
3 Design document....................................................................................................................................38
3.1 Class modeling.................................................................................................................................38
3.2 Sequence diagrams........................................................................................................................39
3.3 System use case diagram...............................................................................................................42
3.4 Collaboration diagram.....................................................................................................................43
3.5 Design Phase....................................................................................................................................45
3.6 A state chart diagram:.....................................................................................................................46
3.7 Persistence modeling.......................................................................................................................48
3.8 Entity relationship diagram.............................................................................................................51
3.9 Component diagram........................................................................................................................53
3.10 Deployment model........................................................................................................................54
Reference..................................................................................................................................................55

2
 Chapter one

1. Introduction

1.1 Background of the organization

Hamaresa edible oil share company is one of the governmental company that produce oil and
share the oil to many organization, individual merchants and customer as needed.it is found 1987
at eastern of Ethiopia in the Harar zone, 5km from the Harar city and 530 km from the Addis
Ababa. The company has its own branch on some cities that promotes and sells their goods to the
customer. Diredawa, Hawassa, Adama and Addis Ababa are the main branches of company that
distribute the oil for the customer and merchants around the area.now a day the company have
165 salaried worker and 20 labor most of the workers are the village people.it produce mainly
two types of oil pinot and …they use pinot,..,and chemical like bleaching ,phosphoric acid,
costicsoda. the source of raw material for product is came from governmental farm that found in
different areas like Ardaita etc. the other income is byproduct around 60 percent of the total row
material are changed to the byproduct means animal feeds only 35-40 percent are going to oil.
Animal’s feeds distributed to around the Hamaresa and to some university like Haramaya and
Diredawa.

 Today, the business is done online, institutions and company is done through network using
internet, all the systems of information management have been digitized. All these innovations
have the aim to simplify life by making a lot of things easily and in a short time. By using this
idea that our project: hamaressa edible oil factory system. As we see, many companies and
institutions in our country, have lack of designed web based application that could help and offer
better service to customers, employees and administrators. As edible oil has differ rent types of
product that are registered in different way. These products have to be stored or registered and
selling through online

3
1.2 Statement of the problem
 There are many problems in the existing since it is manual system some of these problems are
tried to list below. These are:

 Ordering their products, registering of customers and users details.

 It is difficult to order and promote their products.

 Their data base is not up to dated automatically due to they use manual system.

 The product takes time to deliver the customer since they use traditional transaction.

 It doesn't easily store all transaction details.

 Administrator does not properly and easily know situation of stock.

 The product is not verified on time.

 It is difficult to manage the products that sold and remain in store.

 System of transaction is only by cash or by traditional bank system this take time and
need additional spend.

1.3 Objective of the study

1.3.1 General Objective
 The general objective of this project is to implement a web based application that
provides promotion and selling edible oil that manufactured by Hamaressa factory.

4
 1.3.2 Specific objectives
The main specific objectives of the projects are:

 The customers will be able to order goods online from wherever they are.

 Developing the system that used for registering and controlling all information from the
different daily activities.

 The company will be reducing number of workers by increasing the quality of service to
the customer.

 The companies data base will be up to date automatically and no need of monthly ,
weekly audits.

 Customer can search using the keyword or entering some related word or phrase to get
the products.

 Guarantee security of the system by basing on the users' and clients privileges.

 To make payment notification online.

1.4 Methodology of the project

1.4.1 Data collection
The main data source for our project is the Hamaresa edible oil company manager and users
around the company.

Method of data collection we use during data collection is:-

Interviews: An interview is a conversation between two or more people where questions are asked by
the interviewer to draw out facts or statements from the interviewee.

We use interview method to gather information from different workers in different levels in the
company and users of the current system.

Interview- here we ask the manager of the Company about how works is getting done in the
Hamaressa edible oil share company.

 Some of the questions are as follows

5
  How much customer you handle per day; estimated?

 How much liter of oil will be sold per day and what type of oil?

 Do you think you make yourself familiar for new system? (To do).

 Do you ever face problems with your day to day work? If there is what type of problem

Observation: We used observation methods to understand about workers and customer

in the company to get the information that is relevant for our project to analyze the
organization work processes.

1.4.2 System development methodology

We are not well experienced to do this project and we will submit the project Step by step. So
progress of the project is measurable by advisor. Waterfall model is a sequential development
process where development flows steadily downwards through the various phases of analysis,
design, implementation, testing, integration and maintenance.
We preferred Waterfall approach for the following advantages: -

 Simple and easy to understand and use.

 Ideal for supporting less experienced project teams
 Easy to manage due to the rigidity of the model – each phase has specific
deliverables and a review process.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well understood.

The main reason of selecting waterfall model is:-

 The Project has clear objectives and solution
 Pressure does not exist for immediate implementation
 Project requirements are stable or unchanging during the system development life
cycle
 Team members are inexperienced.

6
 1.5 System implementation tool
The tools we will use for document preparation or documentation:

 Microsoft office.

 Visual Paradigm for UML Enterprise Edition.

 During Implementation, we use;

 For front end:

 My SQL

1.6 Scope and limitation of the project

1.6.1 Scope
Scope is an area in which something acts or operates or control. And it indicates the boundary or
size of the project.

Online Hamaresa edible oil company system is a web application that will permit the
customers to get the information wherever they are if they have access to the internet; the
project is limited to Hamaresa edible oil company, Harar. The system can do the
following activities. These are:

 Product management.

 Customer management.

 Ordering, delivering product notification message.

 Transaction system b/n bank system and company.

7
 1.6.2 Limitation

Limitation is factor that restricts the system decision making from achieving potential goal of the
system. There are many factors that restrict our system that limited only Hamaresa. Our system
is limited in the process of promoting and selling the oils that produced by Hamaressa edible oil
factory by online

1.7 Significant of the project

Now a days, the success and benefit of an organization is measured or evaluated by its ability of
acquiring accurate and up to dated data about its operation . An information play great role in
running organization. When we implement our project the problem that found in existing system
will be solved. The main target of our project is to replace the existing system of promotion and
selling of products by online. The other is to reduce the number of workers by increasing
efficiency of service. In manual system much amount of power and products are lost. But our
project solves the problem:

 To shorten time taken to up to date data

 It will not consume much time to process and reduce errors: through this system, errors
will be avoided because the system will be easy to use.
 The data security will be improved; thus data security helps to ensure privacy. It also
helps in protecting personal data.

8
1.8 Feasibility Analysis:
In this phase we have seen different feasibility measures such as, operational feasibility,
technical feasibility, and economical feasibility and schedule feasibilities of the new system

1.8.1 Economic feasibility

The new system is economically feasible but its benefit should observe later in the long run
working environment, in this study cannot be approved in deepness because in the beginning of
the project. Some of the benefit and cost that are estimated to be show in short and long run are:-

Benefits:

This feasible Can be expressed as tangible or intangible. Benefit that are considered as money is
called tangible benefit and benefit which resulted from the design of the new system which
cannot be considered as money called intangible benefit. The following are tangible and
intangible benefit.

 Tangible benefits:

 Reduce cost for manual data management.

 Avoid delaying the product.

 Reduce cost for employers by reducing no of employers. 

Intangible benefits:

The following benefits are intangible benefits of the new system:

 Increased consistency and correctness.

 Enable to make fast communication.

   Improved processing speed.

 Improved up to dated data timely.

Cost:
We have spent some money to complete our project starting from the beginning up to the
end, the total costs we have paid was listed in the following table.

9
No Items Price(in birr) Quantity Total
1 Paper 0.50 20 10
2 CD 10 1 10
3 Pen 4 1 4
4 Transportation 20 4 days 100
5 Call phone 25 25
6 Print 1.00 54 54
7 Binding 7 1 7
8 Miscellaneous cost 20 20
Total 8 230

1.8.2 Technical feasibility

Usually new systems established in order to overcome the technical weakness of the previous
system. In the same way, this system is technically big enough to be applied easily to the
problem identified in the existing system. In addition; the both hardware and software for this
system are highly available and can be purchased with small cost. The system is accessible by
any computing device that permit internet access like any other system from where ever and at
any time. Therefore, it can be concluded that the system is technically feasible.

1.8.3 Operational feasibility

It might not be possible to see fully operational system within the given resource and the given
limit of time for full Web development. However with great cooperation of the project team and
the help of the advisor system can address over all problems of the current system those
mentioned in the above.

1.8.4 Schedule feasibility

Schedule feasibility describe the time frame given for every activity and making measurement
whether activity Completion date can be met or not .The project team members expected to
complete given activity on time without any delay.

10
 1.9 Gantt chart

2014/2015
No. Task Name
Nov 20 – Dec 5 Dec 6 – Dec 20 Dec 21 – Jan 5 Jan 6 – 20 Jan 21-May 15
1 Introduction
i

2 SRS

3 Object Design
&Analysis
4 System Design
5 Implementation

Legend: - Job is complete completed

Job is not complete

1.10 Management Issue

1.10.1 Team Configuration and Management
In our project, we have four members where each of members has their specific given work
and controlled by one person from the team member.

11
The following table shows the types of tasks and the responsibility that given to each of
team members.

Task Team member name

Project manager Muktar kasim

System Requirement And specification Zakeriya Baker
(SRS)
Analysis and Design Ibrahim Abdurrahman
Implementation And Testing Sadat Hussein

Project manager:

Muktar kasim manages over all entire projects and he give activities and arrange schedule
for every activities needed to accomplish the project within the given time.

System and requirement specification

Zakeriya

His responsibility is gathering all required data and resources needed to successive of projects
from beginning up to the end of the projects.

Analysis and Design:

The new system that we are developing for Hamaresa oil company was analyzed and
designed by the team member (Ibrahim Abdurrahman)

Implementation and Testing

The to bring the project to an end and so that will be tested.

1.11 Communication plan

While we are working on our project, we use the following techniques in order to meet one
another and then exchange our suggestions or ideas. Those techniques are listed in the
following table.

Number Techniques
1 E-mail account

12
2 Mobile phone
3 Schedule(time table)

13
 Chapter two

2 System Specific Requirement and System Analysis

Requirement specifications

2.1 Existing system

Hamaressa oil factory is using manual system in its daily activity .every activity in the
organization done by human power since it have no its own automate system and the company
have many workers that have the same or related work.

2.1.1 User Requirements Specifications

The software requirements document is a written statement of what the software will do. What
the software does is directly supposed by its users- either human user or other software systems.
When an external system submits a request of a certain form, it gets a particular response. The
main purpose of requirements document is to serve as an agreement between the developers and
the users on what the application will do.

2.1.2 System Analysis

Any system designer will first analyze the existing system to point out the problems which are
the system requirements creating need for a new one. The system analysis in this study has been
catered for in the research phase during which the designer looked at how the existing operates
and its shortcomings. Here the target is to come up with which would facilitate the customers
and then display the information about product needed for customer.

2.1.3 Process of existing system

The processes that we want to describe are:

 recording product on shelf,

 customer collecting product

 payment after choosing items,

In this part we have two types of customers such as:

 Normal.

 Extra-customer.

14
 Order process

“Order processing" is the term generally used to describe the process or the work flow associated
with the picking, packing and delivery of the packed item(s) to a shipping carrier between
customer and order chief. The specific "order fulfillment process" or the operational procedures
of distribution department are determined by many factors. Each distribution department has its
own unique requirements or priorities.

Payment process

After selecting product and calculating total of money, the payment of customer done in the
following ways:

Cash: where customer present cash to cashier or where cashier receive money and customer get
an invoice.

Checks: where customer present checks to cashier for extra-person not every customer

In our case, an online payment will be done using MTN mobile money, where after paying top
manger will get message from customer's ordering payment.

2.2 Limitations and weakness of the system in use

This results into some errors and or mistakes; they use form of stock, which can cause different
problem such as lack of data. It has some lacks and failure which are the main reasons of
developing and designing a new system.

The existing system presents many problems relative to lack of computerization and internet in
the company mean that lack or missing of online system.

Proposed solutions to the problems

With the existing system, it is difficult to keep up to date information because it lacks a
dynamic application connected to a database that would automate the task.

The design for the company would solve the problems mentioned above which are very close to
an inefficient information system. Realization of this web application would allow sharing of
information between multiple interveners and would end the problems caused by inappropriate
information system by means of the below proposed solutions:

(i) Creation of a web application for online ordering in order to help client, and putting your
product in online which is not experienced with the existing system.

(ii) Controlling and managing their system that can be operated by the proposed web
application.
15
 (iii) An online web application in which the reports will contain all details, made and
submitted on due time.

2.3 Class responsibility collaboration

Class Responsibility Collaboration (CRC) cards are a brainstorming tool used in the design

of object-oriented software.  They are typically used when first determining which classes are
needed and how they will work

2.3.1 Actor class

Top manager<<actor>>
Name Managing the overall activity of company
Email address
Phone number
Sex

customer<<actor>>
Name Order and receive products
email
Address
Phone number
Sex

16
 Store manager<<actor>>
Name Arrange and manage the products
Email
Phone number
Address
Sex

Order receiver<<actor>>

Name Receive order from customer and send to

Id top manager
Email address
Phone number
Sex
Age

Bank<<actor>>

Name Send debit and credit notification to

Issued branch customer and company
Email
Phone number
Address

Product registration screen<<UI>>

Enable to registering product type

Enables to registering product name
Registering product manufacture date Product registration form
Registering expiration date
Price of products

17
 Log in screen<<GUI>>

Enables user to select

language
Check user name Log in screen form
validation
Check user pass word
validation

Payment screen<<UI>>

Enable user to select

product from product
menu
Display product price System Payment form graphical user
Amount of product interface
needed
Enable user to fill his or
her address information
Enables user to enter
valid credit or visa card

Update screen<<UI>>

Enable store manager to

update product menu
Enable to change Update form
product price by using
product id

18
2.3.2 Business class 

19
 2.4 Identify Actors
Definition of actors

An actor is anything that interfaces with the system externally and participates in use case
modeling.

Customer:

 Collect product

 Check order status

 Maintain account information

 Placing order

 Send feed back

Order receiver:

 Receive order from the customer

 Send information about customer to top manager

Store Manager:

 To change the menu

 Arrange and manage the products before sale

 Enter the system to make any change

 Monitor inventory

Bank System:

 Send account balance notification as credit / debit for both customer and company
manger .

20
Top manager:

 Manage over all activity of company

 Read information send by order receiver and take action

 confirm order

 receive feed back

2.5 Use case modeling

The use case model describes the proposed functionality of the new system. A use case
represents a discreet unit of interaction between a user (human or machine) and the system. A
use case is a single unit of meaningful work. Each use case has adscription which describes the
functionality that will be built in the proposed system. Use case my include another use case
functionality or extend another use case with its on behavior use cases are typically relate to
actors.an actor is a human or machine entity that interacts with the system of perform mining full
work.

21
22
Use case modeling

Use Case 1. Place Order

Name Place order

Actor Customer
Pre-conditions: System is connected to a power source, display is turned on and system is
configured to accept the inputs.

Post-condition: Order has been made that goes to the store for processing

Basic course of action

1. User selects his language preference for the session.

2. User selects from the menu.
3. User selects from the combination of good such as nut oils, corn oils, rep seed etc...
4. User should be able to navigate the system without any difficulty.
5. System supports native language of the country and other commonly spoken languages.
6. User should be able to place order according to his choices.
7. User should be able to make payment using cash/credit/debit card.
8. User should get a receipt and the order.
9. User may want to make up his own order by selecting combination of goods.
10. System takes order from the customer as per his/her choice.

Alternative course of action

User is familiar with how to enter values through password and has a general idea why the inputs
are being provided and what is expected out of system
A.1 User accidentally presses a wrong password.
A.2 User enters a wrong order and wants to go back to the main menu.
A.3 goods cannot deliver at given time.
A.4 the use case an end.

23
Use Case 2. Make Payment

Name Make payment

Actors Customer
Description: The user is asked for the mode of payment. The payment is accepted in terms of
credit/debit card or by cash. And the customer is given a token with their order number.

Pre-condition: The order has been confirmed and the total bill has been displayed on the screen
to the customer. Costumer decides to go ahead with the order.

Post-condition: Customer waits for the order to be processed.

Basic course of action.

1. User selects the mode of payment. (Credit/Debit/ cash)

2. User makes the payment in credit card.
3. User fills all needed information like his or her email, address etc.
4. User makes the payment by credit/debit card.
5. System calculates final bill based on the quantity of the items.
6. System verifies the cash amount and gives receipt notification to customer.
7. System informs user to good through card reader.
8. System will prompt the user for mode of payment
9. The use case an end.

Alternative course of action

A: User is familiar with how the system works and what is expected out of system.
A.1 User selects the mode of payment.
A.2 card reader should be able to read the card information.
A.3 the cards enable to get faster communication.
A.4 the use came to an end.

24
Name change menu

Actor Top manager

Description: The menu might change according to the inventories or add/delete items from
menu and deals. The prices of each item might change for the period of time.

Pre-condition: An order menu with their respective price already exists in the system in some
particular format.

Post condition: a menu list will be displayed when the user enter the system.

Basic course of action:

1. The Store manager enters the system with some password.

2. The Store manager makes the required changes.
3. The Store manager saves the changes and logs out.
4. System offers the choice to change the menu items to the store manager.
5. Store manager decides to add / delete an item from the menu.
6. Store manager wants to put festive offers on some items
7. The system should provide security for customer in order to secure to restrict their
information.

Alternative course of action A

the store manager is given the right and privileges to enter system and make required changes.
A.1 .Some of the menu might not need any change.
A.2. User might enter invalid password and need to go back.
A.3 .any one can get the information given the system.
A.4. the use case an end.

Alternative course of action B

The Store manager is given the rights and privileges to enter the system and make the required
changes.
A.1 any can access item easily.
A.2 the item cannot reach on time
A.3.the system return item that can already delivered.
A.4 the use case come an end.

Use Case 5. Read Order

Name Read order

Actor Top manager

25
 Description: top manager reads the order once the customer confirms his order and then he
communicates the order to order receiver.

Pre-condition: User confirms the order.

Post-condition: The final order is being processed in the internet

BASIC COURSE OF ACTION:

1. Top manager reads the order

2. System communicates the order to through the top manager.

3. The system prints out receipt containing a token number, details of the order, bill
5. The use case an end.

Alternative course of action

An order receiver is available to take the order and know the sequence of processing
the orders.

A.2 user should communicate to top manager

A.2.1. the system prints out receipt containing a token number, details of the order, bill
A.2.2 the use case an end.

2.6 User inter face prototyping

Place where user directly interacts with systems.

26
User interface prototype for placing order

User inter face proto type for reading order form

27
28
User inter face proto type for changing menu

2.7 User interface flow diagram

User interface-flow diagrams are typically used for one of two purposes. First, they are used to
model the interactions that users have with your software, as defined in a single use case.
Second, as you see in figure below they enable you to gain a high-level overview of the user
interface for your application.

29
 

2.8 Supplementary specification

2.8.1 Business rule

Business rule is the rule that our system must be fulfilled while accessed

BR1:. The manager shall be responsible for the safety of all activities on the Site.

BR2: the information of customer must be seen only by the top manager of company and cleared after
the customer received the products

BR3: only authorized person can change the main menu and price of the system

BR4: received message is only accessed by authorized person

30
 2.8.2 Functional Requirements

Functional requirement defines the function of the software .It implies what the system must
do .It describes the inputs, the behavior and the output. And also Functional requirements are
system requirements, in this project which specifies a function and defines behavior of the system that a
system component must be capable of performing tasks on inputs to produce outputs. This project
specifies a function and defines behavior of the system that a system component must be capable
of performing tasks on inputs to produce outputs.

The Functional requirements of this project are listed below:

 Storing all data: - handling all the data in the system database

 provides On line ordering product

 arranging and Checking product on store

 Product registration

 Handle payment notifications.

2.8.3 Non- functional requirements

Non-functional requirements place restrictions on the developed system, the development
process, and specify external constraints that the system must meet.

This requirement considers only the front end values rather than values that have relation with
the database.

Now here nonfunctional requirements according to this system are described:

 The system can perform its required functions under stated conditions for a specific period of
time
 The system shall allow only authenticated users

31
  User shall use web browser to access the system

 User shall be use a mobile phone or a computer that is able to connect to the internet.

 Minor and major errors in the system shall be handled by the system.
 The system shall be modified by the system developers if necessary.
 The system shall be run on any operating system.

Any person will not able to access for changing, deleting and adding something to the system
without authorization of administrator.

2.8.4 Constraints
Constraint is any factor that affect the succession of projects or that left projects not completed at
dead line. In our project there are two main constraints.

1. The time taken to us is not enough to complete the project on time since we are student it is
difficult to collect all available resource

2. Budget is the second factor means since Hamaressa is far from campus the data collection is
require additional time and expense

2.9 Activity diagram:

Activity diagrams are graphical representations of workflows of stepwise activities and actions

with support for choice, iteration and concurrency. In the Unified Modeling Language, activity
diagrams can be used to describe the business and operational step-by-step workflows of
components in a system. An activity diagram shows the overall flow of control.

32
Activity diagram for search

33
Activity diagram for product order

34
Activity diagram for update product

35
Activity Diagram for delete expired product

36
 Fill user name and
password

verify
invalid user name and
password

Valid user nae and

password

logged in

Activity diagram for login

37
 Chapter three

3 Design document
3.1 Class modeling
Class modeling is representation of an object, template of which objects are created. It is
modeled as rectangle with three sections. Class have name and attributes that display full
information of described name and methods that returns value.

Class normalization – refactoring the behavior of classes to increase their cohesion and/or to
reduce the coupling between classes

Class diagram

38
 3.2 Sequence diagrams
Sequence diagram are used to show how objects interact in a given situation. They illustrate the
objects that participate in a use case and the messages that pass between them over time for one use
case. A sequence diagram is a dynamic model that shows the explicit sequence of messages that are
passed between objects in a defined interaction

A popular use for them is to document the dynamics in an object-oriented system User inter face
proto type for changing menu, diagrams are created that show how objects interact in various
representative scenarios for that collaboration. An important characteristic of a sequence diagram
is that time passes from top to bottom: the interaction starts near the top of the diagram and ends
at the bottom.

In a Unified Modeling Language (UML) a sequence diagram is a kind of  interaction diagram that shows
how processes operate with one another and in what order. It is a  construct of a Message Sequence
Chart. A sequence diagram shows object interactions arranged in time sequence. It depicts the objects
and classes involved in the scenario and the sequence of messages exchanged between the objects
needed to carry out the functionality of the scenario. Sequence diagrams typically (but not always), are
associated with use case realizations in the Logical View of the system under development. A sequence
diagram shows, as parallel vertical lines (lifelines), different processes or objects that live
simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in
which they occur.

39
 

Sequence diagram for payment

40
 username System Database

Actor

1.give user name 4.process

and password

2.login to the
system
3.check

5.validate

6.correct
7.incorrect
8.logged in

9.incorrect user
name and
password

Sequence diagram for login

41
 Sequence diagram for customers

3.3 System use case diagram

Associations between actors and classes are indicated in use case diagrams, a relationship exists
whenever an actor is involved with an interaction described by a use case

Exist between use cases

Depicted as a line (arrows are optional)

42
3.4 Collaboration diagram
Depict a bird’s eye view of the interactions between objects S hows the message flow between
objects in an OO application and also imply the basic associations between classes.

43
44
 3.5 Design Phase
Systems design is the process of defining the architecture, components, modules, interfaces,
and data for a system to satisfy specified requirements. Systems design could see it as the
application of systems theory to product development. There is some overlap with the disciplines
of systems analysis, systems architecture and systems engineering.

45
 3.6 A state chart diagram:
State machine diagram or state chart diagram, is an illustration of the states an object can attain
as well as the transitions between those states.

Is used to model dynamic nature of a system

The main purpose of state chart diagram is to model reactive systems

46
47
 State chart diagram for update

3.7 Persistence modeling

Persistent modeling describes the persistent data stored by the system and the data management
infrastructure required for it. This section typically includes the description of data schemes, the
selection of a database, and the description of the encapsulation of the database. Persistence data
model or Entity relationship (ER) models are used to communicate the design of a database,
usually a relational database, to both users and other developers. Persistence are used the schema
of database. The strength of persistence data models is that data entities are conceptually the
same as the table of relation data base and that attributes are the same as table columns.

48
Persistent data management also, deals with how the persistent data (like file, database) are
stored and managed and it out lives a single execution of the system information related to ticket
reservation persistent data, hence stored on a database management system.

Database Design

Databases are the store houses of data used in the software system. A database is a collection of
stored data organized in such a way that the data requirements are satisfied by the database. The
data is stored in tables inside a database. The general theme of database design is to handle
information as an integrated whole, with a minimum redundancy and improved performance.
Regardless of the type of data structure used, the objectives of the database are accuracy and
integrity and successful recovery from failure, privacy and security of data, and good overall
performance.
A table is designed as a collection of rows and columns, which are in turn called as tuples and
attributes. Tuple is nothing but a record in the table. A record is a collection of one or more inter-
related fields. The table is an object of Relational Database Management System (RDBMS),
which is used to store and retrieve the data much easier and faster. The tables should be carefully
designed because the efficiency of the software is based on the effective table design.
Two essential settings for a database are
 Primary key - The field that is unique for all the record occurrences.

 Foreign key - The field used to set relation between tables.

Some tables in our project

Customer Table

Field name Data type Size Primary key Foreign key

49
Customer f name varchar 20

Customer l name varchar 20

Customer email Varchar 30
Phone no Int 54 
country Varchar 23

City varchar 23
Po box Int 14

Top manager Table

Field name Data type Size Primary key Foreign key

Manager f name varchar 20 

Manager l name varchar 20

Email varchar 60

Payment table

Field name Data type Size Primary key Foreign key

Payment id Int 67 

Payment date varchar 77

Payment time varchar 66
Payment amount varchar 54

50
 Product registration Table

Field name Data type Size Primary key Foreign key

Product type varchar 67

Product name varchar 77

Product id Int 66 
Pro manufacture date varchar 54
Product expiration date varchar 23
Product price Int 14

3.8 Entity relationship diagram

An entity-relationship model (ER model for short) is an abstract and conceptual representation of data.
Entity relation diagram is the basic diagram that help designer to design the system. Entity
relation diagram shows the relationship between entities that have common attributes. No need
of writing the common character repeatedly it can easily inherit from another

Entity-relationship modeling is a database modeling method, used to produce a type of conceptual schema
or semantic data model of a system, often a relational database. Diagrams created by this process are
called entity-relationship diagrams or ER diagram

51
 

52
 3.9 Component diagram
UML includes a component diagrams that can be used to analyze and design your component
based software .Components are modeled as rectangles with two smaller rectangles jutting out
from the left hand side.

Implement one or more interfaces, modeled using the same “lollipop” notion that UML class
diagrams use .Components have dependencies on the interfaces of other components, modeled
using the standard UML dependency notation

53
 3.10 Deployment model
Depicted by embedding Nodes or Artifacts. As Artifacts are allocated to Nodes to model the
system's deployment and roll out, the allocation is guided by the use of deployment
specifications. Also there are three deployment models:-

Private cloud -- The cloud infrastructure is operated solely for an organization. It may be
managed by the organization or a third party and may exist on premise or off premise.

Community cloud -- The cloud infrastructure is shared by several organizations and

supports a specific community that has shared concerns (e.g., mission, security requirements,
policy, and compliance considerations). It may be managed by the organizations or a third party
and may exist on premise or off premise.

 Public cloud -- The cloud infrastructure is made available to the general public or a large
industry group and is owned by an organization selling cloud service

54
 Reference
1 Essential system analysis and design 2ed edition Jospph
2 [Ambler 2001] the object primer second edition (scottw.Ambler)
3. OO with c++ edition .by balegurusamy
4.[Hoffer 2000] modern system and analysis and design by Jeffery a Hoffer Fred R .mecfaddan.

55