ADAM

A SIENCE AND TECHNOLOGY

UNIVERSITY
SCHOOL OF ELECTRICAL ENGINEERING AND
COMPUTING
DEPARTEMENT OF CSE

Inventory management system for ASTU

GROUP MEMBERS

1, MULUKEN CHIFRAYE………………………..R/00752/07

2, NAHUSENAY TWEDROS…………………….R/00766/07

3, HENOK ADUGA………………………………….R/00524/07

4, HANA KEBEDE……………………………………R/00511/07

5, HENOK ENDESHAW…………………………….R/00530/07

Submitted to:-Bushera Ali

Submitted date:-Apr19-2019
 Inventory management system for ASTU

Submitted by
HenokAdugna _____________________ April 19,2019
Student Signature Date
Hana Kebede _____________________ April 19,2019
Student Signature Date
HenokEndeshaw _____________________ April 19,2019
Student Signature DateMulukenChfraye ________________ April 19,2019
Student Signature Date
Nahusenaytwodros _____________________ April 19,2019
Student Signature Date
MulukenChfraye ________________ April 19,2019
Student Signature Date
Approved by
1. Bshura Ali_______________________ April 19,2019
Advisor Signature Date
2. ______________________ ______________________ ____________________
Chairman, Dept.’s Signature Date
Senior project Committee
Department
3. _______________________ ______________________ ___________________
Head of the Dep’t Signature Date

Acknowledgment
We have taken efforts in this project. However, it would not have been possible
without the kind
support and help of many individuals and organizations. We would like to extend our
sincere

i
 Inventory management system for ASTU

thanks to all of them.

We are highly indebted to Adama Science and Technology University for the
opportunity it
provided us to work on this project and explore further knowledge.
We would like to express our deepest gratitude towards our advisor Mr. Bushra Ali
for his
guidance and constant supervision as well as his kind co-operation and
encouragement, which
helped us in completion of this project, which is a Software Requirement
Specification (SRS)
document.
Our thanks and an appreciation goes to all of those who have willingly supported and
helped us
out with their abilities.

Acronym
IMS……………………Inventory Management System
ASTU….....................Adama Science And Technology University
NCT…………………….Nazareth Technical College
NCTE…………………Nazareth College of Technical Teacher Education
DB……………………… database
HTML……………………Hyper Text Markup Language
CSS………………………Cascading Style Sheet

ii
 Inventory management system for ASTU

SQL…………………….Structural Query Language

PHP…………………….Hypertext Processor
UML…..........................Unified Modeling Language
JS…………………....Java Scrip

Abstract
The objective of this project is Building online inventory management system for
Adama Science and Technology University. Inventory management is one of the
basic problems in almost every company. Before computer age paper tables and paper
work solution was being used as inventory management tools. These was very labor
taking, waste so much time, even needed many employees just for this section of an

iii
 Inventory management system for ASTU

organization. Every process was based on paper, human fault rate was high, and the
process and tracing the inventory losses were not possible. And now we have
proposed to implement new solutions to these problems. The aim of this web
application is to provide the basic tool for tracking as well as monitoring materials of
ASTU. Software based systems bring the advantage of having the most efficient
control with less effort and employs.

The importance of this project will be thethorough description and analysis of

thebasic and necessary functionalities of an Inventory Management System web-
based system. In addition, the cornerstone of the project will be the development of
the online inventory management system and implementation of different techniques
and functions for basic security.

Table of Contents
page

Acknowledgment .................................................................................................................................... iI

Acronym.....................................................................................................................................................I
II
Abstract ......................................................................................................................................................
iV Table of
Contents ....................................................................................................................................... v
1.Chapter
one ............................................................................................................................................. 1 1.1.

iv
 Inventory management system for ASTU

Introduction.......................................................................................................................................... 1
1.2. Background
……………………………............................................................................................................ 1 1.3.
Statement of the problem.................................................................................................................... 3
1.4. Purpose of the
project.......................................................................................................................... 3 1.5. objective
……………..................................................................................................................................41.5.1.
General objective………………………………………………………………………………………………………………………….4
1.5.2. Specific
objective………………………………………………………………………………………………………………………….4 1.6.
Feasibility
study.....................................................................................................................................41.6.1.
Technical feasibility.............................................................................................................................4
1.6.2. Operational
feasibility.........................................................................................................................5 1.6.3.Economic
feasibility…………………………………………………………………………………………………………………..…..5 1.7Scope and
limitation...............................................................................................................................61.7.1.
Scope…………………………………………………………………………………………………………………………………………….6
1.7.2.
Limitation………………………………………………………………………………………………………………………………………6
1.8.Significance of the
project.....................................................................................................................6 1.9.
Methodology.........................................................................................................................................71.
9.1.fact finding
methodology.....................................................................................................................71.9.2.softewar
e development methodology................................................................................................7
1.9.3.Development
tools.............................................................................................................................8 1.10.Testing
plan...........................................................................................................................................81.10.1.uni
t test..............................................................................................................................................9
1.10.2.integration
test..................................................................................................................................9 1.11. overview
of project phase...................................................................................................................9
1.12.schedule..............................................................................................................................................
101.13. Team
composition ............................................................................................................................10

2.Chapter two 2.1 major functionality of the current

system………………………………………………………………………………………..122.2.user of the current
system………………………………………………………..……………………………………………..……..122.3.problem of the
current system…………………………………………………..………………………..………………………….132.4.business rule
of the current system……………………………………………..……..…………………………………………..14

3.chapter three proposed

system3.1.overview………………………………………………………………………………………………………….………………….
….……….153.2.functional requirement……….
…………………………………………………………………………………………….…………….163.3.non-functional
requirement….…………………………………………………………………………………………………………173.4.system

v
 Inventory management system for ASTU

model………………………….
……………………………………………………………………………………………………….183.4.1.scenario……………………………
…….…………………………………………………………………………………………………….183.5.usecase
model…………………………….
…………………………………………………………………………………………………..293.5.1.actor
identification……………………………………………………………………………………………………………………….303.5.2.use
case diagram and description………………………………………………………………………………………………….31
3.6.object model……………………………………………………………………………………………………………………………………
40 3.7.class
diagram ………………………………………………………………………………………………………………………………….42
3.8.dyanamic model
……………………………………………………………………………………………………………………………..44

3.8.1.sequence
diagram………………………………………………………………………………………………………………………..44 3.9.Activity
diagram……………………………….………………………………………………………………………………………………49
3.10.State
diagram………………………………………………………………………………………………………………………………..57

4.chapter four system design

4.1.Overview…………………………………….………………………………………………………………………………………………
664.1.1.purpose of the system design……………………………….
…………………………………………………………………………………….66
4.1.2.design goal
…………………………………………………………………………………………………………………………………..664.2.proposed
system architecture…………………………………………………………………………………………………………67
4.2.1.system process…………………………………………………………………………………………………………….
……………….67
4.2.2.subsystem decomposition……………………………………………………………………………………….……………………
74 4.2.3.hardware/software
mapping…………………………………………………………………….………………………………….764.2.4.persistent data
management…………………………………………………………………….………………………………….76
4.2.5.component
diagram……………………………………………………………………………………………………………………..814.2.6.deploym
ent diagram…………………………………………………………………………………………………………………….85
4.2.7database
design…………………………………………………………………………………………………………………………….89
4.2.8.access control ………………………………………………………………………………………………………………………………
90 4.2.9.user
interface design…………………………………………………………………………………………….………………………
924.2.10.reference……………………………………………………………………….
……………………………………………………………93

vi
Inventory management system for ASTU

vii
 Inventory management system for ASTU

1. Chapter one

1.1. Introduction

Inventory management is an integral process supported by all departments. Effective

and efficient management of equipment and materials, throughout their life cycle,
help ensure university activities are performed in accordance with their policies,
procedures, and sponsor requirements.

This document deals with analyzing the goals, objectives and policies 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.

In this analysis phase we have to collect the details about the project such as what are
all operations that will make interactive and what are all the fields that have to be
present in the database, and the database must store the details of the user .

Analyzing the requirements what we want to do the project and collecting the
requirements needed to develop the project are done in this phase. Also we have to
design the project in mind how it has to be and what are all the operations that have to
carry in the project and how it has to be interactive with the users. In this phase only
we will collect the information about the project.

Generally it is a guide line for the implementation of the system and it shows how we
can do the whole activates of the system including functional, nonfunctional
requirements and system design. After this stage the system design of the project will
carry out.

1.2. Background

Adama Science and Technology University (ASTU) Was first established in 1993 as
Nazareth Technical college (NTC), offering degree and diploma level education in
technology fields. Later, the institution was renamed as Nazareth College of
Technical Teacher Education (NCTTE), a self-explanatory label that describes what

1
 Inventory management system for ASTU

the institution used to train back then: candidate who would become technical
teachers for TVET colleges/Schools across the country.

Following its inauguration in May 2006 as Adama University, the full-fledged

University started opening other academic programs in other areas-an extension to its
original mission. However, it was not until it was nominated by the ministry of
Education as center of excellence in technology in 2008 that it opened various
programs in applied engineering and technology. For its realization, it became a
university modeled after the Germany paradigm: it not only became the only technical
university in the nation, but also the only one led by a Germany professor. The same
period saw pioneering of the university in introducing PhD by Research and
MA/MSC by Research programs.

Adama science and technology university have material management system which
was working as manually to record such as receiving order request, give conformation
for orders they receive, ordering material, and so on. Also the time waste through this
rotation is a lot. In additional to these is a lot of material dropped out through the
ground without any one who take the responsibility.

The central objective of the project is to develop web based inventory management
system(IMS) for Adama science and technology university(ASTU), which can
manage and keep the items stored, maintenance of non-working item etc. In the
existing system inventory management are done manually. As the case study is to
understand the problems which are usually encountered during manual operation of
the inventory management of the ASTU.it was more time taking for the store man to
know the type of available items, there size, the number of non-working items etc.
Another major disadvantage is that of preparing the list of all items available in the
store will more time.

Computerized inventory management enables the user to select and order items they
need without going to the store and he/she can request maintenance support for
nonworking item. Thus, the user can save so much time not only fast as well as
convenient but also very cheap. For those ASTU resource we want to develop
inventory management system because they use manual to store the item currently.

2
 Inventory management system for ASTU

1.3. Statement of the Problem

ASTU inventory management System is working using the old fashioned manual
system which is bulky and wastage of time and money. There are a lot of problems
around the existing system. Here is the list of the problem we found in existing
system:

 Loss of Information for each material in the case of manually problems

 Material profile is kept in manually document.
 Huge amount of paper is needed to register each material profile.
 Unable to find Specific material profile if the customer wants to ask in the
case of finished or if repair needed it takes days to get his/her desire.
 Since the material or information about the material is paper based it may
exposed to external damages.

 The data or information of the resources is not secured.

 The management process for the manager is very tedious and complex.
 It consumes time and it is not fast as needed.
 The total number of available items in the store is not known very well.

1.4. Purpose of the project

The main purpose of this project is to develop centralize inventory management

system which is used to control inventory in the compass

Companies often use inventory management software to reduce their carrying cost.
The software is used to track products and parts as they are transported from a vendor
to a warehouse, between warehouse, and finally to a retail location or directly to a
customer.

Inventory management software is used for a variety of purposes, including:

 Maintaining a balance between too much and too little inventory.

 Tracking inventory as it is transported between location.
 Receiving items into a warehouse or other location.

3
 Inventory management system for ASTU

 Picking, packing and shipping item from a warehouse.

 Keeping track of product sales and inventory level.
 Cutting down on product obsolescence and spoilage.
 Avoiding missing out on sales due to out of stock situation.

1.5. Objective

1.5.1. General objective

The general objective of this project is to develop a web-based material inventory
management system for store ASTU.

1.5.2. Specific objective

The specific objectives of our project are objectives that we have to follow to reach
the final or general objective of our project. To achieve the above general objective
the proposed system has the following specific objectives. These are

 Study the existing system

 Gathering required information for proposed system
 Analyzing gathering information
 Considering applicability of proposed system for the engineering unit
 Designing the proposed system
 Implement the system
 Test the system
 Deploy the system
 handover

1.6. Feasibility study

Feasibility study is essential to evaluate the cost and benefits of the new system. The
main objective of the feasibility study is to test the Technical, Operational and
Economical feasibility for adding new modules and replacing old running
system. It includes the following aspects:-

4
 Inventory management system for ASTU

1.6.1. Technical feasibility

The entire group members are expected the system to be technically feasible. The
system is going to be developed by following the object oriented system development
technique. The team has the ability to develop this system without any difficulty since
the team has studied the required methodologies and tools. So the system will be
technically feasible. The project member also have knowledge about PHP, Java script,
CSS, MySQL database and enterprise architect to design the system. Besides, the
group members have enough capability to develop the project. So the system is
technically feasible. In general using the different techniques, we can perform the
work up to the desire of the organization, even though fulfilling human being’s need
in all direction may be difficulty.

1.6.2. Operational feasibility

Operational feasibility is a measure of how well a new system solve the problems,
how the system operate with existing resource and how much our system easy to
operate by different users.

The system have definitely a positive impact on users as they involved in the
development of this project by providing their feedback and adapt easily how it will
support their day to day business operation.

We follow each step how the existing system is working and our technical skill
transform the existing system into a web based one. The new system is also
compatible to any web browser. Based on these points our new system is operational
feasible.

1.6.3. Economic feasibility

This is to determine the benefitsand savings that are expected from a new system and
compare them withcosts of time. If benefits outweigh costs, then the decision is made
to design and implement the system.

The new system is economically feasible because the new system uses software and
hardware tools that are available by low cost or even forfree(open source software),
so compared to the benefits it is going to get by implementing the system that will

5
 Inventory management system for ASTU

eliminate the time and cost consuming process of traditional inventory management
system by providing a fully automated way of web based inventory management
system with an optimal security.

1.7. Scope and Limitation

1.7.1. Scope
The scope of our the system includes : -Category of material, Registering basic
information of material, Details of material ,Generating report, Price
Details ,Available material information ,Entering the detail contact information, and
other information, Member management ,Member id is generated automatically from
the table by auto generation, Entering the details like primary information,
professional information, contact information and other information in material
Admin Office of ASTU.

1.7.2. Limitation
Limitations are matters and occurrences that arise in a study which are out of the
researcher's control. They limit the extension to which a study can go, and sometimes
affect the end result and conclusions that can be drawn. The few limitations in this
web application are as follows:
 Since, it is a web-based system the service given by the system is not
accessed by users as long as there is no connection

1.8. Significant of the project

At the end of the project the System will have many Significant for the ASTU. This
system helps the ASTU material management system by making simple, reliable, and
convenient through one integrated system. It helps also the lectures and staff members
of ASTU by saving their time.

6
 Inventory management system for ASTU

1.9. Methodology

1.9.1. Fact finding methodology

The Method and techniques used to analyze the existing system and designing web
system includes, document analysis, practical observation. Those methods which help
us to gather the required data to analyze our project and those methods selected due to
the time and the organization’s willingness.

1.9.2. Software development methodology

In developing a system, there are various methods to be followed. The two most
common ways are an algorithm/procedural based and an object-oriented based. The
traditional approach is using the algorithmic perspective where the main building
block of software is the procedure or function. This view leads developer to focus on
issues of control and decomposition of larger algorithms change (and they will) and
the systems grow (and it will).

The current state of the art reveals that Object-Oriented perspective(approach) is

better than the others as it is suitable to update the system easily, minimize size of
programming codes, easiness of maintainability, represents the natural look and
internal relationship of any system documentation and so on.

In object-oriented approach the main building block of all software system is the
object and class. An object is a thing where as a class is a description of a set of
common objects .every object has identity (you can name it or otherwise distinguish it
from other objects), state (there is some data associated with it) ,and behavior ( you
can do things to the object, and it can do things to other objects , as well ).

The unified modeling language (UML) which is a method adapted from the object-
oriented approach will be used by the consultant group to accomplish the task. The
UML is appropriate for modeling systems ranging from enterprises information
systems to distributed web based applications and even to hard real time embedded
systems. The UML is a language for visualizing, specifying, constructing and
documenting the artifacts of software intensive systems.

To develop web based IMS for ASTU we use waterfall software process model.
Because at the beginning of the project we know the requirements clearly , it is

7
 Inventory management system for ASTU

document driven , it allows for right planning and control by project managers ,and
also we use an object oriented approach because of its:-

 Better organization of inherent complexity (use of inheritance and reusability

of codes)
 Reusing objects classes that have been written, tested, maintained by other
cuts development, testing and maintenance time.
 More extensible and maintainable systems.
 Objects enable programmers to customize an operating system to meet new
requirements without disrupting system integrity.
 Objects communicate by means of messages.

1.9.3. Development tools

Generally system development tools we will use are

Front ended:-

 HTML:-For web-designing
 CSS: - For layout design, content decoration in user interface design
 JavaScript:- for validating client side input and forms
Back ended:-

 PHP:-can generate dynamic page content and back end programming

language.
 My SQL:-For Back-End Database Server
 Wamp server:- as a server and notepad++ used as text editor or Xamp

1.10. Testing plan

Testing process identifies errors and makes correct them so as not to happen after it.
The testing process will be done by other parties such as our friends, classmates and
our advisor.

 Executing a program with the intent of finding an error.

 To check if the system meets the requirement and be executed successfully
in the intended environment.
 To check if the system is “fit to purpose”.

8
 Inventory management system for ASTU

 To check if the system does what it is expected to do.

1.10.1. Unit test

This type of testing tests each modules or units of the system is tested alone in attempt
to discover any error that may exist in the code.

Our unit test has been conducted to meet the following objective:

 To test the function of a program or unit of code such as a program or

module
 To test internal logic.
 To verify internal design.
 To test path and condition coverage.
 To test exception condition and error handling.

1.10.2. Integration test

This type of testing tests by integrating the various modules or units of the system
together this phase involves testing of modules which have been integrated in sub
system. Our integration test is by integrating with databases.

Login (): the user enters his/her user name and password and clicks on login button,
the system checks and retrieve if it input is correct otherwise display a message that
tells incorrect password or user name.

1.11. Overview of the project phase

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

plan, and control the process of developing the system. There are different types of
system development methodologies to develop inventory management system; from
those options we use agile method. Because agile method is an iterative, team-based
approach development nature. This approach emphasizes the rapid delivery of an
application in complete functional components. Rather than creating tasks and
schedules, it works by packaging activities into phases called “sprints.”

Within each sprint, we use four different phase those are:-

9
 Inventory management system for ASTU

 Requirement gathering: understanding and identifying requirement of the

system

 Documentation preparation phase.

 Implementation phase

 Tasting phase

1.12. Schedule

Realized within the time duration, we have identified the activities in accomplishing
the project objective with their schedule requirement which is on the table below.

Phase Month
Feb 14 Mar 10 Apr 21 Jun 27 Jul 6 -
- Mar 8 -Mar 29 -Jun 30 - Jul 5 Jul 25

Requirement gathering and analysis

Design
Implementation
Testing
Maintenance
Table 1.1 Time schedule for the project

1.13. Team composition

This technique is used for managing the project team for effective team performance.
The team configuration refers to the members of the team which is determined by the
active and passive languages of the meeting and participation of the group often
referred to as managing strength, team configuration in the narrow sense refers to the
team strength that is the number of interpreters required for a given team depending
on the language used.

10
 Inventory management system for ASTU

Inventory Management System Member

No Name ID Emil Responsibility
1 Hanna Kebede R/00511/07 [email protected] Designing,
programming,analy
sis,implementation
and testing
2 HenokAdugna R/00524/07 [email protected] Designing,
programming,analy
sis,implementation
and testing
3 MulukenChifraye R/00752/07 [email protected] Designing,
programming,analy
sis,implementation
and testing
4 HenokEndeshaw R/00530/07 [email protected] Designing,
programming,analy
sis,implementation
and testing
5 NahusenayTuedros R/00766/07 [email protected] Designing,
programming,analy
sis,implementation
and testing
Table 1.2:-time composition

11
 Inventory management system for ASTU

Chapter Two
2.1. Major functionality of the current system

The major function of the existing system is to register information about ASTU
materials from purchasing to removal of unnecessary or old materials and giving
necessary materials to belong staff members of ASTU.

Process of register a material

 Staff member fill a request form and give the form to a department head

 The department head send the form to School

 The school identify a purchaser to purchase a material that needs by staff

member

 The purchaser after purchasing the material he/she will submit inspection
team

 An Inspection team check the quality of the material submit to store

 The store clerk write down the information or spec of the material and send a
notification to department store

 And the staff member go to store and receive the materials

2.2. User of the current system

I. Staff member

 Fill the request form and give the form to department

 Receive the material from store

II. Department store

 Accept the request form from staff member

 Approve the request form

12
 Inventory management system for ASTU

 Send the request form to department head

III. Department Head

 Receive a request form from department store

 Approve the request form

 Send the request form to school

IV. School

 Receive a request from department

 Select a purchaser to purchase the material

V. Store clerk

 Receive the material from the purchaser

 Send an information of receiving of the material to department

 use Staff id to identify them

2.3. Problem of the current system

 It is difficult to trace and transfer material among stuff members

 It is difficult to identify the new, available and destroyed items in the

university at any time

 During inventory time the existing process is manually count and auditing
process

 There is no any means that show the current status of a given material

 Report generation is time taking and error prone because it is manual

 It is difficult to know the material belongs to individual staff member during

clearance process

 Staff members does not have an option to see material that are registered
his/her name

13
 Inventory management system for ASTU

 Higher official con not see the status item in order to approve or reject new
purchased item request

 It is difficult to generate different type of reports

2.4. Business rule of current system

1. The store asks every employee if there is any material they need using a form once
in a year
2. The employee who needs a new material will fulfill the form and receive the
material

3. If the employee need a material that doesn’t included in the form that provided
form the store, the employee report to the department head.

4. Department Head report the request to the school.

5. The school reports the request to the store.

6. The store provides the requested material to the department head.

7. The employee receives the material from the department head.

8. Sometimes the employee asks his/her request and receives the material directly
from the store.

14
 Inventory management system for ASTU

Chapter Three

3. Proposed system
The proposed system is designed to replace the manual system of inventory
management system in to computerized system. In our proposed system we try to
overcome the problems of the existing system with creating an online system that can
minimize wasting of time, money and energy.

3.1. Overview

The technological innovations and the use of computerized systems is highly being
evolving and increasing from time to time, the knowledge of computers and knowing
how to operate with them is very much important. Fortunately, using web based
system mainly it is computerized system we are tried to overcome the problem of the
current system by increasing the availability and security of the system. One of the
tasks of any material manager is to plan and control the material in the way that its
own organization can achieve its goals.

The proposed system is designed to replace the manual system of inventory

Management System in to computerized system and also designed to store the
material management information in the database for the purpose of reducing the
problem faced by manual system. The application composes different forms to enter
different project detail to the database. And retrieve required information of the
material from the database.

The system we are going to develop will provide a well-organized data storage system
and will create comfortable environment for all employees of ASTU inventory admin
office, staffs, and others like they can easily share, retrieve transfer and store data to
and from the system.

This will decrease the work load of employees for example store clerks in
organizations by means of providing robust and easy interface to interact with. It
also provides material registrations, searches, generate reports, and so many more.

The proposed system will be able to fulfill the under listed expectations.

15
 Inventory management system for ASTU

 It will successfully support the user’s requirements. Specified hardware, software

and business routine must enable the staff effectively undertake their processing
tasks.

 The problem of inaccuracy and data entry error should be easily checked and
remedied

 It must be able to meet functional requirement within a specified time.

 The new system should provide room to eliminate the duplication problem,
which the current system is known for.

 It should be highly economical, demand minimum storage and minimize

redundant data stored by the system in order to reduce the problems associated
with data redundancy.

 The system should provide comfortable environment for work.

 The new system should be able to eliminate the voluminous paper work of the
existing system and produce timely management report.

3.2. Functional requirement

Register material: The system will register material of ASTU.

Display material information:-The system will display the material information.

Manage system user:-The system will provide a way to manage system users for the
admins.

Provide list of materials with necessary information:-The system allows the store
to view list of materials

Requests form:-The system has request form for necessary information.

Keep clients record:-Any types of client record kept in secured way.

Generate reports:-The system will generate report of clerk, and others.

16
 Inventory management system for ASTU

3.3. Non-Functional Requirements

Non-functional requirements are requirements that specify criteria that can be used to
judge the operation of a system rather than specific behaviors and which has no
essential for the system, but it can support and give more quality for the system.

Those are:

Usability:-The system is user friendly. The new system provides web application
user interfaces that are compatible with any browsers. The system shall provide the
easy access ,The system should is easy to understand, Unauthorized person should not
use the system; rather just view the main page and No one can change the password
without log in to the system.

Performance:-The system should respond within a short period of time. It depends

on the performance of the hardware environment and internet connection speed.

Availability:- The system should be available at any 24 hour for user who has
internet connection.

Security:-The system must confidentially be controlled from being accessed by

Unauthorized users (i.e. privilege for each user set by administrator, the user will

Authenticated by his user name and password)

Portability:-The system should be portable thus capable of running on different

Platforms, adaptable with other systems, install able on different machines

Architectures, and replaceable if the need arises.

Error handling:-The system should be able to handle the error when the user of
the system operates the system.

Accessibility:-The system should be accessible at any time since it is needed in

every time. It is web based system, therefore internet connection and platform is
required to be accessible.

17
 Inventory management system for ASTU

Resources:- The system is compatible with specified hardware and software

environment

3.4. System Model

3.4.1. Scenario
 Scenario: 1
Name of use case: login

Participating instance actor: staff member, System admin, central store manager,
department store manager, department head, school head

Entry condition:

 Internet Connections have to be available.

 They have to navigate to einventory.astu.edu.et
 The user has a valid username/password and must login with its own user
name and password which recognize by the system.
Flow of events:

1. The system Display the login form including username and password form.

2. Fill the form and click login button.

3. User Login in to the system.

Alternate conditions:

 If he/she fills the form incorrectly then the system will generate an error
message.
Exit condition: The system saves the entered data into database.

Special requirement: Any web browsers have to be installed.

 Scenario: 2
Name of use case: Add user

18
 Inventory management system for ASTU

Participating instance actor: System admin

Entry condition:

 Internet Connections have to be available.

 They have to navigate to einventory.astu.edu.et
 The user has a valid username/password and must login with its own user
name and password which recognize by the system.

Flow of events:

1. The system displays the login form including username and password form.

2. Fill the form and click login button.

3. User Login in to the system.

4. Click “Add user “

5. The system displays form to Add user

6. The user fills the form

7. Click “Add User” button to add user in to the database.

Alternate conditions:

 If he/she fills the form incorrectly then the system will generate an error
message.
Exit condition: The system saves the entered data into database.

Special requirement: Any web browsers have to be installed.

 Scenario: 3
Name of use case: Delete user

Participating instance actor: System admin

19
 Inventory management system for ASTU

Entry condition:

 Internet Connections have to be available.

 They have to navigate to einventory.astu.edu.et
 The user has a valid username/password and must login with its own user
name and password which recognize by the system.
Flow of events:

1. The system displays the login form including username and password form.

2. Fill the form and click login button.

3. User Login in to the system.

4. Click “Delete user “

5. The system displays form to delete user

6. The user fills the form

7. Click “Delete user” button to delete user from the database.

Alternate conditions:

 If he/she fills the form incorrectly then the system will generate an error
message.
Exit condition: The system saves the entered data into database.

Special requirement: Any web browsers have to be installed.

 Scenario: 4
Name of use case: Add item

Participating instance actor: central store (store Clark)

Entry condition:

 Internet connections have to be available.

 They have to navigate to einventory.astu.edu.et
 The user has a valid username/password and must login with its own user
name and password which recognize by the system

20
 Inventory management system for ASTU

Flow of events:

1. The user inserts username and password and click login button.

2. User Login in to the system.

3. Click Add Item

4. The system displays form to Add Item

5. The user fills the form

6. Click “Add Item” button to add item such as (material type, category)

Alternate conditions:

 If he/she fills the form incorrectly then the system will generate an error
message.
Exit condition: The system saves the entered data into database.

Special requirement: Any web browsers have to be installed.

 Scenario: 5
Name of use case: Return

Participating instance actor: staff

Entry condition:

 Internet connections have to be available.

 They have to navigate to einventory.astu.edu.et
 The user has a valid username/password and must login with its own user
name and password which recognize by the system
Flow of events:

1. The user inserts username and password and click login button.

2. User Login in to the system.

3. Click Return

4. The system displays form to Return Item

21
 Inventory management system for ASTU

5. Click “Return Item” button to Return Item.

Alternate conditions:

 If he/she fills the form incorrectly then the system will generate an error
message.
Exit condition: The system saves the entered data into database.

Special requirement: Any web browsers have to be installed.

 Scenario: 6
Name of use case: update item

Participating instance actor: central store manager

Entry condition:

 Internet connections have to be available.

 They have to navigate to einventory.astu.edu.et
 The user has a valid username/password and must login with its own user
name and password which recognize by the system.
Flow of events:

1. The system displays the login form including username and password form.

2. Fill the form and click login button.

3. User Login in to the system.

4. Click “update item “

5. The system displays form to update item

6. The users fill the form

7. Click “Update item” button to update item in to the system

Alternate conditions:

 If he/she fills the form incorrectly then the system will generate an error
message.
Exit condition: The system saves the entered data into database.

22
 Inventory management system for ASTU

Special requirement: Any web browsers have to be installed.

 Scenarios: 7
Name of use case: Request

Participating instance actor: Staff member

Entry condition:

 Internet connections have to be available.

 They have to navigate to einventory.astu.edu.et
 The user has a valid username/password and must login with its own user
name and password which recognize by the system.
Flow of events:

1. User inserts username and password

2. User Login in to the system.

3. Click “request” button to request a material.

4. Fill the form and click OK button.

Alternate condition:

 If he/she fills the form incorrectly then the system will generate an error
message.
Exit condition: The system saves the entered data into database.

Special requirement: Any web browsers have to be installed.

 Scenario: 8
Name of use case: handover

Participating instance actor: staff member, department store manager, central store
manager.

Entry condition:

 Internet connections have to be available.

 They have to navigate to einventory.astu.edu.et

23
 Inventory management system for ASTU

 The user has a valid username/password and must login with its own user
name and password which recognize by the system
Flow of events:

1. The user inserts username and password and click login button.

2. User Login in to the system.

3. A staff member Click “handover form” button to transfer

4. The system displays the form

5. Fill the form and click OK button.

Alternate conditions:

 If he/she fills the form incorrectly then the system will generate an error
message.
Exit condition: The system saves the entered data into database.

Special requirement: Any web browsers have to be installed

 Scenario: 9
Name of use case: Report

Participating instance actor: central store manager (store Clark),

Entry condition:

 Internet connections have to be available.

 They have to navigate to einventory.astu.edu.et
 The user has a valid username/password and must login with its own user
name and password which recognize by the system
Flow of events:

1. The user inserts username and password and click login button.

2. User Login in to the system.

3. A user click on report generate button

4. The system display the report

24
 Inventory management system for ASTU

Alternate conditions:

Exit condition: The system Exit.

Special requirement: any web browsers have to be installed.

 Scenario: 10
Name of use case: approval

Participating instance actor: department store manager, department head, school head

Entry condition:

 Internet connections have to be available.

 They have to navigate to einventory.astu.edu.et
 The user has a valid username/password and must login with its own user
name and password which recognize by the system.
Flow of events:

1. Users inserts username and password and click login button.

2. User Login in to the system.

3. The system displays request information from the request user

4. Click approval button

Alternate conditions:

 If he/she fills the form incorrectly then the system will generate an error
message.
Exit condition: The system saves the entered data into database.

Special requirement: Any web browsers have to be installed.

 Scenario: 11
Name of use case: Add profile picture

Participating instance actor: staff member, System admin, central store manager,
department store manager, department head, school head

25
 Inventory management system for ASTU

Entry condition:

 Internet connections have to be available.

 They have to navigate to einventory.astu.edu.et
 The user has a valid username/password and must login with its own user
name and password which recognize by the system.
Flow of events:

1. The system displays the login form including username and password form.

2. Fill the form and click login button.

3. User Login in to the system.

4. User click on “Account setting” then click on “Add profile picture”

5. The system allows a user to choose a photo

6. Then the user click on “upload a photo” to a system

Alternate conditions:

 If he/she fills the form incorrectly then the system will generate an error
message.
Exit condition: The system saves the entered data into database.

Special requirement: Any web browsers have to be installed.

 Scenario: 12
Name of use case: update password

Participating instance actor: System admin, central store manager, department store
manager, Department head, school head, staff

Entry condition:

 Internet connections have to be available.

 They have to navigate to einventory.astu.edu.et

26
 Inventory management system for ASTU

Flow of events:

1. Click “Account setting then update password “

2. The system displays form to update the password

3. The user fills the old and new password.

4. Click “Update password” button to update password to the database.

Alternate conditions:

 If he/she fills the form incorrectly then the system will generate an error
message.
Exit condition: The system saves the entered data into database.

Special requirement: Any web browsers have to be installed.

 Scenario: 13
Name of use case: Forgot password

Participating instance actor: System admin, central store manager, department store
manager,

Department head, school head, staff

Entry condition:

 Internet connections have to be available.

 They have to navigate to einventory.astu.edu.et
Flow of events:

1. Click “Forgot password “

2. The system displays form to forgot password

3. The user fill the questioner form then

4. Click “Recover password” button to recover button from the database

27
 Inventory management system for ASTU

Alternate conditions:

 If he/she fills the form incorrectly then the system will generate an error
message.
Exit condition: The system saves the entered data into database.

Special requirement: Any web browsers have to be installed.

 Scenario: 14
Name of use case: notification

Participating instance actor: clerk

Entry condition:

 Internet connections have to be available.

 They have to navigate to einventory.astu.edu.et
Flow of events:

1. Click “send notification “

2. The system displays form to send notification

3. The user fills the form then

4. Click “send notification” button to send notification.

Alternate conditions:

 If he/she fills the form incorrectly then the system will generate an error
message.
Exit condition: The system saves the entered data into database.

Special requirement: Any web browsers have to be installed.

 Scenario: 15
Name of use case: logout

Participating instance actor: staff member, System admin, central store manager,
department store manager, department head, school head

Entry condition:

28
 Inventory management system for ASTU

 Internet connections have to be available.

 They have to navigate to einventory.astu.edu.et
 The user has a valid username/password and must login with its own user
name and password which recognize by the system.
Flow of events:

1. The user clicks on “logout” button.

2. The system will logout the user from the system

Alternate conditions:

Exit condition: The system returns the user to the login page

Special requirement: Any web browsers have to be installed.

3.5 use case model

Use Case

A use case is used during requirement elicitation and analysis to represent the
functionality of the system. Use case focus on the behavior of the system from an
external point of view. A use case describes a sequence of actions that provide a
measurable value to an actor. In other words, it shows a way in which a real world
actor interacts with the system. An essential use case is a simplified, abstract,
generalized use case that captures the intentions of the user in a technology and
implementation independent manner. In order to identify use cases the team examined
the needs of users, the main tasks of users, the information user needs to examine,
create or change, what users inform the system and what the system informs users.

3.5.1 Actor identification

An Actor is something that accomplish use cases upon a system. It is just an entity,
meaning it can be a Human or other system that directly play an external role in the
system.

Name: System admin

Description: A person which are responsible for controlling and auditing system

29
 Inventory management system for ASTU

Role: Give username and password

Name: central store manager

Description: A person which are responsible for governing all items in the store.

Role: control inventory record, give permission to items (product) up on request.

Name: school head

Description: A person which are responsible for giving permission to items

Role: Giving permission to items (product) up on request

Name: department head

Description: A person which are responsible for giving permission and request to
items

Role: Request permission, Give permission to products in department

Name: department store manager

Description: A person who are responsible for keeping record of items (product)

Role: Record, control, view, inventory of items (product)

Name: staff member

Description: staff member is an employee of the company

Role: Request permission to get a product

3.5.2 Use case diagram and description

Use case diagram

A use case diagram illustrates a set of use cases for a system, the actors of these use
cases, the relations between the actors and these use cases, and the relations among
the use cases. The UML notation for a use case diagram is shown on the figure, in
which

30
 Inventory management system for ASTU

 An oval represents a use case

 A stick figure represents an action

 A line between an action and a use case represents that the actor initiates and/or
participates in the process.

31
 Inventory management system for ASTU

class Use Case Mo...

login

central store manager

system admin
manage
manage item
system

«include»
«include»«include»
«include»
«include»«include»
update item manage
manage user content
release item add item
transfer item

«include»
«include»«include»

manage page
add user delete user

priv ilage

department store
manager
«include» «include»
depatment head

request
approv e

Display

«include»
«include»

v iew report
v iew
information
notiication
staff member
school head

logout

Figure 3.1.Use case diagram

Description of use case model

32
 Inventory management system for ASTU

Description 1
Use case name Log in
Use number 1
Use case description Authentication
Participating actor staff member, System admin, central store
manager, department store manager, department
head, school head
Pre-condition They have to navigate to estor.astu.edu.et
Flow of event 1. The system displays the login form
including username and password form.
2. Fill the form and click login button.
3. User login in to the system

Post condition The system saves the entered data into database.
Alternative flow-of events If he/she fills the username or the password it will
display error message
Table3.1:-login

Description 2
Use case name Add user
Use case number 2

33
 Inventory management system for ASTU

Use case description Add user to the database

Participating actor System admin
Pre-condition They have to navigate to estore.astu.edu.et
Flow of event 1. The system display the login form including
username and password form
2. Fill the form and click login button.
3. User Login in to the system.
4. Click “Add user “
5. The system displays form to Add user
6. The user fills the form
7. Click “Add User” button to add user in to the
database.

Post condition The system saves the entered data into database
Alternative flow-of events If he/she fills the form incorrectly then the system will
generate an error message.
Table 3.2:-add user

Description 3
Use case name Delete user
Use case number 3
Use case description Delete user from the database
Participating actor System admin
Pre-condition They have to navigate to estore.astu.edu.et
Flow of event 1. Users inserts username and password and click
login button. User Login in to the system.
2. Click “Delete user “
3. The system displays form to Delete user
4. The user fills the form
5. Click “Delete user” button to delete user from
the database.

Post condition The system delete the entered data into database.
Alternative flow-of events If he/she fills the form incorrectly then the system will

34
 Inventory management system for ASTU

generate an error message.

Table 3.3:-delete user

Description 4
Use case name Add item
Use case number 4
Use case description Add item in to the database related to their category
Participating actor central store (store Clark)
Pre-condition They have to navigate to estore.astu.edu.et
Flow of event 1. The user inserts username and password and
click login button.
2. User Login in to the system.
3. Click Add Item
4. The system displays form to Add Item
5. The user fills the form
6. Click “Add Item” button to add item such as
(material type, category)

Post condition The system saves the entered data into database.
Alternative flow-of events If he/she fills the form incorrectly then the system will
generate an error message.
Table 3.4:-add item

Description 5
Use case name Return
Use case number 5
Use case description Return item from staff to central store
Participating actor staff

35
 Inventory management system for ASTU

Pre-condition They have to navigate to estore.astu.edu.et

Flow of event 1. The user inserts username and password and
click login button
2. User Login in to the system.
3. Click Return
4. The system displays form to Return Item
5. Click “Return Item” button to Return Item.

Post condition The system saves the entered data into database.
Alternative flow-of events If he/she fills the form incorrectly then the system will
generate an error message.
Table 3.5:-return

Description 6
Use case name update item
Use case number 6
Use case description update item that have been added to the database
Participating actor central store manager
Pre-condition They have to navigate to estore.astu.edu.et
Flow of event 1. The user inserts username and password and
click login button
2. User Login in to the system.
3. Click “update item “
4. The system displays form to update item
5. The users fills the form
6. Click “Update item ” button to update item in
to the system

Post condition The system saves the entered data into database.
Alternative flow-of events If he/she fills the form incorrectly then the system will
generate an error message.
Table 3.6:-update item

36
 Inventory management system for ASTU

Description 7
Use case name Request
Use case number 7
Use case description Request an item
Participating actor Staff member
Pre-condition They have to navigate to estore.astu.edu.et
Flow of event 1. The user inserts username and password and
click login button
2. User Login in to the system.
3. Click “request” button to request a material.
4. Fill the form and click OK button.

Post condition The system saves the entered data into database.
Alternative flow-of events If he/she fills the form incorrectly then the system will
generate an error message.
Table 3.7:-request

Description 8
Use case name handover
Use case number 8
Use case description Transfer item that has been requested
Participating actor staff member, department store manager, central store
manager.
Pre-condition They have to navigate to estore.astu.edu.et

37
 Inventory management system for ASTU

Flow of event 1. The user inserts username and password and

click login button.
2. User Login in to the system.
3. A staff member Click “handover form” button
to transfer
4. The system displays the form
5. Fill the form and click OK button.

Post condition The system saves the entered data into database.
Alternative flow-of events If he/she fills the form incorrectly then the system will
generate an error message.
Table 3.8:-handover

Description 9
Use case name Report
Use case number 9
Use case description Report items from the database
Participating actor central store manager(store Clark),
Pre-condition They have to navigate to estore.astu.edu.et
Flow of event 1. The user inserts username and password and
click login button
2. User Login in to the system.
3. A user click on report generate button
4. The system display the report

Post condition The system saves the entered data into database.
Alternative flow-of events If he/she fills the form incorrectly then the system will
generate an error message.
Table 3.9:-report

Description 10
Use case name Approval
Use case number 10

38
 Inventory management system for ASTU

Use case description Approve item request

Participating actor Department store, program head ,school head, central
store manager
Pre-condition They have to navigate to estore.astu.edu.et
Flow of event 1. The user inserts username and password and
click login button
2. User Login in to the system.
3. View request
4. Click Approval button

Post condition The system saves the entered data into database.
Alternative flow-of events If he/she fills the form incorrectly then the system will
generate an error message.
Table 3.10:-approval

Description 11
Use case name Logout
Use case number 11
Use case description log out from the system
Participating actor System admin
Pre-condition They have to navigate to estore.astu.edu.et
1. The system display the login form including username
and password form.
2. Fill the form and click login button.
3. User Login in to the system.
4. After the user enter into system

Post condition The system display the login page

Alternative flow-of events If he/she fills the form incorrectly then the system will
generate an error message.
Table 3.11:-approval

3.6. Object Model

39
 Inventory management system for ASTU

An object model is a logical interface, software or system that is modeled through the
use of object-oriented techniques. It enables the creation of an architectural software
or system model prior to development or programming.

Classes Attribute Operations Description

Authenticate account type authenticate() Authenticate users of
the system
Login user_name login() Logs the user in to
Password the system.
ManageAccount user_name, send Allows the users to
email passwordResetLink() reset there password
Validate_Email() in case they forget
Access level account type allowAccess() Set the access level
denayAccess() of different users of
setAccessLevel() the system.
getAccessLevel()
Staff user name make_request() Allow the users to
password check_notification() log in, make request
view_record() for material, view
make_comment() material they have
handover() from the
organization and
give comment if
something is wrong
on the number of
material they have.
System_Admin user name register() Registers the users
password of the system and
give the user name
and password.
Central_store_Manager user name approval(), Approve request and
password getReport() Can also generate
different report.

Program_Head user name authenticate- Forwards or denies

password request(), the request to central
view_request(), store manager. Can
send_request(), also make request,
getReport() view material he/she
have from the
organization and
give comment if
something is wrong
on the number of
material he/she have.
Can also generate

40
 Inventory management system for ASTU

different report.

Store-clerk user_name register_material() Accepts the request

password send_notification() and give notification
Item_issue() to the requester if the
getReport() material is ready.
Can also generate
different report.

request request_id, request() Allows the users to

request_approval_sta request for a
tus, material.
request_date

Material name, additem() Allow the store

category, manager to add
description, items.
model

Table3.12:-object class

3.7. Class Diagram

Class diagram is a type of static structure diagram that describes the structure of a
system by the system’s classes, their attributes, operations and the relationship among
the objects. Class diagram is the main building block of object oriented modeling.

Its main uses are:

 For general conceptual modeling of the systematics of the application.

 For detailed modeling translating the models into programming code.

A class diagram is typically modeled as rectangle with three sections:

 The top indicates the name of the class.

41
 Inventory management system for ASTU

 The middle contains the attributes of the class.

 The bottom contains the operations the class can execute.

class Class Mo...

material storeclerk

rigisters manageaccount
- mat_discription: char + additem() : void systemAdmin
- mat_model: char + getreport() : void - email: char
- mat_name: char + itemissue() : void - allowacsess() : void - username: char
- notify() : void - denyacsess() : void managers
+ rigester() : void - get_acsesslevel() : void - sendpasswordsetlink() : boolean
- rigester_user() : void - validate_email() : boolean
- set_acsesslevel() : void
+ view_user() : void

program_head
staff
+ approve_request: boolean autenticate
+ get_report: void - firstname: char
- lastname: char - rolid: int
- password: char
+ rolid: int - getlogin() : void
- staffid: char - getrigestered() : void
- username: char + sendpasswordsetlink() : void
- validate() : void
central_store_manager - checknotificaton() : void + validatepasswordsetlink() : void
+ item_transfer() : void
+ approval() : void - make_coment() : void
+ getreport() : void + make_request() : void
+ viewproprety() : void

material_admin

+ approve_request: boolean requests

+ view_report: void acsseslevel
login
- allowacsess() : void
- password: char
- denyacsess() : void
- username: char
- get_acsesslevel() : void
request - set_acsesslevel() : void

+ reques_tapprova_lstaatus: char
+ request_date: char
- request_id: int

+ request() : void

42
 Inventory management system for ASTU

Fig 3.2:-class diagram

3.8. Dynamic Model

3.8.1. Sequence Diagram

 A sequence diagram is an interaction diagram that shows how objects operate with
one another and in what order. It is a construct of a message sequence chart.
 A sequence diagram shows object interactions arranged in time sequence. It depicts
the objects and classes involved in the scenario and the sequence of messages
exchanged between the objects needed to carry out the functionality of the scenario.
Sequence diagrams are typically associated with use case realizations in the Logical
View of the system under development.

43
 Inventory management system for ASTU

Fig 3.3 Sequence diagram for staff, system admin and store manager login

sd pr...

database

staff members, system IMS s creen controller

admin and store
manager
start()

display loginpage()

fill username and passw ord()

click login button()

v alidate user input()

is user()

display homepage()

click logout()

display login form page()

44
 Inventory management system for ASTU

Fig 3.4 Sequence diagram for add item

45
 Inventory management system for ASTU

Fig 3.5 sequence diagram for request materials

46
 Inventory management system for ASTU

Fig 3.6 sequence diagram for request handover

47
 Inventory management system for ASTU

3.9. Activity diagram

An activity diagram describes a system in terms of activities. Activities are states that
represent the execution of a set of operations. The completion of these operations
triggers a transition to another activity. Activity diagrams are similar to flowchart
diagrams in that they can be used to represent control flow (i.e., the order in which
operations occur) and data flow (i.e., the objects that are exchanged among
operations).

48
 Inventory management system for ASTU

1. Log in

Fig 3.7 activity diagram for login

49
 Inventory management system for ASTU

2. Request

Fig 3.8 activity diagram for request

50
 Inventory management system for ASTU

3. view report

Fig 3.9activity diagram for view report

51
 Inventory management system for ASTU

4. generate user

Fig 3.10 activity diagram for general user

52
 Inventory management system for ASTU

5. Register material

Fig 3.11 activity diagram for register material

53
 Inventory management system for ASTU

6. Request approval

Fig 3.12 activity diagram for request approve

54
 Inventory management system for ASTU

7. Handover

Fig 3.13 activity diagram for handover

55
 Inventory management system for ASTU

3.10. State diagram

A state diagram shows the behavior of classes in response to external stimuli.
Specifically a state diagram describes the behavior of a single object in response to a
series of events in a system. This UML diagram models the dynamic flow of control
from state to state of a particular object within a system.

Figure3.14 State diagram for Login page

stm statechart

IMS

[System loaded successfully]

Login page

[System error]

[loaged successfully] [Logout]

Home page

exit

56
 Inventory management system for ASTU

Figure3.15 State diagram for Registration page

stm stat

IMS

[System loaded successfully]

Display login page

[Loged successfully] [Logout]

Home page
[System error]

[Registration selected]

Registration page

Final

57
 Inventory management system for ASTU

Figure3.16 State diagram for request approval page

stm state diagram

IMS

[system loaded successfully]

Loge page

[Loged successfully] [Logout]

Home page

[System error]

[Request approval selected]

Request approv al

[Request aporoved successfully]

58
 Inventory management system for ASTU

Figure3.17 State diagram for Clearance page

stm state diagram

IMS

[System loaded successfully ]

Login page

[Loged successfully] [Logout ]

[System error] Home page

[Clearance page selected]

Clearance page

[clearance created successfully]

59
 Inventory management system for ASTU

Figure3.18 State diagram for request registration page

stm state diagram

IMS

Display login page

[Logout ]

[System error] Home page

Request regisration

60
 Inventory management system for ASTU

Figure3.19 State diagram for Report page

stm state diagram

IMS

Login page

[Logout]

[System error] Home page

Report page

61
 Inventory management system for ASTU

Figure3.20State diagram for Add item page

stm state diagram

ISM

[system loaded successfully]

Login page

[Loed successfully] [Logout ]

[system error] Home page

[Add item selected]

Add item

[Item added successfully]

62
 Inventory management system for ASTU

Figure3.21 State diagram for Delete item

stm state diagram

IMS

[System loaded successfullly]

Login page

[Loged successfully] [Logout]

Home page
[System error]

[Delet item selected]

Delet item

[Item deleted successfully]

63
 Inventory management system for ASTU

Figure3.22 State diagram for handover page

stm state diagram

IMS

Login page

[Logout]

Home page
[System error]

Hand ov er

64
 Inventory management system for ASTU

CHAPTER FOUR
4.1Overview
This is a system Design document to inventory management system for Adama
Science and Technology University. This document includes the design goal, the
proposed system design and object design. Up to know, we were in the problem
domain. System design is the first part to get in to the solution domain in a software
development.
4.1.1 Purpose of the system design
The purpose of this designing is to show the direction how the system is built and to
obtain clear and enough information needed to drive the actual implementation of the
system. This document describes the design issues of the overall system. The
objectives of design are to model the system with high quality so that it could be easy
to make a change to it.

4.1.2 Design Goal

Design goals describe the qualities of the system that developers should optimize. The
design goals are derived from the non-functional requirements of the RAD.

Reliability: IMS for ASTU is designed as secure against human error, deliberate
misuse or machine failure, and in which data will be stored without corruption.

Availability: since the system is an online, it will be accessible through the working
hours of the users, unless some problems happened like connection failure, power
failure and other.

Maintainable: the system design is easy to maintain and this reduces the system’s
maintenance costs, which usually represent a high proportion of the total lifetime cost
of the system.

Secure: In order to protect the confidentiality of the data, It may be important to build
in methods to restrict access to authorized users only. The database can only be
accessed the user with user name and password.

Performance: the response time to users request should be as short as possible.

65
 Inventory management system for ASTU

Cost-effective: This is about designing system that delivers the required functionality,
ease of use, reliable, secured, etc., to the user in the most cost-effective way.

4.2 proposed system architecture

4.2.1System process
composite structure Component Mo...

HTTP
request

send request recive request (web

server) parser

resive send
result result

staff

XML output
admin

store clerk

XMLWitter

program head

central store
manager

Figure 4.1 system activity diagram

Inventory Admin

This section explores in detail Admin architecture design. A top-level overview of the
system, a brief overview of system processes or functionality are described in the below
section.

66
 Inventory management system for ASTU

Service portal
HTTP
USER XML output
Web Server Inventory Admin

DATABASE
figure 4.2. shows Inventory admin system overview in relation to other components.

67
 Inventory management system for ASTU

class Use Case Mo...

HTTP request

send recive
request request(web parser
server)

resive send
request result

XML output
login

approve
request

XML Witter
view report

Figure4.3 inventory admin system process

Staff

68
 Inventory management system for ASTU

Service Portal
HTTP
USER XML output
Web Server Staff

DATABASE
Figure4.4 Staff management system overview

The figure shows Staff management system overview in relation to other components.

class Use Case Mo...

HTTP request

send recive
request request(web parser
server)

resive send
request result
login
XML output check
notification
item
transfer
make
comment
XML Witter
make
request
view
materials

Figure 4.5Staff system process

69
 Inventory management system for ASTU

Program head

Service Portal
HTTP
USER XML output
Web Server Program head

DATABASE

Figure 4.6 program head system overview

The figure shows program head system overview in relation to other components.

class Use Case Mo...

HTTP request

send recive
request request(web parser
server)

resive send
request result
login
XML output

approve
request

XML Witter get report

70
 Inventory management system for ASTU

Figure 4.7. program head system process

Central store manager

Service Portal
HTTP
USER XML output
Web Server Central store
manager

DATABASE
Figure 4.8. central store manager system overview

The figure shows Central store manager system overview in relation to other components.

class Use Case Mo...

HTTP request

send recive
request request(web parser
server)

resive send
request result
login
XML output

approve
request

XML Witter get report

71
 Inventory management system for ASTU

Figure 4.9. central store manager system process

4.2.2.Subsystem Decomposition

Subsystem decomposition's will help reduce the complexity of the system. The
subsystems can be considered as packages holding related classes or objects. The ISM
under consideration is decomposed in to subsystems as shown by the following
diagram. These subsystems are further decomposed into other subsystems.

4.2.2.1 Development view

72
 Inventory management system for ASTU

class Data Mo...

IMS_ system

request

organization
system admin

ASTU inventory_admin

user staff_ member

store_ clerk

Figure 4.10. subsystem decomposition level

73
 Inventory management system for ASTU

cmp Component Mo...

IMS_admin material admin

manage
manege user v iew report
page

manage
delete content
user v iew
notification

giv e user
name and
passw ord
approve
request
admin staff

grant access
admin user

depends on depends on
depends on

staff
store_manager

item_trasnsfer add_ item

make
comment

check_notification get_report item_issue

v ie_ property

notify_staff
mak_
request approv e_request

approve request delivery report

staff_member program_head stor_clerk staff

Figure 4.11. subsystem decomposition level

74
 Inventory management system for ASTU

4.2.2.2. Subsystem Description

Subsystem Purpose Class

System Admin Responsible to provide user  Register user

name and password update
the system as well as manage  View user
user.
 Delete user

Department head Responsible to approve  Approve requests

request from the staff
members and deliver the  get report
request to the department
store or School head in
addition receive report.
Staff member Responsible to makes request  check notification
and make comment.
 Make request

School Head Responsible to approve  Approve request

request from the department
head and deliver the request  View report
to the central store manager.
Central store manager Responsible to approve  Approve request
request from the school head
and deliver the request to the  Get report
store clerk.

Department store manager Responsible for approve  Approve request

request from department  Get report
head and deliver to the clerk

Table 4.1.Subsystem Description

4.2.3. Hardware/software mapping

75
 Inventory management system for ASTU

The following information describes the technologies, techniques and scripting

languages used for the development of the web application. IMS will be a web-based
for online users. The system will run over the windows operating system. The
necessary technologies needed for the web application design, content and
presentation semantics are HTML and CSS. JavaScript technologies are used for the
client-side scripts. The server-side script is PHP and the Relational Database
Management System is MySQL. All the components and technologies are running on
an Apache Linux HTTP Server. The web server will run over Wamp Server. The IMS
consists of three independent components: Web browser, online System Server and
database server. The following UML deployment diagram illustrates the
hardware/software mapping for this system.

4.2.4. Persistent data management

The purpose of this section is to show the mapping of the objects/classes of the
system, identified during the analysis stage, in to the corresponding relational
database.

Key

Mapped

Relational Database
Class
table

76
 Inventory management system for ASTU

Figure 4.12. object staff mapping

class class

staff

- email: char
- fristname: char
- lastname: char
- password: char
+ roleid: int
- staffid: char
- username: char

- checknotification() : void
+ item_transfer() : void
- make_comment() : void
+ makerequest() : void
+ viewproprty() : void

Figure4.13 object store clerk mapping

class class

Store_clerk

- email: char
- firstname: char
- lastname:: char
- password: char
- role: char
- satffid: char
- username: char

+ additem() : void
+ get_report() : void
+ Item_dispatch() : void
- notify() : void

Figure 4.14. object program head mapping

77
 Inventory management system for ASTU

class class

program_Head

- email: char
- firstname: char
- lastname:: char
- password: char
- role: char
- satffid: char
- username: char

+ approve_repuest() : void
+ get_report() : void

Figure 4.15 object central store manager

class class

Central_Store_Manager

- email: char
- firstname: char
- lastname:: char
- password: char
- role: char
- satffid: char
- username: char

+ approval() : void
+ get_report() : void

Figure 4.16.object property mapping

class class

property
Figure4.17. object login mapping
+ pro_catagory: int
- pro_description: char
class class
- pro_model: char
- pro_name: char

+ login
register() : void
- password: char
- username: char

- getlogin() : void
78
- setlog() : void
+ validate() : boolean
+ verify() : boolean
 Inventory management system for ASTU

Figure 4.18. manage account mapping

class class

manageaccount

- email: char
- passwordResetlink: char
- username: char

- sendpasswordresetLink() : boolean
+ setLog() : void
+ validate() : boolean
- validate_email() : boolean

4.2.5. Component diagram

79
 Inventory management system for ASTU

A component diagram (UML component diagram) describes the organization and

wiring of the physical components in a system. It often drawn to help model
implementation details and double-check that every aspect of the system's required
functions is covered by planned development.

It also describes all components in a system, their interrelationships, interactions, and

the interface of the system. It is an outline of the composition structure of
components or modules.

cmp Component Model

component diagram ims

controller

Authentication page Data

controller controller organizer

Component Form controller

controller
«flow»
«flow»
«flow»
«flow» «flow» «flow»

«flow» «flow» «flow» «flow»

«flow»
model
v iew
«flow» «flow»

Profile model Notification Component

model staf v iew View form Footer
model
«flow» template

Activ ity v iew Componentv iew Nav igation

template
Table model Configuration model

Header template Nav igation v iew

Figure4.19: (Component diagram)

Component Description

80
 Inventory management system for ASTU

Authentication controller

Description: This is a class responsible to authenticate a user

Role: it is responsible to check if the validity of a user trying to login to the system

Page controller

Description: This is a route class which will route to each pages as needed

Role: it is responsible to route each page requests in the system.

Data organizer

Description: The base component which is directly linked to the users of the system
and sends it back to the view called view activity.

Role: is responsible for tracking session and displaying the appropriate dash board
and log activities of a user.

Component controller

Description: This is a class which extends the base controller class responsible to
look for components.

Role: this class is responsible to control all the components in the system.

Form controller

Description: the base form controller class in which governs the form submission in
the system and sends back to the view called view form.

Role: this class is responsible for controlling of form submission before further
process.

Profile model

Description: this is a class which is linked with the profile table in the database.

Role: responsible for the extraction of record from and to the table.

81
 Inventory management system for ASTU

Component model

Description: this is a class which is linked with the database table in which used to
determine the

component to display to the user.

Role: responsible for the getting record from the database in order to display the
appropriate component to the user.

Configuration model

Description: it is a class which is used to connect he component controller and the

database table for data exchange.

Role: is responsible to get access to the database table and return the data to the
component controller for further process.

Header template

Description: this is the basic tin plating engine which is the laravel blade

Role: this is used to customize the code so that it would be easier to debug

Navigation template

Description: this is the HTML file used to create the common navigation bar

Role: is used to create a common navigation bar

Activity form

Description: the HTML page which is related to the activity form layouts in the page

Role: this the view class which is used to view the activity forms fetched from the
data organizer Controller.

View form

82
 Inventory management system for ASTU

Description: this is the form viewer class using blade template and connected to the
form Controller class

Role: is used to create the basic form views that will be displayed to the user

Notification view

Description: this is the view class related to the notification views and connected to
data organizer controller class

Role: used to view the notifications for the user

User view

Description: this is the view class using the blade template engine connected to the
component controller class.

Role: used to create the user view to the user

Footer template

Description: the view class using the base template and connected to the footer
controller class

Role: is used to view the footer to the user

Component view

Description: the view class using the blade template engine and connected to the
component controller

Role: used to create the component view to the user

83
 Inventory management system for ASTU

4.2.6. Deployment Diagram

It is a structure diagram which shows architecture of the system as deployment
(distribution) of software artifacts to deployment targets.

 It Describes system hardware, software, and network connections for

distributed computing.
 It covers server configuration and network connections between server nodes
in real-world setting.
 The Deployment model describes how and where the system will be
deployed.
 Physical machines, devices and processors are reflected as nodes, and
the internal construction can be depicted by embedding additional nodes or
artefacts.
 The physical locations, deployment of artefacts and connectivity between
nodes of the final deployed system is depicted in the Topology package.

84
 Inventory management system for ASTU

deployment diagram

Server
Physical firewall for filtering
request,access
Firewall controlling,preventing dos
etc
Computer

http <<filters>> : flows>>

Web browser
Appache Web Server
Web server handles
communication b/n http
IMS
request and IMS system

<<use>>
<<flow>>

Database server Performs:

Data analysis,Storage,Data
mysql database manipulation etc.
server

Fig4.20: Deployment diagram

Start up the system: Having internet connection, a platform and web browser are
enough to initialize the System or Browsing for the URL.

85
 Inventory management system for ASTU

Termination of the system: Closing the browser leads to session destroy. System
termination describes what resources are cleaned up and which systems are notified
upon termination If web server or web server is not started to run then web interface
or web interface will not be visible by the users. After finishing the system interaction
user can be logging out and closes the web.

Failure: Connection down between data transfer. Many possible causes: internet
connection fails, Bugs, errors, external problems (power supply) and also web
application faller may happen.

Error Causes solution

Server Not found Internet connection fail Network connection or
firewall (proxy) protection.
communication link fails IP address is wrong when Verify and test them with
browsering URL. ping.
Hostname in URL Refresh DNS or use IP
is not recognized by local address in URL instead.
DNS server. Verify it based on my.cnf of
Port number is missing SQL DB.
DB server is down.
DB server doesn't accept
TCP/IP connections.
Something in between
PHP blocking connections, e.g.
a firewall or proxy
Web server fail Errors Power outages Using Server fail over.
Overheating High humidity To send a backup
Natural disasters, e.g. automatically on Backup
hurricanes, Floods server.
That means An automatic
server failover solution can
Prevent your website from going
down in the event of a server failure.
Web Application fail web application attacks Firewalls and similar Intrusion
detection mechanisms provide little

86
Inventory management system for ASTU

(treat) cross-site scripting(XSS) defense against full-scale web

and SQL injection Device attacks. Using Server fail over.
driver failures I/O errors, e.g.,
hard disk failures(see database
media failures) Memory parity
errors Network hardware
failures

87
 Inventory management system for ASTU

4.2.7.Database Diagram

Figure4.21:Database Diagram

88
 Inventory management system for ASTU

4.2.8. Access control

In our system, different actors have access to different functionality and data. There
for ,these privileges out of unauthorized users from accessing data’s which they don’t
have privilege access.

The table below shows the global access table, describing the access relation between
the actors, objects and operations in the system:

Table 4.3: access matrix for class’s, staff, manage mtransaction.

Actors Material information Manage material

Staff Material name () Request item ()
material id () Handover ()
material quantity () View material list ()
material category ()

Table 4.4: access matrix for class’s, admin, management user.

Actors User information Manage user account

Admin Staff name () Register user ()
Staff id () Generate password ()
Staff’s department () Delete user ()
Update user information ()
Validate account ()

Table 4.5: access matrix for class’s, report, generate report

Actor Report generate report

System(IMS) report date () generate report date ()
report detail () generate report detail ()

89
 Inventory management system for ASTU

Table 4.6: access matrix for class’s, property management, manage property.

Actor material information manage material

Property manager material name () add item ()
material category () delete item ()
material quantity () update item ()
material id () issue item ()
return item ()

Table 4.7: access matrix for class’s, request item

Actor Request item

Staff material name ()
material id ()
material quantity ()
request date ()
staff name ()

Table 4.8: access matrix for class’s property information, manage staff request.

Actor request information Manage staff request

School head/ material name () view staff name ()
department head material category () view material category ()
request quantity () view item quantity ()
material id () approve staff request ()
disapprove staff request ()

4.2.9. User interface design

90
Inventory management system for ASTU

91
 Inventory management system for ASTU

4.2.10. Reference
Internet, different websites such as
1. (www.google.com, www.ask.com )
2.http://www.en.wikipedia.org/wiki/
3.http://searchsoa.techtarget.com/definition/class-diagram
4. https://en.wikipedia.org/wiki/User_interface_design

Books

1. Copyright © 1999 by Addison Wesley Longman, Inc. The Unified Modeling

Language Reference Manual

2. Jeffrey A. Hoffer, Joey F. George; 1998 Modern Systems analysis and Design

Second Edition

3. Different previous software projects

92