Final Project Document2

HARAMAYA UNIVERSITY
COLLEGE OF COMPUTING AND INFORMATICS
DEPARTMENT OF INFORMATION SYSTEM
Project Title: CUSTOMIZED STORE MANAGEMENT SYSTEM FOR HARAMAYA

UNIVERSITY
Group member
1. Anawar Sharif (580/08)
2. Habtamu Dulo (611/08)
3. Haftom Kidanu (612/08)
4. Eyerus Manaye (598/08)
Project adviser: - Ms.Atakilt.N

Group member
1. Anawar Sharif ( 580/08)
2. Habtamu Dulo ( 611/08)
3. Haftom Kidanu ( 612/08)
4. Eyerus Manaye (598/08)
Adviser by: Co-adviser by:
Mr.Atakilti.M Mr.Woynishet.
Head of department
Mr.Beyene.B(Msc.)
Page | ii
Group member
1. Anawar Sharif ( 580/08)
2. Habtamu Dulo ( 611/08)
3. Haftom Kidanu ( 612/08)
4. Eyerus Manaye ( 598/08)
Approved & adviser/ co adviser by:
Mr……………….. Mr………………..
(lecture….) (lecture….)
Submitted to:Mr.Ataklt.N and Ms.Woynishet.B
JUNE, 2019
Haramaya, Ethiopia
Page | iii
Acknowledgment
First of all, we would like to place ourselves at the feet of God Almighty for his everlasting love
and for the blessings & courage that he gave us, which made it possible to complete our project
and to set us in the right path.
Next we would like to express our deepest gratitude to Mr.Ataklt.N (MSc), who willingly agreed
to supervise and guide us patiently in doing this project. Indeed without his emotional assistance,
encouragement and constructive comments, this project would never have been possible.
Also we would like to express our heartfelt thanks to Ms.Woynishet.B. His constant support
and Encouragement during this phase and forgive us valuable suggestions time to time. Last but
not least we are thankful to our FAMILY members and Friends for their silent cooperation and
passion.
Page | iv
Abstract
Customized store management system is a web based application which aim to change the manual
system into a computerized one which overcome the difficulties of the manual system and make
the university beneficiary. Customized store management systems for HU is the way of the change
existing system into online and it used for keeping property in university.
The main objective of the development of this system is to overcome the problems that exist in
current store management system. Which do online CSMS, filling system for the University this
system is also effective for properly manages the property. And the customers sends request to sell
the property and also staff are take some property from store.
A very common problems in customized store management system can be attributed using of
manual/file based recording system many times advertisement and request perform manually.
There is also no centralized database used to keep the user records and etc… problem is exist.
Web-based customized store management system is website that enables university who want to
manage property easily. It also enables to record and store the data of property and customer,
and it also provides a centralized store management database. The system is developed by
using Bootstrap, PHP, and MySQL as a database system to manage and store the data.
Page | v
Table of Contents
Acknowledgment ........................................................................................................................... iv
Abstract ........................................................................................................................................... v
List of Symbols and Notations ....................................................................................................... ix
List table ........................................................................................................................................ xii
1.2 STATEMENT OF PROBLEM ........................................................................................ 2
1.3 OBJECTIVE OF THE PROJECT .................................................................................... 3
1.3.1 General objectives ........................................................................................................ 3
1.3.2 Specific objective ......................................................................................................... 3
1.4 METHODOLOGY OF PROJECT ................................................................................... 3
1.4.1 Method of data collection ............................................................................................. 4
1.4.2 System development and methods ............................................................................ 4
1.4.3 System development tool .......................................................................................... 5
1.5 Scope and limitation ......................................................................................................... 6
1.5.1 Scope of the project .................................................................................................. 6
1.5.2 Significance of project .............................................................................................. 7
1.5.3 Limitation of the project ........................................................................................... 7
1.6 Feasibility study ............................................................................................................... 8
1.6.1 Economic feasibility ................................................................................................. 8
1.6.2 Technical feasibility .................................................................................................. 9
1.6.3 Operational feasibility............................................................................................... 9
1.6.4 Schedule feasibility ................................................................................................... 9
1.7 Team Configuration and Management ........................................................................... 10
1.7.1 Team Configuration ................................................................................................ 10
1.7.2 Communication plan................................................................................................... 11
CHAPTER TWO .......................................................................................................................... 12
2. Modeling and Prototype ........................................................................................................ 12
2.1 Existing system .............................................................................................................. 12
2.2 Proposed system ............................................................................................................. 12
Overview of the proposed system ................................................................................................. 12
Page | vi
2.3 Functional requirement .................................................................................................. 12
2.4 System requirements, specification and analysis modeling ........................................... 14
2.5 CRC (class responsibility and collaboration) modeling ................................................. 14
2.6 Use case modeling .......................................................................................................... 17
2.6.1 Essential use case modeling .................................................................................... 18
Essential use case descriptions ...................................................................................................... 18
2.6.2 System use case diagram ........................................................................................ 22
2.6.2 Traditional user-interface prototyping ........................................................................ 36
2.6.3 User interface flow diagram ....................................................................................... 37
2.7 Supplementary specifications ......................................................................................... 37
2.7.1 Business rules ............................................................................................................. 37
2.7.2 Nonfunctional requirement ..................................................................................... 38
2.8 Constraints...................................................................................................................... 39
CHAPTER THREE....................................................................................................................... 40
3. Design Document.................................................................................................................. 40
3.1 Class Modeling............................................................................................................... 40
3.1.1 Classes-type layered approach.................................................................................... 42
3.2 Sequence diagram .......................................................................................................... 43
3.3 Activity diagram ............................................................................................................. 47
3.4 User Interface Design ..................................................................................................... 52
3.4.1 Form design ............................................................................................................ 52
Login form .................................................................................................................................... 52
3.4.2 Dialogue and Interface Design ......................................................................................... 53
Figure 3.15 Error dialogue ............................................................................................................ 53
3.4 State chart diagram ......................................................................................................... 54
3.5 Object diagram ............................................................................................................... 56
3.6 Persistence modeling/database design ........................................................................... 57
Normalized physical database model 1st normalized form .......................................................... 59
3.7 Component diagram ....................................................................................................... 65
3.8 Deployment diagram ...................................................................................................... 67
Chapter Four ................................................................................................................................. 68
4. Implementation Document.................................................................................................... 68
Page | vii
4.1 Report on Implementation .............................................................................................. 68
4.2 Implementation plan ....................................................................................................... 68
4.3 System modules.............................................................................................................. 68
4.4 TESTING ....................................................................................................................... 69
Testing procedures .................................................................................................................... 70
4.4.1 Unit testing .............................................................................................................. 70
4.4.2 Integrated testing ..................................................................................................... 70
4.4.3 System Testing ........................................................................................................... 70
4.5 Hardware and Software acquisitions .............................................................................. 70
4.5 Sample Code of the system ............................................................................................ 71
4.6 User manual.................................................................................................................... 82
4.7 Clients Feedback .......................................................................................................... 85
4.8 Conclusion ........................................................................................................................ 86
4.9 Recommendation.............................................................................................................. 87
Reference ...................................................................................................................................... 88
Page | viii
List of Symbols and Notations
Symbols
Use case Diagram symbol
Actor use case Boundary link
Sequence Diagram symbol
Activation message Message return

Object Lifeline constraint
Activity Diagram Symbol
Action state Initial state final state control flow
Class Diagram symbol

Page | ix
Class link Inheritance
Deployment Diagram symbol
Component node instance constraint communication

Notation:
CSMS: Customized store management system
HU: Haramaya University
US: Use Case
OOSAD: object oriented system analysis and design
MYSQL: structure query language
PHP: Hyper Text Processing
HTML: Hyper Text Mark-up Language
UI: User Interface
1NF: First Normal Form
2NF: Second Normal Form
3NF: Third Normal Form
UML: Unified Model Language
DB: Database
Page | x
List of figure
Figure 2.1 class responsibility collaboration diagrams (actor class) 14

Figure 2.2 class responsibility collaboration diagrams (UI class) 15
Figure 2.3 class responsibility collaboration for business class 16
Figure 2.4 essential use cases diagram 17
Figure 2.5 system use case diagram 21
Figure 2.6 Traditional user-interface prototype diagram 33
Figure 2.7 user interface flow diagram 34
Figure 3.1 class modeling diagram 38
Figure 3.2 class type layered approach diagram 39
Figure 3.3 sequence diagram for login 40
Figure 3.4 sequence diagram for update account 41
Figure 3.5 sequence diagram for add property 42
Figure 3.6sequence diagram for create account 43
Figure 3.7sequence diagram for purchase property 43
Figure 3.8 sequence diagram for send request 44
Figure 3.9 login activity diagram 45
Figure 3.10 search account activity diagram 46
Figure 3.11 manage property activity diagram 47
Figure 3.12 search property activity diagram 48
Figure 3.13 State chart diagram for login 51
Figure 3.14 State chart diagram for Update account 52
Figure 3.15 State chart diagram for searching property 53
Figure 3.16 Object diagram 54
Figure 3.17Normalization diagram 61
Page | xi
List table
Table1.4.1 system development tools 5
Table 1.5.1 schedule feasibility 8
Table 1.5.2 team configurations 9
Table 1.5.3 communication plan 10
Table 2.6.1 login use case description 22
Table 2.6.2 manage account use case diagram description 24
Table 2.6.3 manage request use case description 25
Table 2.6.4 view report use case description 26
Table 2.6.5 advertising property use case description 27
Table 2.6.6 View request use case description 28
Table 2.6.7 property manage use case description 29
Table 2.6.8 purchase property use case description 30
Table 2.6.9 generate report use case description 31
Table 2.6.10 update account use case description 32
Table 3.6.1 Persistence Modeling 55
Table 3.6.2 account normalization 56
Table 3.6.3 Request normalization 56
Table 3.6.4 admin normalization 56
Table 3.6.5 storage property 57
Table 3.6.6 Feedback normalization 57
Table 3.6.7 Staff normalization 57
Table 3.6.8 Customer normalization 58
Table 3.6.9 request 2nd normal 58
Table 3.6.10 property 2nd normalization 59
Table 3.6.11 advertisement 2nd normalization 59
Table 3.6.12 Customer 2nd normalization 60
Table 3.6.13 Feedback 2nd normalization 60
Table 3.6.14 Staff 2nd normalization 61
Page | xii
Page | xiii
CHAPTER ONE
1. INTRODUCTION
Store Management systems was a system that used to record and track materials and customer
information. A typical store had a processed and a space within, to receive the incoming materials
(receiving bay), keep them for as long as they were required for use (custody) and then to move
them out of stores for use (issue). In a manufacturing firm this process forms a cycle to maintain
and run the activities of stores. [1]
There were many problems within the existing system such as extensive trained procedures, and
time-consume data manipulation, needs more human power. In addition to this it was limited in
reporting capabilities. The manager had ability to monitored inventory, but there was no dedicated
information through customized store management system. Customized store management system
had developed for web based systems to facilitate different product owners’ management of
customer details and inventory data, which it had include books, cloths and other. We had assigned
to develop a customized store management web based system that had to allow the university to
overcome above listed problem.
1.1 BACKGROUND OF COMPANY
Historical background of the university Haramaya University has gone through a series of
transformations since its establishment as a higher learning institution. The agreement signed
between the imperial Ethiopian government and the government of the United States of America
on May 15, 1952 laid the foundations for the establishment of JIMMA agricultural and technical
school and the imperial college of agricultural and mechanical arts (IECAMA). The agreement
between the government of Ethiopia and the technical cooperation administration of the
government of the United States of America, signed on May 16, 1952, gave the mandate to
Oklahoma state university to establish and operate the college, conduct a nationwide system of
agricultural extension and set up an agricultural research and experimental station.
Based on the emperor’s wish, it was decided to establish the college at its current location at
Haramaya. Later on, the agreement signed between the United States department of states and the
Page | 1
imperial government provided the basis for the operation of Jimma agricultural and technical
school that received its first class of eighty students in October 1952. Nineteen of the students
graduated on august 6, 1953 and became the first freshman students of the imperial Ethiopian
college of agricultural and mechanical arts (IECAMA). The IECAMA opened its doors to its first
batch of students in October 1956 senior class moved from Addis Ababa to Alemaya for their final
semester. At the end of the 1956/57 academic year, eleven students completed their studies and
graduated with a BSC degree in general agriculture. The training programs in agriculture were
further specialized and BSC. Programs were introduced in animal sciences (1960), plant sciences
(1960), agricultural engineering (1961) and agricultural economics 1962.[2]
1.2 STATEMENT OF PROBLEM
The existing store management system was used to store all materials and manage it manually.
This manual system of store management was boring and error prone. Another problem was a
difficulty in searching items, calculating item cost: this was somewhat bad and it takes time to
finish this process.
Furthermore, there is.
 Time delay in generating reports.
 Send request could be apply manual.
 The advertisement could be done manual.
 It should increase updating complexity.
 Data were registered or recorded on excel and word
 Security issue: - When we talk about store management system, the security
must be in the first place. The previous system of HU storage the material
manually, it was easy to breakthrough and stolen it.
 Inaccuracy of information (lose data or information of storage)
Generally, the above problem led the overall the process let and boring Due to this it becomes
necessary for an automated customized store management system to exterminate the bottle neck
of the manual system in place.
Page | 2
1.3 OBJECTIVE OF THE PROJECT
1.3.1 General objectives
The general objective of the project was to develop the web based customized store management
system.
1.3.2 Specific objective
In line with achieving the general objective, the project was going to deal with the following
specific objective.
 Request items is does online.
 Import and export data from excel to inventory.
 It provide capabilities for admin: -Where admin can manage customer, manager, and store
keeper information such as create new manager, store keeper and his information
maintenance.
 Easily control customer details information
 Enable the system user register online in very secret
 Enables the storage workers to record data effectively and efficiently
 It enables to give reliable search facility
1.4 METHODOLOGY OF PROJECT
Choosing a suitable methodology is important because it serve as a guideline when developing the
system step by step. There are a lot of different methodologies that have been created to serve
certain system development. In order to accomplish this project on time and within the cost, we
had follow different procedures which are described below.
Page | 3
1.4.1 Method of data collection
There are two method of data collection that we had used to gather information about our project
they are.
 Primary data collection
 Secondary data collection
Primary data collection

Interviews: we had used this methodology to interview people that was directly involved on
store service and had useful information for that desired system. We had interview the haramaya
university procurement office employers, for example Yonatan Ashanaf and Workinesh Tesfaye.
Yonatan Ashanaf give some information on how they had purchase or selling the property in the
University. Workinesh Tesfaye give information about how the manually control property in the
storage and process it.
Observation: it was a useful data collection technique that assists the team to assess the manual
system by participating or watching in the real work and forms using in the existing manual
system.
Secondary data collection

Documentary analysis: we had use documentary analysis for gathering information (data
collection); we had analyzing the document prepared in the existing system.
The HU procurement directive and store management document
Web site: - The secondary source of data had obtained from HU storage office and from the web
site of http://www.haramaya.edu.et/services/hu-procurement-finance-and-property-
administrationdirectorate/.
1.4.2 System development and methods
A system development methodology refers to the framework that had used to structure, plan, and
control the process of developing the system. There are different types of system development
Page | 4
methodologies. From these we had select waterfall system development method. Because,
Waterfall model is simple to implement and also the amount of resources required for it are
minimal when compared to the others. In this model, output is generated after each stage, therefore
it has high visibility. [3]
The client and project manager gets a feel that there is considerable progress.
The waterfall model serves as a baseline for many other life-cycle models.
 To analyze our project/system we had use UML diagrams and language/model. Such as
use case, sequence diagram, activity diagram etc...
 To design, we had used an object oriented methodology because it was consistent
underlying representation throughout the development process.
Systems Analysis
Systems Analysis is the study of a business problem domain for the purpose of recommending improvements
and specifying the business requirements for the solution.
Systems Design
Designing the human interface and designing Databases are two important activities in the Systems Design
phase. The specification or construction of a technical, computer based solution for the business
requirements identified during systems analysis.
Systems Implementation
The process of transition from the old system to the new system.
1.4.3 System development tool
We had design an interactive web application that customer can access the sites and interact with
the organization.
Page | 5
Table1.4.1 system development tools
1.5 Scope and limitation
1.5.1 Scope of the project
The project is to develop cost effective and efficient store management application package.
Hence, it is expected to include all necessary activities in the store management such as storing
customer information, inventory (stock) activities, reports, and prepare bills to customers.
Generally we had developed the web based store management and then apply to the Haramaya
University.
Major scope of the project:-
 It store for book, medical, electrical material and clothes
 Selling products from store and adding product from vendor purchased
 Inventory management for store
 Vendor support for registration, advertisement the products with discount and service
 It ask quotation to vendor and for vendor send the quotation online
Page | 6
 Quotation comparison order to deliver
 Complete report for admin such as sale, purchase, taxes and profit
 Complete purchase process reports should be in case of any store
 In multilingual
1.5.2 Significance of project
The relevance why we had conducted the project was:
 Understand how Store management system works. And to design an appropriate

computerized system.
 Enhance the service offered inside the store.
 Enables the store customer’s to get fast access and help the store in service giving
operations.
 Manage item and employee information in automatic way.
 Updates relevant information
 Easy to manipulate and maintain the system.
 Easy to generate reports.
1.5.3 Limitation of the project
 This project is works only for Haramaya university store management
 Our system is operate on three language
 Our system does not include issues related with human resource management.
 The system will not use the digital signature
 Not support online payment and will not have connect with banking system.
Page | 7
1.6 Feasibility study
Feasibility study is planning about projects budgets and deadlines. The analysis of factors for
feasibility forms the business case (analysis of the assumptions like resource availability and
potential problems and system cost and benefits) that justifies the expenditure of the resources on
the project. Many of the feasibility studies are included within the project group members and
many ideas have been raised. Among these most of the ways are studied under the following
techniques.[4]
1.6.1 Economic feasibility
Economic feasibility of the project is determined by comparing costs and benefits of the proposed
system provide.
Tangible benefit: - This means the concrete benefit that can be expressed in terms of birr.
 Reduction of paper and pen.
 Reduction of space needed to record data
 Minimize time of operation

  Reduce work overload.
 Small response time and many services
 Easy and fast file management
Intangible benefits: -Benefits of the system that area unquantifiable are
 Improve employees’ moral.

  Error reduction.
 Increase security.
 Increase efficiency.
 Increase satisfaction of customer and employees.
 Increase communication speed.
Page | 8
1.6.2 Technical feasibility
Technical feasibility is to understand the organization’s ability to construct the proposed system.
Deals about testing if it is existing technology have a compatible to new system and develop the
proposed system. Implementation of the proposed system will use windows operating system,
MYSQL server and PHP assuming required hardware and software resources are available for the
development and implementation of proposed system. Therefore, it is technically feasible.
1.6.3 Operational feasibility
Operational feasibility is the degree to which the proposed system will likely solve the business
problems or take advantage of the opportunities specified in the systems requirement documents.
We perform the activity firstly by having the understanding of main problem manually the system
has and we taught has changed this manual system to somehow an automation manner is the best
thing and depending on this, the project result has been operational since it solves their problem.
And to make the workers familiar with the technology, we give the training for about the system
to the working place.
1.6.4 Schedule feasibility
Schedule feasibility is shows the time estimation in which a project will be completed, we used to
Gantt chart technique to show the time schedule.
Page | 9
Table 1.5.1schedule feasibility
1.7 Team Configuration and Management
1.7.1 Team Configuration
In our project, we have four (4) members where each of us has specified work and also the project
is supervised by one of our members. The following are the types of tasks and as well as the
responsibility each of us can have.
Project Customized store management

title
No Name Id Email Role
1 Habtamu Dulo 611/08 habtdu45@gmail.com Project
Prepared manager
by 2 Anuwar Sharif 580/08 sharifanawar@gmail.com Website

designer
3 Haftom Kidanu 612/08 Haftomkidanu7@gmail.com System
analyst
4 Eyerus Manaye 598/08 eyersu123@gmail.com System
Designer
Advisor Mr.ataklit.N&ms.woynshet.B
Table 1.5.2team configurations
Page | 10
1.7.2 Communication plan
While we are working on our project, we used the following techniques in order to meet one
another and then exchange our suggestions or ideas. Those techniques are we were using to
communicate in mobile phone, email, Facebook, Viber and also some other social media
techniques to communicate each other.
Member with Face to face

member
Monday and Saturday 6:00a.m-10:00a.m Facebook
Wednesday 1:00pm-4:00pm Cell phone
Member with Tuesday 2:30a.m-4:30a.m Face to face
adviser Thursday 8:00a.m-10:00a.m Cell phone
Email
Table 1.5.3communication plan
Page | 11
CHAPTER TWO
2. Modeling and Prototype
2.1 Existing system
The existing Store management system uses paper oriented system which means all new items and
all materials that are available in the store are recorded on paper. In the manual store management
system, materials are divided in to two as stuck and fixed assets. Each of them is recorded
separately. Stuck materials are materials that can be used by consumer for a short period of time.
Where us, fixed assets are materials that can be used by consumer for a long period of time. New
materials are bought based on the need of all consumers.
Users are the persons who are external agents to the system. They have interaction with the system.
These persons perform some actions such as providing inputs, removing and updating data to/from
the system.
2.2Proposed system
Overview of the proposed system

The proposed system is the solution of the above mentioned problems, we able to identify the
critical problems clearly observed (that was explained in the limitation of the existing system in
the statement of problem). By using this system an organization can handle its all kinds of above
mentioned works efficiently, accurately, and speedily with all kinds of security features by
involving a few employees. The new system we are going to develop can perform the following
functions:-
 Organizing stocks that run out from the store
 The system ensures each actor enter to the system based on their privilege.
 Search the desired information more quickly.
 To reduce manual efforts in activities that involved repetitive work.  Updating and
deletion of data become much easier
2.3 Functional requirement
Page | 12
Functional requirements are technical details that define what a system is supposed to accomplish.
Functional requirements are supported by non-functional requirements also known as Quality
requirements. Functional requirements are statements of services the system should provide, how
the system should react to particular inputs, and how the system should behave in particular
situations.[5]
It specifies the software functionality that the developers must build into the product to enable
users to accomplish their tasks.
For manager
The newly proposed system performs the following functional requirement.
 Advertising purchased property based on store keeper request
 Report and request view that come from store keeper and customer
 Register property
 Purchase property
For Admin
 Control overall activities in the system
 Manage user account
 Active/deactivate the created account
 Approve/reject request come from manager and customer
Customer
 Register to participate in buying property.
 View advertisement
Store keeper
 Register new items come from manager
 View and update property in the store
 Sell property for the customer
 Send request to manager
Page | 13
 Generate report to the manager.
2.4 System requirements, specification and analysis modeling (SRS)
The purpose of the software requirements specification document is to maintain all the functions
of the CSMS. Company runs various activities such as purchasing, selling, and manages properly
it. To state some, the problems that are found in this organization are using manual based system
to manage property.
Therefore, we try to develop CSMS for the company, for the purpose of solving the problems and
create opportunity in saving time, reducing human power, keeping the records of information in
properly.
2.5 CRC (class responsibility and collaboration) modeling
Class responsibility collaboration is a collection of standard index cards that have been divided
into three sections. A class represents a collection of similar objects, a responsibility is something
that a class knows or does, and a collaborator is another class that a class interacts with to fulfill
its responsibilities.[6]
In this system there is class. Class responsibility collaboration diagram (CRC) shows the classes
of the system, their inter-relationships, and the operations and attributes of the classes.
There are three types of classes
 Actor classes– actors that appear in use case.
 Business classes– places, things, concepts, and events that describe what the business is all
about
 UI classes– screens, menus, and reports
CRC for actor class
These are admin, manager, store keeper and customer.
Page | 14
CRC for actor class
Figure 2.0.1class responsibility collaboration diagrams (actor class)
Page | 15
CRC for user interface class
Figure2.0.2class responsibility collaboration diagrams (UI class)
Page | 16
CRC for business class
Figure 0.3class responsibility collaboration for business class.
2.6 Use case modeling
A use case is an interaction between users and a system. It captures the goal of the users and the
responsibility the system to its users. It is the functionality of the system or the service provided
by the system.
Itis describe what a system does from the viewpoint of an external observer. The emphasis is on
what a system does rather than how use case diagrams are closely connected to scenarios. A
scenario is an example of what happens when someone interacts with the system. [7]
Page | 17
2.6.1 Essential use case modeling
Figure 2.0.4Essential use case diagram
2.6.1.1 Essential use case description
 Manager
 Administrator
 Customer
 Store keeper
Essential use case descriptions
Use case name: - purchase property
Use case identifier: - euc01
Page | 18
Actor: - manager
Pre-condition: - the admin approve request for manager for purchase property
Post-condition: - fills the form
Description: - enables the approved request
Basic course of action: -
1. The manager fills all necessary input to purchase property
2. The manager submits their inputs
3. The registration is success fully
4. Use case end
Use case name: -register property
Actor: - manager
Pre-condition: - the purchasing is completed
Post-condition: - fills the form
Description: registration can be performed
1. The manager fills registration forms
2. The manager submits their inputs
3. The registration is success fully
4. Use case end
Use case name: - advertisement
Actor: - manager
Page | 19
Pre-condition: - the admin must approve request come from customer
Post-condition: - fill necessary form to post purchasing information
Description: the posted news is viewed by customers
1. The manager fills advertisement forms
2. The manager submits their forms
3. The post is success fully
4. Viewed by customer
5. Use case end
Use case name: - approve advertisement
Actor: - admin
Pre-condition: - view request come from store keeper.
Post-condition: - depends on request approve request
Description: the store keeper sends the request then the admin approve request.
1. Admin views the request form which sent from store keeper.
2. Approve request.
3. Use case end.
Page | 20
Use case name: - customer registration
Actor: - customer
Pre-condition: - open the registration form page
Post-condition: - register their information
Description: - register for selling property
1. Register for selling property
2. Registration is successfully
3. Use case end.
Use case name: - send property request
Actor: - store keeper
Pre-condition: - fill request form
Post-condition: - send to admin and manager
Description: the store keeper sends request data to manager and admin.
Basic course of action: - 1.

Fill forms
2. Send request
3. Use case end
Use case name: - generate report
Actor: - store keeper
Pre-condition: - fill report form
Post-condition: - send to report manager
Page | 21
Description: the store keeper sends report data to manager.
Basic course of action: - 1.

Fill forms
2. Send report
3. Use case end.
2.6.2 System use case

diagram
Page | 22
Figure 2.0.5system use case diagram
2.6.1 System use case description
Use case name Login

Identifier Suc1
Actor Manager, admin, store keeper and customers
Description It allows users to login into the system.
Pre – condition The users should have registered into the system
Basic course of action 1. The users want enters into the system
2. The system displays home page
3. The users click on login link
4. The system displays login form
5. The users enters the username and password
6. The system verifies whether the user is valid or not

according BR #1
7. The system display homepage
8. The use case end
Page | 23
Alternative course of action Alternative action of A: if the password and username
Incorrect.
A5: The username or password entered is incorrect. A6:
The system determines the entered information is
incorrect.
A7: The system informs the user the entered information is
incorrect.
A8: The system prompts to re-enter the information.
A9: Use case resumes at step 3

Post condition The user will login in to the system and able to access the
required home page.
Table 2.6.1login use case description
Use case name Manage account

Identifier Suc2
Actor Admin
Description The admin manage the account of all user
Pre-condition Admin of the system open page
Page | 24
Basic course of action 9. The admin enters into the system
11. The admin click on login link
13. The admin enters the username and password
14. The system verifies user name and password
15. The system displays admin page
16. The admin selects manage property link
18. The admin add, update , active or deactivate and view

the account
19. The use case ends

Alternative course of action Alternative course A5: the admin enters incorrect
username or password
A6: The system determines the admin enters incorrect
username and password.
A7: The system displays failure message
A8: The system returns to step 4
A9: The use case end

Post condition The user account is stored in the database and retrieve
from database
Table 2.6.2 manage account use case diagram description
Page | 25
Use case name Manage request
Identifier Suc3
Actor Admin
Description The admin approve/reject request for store keeper and customer.
Pre-condition The store keeper and customer send request.
Basic course of action 1. The admin enter into the system
2. The system displays the home page.
3. The admin select login link
5. The admin enters correct username and password
7. The system displays admin main screen
8. The admin view approve/disapprove page
9. The admin approve/disapprove request
10. The system sends username and password by email to

store keeper and customer
11. Use case end
Alternative course of Alternate course A5: the admin enters incorrect username or
action password
A6: The system determines the admin enters incorrect username
and password.
A7: The system displays failure message to the department
A9: The system returns to step 4. And use case ends
Alternative course B10: there is no new admin to display
B12: The system determines that no one apply
B13: The system displays appropriate message to the
Page | 26
department and use case end
Post condition The store keeper and customer information will be modified
successfully
Table 2.6.3 manage request use case description
Use case name View report
Identifier Su4
Actor Manager
Description Manger views the report
Pre-condition The report should be submitted in database

Basic course of action 1. The manager want enters into the system
3. The manager click on log in button
5. The manager enters the username and password
6. The system verifies username and password according to

br#03
7. The system displays manager page
8. The selects report view link
9. The system displays report
10. The manager download report
Page | 27
Alternative course of Alternative course A5: the manager enters incorrect username
action or password
A6: The system determines the manager enters incorrect
A7: The system displays failure message A8:
The system returns to step 4.
A9: The use case ends
Post condition The report is viewed by the manager
Table 2.6.4 view report use case description
Use case name Advertisement property
Identifier Su5
Page | 28
Actor Manager
Description The responsible person used to perform advertisement
Pre-condition The manager identify purchased and sell property

Basic course of action 1. The manager enters into the system
3. The manager click on login button
5. The manager enters the username and password into log in

form
7. the system displays manager page
8. The responsible person post advertisement and submits it
9. The system validates the information
10. The manager store advertisement into database and post it

Alternative course of Alternative course A5: the manager enters incorrect username or
action password
A6: The system determines the manager enters incorrect

A7: The system displays failure message to manager
Page | 29
Post condition The advertisement is posted
Table 2.6.5 advertising property use case description
Use case name View request
Identifier Su6
Actor Admin and manager
Description Admin and manager want to view the request
Pre-condition The store keeper and customer send request

Basic course of action 1. The admin and manager enters into the system
3. The admin and manager click on the login button
5. The admin and manager enters the username and password
6. The system verifies username and password
7. The system displays admin or manager page
8. The admin and manager select link for view request

9. The system displays request
10. The admin or manager view request
Page | 30
Alternative course of Alternative course A5: the enters incorrect username or
action password
A6: The system identify the admin and manager enters
incorrect username and password
A7: The system displays failure message to the admin and
manager
Alternative course B10: there is no request displayed
B11: The system determines that no one apply
B12: The use case end

Post condition The request is viewed by the admin or manager
Table 2.6.6 View request use case description
Use case name Property manage
Identifier Su7
Actor Store keeper
Description Store keeper manages property
Pre-condition The manager add the property into storage

Basic course of action 1. The store keeper enters into the system
3. The store keeper click on login button
Page | 31
5. The store keeper enters the username and password into log
in form
7. The system displays store keeper page
8. The storekeeper selects manage property link
9. The system displays manage property page
10. The store keeper add, update , sell and view the property
11. The use case ends.

Alternative course of Alternative course A5: the store keeper enters incorrect
action username or password
A6: The system determines the store keeper enters incorrect
A7: The system displays failure message A8:

The system returns to step 4.
Post condition Property properly managed
Table 2.6.7 property manage use case description
Use case name Purchase property
System use case number Su8
Page | 32
Actor Manager
Description The manager purchase property add property to store database
Pre-condition The manager must login successfully

Basic course of action 1. The manager want enter into the system
2. The system displays the manager page
3. The manger clicks the purchase property buttons.
4. The system displays the purchase property buttons
5. The manager fill needed information
6. The system checks the existence of the entered data.
7. The system display success full message
8. Use case end

Alternative course of Alternative course A: manager enters invalid account A.2:
action If the manager does not have a valid account.
A.3. The system displays error message.
A.4. Use case continues with step 1.

Post condition Posting information for customer
Table 2.6.8 purchase property use case description
Use case name Generate report
Identifier Su9
Actor Store keeper
Description The store keeper used to generate report about the task performed
in the storage
Pre-condition Task assigned to store keeper
Page | 33
Basic course of action 1. the store keeper enters into the system
3. The store keeper click on login link

5. The store keeper enter the username and password
6. The system verifies username and password according to

br#04
7. the system displays store keeper page
8. The store keeper perform a given task assigned
9. The system generate the report

Alternative course of Alternative course A5: the store keeper enters incorrect
action username or password
A6: The system determines the store keeper enters incorrect
A7: The system displays failure message to the store keeper
A8: The system returns to step 4.

Post condition The generated report is viewed by the responsible person
Table 2.6.9 generate report use case description
Use case name Update
Page | 34
Identifier Su10
Actor admin
Description Update user account
Pre-condition Account create for user

Basic course of action 1. The admin enters into the system
3. The admin click on login link
5. The admin enters the username and password
8. The admin selects update account link
9. The system displays update account page
10. The admin click on edit link
11. the system display information from database
12. The admin change some parts of come from database
13. The admin click on update button
14. Then successfully update message is displayed
Page | 35
Alternative course of Alternative course A5: the admin enters incorrect username or
action password
A6: The system determines the college enters incorrect
A7: The system displays failure message

Post condition The information on database is update
Table 2.6.10 update account use case description
2.6 User interface prototyping
2.6.2 Traditional user-interface prototyping
Figure 2.0.6Traditional user-interface prototype diagram
Page | 36
2.6.3 User interface flow diagram
Figure 2.0.7 user interface flow diagram
2.7 Supplementary specifications
2.7.1 Business rules
The business rule is a principle or a policy in which the proposed system operates accordingly.
The main business rules or principles of the existing system are:-
Name: - valid users
Identifier: - br#01
Description: -anyone who use the system
Page | 37
Name: - the customer should be registered
Identifier: - br#02
Description: -any customers selling the property have been register to sell the property, to take
property from store.
Identifier: br#03
Description: manager is login to the system with correct user name and password to view report
Identifier: br#04
Description: store keeper must login to the systems with correct user name and password in order
to generate report
2.7.2 Nonfunctional requirement
The following lists of non-functional requirements are expected from our proposed system:
Security: Access to the various subsystems will be protected by a user log in screen that requires
a user name and password
Scalability: The system must be compatible with any environment.
Reusability: Ability of an item that allows it to be used repeatedly unlike a disposable item.
Performance: This system gives service 24 hours per day with maximum response time so, it is
easy to access data from the stored document.
Accuracy: proposed system will be better due to reduction of error. All operation can be done
correctly and it ensures that whatever information is coming from the data base is accurate.
Reliability: The customized store Management System service should not access without
authenticate user.
No Redundancy: In the proposed system can be avoided reputation of data anywhere in the
database.
Availability: All data in the system will be available all the time.
Page | 38
Efficiency: The system must ensure allocation and use of services being requested for the users by
using minimum memory storage, cost, time and human power.
User interface: The user wants the interface to graphical interface to browse easily
2.8 Constraints
Some of the constraints during the development of our project include:
 The time to build our project is not enough to include more functionality to the system. 
Electric power interruption
 Internet connection cannot available always.
 The system operates at most in three languages.
 It’s not suitable for disable person, like blind people.
 It needs some computer skilled person to operate on the system.
Page | 39
CHAPTER THREE
3. Design Document
The purpose of designing document 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. It is based
on understanding of the model the system built on. The objectives of design are to model the
system with high quality. Implementing of high quality system depend on the nature of design
created by the designer. Therefore, if the system is design effectively, it will be easy to make
changes to it. Design of a system is a blueprint for a solution for the system.
3.1 Class Modeling
Class diagram depicts the system’s object structure. They show object classes that the system is
composed of as well as the relationships between those object classes. A class model is comprised
of one or more class diagrams and the supporting specifications that describe model elements
including classes, relationships between classes, and interfaces. [8]
UML class diagram show the classes of the system, their inter-relationships, and the operations
and attributes of the classes. Class diagrams are typically used, although not all at once, to:
 Explore domain concepts in the form of a domain model
 Analyze requirements in the form of a conceptual/analysis model
 Depict the detailed design of object-oriented or object-based software
Page | 40
Figure 3.1 class modeling diagram
Page | 41
3.1.1 Classes-type layered approach
Class type architecture provides a strategy for layering the classes of the system to distribute the
functionality of the software among classes. Furthermore, class type architectures provide
guidance as to what other types of classes a given type of class will interact with, and how that
interaction will occur. This increases the extensibility, maintainability, and portability of the
systems.
Figure 3.2 class type layered approach diagram
Page | 42
3.2 Sequence diagram
The sequence diagram models the collaboration of objects based on a time sequence. It shows
how the objects interact with others in a particular scenario of a use case. With the advanced visual
modeling capability, you can create complex sequence diagram in few clicks. Besides, visual
paradigm can generate sequence diagram from the flow of events which you have defined in the
use case description. It also shows how processes operate with one another and in what order it
shows how the other in particular scenario of use case. Sequence diagram show as a parallel
vertical line (life line) different process objects that live simultaneously and horizontal arrows
the message exchange between them in the order in which they occur[9].
Figure 3.3sequence diagram for login
Page | 43
Figure 3.4sequence diagram for update account
Figure 3.5sequence diagram for manage property
Page | 44
Figure 3.6sequence diagram for create account
Page | 45
Figure 3.7sequence diagram for purchase property
Page | 46
Figure 3.8sequence diagram for send request
3.3 Activity diagram
Activity diagram is another important diagram in UML to describe dynamic aspects of the system.
Activity diagram is basically a flow chart to represent the flow form one activity to another activity.
The activity can be described as an operation of the system. So the control flow is drawn from one
operation to another. This flow can be sequential, branched or concurrent. Activity diagrams deals
with all type of flow control by using different elements like fork, join etc.[10]
Purpose:
Page | 47
The basic purposes of activity diagrams are similar to other diagrams. It captures the dynamic
behavior of the system. Other four diagrams are used to show the message flow from one object
to another but activity diagram is used to show message flow from one activity to another.
Activity is a particular operation of the system. Activity diagrams are not only used for visualizing
dynamic nature of a system but they are also used to construct the executable system by using
forward and reverse engineering techniques. The only missing thing in activity diagram is the
message part. It does not show any message flow from one activity to another. Activity diagram is
some time considered as the flow chart. Although the diagrams looks like a flow chart but it is not.
It shows different flow like parallel, branched, concurrent and single.
Figure 3.9 login activity diagram
Page | 48
Figure 3.10 search account activity diagram
Page | 49
Figure 3.11 manage property activity diagram
Page | 50
Figure 3.12 search property activity diagram
Page | 51
3.4 User Interface Design
3.4.1 Form design

Login form
Figure 3.13 login form
Page | 52
Customer registration form
Figure 3.14 Customer registration form
3.4.2 Dialogue and Interface Design
Error dialogue
Figure 3.15 Error dialogue
Page | 53
3.4 State chart diagram
State diagrams show the sequences of states an object goes through during its life cycle in response
to stimuli, together with its responses and actions; an abstraction of all possible behaviors.
They define different states of an object during its lifetime. And these states are changed by events.
So the state chart diagrams are useful to model reactive systems. Reactive systems can be defined
as a system that responds to external or internal events. State chart diagram describes the flow of
control from one state to another state. States are defined as a condition in which an object exists
and it changes when some event is triggered. So the most important purpose of state chart diagram
is to model life time of an object from creation to termination. State chart diagrams are also used
for forward and reverse engineering of a system. But the main purpose is to model reactive system.
[11]
Figure 3.16State chart diagram for login
Page | 54
Figure 3.17State chart diagram for Update account
Page | 55
Figure 3.18 State chart diagram for searching property
3.5 Object diagram
Object diagrams are also closely linked to class diagrams. Just as an object is an instance of a class,
an object diagram could be viewed as an instance of a class diagram. Object diagrams describe the
static structure of a system at a particular time and they are used to test the accuracy of class
diagrams. The purpose of a diagram should be understood clearly to implement it practically. The
purposes of object diagrams are similar to class diagrams.[12]
Page | 56
Figure 3.19 Object diagram
3.6 Persistence modeling/database design
Persistence models are used to communicate the design of database, usually relational database,
with the user and other developers. This is basically the entity relation in database application. In
our system, we represent our persistent class (class permanently stored in persistent stores) as
business classes.[13]
Persistent modeling is used to depict the design of the database. The team is going to use the
relational database since it is the most used data base system recently. The persistent classes are
Page | 57
used to store most important and permanent information of the system. In persistent modeling we
will perform the following activities.
Page | 58
Table 3.6.1 Persistence Modeling
Normalized physical database model 1st

normalized form
Account
Table 3.6.2 account normalization
Request
Table 3.6.3Request normalization
Advertisement
Page | 59
Table 3.6.4 admin normalization
Property
Table 3.6.5 storage property
Feedback
Table 3.6.6Feedback normalization
Staff
Table 3.6.7 Staff normalization
Customer
Page | 60
Table 3.6.8 Customer normalization
Second Normal form (2NF)
Second normal form (2NF) an entity type is in 2NF when it is in 1NF and when all of its non-key
attributes are fully dependent on its primary key.
Table 3.6.9 request 2nd normal
Page | 61
Table 3.6.10 property 2nd normalization
Table 3.6.11 advertisement 2nd normalization
Page | 62
Table 3.6.12 Customer 2nd normalization
Table 3.6.13 Feedback 2nd normalization
Page | 63
Table 3.6.14 Staff 2nd normalization
3.20Normalization diagram
Page | 64
Figure 3.4.2Database modeling diagram
3.7 Component diagram
Component diagram show how components are wired together to form larger components and or
software system they are used to illustrate the structure of arbitrarily complex systems. It does not
describe the functionality of the system but it describes the components used to make those
functionalities.[14]
Page | 65
Figure 3.4.2Component diagram
Page | 66
3.8Deployment diagram
It describes the physical architecture of the hardware and software in the system. They depict the
software components, processors, and devices that make up the system’s architecture.
A deployment modeling depicts a static view of the run-time configuration of processing nodes
and components that run on those nodes.[15]
Figure 3.4.2. Deployment diagram
Page | 67
CHAPTER FOUR
4. Implementation Document
4.1 Report on Implementation
In the implementation phase all the programs are written, database is created, user operational document is
written, users are trained, and the system tested with operational data. The implementation is carried out
with the results that have been obtained from the feasibility study and analysis. The system is implemented
by finishing the project with the help of appropriate tools that been suggested and are loaded in to the
server. Then the system is tested with appropriate data inputs to check the successfulness of the system.
This being carried out by inputting data that are of rare to be inputted. Then the administrator will be
trained of the operational functionalities to control and maintain system at a later stage.
The objective or goal of the implementation phase is to construct (describe) all what have been designed in
the previous development phase (i.e. Design phase). Specifically, it is to implement the system by PHP and
Bootstrap. The system contains many pages and user interfaces. These pages are combined in one server to
be a system as a whole. Generally, the objective of this phase is to demonstrate how the system or website
works.
4.2 Implementation plan
The first phase in the implementation of a system is the plan to make it implement. For proper
implementation the plan is a pre-requisite and is known as pre-implementation activity. It is in these steps
that various activities which are required for implementing a system are identified and their sequence and
relation to each other is desired. In this step various other estimates like time required for each activity and
cost estimates are also obtained. For the better description of the plan and implementation various tools like
Gantt charts and pert chart have been used.
4.3System modules
The project is divided into four modules namely,
 Administrator Module
 Manager Module
 Storekeeper Module
Page | 68
 Customer module
Administrator Module
The administrator in our context admin is the one who manage the customized store management
system is responsible for maintaining the database. Who is responsible for approve registration and request.
He has the authority to store and manipulate data. He inserts user information into the database, updates
existing data, remove unwanted data and view all data. He can create a manager, storekeeper and customer
account. And also have power to add new user accordingly.
Manager Module
Manager module add purchased property to database, post advertisement, and manage property
information and view request and other information.
Storekeeper Module
A sell property.
Update the property information.
Send request to the manager.
Customer module
There are two types of customer internal and external customer. Internal customer is the employee or staff
in the company. External customer is the customers viewing the advertisement and register for purchase and
sell the property from company.
4.4TESTING
Testing is the process of evaluating a system or its component(s) with the intent to find whether it satisfies
the specified requirements or not. Testing is executing a system in order to identify any gaps, errors, or
missing requirements in contrary to the actual requirements.
The objective of the proposed system is to provide for the organization a new system that provides
all the functionalities specified by the organization that is more users friendly, less complex and save time
than the existing system.
Page | 69
Testing procedures
Before directly deploying this system, the team will perform different testing for its functionality and
meeting customers need. First the team tests each unit at each phase. So, if a problem is encountered it will
immediately have fixed. Then the team will perform an integration testing to check whether the system
meets all the functional requirements. System will be tested using the following system testing procedures
4.4.1 Unit testing
Every module of the System is separately tested. I.e. the team tests every module by applying some selection
mechanism. Through this mechanism every modules gets tested. If an error occurs correction will be taken
without affecting another module. We have tried to test UI screens of our system that needs to verify screen
elements that appears on the screen.
4.4.2 Integrated testing
In this testing part, all the modules will be combined together and tested it for its fitness with each other and
with the systems functionality. If error occurs in combining them, the module with problem will be identified
and recombined. Both units testing and integrated testing are performed by all team members at the work
place.
4.4.3 System Testing
Here we compile the whole system stating from initial and proceed testing the whole system to
checkout for the errors and flow control of the system.
4.5 Hardware and Software acquisitions
For the project implementation we used the following Software and hardware is used.
Hardware
 Server: for connection to the client computer (to host the system)
 Computers
 Network connection(cables)
 Printer to print soft copy
Page | 70
Software
For the System implementation the following software’s are used.
 MySQL and PHP

 Office word 2016
 Test Mail server
 Notepad++
4.5 Sample Code of the system

Sample code for home page
<?php
include "define_lang.php";
include "connection.php";
//session_start();
?>
<!DOCTYPE html>
Page | 71
<html lang="en">
<head>
<meta charset="utf-8">
<title>Customized store management system</title>
<meta content="width=device-width, initial-scale=1.0" name="viewport">
<meta content="" name="keywords">
<meta content="" name="description">

<link href="img/favicon.png" rel="icon">
<link href="img/apple-touch-icon.png" rel="apple-touch-icon">
<link href="lib/bootstrap/css/bootstrap.min.css" rel="stylesheet">

<link href="lib/font-awesome/css/font-awesome.min.css" rel="stylesheet">
<link href="lib/animate/animate.min.css" rel="stylesheet">
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.3.1/css/bootstrap.min.css"

integrity="sha384-
ggOyR0iXCbMQv3Xipma34MD+dH/1fQ784/j6cY/iJTQUOhcWr7x9JvoRxT2MZw1T"
crossorigin="anonymous">
<link href="css/style.css" rel="stylesheet">
<link href="staff.css" rel="stylesheet">

</head>
<body id="page-top">
<header id="header">
<div class="container">
<div class="row">
<div class="col-md-2 col-md-push-3">
<div id="logo" class="pull-left">
<a href="#hero"><img src="img/HU LOGO.png" width=100 height=50 alt="" title="" /></img></a>
</div>
</div>
<div class="col-md-9 col-md-push-3">
<nav id="nav-menu-container">
<ul class="nav-menu">
<li class="nav-item">
<a class="nav-link js-scroll-trigger" href="#hero"><h6><?php echo lhome; ?></h6></a></li>
<a class="nav-link js-scroll-trigger" href="#about"><h6><?php echo laboutus; ?></h6></a></li>
Page | 73
<a class="nav-link js-scroll-trigger" href="#team"><h6><?php echo ldeveloper; ?></h6></a>
</li>
<a class="nav-link js-scroll-trigger" href="#facts"><h6>Advertisement</h6></a></li>
<li class="menu-has-children"><a href=""><h6>Language</h6></a>
<ul>
<li><a href="switch_lang.php?lang=1">English</a></li>
<li><a href="switch_lang.php?lang=3">Amharic</a></li>
<li><a href="switch_lang.php?lang=2">Afaan Oromoo</a></li>
<ul class="navbar-nav text-uppercase ml-auto">
</ul>
</ul>
</li>
<li class="nav-
item">             <button
type="button" class="btn btn-primary" style="width: 90px; height: 33px;" data-toggle="modal" data-
target="#myModal">Log In</button></li>
</ul>
</nav>
Page | 74
</div>
</div>
</div>
</header>
<div align="center"> 
<div class="hero-container">
<h1>Haramaya university <h1>
<h1>Customized Store management System</h1>
<a href="#about" class="btn-get-started">welcome</a>
</div>
</section>
<script type="text/javascript">
var username = document.forms["vform"]["username"];
var password = document.forms["vform"]["password"];
var uname_error = document.getElementById("uname_error");
var pass_error = document.getElementById("pass_error");
var letters = /^[A-Za-z]+$/;
var numbers = /^[0-9]+$/;
var emails = /^([a-zA-Z0-9_\.\-])+\@(([a-zA-Z0-9\-])+\.)+([a-zA-Z0-9]{2,4})+$/;
var phonenos = /^\d{10}$/;
Page | 75
username.addEventListener("blur", unameVerify, true);
password.addEventListener("blur", passVerify, true);
function passVerify(){
if (password.value != "") {
password.style.border = "1px solid #5E6E66";
pass_error.innerHTML = "";
return true;
</script>
Sample code for login


<div id="myModal" class="modal fade" role="dialog">
<div class="modal-dialog">


<br><br><br><br><br><br><br><br><br><br><br>
<div class="modal-content">
<div class="id">
<form method="POST" action="" enctype="multipart/form-data" onsubmit="return Validate()"
name="vform">
<div>
<input type="text" name="username" class="textInput" placeholder="Enter username" class="form-
control">
<div id="uname_error" class="val_error"></div>
Page | 76
</div>
<div>
<input type="Password" name="password" class="textInput" placeholder=" Enter password" class="form-
control">
<div id="pass_error" class="val_error"></div>
</div>
<div align="left">
<input type="submit" name="submit" value="Log in" class="btn">

<input type="reset" name="submit" value="cancel" class="btn">
</div>
<p align="left"> Not yet a member?   <a href="registration.php">Create new
Account</a></p>
<p align="left">
<a href="forget.php"> Forget Password?</a>
</p>
</div>
</div>
</form>
</div>
</div>
</div>
<?php
if(isset($_POST["submit"])){
$username=$_POST["username"];
$password=md5($_POST["password"]);
//$user_type=$_POST["user_type"];
$sql=mysqli_query($con,"SELECT username,password,user_type,status FROM account");
//$sql=mysqli_query($con, "select * from user_table where username='$username' &&
password='$password'");
while ($row=mysqli_fetch_array($sql)) {
Page | 77
$db_username=$row["username"];
$db_password= md5($row["password"]);
$db_type=$row["user_type"];
$db_status=$row["status"];
if ($username==$db_username && md5($row["password"]) ==$db_password) {
$_SESSION["username"]=$db_username;
$_SESSION["user_type"]=$db_type;
$_SESSION["status"]=$db_status;
if ($_SESSION["user_type"]=='Admin' && $_SESSION["status"]=='Active') {

?>
window.location="Admin/index.php";
</script>
<?php
}
elseif ($_SESSION["user_type"]=='Manager' && $_SESSION["status"]=='Active') {

?>
window.location="Manager/Dashboard.php";
</script>
<?php
}
if($_SESSION["status"] == 'Deactive'){
?>
<script type="text/javascript">alert(" Your Account is Deactive")</script>
Page | 78
<?php
}
elseif ($_SESSION["user_type"]=='Customer' && $_SESSION["status"]=='Active') {

?>
window.location="Customer/index3.php";
</script>
<?php
}
elseif ($_SESSION["user_type"]=='DKeeper' && $_SESSION["status"]=='Active') {

?>
window.location="DKeeper/index2.php";
</script>
<?php
}
elseif ($_SESSION["user_type"]=='ELECKepper' && $_SESSION["status"]=='Active') {

?>
window.location="ELECKepper/index2.php";
</script>
<?php
}
elseif ($_SESSION["user_type"]=='BKeeper' && $_SESSION["status"]=='Active') {

?>
window.location="BKeeper/index1.php";
Page | 79
</script>
<?php
}
else
{
?>
window.location="Home.php";
</script>
<?php
}
$_SESSION["username"]=$_POST["username"];
//$_SESSION["user_type"]=$_POST["user_type"];
//$_SESSION["user_id"]=$_POST["user_id"];
$_SESSION["password"]=$_POST["password"];
}
}
}
?>
<section id="hero">
<div class="hero-container">
<h1>Haramaya university <h1>
<h1>Customized Store management System</h1>
<a href="#about" class="btn-get-started">welcome</a>
</div>
</section>
Sample code for add new book
<div id="addbook" tabindex="-1" aria-labelledby="mymodalLabel" class="modal fade" role="dialog">
Page | 80
<div class="modal-dialog" >

<div class="modal-content">
<form action="" method="post" class="form-responsive" enctype="multipart/form-data"
onsubmit="return Validate()" name="vform">
<div class="modal-header" style="background-color:#DCDCDC; color: black;">
<h3 align="center" style="image-rendering: circle;">

<?php
$sql= "select image from account where username='$_SESSION[username]'";
$result=$con->query($sql);
if($result->num_rows>0){
while($row=$result->fetch_assoc()){
$image =$row['image'];
//$user_type = $row['user_type'];
echo "<img src='$image' height='60' width='60' align-center'";
}
}
?>
</h3>
<h3 align="center"><font size="2"> Add New Books:</font></h3>
</div>
<label class="control-label col-sm-3" for="booktype">Product Type:</label>
<div>
<select name="booktype" class="form-control" style="border-radius: 4px;">
<option></option>
<option>C#</option>
<option>C++</option>
<option></option>
<div id="ptype_error" class="val_error"></div>
Page | 81
</select>
</div>
4.6 User manual
User manual express how user use the system
A) User login page
Page | 82
b) User manual registration form
c) User manual admin page
Page | 83
C) New book registration form
Report of the property
Page | 84
4.7 Clients Feedback
By testing the system by user we get good feedback. Some of the comments are:
 Since many activities are automated many problems of individual and organizations are solved.
These are resources such as Cost, Man power and Time
 The system is very attractive, because it reduces man power, cost and time for employees and
company.
 Since the system needs some knowledge about the system there must be some training for the users
of the system in the future
 They never loss document of property easily
Those are the comments we get from clients for example; advisor and classmates by showing the system for
them. So, we recommend, the system should be entitled to the responsible and skilled person (i.e. system
users and administrators). We highly recommend the system should be kept in highly safe and favorable
condition.
Page | 85
4.8 Conclusion
We have already developed a website or web-based application for Customized store management system.
This website has been titled as customized store management System. It provides much functionality for its
users. For example, it enables online advertisement, send request online and it also enables the administrator
to manage events and property record on the system.
As project come up to the end. We pass all software development life cycles. Start from system specification
up to system testing and at each stage system development we understand clearly what to be done and what
need to be done each tasks. For example, in analysis, we tried to model the new and proposed system using
UML diagrams: - use case diagrams, sequence diagrams, class diagrams and Activity Diagram. And from
this we understand how to model the system.
Finally, we concluded our project have some best features that makes customer/user satisfied by our system
and take this features as our strength and some features that makes our customer little satisfaction as our
weakness.
Page | 86
4.9 Recommendation
In recommendation on our project we recommend that: -
 Since our project is effective and efficiency in saving resources we recommended that this project is
only for Haramaya University it must developed for other university.
 We recommended Haramaya university to apply our system starting from 2020 because it save time
 We also recommended this system have some limitation this occur because of lack of time so we
strictly recommended that the teaching and learning process must have changed because insufficient
of time so to do such type project must have taken one year.
 Adjust things to test the developed the project in the right manner.
 Budget should be allocated to take specific measure.
 To change the obsolete hardware instrument by the new one.
Page | 87
Reference
[1] S. A. RAJIB, Store management system, East West University:

http://dspace.ewubd.edu/bitstream/handle, Feb,2013.
[2] About HU, Haramaya, 2008.
[3] M.A. Jackson, System development methodology, Hamilton Terrace, London:

http://mcs.open.ac.uk/mj665, 2015.
[4] Easterbrook, the Feasibility Study, university of Toronto:

http://www.cs.toronto.edu/~sme/CSC340F/2005/slides/, 2016.
[5] C. R. Neal Hunt, FUNCTIONAL and TECHNICAL, University of Washington:

https://sites.nationalacademies.org/cs/groups/pgasite, June,2016.
[6] D. M. Rubin, Introduction to CRC Cards, London:

http://lore.ua.ac.be/Teaching/SE3BAC/CRCIntro, July,2016.
[7] Cockburn, Writing Effective Use Cases, Addison-Wesley:

https://www.win.tue.nl/~jschmalt/teaching/, sep. 2001.
[8] B. j. Scott Hendrickson, Layered Class Diagrams, Irvine, California: {shendric, bjett,
andre}@uci.edu , 2010.
[9] E. Torlak, Software Engineering, courses.cs.washington.edu/courses/cse403/15sp/, Spring

2015.
[10] M. Felici, Activity Diagrams, inf.ed.ac.uk/teaching/.../, 2009.
[11] S. T. R. A. P. L. Stephen Mellor, Softwareplatform-independent, Precise Action Specifications

for UML, Mulhouse, France:
omg.org/news/meetings/workshops/presentations/eai_2001/tutorial_monday/, June,2013.
Page | 88
[12] J. O. R. Shahar Maoz, Model objects diagram, RWTH Aachen University, Germany:
tau.ac.il/~maozs/papers/, 2015.
[13] T. J. Teorey, Database Modeling and Design, University of Michigan:

https://web.eecs.umich.edu, 2016.
[14] M. Felici, Component Diagrams, http://www.inf.ed.ac.uk/teaching/courses/, 2011.
[15] Louisiana, Deployment Diagram, Tech University: http://www2.latech.edu/~box, July,2009.
[16] Material management, free template, 2008.
[17] M. Felici, Collaboration Diagrams, Room 1402, JCMB, KB:

inf.ed.ac.uk/teaching/courses/seoc/2004_2005/, 2016.
Page | 89

Final Project Document2

Uploaded by

Final Project Document2

Uploaded by

HARAMAYA UNIVERSITY

COLLEGE OF COMPUTING AND INFORMATICS

DEPARTMENT OF INFORMATION SYSTEM

Project Title: CUSTOMIZED STORE MANAGEMENT SYSTEM FOR HARAMAYA

1. Anawar Sharif (580/08)

2. Habtamu Dulo (611/08)

3. Haftom Kidanu (612/08)

4. Eyerus Manaye (598/08)

Project adviser: - Ms.Atakilt.N

1. Anawar Sharif ( 580/08)

2. Habtamu Dulo ( 611/08)

3. Haftom Kidanu ( 612/08)

4. Eyerus Manaye (598/08)

Adviser by: Co-adviser by:

1. Anawar Sharif ( 580/08)

2. Habtamu Dulo ( 611/08)

3. Haftom Kidanu ( 612/08)

4. Eyerus Manaye ( 598/08)

Approved & adviser/ co adviser by:

Submitted to:Mr.Ataklt.N and Ms.Woynishet.B

Use case Diagram symbol

Actor use case Boundary link

Sequence Diagram symbol

Activation message Message return

Activity Diagram Symbol

Action state Initial state final state control flow

Class Diagram symbol

Deployment Diagram symbol

Component node instance constraint communication

CSMS: Customized store management system

HU: Haramaya University

US: Use Case

OOSAD: object oriented system analysis and design

MYSQL: structure query language

PHP: Hyper Text Processing

HTML: Hyper Text Mark-up Language

UI: User Interface

1NF: First Normal Form

2NF: Second Normal Form

3NF: Third Normal Form

UML: Unified Model Language

Figure 2.1 class responsibility collaboration diagrams (actor class) 14

1.1 BACKGROUND OF COMPANY

1.2 STATEMENT OF PROBLEM

Furthermore, there is.

 Time delay in generating reports.

 Send request could be apply manual.

 The advertisement could be done manual.

 It should increase updating complexity.

 Data were registered or recorded on excel and word

1.3.1 General objectives

1.3.2 Specific objective

 Request items is does online.

 Import and export data from excel to inventory.

 Enable the system user register online in very secret

 Enables the storage workers to record data effectively and efficiently

 It enables to give reliable search facility

1.4 METHODOLOGY OF PROJECT

 Secondary data collection

Primary data collection

Secondary data collection

The HU procurement directive and store management document

1.4.2 System development and methods

1.5 Scope and limitation

1.5.1 Scope of the project

Major scope of the project:-

 It store for book, medical, electrical material and clothes

 Inventory management for store

 Complete purchase process reports should be in case of any store

1.5.2 Significance of project

The relevance why we had conducted the project was:

 Understand how Store management system works. And to design an appropriate

 Updates relevant information

 Easy to manipulate and maintain the system.

 Easy to generate reports.

1.5.3 Limitation of the project