Chapter One - Two PDF

Download as pdf or txt
Download as pdf or txt
You are on page 1of 53

COLLEGE OF INFORMATICS

Department of Information Technology


An Industrial project On Web based T-Lounge
Service System for University of Gondar
Prepared by:

Name ID

1. Samuel Asamnew…...…………………………………………….01160/12
2. Henok Bikes…….…………………………………………………01145/12
3. Mulusew Melaku………………………………………………….01248/12
4. Edenberg Getachew…….…………………………………………02176/12
5. Fetlework Mohammedzein ……………………………………. 02042/12
6. Yeshiwork Chaklu……………………………………………….. 00750/12

Advisor: Mr. Melaku B.(Msc)

25/08/2015 E.C
GONDAR ,ETHIOPIA
An Industrial project On Web based T-Lounge Service
System for University of Gondar
Name signature

1. Samuel Asamnew ……………….


2. Henok Bikis ……………….
3. Mulusew Melaku ……………….
4. Edenberg Getachew ……………….
5. Fetlework Mohammedzein ……………….
6. Yeshiwork Chaklu ……………….

APPROVAL FORM

This is to certify that I have read this project and that in my opinion it is fully
adequate, in scope and quality, as a project for the degree of Bachelor of Information
Technology

…………………………… ……………………………………….
Name of Advisor Signature

Examiner Name Signature


1. Examiner 1 ………………………………….. ………………………
2. Examiner 2 …………………………………… ……………………….
3. Examiner 3 …………………………………… ……………………….
4. Examiner 4 …………………………………… ………………………

I
Acknowledgement

First of all we would like to praise God for giving us full health and helping us to
prepare this project. Secondly we would like to thank our Advisors Mr. Melaku for
his restless support on the preparations of documentation for T-Lounge Service
System for UOG.

Next to them we have great thanks for UOG T-lounge Workers for their supportive
and giving usable resources to prepare our documentations.

Lastly we would like to thanks our class mate students whom share idea and help us
in any way for accomplishment of our project.

II
Abstract

The principal objective of this project is to demonstrate and automate the capability in
UOG T-Lounge Service to conduct effective, automated, accurately, and
inexpensively services. In this system we would develop a Web based Lounge Service
System that solves the challenges of UOG T-Lounge. The system handles customers’
online order, view order histories, customer registration, receive customer order
request, display payment information and many other functions. For the success of
this project, we used many methods of data collection like interviewing the staffs of
the UOG T-lounge workers. System also includes the use of hardware and software’s
like operating system, DBMS, application software and the likes. DBMS for the
purpose of database implementation, Application software has to develop user and
administrative interface. From this project, we build automatically effective and
efficient system for UOG T-Lounge.

III
Table of content
Acknowledgement ........................................................................................................ II
Abstract ........................................................................................................................ III
List of Tables ...............................................................................................................VI
List of Figures ............................................................................................................ VII
Acronyms and Abbreviations ................................................................................... VIII
CHAPTER ONE: INTRODUCTION ............................................................................ 1
1.1. Background Information of the Organization ................................................. 1
1.2. Motivation ....................................................................................................... 2
1.3. Statement of the Problem ................................................................................ 2
1.4. Objectives ....................................................................................................... 3
1.4.1. General Objective ................................................................................ 3
1.4. 2.Specific Objectives .............................................................................. 3
1.5. Methodologies................................................................................................. 3
1.5.1. Data/Requirement Collection Method ................................................. 3
1.5.2. System development Approach ........................................................... 4
1.6 Development Tools .......................................................................................... 5
1.7. Scope of the Project ........................................................................................ 6
1.8 Constraints ....................................................................................................... 6
1.9. Alternative Solution ........................................................................................ 6
1.10. Feasibility Study of the Project ..................................................................... 7
1.10.1 Operational feasibility......................................................................... 7
1.10.2 Economic feasibility ........................................................................... 7
1.10.3 Technical feasibility ............................................................................ 8
1.11. Proposed solution .......................................................................................... 8
1.12. Significance of the Project ............................................................................ 8
1.13. Beneficiary of the project.............................................................................. 9
1.14 Hardware and Software Tools ....................................................................... 9
1.15 Cost/Budget Estimation ............................................................................... 10
1.16. Work Breakdown Structure ........................................................................ 10
1.17 Time Schedule ............................................................................................. 12
CHAPTER TWO: DESCRIPTION OF THE EXISTING SYSTEM .......................... 14
2.1. Introduction of Existing System ................................................................... 14
2.2. Description of Existing System .................................................................. 14

IV
2.2.1. Drawbacks of the Existing System .................................................... 15
2.3 Overview of activities of the existing system ................................................ 15
2.4. Users of Existing System .............................................................................. 15
2.5 Requirement analysis of the new system ....................................................... 16
2.5.1 Functional Requirements .................................................................... 16
2.5.2 Non-Functional Requirements ............................................................ 17
2.6. System Architecture Diagram ....................................................................... 18
2.7. System Use Case Diagram ............................................................................ 20
2.7.1 Use case diagram ................................................................................ 20
2.7.2. Use case Identification ....................................................................... 23
2.7.3 Actor Identification ............................................................................. 24
2.8. Use Case Narrative ....................................................................................... 25
2.9. Activity Diagram .......................................................................................... 31
2.10. Sequence Diagram ...................................................................................... 34
2.11. Class Diagram ............................................................................................. 38
CHAPTER THREE: DESIGN .................................................................................... 40
3.1. Introduction ............................................................................................... 40
3.2 Process modeling ........................................................................................... 40
3.2.2 Persistence Modeling .......................................................................... 41
3.2.3 Deployment Diagram .......................................................................... 43
References .................................................................................................................... 44

V
List of Tables

Table 1. 1 Development Tools.......................................................................................... 5


Table 1. 2 Cost Estimation.............................................................................................. 10
Table 1. 3 Time Schedule ............................................................................................... 12
Table 1. 4 Teams Role .................................................................................................... 13

Table 2. 1 List of use case .............................................................................................. 21


Table 2. 2 login ............................................................................................................... 25
Table 2. 3 create account ................................................................................................ 26
Table 2. 4 Order foood.................................................................................................... 27
Table 2. 5 Register customers ......................................................................................... 28
Table 2. 6 View food menu ........................................................................................... 29
Table 2. 7 Update food menu ......................................................................................... 30
Table 2. 8 Registration of employee .............................................................................. 31

VI
List of Figures

Figure 1. 1 Work breakdown structure ................................................................ 11

Figure 2. 1 Proposed System Architecture .......................................................... 20


Figure 2. 2 use case diagram ................................................................................ 22
Figure 2. 3 Activity diagram for users’ create accounts ...................................... 32
Figure 2. 4 Activity diagram for users’ login ...................................................... 33
Figure 2. 5 Activity diagram for food order ....................................................... 33
Figure 2. 6 Activity diagram for report generate ................................................ 34
Figure 2. 7 sequence diagram for create account ................................................. 35
Figure 2. 8 sequence diagram for user’s Login.................................................. 36
Figure 2. 9 sequence diagram for customer registration ..................................... 37
Figure 2. 10 sequence diagram for food order ..................................................... 38
Figure 2. 11 class diagram ................................................................................... 39

Figure3. 1 Collaboration diagram for employee registration............................... 41


Figure3. 2 Collaboration diagram for Customers Login ...................................... 41
Figure3. 3 Persistent Database ............................................................................ 42
Figure3. 4 Deployment diagram ......................................................................... 43

VII
Acronyms and Abbreviations

▪ IT : Information Technology
▪ SW: software
▪ UC : Use case
▪ CSS: Cascading style sheet
▪ DB : Database
▪ HW: Hardware
▪ HTML: Hypertext markup language
▪ ID No : Identification number
▪ Admin : Administrator
▪ PHP: Hypertext Preprocessor
▪ UML : Unified modeling language
▪ UOG :University of Gondar

VIII
Web Based UOG T-Lounge Service System

CHAPTER ONE: INTRODUCTION

Information and communication technology has a great effect, especially in developed


countries. But when we see the developing countries still they are using the traditional
system of data communication, data storage, and data movement & transfer so this
influences the development of the country as well as their people. Information
Technologies , which is the convergence of information processing and information
transmission technologies, have a profound effect on every aspect of society. Indeed,
nothing has influenced human civilization as information technologies in modern
times. IT has been changing and affecting communication, trade, business making,
culture, education, service provision, entertainment, research, and other
developmental activities of present society. In a broad, IT has been affecting the way
people live and work. So lounges are one business area that needs IT to computerize
all of the activities inside the lounge. . So we were motivated to develop the web
based T-lounge management system for university of Gondar.

1.1. Background Information of the Organization

The University of Gondar (UOG) was officially established with its current status and
autonomy in 2004. In 1954, the University was initially established as a Public Health
College and Training Centre (PHC & TC), now known as the College of Medicine
and Health Sciences. University of Gondar has five campuses but there are also
community schools and staff residences. This are College of Medicine and Health
Sciences and Referral Teaching Hospital Campus In this campus, Medicine and
Health Science programs and the referral teaching hospital are found Atse Tewodros
Atse Tewodros campus is the main campus of the University. College of Natural and
Computational Science, College of Veterinary and Animal Sciences, Faculty of
Informatics and Institute of Biotechnology are found here. Maraki Campus College
of Social Science and Humanity, College of Business and Economics, School of Law
and Faculty of Education are found this campus. Atse Fasil Campus Institute of

1
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Technology is found this campus. Tseda Campus In this campus, college of


i
agriculture and rural transformation is found . In the main campus there are four
lounges namely Etege mintiwab Lounge which is found around in 50m from males
dormitory building the second one is checheho lounge which is located near to the
president office the third one is gamezone lounges which are found near to the
stadium the fourth one is T-lounge which is found around 40m from females
dormitory building it contains 14 females and 9 males employees. These lounges
gives services like soft drink, hot drink, food etc. for students (it includes non-cafe
students), teachers and academic staffs. All these lounges work their activities like
report generating, food ordering and search mechanism are by manually.

1.2. Motivation

The motivation that initiates us to do this project is the employee works manually, has
work overload, and the customer takes a lot of time to order the food. We have
viewed this problem then we were initiated to change this manual system into a web-
based service system.

1.3. Statement of the Problem

UOG T-Lounge gives services for students manually. It is highly error-prone and too
dull work for employees to handle data and goings-on processes. The manual system
takes a long period to find the data of the employee, foods, and customers. They could
be a misunderstanding due to carelessness in documentation and unclear handwriting.
The report is generated manually takes much time and can’t b always full. Also there
is a security problem because the existing system is a manual system in which the
manager stores the supplied product and customers information in packed paper files
so that the file is highly exposed to damage and can be stolen by any other
unauthorized person and difficult in conducting consistent reports because the record
is documented manually and require much time and human power to search and get
wanted information. So this project is intended on the development of a web-based
lounge service system for UOG T-lounge to solve this problem.

2
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

1.4. Objectives

1.4.1. General Objective

The general objective of the project is to develop a web-based lounge service system
for UOG T-lounge.

1.4. 2.Specific Objectives

To achieve the general objective of this project, the following specific objectives were
addressed:
➢ Gathering required information for the proposed system by using interviews,
observation, and document analysis.
➢ Design a new proposed system to solve the existing problem.
➢ Identify functional and non-functional requirements of the proposed system.
➢ Model the new system using a UML diagram.
➢ Design a user interface for the new system.
➢ Design a database for the proposed system.
➢ Finally, implement and test the new system

1.5. Methodologies

1.5.1. Data/Requirement Collection Method

We used different methods of data collection methods to gather information from both
primary and secondary sources those are: -
➢ Interview –we asked the general managers, users, and employees (waiters) of
UOG T-lounge about the overall activities of the lounge.
➢ Observation –Assessing and analyzing the overall system that has been carried
out by observing the current working system, we have observed the current
working of UOG T-Lounge and how their system (manual system) works and
we have observed how data are handled and information is kept in the
system’s

3
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

➢ Generally, the above data collection tools describe mainly focused on manual-
based activities. Due to this reason, we decide to change manual-based
activities to a computerized system.

1.5.2. System development Approach

A system development methodology refers to the framework that is used to structure,


plan, and control the process of developing an information system.
❖ The system analysis and design approaches for this project we used the object
oriented system analysis & design. Because
✓ It provides code and function reuse through the concepts of
inheritance, polymorphism, encapsulation, modularity, coupling and
cohesion.
✓ To design the system we have choose Object Oriented Modeling
techniques and Unified modeling language tools.
✓ Understanding of the structure is easy because object oriented
modeling and tools used to represent real world entities.
✓ Modification of the object implementation is easy because objects are
loosely coupled.
❖ The system development model for this project we will use iterative model for
the following reasons:
▪ Iterative model: -this model starts from simple implementation of
a small set of the software requirements and iteratively enhances
the evolving versions until the complete system is applied and
ready to be deployed.
✓ It goes to forward and backward.
✓ Used to add new feature on the system.
✓ Reuse concepts of inheritance.

4
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

1.6 Development Tools

To develop the proposed system the following tools will be used during the various
stage of the project life cycle.
Software: - This project uses the following system development tools for different
activities
Tools Activities
Notepad++ For editing code
CSS For attractive layout
PHP for coding
MYSQL data base
Xamp Server Server
Mozilla Firefox, Google Chrome, Opera Browsers

Ms office word For Documentation


Ms office PowerPoint For Presentation
Edraw Max To draw UML Diagram and for designs
Table1. 1 Development Tools

Hardware:
➢ Hard Disk
➢ Flash Disk

5
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

1.7. Scope of the Project

Since the UOG T-lounge performs its basic tasks manually, there are many problems
existed on the system. So to tackle the problems we suggest the following scope
boundaries. Our system only gives service for students, teachers and academic stuff
workers. Those are:
✓ Users order foods online.
✓ Create user account for employees and customers.
✓ Search and Retrieve file from database.
✓ Update records.
✓ Registration of customers and employees.
✓ Allow feedback from any user.
✓ Generate report.

1.8 Constraints

Constraints are restrictions or limitations in the development process imposed by


internal and external factors. This constraints impact the final product, so it is critical
that everyone is aware of them and considers before the project.
⚫ Financial constraint-impacted many areas of the development process, including
tools (specifies what tools to use) and technology.
⚫ Time constraint- deadlines set by department head impacted us how efficiently
finish our work.

1.9. Alternative Solution

An alternative solution is a design solution which differs from the acceptable


solutions given in the approved documents it can include a material, component or
construction method that differs completely or partially from those described in the
ii
approved documents[ ]. An alternative solutions are the various routes you can
pursue to achieve the goal of a project or a particular project management objectiveiii.

6
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

As alternative solution we suggest desktop application, mobile application, phone


call…

1.10. Feasibility Study of the Project

We have analyzed the feasibility of the system in terms of the following:

1.10.1 Operational feasibility

Operationally the system we have to develop is feasible. Mean that the proposed
system will solve the problem and how to ensure success. It is reliable, maintainable
and suitable for user. In addition to that it follow each step how the existing system is
working and our technical skill transform the existing system into a web based and
automated one. The new/proposed system is also compatible to any web browser.

1.10.2 Economic feasibility

Economic feasibility is the process of identifying the financial benefits and costs
associated with the project being developed.
o Intangible benefits
It refers to items that cannot be measurable in terms of money. The following
Intangible benefits are as follows: Minimizing the workload of the employee
(kitchen), Giving moral satisfaction to the user of the system, Reduce Resource
Consumption increasing security, and Increase Management flexibility.
o Tangible benefit
It is a benefit that can be easily measured. Our system will provide tangible benefits
such as:
➢ Cost reduction: The system requires a small number of materials
compared to the existing system.
➢ Improvement in management: The system generates daily reports. So
the manager manages easily.
➢ Increase sales: Because of the system availability many customers
order the food.

7
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

1.10.3 Technical feasibility

Technical feasibility deals with the hardware as well as software requirements.


➢ Assessing the organization’s ability to construct the proposed system
➢ Takes into account various project risk factors

We have to find out whether the necessary technology and proposed equipment have
the capacity to hold the data used in the project. We have learned different types of
courses such as advanced database system and PHP programming language to fill the
gap of technical operation of the lounge service system.

1.11. Proposed solution

The new proposed system is aimed to have a login interface for all customers (non-
cafe students and other students who are not non-cafe), manager, system admin,
cashier, waiter, and kitchen, by inserting valid user name and password will log in to
the system. The proposed system works over a networked environment. After login
users view daily food menus and based on daily menus order the food, view order
history, give comments, and logout. The proposed system will enable to retrieve,
insert, delete and modify needed information simply for the admin. It includes an
attractive user interface that facilitates fast access to the database and generates
reports easily. Generally, the new system will eliminate/reduce problems related to
time accuracy, speed, security, and complexity in information searching, accessing,
and retrieving.

1.12. Significance of the Project

The main benefit of this system as it is computerized web-based system:


▪ It initiates and increases employee confidence to do their task properly.

8
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

▪ It makes the lounge efficient and more profitable in a short period of time, as it
follows fully automated system and has many customers.
▪ It saves the customer’s time when they want to access service from the lounge.
▪ The Customers uses the system safely and gives comfort for them.
▪ It increases performance of the lounge.
▪ Generates more secured information for each customer.

1.13. Beneficiary of the project

The first beneficiaries of these proposed systems are customers, employees and our
group member. We have knowledge on how to access information from the lounge. In
addition, solve the problems of customers to get full access from the lounge.

➢ for managers
➢ for students
➢ for teachers
➢ academic employees
➢ for Gebi mamenchiya and mastebaberiya
The proposed system can let our users to order online right where they are they don't
need to travel and not supposed to wait so its time saving and interesting

1.14 Hardware and Software Tools

We would use different software and hardware components.


Software tools:
Front end:
➢ Microsoft Office: To write documentation of the system.
➢ Windows operating system: Platform used to do both documentation and
implementation.
➢ E-draw Max: Used to draw UML diagram
➢ Snipping tool: Used to snipe diagrams of the system.
➢ Web code: to writing implementation.
Server Side (back end):
9
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

➢ XAMPP Server: To create, store and retrieve files to/from the database.
Intermediate:
➢ PHP
Hardware Requirements:
➢ Desktop and Laptop computer: To work documentation, implementation, and
access the internet.
➢ RAM Size 4GB
➢ Hard disk size- 465.75GB
➢ Flash disk size-32GB

1.15 Cost/Budget Estimation

Type of Quantity single price total price


RESOURCES
Pc &laptop 2 15000 30,000
Flash 2 300 600
Pen 2 25.00 50.00
Ear pod 1 1700 1700
TOTAL 32,350
Table1. 2 Cost Estimation

1.16. Work Breakdown Structure

The work breakdown structure of the UOG T-lounge system is expressed below in the
diagram

10
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Figure1. 1 Work breakdown structure

11
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

1.17 Time Schedule

The scheduling feasibility involves how much time is available to build the new
system when it can be built interference with normal business operations etc. The time
set to develop the system is enough to complete the project on time.

Task Start Finis Dur 2015/06/ 2015/0 2015/07/13 - 2015/07 2015/08


Name h atio 25 - 7/5 - 2015/07/24 /25 - /25 -
n 2015/07/ 2015/0 2015/08 2015/08
03 7/12 /05 /05
Title 2015/ 2015/ 8d
selecti 06/25 07/03
on
Requi 2015/ 2015/ 7d
remen 07/05 07/12
t
gather
ing
Requi 2015/ 2015/ 13d
remen 07/13 07/24
t
analys
is
Desig 2015/ 2015/ 10d
n 08/8 08/01
8
Docu 2015/ 2015/ 1d
menta 08/25 08/25
tion
presen
tation

Table1. 3 Time Schedule

12
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

The team’s role to accomplish this project, we do all activities together.

ID Number Name Task Group meeting


01160/12 Samuel Asamnew
01145/12 Henok Bikes
Monday
(morning)
02176/12 Edenberg Getachew
All work is done
02042/12 Yeshiwork Chaklu by the all group Wednesday
(afternoon)
01248/12 Mulusew Melaku members
00750/12 Fetlework
Mohammedzein
Table1. 4 Teams Role

13
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

CHAPTER TWO: DESCRIPTION OF THE EXISTING


SYSTEM

2.1. Introduction of Existing System

The Current system is a manual system that needs intensive human labor and
consumes time. Customers order by using tickets that contain thicket number and
food type and the registration of non-cafe students is recorded manually. If they want
to update these files and records, the searching activity is tedious. Here there is no
legacy system in this lounge so we cannot show some demos or scenarios on the old
system. So, we are trying to show how the manual system is working in this lounge.
The student goes to the lounge and stands in front of the cashier and orders the food
from the cashier then the cashier receives birr from the student and gives Bono if the
students order hot drinks then the student goes to the Barista and gives the Bono to
him then the Barista will give the hot drink to the student but if the student order food
the cashier gives thicket to student and kitchen then finally the waiter call the student
and the student receive the food. In the case of the non-cafe student first, the student
registers on the agenda and records the ordered food on the agenda and ticket by using
waiters then the waiters give the ticket to the kitchen finally the waiter call the student
by name and give the food. Generally, the existing system uses a manual way of
implementing tasks and information sharing. This is an inconvenience in terms of
providing integrated service.

2.2. Description of Existing System

The existing system at UOG T-lounge services uses a manual system. Those activities
of the existing system are:-
➢ Register non-cafe students on the agenda and record daily order food on the
agenda by a waiter then the waiter gives thicket to the kitchen after preparing
the food the waiter calls the student and gives the food.
➢ The existing system also uploads daily food menus and collects payments
from customers manually.
➢ In the existing system, the cashier also reports daily income to the manager.

14
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

2.2.1. Drawbacks of the Existing System

A. Information Problem
Due to the manual collecting of data, there are redundant records and inconsistencies.
The inaccuracy of data and information may be produced.
Lack of a well-organized database system
B. Registration related problem
The food registration is done manually. This, in turn, will result in poor techniques for
handling the data. The Data can be lost or redundantly registered.
Relying on a manual ordering process or a paper-based system will never improve the
business processes and can jeopardize your business growth.
C. Efficiency Problem
The efficiency of the existing system is not optimal, because the ordering takes much
more time
It is also a labor-intensive process.

2.3 Overview of activities of the existing system

The existing system at UOG T-Lounge services uses manual system. The first
activities of existing system, registration of non-cafe students in the form of paper to
give detail personal information, another activity of the existing system is generating
reports, uploading daily food menus and collecting payment from non-cafe students
and any user’s cash.

2.4. Users of Existing System

There are different users in the existing system:-


1. Customers - customers are the system users which can get service from the lounge.
They view the type of food from the menu and order
Make payment in cash to the cashier.
2. Cashier:-cashier is a person which is responsible for:-

15
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Give tickets for the students/customers


Report the sold food daily in the paper
3. Managers:-Register employees
4. Waiters:- is persons who deliver the foods and have the following duties:
Call customers/students.
Deliver the food to the students/ customers.
5. Kitchen: are persons which are preparing food.
View order histories and prepare food based on the type of ordered food.
6. Baristas: are persons who prepare hot drinks like tea.

2.5 Requirement analysis of the new system

2.5.1 Functional Requirements

Functional requirements are the desired operations of a program, or system as defined


iv
in software development and systems engineering . Functional requirements describe
the interactions between the system and its environment independent of its
implementation. The environment includes the user and any other external system
with which the system interact functional requirements that must be included in the
system are:
A. System admin: The system allows:
FReq1. To manage account
Freq2.To creates user account.
B. Manager: The system allows.
Freq1. To register an employee.
Freq2. To View report.
C. Customer: The system allows -
FReq1. To make payment
Freq2. To give comments,
Freq3. To view menu items.
Freq4. To Order based on menus,
D. Cashier: The system allows:

16
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

FReq1. To update food menu item


Freq2. To view comments.
Freq3. To view notification
Freq4. To check payments.
E. Kitchen: The system allows to -
FReq1. Update account
Freq2. View order.
Freq3. Receive notification.
F. Waiter: The system allows to:
FReq1. Receive notification sent from the manager.
Freq2. View order.
Freq3. Update account.
G. Barista: The system allows to:
FReq1. Update account.
Freq2. View order.
Freq3. Receive notification.

2.5.2 Non-Functional Requirements

Non-functional requirements or NFRs are a set of specifications that describe the


system's operation capabilities and constraints and attempt to improve its functionality
v
[ ].
Performance

There might be many users accessing to the web server simultaneously. As an online
food order tool performance shouldn’t be affected much and the response time for
submitted page should be less than a minute. The performance of our system is also
measured in terms of load time and response time. The system performance will be
highly responsive because of by query optimizing, normalizing tables and making
client-side validation which is very important to check user’s data validation before
navigating to model or database and it support concurrent user at time.
Response Time: Upon request for user inquiry the system under normal condition
should display results as quickly as possible.
17
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Processing Time: Since the system is developing with efficient programming


language and database upon request for user’s activities the system under normal
condition should process the request as quickly as possible.
Work ability: The system should be suitable for all users. It should be accurate in
performing its functions and secured enough from attacks by external users.
Correctness: The system provides correct response to the correct request.
Concurrent Processing: Because the proposed system is web based can execute
multiple users.
Concurrency: The system should support multiple accesses of users. It should give
service to multiple users concurrently.
Reliability

The proposed system will minimize crash during its run time, since more than one
user could use the system simultaneously. The system should be reliable and matured
enough in giving its service. It should have a fault tolerance mechanism in which it
can recover fast from problems that may occur.
Availability
The system should have to be functional at any given time (the system is available in
24 hours a day and seven days a week). There is no delay in the availability of any
information, whatever needed, can be captured very quickly and easily using more
than one server. The server should be always on to be available. The system shall
support the use of multiple users at a time and understandable by all users.

2.6. System Architecture Diagram

➢ Current System Architecture


System design is the transformation of the analysis model into a system design model.
Up to now, we were the existing system of UOG T-lounge service system is not web-
based and hence there is no current software architecture that will be considered. As a
result, we only describe the software architecture of the proposed system.

18
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

➢ Proposed System Architecture


We use client/server architecture. The system uses the browser to interact with the
web server using HTTP. The client-side server interface and the database server are
where all information is stored and can be accessed by authorized parties. we selected
three-tier system architecture because a Three-tier architecture allows any one of the
three tiers to be upgraded or replaced independently.

➢ Client Tier/ Presentation tier


On the client-side, it includes users. For example System manager: Manages
schedules, registers employees, and supervised employees. Casher: responsible for
updating the food menu, generating the report for the manager, and checking
payment. Customer: responsible for ordering food items, giving comments, etc.…

➢ Data Tier/Database tier


The system uses two databases; the first database is the repository consisting of the
application data. It is here that all the database tables will be stored. And the second
database stores the money transaction.

➢ Application tier
The middle tier will contain the core parts of the facility management system, i.e., the
web server. The web server will handle all requests coming from the client machines.
The requests are different in their type, for example; requests for data insertion,
requests for report generation, and others. It is also the web server that the responses
are forwarded to the client machines.

19
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Figure2. 1 Proposed System Architecture

2.7. System Use Case Diagram

A use-case Design is a model of how different types of users interact with the system
to solve a problem. As such, it describes the goals of the users, the interactions
between the users and the system, and the required behavior of the system in
satisfying these goals. A use case diagram is a way to summarize details of a system
vi
and the users with in system [ ].
A use-case model consists of a number of model elements. The most important
model elements are: use cases, actors and the relationships between them System
boundary: indicates the scope of the system project. Anything within the box
represent functionalities in side inscape.

2.7.1 Use case diagram

As use case is a list of steps, typically defining interaction between a role or actor and
the system to achieve a goal some of the use cases of our system are the following:-

20
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Use case number Use case Name

UC-01 Login

UC-02 Create Account

UC-03 Order food

UC-04 Register customer

UC-05 View food menus

UC-06 Update food menus

UC-07 Register employee

Table2. 1 List of use case

21
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Figure2. 2 use case diagram


22
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

2.7.2. Use case Identification

Use case: describes a sequence of actions that provides something of measurable


value to an actor and is drawn as a horizontal ellipse.
1. System administrator: System administrator is a person responsible at the top
management of the system who performs the following tasks:
➢ Create a user account.
➢ Backup database
➢ Restore database.
2. Manager: - is a person who manages all activities of the lounge and he/she is
responsible for the following activities:
➢ Register employee.
➢ View report.
➢ Manage account.
3. Customers: - customers are the system users which can get service from the lounge
and is an entity which is responsible for the following tasks:
➢ View menu item.
➢ Order food,
➢ Give comments,
➢ Make payment.
➢ Update account.

4. Cashier: cashier is an entity which is responsible for the following tasks:


➢ Update menu item.
➢ Check payments.
➢ Receiver notification sent from customer.
➢ View comment.
➢ Update account.
5. Waiter: persons which deliver the foods and have the following duties:
➢ View order.
➢ Update account.

23
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

➢ Receiver notification.
6. Barista: are persons who are preparing tea and coffee. The responsibilities of the
Barista are:
➢ View order histories.
➢ Receive notification.
➢ Update account.
7. Kitchen: are persons which are preparing foods. Responsibilities of the kitchens:
➢ Receive notification.
➢ View order.
➢ Update account.

2.7.3 Actor Identification

Actor: is a person, or external system that plays a role in one or more interaction with
the system and represented with the system.
There are many actors in UOG T-Lounge Service System. Those are described as
follows.
1. Manager: - is a person who manages all activities of the lounge.
2. System administrator: System administrator is the person responsible at the top
management of the system.
3. Customers: - customers are the system users which can get service from the lounge.
4. Cashier: cashier is person responsible for check payments.
5. Waiter: persons which deliver the foods to the customer.
6. Kitchen: are persons which are preparing foods.
7. Barista: are persons who are preparing tea and coffee.

24
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

2.8. Use Case Narrative

Use case Name Login

Use case number UC-01

Actor Admin, Manager, Customers, Cashier, Waiter, Kitchen and Barista.

Description: Users are authenticated and taken to their own user interface based on the
given privilege

Pre-conditions Users must have a valid user name and password.

Post condition The user is authenticated and taken to his/her own user interface.

Basic course of User action System response


action 1The user opens the
Homepage.
2. The user clicks the login
menu. 3. The system will display the login form.

4.The user enters correct


username and password. 6. The system will check the user name and
5. The user clicks on the password is entered correctly.
login button. 7. If valid display message “successfully
login”
User action performed and the wanted page
displayed.
8. End-use case

Alternative If 6 is not true. The System display Error Message and return back the
course of action user to step 4.

Table2. 2 login

25
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Use case Name Create account

Use case number UC-02

Actor System administer

Description: The administrator creates an account for Manager, Customers, Cashier,


Waiter, Kitchen and Barista.
Pre-conditions System Administrator Login to the system

Post condition Account Created Successfully

Basic course User action System response

of action 1. The system admin click on the create


account button. 2. The system will display the user
account creation form.
3. The system admin fills the form.
4. The system admin must enter eight
character password and username.
5. The system admin clicks on create
count button. 6. The system will check the filled
form.
7. The system will display “account
created successful message”.
8.End use case

Alternative If admin misses the required field or entered wrong data, the system notifies
course of action “the missed field or wrong data” and the process continues from step 3

Table2. 3 create account

26
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Use case name Order food


Use case number UC-03
Actors Customer.
Goal To order based on daily food menus that uploaded by the cashier.
Basic course User Action System Action
Action 1. Users click ‘food menus
button. 2. The system displays daily food menus.
3.click on ‘view button’ 4. The system checks available dailyfood
menus.
5. If food available display the found food
6. click on ‘order button’ picture with cost.

8.The customers choose quantity. 7 .The system displays quantity and cost.
9. The customer click on pay
button. 10. The system displays payment option.
If the customer pay in bank. He
click bank button. 11. The system checks payment.
12.If paid the system display “the food is
order successfully”
13. Use case end.
Alternative If 4 and 13 are not true order will fail and nothing changed return to step 1 of
action the flow of events.
Post condition Users must be pay before order the food.
Special Users must be registered correctly.
requirement
Table2. 4 Order food

27
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Use case Name Register customers

Use case number UC-04


Actor Customers

Description: Register customers

Pre-conditions must open home of the website

Post condition Customers registered.

Basic course of action User action System response

1. The customer clicks on the


sign-up button. 2. The system will display a
sign-up form.
3. The customer fills the
sign-up form.
4.The customer clicks on the
Sign-up button.
5. The system will check the
filled form.
6.If all necessary form is
filled,display“successfully
registered message”
End use case
Alternative course of If 6 is not true registration will fail and nothing changed Return to
action step 3 of the flow of events.
Special requirement Registration information should been entered correctly
Table2. 5 Register customers

28
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Use case name View food menus.


Use case number UC-05
Participation actors Customer, Waiter, Barista, Kitchen, Cashier
Pre-condition Open the web page and login in his/her account
Post condition Users view food menu.
Basic course User Action System Action
Action 1. Users click food menus
button. 2. The system displays daily food menus.
3.click on ‘view button’
4. The system checks available foods. daily food
menus,
5. If food available display the found food picture
with cost.

6. Use case end.

Alternative course If the food not appears the process continues from step 1 and display the food
of action doesn't exist.
Exit condition User may logout from the system
Table2. 6 View food menu

29
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Use case name Update food menus.

Use case number UC06

Participation actor Cashier.

Entry condition Cashier login to the system and open existing report on the
registration food menus.

Goal To update the data which registered before

Basic course action User action System action

1. Click on update button


2. system display update form
3 Insert the id no. to be
updated detail.
4. Change the new value that
the form must have.
5.Click on update button 6.system check validity
7.If valid “successfully update
“message will be displayed
8 use case end

Alternative action If 6 is no true the field is missed then will not update

Post condition Save the updated data

Exit condition Cashier logout from the system

Table2. 7 Update food menu

30
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Use case name Registration of employees


Use case number UC-07
Participation actor Manager
Goal To register customers and employees the purpose of security.
Entry condition Open the web-page and login in his/her account.
Basic course Action User Action System Action
1. Clicks on ‘customers and
employees Registration form’. 2. System displays
the form.
3. Fill Registration form.
4. Check the validity
of the data inserted.
5. Click on register button.
6. If all necessary
form is filled
“successfully
registered” message
will displayed.
7. Use case end.
Alternative action If 6 is not true registration will fail and nothing changed
Post condition The customers and employees will be registered on the
database
Special Registration information should be entered correctly
requirement
Table2. 8 Registration of employee

2.9. Activity Diagram

Activity diagrams are graphical representations of workflows of stepwise activities


and actions with support for choice, iteration and concurrency. So use to describe the
flow of activities and a series of actions in a system similar to a flowchart or a data
vii
flow diagram. Activity diagrams are often used in business process modeling[ ].
Activity diagram is essentially an advanced version of flow chart that modeling the
31
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

flow from one activity to another activity. Some of the activity diagram for our
project is listed below.

Figure2. 3 Activity diagram for users’ create accounts

32
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Figure2. 4 Activity diagram for users’ login

Figure2. 5 Activity diagram for food order


33
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Figure2. 6 Activity diagram for report generate

2.10. Sequence Diagram

Sequence diagrams show the interaction between participating objects in a given use
case. They are helpful to identify the missing objects that are not identified in the
other analysis object models. A sequence diagram consists of a group of objects that
are represented by lifelines, and the messages that they exchange over time during the
viii
interaction [ ].

34
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Figure2. 7 sequence diagram for create account

35
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Figure2.8 sequence diagram for user’s Login

36
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Figure2. 9 sequence diagram for customer registration

37
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Figure2. 10 sequence diagram for food order

2.11. Class Diagram

Class diagram in the Unified Modeling Language is a type of static structure diagram
that describes the structure of a system by showing the system's classes, their
attributes, operations, and the relationships among objects. A class diagram is an
illustration of the relationships and source code dependencies among classes in the
ix
Unified Modeling Language (UML)[ ]. You can use class diagrams to model the
objects that make up the system, to display the relationships between the objects, and
to describe what those objects do and the services that they provide. Class diagrams
are useful in many stages of system design. You can use class diagrams to visualize,
specify, and document structural Features in our models.

38
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Figure2. 11 class diagram

39
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

CHAPTER THREE: DESIGN

3.1. Introduction

In the problem domain the System design is the first part to get into the solution
domain in software development. The main purpose of system design is to determine
how the system is going to build and to obtain the information needed to direct the
actual implementation of the system. It focuses on understanding the model of how
the software will be built. Generally, this chapter is describing how the project is
designed, and what tasks are done under this project.

3.2 Process modeling

3.2.1 Collaboration
A collaboration diagram is visual representation of the relationships and interactions
among objects in the unified modeling language. A collaboration diagram, also
known as a communication diagram, is an illustration of the relationships and
x
interactions among software objects in the Unified Modeling Language (UML)[ ].

40
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Figure3. 1 Collaboration diagram for employee registration

Figure3. 2 Collaboration diagram for Customers Login

3.2.2 Persistence Modeling

The purpose of physical design is to translate logical description of data into technical
specification for storing and retrieving data the goal is to create design for storing data
that will provide adequate performance and data integrity, security and recovery.
Physical data model represents how the model built in the database. A physical
database model shows all table structures, including column name, column data type,
column constraints, primary key, foreign key, and relationships between tables.

41
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

Figure3. 3 Persistent Database

42
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

3.2.3 Deployment Diagram

A deployment diagram is a UML diagram type that shows the execution architecture
of a system, including nodes such as hardware or software execution environments,
and the middleware connecting them. Deployment diagrams are typically used to
xi
visualize the physical hardware and software of a system[ ].

Figure3. 4 Deployment diagram

43
Industrial Project Information Technology
Web Based UOG T-Lounge Service System

References

i
https://uog.edu.et/
ii
https://www.projectmanager.com/blog/what-is-alternative-analysis
iii
https://www.projectmanager.com/blog/what-is-alternative-analysi
iv
https://www.techtarget.com/whatis/definition/functional-requirements
v
www.altexsoft.com/blog/non-functional-requirements
vi
https://www.techtarget.com/whatis/definition/use-case-diagram
vii
www.smartdraw.com/activity-diagram/
viii
https://www.ibm.com/docs/sk/rsm/7.5.0?topic=uml-sequence-diagram
ix
https://www.techtarget.com/searchapparchitecture/definition/class-diagram
x
https://www.techtarget.com/searchsoftwarequality/definition/collaboration-diagram
xi
www.creately.com/guides/deployment-diagram-tutorial

44
Industrial Project Information Technology

You might also like