Essay: Assets Tracking System

INTRODUCTION
2.1 PROJECT DEFINITION
Assets Tracking System is Web-based application. It can be used as plug-in for any ERP system. Assets Tracking System is an application to manage the records of all the assets of an organization.Simple but very essential application for any organization. The conventional model of system was having only modules to keep track records of Assets in the organization. But we are going to upgrade the system by including few new modules to provide more user friendliness & more effectiveness to the client. The calibration management system primarily helps to keep track records of the assets of the organization. The act of checking or adjusting the accuracy of a measuring asset.
The system at the same time enables you to calculate depreciation & also enables you to find out the cost, accumulated depreciation & value of asset at the time of sale.
2.2ABSTRACT
Asset Tracking System is one of most valuable web based system for any organization to improve their productivity. This system is useful for our industry.
It is a web-based application that was developed using object oriented approach while NET BEANS 7.1.2 with JSP issued as a programming language, MY SQL is for database, Microsoft visual studio 2008 as an editing tool for database.
Through its Tracking System, activities of procurement through management of asset can be administered online which have user categories such as System Administrator, Super administrator, Regular user and vendor.
It is the method that a company uses to track movable assets, for example factory equipment, desks and chairs, computers. the accurate details of the task differ from company to company, asset management also includes mapping the physical location of assets, managing demand for scarce resources and accounting tasks such as amortization.
The Asset management is used to mean the comprehensive management of asset demand, planning, procurement, operation, maintenance, rehabilitation, disposal and replacement to maximize the overall performance of company.
FRONT END : Net beans 7.1.2
BACK END : My SQL
EXTERNAL GUIDE INFORMATION: NILESH PANDYA
COMPANY NAME : DEV INFOTECH
DESIGNATION : PROPRIETOR
MOBILE NO. : 9033001023
EMAIL ID : info@deveducation.org
ADDRESS : VIP ROAD,
KARELIBAUG,
VADODARA
2.3 PURPOSE AND OBJECTIVE
2.3.1 PURPOSE
• The purpose of asset management system is to provide a tool for the general leader department, keep comprehensive control over any physical or movable asset.
• To establish the responsibilities, process and procedure to enter asset’s information like asset’s allocation information, overall performance of assets, depreciation information, purchasing information.
• To develop intranet system for company so that different users in different departments can show the details about any asset.
• To set up the communication between the users in different departments.
• To maintain shop floor history card, break down analysis and cost analysis
• It reduces manual task, increase portability and profit margin to greater extent.
2.3.2 OBJECTIVE
The system revolves around assets as the main entity. Hence, the foremost objective of the system is to satisfy the needs of employee as well as management.
Following are other related company’s objectives:
• To facilitate improved and fast allocation and view the assets position.
• To maintain consistent assets base.
• To retain existing assets information.
• Acquiring new assets using Place order to vender.
• Fast and efficient problem solving of employee through complaint and feedback mechanism.
• Access to assets account history, order information, and employee information at all touch points.
• To lower communication and servicing expenses.
• Be able to pursue a strategy of relationship marketing.
• To cross transfer of assets more effectively.
• To increase assets scrap as a result of enhanced system.
• To generate organized and proficient analysis of system workflow.
2.4 MODULE DESCRIPTION AND PROCESS LOGIC
1. ADMIN
• The role of admin revolves in managing and distributing the information within a system.
• Its task is to do all the system management in an organization.
2. EMPLOYEES
• This includes the categories of employees like technician,basicemployees,manager(sales manager),clerk,etc whose task is to give order for repairing of particular items
Or place an order for the items or assets which are required for them or company.
3. ITEMS/ASSETS
• This includes various items of company like computer,A.C,chair,table,fan,etc.
• This also have subcategories like for eg. Computer have subcategories like laptop and desktop. A.C includes split,1 ton,0.5,1.5,2.5 ton ,etc.
4. PURCHASE
• The employees of the company place an order for purchasing of particular assets or items.
5. COMPLAIN
• The company complains for the particular items based on warranty and guarantee.
6. VENDOR
• Its role is for selling the materials/items/assets to a company according to their requirements.
Chapter 3:PROJECT PLANNING
3.1 SCOPE:
The scopes are defined as the boundary of the project in term of functionality,
data, benefits and user.
Functionalities
• Login and logout with access level for preventing illegal access to valuable Information.
• Preparing the environment by enabling the activities that would be performed online.
• Creating and storing of a procurement and asset information.
• Searching, viewing and listing of procurement and asset information.
• Updating and deleting of procurement and asset information.
• Locating the placement and movement of asset at site.
• Keeping a inspection record.
• Updating scrap information.
• Supplier can submit and view the relevant information required by online.
• Depreciation can be calculated regularly so that to purchase any expensive asset in future, the required fund will be saved in advance.
• System performs calibration or checks performance of machine regularly to prevent from big loss.
Benefits
 Web Based, Industry Standards.
• Completely Web Based – only a Web Browser is needed toManage assets.
• Easily Accessible on your network.
• Industry Standard Architecture (SQLand Net Beans).
• No Additional Hardware Required (can typically be installed on Existing servers
 User Defined Fields
• User Defined Fields – Allows tracking of any information related to the Asset (i.e. purchase order number, purchase date, serial Numbers, contract numbers, etc.).
 Completely Configurable Asset Views
• Custom Asset List Views – each admin user can configure his own.
• Asset list view.
 Asset Descriptions
• Asset Code/Tag Number ability to auto generate unique, sequential asset code numbers or manually assign codes/numbers
• Asset Image – a picture/image can be uploaded and displayed in the asset detail view.
• Asset Notes – add notes (tracks note date/time and user)
• Attachments – any type of file (i.e. scanned purchase orders, warranty Information, service agreements, drawings, pictures, Technical specifications, etc.) can be attached to an asset. An asset can have multiple attachments.
 Security Groups, Permissions & Assignments
• Administrative User Security Groups and Roles – ability to assign an Administrative user to one or more groups with a unique role (i.e. Edit, View Only, etc.)
• Permission Based Assets – ability to assign the “ownership” of assets to an administrative group. This allows different groups in an organization to manage their own set of assets.
• Asset Associations/Assignments – associate/assign an asset to internal employees or departments.
Users
• Users are divided into several categories and will have different access levelwhen using the system. Among of them are system administrator, super administrator, register user, technician.
3.2 PROCESS MODEL:
Project Development Approach And Justification (SDLC Model)
We are following spiral model for developing our system.Spiral model combines the advantages of top-down and bottom-up concepts. Hence, we are using this model due to its following reasons:
• Our system needs continuous development. We will describe the characteristics with high priority first and then develop a prototype based on these. This prototype will be tested and desired changes will be made in the new system. This continual and steady approach will minimize the risks or failure associated with the change in the system.
• We will be developing the system in small segments that will make it easier to do cost calculations.
• The client will be involved in the development of each segment and retains control over the direction and implementation of the system.
Spiral Model
3.3 PROJECT TEAM ORGANIZATION:
Proper project team organization is one of the key constraints to project success. If the project has no productive and well-organized team, there’s an increased probability that this project will be fail because initially the team is unable to do the project in the right manner. Without right organization of teamwork, people who form the team will fail to perform a number of specific roles and carry out a varieties of group/individual responsibilities.
Name of Internal Guide :Ms.. Mala H. Mehata
Name of Partners : Shramika N. Gour
Keya U. Ghandhi
A Project Team is an organized group of people who are involved in performing shared/individual tasks of the project as well as achieving shared/individual goals and objectives for the purpose of accomplishing the project and producing its results.
The best team structure depends on the Management style. Team Structures are of three types:
1. Democratic Decentralized, 2. Controlled Decentralized, 3. Controlled Centralized.
Our team organization is Democratic Decentralized. There is no leader in our team. We have divided our work as per interest. The modules of our project are divided among us as per the interest so that the work will be completed effectively. So we have chosen Democratic Decentralized team organization.
3.4 FRONTEND AND BACKEND:
• Front-end : Net beans 7.1.2
• Back-end : My SQL
• Environment : Net Beans
• Documentation : Microsoft Office Word 2007
• Presentation : Microsoft Office PowerPoint 2007,
Crystal Report
• VISIO-2003 : Different types of Diagram
3.5 PROJECT SCHEDULE CHART:
1. Task Aug Sep Oct Nov Jan Feb
To To To To To To
Sep Oct Nov Dec Feb Apr
System Analysis System Analysis
Planning Planning
Risk Analysis Risk Analysis
Engineering Engineering
Construction & Release Construction & Release
System Evaluation System Evaluation
Project Plan.
Chapter 4: SYSTEM ANALYSIS
4.2 Feasibility Study
Preliminary investigations examine project feasibility. Three tests of feasibility-all equally important –are studied: operational, technical and financial.
4.2.1 Technical Feasibility
There are number of technical issues which are generally raised during the feasibility stage of investigation. The technical feasibility involves the study about the availability of the tools required for the proposed system. Here the tools involve the hardware required for the development and the implementation of the system. The technical needs of the system may vary considerably, but might include:
 The facility to produce output in a given period of time.
 Response time under certain conditions.
 Ability to process a certain volume of transaction at a particular speed.
 Facility to communicate data to distant location.
4.2.2 Operational Feasibility
Proposed projects are beneficial only if they can be turned into information systems that will meet the organization’s requirements. To know whether system will work when implemented, here are some points we will look when we market the product:
• Are current methods of business acceptable to users? If not they might welcome the change.
• We will try to involve users as much as possible through training to reduce chances of resistances.
Most importantly assessment is done to assure that the proposed system will not cause harm or poor results in any respect or area and will not slow performance of any individual or organization.
4.2.3 Financial and Economic Feasibility
A software product needs to be a good investment for the organization. Financial benefits must equal or exceed the costs. We are examining the Costs of Other Multilevel system before and after installation of Textile Multilevel System. Also as for development cost we have sufficient programming Tools and knowledge base available.
4.2.4 Schedule Feasibility
Projects are initiated with specific deadline. We need to evaluate whether the deadlines are mandatory or desirable. Time is the one of the critical factor in the development of any system but this kind of feasibility is hardly perfect in any system.
We have been asked to complete the project within the working days of the organization having period of 5-6 months approximately. So we have managed to complete the project before given deadline. In this project planning section we have elaborate our ideas to develop the system within the given period.
4.3 SYSTEM REQUIREMENT ENGINEERING
4.3.1 REQUIREMENT ANALYSIS
STUDY OF CURRENT SYSTEM
In the current Assets Tracking System first of all the software is registered i.e., it is installed in the network of the company. Then all the employees working in then organization are registered according to the designation. Then the information about the current assets and the new asset which are bought by the organization is feed into the database of the system, which consist of asset id, vendor, manufacturing date, price, etc. Then, the asset is allocated by the super admin to the admin of various departments and the admin allocates to employees subsequently. After that if there is any problem in the asset, and then the vendor is called for servicing. All the services given by the vendor i.e. pre purchase and post purchase services are recorded in the system, based on which the vendor is observed. If the vendor is not giving proper and timely services then the higher authorities of the organization are provided the facilities to blacklist such a vendor for better decision making in the future.
REQUIREMENTS OF NEW SYSTEM
The industry faces the problem of maintaining asset information properly. They do not have any maintenance system. So, they want to develop a Web based Assets Tracking System that simplifies asset profiling and documentation, collection, and depreciation, for assets including hardware, software, furniture, machinary and telephony.
Through Assets Tracking System, organizations can quickly search through their asset inventories, with features for filtering and sorting by asset type, assignment, model and more. There are obvious benefits from implementing and maintaining a record and control over assets. Savings can be obtained from being able to both see current asset deployment and thereby maximizing their use. In some cases a system is mandated by government regulations, terms of lending, public grant terms, insurance terms etc. One person can maintain and manage all fixed assets of a business if they have software to assist them. Computer systems and software available reduce complexity, save time and prevent mistakes.
User Requirements
• To allow minimum inputs by the user so that any user of the company can access the system with ease.
• To allow the user to keep a track of the status of the complain entered and details of assets.
• The system should be understandable, easy, user friendly and efficient enough to perform the required functions.
Registered User
• The user should have a valid username and password to login into the system.
• He/she should be allowed to change the password.
• Super Administrator: They have highest priority among all the users. They give approval or disapproval for any major problem only.
System Requirement
Hardware and Software Requirements
Hardware requirement
Component Minimum requirements
Micro processor Pentium-1.6 GHz
RAM 2 GM MB RAM
HDD 20 GB HDD(Free)
Mouse Any mouse
Monitor 15”color monitor
Printer For print report and bills.
Software Requirement
Operating System Windows 9x or above
Front End JSP with NetBeans
Back End SQL Server 2008
4.3.2 Requirement Specification
Functional Requirements
Functional requirements are the requirements, which are specified by the user. This type of requirement is necessary for the system to work as a user’s need. This requirement represents functional behaviour of the system.
We have the system that is divided into four modules and each user can have access to the system part based on the role he is playing.
Main Functionality
• REGISTRATION FOR NEW USER:
The administrator enters employee information in the system and also grants permission to make customer account.
• ROLLBACK PRIVILEGES OF USERS:
The authority to grant and revoke the rights to the user is in the hands of administrator.
• ADDING NEW PRODUCT INFORMATION:
The administrator will enter the product details so that the information related to the product can be available when customers need to buy them.
• UPDATING PRODUCT INFORMATION:
Whenever there are some changes in the existing products features or rates, then the administrator can update the details of the product in the database.
• VIEW/ANALYZE REPORTS ON PERIODICALLY BASIS:
The administrator can request for various marketing, sales and support related reports for analysis purpose. This helps to improve the service from time to time.
Non-functional Requirements
Non Functional Requirements are the Requirements, which are not explicitly stated by the user. This type of requirement enhanced the quality of software. These types of requirements are common and without it, it’s difficult to handle the system.
• SYSTEM WILL HAVE CONSISTENT AND FRIENDLY USER INTERFACE:
We have tried to design the user-interface in such a way that it is very easy for novice and casual users to interact with system. Suppose any user makes mistake, the system will provide an appropriate error message that will guide the user for the further interaction.
• SYSTEM WILL BE PORTABLE:
The system is implemented using visual studio 2008. Therefore it is operating system independent and the client does not require to install any additional hardware or software. Thus system is portable.
• EACH MODULE WILL BE INTEGRATED WITH EACH OTHER:
Data, control and information flow between each and every modules of the system and they communicate with each other and tightly integrated.
• EVERY HISTORY DATA WILL BE RETRIEVABLE IN THE FORMAT OF PRINTED REPORT OR IN ANY OTHER FORMAT:(HTML DOCUMENT, PDF FILES, ETC.)
The system consists of analysis module that periodically generates reports and dashboards based on historical data which will be in any format specified above that will be useful to the analyst for forecasting and decision making.
Other features are: System will have security feature to avoid any kind of security breach and the data access of the system will be very fast and accurate.
4.3.3 Software Quality Constraints:-
These are constraints on the services or functions offered by the system.
1. Speed
 Time taken to add, search and retrieve data should be minimum.
2. Ease of use
 The system must provide a unique and easy user interface. The interface should also be attractive and should have a professional look. The System should be user-friendly.
3. Reliability
 The system should be 100% reliable because it deals with one of the most important resource of the company i.e. information.
4. Robustness
 The system should be highly robust and must not lead to any loss or corruption of data.
Chapter 5: SYSTEM DESIGN
Design Principles
Object-Oriented Modeling, or OOM, is a modeling paradigm mainly used in computer programming. The Object-Oriented paradigm assists the programmer to address the complexity of a problem domain by considering the problem not as a set of functions that can be performed but primarily as a set of related, interacting Objects. The modeling task then is specifying, for a specific context, those Objects (or the Class the Objects belongs to), their respective set of Properties and Methods, shared by all Objects members of the Class.
Reason for Selection
We have selected the Object Oriented Design Methodology for developing our system because of the following reasons:
 Code and design reuse is maximum
 It results in increased productivity
 Ease of testing and maintenance
 Better code and design understandability
 Better problem decomposition
 It encourages a high degree of modularity in programming, making large projects easier to implement
 It provides powerful techniques like inheritance and polymorphism to help organize and reuse code
5.1 ER Diagram:
5.2 Class Diagram:
The class diagram is a static diagram. It represents the static view of an application. Class diagram not only used for visualizing describing and documenting different aspects of a system but also for constructing executable code of the software application.
5.3 USECASE DIAGRAM:
5.4 Sequence diagram
Sequence diagram isalso called INTERACTION DIAGRAMS. An interaction diagram shows an interaction, consisting of set of objects and their relationship including the messages that may be dispatched among them. A sequence diagram is an introduction that empathizes the time ordering of messages. Graphically a sequence diagram is a table that shows objects arranged along the X-axis and messages ordered in increasing time along the Y-axis.
ADMIN:
EMPLOYEE
TECHNICIAN
VENDOR
ADMIN-TECHNICIAN-EMPLOYEE
ADMIN-VENDOR INTERFACE:
5.5Activity Diagram:An activity diagram shows the flow from activity to activity. An activity is an on-going non-atomic execution within a state machine.
Activity states and action states
• Transitions
• Objects
ACTIVITY FOR ADMIN:
Login
Change Password
Forgot Password
ACTIVITY FOR EMPLOYEE:
ACTIVITY FOR TECHNICIAN:
ACTIVITY FOR VENDOR:
5.6 Databse Design:
DATA DICTIONARY
Table Name :DeptMst
Referred as : Department master
FIELD TYPE SIZE DESCRIPTION Constraint
DeptId Int Department Code Primary Key
DeptName Varchar 20 Department Name Unique
Table Name :DesiMst
Referred as : Designation master
FIELD TYPE SIZE DESCRIPTION Constraint
DesiId Int Designation No Primary Key
DesiName Varchar 20 Designation Name Unique
Table Name :StateMst
Referred as : State Information
FIELD TYPE SIZE DESCRIPTION Constraint
StateId Int State Identification Primary Key
StateName Varchar 20 State Name Unique
Table Name :CityMst
Referred as : City Information
FIELD TYPE SIZE DESCRIPTION Constraint
CityId Int City Identification Primary Key
CityName Varchar 20 City Name Unique
StateId Int State Identification Foreign Key
Table Name :QuestoinMst
Referred as : Question Information
FIELD TYPE SIZE DESCRIPTION Constraint
Qid Int Question Identification Primary Key
Qdesc Varchar 20 Question Description Not Null
Table Name :EmployeeMst
Referred as : Employee Information
FIELD TYPE SIZE DESCRIPTION Constraint
EmpId Int Employee Identification Primary Key
EmpName Varchar 30 Employee Name Not Null
AddressLine1 Varchar 30 Address Line Not Null
AddressLine2 Varchar 30 Address Line Not Null
StateId Int State Identification Foreign Key
CityId Int City Identification Foreign Key
Pincode Int Pincode of Area Not Null
ContactNo Varchar Contact No of Employee Not Null
EmailId Varchar 40 Email Id of Employee Not Null
Deptid Int Department Id Foreign Key
DesiId Int Designation Id Foreign Key
Qid Int Question Id Foreign Key
Answer Varchar 40 Answer of Question Not Null
Image Varchar 100 Path of Image Not Null
UserName Varchar 30 User Name of Employee Unique
Password Varchar 30 Password of Employee Not Null
 
Table Name :VendorMst
Referred as : Vendor Information
FIELD TYPE SIZE DESCRIPTION Constraint
Vid Int Vendor Identification Primary Key
Vname Varchar 30 Vendor Name Not Null
AddressLine1 Varchar 30 Address Line Not Null
AddressLine2 Varchar 30 Address Line Not Null
StateId Int State Identification Foreign Key
CityId Int City Identification Foreign Key
Pincode Int Pincode of Area Not Null
ContactNo Varchar Contact No of Vendor Not Null
EmailId Varchar 40 Email Id of Vendor Not Null
Deptid Int Department Id Foreign Key
DesiId Int Designation Id Foreign Key
Qid Int Question Id Foreign Key
Answer Varchar 40 Answer of Question Not Null
Image Varchar 100 Path of Image Not Null
UserName Varchar 30 User Name of Vendor Unique
Password Varchar 30 Password of Vendor Not Null
Table Name :Assetscat
Referred as : Assets Category
FIELD TYPE SIZE DESCRIPTION Constraint
ACatId Int Assets Identification Primary Key
ACatName Varchar 30 Assets Name Unique
Table Name :AssetsSubcat
Referred as : Assets Sub Category
FIELD TYPE SIZE DESCRIPTION Constraint
ASubCatId Int Assets Sub Identification Primary Key
ASubCatName Varchar 30 Assets Sub Cat Name Unique
ACatId Int Assets Cat Identification Foreign Key
Table Name : Assets
Referred as : Assets Information
FIELD TYPE SIZE DESCRIPTION Constraint
AID Int Assets Identification Primary Key
AssetsName Varchar 30 Assets Information Not Null
ASubCatId Int Assets Sub Cat Identification Foreign Key
Description Varchar 100 Assets Category Not Null
Table Name :RequirementMst
Referred as : Requirement Identification
FIELD TYPE SIZE DESCRIPTION Constraint
ReqId Int Requirement Identification Primary Key
ReqDate Varchar 40 Requirement Date Not Null
EmpId Int Employee Identification Foreign Key
Aid Int Assets Id Foreign Key
Qty Int Requirement Quantity Not Null
ReqDesc Varchar 50 Requirement Description Not Null
Status Varchar 50 Status of Requirement Not Null
Table Name :VendorSupplyMst
Referred as : Vendor Supply Info
FIELD TYPE SIZE DESCRIPTION Constraint
VID Int Vendor Id Foreign Key
AID Int Assets Id Foreign Key
Rate Float Amount of Assets Not Null
Table Name :OrderMst
Referred as : Order Information
FIELD TYPE SIZE DESCRIPTION Constraint
OID Int Order Id Primary Key
OrderDate Date Order Date Not Null
VID Int Vendor Id Foreign Key
AID Int Assets id Foreign Key
Qty Int Assets Quantity Not Null
Rate Float Rate of Assets Not Null
Amount Float Amount of Assets Not Null
Table Name :InwardMst
Referred as : Inward Information
FIELD TYPE SIZE DESCRIPTION Constraint
InwardId Int Inward Id Primary Key
Indate Date Inward Date Not Null
OrderId Int Order Id Foreign Key
AID Int Assets Id Foreign Key
TAG Varchar Tag of Assets Not Null
Cost Float Cost of Assets Not Null
DepRate Float Cost of Depriciation Not Null
WType Varchar 40 Warranty Type Not Null
WEndDate Date Warranty Date Not Null
Table Name :AllocationMst
Referred as : Assets Allocation Information
FIELD TYPE SIZE DESCRIPTION Constraint
Aid Int Allocation Id Primary Key
Adate Date Allocation Date Not Null
ReqId Int Requirement Id Foreign Key
EmpId Int Employee Id Foreign Key
Location Varchar 40 Assets Location Not Null
GPSCode Varchar 40 Location Not Null
Table Name :ComplaintMst
Referred as : Complaint Information
FIELD TYPE SIZE DESCRIPTION Constraint
Cid Int Complaint Id Primary Key
CDate Date Complaint Date Not Null
EmpId Int Employee Id Foreign Key
AID Int Assets Id Foreign Key
ComplalintDesc Varchar 50 Complaint Info Not Null
Status Varchar 50 Complaint Status Not Null
ActionTaken Varchar 50 Complaint Action Not Null
ActionTakenBy Int Technician Id Foreign Key
CHAPTER 6 PROGRAMMING FUNDAMENTALS
Why Visual Studio & JSP?
o Parallel Development
Microsoft now provides an environment that will help do this through Visual Studio IDE support for Parallel development and Native c++ libraries and compiler support for parallel applications.
o Coding Improvements
A new editor uses Windows Presentation Foundation technology to provide integrated support that helps you understand your code.
o Web Development
A new set of JSP NetBeans tools allows developers to build Model- View-Controller (MVC) based websites.
o Graphical Development Environment
Visual Studio provides a very rich development environment for Web
developers. You can drag and drop controls and set properties the way you do in Visual Basic 6. And you have full IntelliSense support, not only for your code, but also for HTML and XML.
Why JSP?
Advantages over C and C++
o Automatic garbage collection.
o Pointers no longer needed (but optional).
o This is much cleaner and less error prone.
o Usually it is much more efficient than any other languages.
Chapter 7: SCREEN LAYOUTS OR USER MANUAL
HOME PAGE:
LOGIN PAGE:
Required input and Expected output:
LOGIN TEST:
• Valid login:
• Invalid login:
REGISTRATION TEST:
CHANGE PASSWORD TEST:
Forgot password:
Change password:
PROJECT FLOW:
1) EMPLOYEE :Employee will login/register and makes a request for the scarce materials / assets as per the need and will logout.
2) ADMIN: Admin will login and will view a request made by employee.
• Admin will confirm/reject the request made by employee as per availability.
• If the request is confirmed that it will be forwarded to purchase department.
• Then it will forward to the inward department for checking inventory.
• It will allocate the material/assets to the respective employee.
3) EMPLOYEE: Employee will login and view its allocated request.
• If the employee found any fault or damage in the material then it will generate a complain.
4) TECHNICIAN:Technician will view the complain genertaed by the employee and will confirm/scrap the material as per the requirement. Here for e.g. Technician has scraped the material so it will deallocate it from employee side.
5) EMPLOYEE: Deallocation of the asset is done on employee side, If material is scrap.
6) ADMIN:Admin will also view the complain status.
• Admin will view scrap details.
A LIMITATIONS AND FUTURE ENHANCEMENTS
Limitations of the System are:-
 The Database of our system will keep on growing and becoming heavier as new users keep on getting registered in the system.
 ATS performance is bound to network speed. If the network goes down or there is congestion in network than it will cause a poor performance while tracking with GPS.
 A centralized server means clients always need network access.
 Security restrictions may cause you trouble.
Future Enhancements of the System are:-
• The system has been designed at the maximum possible excellence. Still we accept drawbacks, as it is a human effort.
• The system cannot provide the SMS integration. Hence, it can be modified to give the SMS/email integration. Admin can contact with both user and company through message or email. Employee and company can also send message to admin.
• The system can be made more users friendly. The program is coded in more structured manner so we can include future enhancement.
• The searching procedure should be very strong like user can search for their assets as fast as possible.
• Modify the project with better approach with more graphics
B ABBREVATIONS
Symbol Name/Abbreviations
CPU Central Processing Unit
IDE Integrated Development Environment
RAM Random Access Memory
GUI Graphical User Interface
Admin Administrator
Books
 The Complete Reference of Advance Java.
Websites:
• www.microsoft.com
• www.w3schools.com/jsp/
• www.tutorialspoint.com/sql/
• www.w3schools.com/sql/