CUSTOMER MANAGEMENT SYSTEM

Abstract
The project is entitled as Stationary Management is developed by VB.Net as
front end and SQL server as the back.
Thus, the daily manual process of the Stationary Management like Stock
detail maintenance, Supplier maintenance, changing password etc has been implemented
which can be followed through the computer technology i.e., Customer Stationary
Management.

Modules:

Change Password
Supplier Maintenance
Stock Maintenance
Categories
Reports

Change Password:
This module is used to change the password for the Administrator login in. This
may contains the fields like user name, Password.
Supplier Maintenance:
This module describes the maintenance of the supplier details who supplies the
products this may contains the attributes like s the supplier name, address, contact
no etc
.
Category :
This module is described as the category of the products there may be different
categories among the products like pencil ,notes etc.
Stock Maintenance :
This module describes maintenance of the stock details like product id, category
name, price etc.
Reports:
This module is described as the overall reports of the modules described above.

INTRODUCTION

The Stationary Management helps to clients achieve high performance by

efficiently anticipating, purchasing and exceeding their customers' expectations. The
people and the technology support of processes that affect a customer's experience at the
frontline interface between the customer and the organization. Creative designers of
customer experience that meet customer relationship goals of delivering value to the
customer and profit to the organization

SYSTEM STUDY
System analysis is a process of gathering the facts concerning the system breaking
them into elements and relationship between elements. It provides a framework for
visualizing the organizational and environmental factors that operate on a system. The
quality of work performed by a machine is usually uniform, neat and more reliable when
compared to doing the same operations manually.

2.1 EXISTING SYSTEM

In the existing system the billing alone is maintained in FoxPro. The appointment
details, the customer details and the Reminder Details are maintained manually. The
study of the existing system revealed that the system has several drawbacks.

DRAWBACKS
The existing system has no security measure against logging in and no
checks are made for authorized users.
The end user has to remember a lot of command to make efficient use of
the system.
The system does not have any descriptive reports and thus did not help
management in decision-making.
The appointment information per day is unable to find.
Enormous amount of time is consumed

PROPOSED SYSTEM
The proposed system is been developed to maintain the Customer Management
by the customers to maintain the Customer Details, Group Creation, Production Details ,
Appointment Details, Reminder Details etc.,

BENEFITS
The user can enter only if the username and the password are correct.
The process of planning will be easy since every process is computerized.
Time Saving.
The Appointment information per day and per month can be known.
The details of the all saved information can be viewed.
The data can be accessed easily whenever needed and so the manual work can
be reduced.

SYSTEM ENVIRONMENT:
HARDWARE CONFIGURATION:
PROCESSOR

PENTIUM IV

HARD DISK CAPACITY

40 GB

MONITOR

14 SAMTRON MONITOR

FLOPPY DISK DRIVE

1.44 MB

PRINTER

: TVS 80 COLOR

INTERNAL MEMORY CAPACITY :

128 MB

KEYBOARD

LOGITECH OF 104 KEYS

CPU CLOCK

1.08 GHz

MOUSE

LOGITECH MOUSE

SOFTWARE CONFIGURATION:
OPERATING SYSTEM

: WINDOWS XP

FRONT END

: VISUAL BASIC6.0

BACK END

MS-Access 2003

VISUAL BASIC.NET
Visual

Baic.Net

has

revolutionized

windows

programming

windows

programming and with an object based, event driven approach to software designs. Visual
basic.Net applications act as a front end to the database. Visual basic.Net application
provides the interface between the user and the database. Sophisticated features that make
the language truly object oriented and interfaces it with the latest in the database
technology.
.NET provides a new, object-oriented API as a set of classes that will be
accessible from any programming language. This book describes this framework of
classes and provides a reference to what is available and how you can use this framework
to write Windows applications in the brave new world of .NET.
Microsoft .NET Framework is a computing platform for developing distributed
applications for the Internet. Following are the design goals of Microsoft .NET
Framework:
1. To provide a very high degree of language interoperability
2. To provide a runtime environment that completely manages code execution
3. To provide a very simple software deployment and versioning model
4. To provide high-level code security through code access security and strong type
checking
5. To provide a consistent object-oriented programming model
6. To facilitate application communication by using industry standards such as
SOAP and XML.
7. To simplify Web application development

Visual basic.net lets the user to add menus, text boxes, command buttons, option
buttons, check boxes, list boxes, scroll bars, and file directory boxes to blank windows.
Visual basic.net has many different tools.

The Common Language Runtime

The CLR is the mechanism through which .NET code is executed. It is built upon
a single, common languageILinto which source languages are compiled and includes
mechanisms for executing the compiled code. This includes code verification and just-intime (JIT) compilation, garbage collection and enforcement of security policies, and the
provision of profiling and debugging services.
The CLR provides a lot of added value to the programs it supports. Because it
controls how a .NET program executes and sits between the program and the operating
system, it can implement security, versioning support, automatic memory management
through garbage collection, and provide transparent access to system services

IMPORTANT FEATURES:

The application is a graphical user interface.

Client-Server architecture benefits picture and image box can be

easily handled using bit mapped files and icons.

Bit mapped files and icons are used as simple debugging tools.

With the advent of .NET, Microsoft has introduced many new

technologies that make writing component-based distributed
systems easier, more flexible, and more powerful than ever before.

It is now easier than it has ever been to write components in any

programming language that can interoperate with components on
other machines, which may not be Windows-based at all.

SQL SERVER 2000

The purpose of this document is to help you migrate your applications

when you are migrating the underlying database from Microsoft SQL Server to Some
other Database. Most of the issues encountered when migrating applications to use an Sql
Server Database are related to database incompatibility. This paper presents these
incompatibilities and provides solutions for many issues.
You should familiarize yourself with this document prior to migrating your
databases. The choices made about how to migrate your application affect how you
migrate the underlying database from Microsoft SQL Server to some other Database.
If the application uses the Microsoft OLE DB Provider for SQL Server or a thirdparty OLE DB Provider to connect the Microsoft SQL Server database, use the Sql
Server Provider for OLE DB (SQLOLEDB) to connect to the migrated Database.

SQL Server Security

Login Authentication.

Windows NT Authentication

SQL Server Authentication

Permissions validation on user database.

T-SQL statements sent to SQL Server.

SQL server checks user permissions on receipt of T-SQL

statements

FEATURES

Created by Microsoft and Sybase in the 80s.

Is SQL Compliant - Uses ANSI SQL

Supports SQL 92 standards - Uses T-SQL

Stores data in a central location and delivers it to clients on request

New Server Architecture

Graphic Administration Tools

Maintains ANSI standards and 6.x Compatibility

Data integrity means reliability and accuracy of data.

Integrity rules keep data consistent.

Supports Client/Server model.

Request response dialog.

workload is split between the client and the server.

Operating System compatibility.

Runs on Win 95/98 NT, Netware, UNIX, OS/2, Appletalk, Banyan VINES.

SQL Server must have Service Pack 4 (SP4) to run on Windows NT 4.0.

Multiple protocol compatibility.

SQL Server supports these protocols - Appletalk, TCP/IP.

SMP Compatibility and Scalability

3. SYSTEM ANALYSIS
In this chapter, concepts associated with term structured system and how
they are implemented in the project has been dealt with the tools used for structure
system analysis are,

Data Flow Diagram

3.1 ENVIRONMENTAL MODEL

The Environmental model defines the interfaces between the system and
the environment. Building an environmental model is the first and the most important
part of building complete model of user requirements. The critical aspect of
environmental model is to identify the events occurring in the environment to which the
system must respond. It also defines the boundary between the system and the
environment.
3.2 BEHAVIOURAL MODEL:
A system flow diagram is a pictorial representation of the working of the system.
It is a tool that depicts the flow of data through a system and the work processing
performed by that system. This takes an important role in the system analysis part to
know the present level of existing system and what modification is to be done to
overcome the problem occurring in the system. It is the starting point of the design phase
that functionally decomposed the requirement. A system flow diagram consists of a series
of rectangles joined by lines. The rectangles represents data transformation and lines
represent data flow in those systems. A data flow diagram describes data flow rather than

how they are proposed. System Flow Diagram of WORK FLOW MANAGEMENT
is shown in Fig 3.2.1

4. SYSTEM DESIGN
System design is the process of planning a new system to complement or
altogether replace the old system. The purpose of the design phase is the first step in
moving from the problem domain to the solution domain. The design of the system is the
critical aspect that affects the quality of the software. System design is also called toplevel design. The design phase translates the logical aspects of the system into physical
aspects of the system.

3.2 INPUT DESIGN

Input design is one of the most important phase of the system design. Input design
is the process where the input received in the system are planned and designed, so as to
get necessary information from the user, eliminating the information that is not required.
The aim of the input design is to ensure the maximum possible levels of accuracy and
also ensures that the input is accessible that understood by the user.
The input design is the part of overall system design, which requires very careful
attention. if the data going into the system is incorrect then the processing and output will
magnify the errors.
The objectives considered during input design are:

Nature of input processing.

Flexibility and thoroughness of validation rules.

Handling of properties within the input documents.

Screen design to ensure accuracy and efficiency of the input

relationship with files.

Careful design of the input also involves attention to error

handling, controls, batching and validation procedures.

Input design features can ensure the reliability of the system and produce result
from accurate data or they can result in the production of erroneous information. The
input design of the system includes the followin

Form Design:

3.3 OUTPUT DESIGN

Output design is very important concept in the computerized system, without
reliable output the user may feel the entire system is unnecessary and avoids using it. The
proper output design is important in any system and facilitates effective decision-making.
The output design of the system includes the following

5. TESTING AND IMPLEMENTATION

5.1 TESTING
Testing is a series of different tests that whose primary purpose is to fully
exercise the computer based system. Although each test has a different purpose, all work
should verify that all system element have been properly integrated and performed
allocated function. Testing is the process of checking whether the developed system
works according to the actual requirement and objectives of the system.

The philosophy behind testing is to find the errors. A good test is one that has a
high probability of finding an undiscovered error. A successful test is one that uncovers
the undiscovered error. Test cases are devised with this purpose in mind. A test case is a
set of data that the system will process as an input. However the data are created with the
intent of determining whether the system will process them correctly without any errors
to produce the required output.

Types of Testing:

Unit testing

Integration testing

Validation testing

Output testing

User acceptance testing

5.1unit Testing
All modules were tested and individually as soon as they were completed and were
checked for their correct functionality.

5.2 Integration Testing

The entire project was split into small program; each of this single programs gives a
frame as an output. These programs were tested individually; at last all these programs
where combined together by creating another program where all these constructors were
used. It give a lot of problem by not functioning is an integrated manner.
The user interface testing is important since the user has to declare that the
arrangements made in frames are convenient and it is satisfied. when the frames where
given for the test, the end user gave suggestion. Based on their suggestions the frames
where modified and put into practice.

Validation Testing:
At the culmination of the black box testing software is completely assembled as a
package. Interfacing errors have been uncovered and corrected and a final series of test
i.e., Validation succeeds when the software function in a manner that can be reasonably
accepted by the customer.

5.3 Output Testing

After performing the validation testing the next step is output testing of the proposed
system. Since the system cannot be useful if it does not produce the required output.
Asking the user about the format in which the system is required tests the output
displayed or generated by the system under consideration. Here the output format is
considered in two ways. one is on screen and another one is printed format. The output
format on the screen is found to be corrected as the format was designed in the system
phase according to the user needs. And for the hardcopy the output comes according to
the specifications requested by the user.

User Acceptance System

An acceptance test as the objective of selling the user on validity and
reliability of the system. It verifies that the procedures operate to system specification and
mat the integrity of vital is maintained.

Performance Testing

This project is a application based project, and the modules are interdependent
with the other modules, so the testing cannot be done module by module. So the unit
testing is not possible in the case of this driver. So this system is checked only with their
performance to check their quality.

5.2 IMPLEMENTATION
The purpose of System Implementation can be summarized as follows:
It making the new system available to a prepared set of users (the deployment),
and positioning on-going support and maintenance of the system within the Performing
Organization (the transition). At a finer level of detail, deploying the system consists of
executing all steps necessary to educate the Consumers on the use of the new system,
placing the newly developed system into production, confirming that all data required at
the start of operations is available and accurate, and validating that business functions
that interact with the system are functioning properly. Transitioning the system support
responsibilities involves changing from a system development to a system support and
maintenance mode of operation, with ownership of the new system moving from the
Project Team to the Performing Organization.
List of System implementation is the important stage of project when the theoretical
design is tuned into practical system. The main stages in the implementation are as
follows:

Planning

Training

System testing and

Changeover Planning

Planning is the first task in the system implementation. Planning means deciding
on the method and the time scale to be adopted. At the time of implementation of any
system people from different departments and system analysis involve. They are
confirmed to practical problem of controlling various activities of people outside their
own data processing departments. The line managers controlled through an
implementation coordinating committee. The committee considers ideas, problems and
complaints of user department, it must also consider;

The implication of system environment

Self selection and allocation form implementation tasks

Consultation with unions and resources available

Standby facilities and channels of communication

The following roles are involved in carrying out the processes of this phase. Detailed
descriptions of these roles can be found in the Introductions to Sections I and III.
_

Project Manager

Project Sponsor

Business Analyst

Data/Process Modeler

Technical Lead/Architect

Application Developers

Software Quality Assurance (SQA) Lead

Technical Services (HW/SW, LAN/WAN, Telecom)

Information Security Officer (ISO)

Technical Support (Help Desk, Documentation, Trainers)

Customer Decision-Maker

Customer Representative

Consumer

The purpose of Prepare for System Implementation is to take all possible steps
to ensure that the upcoming system deployment and transition occurs smoothly,
efficiently, and flawlessly. In the implementation of any new system, it is necessary to
ensure that the Consumer community is best positioned to utilize the system once
deployment efforts have been validated. Therefore, all necessary training activities must
be scheduled and coordinated. As this training is often the first exposure to the system for
many individuals, it should be conducted as professionally and competently as possible.
A positive training experience is a great first step towards Customer acceptance of the
system.
During System Implementation it is essential that everyone involved be absolutely
synchronized with the deployment plan and with each other. Often the performance of
deployment efforts impacts many of the Performing Organizations normal business
operations. Examples of these impacts include:
_ Consumers may experience a period of time in which the systems that they depend on
to perform their jobs are temporarily unavailable to them. They may be asked to maintain
detailed manual records or logs of business functions that they perform to be entered into
the new system once it is operational.
_ Technical Services personnel may be required to assume significant implementation
responsibilities while at the same time having to continue current levels of service on
other critical business systems.
_ Technical Support personnel may experience unusually high volumes of support
requests due to the possible disruption of day-to-day processing.
Because of these and other impacts, the communication of planned deployment
activities to all parties involved in the project is critical. A smooth deployment requires

strong leadership, planning, and communications. By this point in the project lifecycle,
the team will have spent countless hours devising and refining the steps to be followed.
During this preparation process the Project Manager must verify that all conditions that
must be met prior to initiating deployment activities have been met, and that the final
green light is on for the team to proceed. The final process within the System
Development Lifecycle is to transition ownership of the system support responsibilities to
the Performing Organization. In order for there to be an efficient and effective transition,
the Project Manager should make sure that all involved parties are aware of the transition
plan, the timing of the various transition activities, and their role in its execution.
Due to the number of project participants in this phase of the SDLC, many of the
necessary conditions and activities may be beyond the direct control of the Project
Manager. Consequently, all Project Team members with roles in the implementation
efforts must understand the plan, acknowledge their responsibilities, recognize the extent
to which other implementation efforts are dependent upon them, and confirm their
commitment.

6. CONCLUSION

The stationary Management System has been developed to satisfy all

proposed requirements. The system is highly scalable and user friendly. Almost all the
system objectives have been met. The system has been tested under all criteria. The
system minimizes the problem arising in the existing manual system and it eliminates the
human errors to zero level.
The software executes successfully by fulfilling the objectives of the project.
Further extensions to this system can be made required with minor modifications. The
invention can be implemented in digital electronic circuitry, or in computer hardware,
firmware, software, or in combinations of them. Apparatus of the invention can be
implemented in a computer program product tangibly embodied in a machine-readable
storage device for execution by a programmable processor; and method steps of the
invention can be performed by a programmable processor executing a program of
instructions to perform functions of the invention by operating on input data and
generating output

BIBLIOGRAPHY
.Elias Awath, SYSTEM ANALYSIS AND DESIGN,Tata Mc Graw Hill
Publication, Sixth Edition,2003
.S.Ramachandran,COMPUTER AIDED DESIGN, Air Walk
Publication, Third Edition,2003
.Richard Fairley,SOFTWARE ENGINEERING CONCEPTS,Tata Mc
Graw Hill Publication, Second Edition,1997
.Distributed .NET Programming in VB .NET by Tom Barnaby
Professional VB.NET, 2nd Edition by Fred Barwell, et al
The .NET Languages: A Quick Translation Guide by Brian Bischof
Programming VB.NET: A Guide for Experienced Programmers
by Gary Cornell, Jonathan Morrison
Learning Visual Basic.NET Through Applications by Clayton
Crooks II
Visual Basic .NET How to Program (2nd Edition) by Harvey M.
Deitel, Paul J. Deitel, Tem R. Nieto