Textile Shop management system

Abstract
The textile shop . This project is made in Microsoft visual studio 2008 version
3.5, designing is made by asp.net(Active server page) and the back end used is S
QL server 2000
Textile management system
application is developed for managing the
The idea of textile shop development is how to manage the textile shop in a good
manner or we can say managing the textile shop well from which people can get p
rofit or just stay out from the difficulties, how the things is proper in the sh
opping mall, what is the input in the shopping mall and what is the output how t
o track the goods are available there or which is sort. All this is auto track b
y the application from which there will be no any difficulties facing by the man
agement after all there are certain report generation based on the shopping mall
daily turnover, monthly turnover etc .

TABLE OF CONTENTS
CHAPTER NO
TITLE
PAGE NO
ABSTRACT
1.
INTRODUCTION 1.1 ABOUT THE ORGANIZATION 1.2 PROJECT DESCRIPTION
2.
SYSTEM STUDY 2.1 FEASABILITY STUDY 2.2 EXISTING SYSTEM 2.3 PROPOSED SYSTEM
3
SYSTEM SPECIFICATION 3.1 HARDWARE CONFIGURATION 3.2 SOFTWARE CONFIGURATION
4
LANGUAGE SPECIFICATION 4.1 FEATURES OF ASP .NET 4.2 FEATURES OF SQL SERVER 2000
5
SYSTEM DESIGN 5.1 INPUT DESIGN 5.2 OUTPUT DESIGN

5.3 DATABASE DESIGN 5.4 DATA FLOW DIAGRAM 5.5 ER DIAGRAM

6
SYSTEM TESTING AND MAINTENANCE 6.1 UNIT TESTING 6.2 INTEGRATION TESTING 6.3 VALI
DATION TESTING
7
SYSTEM IMPLEMENTATION 7.1 SCOPE FOR FUTURE DEVELOPMENT
8
CONCLUSION
9
BIBLIOGRAPHY
APPENDIX y y y SCREEN SHOT DATA TABLE STRUCTURE SAMPLE CODING

1. INTRODUCTION 1.1 ABOUT THE ORGANISATION

ORGANISATION PROFILE
At XYZ, We go beyond providing software solutions. We work with our client s tec
hnologies and business changes that shape their competitive advantages. Founded
in 2000, XYZ (P) Ltd. is a software and service provider that helps organization
s deploy, manage, and support their business-critical software more effectively.
Utilizing a combination of proprietary software, services and specialized exper
tise XYZ (P) Ltd. helps mid-to-large enterprises, software companies and IT serv
ice providers improve consistency, speed, and transparency with service delivery
at lower costs. XYZ (P) Ltd. helps companies avoid many of the delays, costs an
d risks associated with the distribution and support of software on desktops, se
rvers and remote devices. Our automated solutions include rapid, touch-free depl
oyments, ongoing software upgrades, fixes and security patches, technology asset
inventory and tracking, software license optimization, application self-healing
and policy management. At XYZ, we go beyond providing software solutions. We wo
rk with our clients technologies and business processes that shape their competi
tive advantages.
About The People As a team we have the prowess to have a clear vision and realiz
e it too. As a statistical evaluation, the team has more than 40,000 hours of ex
pertise in providing real-time solutions in the fields of Embedded Systems, Cont
rol systems, Micro-Controllers, c Based Interfacing, Programmable Logic Controll
er, VLSI Design And Implementation, Networking With C, ++, java, client Server T
echnologies in Java,(J2EE\J2ME\J2SE\EJB),VB & VC++, Oracle and operating system
concepts with LINUX.
Our
ion
ith
ble

Vision Dreaming a vision is possible and realizing it is our goal . Our Miss
We have achieved this by creating and perfecting processes that are in par w
the global standards and we deliver high quality, high value services, relia
and cost effective IT products to clients around the world.

1.2PROJECT DESCRIPTION
Modules:
The Project contains Six Main Modules are
1. Dealer Details 2.Item Details 3. Employee info 4. Stock info 5. Bill details
6. Report
1.Dealer Details:
This modules contains Five sub modules are a. Add Dealer info b. Edit Dealer inf
o c. Delete Dealer info d. View Dealer info e. Purchase Add Dealer info: This mo
dules contains add the new dealer details. It includes are Dealer id, name ,d.o.
b, address ,mobile no ,E-mail address And so on. Edit Dealer info:

This modules contains edit the Dealer details. Edit the name , address and phone
number and update the edit information stored in table Delete Dealer info: This
modules contains are un wanted dealer information deleted. Here Dealer details
deleted in id wise. View Dealer info: This modules contains are view the all dea
ler information view at a time and id wise viewing. Purchase: This modules conta
ins are dealer purchase the item details maintained. It includes are item name,
purchasing date , no of quantity,rate details and so on.
2.Item Details:
This modules contains Add the new item it includes item name , id,date, unit pri
ce ,manufacturing date details maintained. And view the item details, edit the i
tem details,delete the unwanted item details maintained.
3.Employee info:
This modules contains are add the new employee information, it includes are empl
oyee name ,id, d.o.b,address, mobile no, designation and edit the employee infor
mation , view the employee info, unwanted employee information deleted.
4.Stock info:
This modules contains divided into Two sub modules are

a.Old Stock b.New Stock Old stock: This modules contains are maintain the stock
details. It includes how many item stock to us. Price details maintained and tot
al stock details, take a stock date maintained. New stock: This modules contains
are maintain the new stock details.It includes are current stock calculation ,
take a stock date, ouantity date, and total stock details maintained. 5.Bill Det
ails: This modules contains divided into Two sub modules a.Old Bill b.New Bill
Old bill: This modules contains are old bill details maintained. It include purc
hase item id,name, price,billing date and total amount detailsmaintained New Bil
l: This modules contains are new bill details maintained it includes item id,nam
e, billin date , price, total amount details maintained. Report: This modules co
ntains are all report details maintained. It includes are Dealer reprt,Employee
Report,stock report and bill report.

2. SYSTEM STUDY
2.1 FEASIBILITY STUDY:
The feasibility of the project is analyzed in this phase and business proposal i
s put forth with a very general plan for the project and some cost estimates. Du
ring system analysis the feasibility study of the proposed system is to be carri
ed out. This is to ensure that the proposed system is not a burden to the compan
y. For feasibility analysis, some understanding of the major requirements for th
e system is essential.
Three key considerations involved in the feasibility analysis are
y y y
ECONOMICAL FEASIBILITY TECHNICAL FEASIBILITY SOCIAL FEASIBILITY
ECONOMICAL FEASIBILITY:
This study is carried out to check the economic impact that the system will have
on the organization. The amount of fund that the company can pour into the rese
arch and development of the system is limited. The expenditures must be justifie
d. Thus the developed system as well within the budget and this was achieved bec
ause most of the technologies used are freely available. Only the customized pro
ducts had to be purchased.

TECHNICAL FEASIBILITY:
This study is carried out to check the technical feasibility, that is, the techn
ical requirements of the system. Any system developed must not have a high deman
d on the available technical resources. This will lead to high demands on the av
ailable technical resources. This will lead to high demands being placed on the
client. The developed system must have a modest requirement, as only minimal or
null changes are required for implementing this system.
SOCIAL FEASIBILITY:
The aspect of study is to check the level of acceptance of the system by the use
r. This includes the process of training the user to use the system efficiently.
The user must not feel threatened by the system, instead must accept it as a ne
cessity. The level of acceptance by the users solely depends on the methods that
are employed to educate the user about the system and to make him familiar with
it. His level of confidence must be raised so that he is also able to make some
constructive criticism, which is welcomed, as he is the final user of the syste
m.

3. SYSTEM STUDY
3.1 HARDWARE CONFIGURATION
The hardware used for the development of the project is:
PROCESSOR RAM MONITOR HARD DISK FLOPPY DRIVE : CDDRIVE KEYBOARD
: : : :
PENTIUM IV MHz 512 MD SD RAM 15 COLOR 20 GB
1.44 MB : : LG 52X STANDARD 102 KEYS

MOUSE
:
3 BUTTONS
3.2 SOFTWARE CONFIGURATION
The software used for the development of the project is:
OPERATING SYSTEM : ENVIRONMENT .NET FRAMEWORK WEB TECHNOLOGY REPORTS BACK END :
: : : :
WINDOWS 2000 PROFESSIONAL VISUAL STUDIO .NET 2008 VERSION 3.5 ACTIVE SERVER PAGE
S.NET WEB FORM DATA GRID CONTROL SQL SERVER 2000
4. LANGAUGE SPECIFICATION
4.1 FEATURES OF ASP.NET
ASP.NET is the next version of Active Server Pages (ASP); it is a unified Web de
velopment platform that provides the services necessary for developers to build
enterprise-class Web applications. While ASP.NET is largely syntax compatible, i
t also provides a new programming model and infrastructure for more secure, scal
able, and stable applications.

ASP.NET is a compiled, NET-based environment, we can author applications in any

.NET compatible language, including Visual Basic .NET, C#, and JScript .NET. Add
itionally, the entire .NET Framework is available to any ASP.NET application. De
velopers can easily access the benefits of these technologies, which include the
managed common language runtime environment (CLR), type safety, inheritance, an
d so on.
ASP.NET has been designed to work seamlessly with WYSIWYG HTML editors and other
programming tools, including Microsoft Visual Studio .NET. Not only does this m
ake Web development easier, but it also provides all the benefits that these too
ls have to offer, including a GUI that developers can use to drop server control
s onto a Web page and fully integrated debugging support.
Developers can choose from the following two features when creating an ASP.NET a
pplication. Web Forms and Web services, or combine these in any way they see fit
. Each is supported by the same infrastructure that allows you to use authentica
tion schemes, cache frequently used data, or customize your application's config
uration, to name only a few possibilities.
Web Forms allows us to build powerful forms-based Web pages. When building these
pages, we can use ASP.NET server controls to create common UI elements, and pro
gram them for common tasks. These controls allow we to rapidly build a Web Form
out of reusable built-in or custom components, simplifying the code of a page. A
n XML Web service provides the means to access server functionality remotely. Us
ing Web services, businesses can expose programmatic interfaces to their data or
business logic, which in turn can be obtained and manipulated by client and ser
ver applications. XML Web services enable the exchange of data in client-server
or server-server scenarios, using standards like HTTP and XML messaging to move
data across firewalls. XML Web services are not tied to a particular component t
echnology or object-calling convention. As a result, programs written in any lan
guage, using any component model, and running on any operating system can access
XML Web services

Each of these models can take full advantage of all ASP.NET features, as well as
the power of the .NET Framework and .NET Framework common language runtime.
Accessing databases from ASP.NET applications is an often-used technique for dis
playing data to Web site visitors. ASP.NET makes it easier than ever to access d
atabases for this purpose. It also allows us to manage the database from your co
de .
ASP.NET provides a simple model that enables Web developers to write logic that
runs at the application level. Developers can write this code in the global.aspx
text file or in a compiled class deployed as an assembly. This logic can includ
e application-level events, but developers can easily extend this model to suit
the needs of their Web application.
ASP.NET provides easy-to-use application and session-state facilities that are f
amiliar to ASP developers and are readily compatible with all other .NET Framewo
rk APIs.
ASP.NET offers the IHttpHandler and IHttpModule interfaces. Implementing the IHt
tpHandler interface gives you a means of interacting with the low-level request
and response services of the IIS Web server and provides functionality much like
ISAPI extensions, but with a simpler programming model. Implementing the IHttpM
odule interface allows you to include custom events that participate in every re
quest made to your application.
ASP.NET takes advantage of performance enhancements found in the .NET Framework
and common language runtime. Additionally, it has been designed to offer signifi
cant performance improvements over ASP and other Web development platforms. All
ASP.NET code is compiled, rather than interpreted, which allows early binding, s
trong typing, and just-in-time (JIT) compilation to native code, to name only a
few of its benefits. ASP.NET is also easily factorable, meaning that developers
can

remove modules (a session module, for instance) that are not relevant to the app
lication they are developing. ASP.NET provides extensive caching services (both
built-in services and caching APIs). ASP.NET also ships with performance counter
s that developers and system administrators can monitor to test new applications
and gather metrics on existing applications. Writing custom debug statements to
your Web page can help immensely in troubleshooting your application's code. Ho
wever, it can cause embarrassment if it is not removed. The problem is that remo
ving the debug statements from your pages when your application is ready to be p
orted to a production server can require significant effort. ASP.NET offers the
TraceContext class, which allows us to write custom debug statements to our page
s as we develop them. They appear only when you have enabled tracing for a page
or entire application. Enabling tracing also appends details about a request to
the page, or, if you so specify, to a custom trace viewer that is stored in the
root directory of your application.
The .NET Framework and ASP.NET provide default authorization and authentication
schemes for Web applications. we can easily remove, add to, or replace these sch
emes, depending upon the needs of our application .
ASP.NET configuration settings are stored in XML-based files, which are human re
adable and writable. Each of our applications can have a distinct configuration
file and we can extend the configuration scheme to suit our requirements.

THE .NET FRAMEWORK

The .NET Framework is a new computing platform that simplifies application devel
opment in the highly distributed environment of the Internet.
OBJECTIVES OF. NET FRAMEWORK:
1. To provide a consistent object-oriented programming environment whether objec
t codes is stored and executed locally on Internet-distributed, or executed remo
tely. 2. To provide a code-execution environment to minimizes software deploymen
t and guarantees safe execution of code. 3. Eliminates the performance problems.
There are different types of application, such as Windows-based applications and
Web-based applications.To make communication on distributed environment to ensu
re that code be accessed by the .NET Framework can integrate with any other code
.
COMPONENTS OF . NET FRAMEWORK
THE COMMON LANGUAGE RUNTIME (CLR):

The common language runtime is the foundation of the .NET Framework. It manages
code at execution time, providing important services such as memory management,
thread management, and remoting and also ensures more security and robustness. T
he concept of code management is a fundamental principle of the runtime. Code th
at targets the runtime is known as managed code, while code that does not target
the runtime is known as unmanaged code.
THE .NET FRAME WORK CLASS LIBRARY: It is a comprehensive, object-oriented collec
tion of reusable types used to develop applications ranging from traditional com
mand-line or graphical user interface (GUI) applications to applications based o
n the latest innovations provided by ASP.NET, such as Web Forms and XML Web serv
ices.
The .NET Framework can be hosted by unmanaged components that load the common la
nguage runtime into their processes and initiate the execution of managed code,
thereby creating a software environment that can exploit both managed and unmana
ged features. The .NET Framework not only provides several runtime hosts, but al
so supports the development of third-party runtime hosts.
Internet Explorer is an example of an unmanaged application that hosts the runti
me (in the form of a MIME type extension). Using Internet Explorer to host the r
untime to enables embeds managed components or Windows Forms controls in HTML do
cuments.
FEATURES OF THE COMMON LANGUAGE RUNTIME:

The common language runtime manages memory; thread execution, code execution, co
de safety verification, compilation, and other system services these are all run
on CLR. Security. Robustness. Productivity. Performance.
SECURITY: The runtime enforces code access security. The security features of th
e runtime thus enable legitimate Internet-deployed software to be exceptionally
feature rich. With regards to security, managed components are awarded varying d
egrees of trust, depending on a number of factors that include their origin to p
erform file-access operations, registry-access operations, or other sensitive fu
nctions.
ROBUSTNESS:
The runtime also enforces code robustness by implementing a strict type- and cod
e-verification infrastructure called the common type system (CTS). The CTS ensur
es that all managed code is selfdescribing. The managed environment of the runti
me eliminates many common software issues.

PRODUCTIVITY: The runtime also accelerates developer productivity. For example,

programmers can write applications in their development language of choice, yet
take full advantage of the runtime, the class library, and components written in
other languages by other developers.
PERFORMANCE:
The runtime is designed to enhance performance. Although the common language run
time provides many standard runtime services, managed code is never interpreted.
A feature called just-in-time (JIT) compiling enables all managed code to run i
n the native machine language of the system on which it is executing. Finally, t
he runtime can be hosted by high-performance, server-side applications, such as
Microsoft SQL Server and Internet Information Services (IIS).
DATA ACCESS WITH ADO.NET
As you develop applications using ADO.NET, you will have different requirements
for working with data. You might never need to directly edit an XML file contain
ing data - but it is very useful to understand the data architecture in ADO.NET.
ADO.NET offers several advantages over previous versions of ADO:

Interoperability Maintainability Programmability Performance Scalability

INTEROPERABILITY:
ADO.NET applications can take advantage of the flexibility and broad acceptance
of XML. Because XML is the format for transmitting datasets across the network,
any component that can read the XML format can process data. The receiving compo
nent need not be an ADO.NET component.
The transmitting component can simply transmit the dataset to its destination wi
thout regard to how the receiving component is implemented. The destination comp
onent might be a Visual Studio application or any other application implemented
with any tool whatsoever.
The only requirement is that the receiving component be able to read XML. SO, XM
L was designed with exactly this kind of interoperability in mind.
MAINTAINABILITY:

In the life of a deployed system, modest changes are possible, but substantial,
Architectural changes are rarely attempted because they are so difficult. As the
performance load on a deployed application server grows, system resources can b
ecome scarce and response time or throughput can suffer. Faced with this problem
, software architects can choose to divide the server's business-logic processin
g and user-interface processing onto separate tiers on separate machines.
In effect, the application server tier is replaced with two tiers, alleviating t
he shortage of system resources. If the original application is implemented in A
DO.NET using datasets, this transformation is made easier.
ADO.NET data components in Visual Studio encapsulate data access functionality i
n various ways that help you program more quickly and with fewer mistakes.
PERFORMANCE:
ADO.NET datasets offer performance advantages over ADO disconnected record sets.
In ADO.NET data-type conversion is not necessary.
SCALABILITY:
ADO.NET accommodates scalability by encouraging programmers to conserve limited
resources. Any ADO.NET application employs disconnected access to data; it does
not retain database locks or active database connections for long durations.
VISUAL STUDIO .NET

Visual Studio .NET is a complete set of development tools for building ASP Web a
pplications, XML Web services, desktop applications, and mobile applications In
addition to building high-performing desktop applications, you can use Visual St
udio's powerful component-based development tools and other technologies to simp
lify team-based design, development, and deployment of Enterprise solutions.
Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same integrat
ed development environment (IDE), which allows them to share tools and facilitat
es in the creation of mixed-language solutions. In addition, these languages lev
erage the functionality of the .NET Framework and simplify the development of AS
P Web applications and XML Web services.
Visual Studio supports the .NET Framework, which provides a common language runt
ime and unified programming classes; ASP.NET uses these components to create ASP
Web applications and XML Web services. Also it includes MSDN Library, which con
tains all the documentation for these development tools.
XML WEB SERVICES
XML Web services are applications that can receive the requested data using XML
over HTTP. XML Web services are not tied to a particular component technology or
object-calling convention but it can be accessed by any language, component mod
el, or operating system. In Visual Studio .NET, you can quickly create and inclu
de XML Web services using Visual Basic, Visual C#, JScript, Managed Extensions f
or C++, or ATL Server.

XML SUPPORTS
Extensible Markup Language (XML) provides a method for describing structured dat
a. XML is a subset of SGML that is optimized for delivery over the Web. The Worl
d Wide Web Consortium (W3C) defines XML standards so that structured data will b
e uniform and independent of applications. Visual Studio .NET fully supports XML
, providing the XML Designer to make it easier to edit XML and create XML schema
s.
VISUAL BASIC .NET
Visual Basic. NET, the latest version of visual basic, includes many new feature
s. The Visual Basic supports interfaces but not implementation inheritance.
Visual basic.net supports implementation inheritance, interfaces and overloading
. In addition, Visual Basic .NET supports multithreading concept.
COMMON LANGUAGE SPECIFICATION (CLS):
Visual Basic.NET is also compliant with CLS (Common Language Specification) and
supports structured exception handling. CLS is set of rules and constructs that
are supported by the CLR (Common

Language Runtime). CLR is the runtime environment provided by the .NET Framework
; it manages the execution of the code and also makes the development process ea
sier by providing services. Visual Basic.NET is a CLS-compliant language. Any ob
jects, classes, or components that created in Visual Basic.NET can be used in an
y other CLS-compliant language. In addition, we can use objects, classes, and co
mponents created in other CLS-compliant languages in Visual Basic.NET .The use o
f CLS ensures complete interoperability among applications, regardless of the la
nguages used to create the application.
IMPLEMENTATION INHERITANCE:
Visual Basic.NET supports implementation inheritance. This means that, while cre
ating applications in Visual Basic.NET, we can drive from another class, which i
s know as the base class that derived class inherits all the methods and propert
ies of the base class. In the derived class, we can either use the existing code
of the base class or override the existing code. Therefore, with help of the im
plementation inheritance, code can be reused.
CONSTRUCTORS AND DESTRUCTORS: Constructors are used to initialize objects, where
as destructors are used to destroy them. In other words, destructors are used to
release the resources allocated to the object. In Visual Basic.NET the sub fina
lize procedure is available. The sub finalize procedure is used to complete the
tasks that must be performed when an object is destroyed. The sub finalize proce
dure is called automatically when an object is destroyed. In addition, the sub f
inalize procedure can be called only from the class it belongs to or from derive
d classes.
GARBAGE COLLECTION: Garbage Collection is another new feature in Visual Basic.NE
T. The .NET Framework monitors allocated resources, such as objects and variable
s. In addition, the .NET Framework automatically releases

memory for reuse by destroying objects that are no longer in use. In Visual Basi
c.NET, the garbage collector checks for the objects that are not currently in us
e by applications. When the garbage collector comes across an object that is mar
ked for garbage collection, it releases the memory occupied by the object.
OVERLOADING:
Overloading is another feature in Visual Basic.NET. Overloading enables us to de
fine multiple procedures with the same name, where each procedure has a differen
t set of arguments. Besides using overloading for procedures, we can use it for
constructors and properties in a class.
MULTITHREADING:
Visual Basic.NET also supports multithreading. An application that supports mult
ithreading can handle multiple tasks simultaneously, we can use multithreading t
o decrease the time taken by an application to respond to user interaction. To d
ecrease the time taken by an application to respond to user interaction, we must
ensure that a separate thread in the application handles user interaction.
STRUCTURED EXCEPTION HANDLING:
Visual Basic.NET supports structured handling, which enables us to detect and re
move errors at runtime. In Visual Basic.NET, we need to use Try Catch Finally st
atements to create exception handlers. Using Try Catch Finally statements, we ca
n create robust and effective exception handlers to improve the performance of o
ur application. 4.2 FEATURES OF SQL SERVER 2000

The OLAP Services feature available in SQL Server version 7.0 is now called SQL
Server 2000 Analysis Services. The term OLAP Services has been replaced with the
term Analysis Services. Analysis Services also includes a new data mining compo
nent. The Repository component available in SQL Server version 7.0 is now called
Microsoft SQL Server 2000 Meta Data Services. References to the component now u
se the term Meta Data Services. The term repository is used only in reference to
the repository engine within Meta Data Services SQL-SERVER database consist of
six type of objects, They are, 1. TABLE 2. QUERY 3. FORM 4. REPORT 5. MACRO
TABLE: A database is a collection of data about a specific topic.
VIEWS OF TABLE: We can work with a table in two types, 1. Design View 2. Datashe
et View

Design View To build or modify the structure of a table we work in the table des
ign view. We can specify what kind of data will be hold.
Datasheet View To add, edit or analyses the data itself we work in tables datash
eet view mode. QUERY: A query is a question that has to be asked the data. Acces
s gathers data that answers the question from one or more table. The data that m
ake up the answer is either dynaset (if you edit it) or a snapshot(it cannot be
edited).Each time we run query, we get latest information in the dynaset.Access
either displays the dynaset or snapshot for us to view or perform an action on i
t ,such as deleting or updating. FORMS: A form is used to view and edit informat
ion in the database record by record .A form displays only the information we wa
nt to see in the way we want to see it. Forms use the familiar controls such as
textboxes and checkboxes. This makes viewing and entering data easy. Views of Fo
rm: We can work with forms in several primarily there are two views, They are, 1
. Design View 2. Form View Design View To build or modify the structure of a for
m, we work in forms design view. We can add control to the form that are bound t
o fields in a table or query, includes textboxes, option buttons, graphs and pic
tures.

Form View The form view which display the whole design of the form. REPORT: A re
port is used to vies and print information from the database. The report can gro
und records into many levels and compute totals and average by checking values f
rom many records at once. Also the report is attractive and distinctive because
we have control over the size and appearance of it. MACRO : A macro is a set of
actions. Each action in macros does something. Such as opening a form or printin
g a report .We write macros to automate the common tasks the work easy and save
the time.
DataFlow Diagram:
1.SuperMarket:
Login
SuperMarket
DealerDetails
Item Details Stock Details
Bill Details Report Details

2.Login:
username
Login PassWord
3.Dealer Details:

Add Dealer info

Dealer Details
Edit Dealer info Delete Dealer info Purchase Details
4.Item Details:
ItemName Item Details Item Info Item Id PurDate ManuDate
5.Stock Details:

Old Stock
Stock New Stock
Bill Details:
Old Bill Bill Details New Bill
Billno
Pur amt
Date

Table Design

5. SYSTEM DESIGN

5.1 INPUT DESIGN

Input design is the process of converting user-originated inputs to a computer-b
ased format. Input design is one of the most expensive phases of the operation o
f computerized system and is often the major problem of a system. In the project
, the input design is made in various web forms with various methods.
For example, in the Admin form, the empty username and password is not allowed.
The username if exists in the database, the input is considered to be invalid an
d is not accepted. Likewise, the student details ,employee,course,events,scholor
s should be entered as the input by the admin.
5.2 OUTPUT DESIGN
Output design generally refers to the results and information that are generated
by the system for many end-users; output is the main reason for developing the
system and the basis on which they evaluate the usefulness of the application.
In the project, once the employees, students, events, scholor and the course are
given. It stores in to the data base. The reports here generated vividly and th
ese details can be seen through the crystal report in graph format.

6. SYSTEM TESTING AND MAINTENANCE

Testing is vital to the success of the system. System testing makes a logical as
sumption that if all parts of the system are correct, the goal will be successfu
lly achieved. In the testing process we test the actual system in an organizatio
n and gather errors from the new system operates in full efficiency as stated. S
ystem testing is the stage of implementation, which is aimed to ensuring that th
e system works accurately and efficiently. In the testing process we test the ac
tual system in an organization and gather errors from the new system and take in
itiatives to correct the same. All the front-end and back-end connectivity are t
ested to be sure that the new system operates in full efficiency as stated. Syst
em testing is the stage of implementation, which is aimed at ensuring that the s
ystem works accurately and efficiently. The main objective of testing is to unco
ver errors from the system. For the uncovering process we have to give proper in
put data to the system. So we should have more conscious to give input data. It
is important to give correct inputs to efficient testing. Testing is done for ea
ch module. After testing all the modules, the modules are integrated and testing
of the final system is done with the test data, specially designed to show that
the system will operate successfully in all its aspects conditions.Thus the sys
tem testing is a confirmation that all is correct and an opportunity to show the
user that the system works. Inadequate testing or non-testing leads to errors t
hat may appear few months later.
6.1. UNIT TESTING:
Unit testing verification efforts on the smallest unit of software design, modul
e. This is known as Module Testing. The modules are tested separately. This testing
is carried out during programming stage itself. In these testing steps, each mod
ule is found to be working satisfactorily as regard to the expected output from
the module.

6.2. INTEGRATION TESTING:

Integration testing is a systematic technique for constructing tests to uncover
error associated within the interface. In the project, all the modules are combi
ned and then the entire programmer is tested as a whole. In the integration-test
ing step, all the error uncovered is corrected for the next testing steps.
6.3. VALIDATION TESTING:
To uncover functional errors, that is, to check whether functional characteristi
cs confirm to specification or not
7. SYSTEM IMPLEMENTATION
Implementation is the stage of the project when the theoretical design is turned
out into a working system. Thus it can be considered to be the most critical st
age in achieving a successful new system and in giving the user, confidence that
the new system will work and be effective. The implementation stage involves ca
reful planning, investigation of the existing system and its constraints on implem
entation, designing of methods to achieve changeover and evaluation of changeove
r methods. Implementation is the process of converting a new system design into
operation. It is the phase that focuses on user training, site preparation and f
ile conversion for installing a candidate system. The important factor that shou
ld be considered here is that the conversion should not disrupt the functioning
of the organization.
7.1 SCOPE OF FUTURE DEVELOPMENT

Every application has its own merits and demerits. The project has covered almos
t all the requirements. Further requirements and improvements can easily be done
since the coding is mainly structured or modular in nature. Changing the existi
ng modules or adding new modules can append improvements. Further enhancements c
an be made to the application, so that the web site functions very attractive an
d useful manner than the present one.
8. CONCLUSION
The input and output data s are validated and verified. Testing and the implemen
tation are done successfully. The constraints are met and overcome successfully.
The result is concurrent.
It is concluded that the application works well and satisfy the end users. The a
pplication is tested very well and errors are properly debugged. The application
is simultaneously accessed from more than one system. Simultaneous login from m
ore than one place is tested.
Further enhancements can be made to the application, so that the application fun
ctions very attractive and useful manner than the present one. The speed of the
transactions become more enough now.

9. BIBLIOGRAPHY
Microsoft Visual Basic.NET Programmer s Cook Book: -MATTHEW MACDONALD (Tata McGr
aw Hill Edition)
Microsoft Visual Basic.NET Programmer s CookBook: -MATTHEW MACDONALD (Tata McGra
wHill Edition)
Grey Buczek, .NET developers guide 2002, Prentice-Hall India.
Benolt Marchal, VB.NET by example 2003 TataMcGraw- Hill.
System Analysis & Design Alenis Leon.
An Integral approach to software engineering Pankaj Jalole.

Screen Shots

Admin Login:
using System; using System.Data; using System.Configuration; using System.Collec
tions; using System.Web; using System.Web.Security; using System.Web.UI; using S
ystem.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System
.Web.UI.HtmlControls;
public partial class Admin_Login : System.Web.UI.Page { protected void Page_Load
(object sender, EventArgs e) {
} protected void Button1_Click(object sender, EventArgs e)

{ if (TextBox1.Text == "admin" && TextBox2.Text == "admin") { Response.Redirect(

"addproduct.aspx");
}
else { Response.Write("<script>alert('Login Error')</script>");
}
} }

Product Add:

Product Add.aspx
using System; using System.Data; using System.Configuration; using System.Collec
tions; using System.Web; using System.Web.Security; using System.Web.UI;

using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using

System.Web.UI.HtmlControls; using System.Data.SqlClient;
public partial class Admin_addproduct : System.Web.UI.Page { string a = "server=
.;uid=sa;database=ASM";
protected void Page_Load(object sender, EventArgs e) {
} protected void Button1_Click(object sender, EventArgs e) { SqlConnection con =
new SqlConnection(a); con.Open(); SqlCommand cmd = new SqlCommand("insert into
proadd values('" + TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox3.Text
+ "','" + TextBox4.Text + "','" + TextBox5.Text + "')", con); cmd.ExecuteNonQue
ry(); con.Close(); Response.Write("<script>alert('Added Successfully')</script>"
);
} }

protected void Button2_Click(object sender, EventArgs e) { TextBox1.Text = ""; T

extBox2.Text = ""; TextBox3.Text = ""; TextBox4.Text = ""; TextBox5.Text = "";
} }

using System; using System.Data; using System.Configuration; using System.Collec

tions; using System.Web; using System.Web.Security;

using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebCon

trols.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient;
public partial class Admin_Employeeadd : System.Web.UI.Page {
string a = "server=.;uid=sa;database=ASM";
protected void Page_Load(object sender, EventArgs e) {
} protected void Button1_Click(object sender, EventArgs e) {
SqlConnection con = new SqlConnection(a); SqlCommand cmd = new SqlCommand("inser
t TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox4.Text + "','" + TextBo
x5.Text + "','" + TextBox7.Text + "','" + TextBox8.Text + "','" + TextBox10.Text
+ "','" + TextBox11.Text + "','" TextBox13.Text + "')", con); cmd.ExecuteNonQue
ry(); con.Close(); Response.Write("<script>alert('Added Successfully')</script>"
); into empadd values('" + TextBox3.Text + "','" + TextBox6.Text + "','" + TextB
ox9.Text + "','" + + TextBox12.Text + "','" +

} protected void Button2_Click(object sender, EventArgs e) { TextBox1.Text = "";

TextBox2.Text = ""; TextBox3.Text = ""; TextBox4.Text = ""; TextBox5.Text = "";
TextBox6.Text = ""; TextBox7.Text = ""; TextBox8.Text = ""; TextBox9.Text = "";
TextBox10.Text = ""; TextBox11.Text = ""; TextBox12.Text = ""; TextBox13.Text =
"";
} }