.

Ambo university
Institute of Technology
Department of Computer Science
Course: Software Project Management
Title: Localization of Open Source Inventory Management System for OPC
(Oromia Police Commission)

Name: Fekadu Abdisa …………………….ID: MET/209/12

Instructor : Dr. Kuulaa

09/26/2020 1
 Chapter One
Introduction
• Currently Oromia Police Commission use manual
type of inventory management, the organization
process tasks in the form of document-based
applications.

• We are trying to implement the system which can

solve the problems in manual inventory management
system. This will minimize labour force and the time
required

2
 Project overview
• This project is to create Online Inventory management
System. It is an online application where user can view and
manage items in the store without going to the store
manually.
• The application involves user registration, login, viewing
items, managing items, generate different kinds of report,
transaction history and user account management
activities.

• The entire system has to be developed using PHP

language, JavaScript, HTML and MySQL Database server.
3
 Objectives
General Objective

The objective of the project is to develop a web-based Inventory

Management system through the design and development of modern
management Information System.

Specific Objectives : The Specific Objectives of The Projects are to:

 Analyze the current existing system

 Gather requirements and perform requirement analysis
 Provide and design a solution for existing problem.
 Implement  Inventory Management System
 Localize Open source Project to Afaan Oromo Language
 Eliminate data redundancy, lose and inconsistency
 Increase stakeholder’s satisfaction 4
 Scope of the Project

The scope of the project is defined in terms of the tasks that the
system accomplishes. Thus, the scope of the project is limited to:

 Creating Accounts for user of the system

 Authenticating users by use of password.
 Managing Users
 Registering Items
 Add Item to existing Item
 Manage Items
 Generating reports

5
 Project deliverables
 Software Deliverables

 Source code for both the client side, server side and the
Database.
 Document Deliverables

 Project Plan Document

 SRS Document
 Analysis Document
 System Design Document

 Test Plan Document

 Software Quality Assurance Plan

 User’s Manual document 6
Project charter

7
 CHAPTER TWO

Project planning
Project start-up plan

The SPMP outlines the resources and materials needed to start the project and will
include: estimation plan, staffing plan, and training plan.
1. Estimation plan

As soon as the high-level architecture is created and the system is decomposed into
subsystems. the team will prepare a size estimation plan and include it as a part of the
SPMP. Before creating a size estimation plan, the team will have a discussion about the
method that will be used for that purpose.
2. Meeting

The Stakeholders will meet once weekly, on Saturday (3:00pm – 6:00pm). The meeting
will focus on the discussion on what is implemented.

8
 Project Requirements
Functional requirements
Generally the system will provide the following functionalities:
 Users Management

 Register users
 Manage user’s account
 Register Clients
 Manage Clients  Item Release Management

 Item Management  Item Return Management

 Register items  Reports Generation

 Manage items  Item Reports

 Manage item category  Accounts Reports
 Maintain item price  Clients Reports
 Item Release reports
 Item Return Reports

9
Nonfunctional requirements
• Performance
• User Interface
• Security and Access permissions
Software Requirements
 HTML 5
 JavaScript
 MySQL 5
 NotePad++
 Microsoft Visio and Edraw-Max
 Microsoft Office PowerPoint 2016
 Microsoft Office word 2016
 Web browser
Hardware Requirements

 Laptop Intel(R) core i7 Processor, 4GB RAM, 500 GB HD

 Flash disk (8GB)
10
 Project organization
 Process model

Agile methodology is chosen due to it’s adaptability to change, people-oriented,

speedy and responsive are well suited to the software development projects.

 Work Breakdown Structure (WBS)

11
 Roles and Responsibilities
Team Member: Fekadu Abdisa
Project Phase Responsibility Role Team
Leader
Requirements Gather Requirements Engineer  
  Analyze Requirements Engineer  
Specify Requirements Engineer
 
Documentation Requirements Document Requirements Engineer
Project Plan Project Manager, Developers  
 
Test Report Tester Fekadu
User Manual Developers, Requirements Abdisa
Engineer
Implementation Create PHP code Developer

Create Database Developer

Localization to Afaan Developer

Oromoo
Testing Unit Testing Tester
System Testing Tester
Acceptance Testing Tester, Project Manager
Deployment Deploy the system Developer
12
 Time management plan
 Schedule Management
1. Gant chart
The Project will begin on April 01, 2020 and run through the September 25, 2020.

13
2. PERT (Program Evaluation Review Technique) Chart

Identify Requirement Perform System Analysis

001 10days 002 14days

2020/4/1 2020/4/30 2020/5/1 2020/5/20

Fekadu Fekadu

Perform System Design Develop the System

003 17days 004 41days

2020/5/22 2020/6/15 2020/6/19 2020/8/14

Fekadu Fekadu

Perform Unit Testing Perform Integration Testing

005 5days 006 6days

2020/8/20 2020/8/26 2020/8/28 2020/9/4

Fekadu Fekadu

Perform UAT Deploy The System

007 5days 008 5days

2020/9/7 2020/9/11 2020/9/18 2020/9/24

Fekadu Fekadu
14
 3. Critical Path

A network diagram has many paths originating from one point and
ending at another point. Every path has a duration and the one with
the longest duration is the critical path.

15
 Budget and Resources Allocation
The budget and the resources for this project have been summarized as shown below:

Item Quantity Unit price Costs(in Birr)

Desktop computer 2 30,000 60,000

Pen 1 5 5

Flash disk (8GB) 1 300 300

Paper 40 1 40

For printing 50 2 100

Initiation 51,000
Planning 150,000

Executing/Implementing 550,000

Monitoring and controlling 100,000

For others 88,555

Total price 1,000,000 Birr

16
 Risk management plan
Risk Management is the systematic process of identifying,
analyzing, and responding to project risks. A risk management
plan defines how a project team will handle risks to achieve that
goal.

What is a Risk Management Plan?

The Risk Management Plan is used to summarize the proposed

risk management approach for the project. Usually it is included
as a section in the Project Business Plan, however for larger or
more complex projects it can be maintained as a separate
document. It is dependent on the establishment of a Risk Register.

17
 Risk Identification
This section mentions any potential risks for the project:

18
 Risk Control

To control risks in every stage of the project the team member

uses the following methods:
New Risk Identification: all the team member can identify
additional risks and notify to the team of the new risk (or
possible risk) via e-mail, phone and through formal meeting
Audits: each member of the team will be responsible for
overseeing risk activities and ensuring the risk register is
updated.
Review: each member of project team will review the project’s
risks weekly (in every weekly team meeting).
19
 Monitoring
The monitoring of progress is done by the PM using the following
means:

 Development technology analysis, standard, identifying

types of technology with hardware and software and with the
company need and future plan of company.
 Training, policy, Weekly project status meetings 
 Creating Awareness, planning
 Identify methodology, what kind of development
methodology should be selected to fulfil company’s need.
 Shared document repository
20
 n k
h a
T u
Y o
09/26/2020 16