E-Mapping

SYNOPSIS

Computers have become an essential part of

organizational information processing because of the power of
technology and the volume of data to be processed. Through the
technology, the manual process, defects and time consumption can be
reduced. Thats in all the area of business, computer technology are
widely been implemented. Hence the inception of computers had a
great role in reducing large tasks to simpler one. This project E-
Mapping has been designed in Asp.net as front end and Sql server as
the back end. The main objective of this project is maintaining good
relationship with the user. By providing them the best service.

The project modules included are

Administrator:

Tutorials

Colleges

Quiz

Bookstalls

Feedback
User:

View Tutorials

View Colleges

Quiz

View Bookstall

Feedback

Admin
The Admin of the organization can login through
this module.

Tutorials
This module is designed for the admin for adding
the tutorials in their site

Colleges
This module is designed for the admin for adding
the colleges details in their site.
 Quiz
This module has been divided for the administrator
for adding the quiz question to their site.

Book stall
This module has been divided for the administrator
for adding the book stalls to their site

Feeback
This module has been divided for the administrator
for viewing the feedback posted by the user

Users:

View tutorials
This module is designed for the user to view the
tutorials

View Colleges
This module is designed for the user to view the
colleges

Quiz:
 This module has been designed for the user for
attending the quiz questions on line and test their
skill level.
View Book stall
This module is designed for the user to view the
bookstalls
Feedback
This module is designed for the user post their
feedback .

PROJECT OBJECTIVE

The E-Mapping is the project developed to detect the credit card

fraud detection on the time of purchasing through on line.
Time Consuming and Easy to View

Maintaining the customer details and their purchase details easily by the
systematic format

BACKGROUND STUDY

2.1 STUDIES ON THE EXISTING SYSTEM

The system study phase studies the requirements of the existing

system E-Mapping

Limitation of existing system

 It needs manpower to record all the details of all customers
Each and every time the customer details have to be register
manually whenever the customer purchased the products.
On administrator side its difficult to manage more no of
customer if visited.
There should be some panel of large members to enable to
handle all type of customers.
User validation would not be done.

2.2 DRAWBACKS ON THE EXISTING SYSTEM

Takes high cost

Maintenance costs high
Administrator has to keep track of all processes
As files are maintained manually, chances for errors are large
Needs more manpower
Publicity cannot be assured
2.3 STUDIES ON THE PROPOSED SYSTEM

The Proposed system should overcome all the disadvantage faced by the
existing system.

2.3.1 DEFINING THE PROBLEM

The main objectives of the proposed system are to

reduce the human work, reduce the maintenance time, and to make
the system more user friendly, efficient, more accurate and fast
 processing. We used the web service concept to develop this
application.

Advantage of proposed system

Comparing the existing system it reduces the maintenance

cost and investment
Prevents errors due to systematic process
As system exists as online it possible to conduct auction
wherever administrator being in journey.
Its possible to make auction to be familiar world wide
Gaining more customers becomes quite easier
Advertising is possible
Can keep track of all the clients details
Credit card number will be encrypted and saved in the DB for
the Security by using the Secure Hash Algorithm.

DEVELOPING THE SOLUTION STRATEGIES

 In this project, we implemented mainly modules which is
Administrator part, user can view the list of available for those Online
search and all the details. They can add mails which ever they like
after they issue all the records (for the proof) .But they have to get
confirmation letter for admission from the Administrator. In an
Administrator module, he/she can view the entire users profiles. Even
through the issue the records, administrator only have Authority to
permit.

SYSTEM SPECIFICATION

APPLICATION SPECIFICATION

CLIENT/SERVER ENVIRONMENT:

To design and develop the Online Survey, it is essential to

understand the client/server model that plays an important role in the
concern, which needs the information to be retrieved in a fast and efficient
way.

What is Client/Server?

The Client/Server computing model implies a form of processing

when requests are submitted by a client or requests the server which
processes them and returns the result to the client. The client and the server
are two separate logical entities working together over a network to
accomplish the task.

Conceptually, the client server architecture can be defined as a special case of

Co-operative processing where on entire application is shared between the client and a
server system.

Features of client/server computing

Improved access to information due to internet

Globalization of information
Easier maintenance of application and data
Graphically oriented, high interactive user interface
Increased developer productivity through ease of tools

In our project we have divided core part into two parts. Asp pages, html
pages are used as user interface (client). They gather the information from
the user and process them. Sql 2000 is stored in IIS, which is used as server.

Installation requirements

When installing web development to a hard drive other than

ordinary PC, one need to have at least 65-70MB free space on a drive to
precede installation, regardless of how much space is on installation drive.
 Operating system: Windows 2000

Web server : Internet Information Server

(IIS)

4.2. NETWORK SPECIFICATION

Network Card : Ethernet card

Operating system : XP

Communication protocol: TCP/IP, HTTP

Connection Type : Internet

XP PLATFORM:

XP is a powerful multitasking operating system with high security. It

is user friendly and supports multithreading and lot of tools for developing
in any application. This OS has number of enhancements, including
performance improvement, better hardware support and closer integration
with the Internet. Windows support dynamic linking. This OS has the
concept of plug and play.

WEB SERVER:
 The Web server accepts the request and sends the HTML to the
Client browser that requests it. Web browser and web server communicate
through a common protocol (HTTP). The examples for web server are IIS
(Internet Information Services), PWS (Personal Web Server).

IIS-APPLICATION SERVER:

IIS is the Internet information server. This project is a web-based

project. It needs an application server to run. IIS is an application server
where the project runs. This application server is chosen because the project
is developed in ASP and both of them are Microsoft products. The
performance will be good if the product is form the same Vendor. IIS is user-
friendlier than other application servers. It is come as free along with
Operating System.

Features of Internet Information Server (IIS):

Its software, which makes the connectivity between client and server
communication and this software enable to run the asp pages on the client side
browsers. This software is responsible for routing the request to server and
provides the services to the client.

High performance network and application server.

 The server includes the Secure Sockets Layer (SSL)
encrypted communication standard for private
communication between the clients and server.
Active server page allows application with scripts and
components to perform multiple actions.
With Windows NT service pack. It also acts as a web
server.

4.3. HARDWARE SPECIFICATION

Server

Platform : Windows XP

System : Pentium IV 2.8 GHz

Ram : 512MB

Hard disk : 80GB

Client

Platform : Windows XP

System : Pentium IV 2.8 GHz

Ram : 256MB

Hard disk : 40GB

4.4 SOFTWARE SPECIFICATION

Web server : IIS Server

Back end : SQL Server 2000

 Server side scripting : ASP with Vb.net

Client side scripting : HTML

ACTIVE SERVER PAGES:

Active Server Pages (ASP) is a technology that enables the development of

dynamic web pages. ASP was developed by Microsoft to allow server side development.
ASP files are HTML files with special tags containing source code that provide the
dynamic content

Using Active server pages

Generate dynamic web pages. An active server page can display
different content to different user or display different content at
different times of the day.
Process the contents of HTML forms. We can use an active server page
to retrieve and respond to the data entered into an HTML form.
Can create database-driven web pages. An active server page can
insert new data or retrieve existing data from a database such a
Microsoft SQL Server, Microsoft Access.

Working of active server pages

An Active server page is a standard HTML file that is extended with
additional features. Like a standard HTML file, an active server page contains
HTML tag that can be interpreted and displayed by a web browser. Anything
we could normally place in an HTML file Java applets, Blinking text, client side
scripts, client-side Active X Controls we can place in an active server page.
However, Active server page has three important features that make it
unique.

An active server page contains server side scripts.

Active server page provides several built-in objects.
Active server page can be extended with additional
components.

ASP Objects and components

Active server pages include several built-in objects and installable ActiveX
components.

Objects:

An object is something typically has methods, properties or collections.

An object method determines the things we can do with the object. An
objects property can be read or set to specify the state of the object. An
object constitutes different sets of keys and value pairs related to the objects.

Components:

An ActiveX component is similar to an active server page built-in

object. However, when we are using V, there is one important distance
between components and object. A distance of a component must be
explicitly created before it can be used.

ASP Objects:
 Active server pages include several built-in objects. The following
explain detail how to use each of the built-in objects. Built-in objects of ASP
are

Application Object
Request object
Response object
Server object
Session object
Object context object

Application objects:

The application object is used to store and retrieve information that

can be shared among all users of an application. For Example, we can use the
Application Object to pass information between users of your web site.

Response objects:
 The response object is used to send information back to a browser.
We can use the response object to send output from our scripts to a browser.

Server objects:

The server object enables us to use various utility functions on the

server object to control the length of time a script executes before it times
out. We can also use the server object to create instance of other objects.

Session objects:

The session object can be used to store and retrieve information about
particular users sessions. We can use the session object to store information
that persists over the course of a visit by a user to our web site.

Object context object:

The object context object is used to control Active server page

Transactions. The transactions are managed by the Microsoft transaction
server (MTS).

The built in objects differ from normal objects. We dont need to create
an instance of a built in object before we can use it in a script. The methods,
collections and properties of a built in objects are automatically accessible
throughout a web site application.
ASP Components:

Active server page components can be used to extend the power of our
scripts components differ from the built-in-objects because there are typically
used for more specialized tasks. The following list provides a brief overview of
some of the components bundled with active server pages.

Ad rotator component
Browser capabilities component
Content linking component
Counters component
Content rotator component
Collaborations data objects
ActiveX Data objects

VBScript
VBScript stands for Visual Basic Script, a scripting language
developed by Microsoft to be used with Microsoft products, mainly Internet Explorer. It
has gone through many changes over the years and is now mainly used as the default
scripting language of ASP. VBScript was created to allow web page developers the ability
to create dynamic web pages for their viewers who used Internet Explorer. With HTML,
not a lot can be done to make a web page interactive, but VBScript unlocked many tools
like: the ability to print the current date and time, access to the web servers file system,
and allow advanced web programmers to develop web applications.

HYPER TEXT MARKUP LANGUAGE (HTML)

HTML is an application of the Standard Generalized Markup Language

(SGML), which was approved as an international standard in the year 1986.
SGML provides a way to encode hyper documents so they can be
interchanged.
 SGML is also a Meta language for formally describing document
markup system. Infect HTML uses SGML to define a language that describes a
WWW hyper documents structure and inter connectivity.

Following the rigors of SGML, TBL bore HTML to the world in 1990. Since
then, many of us have it to be easy to use but sometimes quite limiting.
These limiting factors are being addressed but the World Wide Web
Consortium (aka W3c) at MIT. But HTML had to start somewhere, and its
success argues that it didnt start out too badly.

MS-SQL SERVER 2000

MS SQL Server is a powerful database management system and the user can
create applications that require little or no programming. It supports GUI features and an
entire programming language, Visual Studio Application which can be used to develop
richer and more developed application.

There are quite a few reasons, the first being that SQL is a feature rich
program that can handle any database related task you have. You can create
places to store your data build tools that make it easy to read and modify your
database contents, and ask questions of your data. SQL is a relational
database, a database that stores information about related objects. In MS SQL
that database means a collection of tables that hold data. It collectively
stores all the other related objects such as queries, forms and reports that are
used to implement function effectively.

The MS SQL database can act as a back end database for .NET as a
front end, MS SQL supports the user with its powerful database management
functions. A beginner can create his/her own database very simply by some
mouse clicks. Another good reason to use SQL as backend tool is that it is a
component of the overwhelmingly popular Microsoft office software suite.

MS SQL however is a relational database, which means that you can

define relationships among the data it contains. Relational database, are
superior to flat file databases because you can store discrete information.

Primary key and other indexed fields:

Access use key fields and indexing to help speed many database
operations. We can tell access, which should be key fields, or access can
assign them automatically.

Controls and objects:

Queries are access objects us display, print and use our data. They can
be things like field labels that we drag around when designing reports. Or
they can be pictures, or titles for reports, or boxes containing the results of
calculations.

Queries and dynasts:

Queries are request to information. When access responds with its list
of data, that response constitutes a dynaset. A dynamic set of data meeting
our query criteria. Because of the way access is designed, dynasts are
updated even after we have made our query.

Forms:
 Forms are on screen arrangement that make it easy to enter and read
data. we can also print the forms if we want to. We can design form our self,
or let the access auto form feature.

Reports:

Reports are paper copies of dynasets. We can also print reports to disk, if
we like. Access helps us to create the reports. There are even wizards for
complex printouts.

Properties:

Properties are the specification we assigned to parts of our database design. We can
define properties for fields, forms, controls and most other access objects.

4.5 COST ESTIMATION AND SCHEDULING

For developing the software and hardware requirements needed

the less cost of developing the software package takes five months
duration.

4.5 DEVELOPMENT SPECIFICATION

 This includes salaries and other employment costs of the staff
involved in the development project and all associated costs.

I. Setup cost:

This includes the cost of putting the system into place. These
consists mainly of the cost of any new hardware and ancillary equipment
but will also include cost of file conversion, recruitment and staff training.

II. Operational cost:

It consists of cost of operating the system once it has been

installed.
Benefits on the other hand, or often quite difficult to quantify
in monetary terms even once thus have been identified.

III. Development cost

Development cost includes salaries and other employment costs of the

staff involved in the development project and all associated costs

Benefits may be categorized as follows:

 Direct benefits
Accessible indirect benefits
Intangible benefits

Direct benefits:

These accrue directly from the operation of the proposed system.

These could for example: include reduction in salary bills through introduction
of a new, computerized system.

Accessible indirect benefits:

These are generally secondary benefits such as increased accuracy

through the introduction of a user-friendlier screen design where we might be
able to estimate the reduction error and hence cost of proposed system.

Intangible benefits

These are generally longer term or benefit that are considered very difficult to
quantify. Enhanced job interest can lead to reduced staff turn over and hence lower
recruitment
DESIGN AND DEVELOPMENT PROCESS

5.1. FUNDAMENTAL DESIGN CONCEPTS

System design is a how to approach to creation of a new

system. System design goes through 2 phases. They are

- Logical design
- Physical design

Logical design reviews the present physical system, prepares input

and output specifications, makes edit security and control specifications

Physical design maps out the details of the physical system, plans,
system implementation, device a test and implementation plan.

5.2. DESIGN PROCESS

5.2.1.INPUT DESIGN

Input design is the process of connecting the user-originated inputs

into a computer to used formats The goal of the input design is to make data
entry Logical and free from errors. Errors in the input database controlled by
input design

This application is being developed in a user-friendly manner. The forms are

being designed in such a way that during the processing the cursor is placed
in the position where the data must be entered. An option of selecting an
appropriate input from the values of validation is made for each of the data
entered. Concerning clients comfort the project is designed with perfect
validation on each field and to display error messages with appropriate
suggestions.

Help managers are also provided whenever user entry to a new field
he/she can understand what is to be entered. Whenever user enter a error
data error manager displayed user can move to next field only after entering
a correct data

5.3.2.OUTPUT DESIGN

The output form of the system is either by screen or by hard copies.

Output design aims at communicating the results of the processing of the
users. The reports are generated to suit the needs of the users .The reports
have to be generated with appropriate levels. In our project outputs are
generated by asp as html pages. As its web application output is designed in
a very user-friendly which will be through screen most of the time.

5.3.2. CODE DESIGN

 The main purpose of code design is to simplify the coding and to
achieve better performance and quality with free of errors. The coding is
prepared in such a way that the internal procedures are more meaningful
validation manager is displayed for each column. The coding of the variables
is done in such a way that one other than person who developed the
packages can understand its purpose.

To reduce the server load, the project is designed in a way that

most of the

Validation of fields is done as client side validation, which will be more

effective.

5.4.4. DATABASE DESIGN

The database design involves creation of tables that are represented in

physical database as stored files. They have their own existence. Each table
constitute of rows and columns where each row can be viewed as record that
consists of related information and column can be viewed as field of data of
same type. The table is also designed with some position can have a null
value.
 The database design of project is designed in such a way values
are kept without redundancy and with normalized format. Refer the appendix
for screen shots of Database Design

5.3. DEVELOPMENT APPROACH

TOP DOWN APPROACH

The importance of new system is that it is user friendly and a better

interface with users working on it. It can overcome the problems of manual
system and the security problem.

Top down approach of software development is the incremental approach to

the construction of program structure. Modules are integrated by moving
through the control hierarchy, beginning with the main control module.
Modules subordinate to the main control modules are incorporate into the
structure in either a depth first or breadth first manner.

The top down approach is performed in a serious of five steps

1. The main module that is overall software is divided into

five modules that are under the control of the main
control module.
2. Depending on the top down approach selected
subordinate stubs is replaced one at a time with actual
components.
3. Tests are conducted as each component is integrated
4. On completion of each test another stub is replaced with
real time component.
5. Regression testing may be conducted to ensure the new
errors have not been introduced.
 TESTING AND METHODLOGIES

System testing is the state of implementation, which is aimed at

ensuring that the system works accurately and efficiently as expect before
live operation, commences. It certifies that the whole set of programs hang
together System testing requires a test plan, that consists of several key
activities and steps for run program, string, system and user acceptance
testing. The implementation of newly design package is important in
adopting a successful new system

Testing is important stage in software development. System test is

implementation should be a confirmation that all is correct and an
opportunity to show the users that the system works as they expected It
accounts the largest percentage of technical effort in software development
process.

Testing phase is the development phase that validates the code

against the functional specifications. Testing is a vital to the achievement of
the system goals. The objective of testing is to discover errors. To fulfill this
objective a series of test step such as the unit test, integration test,
validation and system test where planned and executed.
Unit testing

Here each program is tested individually so any error apply unit is

debugged. The sample data are given for the unit testing. The unit test
results are recorded for further references. During unit testing the functions
of the program unit validation and the limitations are tested.

Unit testing is testing changes made in a existing or new program

this test is carried out during the programming and each module is found to
be working satisfactorily. For example in the registration form after entering
all the fields we click the submit button. When submit button is clicked ,all
the data in form are validated. Only after validation entries will be added to
the database.

Unit testing comprises the set of tests performed by an individual

prior to integration of the unit into large system. The situation is illustrated in
as follows

Coding-> Debugging ->Unit testing -> Integration testing

The four categories of test that a programmer will typically perform on a

program unit

Functional test
Performance test
Stress Test
Structure test
 Functional test involve exercising the code with nominal input
values for which the expected results are known as well as boundary values
and special values.

Performance testing determines the amount of execution time

spent in various parts of unit program through put and response time and
device utilization by the program.

A variation of stress testing called sensitivity testing in same

situations a very small range of data contained in a the bounds of valid data
may cause extreme and even erroneous processing or profound performance
degradation.

Structured testing is concerned with a exercising the internal logic

of a program and traversing paths. Functional testing, stress testing
performance testing are referred as black box testing and structure testing
is referred as white box testing

VALIDATION TESTING

Software validation is achieved through a serious of testes that

demonstrate conformity with requirements. Thus the proposed system under
consideration has been tested by validation & found to be working
satisfactory.
OUTPUT TESTING

Asking the user about the format required by them tests the
output generated by the system under consideration .It can be done in two
ways, One on screen and other on printer format. The output format on the
screen is found to be correct as the format designed n system test.

SYSTEM TESTING

In the system testing the whole system is tested for interface

between each modules and program units are tested and
recorded. This testing is done with sample data . The securities,
communication between interfaces are tested

System testing is actually a series of different tests whose

primary purpose is to fully exercise the computer based system
although each test has a different purpose all work to verify
that all system elements properly integrated and perform allocate
function.

It involves two kinds of activities namely

1. Integrated testing

2. Acceptance testing
INTEGRATED TESTING

Integrated testing is a systematic technique for constructing tests

to uncover errors associated with interface.

Objective is to take unit tested modules and build a program

structure that has been dictated by design

ACCEPTANCE TESTING

Acceptance testing involves planning an execution of a functional

test, performance test and stress test to verify that the implemented system
satisfies the requirement.

The acceptance testing is the final stage of the user the various
possibilities of the data are entered and the results are tested.

VALIDATION TESTING

Software validation is achieved through a series of test that

demonstrates the conformity and requirements. Thus the proposed system
under consideration has to be tested by validation and found to be working
satisfactorily. For example in customer enters phone number field should
contain number otherwise it produces an error message Similarly in all the
forms the fields are validated

TESTING RESULTS

All the tests should be traceable to customer requirements the focus of

testing will shift progressively from programs Exhaustive testing is not
possible To be more effective testing should be which has probability of
finding errors

The following are the attributes of good test

1. A good test has a probability of finding a errors

2. A good test should be best of breeds

3. A good test to neither simple nor too complex

6.2 QUALITY ASSURANCE

Quality assurance consists of the auditing and reporting functions of

management. The goal of quality assurance is to provide management with
the data entries necessary to be informed about the product quality thereby
gaining the goal of insight and confidence that the product quality is meeting

Greater emphasis on quality in organization requires quality assurance.

To be an integral part of the information system development .The
development process must include checks throughout the process to ensure
that the final product meets the original user requirements.

Quality assurance thus becomes an important component of the

development process, Its included in the industry standard (IEEE 1993) On
the development process quality assurance process is integrated into a linear
development cycle through validation and verification performed at crucial
system development steps .The goals of the management is to institute and
monitor a quality assurance program with in the development process

Quality assurance induces

1. Validation of the system against requirements

2. Checks for errors in design documents and in the system itself

3. Quality assurance for usability

Quality assurance Goals:

Correctness: The extent to which the program meets the system

specifications and user objectives

Reliability: The degree to which the system performs its intended

functions overtime

Efficiency: The amount of computer resources required by a program to

perform a function

Usability: The effort required learning and operating a system

Maintainability: To use with which program errors are located and corrected

Testability: The effort required a testing a program to ensure its correct

performance

Portability: To ease of transporting a program from hardware

configuration to another

Accuracy: The required position in input editing computation and output

6.2.1 GENERIC RISKS.

Risk identification is the systematic attempt to specify threats to the

project plan (estimates the schedule resource overloading etc.). By
identifying know and predictable risk the first step is to avoiding them. When
possible and controlling them when necessary there are two types of risks

Generic Risk
Product specific risk
 Generic risks are potential threats to every software project. Only those
with a clear understanding of technology can identify product specific risk
The people and the environment that is specific to the project at a hand and
to identify the product specific risk and the project the plan and the software
statement of scope are examined and answer to the following question is
developed.

What special characteristics of this product may threaten

the project plan one method for identifying risk is to create a risk item and
checklists. The checklist can be used for risk identification and focus on some
subset to know and predictable risk in the following sub categories.

Product risk
Risk associated with overall size of software to
built or modified
Business imparts
Risk associated with constraints imposed with
management
Customer characteristics

Risk associated with sophisticated of the customer and developers ability to

communicate with the customer in a timely manner.

Different categories of risks are considered

Project Risks
It identify a potential budgetary, schedule, personnel like staffing,
organizing, resource, customer requirement, problems and their impact on a
software project
Technical risks
Technical risks identify potential design implementation interface,
verification, and maintenance problems.

6.2.2 SECURITY TECHNOLOGIES AND POLICIES

Any system developed should be secured & protected against possible

hazards. Security measures are provided to prevent unauthorized access to
database at various levels. Password protection & simple procedures to
change the unauthorized access are provided to the users.

The user will have to enter the user name and password and if it is
validated he can participate in auction. Otherwise if he/she is a new user he
should get registered and then he can place an order

When he/she registered they should provide authentication through jpg

files (like ration card Xerox, voter identity card Xerox). A multi layer security
architecture comprising firewalls filtering routers encryption & digital
certification must be assured in this project in real time that order details are
protected from unauthorized access.

6.3 SYSTEM IMPLEMENTATION

Implementation is the stage in the project where the theoretical design

is turned into a working system. The most crucial stage is achieving a
successful new system and giving a user confidence in that the new system
will work efficiently and effectively in the implementation stage. The stage
consist of

1. Testing a developed program with sample data

2. Detection and correction of error

3. Creating whether the system meets a user requirements

4. making necessary changes as desired by users.

5. Training user personal

6.3.1 IMPLEMENTATION PROCEDURES

The implementation phase is less creative than system design. A

system design may be dropped at any time prior to implementation, although
it becomes more difficult when it goes to the design phase. The final report of
the implementation phase includes procedural flowcharts, record layouts, and
a workable plan for implementing the candidate system design into a
operational design.

6.3.2 USER TRAINING

It is designed to prepare the users for testing & converting the system. There is
several ways to trail the users they are:

1) User manual
 2) Help screens

3) Training demonstrations.

1) User manual:

The summary of important functions about the system &

software can be provided as a document to the user. User training is designed
to prepare the user for testing and convening a system

The summary of important functions about the system and the

software can be provided as a document to the user

1. Open http page

2. Type the file name with URL index .asp in the
address bar
3. Index. ASP is opened existing user the type the
username and password
4. Click the submit button

2) Help screens:

This features now available in every software package,

especially when it is used with a menu. The user selects the Help option
from the menu. The System success the necessary description or information
for user reference.

3) Training demonstration:

Another user training element is a training demonstration. Live

demonstration with personal contact is extremely effective for training users.
6.3.3 OPERATIONAL DOCUMENTATION

Documentation means of communication; it establishes the design and

performance criteria of the project. Documentation is descriptive information
that portrays the use and /or operation of the system. The user will have to
enter the user name and password if it sis valid he participate in auction.
Otherwise if it is new user he needs to register

Documentation means of communication; it establishes design

& performance criteria for phases of the project. Documentation is descriptive
information that portrays he use &/or operation of the system.

1) Documentation tools:

Document production & desktop publishing tool support nearly ever aspect
of software developers. Most software development organizations spend a substantial
amount of time developing documents, and in many cases the documentation process
itself is quite inefficient. It is not use unusual for a software development effort on
documentation. For this reason, Documentation tools provide an important opportunity to
improve productivity.

2) Document restructuring:
 Creating document is far too timed consuming. If the system works, well live
with what we have. In some cases, this is the correct approach. It is not possible to
recreate document for hundreds of computer programs.

Documentation must be updated, but we have limited resources.

It may not be necessary to fully re document an application. Rather, those
portions of the system that are currently undergoing change are fully
documented.

The system is business critical and must be fully re documented.

Even in this case, an intelligent approach is to pare documentation to an
essential minimum.

6.4 SYSTEM MAINTENANCE

Maintenance is actually implementation of the review plan as

important as it is programmers and analyst is to perform or identify with him
or herself with the maintenance. There are psychologically personality and
professional reasons for this. Analyst and programmers spend fair more time
maintaining programmer then they do writing them Maintenances account
for 50-80% of total system development. Maintenance is expensive .One way
to reduce the maintenance costs are through maintenance mgt and software
modification audits Types of maintenance are

1. Perfective maintenance

2. Preventive maintenance
Perfective maintenance:

Changes made to the system to add features or to improve the

performance.

In future any more features can be added in AUCTION WAREHOUSE.COM and

it can easily adopt the changes.

Preventive maintenance:

Changes made to the system to avoid future problems. Any

changes can be made in the future and our project can adopt the changes.

CONCLUSION

One greater advantage of hosting web is to make the resource

to know all and to become familiar which paves a way for development
of organization as well as for profit. While hosting the software it
should be attractive, user-friendly, and easier to access. This auction
warehouse software constitutes all this characteristics

Some special features of this project are

It reduces the manpower to some extent

It reduces the time cost.

 It avoids redundancy of data and also system

supports for taking the floppy backups of front end

for future enhancements

SCOPE OF FUTURE ENHANCEMENTS

 Nothing will be useful until it is update & enhanced timely just like IT
field. In such a way that this software can have more future enhancement
such as

Authentication on administrator side can be moved over to

biometrics for more secure access

Database used has limited storage, Which can be switched

to SQL etc

Virtual auction can be enabled through web cams

Virtual reality for the products can be achieved with the

development of technology

It can be enhanced according to the client user friendliness

Can be enhanced with blogs in future for tie up with

different organization

Further the remote monitoring can be done for this project.

BIBLIOGRAPHY

WEBSITES

www.asptutorial.com
www.pscode.com
www.w3schools.com
www.hotscripts.com
www.freesoft.in

BOOKS:

1) Software engineering

By

Roger S.Pressman

Fifth Edition,

Mc.Graw Hill International Edition 2001

2) System Analysis And Design

Elais M.Awad, Second Edition

Galgotia Publications (P) Ltd

Published by Sunil Galgotia, 2002