Manage IBD Assets Efficiently

IBD ASSET MANAGEMENT 1
CHAPTER-1
INTRODUCTION
.

1. INTRODUCTION
“IBD (INDUSTRIAL BATTERY DIVISION) ASSET MANAGEMENT SYSTEM”
is the process of maintaining the records of information regarding to the Battery service tools,
minimization of manual work and increasing computer automation.
1.1 Organization Profile
History
Amara Raja Batteries Limited (ARBL) has been started by the technocrat Mr.
Ramachandra N.Galla, hailing from Chittoor Dist. of A.P, INDIA. Mr.R.N.Galla holds a
postgraduate degree in applied electronics in Rourkela University and MS (control system) at
Michigan University in U.S.A. He started his career as an engineer in USA, worked for 17 years
specializing in the arrears of UPS system, Battery Chargers and Batteries.
Amara Raja Batteries Limited (ARBL) a widely held public limited company was
established in 1985 as private Limited Company was established in 1985 as private Limited
Company and subsequently converted into public Limited Company in 1989.
The registered office and works of the company are situated near the temple town
Tirupati. ARBL is engaged in the manufacturing of maintained Free-value Regulated Lead Acid
(VRLA) storage batteries and automotive Batteries. ARBL is the first company to introduce
these Hi-tech (VRLA) Batteries in INDIA.ARBL had a technical partnership with JCI, USA.
Amara raja is largest supplier of standby Power System to core Indian utilizes such as
India Railways, Department of Telecommunications ,electricity Boards and major power
generation companies. On VRLA front: Amara raja Batteries Limited is primarily
.

manufacturing two types of VRLA Batteries, namely power Stack and Power Plus/Kombat
Batteries.
Power Plus/Kombat:
Power Plus/Kombat batteries are manufactured in mono block version 12V, 6V, 4V, 2V
with capacities ranging from 40 to 4000h. These batteries have good high rate discharge
capability due to thinner grids and more active materials. This battery in general finds
applications in UPS (Uninterrupted Power supply system) and EPABE (Electric Private
Automatic Exchange).
Power Stack:
Power Stack Batteries are manufactured as 2 volt Cells. Which are kept in mild steel
trays, the power system cells are available in 40 to 500 Ah Capacity range. Power Stack
batteries have excellent float characteristics; hence his range finds wide use in the segments of
telecommunication, Railways, power and Process Industries.
Auto Batteries:
After the successful launch of VRLA Batteries ARBL Introduced highly versatile and
long life automotive batteries into the INDIAN market. These batteries not only well received
by the customers, but also the product were judged as the best product of the year 2000. The
company is seriously contemplating to introduce a variety of other new and versatile models to
meet ever-increasing demand in other segments.
Amara raja entered into a joint venture agreement in the year 1997 for manufacturing
automotive batteries with JOHNSON Controls JNC, USA, and ARBL entered the replacement
product of collaborative and collective efforts of engineers concerned with Amara raja and JCI.
The fully charged factory activated Amaron provides an extra high starting performance
and power at any temperature and is specially designed to suit INDIAN roads and climatic
conditions.
.

ARBL has prestigious OE clients like Ford, Daimler Chrysler and general motors for
DIN range products and preferred Ashok Leyland, Mahindra & Mahindra, Hindustan Motors
for JIS range products.
1.2 Project Report Layout
The project consists of nine chapters, which tells about the system “IBD ASSET
MANAGEMENT SYSTEM”.
 Chapter 1 deals with the overview of the organization and its administrative
hierarchy has been discussed.
 Chapter 2 outlines the given problem, the solution proposed, methodology used and
looks at how the preliminary investigation is carried out, what are all its scope and objectives
and limitations of existing manual system.
 Chapter 3 is used to test the feasibility of the project i.e., operational, technical and
economical feasibilities of the system. Cost benefit analysis has been presented.
 Chapter 4 deals with System analysis. The logical model of the proposed system is
conceptualized and presented using data flow diagrams.
 Chapter 5 deals with system requirements. In this chapter what are all the software
and hardware components used to develop the system has been discussed.
 Chapter 6 presents system design. The different design techniques used in this
chapter are database design and user interface design.
 Chapter 7 presents software-testing strategies and techniques like white box testing,
black box testing.
 Chapter 8 gives the software and hardware implementation details of the system.
 Chapter 9 Conclusions.
 Appendix contains user manual, data entry screens and reports.
 Bibliography gives detailed information of references i.e., books, sites, guides etc.
.

CHAPTER-2
GENESIS OF STUDY
.

2. GENESES OF STUDY
This chapter deals with the study of the existing system and describes the need for the
proposed system to overcome the drawbacks in the existing system. It also specifies the
objectives, scope of the system and also the methodology for the system development.
Hence, the genesis of the study clearly depicts the factors regarding the beginning of the
existing system and its extension to the proposed system and it includes the following.
2.1 Aim
This project is aimed to develop an application for Maintaining assets related to the tools
which are used to send for technical Calibrations.
2.2 Problem description
This problem begins with Analyzing the existing system practice and problems with
regard to present situations. Further it discovers the potentials and significance in introducing
computer system for effective maintenance.
Project Module:
This module consists of all the projects that are undertaken by the IBD ASSET
MANAGEMENT SYSTEM. The entire project has been divided into five modules:
 INSTRUMENT MASTER
.

 NEW ALLOCATION
 CHANGE ALLOCATION
 ADD NEW STAFF
 REPORTS
Master:
The Master is to maintain the Instruments, Employees profile at time of initial stage. The
information about particular Service provider (operator), Tools or Instrument of the service
provider is stored in IBD Asset Management System.
 Instruments
 Employees
New Allocation:
The New Allocation is the process of the instruments is to allocating the employee at
first time. It maintains the information about instruments regarding to employee.
Change Allocation:
The Change Allocation is the process of the to Transferring instruments into one
employee to another after new allocation. The new employee information is needed for the
change allocation.
Add new staff:
To add the login details of the new staff .who is willing to take a tool from the IBD
he/she can sign up and take the tool for his/her purposes.
Reports:
.

The finally to generate the reports for particular instrument, employee, calibration time,
manufacturing date etc., in various categories.
2.2.2 Problems in the Existing system
 It is very difficult to maintain the information about the assets in the manner of asset
registers.
 It is very difficult to capture information about the assets.
 It is time consumable.
 All Force type master, Sector master details are not perfect that is deployment
information of the Employees.
2.2.3 Solutions to these problems
 Management has decided to have a system for tracking the assets which will access
the central database.
 This Application would facilitate the Marketing Division Department to track the
assets.
 The software and information stored on the organizations computer system.
 The Instrument with attributes like date of issue, type of instrument, cost of
instrument etc can be easily maintained.
 The monitoring of assets is very facile with this application.
 It is enhancement of old process system which is time consumable.
2.3 Scope of the Project
The Asset Management System is a multi-users, multi-offices, wed-based centralized
database management system. The system aims to assist organization to better manage the
allocation, distribution and productive use of its assets. The system facilitates the management
.

of assets with the objective of capturing information on assets and the tracking of the assets
through the entire assets life cycle of asset registration, assignment or allocation, maintenance
and eventually disposal or reported lost.
This project is aimed to develop an application for Maintaining assets related to the tools
which are used to send for technical Calibrations .Anything that is used by an organization in
order for it to achieve its function can be considered an asset of the organization.
A list of all the different types of assets must be drawn up. This may have been done as
part of the classification system if that system classifies assets according to their type. It could
also be standardized across the sector. This is a web based tool that allows logged in user to
maintain the Asset history.
2.4 Methodology
2.4.1 Prototyping Model:
The prototyping paradigm assists the software engineer and the customer to better
understand what is to be built when requirements are fuzzy. The prototype can serve as “The
first system”, the one that Brooks recommends we throw away. But this may be an idealized
view.
.

2.4.2 RAD Model:
Rapid Application Development is an incremental software process model that
emphasizes a short development cycle. The RAD model is a “high-speed” adaptation of the
waterfall model, in which rapid development is achieved by using a component-based
construction approach.
.
Communication
Planning
Deployment
Integration
Delivery
Feedback
Construction
Component reuse
Automatic code
Construction
Component reuse
Automatic code
Modeling
Business modeling
Data modeling
Modeling
Business modeling
Data modeling
Construction
Component reuse
Automatic code
Modeling
Business modeling
Data modeling
Team #n
Team #2
Team #1

60- 90 days
2.5 Proposed system
2.5.1 Advantages of Proposed System
The proposed systems successfully overcome the drawbacks of the existing manual
system. The system is proposed by taking the following aspects into consideration.
 Efficiency
 Extended Security
 Maintainability
 Easy Usability
Data security is another key area in which the system takes special care and reserves
valuable data from corruption, intentionally of accidentally, several reports can be generated in
desirable format and the required information can be retrieved quickly.
Greater Processing Speed:
Using computers inherent ability to calculate, sort; retrieve data with greater speed than
that of the human doing we can get results in less time.
.

CHAPTER-3
FEASIBILITY STUDY
.

3. FEASIBILITY STUDY
Generally the feasibility study is used for determining the resource cost, benefits and
whether the proposed system is feasible with respect to the organization. The feasibility of
proposed System could be evaluated as follows. There are three types of feasibility which are
equally important are:
 Operational feasibility
 Technical feasibility
 Economical feasibility
3.1. Operational Feasibility
The operational feasibility is the willingness & ability of the users to run the developed
system without any difficulty. The present system is been developed in such a way that the
users can use the system with maximum knowledge by giving the training about how to run the
system and the users require extra training to trouble shoot the errors at run time.
.

The data entry can be done without any difficulty because the screens has been
developed as user friendly and by seeing the screens itself, he can get an overview of the
process to be done. Operational Feasibility has to provide that the user have to feel the
operations are user friendly.
3.2 Technical Feasibility
Technical feasibility deals with the existing technology, software & hardware and its
family. Thus, we get to know that this project is considered technically feasible for the
development because the work for the project can be done with current equipment, existing
software technology and available personal. Hence the proposed system is technically feasible.
3.3 Economic Feasibility
This method is most frequently used for evaluating the effectiveness of a system. It is
also called as cost/benefit analysis. The development of the system can be done with the current
equipment, existing software technology. Since the required Hardware and software for
developing the system is already available in the organization, it does not cost for developing
the proposed system.
.

CHAPTER-4
SYSTEM ANALYSIS
.

4. SYSTEM ANALYSIS
System analysis is an important activity that takes place when we are building a new
system or changing existing one. Analysis helps to understand the existing system and the
requirements necessary for building the new system. If there is no existing system then analysis
defines only the requirements.
One of the most important factors in system analysis is to understand the system and its
problems. A good understanding of the system enables designer to identify and correct
problems.
Based on the drawbacks of the existing system the system is being planned. So the total
definition of the given problem has to be analyzed.
4.1 Entity-Relationship Diagrams
.

The Entity-Relationship Diagram depicts a relationship between data objects. The ERD
is the notation that is used to conduct the data modeling activity. The attributes of each data
object noted in the ERD can be described using a data object description.
At first a set of primary components are identified for ERD i.e. Data objects, Attributes,
Relationships and Various type indicators. Data objects are represented by labeled rectangles.
Relationships are indicated with labeled lines connecting objects.
.
Master
Change allocation
New allocation
Add new staff
Deploye
d
Collects
Rules Empid
pass
e-mail
Asset
NO
Locatio
n
Ename
EmpID
Locatio
n
Asset
type
Model
Asset
NO
Place
DeptEname
Emp
id

FIG 4.1: E-R Diagram for the module
4.2 Data Flow Diagram
A data flow diagram is graphical tool used to describe and analyze movement of data
through a system. These are the central tool and the basis from which the other components are
developed. The transformation of data from input to output, though processed, may be
described logically and independently of physical components associated with the system.
These are known as the logical data flow diagrams. The physical data flow diagrams show the
actual implements and movement of data between people, departments and workstations.
A full description of a system actually consists of a set of data flow diagrams. Using
two familiar notations Yourdon, Gane and Sarson notation develops the data flow diagrams.
Each component in a DFD is labeled with a descriptive name. Process is further identified with
a number that will be used for identification purpose. The development of DFD’s is done in
several levels. Each process in lower level diagrams can be broken down into a more detailed
DFD in the next level. The Top-level diagram is often called context diagram. It consists of a
single process bit, which plays vital role in studying the current system. The process in the
context level diagram is exploded into other process at the first level DFD.
.

The idea behind the explosion of a process into more process is that understanding at
one level of detail is exploded into greater detail at the next level. This is done until further
explosion is necessary and an adequate amount of detail is described for analyst to understand
the process. Larry Constantine first developed the DFD as a way of expressing system
requirements in a graphical form, this lead to the modular design.
A DFD is also known as a “bubble Chart” has the purpose of clarifying system
requirements and identifying major transformations that will become programs in system
design. So it is the starting point of the design to the lowest level of detail. A DFD consists of a
series of bubbles joined by data flows in the system.
DFD SYMBOLS:
In the DFD, there are four symbols
1 A square defines a source (originator) or destination of system data
2 An arrow identifies data flow. It is the pipeline through which the information flows
3 A circle or a bubble represents a process that transforms incoming data flow into
outgoing data flows.
4 An open rectangle is a data store, data at rest or a temporary repository of data.
Process
Source or Destination of
data
.

Data flow
Data Store
Constructing A DFD:
Several rules of thumb are used in drawing DFD’s:
1 Process should be named and numbered for an easy reference. Each name should be
representative of the process.
2 The direction of flow is from top to bottom and from left to right. Data traditionally
flow from source to the destination although they may flow back to the source. One way to
indicate this is to draw long flow line back to a source. An alternative way is to repeat the
source symbol as a destination. Since it is used more than once in the DFD it is marked with a
short diagonal.
3 When a process is exploded into lower level details, they are numbered.
4 The names of data stores and destinations are written in capital letters. Process and
dataflow names have the first letter of each work capitalized.
A DFD typically shows the minimum contents of data store. Each data store should
contain all the data elements that flow in and out. Questionnaires should contain all the data
.

elements that flow in and out. Missing interfaces redundancies and like is then accounted for
often through interviews.
.
IBD ASSET
MANAGEMEN
T SYSTEM
New allocation
details
Deployment
IBD HOD views
all branches
Respective
Branch HOD’s
views the report
Service head
enters the
instrument &
employee
Instrument
+
Employee
Branch- 1
service engineer
Super HOD
He can create
branches

FIG 4.2: CONTEXT LEVEL - 0 DIAGRAMS
.
USER
Verify Userid
and Password
USERS
MENU PAGE
in VDU
UserID
Password
If not found
USERS
If found

FIG 4.3: Context Level-0 Diagram for Login
.
Transactio
n
Employee
Instrument
New Allocation
Display
Change Allocation
Masters
Display

FIG 4.4: FIRST LEVEL DATA FLOW DIAGRAM
USECASE DIAGRAM:
.
USER
Verify Userid
and Password
USERS
MENU PAGE
in VDU
UserID
Password
If not found
USERS
If found

CLASS DIAGRAM:
.

4.3 Data Dictionary
After carefully understanding the requirements of the client then the entire data storage
requirements are divided into tables. The below tables are normalized to avoid any anomalies
during the course of data entry.
.

FIELD NAME DESCRIPTION
User Name It gives User Name
Password It takes Password
Serial No It gives the Serial number of the vehicle
Type of Vehicle It gives the type of vehicle
Vehicle Number It gives the vehicle number
No. of Seats It gives the number of seats
Date of Collect It gives the date of amount collected
Time It gives the time of the amount collected
Amount It gives the amount collected
Employ Id It gives the employ id
Employ Name It gives the employ name
Department It gives the name of the department
Shift It gives the shift of the employ
Place It gives the place where the culprint was caught
Fine It is the fine that is collected from the culprint
Vg No It is the vigilance number
Name It gives the name of the vigilance Employ
Designation It gives the designation of the employ
Deported To It gives the name of the Deported to place
Deported On It gives the name of the deported on place
.

CHAPTER-5
SYSTEM REQUIREMENTS
5. SYSTEM REQUIREMENTS
.

System requirements gives the idea about what are the necessary things that are needed
for proposed system, which plays very important role in development of any system. This
chapter deals with what are hardware components that are needed for the system, application
software that are required for the development and usage of the system.
The environment deals with the features of software. HTML is used as the front-end tool
and MY- SQL as a backend. Front end tools help to visualize the system through naked eyes
while back end helps in activities which are unseen to the end user.
5.1 System Specifications
HARDWARE REQUIREMENTS:
Processor : Intel Pentium IV and other greater versions
RAM : 512MB or Greater
Hard Disk : 80 GB Min
SOFTWARE REQUIREMENTS:
Operating System : Windows 2003 and other greater versions
Front-End : MICROSOFT VISUAL STUDIO 2010
Back-End : SQL SERVER 2008
Features of Software
Introduction to Microsoft Visual Studio:
.

Microsoft Visual Studio is an integrated development environment (IDE)
from Microsoft. It is used to develop computer programs for Microsoft Windows superfamily of
operating systems, as well as web sites, web applications and web services. Visual Studio uses
Microsoft software development platforms such as Windows API, Windows Forms, Windows
Presentation Foundation, Windows Store and Microsoft Silverlight. It can produce both native
code and managed code.
Visual Studio includes a code editor supporting IntelliSense as well as code refactoring.
The integrated debugger works both as a source-level debugger and a machine-level debugger.
Other built-in tools include a forms designer for building GUI applications, web designer, class
designer, and database schema designer. It accepts plug-ins that enhance the functionality at
almost every level—including adding support for source-control systems (like Subversion) and
adding new toolsets like editors and visual designers for domain-specific languages or toolsets
for other aspects of the software development lifecycle (like the Team Foundation Server client:
Team Explorer).
Visual Studio supports different programming languages and allows the code editor and
debugger to support (to varying degrees) nearly any programming language, provided a
language-specific service exists. Built-in languages include C,[5]
C++ and C++/CLI (via Visual
C++),VB.NET (via Visual Basic .NET), C# (via Visual C#), and F# (as of Visual Studio 2010).
Support for other languages such as M, Python, and Ruby among others is available via
language services installed separately. It also
supports XML/XSLT, HTML/XHTML, JavaScript and CSS.
Microsoft Visual Basic
Microsoft Visual Basic is Microsoft's implementation of the VB.NET language and associated
tools and language services. It was introduced with Visual Studio .NET (2002). Microsoft has
positioned Visual Basic for Rapid Application Development. Visual Basic can be used to author
both console applications as well as GUI applications. Like Visual C#, Visual Basic also
supports the Visual Studio Class designer, Forms designer, and Data designer among others.
Like C#, the VB.NET compiler is also available as a part of .NET Framework, but the language
services that let VB.NET projects be developed with Visual Studio, are available as a part of the
latter
.
Microsoft Visual Web Developer
Microsoft Visual Web Developer is used to create web sites, web applications and web
services using ASP.NET. Either C# or VB.NET languages can be used. Visual Web Developer
can use the Visual Studio Web Designer to graphically design web page layouts.
.

Visual Studio 2010
On April 12, 2010, Microsoft released Visual Studio 2010, codenamed Dev10, and .NET
Framework 4.
The Visual Studio 2010 IDE was redesigned which, according to Microsoft, clears the
UI organization and "reduces clutter and complexity." The new IDE better supports multiple
document windows and floating tool windows,[96]
while offering better multi-monitor support.
The IDE shell has been rewritten using the Windows Presentation Foundation (WPF), whereas
the internals have been redesigned using Managed Extensibility Framework (MEF) that offers
more extensibility points than previous versions of the IDE that enabled add-ins to modify the
behavior of the IDE.
The new multi-paradigm ML-variant F# forms part of Visual Studio 2010.
Visual Studio 2010 comes with .NET Framework 4 and supports developing
applications targeting Windows 7. It supports IBM DB2 and Oracle databases, in addition
to Microsoft SQL Server. It has integrated support for developing Microsoft
Silverlight applications, including an interactive designer. Visual Studio 2010 offers several
tools to make parallel programming simpler: in addition to the Parallel Extensions for the .NET
Framework and the Parallel Patterns Library for native code, Visual Studio 2010 includes tools
for debugging parallel applications. The new tools allow the visualization of parallel Tasks and
their runtime stacks. Tools for profiling parallel applications can be used for visualization of
thread wait-times and thread migrations across processor cores. Intel and Microsoft have jointly
pledged support for a new Concurrency Runtime in Visual Studio 2010 and Intel has launched
parallelism support in Parallel Studio as an add-on for Visual Studio.
The Visual Studio 2010 code editor now highlights references; whenever a symbol is
selected all other usages of the symbol are highlighted. It also offers a Quick Search feature
to incrementally search across all symbols in C++, C# and VB.NET projects. The Call
Hierarchy feature allows the developer to see all the methods that are called from a current
method as well as the methods that call the current one. IntelliSense in Visual Studio supports
a consume-first mode which developers can opt into. In this mode, IntelliSense will not auto-
complete identifiers; this allows the developer to use undefined identifiers (like variable or
method names) and define those later. Visual Studio 2010 can also help in this by automatically
defining them, if it can infer their types from usage. Current versions of Visual Studio have a
known bug which makes IntelliSense unusable for projects using pure C (not C++)
.

Introduction to MYSQL:
What is MySQL and why are we using it?
MySQL is a powerful Relational Database Management System (RDBMS) which we
will use to learn the basic principles of database and data manipulation using Structured Query
Language (SQL) statements. SQL is a database language that is used to retrieve, insert, delete
and update stored data. This is achieved by constructing conditional statements that conform to
a specific syntax (i.e. the strict order required of elements for a statement to work). Although it
is assumed that most people reading this know what a database and SQL are (if not necessarily
how to use them), there follows a little recap that it does no harm.
How does MySQL work?
MySQL is a database server program and as such is installed on one machine, but can
'serve' the database to a variety of locations. To explain MYSQL look at the following diagram.
.

The MySQL Server is installed on a Server and can be accessed directly via various
client interfaces, which send SQL statements to the server and then display the results to a user.
Some of these are:
A Local Client
A program on the same machine is the server. An example of this is the command line
MySQL client software we will be using in the rest of the MySQL workshops (although there
are other programs including graphical interfaces).
A Scripting Language – can pass SQL queries to the server and display the result.
A Remote Client - Program on a different machine, which can connect to the server
and run SQL statements. You can also use two more indirect methods.
Remote Login - You may be able to connect to the Server Machine to run one of its
local clients.
Web Browser - you can use a web browser and scripts that someone has written
(we're going to use this method for the rest of the workshop).
A bit about SQL
Structured Query Language is cross between a math-like language and an English-like
language that allows us to ask a database questions or tell it do things. There is a structure to
this language: it uses English phrases to define an action, but uses math-like symbols to make
comparisons. For example:
.

SELECT * FROM table;
Where 'SELECT', 'FROM' and 'table' are in English, but '*' is a symbol that means all. It
is important to learn SQL as it is common to almost all database programs and was developed
specifically as a language used to retrieve, add and manipulate data in databases. You will find
it not only here in MySQL, but underlying MS Access, MS SQL Server, and in every web-
based database application. While it may seem confusing at first it is almost like telling a story
or asking a question once you become comfortable with the syntax.
Creating a First SQL Statement
As we have yet to create a database it would be difficult to construct some simple SQL
statements to explain the above without first getting involved in some MySQL server
administration. However as we saw above there are many ways to interact with a database and
thus I have created a database and a 'cars' table filled with car info and provided a web browser
interface to accept SQL statements and return the results for you to experiment with.
The first SQL statement we will look at is the SELECT statement. The basic SELECT
statement has the following syntax.
SELECT columns FROM table [WHERE (condition)]
The WHERE condition is in square brackets as it is optional. So using our 'cars' table
we can start issuing commands and you should see the actual data being displayed.
A Tiny Bit about Operators
Operators are another tool that you can use within your SQL statement to refine your
search for specific records.
SELECT * FROM cars
WHERE ((cars. Year = '95-98')
.

AND (cars. Manufacturer = 'Volvo'));
The above statement uses the 'AND' operator (it can also be expressed as '&&') to
combine two conditions. Both conditions have to be met in order for the record to be displayed.
We can also use the 'OR' operator (can be expressed as '||' ) to ask for a record to be displayed if
either condition is met.
SELECT * FROM cars
WHERE ((cars. Year = '95-98')
OR (cars. Manufacturer = 'Volvo'));
The final operator we'll discuss here is the 'NOT' operator ('!' in case you were
wondering), which is a bit more complicated. Rather than joining conditions together it
becomes part of the condition, turning a positive into a negative. The following statement
retrieves all records that do not contain 'Volvo' as 'Manufacturer'.
SELECT * FROM cars
WHERE (cars.Manufacturer! = 'Volvo')
;
.

CHAPTER-6
SYSTEM DESIGN
.

6. SYSTEM DESIGN
6.1 Introduction
Design is the first step in the development phase for any system. It may be defined as the
“process of applying various techniques and principles for the purpose of designing a device, a
process, or a system”.
Software design is an iterative process through which requirements are translated into a
‘Blue Print’ for constructing the software. Preliminary design is concerned with the
transformation of requirements in to data and software architecture.
The design is a solution, a “how to” approach to the creation of a new system. This is
composed of several steps. It provides the understanding and procedural details necessary for
implementing the system recommended.
The database 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 implements flow of
information.
.

6.2 Design Principles
Basic design principles that enable the software engineer to navigate the design process
are:
 The design should be traceable to the analysis model.
 The design should minimize the intellectual distance between the software and the
problem, as it exists in the real world.
 The design should exhibit uniformity and integrity.
 The design should be structured to accommodate changes.
 The design is not coding, the coding is not a design.
 The design should be reviewed to minimize the conceptual errors.
6.3 Database Design
The goal of database design is to generate a set of relation schemes that allow us to store
information without necessary redundancy and allows us to retrieve information easily. We can
achieve optimization, ease of use in which data is stored in the form of tables and there exists a
relation between or among tables. The design objectives must be:
 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.
6.3.1 Normalization
Normalization of relation schema is done to eliminate insertion and deletion anomalies
that exist in databases. Normalization is a step-by-step reversible process of converting given
collection of relations to some desirable form in which the relations have a progressively
simpler and regular structure. The objectives of Normalization are:
.

 To make it feasible to represent any relation in the database.
 To obtain powerful retrieval algorithms based on a simpler collection of relational
operations.
 To free relations from undesirable insertions, update and deletion dependencies.
 A relation R is said to be in 1NF if all underlying domains contain atomic values
only.
 A relation R is said to be in 2NF if and only if it is in 1NF and every non-key
attribute is non-transitively dependent on the primary key.
 A relation R is said to be in 3NF if it is in 2NF and its non-key attribute is non-
transitively dependent on its primary key.
 All the tables that have been designed for developing this system follow 2nd
Normalization form.
6.3.2 Database Tables
Table Name: Login Table No: 6.3.2.1
Field Name Data Type Description
Username Varchar Username
Password Varchar User password
Lstatus Varchar Login status
Branch Varchar Branch name
Region Varchar Region name
.

Table Name: Instrument Table No: 6.3.2.2
.
Sno Number Serial number
Imtno Varchar Imt number
Mfno Varchar Manufacturing
number
Ast Varchar Asset type
Ides Varchar Instrument
description
Imake Varchar Instrument make
Mdate Varchar Manufacturing date
Branch Varchar Branch received on
Bname Varchar Branch name

Table Name: Employee Table No: 6.3.2.3
Ecode Varchar Employee code
Ename Varchar Employee name
Mail Varchar Employee mail id
Dept Varchar Department name
Role Varchar Role
Company Varchar Company name
Type Varchar
Branch name Varchar
Table Name: Asset History Table No: 6.3.2.4
Imtno Varchar Imt number
Manfno N Varchar Manufacturing
number
Asset type Varchar Asset type
Instrument Desc Varchar Instrument description
Instrument Make Varchar Instrument make
Manf Date Varchar Manufacturing date
Res Varchar Resolution
Empcode Varchar Employee code
Empname Varchar Employee name
Emptype Varchar Type
Empmail Varchar Mail id
.

Ncdate Varchar Next calibration date
Lcdate Varchar Last calibration date
Adate Varchar Asset issued date
6.4 User Interface Design
User Interface design focuses on three areas of concern,
 The design of interfaces between software module and internal interface.
 The design of interface between the software and other external entities like non-
human producers and consumers of information-external interface.
 The design interface between a human (i.e. user) and the computer.
CHAPTER-7
SYSTEM TESTING
.

7. SYSTEM TESTING
Testing is the process of detecting errors. Testing performs a very critical role for quality
assurance and for ensuring the reliability of software. The results of testing are used later on
during maintenance also.
Psychology of Testing
The aim of testing is often to demonstrate that a program works by showing that it has
no errors. The basic purpose of testing phase is to detect the errors that may be present in the
program. Testing is the process of executing a program with the intent of finding errors.
Testing Objectives
.

The main objective of testing is to uncover a host of errors, systematically and with
minimum effort and time.
 Testing is a process of executing a program with the intent of finding an error.
 A successful test is one that uncovers an as yet undiscovered error.
 A good test case is one that has a high probability of finding error, if it exists.
 The tests are inadequate to detect possibly present errors.
Levels of Testing
The basic levels of testing are
.
Client Needs Acceptance Testing
Requirements System Testing
Design Integration Testing
Code Unit Testing

7.1 White Box Testing
This is a unit testing method where a unit will be taken at a time and tested thoroughly at
a statement level to find the maximum possible errors.
I tested step wise every piece of code, taking care that every statement in the code is
executed at least once. The white box testing is also called Glass Box Testing. I have generated
a list of test cases, sample data which is used to check all possible combinations of execution
paths through the code at every module level?
7.2 Black Box Testing
This testing method focuses on the functional requirements of the software. Here each
module will be treated as a black box that will take some input and generate output. Output for a
given set of input combinations are forwarded to other modules. Black box testing attempts to
find the following types of errors:
 Incorrect or missing functions.
 Interface errors.
 Errors in data structures or external database access.
.

 Performance errors
 Initialization errors and termination errors.
All the forms have been executed and verified .Based on some sample input data, the
generated output is verified whether the system is providing better results or not.
7.3 Unit testing
Unit testing focuses on the verification of code produced during coding phase and hence
the goal is to test the interface in order to ensure that information property flows in and out of
the program under unit test. In this project each service can be thought of a module. There is a
module called login module. The inputs are validated while accepting from the user. Each
screen has been taken a control and tested by giving different sets of inputs. The inputs are
validated when from the User Interface User Entry Form
Text Box1: Here the text box will allow first letter as a character and next values may
be special characters.
Text Box2: Here this text box property as a Password and it allows any special
characters greater than 6 letters.
7.4 Integration Testing:
The goal here is to see whether the modules are integrated properly, the emphasis being
on testing interfaces between modules. This testing activity can be considered as testing the
design and hence the emphasis on testing module interactions. In this project the main system is
formed by integrating all the modules. When integrating all the modules I have checked whether
the integration effects working of any of the services by giving different Combinations of inputs
with which the two services run perfectly before Integration.
.

For Example of Integration testing this Administration module may allow the user to
enter from user entry form and opens MDI form to all related forms and it will ends with
appropriate operations on that form.
7.5 Validation Testing:
Validation testing demonstrates tractability of software requirements. Validation
succeeds when the software functions in expected manner. The major elements of this process
are alpha and beta testing along with configuration reviews.
In the present system, validations are been written for Work code entry, Name entry and
proper error messages are displayed when any validation error occurs. Validation’s such as a
Text Field should accept only Character data but not any other Characters. Thus, in the present
system, Proper validations is been written where it is found to be necessary. Validation such as
eliminating Duplicate values is performed.
.

CHAPTER-8
IMPLEMENTATION
8. IMPLEMENTATION
Implementation is the process of converting a new or revised system design into an
operational one. Apart from planning, the major tasks of preparing for implementation or
education and training of users. Implementation includes following activities:
.

 Obtaining and installing the system 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
 Evaluating the operation and use of the system
Implementation Methods
There are four basic methods of implementation:
 Direct conversion
 Parallel conversion
 Pilot conversion
 Phasing conversion
Parallel Conversion:
Description: In this method, the old system is operated along with the new system.
Advantages:
This method offers greatest security. The old system can take over if errors are found in
the new system or if some usage problems occur.
Disadvantages:
.

This method doubles operating costs also the new system may not get fair trial. The
Present system “IBD Asset Management System” has been done by using Parallel Conversion
in which the old one is replaced with the newly developed system. In this method, we can run
both the systems and we can decide which method to follow based on results. Finally we used
the Parallel Conversion both Existing and Proposed system.
.

CHAPTER-9
CONCLUSION
9. CONCLUSION
The present “IBD ASSET MANAGEMENT SYSTEM” has been developed effectively
in such a way that it meets all the criteria that are expected by the user and in future, if any
.

further enhancements are required by the user, then it can be done with minimal coding. It has
the following features:
 The project has been appreciated by all the users in the organization.
 It is easy to use, since it uses the GUI provided in the user dialog.
 User friendly screens are provided.
 The usage of software increases the efficiency, decreases the effort.
 It also provides the user with variable options in customizing the Ads.
 It has been thoroughly tested and implemented.
 Transactions are updated and processed immediately
 Portable and it allows further enhancements
 Simplified operation and increase productivity
 Easy to operate
 Less processing time and high performance
After developing the system, it has been tested with sample data and the results are
found to be satisfactory. The input screens are user friendly, reducing user strains and
inconsistency during data entry. It also provides all necessary reports.
.

CHAPTER-10
ADVANCEMENTS
10. ADVANCEMENTS
Our project, IBD Asset Management system can also be used for further
implementations to Amara Raja Batteries Limited (ARBL) such as:
.

 Vehicle Management System
 Goods Transport Management System
 Workshop Management System
1. VEHICLE MANAGEMENT
The Vehicle Management system can store the count of all vehicles in the company and
updating the database regarding the information of how many vehicles are in service and how
many are going out of the company.
2. GOODS TRANSPORT MANAGEMENT
The Goods Transport Management System is helpful to the service engineers to know
how many batteries or goods are in the company, manufacturing dates for the goods and also to
know which goods are being exported from the company and imported into the company.
3. WORKSHOP MANAGEMENT
Workshop Management System can store the information of the machines used in the
company such as, the count of the machines in each department of each branch and which
machines are in the use etc.
.

CHAPTER-11
APPENDICES
11. APPENDICES
.

Appendix-A User Manual
The user manual provides an environment that helps the users to understand about the
each form to operate.
 Screen 1: Login form.
 Screen 2: Titles
 Screen 3: Instrument Master
 Screen 4: New Allocation
 Screen 5: Change Allocation
 Screen 6: Add new staff
 Screen 7: Reports
Appendix-B Test Screens
.

Basic visual studio screen:
Screen 1: Login form
.

Screen 2: Titles
.

Screen 3: Instrument Master
.

Screen 4: New Allocation
Screen 5: Change Allocation
.

Screen 6: Add new Staff
Screen 7: Reports
.

Appendix-B Sample Code
.

LOGIN
Titles
.

Instrument Master
.

New Allocation
.

Add new Staff
.

Change allocation
.

Reports
.

CHAPTER-12
BIBLIOGRAPHY
.

12. BIBLIOGRPAHY
References:
Book References:
[1] Jiawei Han and Micheline Kamber. “Data Ware Housing and Data Mining. Concepts
and Techniques”, Third Edition 2007.
[2] P. Raghu Rama Krishnan, “Accessing Databases with JDBC and ODBC”, Pearson
Education, Fourth Edition.
[3] Henry F Korth, S. Sudharshan, “Database System Concepts” McGraw – Hill,
International Editions, Fourth Edition, 2002.
[4] “Microsoft visual studio” for basics ,fourth edition,2008
Web References:
[1] http://www.visualstudio.com
[2] http://www.mysql.com/
[3] http://www.microsoft.com
[4] http://en.wikipedia.org/
.

Manage IBD Assets Efficiently

Recommended

Recommended

More Related Content

What's hot

What's hot (16)

Viewers also liked

Viewers also liked (9)

Similar to Manage IBD Assets Efficiently

Similar to Manage IBD Assets Efficiently (20)

Manage IBD Assets Efficiently