8/6/2019 Arati Documentation
1/91
ASMsInstitute of Management & Computer Studies
(Affiliated to University of Mumbai & Approved by AICTE)C-4, Wagale Industrial Estate, Near Mulund West Check Naka,Opp. to Aplab, Thane (West), Mumbai 400 604.
Certificate
This is to certify that Mr. /Ms. Arati M. Gangan,
Roll No. MC0809022 has successfully submitted partially completed
project titled Warehouse Management System under our
guidance towards the partial fulfillment of Semester VI ofMaster
of Computer Applications as prescribed by the University of
Mumbai under our supervision during the academic year 2010-
2011.
Internal Examiner External Examiner
Date - Date -
Director HODIMCOST (MCA)
1
8/6/2019 Arati Documentation
2/91
PROJECT ON
Warehouse Management System
DONE AT
HCL
SUBMITTED IN PARTIAL FULFILLMENT OF
REQUIREMENT FOR THE DEGREE MCA
(MASTER OF COMPUTER APPLICATION)
SUBMITTED BY
Miss. Arati M. GanganROLL NO. MC0809022
DEPARTMENT OF MASTER OF COMPUTER APPLICATION
A.S.Ms
Institute of Management & Computer Studies(Affiliated to University of Mumbai & Approved by AICTE)
Plot C-4, Wagle Industrial Estate, Near Mulund Check Naka,
Opp. To Aplab ,Thane(W),Mumbai 400604.
2
8/6/2019 Arati Documentation
3/91
ACKNOWLEDGEMENT
It gives me immense pleasure in bringing out report on project Warehouse
Management System. I owe a greatmany thanks to the people who helped andsupported me throughout this project.
My deepest thanks to Lecturer, Mrs. Ruchita Meher, the Guide of the
project for guiding and correcting various documents of mine with attention and care.
She has taken pain to go through the project and make necessary correction as and
when needed.
My deep sense of gratitude to Mohsina Kachhawa , project guide at Hindustan
Computers Ltd(HCL) for her support and guidance. This project has given me
immense industrial experience and has exposed me to the latest technologies in market
and has helped to enhance my software skills.
I would also thank my Institution and my faculty members without whom this project
would have been a distant reality. I also extend my heartfelt thanks to my family and
well wishers.
3
8/6/2019 Arati Documentation
4/91
INDEX
Sr. No. Name Page No.
1. Synopsis 5
2. Company Profile 6
3. Abstract 7
4. Existing System 8
5. Literature survey 9
6. Scope & Objective of Project 13
7. Methodology 15
8. Hardware & Software Requirement 17
9. Requirement Analysis 18
10. Feasibility Study 20
11. Analysis & Design Model
1. Entity Relationship Diagram(ERD)
2. Data Flow Diagram(DFD)
3. Use case diagram
4. Activity Diagram
5. Class Diagram
23
24
31
32
43
12. Master Tables 44
13. Interface diagrams(snapshots) 4814. Testing and Results 80
15. Implementation 86
16. Conclusion 87
17. Future Work 88
18. References 89
4
8/6/2019 Arati Documentation
5/91
SYNOPSIS
5
Project Title Warehouse Management System
Project Type Web Application
Objective Development of an online WarehouseManagement.
Organization HCL
External Project Guide Ms. Mohsina Kachhawa
Internal Project Guide Mrs. Ruchita Meher
Developed By Arati Gangan, Dhanya Nair, Madhavi
Sawant.
Front End Microsoft Visual Studio 2008
Back End SQL Server 2005
Operating System Windows Operating System
8/6/2019 Arati Documentation
6/91
COMPANY PROFILE
Company Name: Hindustan Computers Ltd(HCL)
Address: Cosmos Vijay, Opposite to Jagdish Book Depot,
Station Road, Thane West, Thane - 400601
Website:www.hclcdc.in
Company Background:
Hindustan Computers Ltd(HCL) is an Electronics, Computing and IT company based
in Noida, India.
The company comprises two publicly listed companies, HCL Technologies and HCL
Infosystems.
6
http://www.hclcdc.in/http://www.hclcdc.in/8/6/2019 Arati Documentation
7/91
ABSTRACT
This project is aimed at developing an online Sales and Inventory Management
System (SIMS) for a departmental store.
The system was developed as per the Requirements specifications given by the
company.
This system can be used to store the details of the inventory, update the
inventory based on the sale details, produce receipts for sales, generate sales and
inventory reports periodically etc.
This is one integrated system that contains both the user component (used by
salespersons, sales managers, inventory managers etc) and the admincomponent (used by the administrators for performing admin level functions)
System provides a secure login for the various users of the system.
The system periodically generates reports such as inventory reports
and sales reports.
The status of the stock can be checked and the system also generates
sales trend and inventory trend graphs.
7
8/6/2019 Arati Documentation
8/91
EXISTING SYSTEM
Problem Definition:-
Existing system is manual system. The system has to keep all information of Different
Branches and Department Asset.
Earlier the appropriate staff of several departments manually maintains all the records.
Its very tedious job to keep track of all Asset and Vendor register and files. Such
process takes lot of time and required lot of skills.
Drawbacks:
Existing system is totally manual.
Maintaining registers take away a lot of important office space and is also time
consuming.
The existing system is not able to generate reports as per the requirements.
Many times there is problem of inconsistency of data.
Time consuming and mistakes are bound to happen.
Proposed System:-
Well operational and functional system Proposed system is Windows Web Application.
Maintaining record through forms. Saving data into one database. Less amount human resources.
Easy to insert, delete and update the data.
8
8/6/2019 Arati Documentation
9/91
LITERATURE SURVEY
Technology Overview:
A major element in building a system is the selection of compatible software
since the software in the market is experiencing a geometric progression.
Selected software should be acceptable to the firm and the user as well as it
should be feasible for the system.
The system is developed in C#.NET 2008 and SQL Server 2005 for use on
Windows environment.
The software we have used for our project is Visual Studio 2008 for Designing
and Coding and Reports. SQL Server 2005 for Database
C#.Net:
C-Sharp .NET (C#.NET) is an object-orientedcomputer programming language
which is generally implemented on the Microsoft .NET Framework.
Microsoft currently supplies C # Express Edition free of charge.
C-Sharp .NET provides the easiest, most productive language and tool for
rapidly building Windows and Web applications
C# .NET comes with enhanced visual designers, increased application
performance, and a powerful integrated development environment (IDE).
It also supports creation of applications for wireless, Internet-enabled hand-held
devices.
9
http://en.wikipedia.org/wiki/Object-oriented_programminghttp://en.wikipedia.org/wiki/Programming_languagehttp://www.startvbdotnet.com/dotnet/vbnet.aspxhttp://en.wikipedia.org/wiki/Object-oriented_programminghttp://en.wikipedia.org/wiki/Programming_languagehttp://www.startvbdotnet.com/dotnet/vbnet.aspx8/6/2019 Arati Documentation
10/91
Features of C#.NET:
Powerful Windows-based Applications
Powerful Web-based Applications
Simplified Deployment
Powerful, Flexible, Simplified Data Access
Improved Coding
Direct Access to the Platform
Full Object-Oriented Constructs
XML Web Services
Mobile Applications
COM Interoperability
Reuse Existing Investments
Upgrade Wizard
10
8/6/2019 Arati Documentation
11/91
SQL SERVER 2005:
Microsoft SQL Server 2005 provides the database developer the opportunity to
locate programming code in native formats or create server-driven complex
systems.
The .NET framework, in combination with the SQL Server 2005, delivers the
functionality of the powerful class library in combination with modern
programming languages. Common Language Runtime (CLR) is used to code
procedures, triggers and functions within the chosen language in the .NET
framework.
Using object-oriented constructs such as structured exception handling,
namespaces, classes and arrays assist the programmer in effectively handlingprocedural issues when programming with SQL Server 2005.
Feature of SQL SERVER 2005:
Feature Description
Database Mirroring Extend log shipping capabilities with
the database mirroring solution. You
will be able to use database mirroring
to enhance availability of your SQL
Server systems by setting up automatic
failover to a standby server.Online Restore With SQL Server 2005, database
administrators are able to perform a
restore operation while an instance of
SQL Server is running. Online restore
improves the availability of SQL
Server because only the data beingrestored is unavailable; the rest of the
database remains online and available.
Online Indexing Operations The online index option allows
concurrent modifications (updates,
deletes, and inserts) to the underlying
table or clustered index data and any
associated indexes during index data
definition language (DDL) execution.
For example, while a clustered indexis being rebuilt, you can continue to
11
8/6/2019 Arati Documentation
12/91
make updates to the underlying data
and perform queries against the data.
Fast Recovery A new faster recovery option improves
availability of SQL Server databases.
Administrators can reconnect to a
recovering database after the
transaction log has been rolled
forward.
Standards-based Information
Access
Any object, data source, or business
intelligence component can be
exposed using standards-based
protocols such as SOAP and HTTP
eliminating the need for a middle-tier
listener, such as IIS, to access a Web
services interface that is exposed by
SQL Server 2005.
SQL Server Management Studio SQL Server 2005 includes SQL ServerManagement Studio, a new integrated
suite of management tools with the
functionality to develop, deploy, and
troubleshoot SQL Server databases, as
well as enhancements to previous
functionality.
Dedicated Administrator
Connection
SQL Server 2005 provides a dedicated
administrator connection that
administrators can use to access arunning server even if the server is
locked or otherwise unavailable. This
capability enables administrators to
troubleshoot problems on a server by
executing diagnostic functions or
Transact-SQL statements.
Snapshot Isolation Snapshot Isolation (SI) level is
provided at the database level. With
SI, users can access the last committedrow using a transitionally consistent
view of the database. This capability
provides greater scalability.
Data Partitioning Data partitioning is enhanced with
native table and index partitioning that
enables efficient manageability of
large tables and indexes.
12
8/6/2019 Arati Documentation
13/91
SCOPE AND OBJECTIVE
Scope of the project:
The aim of the project is to automate the process involved in warehouse
management system.
The automated system should have the records of the inventory, sales as well as
the users who are using the system.
The new system will keep track of the level fo stock in the inventory so that the
people in charge of the maintenance of stock is alerted when the stock has
reached reorder level.
Advantage of such a system is that earlier the job of maintaining stock was done
manually which was a heinous task. But using the new system the records areupdated and hence the stock calculations are performed easily.
Also the sales related tasks like creating bill, generating new bill after items are
returned etc. are done in an efficient and easy manner.
Thus the transaction of money can be easily tracked.
13
8/6/2019 Arati Documentation
14/91
Objective of the project:
Maintain the records of the daily stock depletion and addition.
Maintain the details of money transactions.
Generate a sales and inventory trends graph for each item so that the
inventory managers can reorder the stock according to the demands of the
customer.
Create a secure login for the users of the system.
The sales person should be able to notify the inventory managers if a
certain item is not available in stock.
14
8/6/2019 Arati Documentation
15/91
METHODOLOGY
Software Development Model
Some programs are written around what is happening and others are written
around who is being affected. The first way is called Structure or Procedure
oriented model. This approach characteristics a program as a series of linearsteps (that is code).Here code acts on data.
To manage the increasing complexity, the second way i.e. the Object-Oriented
approach was conceived.
Object-oriented programming organizes a program around the data and a set of
well-defined interfaces to that data. Here there is data controlling access to code.
Object Orientation is an approach to software development that organizes both
the problem and its solution as a collection of discrete objects; both data
structure and behavior are included in the representation.
Object oriented representation is recognized by its seven characteristics:
Identity,
Abstraction,
Classification,
Encapsulation,
Inheritance,
Polymorphism And
Persistence The main property which we have used is that of Persistence: the
ability of an objects name, state and behaviors are saved as the object is
transformed.
An Object Oriented process uses the encapsulation of data and behavior to form
independent units (objects).The same constructs represent the system from the
requirements to the applications implementation and testing.
15
8/6/2019 Arati Documentation
16/91
Thus Object Oriented is a philosophy of problem and solution representation,
not a software Life cycle by itself.
Indeed OO can be used in many different software life cycles from waterfall to
spiral which was even useful for our Prototyping model.
In general, OO deals with requirements, high-level design, coding and testing
but not necessarily in a sequential fashion; the sequence is determined by the
life-cycle, not by the OO representation.
16
8/6/2019 Arati Documentation
17/91
HARDWARE AND SOFTWARE REQUIREMENTS
Processor TypeIntel Pentium IV or greater
System RAM 1 GB or greater
Input Device Basic Keyboard and Scroll Mouse
Output Device Standard Color Monitor, Printer
Storage Device 40 GB HDD Minimum
Operating System Microsoft Windows XP Professional.
Front End Visual Studio 2008
Back End SQL SERVER 2005
17
8/6/2019 Arati Documentation
18/91
8/6/2019 Arati Documentation
19/91
Record Inspection:
Much kind of record and reports provide us with valuable information about the
organization and its operations. In order to know the internal working of the
organization this technique is essential. This technique helped us a lot to know moreabout:
The paper work involved in the organization.
The bills and reports involved in the system.
The importance of the documents involved in the organization.
Their forms and their layouts
19
8/6/2019 Arati Documentation
20/91
FEASIBILITY STUDY
Feasibility is the measure of how beneficial or practical the development of an
information system will be to an organization.
Feasibility Analysis is the process of measuring feasibility. There are following
categories of feasibility tests:
1) Operational Feasibility :
The staff of the company was not comfortable with the manual System. As the new
system will reduce the time taken for searching process strain, an easy way of error
free and accurate work can be experienced, the staff of company welcomed the new
system and users are ready to switch over from manual to computerized system.
The management is willing to switch over because of increased effectiveness of
individual moreover, they will receive timely and accurate reports which indeed
helpful for an organization from the point of view planning. So, the system is
operational feasible.
2) Technical Feasibility :
Measure of practicality of a specific technical solution and availability of technical
resources are expertise.
Is the proposed technology or solution practical?
Make sure that the chosen technology is known and easy enough to solve
the problems.
Do we currently possess the necessary technology?
Technology is infeasible and not practical if the organization cannot
afford the technology.
Do we possess the necessary technical expertise , and is the schedule
reasonable?
20
8/6/2019 Arati Documentation
21/91
This involves financial consideration to accommodate technical
enhancement.
21
8/6/2019 Arati Documentation
22/91
3) Economical Feasibility :
Measure of cost effectiveness of a project or solution is called as Cost Benefit
Analysis. As soon as specific requirements and solutions have been identified, the
analyst can weigh the cost and benefits of each alternative cost benefit analysis.
The company is already having the required hardware and software, so major cost
will be in terms of development of the new system.
4) Schedule Feasibility :
Measure of how reasonable the project timetable is. Schedule can be mandatory or
desirable. It is better to deliver a properly functioning information system later than
to deliver an error prone.
22
8/6/2019 Arati Documentation
23/91
ANALYSIS & DESIGN MODEL
23
8/6/2019 Arati Documentation
24/91
8/6/2019 Arati Documentation
25/91
DATA FLOW DIAGRAM CONTEXT-LEVEL:
25
WarehouseManagement System
Administrator
Sales Person
Sales Manager
Inventory Manager
Add New UserAdd item to inventory
Change item price
Check No.ofbills generated
Check cancelled bills
money transaction
Check returned items
Check Exception report
Generate Sales Graph
8/6/2019 Arati Documentation
26/91
DFD LEVEL-1:
Create Bill
26
Sales Person
1.0
EnterItemDetails
bill_details
bill_item_details
1.1
Getpriceper item
1.2
Calculate Total
1.3
Create Bill
newitem
bill_details
8/6/2019 Arati Documentation
27/91
Check Status:
27
Sales Person
2.1
Enter item id newitem
2.2
Check itemStatus
8/6/2019 Arati Documentation
28/91
Search Item:
28
Sales PersonSelect
Gategory
1.0
EnterItemName
1.2
Get
Itemsby
category
1.1
Display ItemDetails
1.3
New item
8/6/2019 Arati Documentation
29/91
Return Item
29
Sales Person 1.0Select
bill
1.1Get
purchased
items
1.2
Select Item
1.3
Return Item
Bill_details
Bill_item_details
newitem
returnitem
8/6/2019 Arati Documentation
30/91
Admin Tasks:
30
Admin2.0
Add newuser
2.1
Add newitem
2.2
Removeuser
2.2
Change
Password
Login
newitem
Login
Login
8/6/2019 Arati Documentation
31/91
Inventory Manager Tasks:
31
InventoryManager Check
Status
2.0
Inventory
Report
2.2
ValidateInventory
2.
1
InventoryTrend-graph
2.
3
8/6/2019 Arati Documentation
32/91
USE CASE DIAGRAM:
32
8/6/2019 Arati Documentation
33/91
ACTIVITY DIAGRAM:
Add New Item
Update Item
33
8/6/2019 Arati Documentation
34/91
Add New User
34
8/6/2019 Arati Documentation
35/91
Change Password
35
8/6/2019 Arati Documentation
36/91
Create Bill
36
8/6/2019 Arati Documentation
37/91
Check Item Availability:
37
8/6/2019 Arati Documentation
38/91
Return Item
38
8/6/2019 Arati Documentation
39/91
Search Item
39
8/6/2019 Arati Documentation
40/91
Count Bills
Count Return Items
40
8/6/2019 Arati Documentation
41/91
Count Cancel Bills
Sales-Trend Graph
41
8/6/2019 Arati Documentation
42/91
Validate Inventory
42
8/6/2019 Arati Documentation
43/91
Inventory Report
Inventory-Trend Graph
43
8/6/2019 Arati Documentation
44/91
CLASS DIAGRAM
44
8/6/2019 Arati Documentation
45/91
MASTER TABLES
45
8/6/2019 Arati Documentation
46/91
Newitem
Bill_Details
Bill_item_details
46
8/6/2019 Arati Documentation
47/91
Login
Returnitem
Messages
47
8/6/2019 Arati Documentation
48/91
Graph
Cancel_bills
48
8/6/2019 Arati Documentation
49/91
INTERFACE DIAGRAMS
SNAPSHOTS
49
8/6/2019 Arati Documentation
50/91
ADMINISTRATOR:
50
8/6/2019 Arati Documentation
51/91
ADD NEW ITEM
51
8/6/2019 Arati Documentation
52/91
UPDATE ITEM:
52
8/6/2019 Arati Documentation
53/91
ADD NEW USER:
53
8/6/2019 Arati Documentation
54/91
CHANGE PASSWORD:
54
8/6/2019 Arati Documentation
55/91
55
8/6/2019 Arati Documentation
56/91
REMOVE USER:
56
8/6/2019 Arati Documentation
57/91
SALES PERSON
LOGIN:
57
8/6/2019 Arati Documentation
58/91
SALES PERSON HOME:
58
8/6/2019 Arati Documentation
59/91
CREATE BILL:
59
8/6/2019 Arati Documentation
60/91
BILL:
60
8/6/2019 Arati Documentation
61/91
ITEM AVAILABILITY:
61
8/6/2019 Arati Documentation
62/91
RETURN ITEM:
62
8/6/2019 Arati Documentation
63/91
SEARCH ITEM:
BY CATEGORY
63
8/6/2019 Arati Documentation
64/91
BY ITEM:
64
8/6/2019 Arati Documentation
65/91
SALES MANAGER:
COUNT BILLS
65
8/6/2019 Arati Documentation
66/91
COUNT RETURN ITEMS:
66
8/6/2019 Arati Documentation
67/91
COUNT MONEY TRANSACTION:
67
8/6/2019 Arati Documentation
68/91
COUNT CANCEL BILL:
68
8/6/2019 Arati Documentation
69/91
SALES-TREND GRAPH:
69
8/6/2019 Arati Documentation
70/91
70
8/6/2019 Arati Documentation
71/91
INVENTORY MANAGER:
CHECK STOCK STATUS:
71
8/6/2019 Arati Documentation
72/91
72
8/6/2019 Arati Documentation
73/91
INVENTORY REPORT:
73
8/6/2019 Arati Documentation
74/91
BY CATEGORY:
74
8/6/2019 Arati Documentation
75/91
BY PRICE
75
8/6/2019 Arati Documentation
76/91
VALIDATE INVENTORY:
76
8/6/2019 Arati Documentation
77/91
RESTOCK MESSAGES
77
8/6/2019 Arati Documentation
78/91
78
8/6/2019 Arati Documentation
79/91
INVENTORY-TREND GRAPH:
79
8/6/2019 Arati Documentation
80/91
CHANGE PASSWORD:
80
8/6/2019 Arati Documentation
81/91
8/6/2019 Arati Documentation
82/91
General Plan for Testing:
o Process Support Tool is tested using bottom up testing strategy.
o Testing of form pages and interfaces while input and output design.
o Module wise testing (Also sub module wise) while code
develpment
o Integration testing of system when integration of individual testing.
o
Security testing.o User level testing.
TESTING STRATEGY:
A strategy for software testing integrates software test case design method into a well-
planed series of steps that result in the successful construction of the software.
The strategy provides the roadmap that describes the steps to be conducted as a part of
testing, then these steps are planed and then undertaken, and how much effort, timeand resource will be required.
We have tested our whole Process Support Tool Support System using bottom up
testing strategy.
Bottom up testing involves integrating and testing the modules to the lower levels in
the hierarchy, and then working up hierarchy of modules until the final module is
tested.
Bottom up testing strategy shows how actual testing is to be done with whole system
but it does not show any detail about each module testing.
For each module testing we have decided to test each lower level module with white
box testing strategy.
When all modules are tested successfully then we will move to one step up and
continue with white box testing strategy.
When all modules will be tested successfully then we will integrate those modules and
try to test integrated system using black box testing strategy.
82
8/6/2019 Arati Documentation
83/91
We have done path testing to exercise every independent execution path through a
component of program. If every independent path is executed then all statements in
the components must have been executed at least once.
We have tested our functions of component to check the specification of our
components. We selected input set to test the components like in query process we
gave the different kinds of inputs to examine there output
TESTING METHODS
Unit testing:
Unit testing focuses verification effort on the smallest unit of software
design the software component or module. In this type of testing the individual
modules are tested and verify whether the accurate output is available or not. It can be
done in two ways bottom-up or top- down. In bottom-up approach the last module is
tested first and then moving upwards towards the first module. Top-down integration
testing is an incremental approach to construction of program structure. Modules areintegrated by moving down ward through the control hierarchy, beginning with the
main control module.
Integration Testing:
When the unit testing is over, all the modules are integrated and tested as a
whole. It might be possible that all modules may work individually, but they may not
work when we put them together. Data can be lost across the interface, one module
can have adverse affect on other or sub functions of another, when combined may not
produce desired major function, individually acceptable imprecision may be
magnified to unacceptable level; global data structure can present problem. So any
system has to be tested this way so that the final output is the desired one.
Validation Testing:
After the integration testing software is completely assembled as a package,
interfacing error have been uncovered and corrected, and then validation testing may
begin. Validation can be defined in many ways but a simple definition is what a
validation succeeds when software functions in a manner that can be reasonably
accepted by the company.
System testing:
Any software is only one element of a larger computer based system.
Ultimately software is incorporated with other system elements like hardware, people,
information and a series of system integration and validation tests are conducted.
System testing is actually a series of different test whose primary purpose is to fully
exercise the computer based system. Although each test has a different purpose, all
work to verify that system elements have been properly integrated and perform
allocated functions.
Storage Testing:
83
8/6/2019 Arati Documentation
84/91
The database of the system has to be stored on the database server. So the
storage capacity of the database server should be enough to store all the data required
for the efficient running of the system.
TEST CASES:
Tested modules:
Login form
Change password
Create bill
Check status
Return item
Search item
84
8/6/2019 Arati Documentation
85/91
Test Case 1:
Test Case Title Login
Purpose of test Validates the user
Test-Data UserID:SM1001
Password:abcd
Designation: Sales Manager
Steps o Enter the details correctly
o Click login button
Expected Result The home page of sales manager is displayed.
Test Case 2:
Test Case Title Change Password
Purpose of test Validates Password
Test-Data User ID:IM1001
Old Password: abc
New Passwoed:aratiim1001
Retype New Password
Steps
o Enter the details correctly
o Click Submit button
Expected Result Password is Change Successfully Message is
displayed.
.
85
8/6/2019 Arati Documentation
86/91
8/6/2019 Arati Documentation
87/91
Test Case 5:
Test Case Title Search Item
Purpose of test To Check Item is available
Test-Data Item-wise option chosen
Item Name: Banana
Steps
o Enter the details correctly
o Click Submit button
Expected Result Item details are displayed.
87
8/6/2019 Arati Documentation
88/91
IMPLEMENTATION
This is the Phase were Software as a product is handover / installed at client side
environment.
A detail talk was done & training phase was conducted for the project users, there errors are
noted and rectified.
The following steps were carried out in implementation phase.
Conduct Training: The training was conducted for the employees of the company to make
them familiar with the system.
Bug fixing and documentation: Any errors that occurred were solved and documented.
Install the system: The system was then installed.
88
8/6/2019 Arati Documentation
89/91
CONCLUSION
An attempt is made in all its earnest towards the successful completion of the project. This
system was verified with valid as well as with invalid data.
This system is user friendly since it has been developed in Visual Studio 2005, a successful GUI
environment. Since the connection can be extended to any database. The control will be more
powerful.
Connecting it to any type of database extends the development control. Any suggestions for future
development of the system are welcome.
Upgrading the system can be done without affecting the proper functioning of system.
89
8/6/2019 Arati Documentation
90/91
FUTURE WORK
The maintenance of software is the time period in which the software product performs useful
work. Maintenance activities involve making enhancement activities to the, adapting product to new
environment and correcting problems. Software enhancement may involve providing new functionalcapabilities, improving user displays and modes of interaction.
Adaptation of software to a new environment may involve moving the software to a different
machine. Problem correction involves modification and revalidation of software to correct errors.
The four types of maintenance activities are described below:
Corrective Maintenance: - Corrective maintenance includes the diagnosis and correction of one or
more errors.
Adaptive Maintenance: - Adaptive maintenance is an activity that modifies software to properlyinterface with the changing environment.
Perfective Maintenance: - Perfective maintenance is performed to satisfy user requests such as new
Capabilities, modifications to existing functions and general enhancements.
Preventive Maintenance: - Preventive maintenance occurs when software is changed to improve
future maintainability or to provide a better basic for future enhancements.
90
8/6/2019 Arati Documentation
91/91
REFERENCES
Book reference
Sr. No. Title Reference
1 ASP.Net Black Book
2 C# Balagurusami
3 SQL Server 2005 Paul Dubois
Web References:
www.codeprojec.com www.aspforum.com
www.hclcdc.com
http://www.codeprojec.com/http://www.aspforum.com/http://www.hclcdc.com/http://www.codeprojec.com/http://www.aspforum.com/http://www.hclcdc.com/Top Related