FIXED ASSET MANAGEMENT SYSTEM

INTRODUCTION

 When we talk about fixed assets, we're talking about

material possessions that belong to the institution and
aren't meant for sale or use right away.
. With the help of QR codes, users can make their
operations automatic.
 Vehicles, computers, furniture, and tools are examples
of fixed assets.
 The value of an organization's fixed assets represents
fairly a considerable proportion of its total value.
 Background of the Study
The ability for users to act on the information they receive

has been revolutionized by the use of the Internet and the

World Wide Web.
The MTU can easily access and secure its data by using the

Internet.
In general, our project aims to create a web-based fixed

asset management system for MTU Property Management

Office that registers items, tracks items, and withdraws
items by using QR codes.
 Motivation

Asset tracking and visibility: The system helps

organizations accurately track and monitor their assets,
providing real-time visibility into the location, condition,
and status of each asset.
 Risk mitigation: Effective asset management helps

organizations identify and mitigate risks related to asset

loss, theft, damage, or regulatory non-compliance.
Cost control and optimization: By tracking asset usage,

maintenance, and depreciation, organizations can

optimize asset utilization, reduce maintenance costs, and
make informed decisions about asset replacement or
disposal.
Improved decision-making: The system provides data-

driven insights and analytics that enable organizations to

make informed decisions about asset management
strategies, investments, and resource allocation.
 Statement of Problems
The Property Management Office at MTU currently uses

a manual fixed asset management system that is based on

paper-based procedures with handwritten asset details in
markers.
The university has several difficulties with this manual

method, especially in the fixed asset management office.

Manual labor is used to complete tasks, which reduces
overall efficiency and delays the timely delivery of vital
information.
 Additionally, the risk of data loss from insufficient data

storage techniques is increased when paper-based systems are

used.
 Fixed asset models are manually documented with markers

under the current asset management system, wasting time and

expensive resources in the process.

Through this shift, the university's asset management

departments would experience less difficulty in the short

term due to increased efficiency and data integrity.
 Objectives
General Objective of project
 The general objective of the project is to develop a QR-

based fixed asset management system for the MTU

property management office.

Specific Objective of project

 Track the location and condition of all fixed assets

 Generate reports on fixed assets

 Design the system architecture for the proposed system.

 Scope and Limitation of the Project
Scope of the Project

 The scope of the project is managing the fixed asset in a

simple, effective, and useful manner is the main focus of
the project.
This project mainly focuses on identifying the existing

problem of the MTU fixed management system and

designing an alternative solution for the problem.
The system is targeted at MTU Property Management

Office and does not include any other university's asset

 Limitations of the Project
System limitations are restrictions because of which the

system cannot function:

The project is not capable of distributing assets on its

own.
 Asset distribution needs human intervention and
authorized personnel coordination.
Additionally, our system is unable to focus on internet

asset purchases.
 Methodology
Data Gathering Methodology
Primary data collection method
Observation: To gather relevant information the project

team were observed how the current system works.

Interview: We questioned asset management personnel in

order to obtain information using this strategy.

 Secondary data collection methods
Document analysis: The team working on the project

made an effort to find written records detailing how they

handle project-related assets.

The System Analysis and Approaches

For the system analysis and design approaches for this

project, we used object oriented system analysis & design.

Because:
It provides code and function reuse through the concepts

of inheritance, polymorphism, encapsulation, modularity,

coupling, and cohesion.
Understanding the structure is easy because object-

oriented modeling and tools are used to represent real-

world entities.
 Feasibility study

A feasibility study is a preliminary exploration of a

proposed project or undertaking to determine its merits

and viability.
 A feasibility study aims to provide an independent

assessment that examines all aspects of a proposed

project.
 Technical Feasibility

The system created using a well-known programming

language like PHP, JavaScript, bootstrap, CSS, and a

MySQL database and can function with the hardware and
software of an existing computer system.

Operational Feasibility
The new system is usable, reliable, maintainable,

supportable, and problem-solving from an operational

standpoint.
 Economic Feasibility
Economic Feasibility is a measure of how cost-effective

the proposed solution will be.

To develop the proposed system at a minimum cost at a

lower price.
To identify the economic feasibility of the project the

team has done a cost-benefit analysis which enables it to

specify the benefits and costs associated with the project.
 Significance of the Project

 We used web-based principles and QR codes to design

the system, so all the data of one or more assets would be

accurately and uniformly kept for quick decision-making.
 The administrator is responsible to maintain and manage

the system.
 The administrator interacts with the back-end and front-

end interface programs; the staff can interact from the

front-end interface only to perform the operations.
 Chapter Two
Description of Existing System
The Property Management office is responsible for

managing fixed assets at MTU.

The asset managing activities are performed manually,

such as registering new assets, viewing asset information,

report generation, preparation of user requests, and

distributing the asset to the requested user .

 Players in the existing system
Administration Office: The administrative office
approves the letters of application that staff members
present and send to the facility.
Facility Directorate: The facility directorate will receive

the application letters that workers present and submit

when they are approved by the administration office.
Property Manager: The Property Manager will also

prepare Model 20 for the application (which contains his

or her name and signature, the asset information,
Fixed Asset Store man: Fixed-asset store man writes on
bin cards and registers new assets using Model 19 to keep
track of the inventory.

Staff: Staffs are employees at MTU and are also users of

assets from all colleges and administrative divisions.
They can write an application letter to withdraw money

from the bank or to ask for something to be bought for

their institutions or departments.
Functions / Activities of the existing system.
Asset Inventory Management: The office maintains an

accurate inventory of all fixed assets owned by the

university. This includes recording asset details such as
descriptions, identification numbers, purchase dates,
costs, locations, and any relevant information.
Location Tracking via QR Codes : Implement location

tracking by associating QR codes with specific physical

locations. Users should be able to update asset locations
by scanning QR codes at different sites.
Asset Tracking and Movement: The office tracks the

movement of assets within the university. This includes

recording transfers of assets between departments or
locations, updating the asset register accordingly, and
ensuring that accurate records are maintained for asset
locations and custodians.
Reporting: The office prepares reports and
documentation related to fixed assets as required. This
includes providing regular updates on asset inventory,
depreciation, maintenance activities, and disposal records.
Maintenance and Repairs: The Property Management

Office may coordinate or oversee the maintenance and

repair activities for fixed assets.
Fixed-asset store man registers new assets with model 19

and adds on bin cards, to know how many items are in

stock.
The Store man of fixed assets registers assets while

withdrawing with model 22 and deduct them from the

stock card to determine how many items are left in the
store.
 Business Rules
Business rules of fixed asset management refer to the

guidelines and policies that govern the management of a

company's fixed assets.
Fixed assets include property, equipment, such as
electronics, machinery, vehicles, and furniture, which are
used in the company's operations.
The asset users must be involved in a University.
 Chapter Three
Proposed System Modeling
 The proposed system for QR-based fixed asset management

for MTU Property Management Office involves using QR

codes to track and manage the fixed assets owned by the
university.
 The system will involve attaching QR code labels to each

fixed asset, which will contain unique identifiers that are

linked to a database.
 The database will store information about each asset,

including its location, condition, and other relevant data.

 Proposed System Requirement Specification
 System requirement is the requirements at the system level

that describe the functions which the system as a whole

should fulfill to satisfy the stakeholder needs and
requirements

Functional Requirements
 The system should grant access to the user after he

provides a username and password.

 To get that provide a username and password admin can

The asset user (staff) can prepare the request to withdraw

the asset and prepare a problem report for the

administrative officer, facility director, and property
manager.
The administration officer, facility director, and property

manager approve the request and prepare feedback for the

asset user (staff).
The system should grant to generate reports for the store

man and staff for a property manager.

 Actors and use case identification
Actor Identification
Administration office

Facility director

Property Manager

 Store man

 Staff

Administrator
 Use case identification
Login

Approve the request

Manage account

Prepare feedback

View report

View asset information

Withdraw asset

Generate report
Register asset

Prepare request

Prepare problem report

View feedback

View the problem report

Logout
Use case diagram
 Use Case Description
Use case description explains in detail the general flow of

use case diagrams.

 Each table contains the use case name, the actor that

initiates and interacts with the use case, and the flow of
event that show the interaction between the actor and the
use case which enable the user to easily understand the
functions of the proposed system.
 Nonfunctional Requirements
A non-functional requirement is a statement defining a

system quality, constraint, or external interface.

Responsiveness: The bootstrap mechanism will use to

construct the system To create a system that can adapt the

size of the user's computer screen.
User-friendly: The user interface of the system should be

simple to grasp and allow for easy interaction, allowing

the user to utilize it without much computer program
experience.
Security: The system should only permit registered users,

or those who have previously made accounts using

usernames and passwords, to access it. Whenever they are
entered into the database, the password is also encrypted.
Performance criterion: The system we suggested has a

long access period and a rapid response period. The

system is accessible at any time, supports multiple users
concurrently, and is simple to use.
 Sequence Diagram
A sequence diagram is a type of interaction diagram

because it describes how and in what order a group of

objects works together.
These diagrams are used by software developers and

business professionals to understand requirements for a new

system or to document an existing process.
The team uses a sequence diagram to easily define the

sequence of tasks that are accomplished by the actors of the

system.
 Activity Diagram
An activity diagram visually presents a series of actions or

flow of control in a system similar to a flowchart or a data

flow diagram.
Activity diagrams are often used in business process

modeling .They can also describe the steps in a use case

diagram.
this activity diagram provides a high-level overview of the

main activities involved in the QR-based fixed asset

management system.
 Chapter Four
System Design
Introduction
After gathering information by using different
methodologies the information is transferred from analysis
to the design phase.
 In this phase we describe the general description of the

analysis phase and additionally the internal structure of the

system and hardware configuration.
 Design Goal
User friendly: The system should have an easily

understandable interface (the user can interact with the

system through the user interface easily).
Accuracy: The system gives only valid results if the user

gives the correct input otherwise the system gives an

invalid response if the user gives wrong in the put.
Maintainability: The system is developed using an

object-oriented software development technique that

makes the software highly maintainable.
 Hardware/Software Mapping (Deployment
Diagram)
A deployment diagram is a static view of the run-time

configuration of hardware nodes and the software

components that run on those nodes.
It shows the hardware of the system, the software that is

installed on that hardware.

 Generally, deployment diagrams are used for describing

the hardware components where software components are

deployed.
 Persistence Data Management
Persistent data management describes the persistent data

stored by the system and the data management

infrastructure required for it.
The persistence of our object can be achieved by a

relational database since it is used as a machine to make

the object persistent.
The system will use the MySQL database server for

storing data. This will allow the database to be easily

integrated with and accessed by the rest of the system.
 Class Diagram
Class diagrams can also be used for data modeling. This

class diagram provides a high-level overview of the

classes and their relationships in the QR-based fixed
asset management system.
The class diagram is the main building block of object-

oriented modeling. It is used for general conceptual

modeling of the structure of the application, and for
detailed modeling, translating the models into
programming code.
THANK YOU!!!