Documentation PDF

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET
/2007
CHAPTER ONE
1. Introduction
1.1Background
Ambo university consumer coop super market is one of the parts of AU service. Ambo
university consumer coop super market is established in 2002 E.C.
This organization gives service to the customer .the main purpose of the super market is
provide service to the costumer in optimum price. One of main purpose of AU producing
skill people and giving service to the community .this consumer coop supermarket is leading
by professionals people they perform many research to solve the community problems .this
supermarket service is greatly related with this society day to day life. The university
performs main society based research to solve the society problem from this consumer super
market is one of the best practical achievements.
The case study of Ambo university consumer cooperation supermarket that how do they
evaluate and judge its employees will be carried out in form of research on the upcoming
years. This consumer cooperation supermarket is a subsidiary of ambo town and one of the
leading retail stores of Ambo University. In more than one stores consumer cooperation
supermarket are usually 5-10 plus employees working in different shifts. Consumer
cooperation supermarket is became a part of in ambo university more than 7 years ago. All
these can be due to the fact that it has a strong friendly policy that includes staff discounts,
money off vouchers, plus other benefits. The other key factor that plays an important part in
retention is the ability to progress from a supermarket manager.
Information Technology
page 71
/2007
1.2 Statement of the problem
The existing working process for the supermarket management has the following
problems:
It is difficult to retrieve product and its information when it is required.

It needs huge human power.
There is no centralized database system.
There is loss of product data because they placed product data in different places.
Customer crowded
Wastage of time and money customers
Take more working space
It is difficult for supper market managers to search and announce the products price
that exist in the supermarket.
1.3 Objective of the project

1.3.1 General objective
The main objective of this project is to develop the web application for ambo university
consumer cooperation supermarket management system.
1.3.2 Specific objective
After the successful completion of this project the software will provide the following
application (services):
To register new product

To record customer history(information)
To upload product information
To provide online access: customers can get full information about supermarket service.
To provide Online marketing and reservation of service:
Customers can payed by which they can access the internet access from anywhere.
To provide real time delivering service

Updating product and customer information
page 71
/2007
1.4 significance of the project
To keep records of the customer and product in the database

To develop computer based online management system
To overloading of jobs
To save time
Facilitating online marketing
Easily accessing of product information
Will Increase the income of the organization: as long as the system satisfied the users,
the customers will increase.
Reduce the work load: cause the paper based system replaced by the computerized
one.
Our country can get currency from local and international customers.
1.5 Scope of the project and limitation

1.5.1 Scope of the project
Scope of the project is developing website for consumer coop supermarket.

The system going to carry out the following tasks:
Online Registration and reservation of product for the customers.
Update and registration of products in computerized system.
1.5.2 Limitation of the project:
LAN: the system will not concern about installation of network.

Training: the system will not give training about the system how it works or how to
access the system to the users.
Web site promotion: Promotions about other websites will not be performed. This
project concern about only the system of car renting. It does not include any
promotion of website.
Insurance: System does not provide detailed information about the process of
insurance.
page 71
/2007
1.6 Methodology
1.6.1 Requirement gathering method
Data about the organization will be collected using Observation, Document Analysis and
interview. Because this methods help us to get full and clear information about the
organization in easy way.
1.6.1.1 Observation
We are used in order to analyse the conditions to which the existing system is acting. We are
collect useful information how jobs are done and how information flows directly from the
user is observed.
1.6.1.2 Document Analysis

We studying the documents that are used in the past, in order to understand about the
problems in the existing system, rule for processing data etc.
1.6.1.3 Interview
Interviewing the employers and customers to have reliable and clarified information from the
users, managers, workers of the company .It will be used assure the information which is
observed from documents, forms, and reports etc. It enables to understand the feeling or
interest of the interviewer directly.
1.6.2 Requirement modelling
We try to use waterfall model to show the process in phases. The output of one
phase in the waterfall model is the input to the other phase. There is a sequential
and linear flow among the process. There are standards set for the output of each
process. If one output is wrong it disturbs the entire model.
OOA (object oriented analysis): This is an entirely different approach in to
information system.
1.6.3 Development tools
1.6.3.1 Software
After having all required data and information, different programming tools will be used
in order to design and represent the new system. This includes
Database server:-this is the most crucial requirements of the new system use MySQL
for the database.
Dreamweaver
Web server: apache running multiple processes to have them ready when a client
request comes in.
Editing /documentation/ software: MS notepad++would be used as documentation
and for other text editing.
Client side script: JavaScript
Adobe Photoshop
Internet explorer
page 71
/2007
Mozilla Firefox
Opera
Google chrome
1.6.3.2Hard ware
Personal computer
Cd: to store the file.
Flash disk: to store a file.
Printer: to print the document of the project.
Digital camera: to take necessary pictures for developing the website.
Scanner: to change pictures from hard copy to soft copy.
1.7 project budgeting
Project funding summary

The project budget information is an important part of every project proposal and must be
completed prior to consideration of a proposed project for funding.
To do this project we budget one hundred eighty thousand (180,000) birr.
Total cost(local currency)
Funding source
Funding plan
Proposing organization
By showing
proposal
Ambo university
Requesting to allocate budget
50,000
Other co financer
By promotion
50,000
Total project cost
the
project 80,000
180,000
Table 1.1 project budgeting
page 71
/2007
1.8 project schedule
Dec 2014
ID
Task Name
Start
Finish
Jan 2015
Feb 2015
Mar 2015
Apr 2015
May 2015
Jun 2015
Duration
12/7 12/14 12/21 12/28 1/4 1/11 1/18 1/25 2/1 2/8 2/15 2/22 3/1 3/8 3/15 3/22 3/29 4/5 4/12 4/19 4/26 5/3 5/10 5/17 5/24 5/31 6/7
1 Chapter 1
12/8/2014 12/15/2014 1.2w
2 Chapter 2
12/16/2014 12/30/2014 2.2w
3 Chapter 3
1/1/2015
1/14/2015
2w
4 Implementation
1/15/2015
6/8/2015
20.6w
5 presentation
6/17/2015
6/16/2016 52.4w
1.9. Project Organization
Our project team organization structure is also decentralization .this best team
structure, participate all member s in the group.
Responsibility
Facilitator
Members
Proposal
All members
All members
System analysis
All members
All members
System design
All members
All members
Implementation
All members
All members
Table 1.2 project organization
page 71
/2007
CHAPTER TWO
System Analysis
2.1 Major function of the current system
The current systems of ambo university customer cooperation supermarket use manual
system. This super market cannot give full service to the customer because of they are not
fulfill customer satisfaction. The customer directly comes to the store and buys the service.
When the customer comes to the super market they have lose some things such as time,
money and human labor. They maintain (record) product, customer and employee
information using pen and paper. This has great problem on the consistency of the system.
1. Customer registration
When the customer buying to the product in the super market at that time employees register
the customer.
2. Report
The employee report to daily, weekly and monthly to the manager which product is sold,
some products immediately required for the customer and type of product completed or
finished.
3. Product Registration
The employee to register new Products, selling products and complete products of the super
market of Ambo University and also, the employee update status of the Product list
2.2 problem analysis /definition
Manual system is not secured because of the document is paper based; the document is lost
or damaged. If the documents are lost, damaged or theft by other person leads to endangers
the customers .this means customer information are lost. Even the organization also
endangers by the cause of left their communication with the organization.
Customer must go to the organization from anywhere. So this system consumes time and
money. If you want to buy you must go to the organization you may use a transport like taxi,
this causes for extravagance of time and money.
The problem in the existing system is solved by automated system. For example, identifying
the product price, customer id, and circulation of the employees, done by using the new
system. This automated system saves time and reduces human power
page 71
/2007
Generally the Existing System has the following Problems:
Performance: - It is time consuming and less performance since every task is

done manually and it has taking much time and to complete the task requires a
long period of time.
Regarding on lack of speed the system will generate output with slow speed.
Information: - Redundancy of data.

-Not accurately captured.
Efficiency: It operates over specified long period of time interval. Generally,

the above current system mentioned is inefficient.
Service: It takes more time to give as well as get the services both the
workers and users
Security: It is not secured because it has not guard.
This frame work is used to identify the problems with in an existing Dormitory System.
2.3 user needs
We see user needs from two aspects, one from the workers aspect and on the other hand from
the peoples that get services (customer).
Workers aspect: since every activity was performed manually the workers doesnt provide
well service to their customers and feel lack of work satisfaction while if the system will
changed with automated system they make sure that totally their work activity will change
accordingly; and get work satisfaction with their work activities and they can get much more
time to give services for many customer.
Work space also reduced, retrieving, dealing with the customer data also so easiest to.
From customer aspects: since the workers perform their services manually they spend
much time on dealing with only a single customer then, almost 25% if the customer will
wait some long queue on almost all customer; due to this most of the customer doesnt get
service timely. Due to this all the users ensure that if the system is changed to automated
system than every activity (services) will gain timely and believe that the workers
provides such enough service to them.
Generally the users need the system to be having the following things:
The system shall provide a friendly user interface with attractive
The system shall provide easy access, storage
System shall offer security to the stored information through the use of password to
control access to the information
System shall accept data and modification by authorized users
System should be able to store large quantity of data in a central location
page 71
/2007
System is expected to give result in a reasonable amount of time

Protect the users from moving errors like inserting invalid data
Provide easy navigation for users
2.4 Requirement
analysis of the existing system
The requirement analysis of the existing system in ambo university super market
cooperative system is
A, Selling:
The employee to sell the product to the customer
B, Audit:
They can check the selling and the remaining products
They can calculate the income and expense of money
They can checks the expired product
2.4.1 Essential use case modeling:
is also called business use case; simply abstract, generalized use case that capture the
intentions complete, meaningful and well-designed form the point of view of users in some
role, or roles in relation to system and that embodies the purpose or intentions underlying the
interaction.
2.4.1.1 Actors involve in the existing system

1, Manager
2, Employee
3, Customer
2.4.1.2 Essential user interface prototype

Are the models of graphical user interfaces for software programs. User interface prototype
shows the structure of an interface and the relationship between individual screens; and also
used to define the structure, content and functionality of the software application, used to
conduct usability of testing. For this consumer cooperation supermarket we identifies the
following essentials user interfaces
2.4.2 The supplementary specification:
The system GUI should be consistent with a specific browser.
All the icons and buttons used in the program should be consistent throughout the program.
The GUI should be easily customizable.
The GUI should be easily understandable.
page 71
/2007
The systems in general have a good graphical user interface that enables the users to
Use it easily and in efficient manner.
Business rule: A business rule defines or constrains one aspect of your business that is
intended to assert business structure or influence the behavior of your business.
Name: manager
Identifier: - BR1
Description: control and manage all activities of the super market
Receive product with full information

Generate report
Name: employee
Identifier: BR2
Description: register product and customer
Sell product
Preparing bill
Name: customer
Identifier: - BR3
Description: view product information
Buy product
Constraints: A constraint is a restriction on the degree of freedom you have in providing a

solution.
Time limitation
Financial capacity
Working place
2.5 alternative solution
The current system of cooperation super market service has disadvantages that limit the
performance, efficiency and speed of system.
The current system of cooperation super market has advantages
It takes less time to perform activities, availability of full service.
Improve quality of the company service and have fast response time.
Reduce time consuming
page 71
/2007
Decrease a lot of/multiple paper works.
2.5.1 Automated system
The system worked totally in computerized and web based system. This system was
designed to solve all problems that are phased in the existing system and activity has great
change on the consistency of the system.
2.5. 1.1 FUNCTIONAL REQUIREMENTS

The system totally acted in terms of manual system. This activity has great change
on the consistency of the system.
The supermarket management system must support the following functional
requirements.
Record (add)
The new proposed system has to allow the supermarket manager to login into the
system before doing anything. After log into the system, system has to allow the
manager to manage product, customer and employees data and register new
product, customer and employee.
Delete
The system should allow the supermarket manager to delete the unwanted
product, customer and employees data from the database. This activity will
include deleting of the sold product data when they leave the dorm and deleting of
the employees data when they leave the university.
Update
The system should allow the supermarket manager and the employee to update the
product and customer data when changes are made.
Search
The system should display the information when it is required. When the user
wants to display and view the data, which is stored in the database, the system
should be able to display the stored data.
2.5.1.1 NON-FUNCTIONAL REQUIREMENTS

Back up
The system should support back up to database or sql and recovery mechanism
from system failure.
Hardware requirement
As mentioned above, we use hardware such as different CD-ROM, Flash, hard
disk and others.
Error Handling
The system has to eject all unnecessary data entry. For example, in place of name,
numeric data value cannot be placed. And in place of number, letters cannot be
placed.
page 71
/2007
Usability
Since I use powerful programming languages which support graphical user interface it
is user friendly for the user and does not require a great deal of skill and expertise.
Performance
The new system accomplishes tasks within good response time and produces
output within a good throughput time.
Time
The system saves lots of time in performing tasks performed by the current system
Security:-To access any data in the database the user should be an authorized
otherwise unauthorized person cannot access any system information illegally.
Portability
The system can be executed in different platforms without any restriction. It is
also adaptable.
Reliability
Compared with the current system it is very reliable where it can handle error and
can effectively produces the desired result in case of performing a specific task.
Flexibility
It is easy to add additional features and tasks performed by the system and also it
is easy for manipulation.
Quality Issues
A much larger volume of software is business-critical, e.g., software that runs in powers web
servers and manages data centres. Defects in this type of software can lead to significant
financial losses. The system will also have different modules for taking backup of
organization data with tape devices or Medias and the backup of the system will of two types
differential or incremental backup depending on the choice of user. Underpinning all of these
areas is systems software: the low-level operating systems, device drivers and networking
software on which complex systems are built. This foundational role means that the reliability
of systems software is of primary importance.
The new system is reliable, robust compare with the current system and also when we
observe the current system its not always available as the new system. In case of our new
system user involvement in the development processes is our vital requirement for the quality
of the system.
System Modification
In future the system can be re-implemented to modify online payment .The reimplementation can be performed by the developers or other system developers by using
technical document.
Physical Environment
The system expected to withstand external problems like when the network connection fails
or slow the system must withstand the network frailer, and if the hardware crashed the system
must be back-up the file that the user use.
page 71
/2007
Security Issues
Security of the system must be given the outmost consideration in a database intensive
system. This document is defined to serve all application parts, to make authentication of
users and authorization on and incorporate functionality that the system need to have:
All the system must be secured: user must be able to give right or deny for all user
based on his or her position by the administration of the system.
All major transaction of the system should be logged to database and seen only by the
administrator. If the system has login part the external intrusions or malicious users
cannot get access.
The system has session control: when the user registered once the system can save the
user data.
Resource Issues
The system has a resource that requires having the following performance characteristics
The server and the client must have memory space.
The server and client must have process speed.
2.6 feasibility study

1.6.1 Technical feasibility
The technical feasibility focused on gaining an understanding the present technical

resources of the organization and their applicability to the expected need of the
proposed system.
The system is easier to operate, to learn, how it works and easy for non-technical
people.
The system gives a technical support for users how to operate.
1.6.2 Economic feasibility
This project consumes 180000 birr to develop the entire for proposals 30000 birr, for
project analysis 40000 birr, for project designs 40000 birr and for implementation part 70000
birr. For these small budgets it can be beneficially for to:
Reducing the cost of the organization. It reduce the cost paid for human power,
reduces the number of employees works in management in the organization
It reduce resource that are used for documentation
It also increases the availability of resources anywhere, so that decrease
transportation rate.
It is beneficiary in terms of reducing the cost of the organization.
It reduces the cost paid for updating and storing of the product data and although
the staff data.
It reduces resources that are used for documentation like paper, pen, etc.
page 71
/2007
1.6.3 Operational feasibility
The operational feasibility of this proposed project provides an efficient and

effective solution for the problems.
This system provides an easier access of product file rather than searching
product file from the file cabinet.
It increases the performance of the work in the time of searching, editing, and
deleting of stored file.
1.6.4. Scheduled feasibility
Projects are always given deadlines. Every project is completed in specific duration. I had to
complete the project in time and if it is not possible to complete on time then we should try to
fulfil requirements.
2.7 Requirement analysis for new system
Requirements analysis is critical to the success of a systems or software project. The Requirements
should be documented, actionable, measurable, testable, traceable, related to identified business needs
or opportunities, and defined to a level of detail sufficient for system design. So we identify the
following things for the new system:
2.7.1 Actor and Use Case Identification
A use case model is used to document the behavioural requirement and functional tasks .the
system must support essential use case model often returned to as a business use case model
or abstract use case model, models technology independent view of your behavioural
requirement. Essential use case model include after the identification use case diagram.
2.7.1.1Actor Identification
Actors represents anything that can be interact directly or indirectly
Customer
Employee
Manager
Actor Documentation
Name: Customer
ID: AU0001/2007
Description: every customer should be register
Name: employee
ID: AU0002/2007
Description:
page 71
/2007
2.7.1.2 Use case identification

Use case is sequence of action that provides a measurable value to an actor. Another way to
look at is that a use case describes a way in which a real world actor interacts with the
system.
The team has identified the following use case.
Generate report
View product information
Delete customer information and product
Accept comment
Update product and customer information
Search customer data
Register customer product
2.7.2 Importance of use case diagram
The technical definition of a USE CASE is that it is a description of a systems behaviour

or a particular scenario in which a system responds to an external request that originates.
An example of an external request is a user input. Basically, a use case is helpful to
understand the system from the end-user who is ultimately to actually use the systems
point of view. Use cases help to specify and explain the interaction between the actors and
the system. Use case diagram is a diagram that shows the relationship among actors and use
case within a system.
Since use case diagram show the relationship among actors and the use case it provides an
overview of all or part of the usage requirements for a system organization in the form of an
essential model or business model and also communicate the scope of a development
project as well as it provides to model your analysis of your usage requirement in the form
of system use case model.
Importance: Use cases are important because they are in a tracking format. Hence they
make it easy to comprehend about the functional requirements in the system and also make
it easy to identify the various interactions between the users and the systems within an
environment.
They are descriptive and hence clearly represent the value of an interaction between actors
and the system. They clarify system requirements very categorically and systemically
making it easier to understand the system and its interactions with the users. During the
analysis phase of the projects System Development Life Cycle, use cases help to
understand the systems functionality.
2.7.3 Essential elements in UML use case diagram
Use case diagram may contain many elements within it namely: Actors, Use case,
Associations, System and they are drowning as stick figures.
Actors: an actor is a person, organization, external system that plays a role in one or more
interactions with your system and they are drowning as stick figures.
page 71
/2007
Use case: Sequence of actions, including variants that a system (or other entity) can perform,
interacting with actors of the system. We use for the action of delete, update, view, record,
report, comment, Login and logout
System boundary: Represents the boundary between the physical system and the actors who
interact with the physical system. We use this boundary between physical systems
Extend: a relationship from an extension use case to a base use case, specifying how the
behavior from the extension use case can be inserted into the behavior defined the base use
case. Use this extension from login to other use case
Uses: A relationship from a base use case to an inclusion use case, specifying how the
behavior for the inclusion use case is inserted into the behavior defined for the base use case.
We use this to indicate which tasks the actors to be performed
2.8 use case diagram documentation and forms
Name: login
Id: UC-1
Priority: high
Actor: manager, employee
Description: This use case allows the manager and employee to login to the system
Precondition: This is done by the manager and employee before doing any activity
Flow of event:
1.
2.
3.
4.
5.
Browse the browser window

The system displays the login button.
The user enter username and password
The system display the main page
End use case
Alternative flow of events:

A1. If the username and password are incorrect go to step 3
Post condition: After log to the system do their job.
Name: Update customer data

Id: uc-2
Priority: high
page 71
/2007
Actor: Manager
Description: This use case permit user to update or modify customer information in case of
wrong input or needs.
Precondition: Checked the type of the information that can be updated
Flow of event:
1. User wants to login to system
2. Open the customer page
3. Fill the updated information
4: press update button
5 end of use case
A1. If fill information is incorrect back to step 3
Post condition: Checked the updated one
Name: delete customer data
Id: uc-3
Priority: high
Actor: Manager
Description: This use case permit user to delete or modify customer information in case of
Precondition: Checked the type of the information that can be deleted
Flow of event:
3. Fill the deleted information
4: press delete button
5 end of use case
page 71
/2007

Post condition: Checked the type of the information that can be deleted
Name: Generate report
Id: uc-4
Priority: high
Actor: manager and employee
Description: The manager and employee write the report
Precondition: Analysis the types of report that can be generated
Flow of events:
2. Open the reported page
3. Write the report that can be generated
4. The system prompts the managers and employee for the pickup and generate.
5. End of use case
A1. : If the information is empty or incorrect back to 3:
Post condition: The system display the reports successfully
Name: search customer data
Id: uc-5
Priority: medium
Actor: Manager and employee
Description: This use case permit user to record customer information when the they provide
Precondition: Checked the type of the information that can be record
Flow of event:
3. Fill the customer id number
page 71
/2007
4: press search button

5 end of use case
Post condition: Checked the type of the information that can be recorded
Name: View product
Id: uc-6
Priority: high
Actor: Manager, employee and customer
Description: The manager employee and customer view the new reports
Precondition:
Flow of events:
1. The manager, employee and customer want to main page.
2. Then on the main page the manager, employee and customer clicks on the view Button.
4. The system responds the requested page.
5. The system displays all reported information to the manager, employee and customer.
7. Use case ends.
Alternative flow of events
A1. : If reported information is not found back to main sequence of step 2.
Post condition: Display all provided information
Name: customer record
Id: uc-7
Priority: medium
Actor: Manager and employee
Description: This use case permit user to record customer information when they buys a
product.
Precondition: Checked the type of the information that can be record
page 71
/2007
Flow of event:
3. Fill the customer information
4: press record button
5 end of use case
Post condition: Checked the type of the information that can be recorded
Name: give comment
Id: UC-8
Priority: low
Actor: manager, employee and customer
Description: This use case allows the manager, employee and employee to login to the
system
Precondition:
Flow of event:
1.
2.
3.
4.
5.
Browse the main page

The system displays the comment button.
Fill information
Press comment
End use case

A1. If the fill information is incorrect step 3
Post condition: After log to the system do their job.
page 71
/2007
2.9 use case diagram
Ambo University consumer cooperation supermarket
search customer
data
logout
Manager
modify information
extends
extendsextends
update
delete
login
give comment
Customer
record custemer
view product
Employee
generate report
make payment
Fig 2.4 use case diagram for current system
page 71
/2007
2.9.1 Importance of use case diagram
describe or capture functional requirements

represent the desired behaviour of the system
identify users (actors) of the system and associated processes
are the basic building blocks of activity and sequence diagrams
tie requirements phase to other development phase
a diagram that shows a set of use cases and actors, and their relationships
is central to modelling the functions of the system
is used to visualize the functions of a system, so that:
users can comprehend how to use the system and
developers can understand how to implement it
puts everything together
2.9.2 Use case diagram documentation and forms
The new system will design by using object oriented model. The object oriented model
contains use case diagram.
The purpose of use case diagram is to identify the user or how the user interact with the new
system, in other words to identify how the system will be used. The use case diagram is
graphical model that summaries the information about actor and use case.
2.10 User interface identification

Every web website has two parts static and dynamic. Most of the pages are documentations
or static pages but there are also dynamics pages.in general this website includes CSS,
JavaScript, PHP, and MySQL the interface is no direct login page but one user directly enters
into the main page then if he or she wants to gather other information he/she can login to
secure part.
Name: login Page
Id: UI-1
Description: the manager and employees to get their own pages to enter username and
password
Name: Modifications update Page
Id: UI2
Description: This use case permit user to update or modify customer information in case of
Name: Modifications delete Page
Id: UI3
Description: This use case permit user to update or modify customer information in case
of wrong input or needs
Name: Report generate Page
page 71
/2007
Id: UI 4
Description: This page used to manager and employee write the report
Name: search customer data Page
Id: UI5
Description: the manager and employees to get their own pages to enter username and
password
Name: Record customer Page
Id: UI7
Description This use case permit user to record customer information when the customer
buys a products.
Name: main Page
Id: UI8
Description: All users firstly can get the main page .This page consists of about as,
comment page, view page.
2.11 sequence diagram
Sequence diagrams are usually created to show the flow of message among objects and actors in
the system. Sequence diagrams answer questions about how the system will work. Once we have
created the sequence diagram, you next need to determine which the manager, employee and
customer interact with the system and we are drag all actors involved in the use case to the
sequence diagram, then walk through the functionality, adding objects to facilitate that
functionality as needed
page 71
/2007
manager and employee
login:controler
login
home page
database
sequance of action for login

weant to login()
1:Went to login
create()
2:Enter username
and password
username
validte()
password
3:validate username and

password
requst()
valid()
4:Display
display()
Fig2.5 login for sequence diagram
page 71
/2007
ckage::manager
main page login :controler
login()
delete controler
database
delete
activate()
initiate()
create()
username()
checke validity()
initiate()
password()
create()
fill information
validity()
press delete()
delete()
you are delete successfully
logout()
Fig 2.6 sequence diagram for delete
page 71
/2007
ckage::manager
main page
login :controler
login()
update:controler
update
custemer database
activate()
initiate()
create()
username()
checke validity()
initiate()
create()
password()
fill information
validity()
press update()
save()
you are update successfully
logout()
Fig2.7 sequence diagram for update

page 71
/2007
Top Package::manager and employee

main page login :controler
login()
search:controler
search custemer database
activate()
initiate()
create()
username()
checke validity()
initiate()
password()
create()
fill information
chack valid()
press search()
search()
display()
logout()
Fig2.8 sequence diagram for search
page 71
/2007
age::employee and manager

main page
login :controler
login()
record controler
record
customer database
activate()
initiate()
create()
username()
checke validity()
initiate()
password()
create()
fill information
checke validity()
press record button()
save()
record seccefull
logout()
page 71
/2007
Fig2.9 sequence diagram for record
page 71
age::employee and manager

main page
login :controler
login()
report controler
/2007
report
report database
activate()
initiate()
create()
username()
checke validity()
initiate()
password()
create()
fill information
check validity()
presss report()
save()
success()
logout()
Fig2.10 sequence diagram for report
page 71
/2007
age::employee, manager,and customer

home page
view
view :controler
database
activate()
initiate()
create()
press view button()

requst()
check()
display()
Fig2.11 sequence diagram for view
page 71
/2007
2.12 Activity diagram

Activity diagram are graphical representation of work flows of stepwise architecture and action with
support for choice iteration and concurrence. Therefore, these activity diagrams the manager,
employee and customer to facilitate there function describe what types of steps required from them.
This activity diagram shows the overall logical flow of control.
-user
Login(uI 1)
-system
disploay login
weant to login
incorrect
username and password
ckeck
correct
display homepage
Fig2. 12 activity diagram for login
page 71
-user
/2007
Customer search(UI 5)
-system
disploay login
weant to login
incorrect
ckeck
return
Correct
fill information
went to search
incorrect
ckeck
Correct
save
Fig2.13 activity diagram for search
page 71

-user
Customer update(uI 2)
/2007
-system
disploay login
weant to login
ckeck
fill information
went to update
ckeck
save
Fig2.14 activity diagram for update
page 71
-user
Customer delete(uI 3)
/2007
-system
disploay login
weant to login
incorrect
ckeck
return
Correct
fill information
went to delete
incorrect
ckeck
Correct
save
Fig 2.15 activity diagram for delete
page 71
-user
Customer record(uI 7)
/2007
-system
disploay login
weant to login
ckeck
fill information
went to record
ckeck
save
Fig 2.16 activity diagram for record
page 71
-user
Customer view(UI 6)
/2007
-system
disploay view
weant to home
click view
display information
Fig 2.17 activity diagram for view
page 71
-user
Customer report(uI 4)
/2007
-system
disploay login
weant to login
incorrect
ckeck
return
Correct
fill information
went to report
incorrect
ckeck
Correct
save
Fig 2.18 activity diagram for report
page 71
/2007
2.13 Class diagram
This diagram shows the static structure of the manager, employee and customer, in
particular, the things that exist (such as classes and types), their internal structure, and their
relationships to other to one another.
This section discusses classes and their variations, including templates and instantiated
classes, and the relationships between classes association and the contents of classes .
Person
+f_name
+l_name
+id
+view()
+comment()
Employee
Manager
-m_username
-m_password
-update()
-delete()
+record()
+report()
+search()
-many
-one
*
*
-one
-phone
-address
+record()
+report()
+search()
many
-many
Customer
-acount_no
-email
-phone
-nationality
-sex
many
Fig2.19 class diagram
page 71
/2007
CHAPTER THREE
Design
3.1 Collaboration diagram
1:activate
manage
main page
4:username and
password
2::initiate
login controler
3:activate
8:fill info
5:Check
validity()
9:press update
database
12:you are
succesfullyupdated
login
11:save
13:logout
10:Check
validity()
6 initiate
update
7:create
update:controler
Fig 3.1collaboration diagram for update
page 71
/2007
1:activate
manage
main page
4:username and
password
5:select and
Fill()
2::initiate
login controler
3:activate
8:fill info
5:Check
validity()
9:press delete
database
12:you are
successfully
deleted
11:delete
login
13:logout
10:Check delete
validity()
6 initiate
7:create
delete:controler
Fig 3.2 collaboration diagram for delete
page 71
/2007
1:activate
main page
4:username and
password
2::initiate
login controler
3:activate
8:fill info
5:Check
validity()
9:press record
database
12:you are
successfully record
login
11:save
13:logout
10:Check record
validity()
6 initiate
7:create
record:controler
Fig 3.3 collaboration diagram for record
page 71
/2007
1:activate
main page
4:username and
password
2::initiate
login controler
3:activate
8:fill info
5:Check
validity()
9:press report
database
12:success
login
11:save
13:logout
10:Check report
validity()
6 initiate
7:create
report:controler
Fig 3.4 collaboration diagram for report
page 71
/2007
1:activate
main page
4:username and
password
2::initiate
login controler
3:activate
8:fill info
5:Check
validity()
9:press report
database
12:display
login
11:requst
13:logout
10:Check search
validity()
6 initiate
7:create
search:controler
Fig 3.5 collaboration diagram for search
page 71
/2007
1:activate
homepage
1:Went to login
3:username and
password
7:display
login controler
2:create
6:valid
4:Check
validity()
database
5:requst
login
Fig 3.6 collaboration diagram for login
page 71
manager,employee and
customer
/2007
1:activate
main page
2:iniated
4:press view button

7:display
view: controler
3:create
6:check
database
5:requst
view
Fig 3.7 collaboration diagram for view
page 71
/2007
3.2 STATE CHART DIAGRAM
In this part the team used to model the behaviours of the objects by drawing the state
diagram. The state diagram depicts the state of objects as their attributes change from one
state to the other state. State chart modelling is used to show the sequence of states that an
object goes through, the events that cause the transition from one state to the other and the
actions that result from a state change. The following figure shows the modelling of the
system State chart diagram describes an object as it passes through different states The
management object has the following identified states as shown in figure below:-
login
record
fill information
ok
logout
Fig 3.8 state chart diagram for record
page 71
login
update
fill information
/2007
ok
logout
Fig 3.9 state chart diagram for update
login
delete
fill information
ok
logout
Fig 3.10 state chart diagram for delete
page 71
login
report
fill information
/2007
ok
logout
Fig 3.11 state chart diagram for report
page 71
login
search
/2007
ok
fill information
logout
Fig 3.12 state chart diagram for search
login to system
view
press view
page 71
/2007
Fig 3.13 state chart diagram for view
login
fill username and password
press login
logout
Fig 3.14 state chart diagram for login
3.3 Revised class diagram
page 71
/2007
person
+first_name : string
+last_name : string
+adress : string
+email : char
+phone : char
+password : char
+view()
+comment()
+exit()
+clear()
product
-id
-price
-product_name
-num_product
-level
-expried_date
Payment
-acount_no : String
-amout_mony : char
-product_type : char
+total()
+save()
*
1
Customer
-contact
-trnasaction_number
-product
-payable
*
-date
Manager
Employee
-manager_id :
char
-update() : char
-delete() : char
+record() : char
+report() : char
+search() : char
-employee_id : char
-record() : char
-report()
: char
*
-search() : char
*
*
*
*
*
1
1
*
*
customer_account
-account
-money
Home
-name
-description
-image
Contact
-name
-product
-email
-message
Fig 3.15 revised class diagram
3.4 Component diagram
The component diagram main purpose is to show the structural relationships between
the components of a system. We use this component diagram to describe the relation of
physical Components in the Ambo university consumer cooperation supermarket.
page 71
manager
/2007
Access data
search customer data
Access modify informatin

modify information
-security
security
Access custemer data

employee
record customer
-backup data
backup
Access generate report

generate report
customer
Access view data
view information
Fig 3.16 component diagram for search
3.5 Deployment diagram
page 71
/2007
:application server
:actors
search customer data

manager
http
record costomer
employee
modify customer data

custemer
generate report
ADO.NET
:database servver
view inforation
database
Fig 3.17Deployment diagram
3.6 User interface diagram
Every web website has two parts static and dynamic. Most of the pages are
documentations or static pages but there are also dynamics pages.in general this website
includes CSS, JavaScript, PHP, and MySQL the interface is no direct login page but one user
directly enters into the home page then if he or she wants to gather other information he/she
can login to secure part.
Main page
page 71
/2007
All user firstly can get the main page .This page consists of about as, comment, view
customer data page, login page and logout page .the user can see this pages and select their
needs and continues to next session
Fig 3.18 main page form
Code
<html>
<head>
<link rel="stylesheet" href="css/style.css" type="text/css" />
</head>
<body>
page 71
/2007
<table id="table5" width="100%"><tr><td colspan="3"height="100%">


<img src="../../awelehusen/image/aw.GIF"
width="200" heigh="10"/>
alt="ERROR
LOADING"
align="right"
<img src="../../awelehusen/image/money.GIF" alt="ERROR LOADING" align="center"

<img src="../../awelehusen/image/AA.PNG"
alt="ERROR
LOADING"
align="left"
<header>
<hgroup>
<div id="menu" data-role="page" >
<ul id="nav">
<li><a href="home.php">home |</a></li>
<li><a href="about as.php">About us |</a>
<li><a href="index.php">login |</a></li>
<li><a href="contactas.php">contact as |</a></li>
<li><a href="payment1.php">payment|</a></li>
<tr>
<td id="right"width="5%"height='100%'>
</td>
<td>
<p align="right"> <h1>Ambo Uiniversity Consumer cooperation Supermarket </h1></p>
<?php
$db_username
= 'root';
$db_password
= '';
$db_name
= 'assignment';
$db_host
= 'localhost';
page 71
/2007
$items_per_group = 5;
$mysqli = new mysqli($db_host, $db_username, $db_password,$db_name);
$results = $mysqli->query("SELECT * FROM home ");
?>
<table width="800px;" cellpadding="5" cellspacing="5" style=" ">
<section class="container"
<?php
if ($results) {
while($obj = $results->fetch_object())
{
?>
<tr valign="top" style="padding-left:-40px;" >
<td width="150px" height="85" style=""><br />
<?php
echo "<img src='$obj->image' width='100' height='100' />";
?>
</td>
<td width="741" height="95" style=""><br />
<h1> <?php echo $obj->bookname; ?> </h1>
<br>
<?php echo $data= $obj->des;
}}
?> </p>
</td>
</tr>
</section>
page 71
/2007
</table>
</div>
<div id="left1"></br> <td id="image"width="10%"height='100'>
<img src="1.jpg" alt="map of asia">
<td id="normal" align="Center"> </td></div></p></tr>
<tr><td>
</td><td></td>
</tr>
<tr>
<td colspan="3"id="footer1">
<div id="footer" align="Center"> <b>ambo university consumer cooperation project done by
IT gradution student</div
</table>
</div>
</body>
</html>
Login page
This page is the manager and employee by entering username and password going to their
provided pages this page consists of about as, comment, view customer data page and logout
page .the user can see this pages and select their needs and continues to next session
page 71
/2007
Fig 3.19 login page form
Code
<?php
include_once 'connect_db.php';
if(isset($_POST['submit'])){
$username=$_POST['username'];
$password=$_POST['password'];
$position=$_POST['position'];
switch($position){
case 'manager':
$result=mysql_query("SELECT f_name,l_name, username FROM manager WHERE
username='$username' AND password='$password'");
$row=mysql_fetch_array($result);
if($row>0){
page 71
/2007
session_start();
$_SESSION['f_name']=$row[0];
$_SESSION['l_name']=$row[1];
$_SESSION['username']=$row[2];
header("location:http://".$_SERVER['HTTP_HOST'].dirname($_SERVER['PHP_SELF'])."/
managerrecord.php");
}else{
$message="<font color=red>Invalid login Try Again</font>";
}
break;
case 'employee':
$result=mysql_query("select f_name,l_name,username
username='$username' AND password='$password'");
FROM
employee
WHERE
if($row>0){
session_start();
$_SESSION['f_name']=$row[0];
$_SESSION['l_name']=$row[1];
header("location:http://".$_SERVER['HTTP_HOST'].dirname($_SERVER['PHP_SELF'])."/e
mployeerecord.php");
}else{
}
break;
case 'Cashier':
$result=mysql_query("SELECT cashier_id, first_name,last_name,staff_id,username FROM
cashier WHERE username='$username' AND password='$password'");
page 71
/2007
if($row>0){
session_start();
$_SESSION['cashier_id']=$row[0];
$_SESSION['first_name']=$row[1];
$_SESSION['last_name']=$row[2];
$_SESSION['staff_id']=$row[3];
header("location:http://".$_SERVER['HTTP_HOST'].dirname($_SERVER['PHP_SELF'])."/c
ashier.php");
}else{
}
break;
case 'Manager':
$result=mysql_query("SELECT manager_id, first_name,last_name,staff_id,username FROM
manager WHERE username='$username' AND password='$password'");
if($row>0){
session_start();
$_SESSION['manager_id']=$row[0];
$_SESSION['first_name']=$row[1];
$_SESSION['last_name']=$row[2];
$_SESSION['staff_id']=$row[3];
header("location:http://".$_SERVER['HTTP_HOST'].dirname($_SERVER['PHP_SELF'])."/
manager.php");
}else{
page 71
/2007

}
break;
}}
echo <<<LOGIN
<!DOCTYPE html>
<html>
<head>
<title>login</title>
<link rel="stylesheet" type="text/css" href="style/mystyle_login.css">
<body>
<div id="content">
</head>
<body>
<table id="table5" height="100%"><tr><td colspan="3"height="100%">
alt="ERROR
LOADING"
align="right"

alt="ERROR
LOADING"
align="left"
<header>
<hgroup>
<ul id="nav">
<li><a href="home.php">home |</a></li>
<li><a href="about as.php">About us |</a>
page 71
/2007
<li><a href="contactas.php">contact as |</a></li>

<li><a href="payment1.php">payment|</a></li>
<tr>
</div>
<div align="center">
<style>
#content {
height: auto;
}
#main{
height: auto;}
</style>
</head>
<div id="main">
<section class="container">
<div class="login">
$message
<table class="signup" border="0" cellpadding="10"
cellspacing="5" bgcolor="#eeeeee">
<form method="post" action="index.php">
<p><td>Username</td><td><input
type="text"
name="username"
type="password"
name="password"
required</p>
<p><tr><td>password</td><td><input
required</p>
<p><tr><td>privilage</td><td><p><select name="position">
<option>--Select position--</option>
<option>manager</option>
page 71
/2007
<option>employee</option>
</select></p>
<p class="submit"><input type="submit" name="submit" value="Login">
<input type="reset" name="Reset"value="clear"></td></p>
</tr></form></table>
</div>
</section>
</div>
</body>
</html>
LOGIN;
?>
Manager
This page is the manager by entering username and password going to their provided
pages this page consists of manager, employee, customer account, view report, logout and
home.
page 71
/2007
<?php
session_start();
//echo "User".$_SESSION['user'];
if(isset($_SESSION['username']))
{
$username=$_SESSION['username'];
//echo "User name :".$username;
} else {
?>
<script>
alert('You Are Not Logged In !! Please Login to access this page');
window.location='../../../awelehusen/index.php';
</script>
page 71
/2007
<?php
}
?><html>
<head>
<script language="javascript">
// function for comfirm box !!
function logoutcon() {
var conlog = confirm('Are you sure you want to log out !!');
if(conlog)
{
alert(window.location="logout.php");
}
else
{
return false;
}
}
function check()
{
if(document.getElementById('selpid').value
==
document.getElementById('seldate').value == 'seldate')
'selpid'
&&
{
alert('Select any option !!');
return false;
}}
</script>
page 71
/2007
</head>
<body>
<table id="table5" height="100%"><tr><td colspan="3"height="100%">
alt="ERROR
LOADING"
align="right"

alt="ERROR
LOADING"
align="left"
<header>
<hgroup>
<ul id="nav">
<li><a href="home.php">home </a>
</li>
<li><a href="logout.php">logout </a>
<li><a href="">view report </a>
<ul>
<li><a href="viewreport1.php">report for cash</a>
<li><a href="viewreport.php">report for credit card </a>
<li></ul>
</nav></td></tr>
<tr>
<td id="image"width="5%"height='120%'>
<script language="javascript" type="text/javascript">
var slideShowSpeed = 2000;
var crossFadeDuration = 3;
var Pic = new Array();
page 71
/2007
Pic[1] = '../../awelehusen/image/sup.PNG'
Pic[2] = '../../awelehusen/image/supe.PNG'
Pic[3] = '../../awelehusen/image/super.PNG'
Pic[4] = '../../awelehusen/image/photo5.PNG'
Pic[11] = '../../awelehusen/image/photo7.PNG'//// do not edit anything below this line
var t;
var j = 0;
var p = Pic.length;
var preLoad = new Array();
for (i = 0; i < p; i++) {
preLoad[i] = new Image();
preLoad[i].src = Pic[i];
}
function runSlideShow() {
if (document.all) {
document.images.SlideShow.style.filter="blendTrans(duration=3)";
document.images.SlideShow.style.filter="blendTrans(duration=crossFadeDuration)";
document.images.SlideShow.filters.blendTrans.Apply();
}
document.images.SlideShow.src = preLoad[j].src;
if (document.all) {
page 71
/2007
document.images.SlideShow.filters.blendTrans.Play();
}
j = j + 1;
if (j > (p - 1)) j = 0;
t = setTimeout('runSlideShow()', slideShowSpeed);
}
window.onload=runSlideShow;
// End -->
</script>
<img src="1.jpg" name='SlideShow' width=95% height=500></td>
<td id="table3"height="100%"width="10%"rowspan="1">
<div id=arsema>
<a href="manager.php" class="dashboard-module">
<img src="image/employee.jpg"" width="75" height="75" alt="edit" />
<span>manager</span>
</a>
<a href="employee.php" class="dashboard-module">
<img src="image/manager_icon.png" width="75" height="75" alt="edit" />
<span>employee</span></a>
<a href="customer.php" class="dashboard-module">
<img src="image/customer.gif" width="75" height="75" alt="edit" />
</td></tr>
<tr><td>
</td><td></td>
</tr>
<tr>
page 71
/2007
<td colspan="3"id="footer1">
<div id="footer" align="Center"> <b>ambo university consumer cooperation project done by
IT gradution student</div
</td></tr>
</table>
</div>
</body>
</html>
Recommendation
The team recommends the following points for the best implementation and instalment of this
project.
Employers who are working on this system get better performance and speed.
The organization should facilitate the system access to all employers of the
organization and support them to learn & use it.
page 71
/2007
The data and all things on the system that is used by customers and should be
updated must updated by the administrator.
The website should be promoted and advertised through websites that have
much opportunity to be visited so that many people become aware of its
existence and get the chance of using it.
Conclusion
To conclude the work in this project, the proposed solutions that are stated on the proposal
part of the project are more or less properly implemented. The development of web based
application for Ambo university consumer cooperation supermarket could be hindered due to
some constraint as time, money and mainly performance. These factors along with other
unspecified reasons have resisted the team from developing more efficient and rich
application.
page 71
/2007
Reference
System analysis and design,1997 ,2nd edition by Elias M A Wad

Modern Systems Analysis and Design, 2008, 5th Edition. Hoffer J., George J. and ,Valacich J
Project Management Institute (2004), Guide to the Project Management Body of
Knowledge, third edition, PMI press.
page 71
/2007
Software Engineering (2009), A Practitioners Approach, Seventh Edition, Roger S.

Pressman, Ph.D.
Software Engineering for Students (2005), A Programming Approach, Fourth
Edition, Douglas Bell.
Contents
CHAPTER ONE ..................................................................................................................................... 1
1. Introduction .................................................................................................................................... 1
page 71
/2007
1.1Background ................................................................................................................................ 1
1.2 Statement of the problem ........................................................................................................ 2
1.3 Objective of the project ............................................................................................................ 2
1.4 significance of the project ......................................................................................................... 3
1.5 Scope of the project and limitation .......................................................................................... 3
1.6 Methodology ............................................................................................................................. 4
1.7 project budgeting ...................................................................................................................... 5
1.8 project schedule ........................................................................................................................ 6
1.9. Project Organization ................................................................................................................ 6
CHAPTER TWO .................................................................................................................................... 7
System Analysis ................................................................................................................................... 7
2.1 Major function of the current system....................................................................................... 7
2.2 problem analysis /definition ..................................................................................................... 7
2.3 user needs ................................................................................................................................. 8
2.4 Requirement analysis of the existing system ............................................................................. 9
2.5 alternative solution ................................................................................................................. 10
2.6 feasibility study ....................................................................................................................... 13
2.7 Requirement analysis for new system .................................................................................... 14
2.8 use case diagram documentation and forms ......................................................................... 16
2.9 use case diagram ..................................................................................................................... 21
2.10 User interface identification ..................................................................................................... 22
2.11 sequence diagram ................................................................................................................. 23
2.12 Activity diagram .................................................................................................................... 32
2.13 Class diagram ........................................................................................................................ 39
CHAPTER THREE ................................................................................................................................ 40
Design................................................................................................................................................ 40
3.1 Collaboration diagram ............................................................................................................ 40
3.2 STATE CHART DIAGRAM.......................................................................................................... 47
3.3 Revised class diagram ............................................................................................................. 51
3.4 Component diagram ............................................................................................................... 52
3.5 Deployment diagram .............................................................................................................. 53
3.6 User interface diagram ........................................................................................................... 54
page 71
/2007
page 71

Documentation PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Documentation PDF

Enviado por

Direitos autorais:

Formatos disponíveis

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

1.2 Statement of the problem

It is difficult to retrieve product and its information when it is required.

1.3 Objective of the project

To register new product

To provide real time delivering service

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

1.4 significance of the project

To keep records of the customer and product in the database

1.5 Scope of the project and limitation

Scope of the project is developing website for consumer coop supermarket.

LAN: the system will not concern about installation of network.

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

1.6.1.2 Document Analysis

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

1.7 project budgeting

Project funding summary

Total cost(local currency)

Requesting to allocate budget

Total project cost

Table 1.1 project budgeting

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

1.8 project schedule

12/8/2014 12/15/2014 1.2w

12/16/2014 12/30/2014 2.2w

1.9. Project Organization

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

Generally the Existing System has the following Problems:

Performance: - It is time consuming and less performance since every task is

Information: - Redundancy of data.

Efficiency: It operates over specified long period of time interval. Generally,

Security: It is not secured because it has not guard.

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

System is expected to give result in a reasonable amount of time

analysis of the existing system

2.4.1.1 Actors involve in the existing system

2.4.1.2 Essential user interface prototype

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

Receive product with full information

Constraints: A constraint is a restriction on the degree of freedom you have in providing a

It takes less time to perform activities, availability of full service.

Reduce time consuming

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

Decrease a lot of/multiple paper works.

2.5.1 Automated system

2.5. 1.1 FUNCTIONAL REQUIREMENTS

2.5.1.1 NON-FUNCTIONAL REQUIREMENTS

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

2.6 feasibility study

The technical feasibility focused on gaining an understanding the present technical

1.6.2 Economic feasibility

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

1.6.3 Operational feasibility

The operational feasibility of this proposed project provides an efficient and

1.6.4. Scheduled feasibility

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET

2.7.1.2 Use case identification

2.7.2 Importance of use case diagram

The technical definition of a USE CASE is that it is a description of a systems behaviour

AMBO UNIVERSITY CONSUMER COOPERATION SUPERMARKET