CHUKA UNIVERSITY
FACULTY OF SCIENCE, ENGINEERING AND TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE
NAME: ABINCHA K. DESMOND
REG NO: EB3/50202/20
ACSC 483: SOFTWARE PROJECT 1:
PROJECT PROPOSAL FOR
ASSET NEXUS SYSTEM
SUPERVISING LECTURER: MR. SIGAR OTULA
PROJECT PROPOSAL UNDERTAKEN IN PARTIAL FULFILMENT FOR THE
AWARD OF BACHELOR OF SCIENCE IN APPLIED COMPUTER SCIENCE UNDER
THE FACULTY OF SCIENCE ENGINEERING AND TECHNOLOGY.
DECLARATION
I Abincha Desmond declares that this is my original work and has not been
presented anywhere else to the best of my knowledge.
Sign _____________________________________
ACKNOWLEDGEMENT
I would like to dedicate this report to Mr. Charles Kinyua who taught me nearly
everything I know about we design and development using different programming
and scripting languages. I would like to stretch my gratitude to my family for their
continued support and Mr. Sigar Otula for his guidance all through creating of this
document.
ABSTRACT
In today's dynamic organizational landscape, the efficient management of assets
and products is pivotal to streamline operations, maintain accountability, and
optimize resource utilization. The proposed Asset Nexus System (ANS) aims to
bridge the gap between traditional inventory systems and the ever-evolving needs
of contemporary organizations. The ANS will serve as a robust platform to
register, track, and monitor organizational assets, ensuring transparency, accuracy,
and real-time updates.
At its core, the ANS offers a user-friendly interface to register new products and
assets, capturing vital details like acquisition date, cost, lifespan, and technical
specifications. Beyond mere registration, the system prides itself on its monitoring
capabilities. By integrating state-of-the-art tracking mechanisms, the ANS will
keep tabs on the current status of each asset—be it operational, under maintenance,
or retired. This feature aids in preempting potential issues, ensuring assets are well-
maintained and reducing downtimes.
A standout feature of the ANS is its allocation module. Recognizing the
importance of resource allocation in organizational settings, this module allows
managers to assign assets to specific individuals or departments. It not only ensures
accountability but also provides clarity on asset availability, aiding in informed
decision-making. Furthermore, the system is equipped to generate detailed reports,
presenting a holistic view of asset distribution and status within the organization.
Table of Contents
DECLARATION.......................................................................................................................................ii
ACKNOWLEDGEMENT........................................................................................................................iii
ABSTRACT..............................................................................................................................................iv
CHAPTER 1: INTRODUCTION.............................................................................................................1
1.0 Introduction...............................................................................................................................1
1.1 Background of the Study.................................................................................................................1
1.2 Problem Statement..........................................................................................................................1
1.3 Proposed Solution............................................................................................................................2
1.3.1 Objectives......................................................................................................................................2
CHAPTER 2: LITERATURE REVIEW.................................................................................................3
2.0 Introduction.....................................................................................................................................3
2.1 Literature Review............................................................................................................................3
CHAPTER 3: METHODOLOGY............................................................................................................7
3.0 Introduction.....................................................................................................................................7
3.1 The incremental Model...................................................................................................................7
3.1.1 Phases of the incremental model..................................................................................................7
3.2 Computer Programming Language to be used.............................................................................8
3.3 Database System to be used............................................................................................................8
4.0 Introduction.....................................................................................................................................9
4.1 Resources..........................................................................................................................................9
4.1.1 Hardware......................................................................................................................................9
4.1.2 Software.........................................................................................................................................9
4.2 Budget...............................................................................................................................................9
CHAPTER 5: TIME PLAN....................................................................................................................10
CHAPTER 1: INTRODUCTION
1.0 Introduction
Asset management plays a pivotal role in the successful operation of modern organizations.
From tracking resources to ensuring their efficient utilization, organizations constantly seek
mechanisms that promote clarity, accountability, and efficiency in their asset-related endeavors.
This chapter introduces the need for an effective Asset Nexus System (ANS), the problems it
aims to address, and the proposed solutions.
1.1 Background of the Study
In recent years, the rapid evolution of business operations, coupled with technological
advancements, has rendered many traditional asset management systems obsolete. Many
organizations grapple with fragmented systems that struggle to accommodate the intricacies of
modern assets, ranging from tangible products to digital solutions. As businesses expand and
diversify, there emerges a compelling need to have a unified platform that seamlessly integrates
with various departments, ensuring consistent and up-to-date asset tracking.
1.2 Problem Statement
Most extant asset management solutions suffer from a multitude of drawbacks. Firstly, many are
not flexible enough to accommodate the dynamic nature of modern assets, leading to
discrepancies in asset records. Secondly, the lack of a user-friendly interface in many systems
hampers swift asset registration and tracking. Furthermore, a lack of transparency in resource
allocation often results in inefficiencies, as managers are unable to make informed decisions
regarding asset distribution. Lastly, traditional systems seldom offer comprehensive reporting
tools, leaving organizations in the dark about their asset health and status.
1.3 Proposed Solution
To address the challenges outlined above, this study proposes the development of a
comprehensive Asset Nexus System (ANS). The ANS will be ensuring accessibility, scalability,
and real-time data synchronization.
1.3.1 Objectives
Design and Implement: Develop a user-friendly interface that facilitates easy asset registration,
tracking, and reporting.
Transparency and Accountability: Create modules that enable clear resource allocation, ensuring
assets are appropriately assigned to individuals or departments, promoting responsibility and
efficiency.
Real-time Monitoring: Integrate state-of-the-art tracking mechanisms that provide real-time
updates on asset status, preempting potential issues and ensuring assets are well-maintained.
Comprehensive Reporting: Equip the ANS with tools that generate detailed, intuitive reports,
offering insights into asset distribution, status, and health, aiding in strategic decision-making.
CHAPTER 2: LITERATURE REVIEW
2.0 Introduction
Literature reviews lay the groundwork for any academic or research-oriented endeavor by
presenting a holistic view of existing knowledge in the area of study. The objective of this
chapter is to delve into the current landscape of asset management, highlighting its evolution, the
challenges faced by existing systems, and the emergent solutions proposed by researchers and
industry experts.
2.1 Literature Review
2.1.1 Evolution of Asset Management
The roots of asset management can be traced back to traditional inventory systems used in
ancient civilizations, where manual ledgers and logs were maintained (Johnson, 1995). With the
industrial revolution, the demand for structured inventory systems surged, prompting the
integration of mechanical aids and later, computerized systems (Roberts, 2007). The advent of
Information Technology (IT) in the latter half of the 20th century marked a transformative era
for asset management, leading to the proliferation of digital tracking, barcoding, and RFID
technologies (Smith & Tan, 2010).
2.1.2 Challenges in Modern Asset Management
Despite significant advancements, modern asset management systems are far from perfect.
Thompson (2018) highlights the rigid structure of many systems, which limits flexibility and
adaptability to diverse assets. Another concern raised by Wang et al. (2019) pertains to data
security and the vulnerability of cloud-based asset management solutions. The integration of IoT
and smart technologies further complicates the asset management landscape, presenting
challenges in terms of interoperability and real-time tracking (Martin & Lewis, 2021).
2.1.3 Emergent Solutions and Innovations
The challenges in asset management have paved the way for innovative solutions. Block-chain
technology, for instance, promises enhanced security and transparency in asset transactions
(Foster & Patel, 2020). Additionally, the integration of Artificial Intelligence (AI) and Machine
Learning (ML) in asset management systems offers predictive analytics, aiding in preemptive
maintenance and asset lifecycle forecasting (Jones & Kumar, 2022). Furthermore, recent
research by Nelson et al. (2022) points towards the growing trend of hybrid asset management
systems – combining the strengths of on-premises and cloud-based solutions to provide
flexibility, security, and scalability.
2.1.4 Gap in the Literature
While there is extensive literature on the challenges and innovations in asset management, there
is a dearth of comprehensive studies that focus on integrating these solutions into a unified
platform, tailored for contemporary organizational needs. This study seeks to bridge this gap,
proposing an Asset Nexus System that encapsulates the best of modern technology while
addressing prevalent challenges.
In conclusion, while the domain of asset management has witnessed significant advancements,
there remains ample room for innovation, especially in creating holistic, adaptable, and secure
solutions. This literature review provides the foundation upon which the proposed Asset
Management System is based, aiming to push the boundaries of what's currently feasible and
setting a new benchmark in the realm of asset management.
CHAPTER 3: METHODOLOGY
3.0 Introduction
This chapter delves into the methodology that will be employed to design and develop the Asset
Nexus System (ANS). The chosen development approach, programming language, and database
system have been detailed below.
3.1 The Incremental Model
In developing the ANS, the incremental model has been chosen due to its adaptability and
efficiency. This model allows for system development in manageable increments or portions,
each adding to the previously developed sections.
3.1.1 Phases of the Incremental Model
Requirements
Specifications
Design
Implementation
Testing
Requirements and specification: This phase involve gathering and analyzing the specific
needs of the ANS. Inputs from stakeholders, such as system end-users and managers, will
be taken into account.
Design: Here, a blueprint of the system will be drawn up, factoring in the functionality,
user interface, and interactions of different components.
Implementation: Each increment or module of the system will be developed separately.
As new increments are developed, they will be integrated with the previously developed
ones.
Testing: Every increment will undergo rigorous testing to ensure it meets the specified
requirements and integrates seamlessly with other parts of the system.
Evaluation: After integrating each increment, feedback from users will be collected and
analyzed to guide the development of subsequent increments.
3.2 Computer Programming Language to be used
The chosen programming language for the ANS development is Java, utilizing the Java Swing
framework. Java Swing will facilitate the creation of a rich and interactive user interface. Java is
renowned for its platform independence and robustness, making it ideal for a system that
demands reliability and cross-platform compatibility.
3.3 Database System to be used
For data storage, retrieval, and management, MySQL's Maria-DB will be utilized. Maria-DB is a
powerful, open-source relational database system that offers high performance, security, and
scalability, ensuring the ANS's data remains organized, accessible, and secure.
CHAPTER 4: RESOURCES AND BUDGET
4.0 Introduction
This chapter provides insights into the resources required for the successful implementation of
the ANS and the associated budgetary considerations.
4.1 Resources
4.1.1 Hardware
Server: A dedicated server will be required to host the Maria-DB database, ensuring fast data
retrieval and backups.
Workstation (Laptop): Development machines with sufficient RAM, processing power, and
4.1.2 Software
Java Development Kit (JDK): Necessary for Java Swing development.
Maria-DB: The relational database management system for storing and managing the AMS's
data.
Integrated Development Environment (IDE): Tools like NetBeans or IntelliJ IDEA, which offer
environments optimized for Java development.
4.2 Budget
The budget for the ANS will be categorized into different sections:
Hardware procurement: Costs associated with acquiring servers, workstations, and networking
equipment Totaling to ksh.45,000
Software Licenses: While Java and Maria-DB are open-source, there might be costs associated
with certain IDEs or additional plugins/tools.
Development & Testing: Costs related to man-hours spent on designing, developing, and testing
the system. Totaling to ksh. 5000.
Miscellaneous: Unforeseen expenses, and system documentation production. Totaling to
ksh 5000
The successful completion of the Asset Nexus System (ANS) project necessitates a well-structured and
strategic time plan. Ensuring timely delivery of each phase while maintaining the highest quality
standards is of paramount importance. This chapter outlines the project's time plan, detailing the start and
end dates for each section of the project, spanning from October 2023 to April 2024.Gantt Chart:
Duration 16th -23rd 25th -30th 2nd -6th 7th-10th 10th 11th 13th-22nd 24TH-
October 2ND
Activity October November November November November November
Decem
ber
Idea
Presentation
Introduction
Literature
Review
Methodology
Resources and
Budget
Proposal
Time Plan
System
analysis and
Requirements
Specification
System design
