ARBA MINCH UNIVERSITY INSTITUTE TECHNOLOGY

DEPARTMENT IT
TITLE: SUPER MARKET AUTOMINION SOFTT WARE

CHAPTER ONE

1. INTRODACTION

1.1. BACK GROUND INFORMATION ABOUT SUPER MARKET

1.1.1 THE STRENGTHS AND WEAKNESS OF THE CURRENT SYSTEM

1.2 BACKGROUND OF THE PROJECT

1.2.1 How Is Initiated

1.2.2 Team composition

1.2.3 STATEMENT OF THE PROBLEM

1.3 OBJECTIVE OF THE PROJECT

1.3.1General objective

1.3.2 Specific objective

01.4 FEASIBILITY ANALYSIS

1.4.1 Operational Feasibility

1.4.1 Operational Feasibility

1.4.3 Economic Feasibility

 COST BENEFIT ANALYSIS

A. Tangible benefits

B. Intangible benefits

1.4.4 Schedule Feasibility

Amu SISPage1
1.5 SIGNIFICANCE OF THE PROJECT

1.6 PROJECT BENEFITS AND BENEFICIARY

 Benefits
1.Intangible Benefits:
2.Tangible Benefits:
1.7 METHODOLOGY FOR THE PROJECT
1.7.1 Data Collection Method

1 Interviewing:

2 Practical observations:

1.7.2 System analysis and design methodology

A. Object Oriented Analysis:

B. Object Oriented Design:

1.7.3 Data modeling tools

1.7.4 Test Procedure

1.8 SCOPE AND LIMITATION OF THE PROJECT

 Scope

 Limitation
1.9Risk, assumption and constraint

CHAPTER TWO

2. DESCRIPTOION OF EXISTING SYSTEM

2.1 Players and major functions of existing system with input Process and
output Players

 Major Functions of the Existing System

2.2 Business Rule

2.3 Report Generated in the Traditional Shopping System

Amu SISPage2
2.4 Forms Used in Existing System

2.5 Alternative Option to Address the Problem of Existing System

2.6 Optional Analysis and the Proposed New system

2.7 Functional Requirement and Non Functional Requirements

 Functional Requirements:

 Non Functional Requirements:

CHAPTER 3

MODELING

3.1 USE CASE DIAGRAME

3.2 use case documentation

3.3 Sequence Diagram

3.4 Analyses level class diagram

3.5 User interface prototyping

CHAPTER FOUR
Conclusion and Recommendation
4.2 Conclusion
4.2Recommendation

CHAPTER ONE

1. INTRODACTION

1.1. BACK GROUND INFORMATION SUPER MARKET AUTOMINION

SOFTT WARE

Amu SISPage3
Fruit Super market where found in Arbaminch, Seikala city near to abe hotel. The super market
was organized before 6 and half year ago. This supermarket was established because of to fulfill
the need of the community with different items.

1.1.1 THE STRENGHS AND WEAKNESS OF THE CURRENT SYSTEM

The organization has got the weakness in the side of implementing the proposal that was
drafted for the organization to modernize the supermarket in the field of buying the goods and
dividing the profit to the owners of the supermarket. This proposal has not contained computer
application and drafted a long period of time but they are not implementing the proposal yet.

The strength of the supermarket is supply the goods in a proper time with a great discount
and accepting the comment (suggestion) from the customer and correcting the defaults as fast as
they could and maintaining the strengths

1.2 BACKGROUND OF THE PROJECT

Our project is windows based. Because all of this project team have the experience of
windows application and have the knowledge of software that apply /provides/ this application.
Hence, we wanted to implement this project as a windows application and improve our previous
knowledge.

1.2.1 How Is Initiated

To do this project, we initiated greatly because of the following reasons:

 We can get the access for this project easily

 Our interest to be develops software to Fruit Super market. Because, there are
some problems regarding of this supermarket. Later we will mention in problem
statement portion.

 To get experience and use as stepping stone for future software project
development

 And also we want to be software developer in the future.

 We have been a great knowledge about windows based programming.

1.2.2 Team composition

Student Name ID The task he/she done

Amu SISPage4
 Mubarak Ahmed RNS/1771/10 Manager
Hamid Mohammed RNS/1686/10 Designer
Mohammed Hassen RNS/1766/10 Data collection
Selehadin Ahmed RNS/1822/10 Analyst
Wagaye RNS/1853 Assistant designer

1.2 STATEMENT OF THE PROBLEM

As the project team observed Fruit Super market many of its services are not satisfy the interest
of consumers because of the following problems. The way of selling items, the way of recording
goods have some problems.

 Since the system is manual information storage and recording, retrieval and
searching of items is tiresome, time consuming and error prone.

 Due to poor information system, the performance of supermarket is very low and
liable to consumers’ complaints.

 It is bulky to oddity the daily sold items’ and their price so they calculate their profit
monthly.

 Improper way of searching items auctioned by customers’ since they are ordered by
no any well known means.

 their goods through any means for their consumers’.

 Some goods are expired since they don’t sell in their chronological expiry date order
of the same items.

 Consumers’ dissatisfaction related with price raising and sloping down on the same
items to different consumers’.

 Low service efficiency does to little even a single service provider for many
customers at a time with manual system.

 Forgetting the price of goods by service providers and letting customers to come after
awhile until who is aware of servant comes.

Lack of giving awareness about

1.3 OBJECTIVE OF THE PROJECT
Amu SISPage5
1.3.1General objective
The main objective of the project is analyzing the current system problem from different
angles, and replacing the system with best user interface, comfortable solution oriented and
reliable through consumer, clerk and all other persons that got benefit from the supermarket. For
creating best organized database information recording system and information flow. Consumer
satisfaction with the service provided by super market.Mostly to get great profit and increasing
efficiency of performance in time and delicacy consumer.

1.3.2 Specific objective

To accomplish the objective of the project, the following specific activities are necessary to
accomplish the Subject: objectives:-

 To generate report.

 To display customer information.

 To register (login).

 To make ordering, searching or track down, and trap expiry of items solved through user
interface and easily applicable system.

 To develop a database to keep the overall records associated with items processing.

1.4 FEASIBILITY ANALYSIS

Our system project has nice feasibility since we identified problems those will be
undertaken through computerized system easily. It is definitely feasible on issues providing
effective service, time saving, reducing labor wasting, greatly for satisfying consumer and for
handling them, and absolutely to be more profitable through considering the above situations.
We are measuring our projects feasibility regarding on some certain criteria like:-operational
feasibility, technical feasibility, economical feasibility and schedule feasibility.

Amu SISPage6
 1.4.1 Operational Feasibility
With regard to operational feasibility it is clearly visible our system operationally feasible.
Because the problems those we identified are easily solved by using easily available software are
C++, Java, Dev++, Microsoft SQL Server Management Studio Express: and using browsers.
The mathematical and logical problems are easily solved using C++ or Java. Item displaying
system will be possible using Dev++ and linking items with their position, price, and amount is
also possible using browsers. The goal of this study is to understand the degree to which our
propose system is working. This process examines whether our project will attain its d esired
objectives. Hence, our project is clearly operational feasible how that it is specific solution will
work in the organization and overcome with a good environment towards the needs of the
people. Additionally, our project helps us to understand the degree to which the proposed system
will likely find solution to the business problem.

1.4.2 Technical Feasibility

Technical feasibility is to understand the organizational ability to construct the proposed
system. We are sure of that with little training they are able using the system, because the
system will develop exactly in user interface and window related application pattern.

We analyzing the possible target hardware, software and operating environment. Therefore, our
project is technical feasible in order to understand the organization’s ability to construct
proposed system and measure specific technical solution.

1.4.3 Economic Feasibility

Economic feasibility is concerned with assessing the financial benefits and the cost association
with our project to generate economic benefits. It referred to as cost benefits, analysis.

At the time of project initiation and planning, that is not possible to clarify correctively all the
benefits and cost that related to our project specifically, even if it is important aspect.

Is the action taken to determine how well, how poorly. It is commonly done on financial
question.

COST BENEFIT ANALYSIS

The refined cost benefit analysis will be presented as follow. In our project, we analyzed the
costs in terms of tangible and intangible to clear out the benefits.

 Tangible cost
 Inventory cost

Amu SISPage7
 Purpose Amount Unit price Total price
Sells person 2 1000 birr/month 12000 birr/year
Paper 2 180 birr/month 1800 birr/year
Pen 4 14 168birr/year
Total 14328 birr/year

 Intangible cost
 Consumers’ dissatisfaction
 Energy consumption

This project gives more benefits to Fruit Super market. So, our project is economically feasible
in terms of capital, energy and so on.

Our project provides many benefits to the organization that can be categorizes as tangible and
intangible benefits.

A. Tangible benefits
Tangible benefits are items which can be quantified in monetary terms and with certainty. From
the tangible benefits some of them are summarized below.

 Increase flexibility

 Improvement of the management control and planning

 Increasing sales opportunity in the current super market

Cost reduction.

Decreases/ removes the paper work for the movie renting shop

B. Intangible benefits
Intangibles are terms for which a value can’t precisely determined, and where the value may be
the result of subjective judgment. Some of them are:-

 Increase benefits
 Effective service for consumers’.
 Consumers’ satisfaction with the service.
 Providing effective service to the customers all in recording items, sales and recording
customers’ information.
 Accurate selling process of items

Amu SISPage8
 1.4.4 Schedule Feasibility

The project will be finished at the predefined day and time.

No Task name Start Finish duration

1 Chapter one December,4,2010 December,10,201 7days
0
2 Chapter two MAY18,2010 MAY 24,2005 7day
3 Chapter three& four MAY26,2005 MAY 30,2005 6day
1.5 SIGNIFICANCE OF THE PROJECT
Our project has much significance since it is designed to solve particular problem

 To full file customers requirements.

 Reduce the time required to perform the operation.

 Reduce the error that made by the clerk’s.
 It changes the manual storage mechanisms to computerize system.
 It provides speed, efficiency, flexibility, reliability and security.

 And it improved the moral of the employee

1.6 PROJECT BENEFITS AND BENEFICIARY

Benefits

The benefits we get from the system are divided into two:-

1. Intangible Benefits:
 Increase benefits by shortening the processing time for the whole tasks.

 Providing effective service to the customers all in recording items, sales and recording
customers’ information.

 Accurate selling process of items for the customers.

2. Tangible Benefits:

 Reduction of cost for items used for manual operation and data storage.

Amu SISPage9
  Optimizes man power for the given tasks.
 It is cost effective; it reduces unnecessary wastage of material like paper, pen, and
number of person….
 It reduces the time that customer stay to get services.
 Decreases/ removes the man power work for the supermarket.

Beneficiaries
The beneficiaries of the systems are:-
 Owner/ clients these using the software to controls.
Employees/ users
 Customers those buying goods.
 Software developer

1.7 METHODOLOGY FOR THE PROJECT

1.7.1 Data Collection Method

For developing our project we had followed two well known types of data collection methods.

1 Interviewing: To get basic and background information about the supermarket

existing system, we interview the clerk and also the manager.

2 Practical observations: To get additional information rather than the interview for
the process of the existing system, we went to Fruit Super market and saw some activities
which already mentioned above as problem. We did this because on some urgent issues
they ignore providing appropriate information.

1.7.2 System analysis and design methodology

In our project, we applied the concept of object oriented system development methodology
which categorized in to two phases. These phases are object oriented analysis and object oriented
design.

A. Object Oriented Analysis:

Model the use cases of the system

Finding and identify the business objects.

Analyze level class diagram (conceptual modeling)

Amu SISPage10
Organize the objects and identify the relationship between them

B. Object Oriented Design:

Refine the use case model to reflect the implementation environment,

Model object interactions and behaviors that support the use case scenarios

Finally update object model to reflect the implementation environment.

1.7.3 Data modeling tools

Java:to solve problems which are mathematical, logical and track down of items.
Microsoft SQL Server Management Studio Express: to design the database.

Macro Media Dream weaver 8.0: for designing the report view form for the generated
report.

HTML: for applying user interfacing

Microsoft Visio and E draw: for drawing of some diagram like sequence diagram.

1.7.4 Test Procedure

After design our proposed system, we try to test the system starting introduction part. First we
test our introduction part that whether it contains the brief summary of our developed system or
not. Secondly, we test our objectives are putted clearly or not. Thirdly, we test the problem of the
statement. Fourthly, we test the scope of our system is time concern or not and we try to test the
problems are clearly identified or not. Finally, we specify or put the solution for this problem of
the current system.

1.8 SCOPE AND LIMITATION OF THE PROJECT

Scope
The Scope of this project is to analyze the requirements, design and deploy the supermarket
inventory system generally our system scope includes the whole customer and all the item which
are concerned in the inventory system.

 Maintain items , buying items ,controlling the expire date of the items

 Record items information

 Manage user account

Amu SISPage11
  Manage customer information

 Generate reports

 Sales

Limitation
The following are limitations faced while conducting this project:

 Due to the shortage of time we may not include chapter four and implementation Part.

 Since we lack enough knowledge for the time of being we are obligated to desktop
base rather than web based

 The time given to the project is not enough to solve all the problems. Problems which
we face on doing this project are:

 Absence of light
 The situation when we interview some of the clerks which is not answer properly.

1.10 Risk, assumption and constraint

We have several risks during the completion of our project some actions may occur when we are
doing our project.

 Those actions may be destroying our system.

 Conflict within group members.

 Power break.

 Miss of responding on appropriate schedule

 Lack of management.

 Virus attack

Examples

If the power is off before saving the project the hard disk is infected with virus and worms the
computer does not open unless being formatted

If one of our group mates leave the university and one of our group mates gets sick

Amu SISPage12
All of these are the risk. To avoid these risks we should take some action .For instance before
the power is off we must save the project we have done, store

In other devices like flash disk and CD. So our assumption s all these risks should be taken in
to consideration during the starting date of the project.

Through giving moral intention for properly working group member and by discussing about
each step developments.Wemange conflicts within group members.

We came up with the problem of lack of management through properly planning appropriate
schedule for each of group members.

WE solve problem of responding in appropriate time through scheduling efficien6tly each task in
consideration with request time.

CHAPTER TWO

2. DESCRIPTOION OF EXISTING SYSTEM

2.1 Players and major functions of existing system with input

Process and output

Players
The existing system is manually working system it contains its own players those are participated
in over all selling buying Administering process in the shop of Fruit Super market.

They are listed as follows:

 Customers
 Sells person
 Store keeper
 Manager
 Administrator
 Sell item
 Forms
 Clerk

Amu SISPage13
 Major Functions of the Existing System
In the existing system of Fruit Super market there are many major functions which are
basically performed .These includes purchasing of items ,selling of items for their customers,
storing item’s.

INPUTS

Input s in Fruit Super market is:

 Customer order
 Items those are purchased by owners for sale from national distributors.

Input items purchased by owners for Fruit super market includes:

 Jose, Highland, softdrink…….

PROCESS

The process performed in existing system of Fruit supermarket are first, the customer order
items then ,the seller shows appropriate location of the items after collecting all the requested
items the clerk check and calculate the total price , and receives the appropriate price
according to the calculation from customer’s .

OUTPUTS

Out puts from Fruit supermarket are sold items to customers in accordance with customer’s
request .

2.2 Business Rule

The existing system has its own formatted rules in which its employees are treated. These rules
are viewed by the owner of the Fruit supermarket as possible as appropriate for governing the
employee’s .And which includes:

 The seller must treat customers in Faithfull manner and should address customer’s
request.
 The Clerk should receive the price of goods honestly from customers and he should
generate report for manager.
 Store keeper should ensure the security of supermarket property’s from physical danger
in the supermarket.
 Manager should control the entire activity in the supermarket and should receive clear
and appropriate report from clerks.

Amu SISPage14
  New items would be registered appropriately and placed with their related items place
correctly.
 Administrator should control the overall information from any biases properly.
 Form could contain items information appropriately

2.3 Report Generated in the Traditional Shopping System

In the existing system reports are generated from clerks to the manager containing information’s
about weekly sold items and their price and also the seller should generate the current conditions
of items like reducing quantity of items, their expiry conditions to manager. And manager
generates total report monthly for the honor.

2.4 Forms Used in Existing System

Forms which are related to our project are used during the time of purchasing process like bill
forms receipt forms and payroll forms.

Amu SISPage15
2.5 Alternative Option to Address the Problem of Existing System
Since there are many problems preserved in statement of the problem in chapter one we are
forced to develop an alternative computerized system in place of more problematic manually
working system for improving the performance of the supermarket

2.6 Optional Analysis and the Proposed New system

Our newly proposed system aimed at creating efficient and fast interaction between each of the
employees’ and also to generate contemporary report rapidly about items information which
includes the quantity of an item left, which item to be purchased as soon as possible and

Which are most in demand contemporarily?

But to provide these services for Fruit supermarket the supermarket needs to have many
expensive features for example these services are meaningless without network connection and
computers. In addition, every one may not have access to computer and difficult to create net
work infrastructure. Therefore, in order to install our new system the Fruit supermarket should
have enough capital to build this system.

2.7 Functional Requirement and Non Functional Requirements

Functional Requirements:
 List the detail of the item.
 Keep alert signal for expired items
 Recording customer information
 Verify the role of the user
 Making product available for customers

Non Functional Requirements:

 System must be against virus attacks.

 The system should have higher speed.
 System should be learnable and usable.

CHAPTER 3

Amu SISPage16
 MODELING

3.1 USE CASE DIAGRAME

The use case diagramed describes the typical interaction between the users of a system and the
system itself.

For the project, the project team has identified the users and use cases that are associated with the
system and the system itself. So the system has the specified actors and use case that is identified
within the new proposed Fruit super market inventory system.

When we describing them use case represents system functionality of the requirement of the
system

Login

Cus t o order and sales

mer

A dmini
s trat or
Edit profile

Mainten item

Cl erk

Sal l es Generate report

pers o n

manag
er
Control and
recive reports

Amu SISPage17
 from the user’s perspective, actors represent the system that provide or receive information from
the system.

3.2 use case documentation

The following list specify the actors and use cases that are identified within the proposed new
Fruit supermarket inventory system .the use case lists have the use case descriptions associated
with the corresponding actos.so the project team documents all these uses case in the following.

Use case name Login

Actors Clerk, sell person, Administrator
Use case id Uc-1
Description This use case describes the Clark, sell person, Administrator login process of the Clark,
sell person, Administrator
-when a user enters the username and password, it checked the inputs with username and
password previously stored in the database.
-If it is valid it allows the user to access and if not valid it displays un authorization
message.
Precondition User must enter name and password.
Typical course of Actors action System response
action Step 1.The user click on Step 2.The system display the login form
the login form Step5.The system verifies its authority
Step 3. The user enter Step 6. The system display the main page
username and password
Step 4. The user click on
the login button
Alternative course Step 7.If the user enter incorrect input
of action Step 8.The system display error message and use case continues at step3.
Post condition User are registered.

Amu SISPage18
 Table 1.1 login

Use case name Edit profile

Actors Manager, clerk
Use case id Uc-2
Description This use case describes the Manager and clerk can edit his/her profile.
-when a user edits the username and password, it checked the inputs with username
and password previously stored in the database.
-If it is valid it allows the user to access and if not valid it displays un authorization
message.
Precondition Enter the user old password, a new confirmation password and submits the form.
Typical course of Actors action System response
action Step 1.the user click edit Step 2: The system displays the Edit Profile form.
profile button. Step 4: The system checks the user using the submitted
Step 3.Themanager or credentials and also equates new with confirmation
clerk enter the user old password.
password a new If new password is equal with confirmation password
confirmation password the system saves the changed password to the user
and submits the form database.

Alternative course Step 5.If the user enter incorrect input

of action Step 6.The system display error message and use case continues at step3.
Post condition The system will edit profile.
Table1.2 Edited profile

Use case name Maintain item

Actors Manager
Use case id Uc-3
Description This use case describes the Manager should maintain item.
-the manager must check if new item are needed and removed when items are
expired.
Pre condition Check the items which are expired and already finished.
Typical course of Actors action System response
action Step 1.the user click list Step 2: The system displays the listed items.
item button. Step 4: The system displays items which are expired

Amu SISPage19
 Step 3.The manager and items which are already finished .
click search button.
Alternative course Step 5.If the user not found the item which are expired or already finished.
of action Step 6.The system display not found message and use case continues at step3.
Post condition Delete and add items.

Table1.3Maintain item

Use case name Generate reports

Actors Sells person, clerk
Use case id Uc-4
Description This use case describes the Sells person and clerk should enter appropriate
data.
-when the users enter data then the system generate reports.
Per condition Enter appropriate data about customer information and items.
Typical course of Actors action System response
action Step 1.user enters Step 2: The system process the data.
customer information. Step 4: The system generate reports.
Step 3.the user click
report button
Alternative Step 5.If the user dose not enter the customer information.
course of action
Step 6.The system display no report message and use case continues at step3.
Post condition The system store and display reports.
Table 1.4 generate reports

Use case name Control and receive reports

Actors Manager
Use case id Uc-5
Description This use case describes the manager must control all activity and receive reports
from the system.

Pre condition Check and access the stored reports.

Typical course of Actors action System response

action Step 1.user click on the Step 2: The system display all information.
report button.
Alternative Step 3.If there is no information entered previously.

Amu SISPage20
course of action
Step 4.The system displays no report available message.
Post condition Control the overall system.

Table 1.5 controls and receive report

Use case name Order and sales

Actors Sales person, Customer and Clerk
Use case id Uc-6
Description This use case describes the general activity of order and sales process
between sales person, customer and clerk.
Pre condition Customer orders the items.

Typical course Actors action System response

of action Step1.customer Step 2: The system displays position of item.
should order item and
sales person login
then click search Step 4. The system store the record and displays
button. the record
Step3. Customer pays
then clerk received
and record in pay
button
Alternative Step 5.if the item is not found
course of action
Step 6.The system displays the item is absent available message. Then
step 3
Post condition Pay the item price.

Table 1.6 order and sales.

3.3 Sequence Diagram

Amu SISPage21
 user : Security Edit profil
<<controler>> <<ul>> Account
<<actor>>
Sequence for edit
profile.UC-2

S tep 1.the user click edit profile

button.
Step 2: The system displays the Edit
Profile form Wants to change
S tep 3.Themanager or clerk enter the password
user old password a new confirmation <<creat>>
password and submits the form.

Step 4: The system validates the

Enter old
password if it doesn’t match with the password
one stored in account turns to step3
Enter new
password

is illigible()

mantain
password

Amu SISPage22
 user login
list of items form List of Items Mantain items
sequence <<actor>> <<controller>>
diagram for
maintain item
:UC-3
request
S tep 1.the user click list item invoke
button

Step 2 : The system displays check

the listed items.

S tep 3.The manager click search

button. process

S tep 4: The system displays

items which are expired and
items which are already finished
.

. Step 5.If the user not found

the item which are expired or
already finished
Step 6.The system display not mantain items
found message and use case
continues at step3.

respond

Amu SISPage23
 Customer Report
User Login Information <<ul>>
<<actor>> <<controller>> Manager
<<ui>>
Sequence Diagram login password
for maintain item
UC-3
check
S tep 1.user enters customer clike onlist item
information.
Step 3.the user click report
button
do filter
Step 2: The system process
the data. process
Step 4: The system generate
reports

Step 5.If the user dos e not

ente r the customer
information.
Step 6.The s ystem di s pl a y
no report mes s age
pripare
a nd use case continues
at step3.

Generate report to

Amu SISPage24
 User Login report button Report Main screen
<<actor>> <<controller>> <<ul>> <<ui>> <<ui>>
Sequence Diagram
for controlle and check
login password
recive reportUC-5

Step 1.user click on the report

button click on

Step 2 : The system display all

information

Step 3.if there is no information

do filter
entered previously
process
Step4: The system display no
report available message.

is There()

Desplayes reported
items list

Amu SISPage25
 User Login search button pay button Main screen
Sequence Diagram <<actor>> <<controller>> <<ul>> <<ui>> <<ui>>
for order and sales
UC-6 check
login password
Step1.customer should
order item and sales
person click on
login then click search
button.
Step 2: The system record payment
displays position of item.

process
Step3. Customer pays
then clerk received and
record in pay button Desplayes record

Step 4. The system store

the record and displays the
record absent item
Step 5.if the item is not
found

Step 6.The system

displays the item is absent
available massage

Amu SISPage26
3.4 Analyses level class diagram
The adding lend information process takes item name, item number, customer
order ,item category and material information as input and the system checks
the validity of the data and add it to the database

FOR SALES ITEM PROCESS

Input process Output

item number
-type
sales item
-purchased amount computer display the
-data purchase reportes
-customer
description

Evaluation

FOR EDIT PROFILE PROCESS

Input process Output

user name password

Edit profile Modify the old
change password
password and record
confirm new
the new password
password

Evaluation

Amu SISPage27
FOR GENERATING REPORT

Input process Output

sales item and thair Report generat

computer generate
payment
reports
expiry date item

Evaluation

FOR MAINTANING ITEM

Input process Output

new item number Maintane item

item position add and remove item
removed item

Evaluation

Amu SISPage28
 UML Class Diagram

Customer Sell Personn

Custname:(string) 1
1_* Sname(string)
CustAddrss:(string)

cridetrating() Report()
sale()
Login()

1
Corporate customer Personal Customer

contactname(stirng)
Criditrating(string) CreditNumber(double)

1_*
Criditlimit(double)

Remined() Order and sales

Billformonth()
Record()
Daterecived(Date)
isPrepared(boolean)
Price(double)
Itemtype(string)

Cleark Dispatch()
1 1_*
close()

clearkname(string)
pricerecived(double)
Manager
Login()
Report()
Calculate()
Sales() 1 1 Managername(string)

Delet()
Add()
control()
Change()

Amu SISPage29
3.5 User interface prototyping
User Interface prototype is an iterative analysis in which users are actively
involved to the system. We use Web Based Graphical User Interface

login form

manager sale person clerk Administratore

Home Home
Home
accounting
form
system search
info box
controll form foim

calculating
info box
edite
profile form
search
form cash
list and search pamyemnt
form form
record form

record form

CHAPTER FOUR

Conclusion and Recommendation

4.1 Conclusion

In conclusion this project is initiated to identify and analyze some of problems associated with
the Fruit supermarket inventory management system and also mainly to come up with possible
solution.

Amu SISPage30
These system flexible to access, update, delete, insert & producing report for any data that is
found in the database with easy GUI approach. The system notified when the item is expired and
its quantity reaches minimum.

4.2Recommendation
Our recommendation towards the project is modification of some modules and adding of some

Features to make it more dynamic and prefect this system can be made more efficient and
general

To all super markets with a little modification within a short period of time

The features that we recommend to be included in the system are:

 Super market inventory system needs to allocate enough budgets for further
investigation on the system so as to come up with fully developed system that
incorporates the ideas and ways we raised in this system analysis and development.

 It is better to be web based since our system is window based

 It should also work for other super market
 It is better for users if they communicate in their national language
 It is better to use online system.
 It is better to use barcode reader.

THANK YOU

Amu SISPage31