AKSUM UNIVERSITY

AKSUM INSTITUTE OF TECHNOLOGY

FACULTY OF COMPUTUING TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

PROJECT PROPOSAL TITLE: STORE MANAGEMENT SYSTEM FOR

AKSUM INSTITUTE OF TECHNOLOGY

GROUP MEMBERS ID No
SELAMAWIT HAILE AKU0906380
ABADIT KASAHUN AKU0906345
ASKALE WELEAREGAY AKU0906351

Advisor’s name: Teklay Muruts

i
 Axum, Tigray, Ethiopia
September, 2023

ACKNOWLEDGMENT
First of all, we would like to thank the GOD for helping us from the beginning to the end of the
project. The team would like to give deepest thanks to those who helped us for the
accomplishment of this project. Firstly, we would like to say thanks with great respect to our
advisors TEKLAY MURUTS (MSC.) For his constructive comments, for the successful
completion of the first phase of the project and we would like to thank our friends and classmate
for their suggestion and support

ii
ABSTRACT
The AIT store in Aksum University uses manual process system. When customer needs any
materials they must go to the office and record what they want manually, that’s way it is
making the process too late. Which requires the employee to use paper based recording files
to know the status of each customer and to perform the process in the system. Which leads
the system to be inefficient. As part of the effort to bring efficient and modern store
management system in AIT, The new system should be designed and implemented that
enables properties to be controlled and managed properly. The implemented of the system
will be user friendly and built in php programming language and the database. The approach
we are going to implement will be structured query language (MY-SQL) server which will be
more appropriate to store database and queries.

iii
Contents
ACKNOWLEDGMENT...............................................................................................................................ii

ABSTRACT.................................................................................................................................................iii

CHAPTER ONE............................................................................................................................................1

1.1. Introduction................................................................................................................................1

1.2. Statement of the Problem...........................................................................................................1

1.3. Objectives of The Project...........................................................................................................2

1.3.1. General Objective 2

1.3.2. Specific Objectives 2

1.4. Purposes of the Project...............................................................................................................2

1.5. Scope of the Project...................................................................................................................2

1.6. Methodology..............................................................................................................................3

1.6.1. Data Gathering Method 3

1.6.2. System Analysis and Design Methodology 3

1.7. Significance of the Project.........................................................................................................3

1.8. Feasibility Study........................................................................................................................4

1.8.1. Technical Feasibility 4

1.8.2. Economic Feasibility 4

1.8.3. Operational Feasibility 4

1.8.4. Legal Feasibility 4

1.9. Development Tools....................................................................................................................4

iv
 1.10. Cost Analysis.............................................................................................................................6

1.11. Time schedule............................................................................................................................7

CHAPTER TWO...........................................................................................................................................8

Requirement Analysis Description................................................................................................................8

2.1. Introduction................................................................................................................................8

2.2. Overview of the Existing System..............................................................................................8

2.3. Activity of the System...............................................................................................................8

2.4. SWOT Analysis.........................................................................................................................9

2.5. Overview of the Proposed System...........................................................................................10

2.5.1. Functional Requirements 11

2.5.2. Non Functional Requirements 11

2.6. User Requirement....................................................................................................................12

2.7. Constraints...............................................................................................................................12

2.8. Assumptions.............................................................................................................................12

CHAPTER THREE.....................................................................................................................................13

System Modeling.........................................................................................................................................13

3.1. Use Case Model:......................................................................................................................13

3.1.1. Actor Specification 13

3.1.2. Use Case Diagram 14

3.1.3. Use Case Description 16

Table9: Request online 21

3.2. Sequence Diagram...................................................................................................................29

3.3. Class Diagram..........................................................................................................................36

CHAPTER FOUR........................................................................................................................................37

System design..............................................................................................................................................37

4.1. Introduction.......................................................................................................................................37

4.2 Design goal........................................................................................................................................37

v
 4.4. Deployment Diagram...............................................................................................................39

4.5. Access Control and security.....................................................................................................39

4.6. User Interface Design..............................................................................................................41

References....................................................................................................................................................42

List of tables

Table1: list of software tools...........................................................................................................5

Table2: Cost analysis.......................................................................................................................6
Table3: Actor Specification...........................................................................................................13
Table4: Use-Case Description for Login.......................................................................................16
Table5: Use-Case Description for add item...................................................................................17
Table6: View Request....................................................................................................................18
Table7: Approve Request..............................................................................................................19
Table8: Update Item Information..................................................................................................20
Table9: Request online..................................................................................................................21
Table 10 View Item.......................................................................................................................22
Table 11: Cancel Request..............................................................................................................23
Table 12: Search for Item..............................................................................................................24

vi
Table 13: Delete User....................................................................................................................25
Table 14: Register User.................................................................................................................26
Table 15: View Report...................................................................................................................27
Table 16: Manage User..................................................................................................................28
Table 17: Access Control and security..........................................................................................40

vii
List of figures

Figure 1: Time Schedule..................................................................................................................7

Figure 2: Use Case Diagram..........................................................................................................15
Figure 3: Sequence diagram for Login use case...........................................................................29
Figure 4: Sequence diagram for update item info.........................................................................29
Figure 5: Sequence diagram for search item.................................................................................30
Figure 6: Sequence diagram for cancel request.............................................................................30
Figure 7: Sequence diagram for view item....................................................................................31
Figure 8: Sequence diagram for delete user..................................................................................31
Figure 9: Sequence diagram for manage user................................................................................32
Figure 10: Sequence diagram for register user..............................................................................32
Figure 11: Sequence diagram for view report...............................................................................33
Figure 12: Sequence diagram for add item....................................................................................33
Figure 13: Sequence diagram for request online...........................................................................34
Figure 14: Sequence diagram for request approving.....................................................................35
Figure 15: Sequence diagram for view request.............................................................................35
Figure 16: Class Diagram..............................................................................................................36
Figure 17: deployment diagram.....................................................................................................39

viii
CHAPTER ONE

1.1. Introduction

Aksum University is a public higher education institution located in the historical town of
Aksum. It was launched in the year of 1999 E.C in Tigray regional state at Aksum town. Now a
day it is one of the governmental higher institutions found in our country and renders quality
education to students of the university.
Even though Aksum University is one of the competent higher institutions in Ethiopia, there are
a number of constraints in its service delivering. One of those problems is Aksum institute of
technology’s (AIT) store management system. The current store management system gives vast
service however it uses manual management system which leads the system to be inefficient. As
part of the effort to bring efficient and modern store management system in AIT, the new system
should be designed and implemented that enables properties to be controlled and managed
properly.
When customer needs any material they must go to the office and record what they want
manually tthat’s why it makes the process too tedious and time consuming and which requires
the employee to use paper based recording files. The implementation of the new system is user
friendly and built in php programming language and the database. The approach it is going to be
implemented is structured query language (MY-SQL) server which is more appropriate to store
database and queries.

1.2. Statement of the Problem

The existing store management system is functioning using manual system. We can list the
problems shortly as follows.

 The manual system is much time consuming to work with. Searching and getting available
items requested for use by staff takes long time and it is tedious.

 The extra energy and time required to be with the manual system creates a gap in other
sectors of professions.

 Materials are recorded and issued manually through long steps.

1
 Employees couldn’t get clearance on time because of the store manual record checking
systems.

 It is vulnerable to data lose.

1.3. Objectives of The Project

1.3.1. General Objective

General objective of the proposed system that we are going to develop is to automate the current
manual based system and to put web based store management system for AIT.

1.3.2. Specific Objectives

 Understand Manual process and its efficiency of the existing system

 Review the current system to know the problem.

 Identify functional and nonfunctional requirements.

 Propose possible solutions for current system.

 Model the new system using object oriented methodologies.

 Finally implement and test the new system.

1.4. Purposes of the Project

The project is significant to simplify store management systems in many aspects. For instance,
the employee works the activities without any kind of confusion, wastage of time and
interruption. Besides of this, customer also gets efficient service without any confusion.
Generally, there are different bodies that will be benefited from this system.

1.5. Scope of the Project

This project is intended to develop online store management system that will assist the customers
and handle the overall operations, including register user, adding items, approve request items,
manage users(update, delete), view items, search items (is it exist or not).

2
1.6. Methodology

1.6.1. Data Gathering Method

 Interview

An interview was conducted with the entire store worker to get detail information about
the store.
 Observation

We have tried to observe the recommended methods and to really understand the manual system
and We have tried to observe how AIT store workers do their work.

1.6.2. System Analysis and Design Methodology

We have used object-oriented methodology in this project to model the functionality of the
system, to organize the objects, classes, to identify the relationship between each object and
classes and the behavior of the objects. Because object-oriented methodology enables us to
reuse, maintain, modify design and code of the system and it increases consistency among
analyzer, designer, and test.

1.7. Significance of the Project

 Unauthorized person will be out of service

 Each tasks are performed easily

 Can perform many tasks in short period of time

 Reduce unnecessary resource wastage.

 Reduce work overload.

 System gives fast service to the customer

The target beneficiaries of the project:-

 Developer: - the first and the most benefit of this project for the developer is satisfaction.

 Employers: - Aksum University, AIT.

3
 Staffs: - Administrative staffs, Instructors, Technical assistance of the institute.

 Student: - AIT students.

1.8. Feasibility Study

Depending on the results of the initial investigation the review is now expanded to a more
detailed feasibility study. Feasibility study is a test of system proposal according to its
workability, impact of the store management system ability to meet needs and effective
use of the resources

1.8.1. Technical Feasibility

Technical feasibility is the measure of practicality of the specific technical solution and the
availability of technical resources and skill. The proposed system can be easily maintained and
repaired without requiring high specialists or technical assistants.

1.8.2. Economic Feasibility

The system which we have developed is economically feasible. It is financially affordable. And
have economic benefit. Since computer devices and different materials are available, there is no
more cost to develop our system. This system is targeted to be in accordance with the above-
mentioned issues.

1.8.3. Operational Feasibility

The system is operationally feasible as it very easy for the end users to operate it. Operational
feasibility covers two aspects. One is the technical performance aspect and other is the
acceptance within the organization. The system that this project team will develop is user

friendly.

1.8.4. Legal Feasibility

The proposed system has no any conflict with any government directives, because it gives
services for the people effectively and efficiently so the organization is profitable and the system
is legally feasible.

1.9. Development Tools

We used different hardware and software to develop the project.
4
  Hardware tools:

Computer: we use a computer which is operating system of window7

Flash disk: to move our data from one machine to another

External hard disk: to store our project

 Software tools:

Table1: list of software tools

Tools/programs Activities

HTML Client side coding

JavaScript Client side scripting

MySQL Database server

Object oriented PHP Server side scripting

Notepad++ Text editor

MS-word 2010 Documentation

MS-PowerPoint 2010 User training

UML(Unified Modeling Language) Modeling tools

Mozilla fire fox, UC Browser browsing

But the system needs to fulfill the following software:

 Operating system: MS-window 2003, 2008 server is used for the system.
 Database management software (DBMS): is the mandatory one for the new system.
To implement the database easily, (MySQL) is recommended.
 Application software: to develop user and administrative interface it also used for
connecting to the database, Most MS-Office applications are appropriate.

5
  PhpMyAdmin: choose PHP scripting language which aims at providing the user with
an interface that is easy to learn and attractive.
 Macromedia Dreamweaver and notepad++: to edit the PHP code.

1.10. Cost Analysis

Table2: Cost analysis

No Material Amount Price per unit Total price

1 A4 size paper 200 sheet 3 birr 600 birr

2 Pen 3 10 birr 30 birr

3 Flash disk 16 GB 2 250 birr 500 birr

4 For print 3 times 250 birr at once 750 birr

5 Laptop 1 20,000 birr 20,000 birr

Total= 21,880 birr

6
1.11. Time schedule
Figure 1: Time Schedule

7
CHAPTER TWO

Requirement Analysis Description

2.1. Introduction
This chapter deals with analyzing the general work flow of the existing system. It produces a
broad outline of the proposed system that identifies the function to be performed and the
technical aspect that the system must fulfill and briefly describes the existing system
functionality, problem of the existing system. It also deals the functional and non- functional
requirements of the proposed system. The system requirement specification is necessary
requirements that are required for the project development. To derive the requirements, we need
to have clear and thorough understanding of the products to be developed or being developed.
This is achieved and refined with detailed and continuous communications with the project team
and customer until the completion of the web page.

2.2. Overview of the Existing System

The existing store management system currently is functioning using manual system. Firstly the
user requests their needs to the purchaser and the purchaser approves the request. And also the
store manager checks the item whether it found in the system or not. If the requested material is
exist the user fill the form and take the item that he/she need. But if the requested item is existed,
store manager permitted to the purchaser to buy the requested item and the manager announce to
the user the item you need is coming.

2.3. Activity of the System

The proposed online store management system provides efficient way to access in the system.
This system enables users to do work in relaxed way by reducing manual works, errors and that
attempts to replace the manual system has the following nature.

 The system can record any new item issue requested items with appropriate
specification and category.

 The system generates a unique ID for each new fixed asset which is added to the
database.

8
  The system can enable to search items that are available in the store house and use.

 It shortens the step by step processes in delivering items.

 It generates up to date report at any time for decision makers for budget allocation
and controlling.

 The system has database security. Since each workers in the store house has its own
privilege to do their allowed operation on the database.

2.4. SWOT Analysis

SWOT analysis (alternatively SWOT Matrix) is a structured planning method used to evaluate the
Strengths, Weaknesses, Opportunities, and Threats involved in a project. A SWOT analysis can be
carried out for a product. It involves specifying the objective of project and identifying the
internal and external factors that are favorable and unfavorable to achieving that objective. Being
manual, by itself doesn’t mean it has no strengths, when we say one system is weak, its weakness
is more magnified than its strengths.

1. Strength: These are characteristics of project that give it an advantage over others.
a. Storage Area: No space is required to accommodate signed paper files but the
existed system needs large storage area.
b. Data Retrieval: Since the means of communication is web based is easily
accessible.
c. Time: Time required to communicate among different authorities is web based
and it takes less time compared to the manual system
d. Security: Files not vulnerable to manipulations and damage. But, in the existed
system paper files can be easily destructed or manipulated.
e. Accuracy: The existing system mostly characterized by prone to error. The
probability of making error in current system is high. Since there is no way of
validating inputs, data entry errors cannot be easily detected. Accuracy can be
attained in the new system by validating user inputs.
f. Sharing files: In the new system, by using computer networks, sharing files is
easy. File is identical on every computer across the network and only authorized
bodies are allowed to access and modify them.

9
 g. Cost: Cost spent for stationary materials such as paper and printer toner is
minimized.
2. Weaknesses
These are characteristics that place the team at a disadvantage relative to others. Here It is
advantageous to use manual system when:

a. No accessibility without power

b. Offline inaccessible

3. Opportunities
These are elements that the project could exploit to its advantage. These includes

a. The project may improve the work quality and increase motivation of users to
work on the new system.
b. It will decrease user’s workloads.
c. Increase the efficiency of the system, as the result service delivered to the AIT
community will be fast.
d. It will improve safety. Since the outputs of the system will be accurate and data
stored in database is confidential.
4. Threats
These are elements in the environment that could cause trouble for the project. These include:

a. Power interruptions
b. Network problems(LAN, slow internet speed)
c. User’s computer skills.
d. Technological advancements – may need the software maintenance and update to
fit the new demands.

2.5. Overview of the Proposed System

the new system is targeted to address the problem of the current system and to support
additional manipulations or features. Our proposed system will overcome the problems
being faced by the manual management system. The newly proposed system is online
system that the users can access the web page and can get different services from this
website.

10
2.5.1. Functional Requirements
Log on: the system validates the store staff to use the system.

Receive Item: the system allows the store keeper to enter a new item which comes from
deliverer or donor at the acquisition time.

Approve Request: the system allows the store administrator to search the availability of
the items in the store before approving the requested item availability and relevance.

Cancel Request: the system allows the store administrator to cancel the approved request
before the items are issued by the store keeper using approval number.

View Report: the system allows the store administrator and store keeper to overview and
report from the system database monthly.

Request Item: the staff request item to the system.

Search Item: the store man search the item whether it found or not in the store. The
system generate error message that says the number of certain item become zero

2.5.2. Non Functional Requirements

 Maintenance: The store Management System is being developed in php. Php is an
object oriented programming language and shall be easy to maintain

 Portability:-The store Management System shall run in any Microsoft Windows

environment that contains php Runtime and the Microsoft Access database.

 Reliability: - The store Management System service should not access without
authenticate user.
 Usability: - The graphical user interface of the system shall have easily understood
to the user (have consistent look and feel graphical user interface).
 Performance: -Acceptable response times for system functionality.
 Security: - Access to the various subsystems will be protected by a user log in
screen that requires a user name and password.

11
2.6. User Requirement
 The user interface shall be menu driven, it shall provide dialog boxes; help screens,
drop down lists, radio buttons, check boxes and text boxes for user input.
 The navigation from one screen to the other must be easy.
 Necessary material for using the system will be easy to the customer.
 Customers must fullfil the business rule to apply registration.
The store keeper can check the items that are taken by the users

2.7. Constraints
Time: this project has to be finished according to the planned time stated in the schedule
of the project section.
Cost: the system has to be in the range of the budget stated above in the budget of the
project section.
Resources: the resources needed for this project other than the designing team this
system are computers, web designing software, and database.
Quality: quality comes with cost. When thinking of a particular quality specification
related to our system, the cost must be considered with it.
Risk: any risk arose in the project should be addressed immediately before causing any
trouble like if a slip in schedule happens, it should be handled.
2.8. Assumptions
The methodologies being used in this project will help us get the information we need
The project will go according to the planned schedule
The scope of the project will cover what needs to be cover to address the problems
The project’s cost will stay the same with initially planned budget
After the completion of this project, it will be available to anyone who want to use this
system.

12
 CHAPTER THREE

3. System Modeling

3.1. Use Case Model:

A use case describes particular functionality that a system is supposed to perform. Each use
case describes a possible scenario of how the external entity interacts with the system. The
use case is made up of a set of possible sequences of interactions between systems and users
in a particular environment and related to a particular goal.

3.1.1. Actor Specification

Actors and use cases are determined from the analysis of function requirements. An actor is a
role that somebody or something external to the system plays with regard to a use case. The actor
can be a human or an external system. For the proposed systems the identified actors are:

 Store Manager

 Store Keeper

 Users

Table3: Actor Specification

No Actor Name Descriptions Use Case

1. Store Manager A person who manages  Log in

the system.
 Manage user

 Register user

 Delete user

 View report

13
 2. Store Keeper A person who keep the  Login
store.
 Update item
information

 View item

 Add item

 Search item

 View request

 Approve request

3. User A Person who access  Log in

activities from system
 Search item

 View item

 Request online

 Cancel request

3.1.2. Use Case Diagram

Use case diagram shows the interaction between the actors and the use cases which is found in
our proposed system. Our system is represented using a use case diagram in the figure below:

14
Figure 2: Use Case Diagram

15
 3.1.3. Use Case Description
Use case description includes descriptions of the use case name, use case ID, preconditions, post
conditions, basic course of action and whatever which is important in modeling the user goal.

Table4: Use-Case Description for Login

Use case name Log in

Use case ID UC-1

Participating actor(s) Store manager, store keeper, and user.

Description This use case is used to insure security for login in to the system.

Pre-condition The actors must have at least correct username and password.

Basic course of action Step1: actors have to open the system.

Step2: The system displays the login interface and allows the user for the
username and password.

Step3: the actors fills username and password

Step4: Click login button

Step5: Display login successful

Step6: The actors gets access the system

Step7: Displays its main window.

Step8: Use case end.

post-condition The login page will be displayed then user gets access to its privilege and after

16
 finishing his/her work he can logout

Alternative course of action If the actors are not authorized, the system gives a confirmation message that
is wrong username and password and go to step 3.

Table5: Use-Case Description for add item

Use case name Add item

Use case ID UC-2

Participating actor(s) store keeper

Description This use case is used to allow add new item from received item

Pre-condition The store keeper should have username and password and login into the
system.

Basic course of action Step1: The store keeper click on received item link
Step2:The system displays received item form to the store keeper
Step3: The store keeper enters details of new item.
Step4: The system will check the validity and display successful massage

Step5: The store keeper stores the item to database

Step6: Use case end.

post-condition The item is added to the database.

Alternative course of action If there is any invalid entry then the system displays error message and allows
the store keeper to re-enter the correct data.

17
 Table6: View Request

Use case name View request

Use case ID UC-3

Participating actor(s) store keeper

Description It allows the store keeper to see the requested from the user

Pre-condition The store keeper must have a full Privilege to view the request

Basic course of action Step1:The store keeper click on view request link
Step2: The system displays view request form.
Step3: The Store keeper click the view button.
Step4: The system displays the requested data.
Step5: use case end.

post-condition The Store keeper view the list of requested from the system.

Alternative course of action The system displays empty box when there is no request

18
 Table7: Approve Request

Use case name Approve request

Use case ID UC-4

Participating actor(s) store keeper

Description It allows the store keeper to approve request

Pre-condition The Store keeper should log in to the system.

Basic course of action Step1: The Store keeper click on request approval form link
Step2: The system display request approval form
Step3: The user inserts their user username and password
Step4: The system displays the requested data that request by the user
Step5: The Store keeper will check the request form data

Step6: Store keeper approve the request

Step7: use case end.

post-condition Approve and save the data to the store database.

Alternative course of action If the requested item is not exist the system displays not found message

19
 Table8: Update Item Information

Use case name Update Item Information

Use case ID UC-5

Participating actor(s) store keeper

Description It allows the store keeper to Update Item Information

Pre-condition The store keeper should login to the system

Basic course of action Step1: The store keeper click on form of update link
Step2:The system displays the form
Step3: The store keeper inserts item name to search the updating item.
Step4: The system display the update information
Step5: The store keeper fills the updating information.
Step6: The store keeper click update button.

Step7: The item will be updated

Step8: use case end.

post-condition The item will be updated

Alternative course of action If there is any invalid entry then the system displays error message and allows
the store keeper to re-enter the correct item name.

Table9: Request online

20
Use case name Request online

Use case ID UC-6

Participating actor(s) User

Description It allows the user to request online

Pre-condition The user should login to the system

Basic course of action Step1: The user click on the form of request link.
Step2: The system displays the request form.
Step3: The user fill the form to send request
Step4: The system validates request form.
Step5: The user send request by clicking send button.
Step6: The request form is now registered.
Step7: Use case end

post-condition The users request registered to the system.

Alternative course of action 1. If the entered password and user name is incorrect go to step 2
[alternative course of action 1]
2. If the entered information are incorrect go to step 5 [alternative course
of action 2]

Table 10 View Item

Use case name View Item

Use case ID UC-7

Participating actor(s) Store keeper and user

21
Description It allows the store keeper and user to View Item

Pre-condition The actors should login to the system

Basic course of action Step1: The actors click on view item form link.
Step2: The system displays the form.
Step3: The actors click the view button
Step4: The system displays the items that are stored in the system.
Step5: Then the actors see the list item and decide what they want

post-condition Retrieve stored items and view the item list.

Alternative course of action If the entered user name and password is incorrect, go to step 2[alternative
course of action 1].

Table 11: Cancel Request

Use case name Cancel request

Use case ID UC-8

Participating actor(s) User

Description It allows the user to cancel request.

22
Pre-condition The user should login to the system

Basic course of action Step1: The user click on request form link
Step2: The system displays request form.
Step3: The user search the request form by their id
Step4: The user sees and checks the previous request form.
Step5: When they are not available, cancel the request.

post-condition The user cancel the request

Alternative course of action If the id is incorrect go to step2

Table 12: Search for Item

Use case name Search for Item

Use case ID UC-9

Participating actor(s) Store keeper and user

Description It allows Store keeper and users to Search for Item

Pre-condition The Store keeper and users should log in to the system.

Basic course of action Step1: The actors click on the search item form.

23
 Step2: The system display the form
Step3: The actors insert the item name.
Step4: The actors click search button
Step5: The system displays the information of search item

post-condition The Store keeper and users search the item by click search button.

Alternative course of action If the name of item is incorrect go to step 3.

Table 13: Delete User

Use case name Delete user

Use case ID UC-10

Participating actor(s) Store manager

Description It allows Store manager to delete users.

Pre-condition The actor should log in to the system.

Basic course of action Step1: The actor click on form of delete users link

24
 Step2: The system displays the form
Step3: The actor enters user ID.
Step4: The system Search the user information from the database
Step5: The system display confirmation (yes or no)
Step6: The actor Delete the user successfully.

post-condition The user is out of the service.

Alternative course of action If the user id is incorrect go to step 3.

Table 14: Register User

Use case name Register user

Use case ID UC-11

Participating actor(s) Store manager

Description It allows Store manager to register users.

Pre-condition The Store manager should log in to the system.

Basic course of action Step1: The actor click on the form of register user link.
Step2: The system display the registration form
Step3: The actor fills the attributes of the beneficiary

25
 Step4: The actor clicks register button
Step5: The beneficiary is registered to the Database

post-condition The beneficiary is registered to the Database

Alternative course of action If the entered attribute(s) is(are) incorrect go to step 3

Table 15: View Report

Use case name View report

Use case ID UC-12

Participating actor(s) Store manager

Description It allows Store manager to view reports

Pre-condition The Store manager is log on to the system

Basic course of action Step1: The actor click on the form of view report link
Step2: The system displays the view report form

26
 Step3: The actor clicks the view report button
Step4: The system displays the reports.
post-condition view the reports

Table 16: Manage User

Use case name Manage user

Use case ID UC-13

Participating actor(s) Store manager

Description It allows Store manager to manage users.

Pre-condition The store manager should log in to the system.

Basic course of action Step1: The actor go to manage user link

27
 Step2: The system displays manage user form.
Step3: The Store manager search user by entering user id .
Step4: The system displays the user information page.
Step5: Store manager can enable/disable the user

post-condition The Store manager can enable/disable user in the system.

Alternative course of action If the user id is incorrect go to step 3.

3.2. Sequence Diagram

The sequence diagram is using primarily to show the interaction between objects in the
sequential order that those interaction occur. The main purpose of sequence diagram is to define
event sequence that result in some desire outcome.

28
Figure 3: Sequence diagram for Login use case

Figure 4: Sequence diagram for update item info

29
Figure 5: Sequence diagram for search item

Figure 6: Sequence diagram for cancel request

30
Figure 7: Sequence diagram for view item

Figure 8: Sequence diagram for delete user

31
Figure 9: Sequence diagram for manage user

Figure 10: Sequence diagram for register user

32
Figure 11: Sequence diagram for view report

Figure 12: Sequence diagram for add item

33
Figure 13: Sequence diagram for request online

Figure 14: Sequence diagram for request approving

34
Figure 15: Sequence diagram for view request

35
3.3. Class Diagram
Class diagrams are refined by adding relationships between classes, attributes, and methods.
Representing how objects of the static view are used to realize use cases in sequence diagrams.

Figure 16: Class Diagram

36
CHAPTER FOUR

System design

4.1. Introduction
System design is a process of delivering the analysis model into design. It also a process of
describing, organizing and structuring system components at architectural design . This chapter
mainly concerning with the design part of the system. In order to make the implementation easy
the design is very important.

4.2 Design goal

Design goals describe the qualities of the system that we should consider. Some of the design
goals are: -

 Response time: reduces the waiting time taken to response a request.

 Minimize error: the proposed system minimizes errors occurred during performing of the
tasks.

 Availability: the proposed system is available to employers every time in the week.

 Performance: -the proposed system has high performance compared to the existing
system.

 Security: the proposed system should authenticate users to reject unauthorized users.

 Easy to use: the project has a well-defined and easily understood interface

 Storage capability: -the system has ability to store information in the database.

 Usability: - the system is easily access and used everywhere in which internet connection
is available

37
4.3. System Decomposition

Subsystem decomposition is the process of decomposing or separating the system in to smaller

system for easily understands, design, and implement the system. The overall system can be
decomposed into server and client sub system.

The proposed system is decomposition of three subsystems.

a. Store Manager Subsystem: -this subsystem has the following functionalities

 manage user

 delete user

 register user

 view report

b. Store Keeper Subsystem: -this subsystem has the following functionalities

 Add item

 Update item information

 View item

 Search item

 Approve request

 View request

c. User Subsystem: -this subsystem has the following functionalities

 View item

 Search item

 Request online

 Cancel request

38
4.4. Deployment Diagram
The deployment diagram shows how the software components, processes, and objects are
deployed into the physical architecture of the system. It shows the configuration of the hardware
units (e.g. Computers, communication devices, etc.) and how the software components are
distributed across the units.

Figure 17: deployment diagram

4.5. Access Control and security

Access control is a way of limiting access to a system or to physical or virtual resources. In
computing, access control is a process by which users are granted access and certain privileges to
systems, resources or information. Access control systems, users must present credentials before
they can be granted access. In physical systems, these credentials may come in many forms, but
credentials that can't be transferred provide more security.

Table 17: Access Control and security

39
 Actor

Function Store manager Store keeper user

Delete user 

Registration user 

Manage user 

View report 

Update item information 

Add item 

View item  

Search item  

Approve request 

View request 

Request online 

Cancel request 

4.6. User Interface Design

The goal in user interface design is to make the user's interaction as simple and as efficient as
possible, in terms of accomplishing user goals. Graphical user interface design is utilized to
support its usability by allowing users to interact with the new system through graphical icons
and visual indicators.

40
41
References
[1] Introduction to object oriented analysis and design with UML and the unified process by
Stephen R.schach

[2] System analysis and design 5 th Edition. By Julice E. and Kondall Price H. Software
Requirements 3rd Edition all 2002

[3] Modern Systems Analysis and Design Seventh Edition Jeffrey A., Hoffer Joey F., George,
Joseph S., and Valacich.

[4] Software Engineering - Pressman

[5] http://www.tutorialspoint.com

42