Online Asset Tracking Software for LogistiX Company

The project aims at developing an online based asset tracking system for LogistiX company. The system will include features like addition, modification, and deletion of assets, as well as version control. The system will be accessed securely over the internet and will eliminate data inconsistency and redundancy.

Background
The project aims at developing an asset tracking software for LogistiX company. Currently,
the company is using spreadsheet to track their assets which includes containers, trucks,
cranes and other maintenance items. This manual monitoring of the assets can no longer be
used because of increase customer base and its scalability. Also, with the increase in data,
keeping information in spreadsheet has become a new challenge.
Hence, a new proposal has been put forward to develop an online based asset tracking system
with a secure accessibility layer over the internet. In this project, a backend i.e. data storing
functionality shall be created using a database, preferable a free source and a frontend shall
be created to present an interface to the user where in one can enter or retrieve data from the
backend. The system shall be accessed by only authorized person. There shall be no data
inconsistency and redundancy and remain protected from illegal access. The entire system
will be present in cloud i.e. company will have to pay as per the use and no infrastructure
shall be required to be installed on company’s end.
Group members
# Group member name Mark
1
2
3
Sprint Planning
Activities
In the first sprint, the analysis and planning activities will be carried out. The requirements
will be defined and included in the product backlog and the number, duration, resources, and
budget for each sprint will also be determined in the first sprint.
The second sprint will include the initiation of design activities and the UI aspects of the
online asset tracking system along with the system prototype will be prepared. The
development will begin by the end of this sprint (Rajasekaran, 2015).
1

Features to be Investigated/Implemented
The features will include the addition, modification, and deletion of an asset from the system.
The version control features will also be added.
Members Assigned
Members of the Team Tasks & Features
Team Member 1 Project planning, design of the UI/UX aspects
Team Member 2 Requirements analysis – user, functional, non-functional, security
frameworks, and design prototypes
Team Member 3 Investigation and setting up the database at the back end, cost
estimations
Team Member 4 Development of the source code, wireframes
Team Member 5 Development of the source code, wireframes
List of Resources
There will be five members in the project team.
 Team Member 1 (Name)
 Team Member 2 (Name)
 Team Member 3 (Name)
 Team Member 4 (Name)
 Team Member 5 (Name)
Ownership Roles
Members of the Team Ownership
Team Member 1 Project planning, System Design
Team Member 2 Requirements analysis – user, functional, non-functional, System
Security, System Design
Team Member 3 Backend of the System, Project Budget
Team Member 4 System Development, System Design (Wireframes)
Team Member 5 System Development, System Design (Wireframes)
User Stories
User story # User story List of features
2

1 As a staff, I wish to manipulate asset data
so that all assets information is present on
cloud and can be accessed by all the
employees across the remote locations.
 Add an asset
 Modify an asset
 Delete an asset
2 As a staff, I wish to have a version control
system so that all employees get to know
when and who has updated status of
which items
 Update status of item
 Create a version
entry
 List all change
versions
3 As a manager, I would like to access the
system over the Internet so that the
information can be shared at any time and
the accessibility is not an issue
(Ashbacher, 2010).
 Access the system
over the Internet
 Securely log in to the
system
4 As a staff, I would like to have the record
of the changes accessible on the system
 Access the change
log
Story points
List of features Story points Explanation
Add an asset 2 The feature is more completed than listing
feature. It includes various validation on
entered data and then raising error
accordingly.
Modify an asset 3 The feature is more complicated than adding
because along with performing all actions
for adding feature, it will also conduct dirty
checking.
Delete an asset 1 This is 1/3rd complicated as compare to
modify function because it needs not to
conduct validations which are required for
modify and add features.
Update status of item 2 This is less complicated as compare to
3

“Modify” feature.
Create a version entry 3 This feature is more complicated that above
all because versioning is a complicated
feature.
List all change versions 1 It just involves listing of versions.
Access the system over the
Internet
1 It is the basic functionality of the system.
Securely log in to the system 1 It is the basic functionality of the system.
Access the change log 1 It is the basic functionality of the system.
Reflection
We will design the online asset tracking software for the organization using responsive
methodology so that the users get to have enhanced interaction and responsiveness with the
system and the development processes will also be simplified for us. We could analyze the
issues that the organization currently has in terms of the asset tracking and control and could
identify the need and requirements of the system so that we could deliver the system as per
the expectations of the client. We have decided to use PHP as the programming language for
the system as it will allow us to develop a system that is flexible, reliable, and secure. The
first two sprints provided us with the ability to carry out the initial planning and analysis
activities along with the completion of the system design so that the development processes
could begin. There will be two more sprints needed to complete the activity and develop the
system ready for deployment.
4

References
Ashbacher, C. (2010). Succeeding With Agile: Software Development Using Scrum, by Mike
Cohn. The Journal Of Object Technology, 9(4). doi: 10.5381/jot.2010.9.4.r1
Rajasekaran, V. (2015). Issues in Scrum Agile Development Principles and Practices in
software development. Indian Journal Of Science And Technology, 8(35). doi:
10.17485/ijst/2015/v8i35/79037
5