Asset Management System

Dissertation Submitted in Partial fulfillment of the

Requirement for the Award of the Degree of

Bachelor of Computer Applications

Semester VI

Jan - May, 2017

Under the guidance of Submitted By

Dr.Shraddha Masih Neetu Singh-1410132

School of Computer Science & IT

Devi Ahilya Vishwavidyalaya, Indore, M.P.2017

I
 School of Computer Science & IT
Devi Ahilya Vishwavidyalaya, Indore, M.P.

DECLARATION

I hereby declare that the project titled Asset Management System

submitted by me for the partial fulfillment of the requirement for the
award of Bachelor of Computer Applications to School of Computer
Science & IT, Devi Ahilya Vishwavidyalaya, Indore, comprises my own
work and due acknowledgement has been made in text to all other
materials used.

Signature of Student:
Date:
Place: SCSIT, DAVV, Indore

II
 School of Computer Science & IT
Devi Ahilya Vishwavidyalaya, Indore, M.P.

CERTIFICATE FROM GUIDE

It is to certify that dissertation on Asset Management System, submitted by

Ms.Neetu Singh to the School of Computer Science & IT, DAVV, Indore has been
completed under my supervision and the work is carried out and presented in a
manner required for its acceptance in partial fulfillment for the award of the degree of
Bachelor of Computer Application.

Project Guide
Signature:

Name:
Date:

III
 School of Computer Science & IT
Devi Ahilya Vishwavidyalaya, Indore, M.P.

CERTIFICATE

It is to certify that we have examined the dissertation on Asset

Management System submitted by Neetu Singh to the School of
Computer Science & IT, DAVV, Indore and hereby accord our approval
of it as a study carried out and presented in a manner required for its
acceptance in partial fulfillment for the award of the degree Bachelor of
Computer Application.

Internal Examiner: External Examiner:

Sign: Sign:
Name: Name:
Date: Date:

IV
 ACKNOWLEDGEMENT

Apart from the efforts done, the success of any project depends largely on
the encouragement and guidelines of many others. I take this opportunity
to express my gratitude to the people who have been instrumental in the
success of this project.
I express my heartfelt thanks to my revered Head of Department Dr.
Sanjay Tanwani, project coordinator Mr. Hitesh Ninama and project
guide Dr. Shraddha Masih,SCSIT, for their evaluable guidance,
significant suggestion and help for accomplishing the project work. I feel
motivated and encouraged every time I attend her meeting. Without their
encouragement and guidance the idea would not have been materialized.
The guidance and support received from all the member who contributed
and who are contributing to this project, was vital for this project. I would
like to thank SCSIT staff member and institute, in general for extending a
helping hand at every juncture of need. We are highly grateful for their
constant support and help.
.

V
 ABSTRACT

The record keeping routines, information tracking, complicated logistics and many
other administrative procedures are all regular activities that constantly make up the
core processes in the management of real assets. However these processes could be
quite cumbersome and inefficient when manual systems being used continue to play
prominent roles in organizations that offer such services. Basically, with the advent of
this project "ASSEST MANAGEMENT SYSTEM" work finds it necessary to study
and analyze the difficulties inherent in the administration and management of asset
manually in organizations with a view to proposing an extensive solution to these
problems.

VI
 CONTENTS

Description Page No
1.INTRODUCTION 1-2
1.1Aim 1
1.2Objective 1
1.3Scope 2
1.4Purpose 2
1.5 Problem with existing system 2

2.ANALYSIS 3-8
2.1Project Overview 3
2.2Specification Requirement 4
2.4Software Specification 6

3.PROJECT PLANNING 7

4.SYSTEM DESIGN 7-14

4.1Introduction 8
4.2Design Process 9
4.3Design Principles 10
4.4Database Design 11
4.5Data Flow Diagram 12-13
4.6Data Dictionary 14

5.SOFTWARE DEVELOPMENT 15
5.1 Software Development Life Cycle

6.SYSTEM IMPLEMENTATION 16-18

6.1Introduction 16
6.2Hardware Requirement 17
6.3Software Requirement 18

7.SYSTEM TESTING 19-20

7.1 Introduction 19
7.2 White Box Testing 19
7.3Unit Testing 20
7.4 Verification and Validation 20

VII
8.OUTPUT FORMS AND REPORTS 20-22

9. FUTURE SCOPE 23

24
10.CONCLUSION

VIII
 1. INTRODUCTION

Asset Management system plays a typical role and acts like a link between Units of an
Organization usually a department.
1.1 Aim

This Asset Management System helps in creating and managing a data repository of
the assets in organization,just a paper free work and time saving system.

1.2 Objectives

The main objective of Asset Management system is to introduce computerized

system in a widely spread organization which can be used as a resource for
management ,in order to fulfill the basic needs of an Organization like Information
about assets.
The following points describe the objective of Asset Management System.

1.To eliminate the error associated with the existing system.

2. To provide more reliable storage and retrieval of asset record through the use of
computer.
3.To increase information availability and accessibility.
4. To enable asset managers easily estimate assets.

I
1.3 Scope

The following points describe the scope of Asset Management System.

1.Basic procedures and process associated with record keeping.

2. Information about assets.
3. It provides facility to download excel sheet of asset information.

1.4 Purpose

Asset Management System is a web based application,that helps to manage inventory

of assets .

1.5 Problems Inherent in the Existing Manual System

The following are the lapses in the existing manual system:

1. Inaccurate data entry and mix-up of records
2. Unavailability of accurate data-bank of records since paper is a bio-degradable
material they tend to spoil with time
3. Ineffective security of documents
4. Long process on retrieval of record due to large volume of paper stored
5. Delay in accounting and auditing proceedings due to tedious process involved in
record retrieval
6. Documents occupy a lot of space that could be put into other profitable use.

2
 2. ANALYSIS

2.1 Project Overview

This application ASSET MANAGEMENT targeted for the information of assets

entry in the deapartment.

2.1 Specification Requirement

The project is based on:-

The Interface of the New System

The application login Page (this requires a User name and Password)
Applications Main Page from this page other windows can be called and admin
can interact with the information of assets. It contains assets name,incorportae
date,department particular class name.
Details page used to enter information about Assets admin into the database
Asset Details page used to Enter assets into the database and to find asset
information.
A Report Page uses excel reports to display information about assets.

2.4Feasibility Study:

The purpose of a feasibility study is to provide a sound basis for decision-making.

The best decisions are made with the benefit of a high level of information. The
feasibility study examines the options for the provision and acquisition of assets. The
feasibility study comprises both specification and appraisal. Specification. This
involves the detailed examination of service demand, the assessment of options for
service delivery against service delivery levels and emerging environmental factors. It
also involves the development of an asset acquisition brief that identifies alternative
courses of action to meet the service demands and the training requirements for staff
if new skills are involved in the assets operation.. They are

3
 Economical feasibility
Technical feasibility

2.4.1 Economical Feasibility:

Economical feasibility is concerned with cost savings, increased profits & reduction
in efforts. It shows how much beneficial is the new developed system over the
existing system.
As this Application is related to service sector which aims at providing better service.
Providing better service is the basic requirement of any organization either service
sector or financial sector. So the proposed system is economically feasible as it also
reduces manpower utilization.

2.4.2 Technical Feasibility:

Technical feasibility deals with the existing technology, software and hardware
requirements of the proposed system. The proposed system ASSET
MANAGEMENT SYSTEM needs the following:
Dual Core Processor, 512 MB RAM.
Microsoft Access for DB backend
HTML,JSP as front-end tool
In order to implement the proposed system necessary technology will be acquired.
Hence the proposed system is technically feasible.

2.5 Software Specification

2.5.1 System Environment and Tools

Eclipse IDE

Eclipse is an open source Integrated Development Environment (IDE) used

extensively for web-application development. It has various versions like Callisto,
Europa, Ganymede, Galileo, Helios, Indigo and Juno. This system uses Eclipse for
processing the information received via JavaServer Pages. It is also used for

4
interacting with the database, in this case Microsoft access, for storing, modifying and
retrieving information.

Apache-Tomcat-9.0.0.M11

Apache-Tomcat-9.0.0.M11Apache Tomcat is an open source web server and servlet

container. Tomcat implements the Java Servlet and the JavaServer Pages (JSP)
specifications from Oracle Corporation, and provides a pure Java HTTP web server
environment for Java code to run. This would be used to host the JavaServer Pages
required for user interaction.

Web Browser

Web Browser A web browser is a software application for retrieving and presenting
information on the World Wide Web. This system is hosted using the Apache Tomcat
web server and can be accessed via a web browser by entering the URL of the hosted
JavaServer Page. All the user-system interactions are done through the web browser.

3.PROJECT PLANNING

Planning is one of the most important project management and time management
techniques. Planning is preparing a sequence of action steps to achieve some specific
goal. If you do it effectively, you can reduce much the necessary time and effort of
achieving the goal.
It is during this phase that a project management plan is developed all comprehensive
of individual plans for cost, scope, time, quality, communication, risk and resources.
Some of the important activities that mark this phase are - development of schedule,
milestone charts, GANTT charts, estimating and reserving resources, planning dates
and modes of communication with stakeholders based on milestones, deadlines and
important deliveries. Projects have identified and unidentified risks that may affect
aspects of projects in later stages, hence a plan for managing these risks should they
happen is determined. Risk management planning includes risk identification and

5
analysis, risk mitigation approaches and risk response planning.This phase include
following things:

1. ANALYSIS

Project overview
Specification Requirement
Hardware & Software Requirements
Software Specification

2. SYSTEM DESIGN

Introduction
Design Process
Design Principles
Database Design
Data Flow Diagram
Data Dictionary

3. SOFTWARE DEVELOPMENT METHODOLOGY

Software development life cycle

4. SYSTEM IMPLEMENTATION

Introduction
Hardware Requirements
Software Requirements

5. SYSTEM TESTING

Introduction
Black Box Testing
White Box Testing
Unit Testing
Integration Testing
Verification and Validation

4.SYSTEM DESIGN

6
4.1 Introduction

Design is the first step in the development phase for any engineering product (or)
system. It may be defined as the process of applying various techniques and
principles for the purpose of defining a device, a process, or a system insufficient
detail to permit its physical realization.
Software design is an iterative process through which requirements are translated into
a Blue print for constructing the software. The design is represented at a high level
of abstraction. A level that can be directly translated to specific data, functional and
behavioral requirements.
Preliminary design is concerned with the transformation of requirements into a data
and software architecture. Detail design focuses on refinements to the architectural
representation. That leads to detailed Data structure and algorithmic representation for
software.
In the design step, the element of the analysis model gets converted into a data
design, and architectural design, an interface design and a procedural design.
The data design transforms the information domain model created during analysis
into the data structures that will be required to implement software.The architectural
design defines the relationship among major structural elements of the program.
The interface design describes how the software communicates within itself, to
systems that interoperate with it, and with humans who use it. An interface implies a
flow of information. Therefore, the data and control flow diagrams provide the
information required for interface design.

7
4.2 Design Process

Design process is in between the analysis and implementation process. The following
design diagrams (data flow diagrams) make it easy to understand and implement.The
design process of software system has two levels.
1. Systems Design or Top Level Design.
2. Detailed Design or Logical Design.

System Design or Top Level Design:

In the system design the focus is on deciding which modules are needed for the
system, the specification of these modules andhow these modules should be
interconnected.

Detailed Design or Logical Design:

In detailed design the interconnection of the modules or how the specifications of
the modules can be satisfied is decided . Some properties for a software system
design are

Verifiability
Completeness
Consistency
Trace ability
Simplicity/understandability

8
4.3 Design principles:
Basic design principles that enable the software engineer to navigate the design
process are:
1. The design process should not suffer from Tunnel vision.
2. The design should be traceable to the analysis model.
3. The design should not reinvent the wheel.
4. The design should minimize the intellectual distance between the software and
the problem .
5. The design should exhibit uniformity and integrity.
6. The design should be structured to accommodate changes.
7. The design is not coding. The coding is not a design.
8. The design should be assessed for the quality, as it is being created, not after the
fact.
9. The design should be reviewed to minimize the conceptual errors.

9
4.4Database Design:
The goal of Database Design is to generate a set of relation schemes that allow
us to store information without unnecessary redundancy and allows us to retrieve
information easily. We can achieve optimization, ease of use in maintenance by
designing the database using relationalmodel between oramong the tables.

To reduce redundancy.
To arrive at loss-less join.
To reduce the time as compared to the present system.
To reduce the number of errors.

10
4.5 Data Flow Diagram (DFD)

The data flow diagram (DFD) is one the most important modeling tools. It is used to
model the system components. These components are the system process, the data
used by the process, an external entity that interacts with the system and the
information flows in the system.
DFD shows how the information moves through the system and how it is modified by
a series of transformations. It is a graphical technique that depicts information flow
and those transformations that are applied as data moves from input to output.DFD is
also known as bubble chart. A DFD may be used to represent a system at any level of
abstraction. DFD s may be partitioned into levels that represent increasing
information flow and functional details.
A level 0 DFD, also called as the context diagram, represents the entire system as a
single module with input and output data indicated by incoming and outgoing arrows
respectively. Additional process and information flow paths are represented, as the
level 0 DFD is partitioned to reveal more details. A level 1 DFD, also called as top-
level DFD, represent the system with major modules and data stores. The other levels
will show each module in the top-level DFD in a more detailed fashion.

Notation:

Data Flow: Data move in a specific direction from an origin to a destination. The
data flow is a packet of data.

Process: People, procedures or devices that produce data. The physical component is
not identified.

Source or Destination of data: External sources or destinations of data, which may

be people or organizations or other entities.

Data Store:Here, the data referred by a process in the system.

11
0 level dfd:

1 level dfd:

Use case diagram for admin:

12
E-R diagram:

4.6 Data Dictionary

A data dictionary is a catalog a repository of the elements in the system. As the

name suggests, these elements center on data and the way they are structured to meet
user requirements and organization needs. A data dictionary is a collection of data
about data. The basic idea is to provide information on the definition, structure and
the user of the element an organization uses. The data element is a unit of data that
cant be decomposed.

13
 5. SOFTWARE DEVELOPMENT METHODOLOGY

5.1 Software Development Life Cycle:

The systems development life cycle (SDLC) is a conceptual model used in

project management that describes the stages involved in an information system
development project, from an initial feasibility study through maintenance of the
completed application. Various SDLC methodologies have been developed to guide
the processes involved, including the waterfall model (which was the original SDLC
method); rapid application development (RAD); joint application development (JAD);
the fountain model; the spiral model; build and fix; and synchronize-and-stabilize.
I implemented Waterfall model in this project. Some methods work better for specific
types of projects, but in the final analysis, the most important factor for the success of
a project may be how closely the particular plan was followed.
In general, an SDLC methodology follows these steps:

If there is an existing system, its deficiencies are identified. This is

accomplished by interviewing users and consulting with support personnel.

The new system requirements are defined including addressing any

deficiencies in the existing system with specific proposals for improvement.

The proposed system is designed. Plans are created detailing the hardware,
operating systems, programming, and security issues.

The new system is developed. The new components and programs must be
obtained and installed. Users of the system must be trained in its use, and all
aspects of performance must be tested. If necessary, adjustments must be
made at this stage.

14
 6. SYSTEMIMPLEMENTATION

6.1 Introduction:

Implementation is the process of assuring that the information system is

operational and then allowing users take over its operation for use and evaluation.
Implementation includes following activities.

Obtaining and installing the system hardware.

Installing the system and making it run on its intended hardware.
Providing user access to the system.
Creating and updating the database.
Training the users on the new system.
Documenting the system for its users andfor those who will be responsible for
maintaining.
Making arrangements to support the users as the system is used.
Transferring ongoing responsibility for the system from its developers to the
operations.
Evaluating the operation and use of the system.

The most visible component of implementation process is the system conversion. The
four basic conversion strategies include.

Direct Conversion
Parallel Conversion
Pilot conversion
Phased Conversion

Direct Conversion:
In direct conversion, the organization stops using the old system and starts using the
new one at the same time.

15
Parallel Conversion:
A parallel conversion involves running both old system and new system and
comparing their results. The new system is accepted only after the results have
matched for an acceptable period.

Pilot Conversion:
Pilot conversion means introducing the new system to a small part of the organization,
expanding its use once it is known to operate property there. Eventually, it will be
in use by the entire organization.

Phased Conversion
Phased conversion means introducing a system in stages, one component or module
at a time, waiting until that one is operating properly before introducing the next.

6.2 Hardware Environment

CPU : Dual Core, 1.3 GHz
RAM : 512 MB
Hard disk : 50 GB

6.3 Software Environment

Operating Environment : Windows Xp and Above
Back-End : Microsoft Access
Front End : HTML, JSP
Browser : IE7,Chrome, Mozilla

16
 7. SYSTEM TESTING

7.1 Introduction:

System testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding. Software testing fundamentals
define the overriding objectives for software testing. Testing is one of the steps in the
software engineering process that could be viewed (psychologically, at least) as
destructive rather than constructive.

Testing is a process of executing a program with the intent of finding an error. A good
test case is one that has a high probability of finding a yet undiscovered error. A
successful test is one that uncovers an as yet undiscovered error.

7.2 White-Box Testing (GLASS-BOX TESTING)

White-box tests focus on the program control structures. Test cases are derived to
ensure that all statement in the program has been executed at least once during testing
and that all logical conditions have been exercised.

Knowing the internal working of a product, tests can be conducted to ensure that
all gears mesh, that is the internal operation performs according to specification
and all internal components have been adequately exercised.

White box testing is a test case design methods that uses the control structure of the
procedural design to design to derive test cases.

1. Guarantee that all independent paths within a module have been exercised at
least nice.
2. Exercise all logical decision on their and false sides
3. Execute all loops at their boundaries and within their operational bounds.
4. Exercise internal data structures to ensure their validity.

17
7.3 Unit Testing

Unit testing focuses verification effort on the smallest unit of software design. Using
the procedural design description, important control paths are tested to uncover errors
within the boundary of the module. The relative complexity of test and uncovered
errors is limited by the constrained scope established for unit testing. The unit test is
normally the constrained scope established for unit testing. The unit test is normally
white box oriented, and the step can be conducted in parallel for multiple Modules.

The module interface is tested to ensure that information properly flows into and out
of the program unit under test. The local data structure is examined to ensure that data
stored temporarily maintains its integrity during all steps in an algorithms execution.
Boundary conditions are tested to ensure that the module operates properly at
boundaries established to limit or restrict processing.

18
7.4 Verification and Validation:

Validation is a process of finding out if the product being built is right? i.e. whatever the
software product is being developed; it should do what the user expects it to do. The
software product should functionally do what it is supposed to, it should satisfy all the
functional requirements set by the user. Validation is done during or at the end of the
development process in order to determine whether the product satisfies specified
requirements.
The standard definition of Verification goes like this: are we building the product
RIGHT? i.e. verification is a process that makes it sure that the software product is
developed the right way. Thesoftware should confirm to its predefined specifications, as
the product development agues through different stages, an analysis is done to ensure that
all required specifications are meeting.
Validation and verification process go hand. In handbut visibly validation process starts
after verification process ends (after coding of the product ends). Each verification
activity (such as requirement specification verification. Functional design verification
etc.) Its corresponding validation activity (such as functional validation/testing, code
validation/testing, system/integration validation. etc.).

7.5 Testing Analysis

Table 2

S.No Testing object Explanation Remarks

Equal of expected and
1 Password Pass
simulated values
Unequal of expected
2 Password Fail
and simulated value

19
8. OUTPUT FORMS &REPORT

fig:1.welcome form

fig-2.login update form

20
 fig:3.update form

fig:asset entry form

21
fig:4.asset excel sheet

fig:5.asset view form

22
 9. FUTURE SCOPE
Since, the system is organized in a very structured manner using Microsoft access
database, it is possible to expand the system to encompass even more information.
More number of attributes regarding an asset can be stored, modified and viewed
depending upon the requirement.
The number of possible operations on the data can be increased. Features like sorting
asset entries based on their value, last modified date, etc can be incorporated.
Computational features such as calculating the current value of assets, calculating the
increase or decrease in the value of an asset can also be integrated with the existing
system. A feature to create soft-copy in different file formats like .xls, .pdf, .doc, etc
of different assets possessed by a user can also be unified in the system. This feature
would help the user to instantly process an electronic copy of the list of assets
currently maintained in the system.

10. CONCLUSION

No application can be called perfect in the fast moving hi-tech world. Asset
Management seems to be very useful but may be outdated near future.
The Asset Management system is designed for efficient management of several assets
possessed by an individual. It allows the user to add information about different assets
in a quicker and systematic way. The data is organised efficiently to aid future
expansion of the system. The user is facilitated with the feature of updating the
existing information of an asset entry. This feature is especially helpful while
maintaining assets like Bank Accounts and Mutual funds, since their values are
constantly changing. As observed in figure4, the asset management system provides
the facility to view the different asset entries pertaining to different asset types. This
feature helps to keep a track of all assets in a much quicker and efficient way as
compared to the traditional method of poring over innumerable files.

23
Reference:

Baron Schwartz, Peter Zaitsev, Vadim Tkachenko, Jeremy Zawodny, Arjen

Lentz and Derek J. Balling, High Performance MySQL.
Mark Matthews, Jim Cole, Joseph D. Gradecki, MySQL and Java Developer's
Guide.
Budi Kurniawan, Java for the Web with Servlets, JSP, and EJB: A Developer's
Guide to J2EE Solutions.
Deepak Alur, John Crupi, Dan Malks, Core J2EE Patterns: Best Practices and
Design Strategies (Second Edition)
http://tomcat.apache.org/tomcat-7.0-doc/index.html
http://dev.mysql.com/doc/workbench/en/index.htmlhttp://www.google.com
http://www.wikipedia.com
http://www.youtube.com
http://www.livecareer.com
http://www.codecademy.com
http:// www.htmlgoodies.com
https://www.codecademy.com

24