ABSTRACT

The project entitled as “DECORED ONLINE ART GALLERY FOR

SHOPPING PROVIDENCE ASSISTANCE” has been developed under ASP.Net as a
front end and SQL Server as a back end. The coding language used for web page
development is VB .Net.

The main of this project is to sell the art gallery products online, which is painted
by members registered on this website. In this website admin allows member to register
their details online. It contains information such as member id, name, address, mobile
number and password. Therefore each member has unique username and password.

After the registration process the members are allowed to upload their art gallery
product, for customer’s view. Only after the registration customer can views the various
category of product which is uploaded by each member in website. Customer can able to
order any king of art using this portal. Member can approve or reject the buying request
made by customer. In addition admin views frequently selling product of each member.

Various reports such as List of member and user requests rose by them and
approved requests can be generated. Thus the web site helps to improve the environment
in an efficient manner.
 1. INTRODUCTION

1.1 ABOUT THE PROJECT

The main aim of this web site is to make easier the art sale process without less
effort. In current system the artist need to face more difficulties to sale his/her product
without web interface. Manual effort is needed more to sale and reaches the product to
customers. Here the web interface provides registration portal to those artists. After the
registration process the members are allowed to upload their art gallery product, for
customer’s view. Only after the registration customer can views the various category of
product which is uploaded by each member in website. Customer can able to order any
king of art using this portal. Member can approve or reject the buying request made by
customer. In addition admin views frequently selling product of each member.

The main objectives of this project are

1. To make user request through online, whose can receive the items through online.
2. To reducing the traversal time.
3. To verify stock through online.
4. To improve sales volume.
5. To improve customer satisfaction
1.2 SYSTEM SPECIFICATION

HARDWARE CONFIGURATION

This section gives the details and specification of the hardware on which the
system is expected to work.

Processor : Dual Core or Higher

Hard Disk Capacity : 500 GB
RAM : 4 GB RAM
Monitor : 15’ Color
Keyboard : 102 keys
Mouse : Optical Mouse

SOFTWARE CONFIGURATION

This section gives the details of the software that are used for the development.

Software Tool : Visual Studio 2010

Front-End : ASP .Net
Back-End : MS SQL Server 2008
Operating System : Windows 10
1.2.3 SELECTION OF SOFTWARE

THE .NET FRAMEWORK

The .NET Framework is a new computing platform that simplifies application
development in the highly distributed environment of the Internet.

OBJECTIVES OF .NET FRAMEWORK

1. To provide a consistent object-oriented programming environment whether object codes

is stored and executed locally on Internet-distributed, or executed remotely.
2. To provide a code-execution environment to minimizes software deployment 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 ensure
that code be accessed by the .NET Framework can integrate with any other code.

COMPONENTS OF .NET FRAMEWORK

1. 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, remoting and also ensures more security and
robustness.

The concept of code management is a fundamental principle of the runtime. Code

that 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 collection of reusable types used to develop

applications ranging from traditional command-line or graphical user interface (GUI)
applications to applications based on the latest innovations provided by ASP.NET, such as
Web Forms and XML Web services.

The .NET Framework can be hosted by unmanaged components that load the
common language runtime into their processes and initiate the execution of managed code,
thereby creating a software environment that can exploit both managed and unmanaged
features. The .NET Framework not only provides several runtime hosts, but also supports
the development of third-party runtime hosts.

Internet Explorer is an example of an unmanaged application that hosts the

runtime (in the form of a MIME type extension). Using Internet Explorer to host the
runtime to enables embeds managed components or Windows Forms controls in HTML
documents.

FEATURES OF THE COMMON LANGUAGE RUNTIME

The common language runtime manages memory; thread execution, code execution,
code 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 the runtime thus
enable legitimate Internet-deployed software to be exceptionally feature rich. With regards
to security, managed components are awarded varying degrees of trust, depending on a
number of factors that include their origin to perform file-access operations, registry-
access operations, or other sensitive functions.

ROBUSTNESS
 The runtime also enforces code robustness by implementing a strict type- and
code-verification infrastructure called the common type system(CTS). The CTS ensures
that all managed code is self-describing. The managed environment of the runtime
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
runtime provides many standard runtime services, managed code is never interpreted. A
feature called just-in-time (JIT) compiling enables all managed code to run in the native
machine language of the system on which it is executing. Finally, the 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
containing 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 component need
not be an ADO.NET component.
 The transmitting component can simply transmit the dataset to its destination
without regard to how the receiving component is implemented. The destination
component 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,
XML 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 become
scarce and response time or throughput can suffer. Faced with this problem, software
architects can choose to divide the server's business-logic processing and user-interface
processing onto separate tiers on separate machines.

In effect, the application server tier is replaced with two tiers, alleviating the
shortage of system resources. If the original application is implemented in ADO.NET
using datasets, this transformation is made easier. ADO.NET data components in Visual
Studio encapsulate data access functionality in 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
applications, XML Web services, desktop applications, and mobile applications In
addition to building high-performing desktop applications, you can use Visual Studio's
powerful component-based development tools and other technologies to simplify team-
based design, development, and deployment of Enterprise solutions.

Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same
integrated development environment (IDE), which allows them to share tools and
facilitates in the creation of mixed-language solutions. In addition, these languages
leverage the functionality of the .NET Framework and simplify the development of ASP
Web applications and XML Web services.

Visual Studio supports the .NET Framework, which provides a common language
runtime and unified programming classes; ASP.NET uses these components to create ASP
Web applications and XML Web services. Also it includes MSDN Library, which contains
all the documentation for these development tools.

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 easier by providing services.

Visual Basic .NET is a CLS-compliant language. Any objects, classes, or

components that created in Visual Basic .NET can be used in any other CLS-compliant
language. In addition, we can use objects, classes, and components created in other CLS-
compliant languages in Visual Basic.NET .The use of CLS ensures complete
interoperability among applications, regardless of the languages used to create the
application.

IMPLEMENTATION INHERITANCE
 Visual Basic.NET supports implementation inheritance. This means that, while
creating applications in Visual Basic. NET, we can drive from another class, which is
known as the base class that derived class inherits all the methods and properties 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 implementation inheritance, code
can be reused.

CONSTRUCTORS AND DESTRUCTORS

Constructors are used to initialize objects, whereas 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 finalize 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 procedure is called automatically when an object is destroyed. In addition, the sub
finalize procedure can be called only from the class it belongs to or from derived classes.

GARBAGE COLLECTION
Garbage Collection is another new feature in Visual Basic.NET. The .NET
Framework monitors allocated resources, such as objects and variables. In addition,
the .NET Framework automatically releases memory for reuse by destroying objects that
are no longer in use. In Visual Basic.NET, the garbage collector checks for the objects that
are not currently in use by applications. When the garbage collector comes across an
object that is marked for garbage collection, it releases the memory occupied by the object.

OVERLOADING
Overloading is another feature in Visual Basic .NET. Overloading enables us to
define multiple procedures with the same name, where each procedure has a different 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
multithreading can handle multiple tasks simultaneously, we can use multithreading to
decrease the time taken by an application to respond to user interaction. To decrease 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
remove errors at runtime. In Visual Basic .NET, we need to use Try…Catch…Finally
statements to create exception handlers. Using Try…Catch…Finally statements, we can
create robust and effective exception handlers to improve the performance of our
application.

ASP.NET
ASP.NET is a web application framework developed and marketed by Microsoft to
allow programmers to build dynamic web sites, web applications and web services.
It was first released in January 2002 with version 1.0 of the .NET Framework, and
is the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built
on the Common Language Runtime (CLR), allowing programmers to write ASP.NET
code using any supported .NET language. The ASP.NET SOAP extension framework
allows ASP.NET components to process SOAP messages.

ADVANTAGES OF USING ASP.NET

 ASP.NET drastically reduces the amount of code required to built large
applications.
 ASP.NET makes development simpler and easier to maintain with an event-driven,
Server-side programming mode.
 ASP.NET pages are easy to write and maintain because the source code and
HTML are together.
 The source code is executed on the server. The pages have lots of power and
Flexibility by this approach.

CODE-BEHIND MODEL
Microsoft recommends dealing with dynamic program code by using the code-
behind model, which places this code in a separate file or in a specially designated script
tag. Code-behind files typically have names like default, while the page file is
MyPage.aspx (same filename as the page file (ASPX), but with the final extension
denoting the page language). This practice is automatic in Microsoft Visual Studio and
other IDEs. When using this style of programming, the developer writes code to respond
to different events, like the page being loaded, or a control being clicked, rather than a
procedural walk through the document. ASP.NET's code-behind model marks a departure
from Classic ASP in that it encourages developers to build applications with separation of
presentation and content in mind. In theory, this would allow a web designer, for example,
to focus on the design markup with less potential for disturbing the programming code that
drives it. This is similar to the separation of the controller from the view in model-view-
controller frameworks.

FEATURES OF SQL-SERVER
Microsoft SQL Server is a relational model database server produced by
Microsoft. Its primary query languages are T-SQL and ANSI SQL.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 component. 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 use the term Meta Data Services. The term
repository is used only in reference to the repository engine within Meta Data Services

INTERNET INTEGRATION
The SQL Server 2000 database engine includes integrated XML support. It also
has the scalability, availability, and security features required to operate as the data storage
component of the largest Web sites. The SQL Server 2000 programming model is
integrated with the Windows DNA architecture for developing Web applications, and SQL
Server 2000 supports features such as English Query and the Microsoft Search Service to
incorporate user-friendly queries and powerful search capabilities in Web applications.

SCALABILITY AND AVAILABILITY

The same database engine can be used across platforms ranging from laptop
computers running Microsoft Windows® 98 through large, multiprocessor servers running
Microsoft Windows 2000 Data Center Edition. SQL Server 2000 Enterprise Edition
supports features such as federated servers, indexed views, and large memory support that
allow it to scale to the performance levels required by the largest Web sites.

ENTERPRISE-LEVEL DATABASE FEATURES

The SQL Server 2000 relational database engine supports the features required to
support demanding data processing environments. The database engine protects data
integrity while minimizing the overhead of managing thousands of users concurrently
modifying the database. SQL Server 2000 distributed queries allow you to reference data
from multiple sources as if it were a part of a SQL Server 2000 database, while at the same
time, the distributed transaction support protects the integrity of any updates of the
distributed data. Replication allows you to also maintain multiple copies of data, while
ensuring that the separate copies remain synchronized. You can replicate a set of data to
multiple, mobile, disconnected users, have them work autonomously, and then merge their
modifications back to the publisher.

EASE OF INSTALLATION, DEPLOYMENT, AND USE

SQL Server 2000 includes a set of administrative and development tools that
improve upon the process of installing, deploying, managing, and using SQL Server across
several sites. SQL Server 2000 also supports a standards-based programming model
integrated with the Windows DNA, making the use of SQL Server databases and data
warehouses a seamless part of building powerful and scalable systems. These features
allow you to rapidly deliver SQL Server applications that customers can implement with a
minimum of installation and administrative overhead.

DATA WAREHOUSING
SQL Server 2000 includes tools for extracting and analyzing summary data for
online analytical processing. SQL Server also includes tools for visually designing
databases and analyzing data using English-based questions.
 2. SYSTEM STUDY

2.1 EXISTING SYSTEM

The existing system is in offline. Selling of art is made manually, so there is no

way of gallery promotion and business development. So a new proposed system is needed
to overcome these drawbacks.

2.1.1 DRAWBACKS OF EXISTING SYSTEM

The existing system has following disadvantages,

 Promoting art gallery is less possible.
 Less variety of art is accessed.
 More time is required for approaching galleries.
 Existing system has poor communication between member and customer.
 More clerical work is needed for maintaining the data.
 Sales report can’t be obtained easily.
2.2 PROPOSED SYSTEM

The proposed system is web based application. This project helps to sale art gallery
products online using this web application. In this website customers can view various
category of handmade product and can make their own order online.

2.2.1 ADVANTAGES OF PROPOSED SYSTEM

The proposed system has following advantages,

 Customer can easily track the galleries.
 Sellers will have a great platform for posting art.
 Provides option for viewing frequently moving art of each member
 The customers can make request through online.
 Reducing the traversal time between personals.
 Tracking order is easier since it is a web application.
 3. SYSTEM DESIGN AND DEVELOPMENT

3.1 INPUT DESIGN

Input Design is one of the most expensive phases of the operation of

computerized system and it is often the major problem of a system. A large number
of problems with a system can usually be tracked backs to fault input design and
method. Needless to say, therefore, that the input data is the life blood of a system
and have to be analyzed and designed with utmost case and consideration. The
decisions made during the input design are,
 To provide cost effective method of input.
 To achieve the highest possible level of accuracy.
 To ensure that the input is understand by the user.

System analysis decide the following input design details like, what data to input,
what medium to use, how the data should be arranged or coded, data items and
transactions needing validations to detect errors and at last the dialogue to guide user in
providing input.

Input data of a system may not be necessarily is raw data captured in the system
from scratch. These can also be the output of another system or subsystem. The design of
input covers all the phases of input from the creation of initial data to actual entering of the
data to the system for processing. The design of inputs involves identifying the data
needed, specifying the characteristics of each data item, capturing and preparing data fro
computer processing and ensuring correctness of data.

Input design is the process of converting user-originated inputs to a computer-

based format. Input design is one of the most expensive phases of the operation of
computerized system and is often the major problem of a system.Any Ambiguity in input
leads to a total fault in output. The goal of designing the input data is to make data entry as
easy and error free as possible.
INPUT FORMS

ADD CATEGORY

In this form, admin adds the category details such as category id, category name,
description and saved into database.

ADD PRODUCT
In this form, member uploads their product with the product name, product id,
product description and rate and saved into database. This helps the customer to choose the
right product.

ADD STOCK
In this form member add the stocks to the existing product by filling up the
appropriate details which are all stored in the database using SQL server.
3.2 OUTPUT DESIGN

Computer output is the most important direct source of information to the user.
Outputs computers are required primarily to communicate the results of processing to the
users. They are also used to provide permanent copy of these results for rate reference.
Thus it is designed in a user –friendly way to avoid user burden.
The output design refers to the results and information that are generated by the
system form many end users. To produce the outputs which are displayed in a screen.
Efficient and intelligent output design improves the system relationships with the users
and help in decision making. The output of the system is in the form of reports. The
following reports are generated in the system.

OUTPUT FORMS

VIEW CATEGORY
In this module, customer views the category details such as category id, category
name, descriptions to know the category available under sale.

VIEW MEMBER PRODUCT

In this module, admin view the product upload by member with their product
description.

VIEW APPROVE ORDER

In this module, admin view the order status such as order id, order name and status
description.
3.3 DATABASE DESIGN

The most important consideration in designing the database is how information

will be used. The main objectives of designing a database are:

Data Integration:
In a database, information from several files are coordinated, accessed and
operated upon as through it is in a single file. Logically, the information are centralized,
physically, the data may be located on different devices, connected through data
communication facilities.

Data Integrity
Data integrity means storing all data in one place only and how each application to
access it. This approach results in more consistent information, one update being sufficient
to achieve a new record status for all applications, which use it. This leads to less data
redundancy; data items need not be duplicated; a reduction in the direct access storage
requirement.

Data Independence:
Data independence is the insulation of application programs from changing aspects
of physical data organization. This objective seeks to allow changes in the content and
organization of physical data without reprogramming of applications and to allow
modifications to application programs without reorganizing the physical data.
The tables needed for each module were designed and the specification of each and
every column was given based on the records and details collected during record
specification of the system study.
TABLE STRUCTURE

Table Name: Admin Table

Description: This table is used to admin login into the website

FIELD NAME DATA TYPE SIZE CONSTRAINTS

Username Varchar 15 Primary key
Password Varchar 15 Not Null

Table Name: Category Table

Description: This table is used to store the product category details

FIELD NAME DATA TYPE SIZE CONSTRAINTS

Category_Id int 4 Primary key
Category_name varchar 50 Not Null
Description varchar 500 Not Null

Table Name: Customer Table

Description: This table is used to store the Customer details

FIELD NAME DATA TYPE SIZE CONSTRAINTS

Customer_Id varchar 50 Primary key
Customer_name varchar 50 Not Null
Gender varchar 50 Not Null
Address varchar 50 Not Null
Email_id varchar 50 Not Null
Contact_no varchar 50 Not Null
Password varchar 50 Not Null
Table Name: Member Table
Description: This table is used to store the Member details

FIELD NAME DATA TYPE SIZE CONSTRAINTS

Member_Id varchar 50 Primary key
Member_name varchar 50 Not Null
Gender varchar 50 Not Null
Address varchar 50 Not Null
Email_id varchar 50 Not Null
Contact_no varchar 50 Not Null
Password varchar 50 Not Null

Table Name: Invoice Table

Description: This table is used to store the Customer Invoice details

FIELD NAME DATA TYPE SIZE CONSTRAINTS

Invoice_id int 4 Primary key
Member_id varchar 50 Foreign Key
Member_name varchar 50 Not Null
Product_id int 4 Not Null
Product_name varchar 50 Not Null
Category varchar 50 Foreign Key
Initial_price numeric 9 Not Null
Tax numeric 9 Not Null
Gross_price numeric 9 Not Null
Quantity float 8 Not Null
Total numeric 9 Not Null
Description varchar 500 Not Null
Table Name: Rating Table
Description: This table is used to store the Customer Product rating details

FIELD NAME DATA TYPE SIZE CONSTRAINTS

SNO Int 4 Primary key
Customer_id varchar 50 Foreign Key
Product_id varchar 50 Foreign Key
Product_name varchar 50 Not Null
Rating int 4 Not Null

Table Name: SalesList Table

Description: This table is used to store the Customer Product SalesList details

FIELD NAME DATA TYPE SIZE CONSTRAINTS

Invoice_id int 4 Primary key
Product_id int 4 Foreign Key
Product_name varchar 50 Not Null
Category varchar 50 Not Null
Price numeric 9 Not Null
Quantity float 8 Not Null
Total numeric 9 Not Null
Table Name: Sales Table
Description: This table is used to store the Sales details

FIELD NAME DATA TYPE SIZE CONSTRAINTS

Invoice_id int 4 Primary key
Customer_id varchar 50 Foreign Key
Customer_name varchar 50 Not Null
Quantity float 8 Not Null
Total numeric 9 Not Null
status varchar 500 Not Null

Table Name: Stock Table

Description: This table is used to store the Stock details

FIELD NAME DATA TYPE SIZE CONSTRAINTS

Member_id varchar 50 Primary key
Product_id int 4 Foreign Key
Product_name varchar 50 Not Null
Initial_Price numeric 9 Not Null
Tax numeric 9 Not Null
Gross_Price numeric 9 Not Null
Selling_Price numeric 9 Not Null
Quantity float 8 Not Null
Category varchar 50 Not Null
Image varchar 500 Not Null
Description varchar 50 Not Null
Rating varchar 50 Not Null
.
3.4 SYSTEM DEVELOPMENT

3.4.1 DESCRIPTION OF MODULES

The following are the modules in the project.

 ADMIN
o ADD CATEGORY
o ADD ITEM
o ADD MEMBER
o VIEW MEMBER’S PRODUCT
o VIEW APPROVE ORDER
o VIEW FREQUENTLY MOVED PRODUCT

 MEMBER
o VIEW PROFILE
o UPLOAD PRODUCT
o VIEW REQUEST

 CUSTOMER
o VIEW CATEGORY
o VIEW ITEMS
o ADD ORDER
o VIEW STATUS
ADMIN

ADD CATEGORY
In this module, admin adds the category details such as category id, category name,
description and saved into database.

ADD ITEM
In this module, admin add the item detail that contains item code, item name,
description, available stock and saved into database.

ADD MEMBER
In this module, admin add the member details such as member name, address,
mobile number, and city and saved into database.

VIEW MEMBER’S PRODUCT

In this module, admin view the product upload by member with their product
description.

VIEW APPROVE ORDER

In this module, admin view the order status such as order id, order name and status
description.

VIEW FREQUENTLY MOVED PRODUCT

In this module, admin view the frequently moved handmade items with the product
name, description which helps other users to choose best product.
MEMBER

VIEW PROFILE
In this module, member view the profile of other members such as member name,
member id, contact number and address details for further use.

UPLOAD PRODUCT
In this module, member uploads their product with the product name, product id,
product description and rate and saved into database. This helps the customer to choose the
right product.

VIEW REQUEST
In this module the member view the request added by the customers with their
name, product like to purchase and add the status for their request.

CUSTOMER

VIEW CATEGORY
In this module, customer views the category details such as category id, category
name, descriptions to know the category available under sale.

VIEW ITEMS
In this module the admin views the item detail that contains item code, item name,
description, available stock and saved into database

ADD ORDER
The order details consist of order no, order date, customer code, customer name
along with quantity and rate.

VIEW STATUS
In this module, customer can view their order status such as order id,oder name,
description and order status such as approval or reject.
 4. SYSTEM TESTING AND IMPLEMENTATION

4.1 SYSTEM TESTING

After the source code has been completed, documented as related data structures.
Completion of the project has to undergo testing and validation where there is subtitle and
definite attempt to get errors. The project developer treats lightly, designing and execution
of the project test that will demonstrates that the program works rather than uncovering
errors, unfortunately errors will be present and if the project developer doesn’t found
errors, the user will find out.

The project developer is always responsible for testing the individual units i.e.
modules of the program. In many cases, developer should conduct the integration testing
i.e. the testing step that leads to the construction of the complete program structure.

This project has undergone the following testing procedures to ensure its
correctness.

 UNIT TESTING
 INTEGRATION TESTING
 VALIDATION TESTING

UNIT TESTING

In unit testing, user has to test the programs making up the system. For this reason,
Unit testing sometimes called as Program testing. The software units in a system are the
modules and routines that are assembled and integrated to perform a specific function.
In this project, all modules are tested individually like given all the fields and can
be updated for all criteria.
INTEGRATION TESTING

Integration testing is a systematic technique for constructing the program structure.

While at the same time conducting tests to uncover errors associated with interfacing. The
objective is to take unit tested modules and build a program structure that has been
dictated by design.
In this integration testing its done using the main module and based on the type of
integration testing the subordinate tables and other criteria along with their path, is
replaced one at a time with actual modules.
In the project, after integrating the all modules like complaint and service update
are tested with their integration and that could integrated and manipulated with respect to
the to and fro in between modules.

VALIDATION TESTING

It is said that validation is successful when the software functions in a systematic

manner that can be reasonably accepted by the customers. This type of testing is very
important because it is the only way to check whether the requirements given by user have
been completely fulfilled.

The input given to various forms are validated effectively. The input is given for
complaints details and service details. Each module is tested independently. In this project,
code, username and password are validated successfully.
4.2 SYSTEM IMPLEMENTATION

When the initial design was done for the system, the client was consulted for the
acceptance of the design so that further proceedings of the system development can be
carried on. After the development of the system a demonstration was given to them about
the working of the system. The aim of the system illustration was to identify any
malfunction of the system.

After the management of the system was approved the system implemented in the
concern, initially the system was run parallel with existing manual system. The system has
been tested with live data and has proved to be error free and user friendly.
Implementation is the process of converting a new or revised system design into an
operational one when the initial design was done by the system; a demonstration was
given to the end user about the working system. This process is uses to verify and identify
any logical mess working of the system by feeding various combinations of test data.

After the approval of the system by both end user and management the system was
implemented. A product software implementation method is a blueprint to get users and/or
organizations running with a specific software product. The method is a set of rules and
views to cope with the most common issues that occur when implementing a software
product: business alignment from the organizational view and acceptance from the human
view.

The implementation of product software, as the final link in the deployment chain
of software production, is in a financial perspective of a major issue. The Implementation
methodology includes four phases - Discovery, System Development, User Acceptance
Testing and Production Rollout. It’s easy to be overwhelmed by slick marketing
presentations, particularly when the sales force is talking about things that most people
don’t completely understand. Showmanship gets in the way of real capabilities. Unless the
review team is judging each vendor against the same list of needs, with the same
understanding of the significance of each rating, “likeability” can win over capability.
These implementation phases are designed to provide clients with a seamless
transition from an existing electronic or paper-based system to Sigmund while ensuring all
aspects of a client’s operations are accounted for by the software. The Sigmund project
team, comprised of individuals with clinical, billing and operations experience, is
equipped with the skills and tools to manage the entire process from system requirements
gathering to deployment. Sigmund provides various levels of support, depending on client
needs, including client-side Project Management.
The Discovery Phase is preceded by a Project Kick-off Work-session that includes
application demonstrations, completion and review of requirements and configuration
questionnaires, identification of key client documentation, as well as consultation on
possible process re-engineering needs. The Project Kick-off provides your organization
with the opportunity to not only introduce the Sigmund Project Team to your organization,
but also to define and structure your organization’s Project Team.
System implementation is made up of many activities. The six major activities are
as follows.

CODING
Coding is the process of whereby the physical design specifications created by the
analysis team turned into working computer code by the programming team.

INSTALLATION
Installation is the process during which the current system is replaced by the new
system. This includes conversion of existing data, software, and documentation and work
procedures to those consistent with the new system.

DOCUMENTATION
It is result from the installation process, user guides provides the information of
how the use the system and its flow.

TRAINING AND SUPPORT

Training plan is a strategy for training user so they quickly learn to the new system.
The development of the training plan probably began earlier in the project. As part of the
proven implementation methodology, every customer gets Administrator Training for each
of the applications they're implementing. The trainer will deliver the Administrator
Training on-site, face-to-face, to a maximum of system administrators, so each learner gets
personalized attention and can ask and get specific answers to questions. If it's more
convenient for them and they can be offered the training facilities.
 5. CONCLUSION

The new system eliminates the difficulties in the existing system. It is developed in
a user-friendly manner. The aim of the project is to generate data to carry out the order
details and improve communication between admin and customer.

 A good documentation of user-friendly features had been incorporated in the

system.
 The system has been introduced to eliminate human error.
 To minimize the time consumption and clerical work.
 The reports will have the accuracy and error free calculation and stylish, neat and
clear presentation.
 6. SCOPE FOR FUTURE ENHANCEMENTS

Future of this project can be easily updated. To achieve the benefits that expected
from the user must understand the overall system and they must be able to carry out their
specific tasks effectively. The successful implementation depends upon the right people at
the right time.

The future work considers the implementation and evaluation of the proposed sub
optimal solution on an online ticketing based customer support. The updated tickets details
are send to through mail as well as ‘SMS’ to the customers and administrator mail in
future. The engineers tickets are send through ‘SMS’ who are working in the organization
after assigned by the administrator.

The future enhancement includes a more advances and secures the data which will
be incorporate all the methods, which are convenient for the company. The future
enhancement could be converting the entire application into new technology. Any
additional features can be included with this system without affecting the existing
architecture of module description.

The proposed system has so many advanced features than the existing system by
means of user friendliness. Any additional feature can be included with this system
without affecting the existing architecture of module description.
 7. BIBLIOGRAPHY

TEXT BOOKS
 Alistair MeMommien, “Object-Oriented Programming in Visual Basic.NET”,
Pearson Education, and ISBN: 81-297-0649-0, First Indian Reprint 2004.
 Jittery R.Shapiro, “The Complete Reference Visual Basic. NET” Edition 2002,
Tata McGraw-Hill, Publishing Company Limited, New Delhi.
 Robert D,Schncider, Jettey R.Garbus, “Optimizing SQL Server”, Second Edition,
Pearson Education Asia, ISBN : 981-4035-20-3

WEB REFERENCES

1. http://msdn.microsoft.com
2. http://www.vbdotnetheaven.com
3. http://www.codeproject.com
4. http://www.programmersheaven.com
 8. APPENDIX

A. SYSTEM FLOW DIAGRAM

Art Gallery

Admin Member Customer

Add Registration Registration

Category

View Product Upload View Art

Product
Add/ View
View Invoice Update Rating
Stock Add Order

View Stock
View
View Delivery
Product Details
Approve
Upload
Product Delivery
Status
View
Frequently
Moved
Product
B. DATA FLOW DIAGRAM

LEVEL 1

Art Gallery

Customer
Login

Add
View View Order
Category Items

Order
Category Items

View
Order
Status
LEVEL 2

Art Gallery

Customer
Login

Add
View View Order
Category Items

Order
Category Items

View
Order
Status
C. SCREEN SHOTS

HOME
CUSTOMER REGISTRATION
ADD ARTIST
LOGIN
VIEW ARTIST
VIEW CUSTOMER
ADD PAINTING
APPROVE PAINTING
VIEW PAINTING
VIEW INVOICE
VIEW PAINTING
ORDER PAINTING
ADD RATING
VIEW HIGHLY MOVING PAINTING
CONTACT
D. SAMPLE CODING

PAINTING ADDITION

Imports System.Data

Imports System.Data.SqlClient

Partial Class AddCategory

Inherits System.Web.UI.Page

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs)

Handles Me.Load

loaddata()

If IsPostBack = False Then

ddCategory.Items.Add("")

Db.cmd.CommandText = "Select DISTINCT Category_Name From

CategoryTable"

Dim r As SqlDataReader = Db.cmd.ExecuteReader

While r.Read

ddCategory.Items.Add(r(0).ToString())

End While

r.Close()

End If

End Sub
 Private Sub loaddata()

Db.cmd.CommandText = "Select MAx(Product_Id) + 1 From StockTable "

If Db.cmd.ExecuteScalar() Is DBNull.Value Then

txtId.Text = 1

Else

txtId.Text = Db.cmd.ExecuteScalar()

End If

End Sub

Protected Sub btnSubmit_Click(ByVal sender As Object, ByVal e As

System.EventArgs) Handles btnSubmit.Click

Try

If Not FileUpload1.PostedFile Is Nothing Then

FileUpload1.PostedFile.SaveAs(Server.MapPath(".") & "\Image\Product\"

& Session("username") & FileUpload1.FileName.ToString())

End If

Db.cmd.CommandText = "Insert Into StockTable Values('" &

Session("username").ToString() & "','" & txtId.Text & "','" & txtName.Text & "','"
& txtInitialPrice.Text & "','" & txtTax.Text & "','" & txtGrossPrice.Text & "',0,'','"
& ddCategory.Text & "','" & Session("username") & FileUpload1.FileName & "','"
& txtDesc.Text & "','','PENDING')"

Db.cmd.ExecuteNonQuery()

txtId.Text = ""

txtName.Text = ""

txtInitialPrice.Text = ""
 txtTax.Text = ""

txtGrossPrice.Text = ""

ddCategory.SelectedIndex = 0

txtDesc.Text = ""

lblStatus.Text = "Product Addition Successfull!"

loaddata()

Catch ex As Exception

lblStatus.Text = ex.Message

End Try

End Sub

Protected Sub Button1_Click(ByVal sender As Object, ByVal e As

System.EventArgs) Handles Button1.Click

If txtInitialPrice.Text <> "" And txtTax.Text <> "" Then

txtGrossPrice.Text = Val(txtInitialPrice.Text) * ((100 + Val(txtTax.Text)) /

100)

End If

End Sub

End Class
CUSTOMER REGISTRATION

Partial Class Registration

Inherits System.Web.UI.Page

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs)

Handles Me.Load

Db.cmd.CommandText = "Select COUNT(Customer_Id) + 1 From

CustomerTable "

If Db.cmd.ExecuteScalar() Is DBNull.Value Then

txtId.Text = "Customer" & "001"

Else

Dim id As Integer

id = Db.cmd.ExecuteScalar()

txtId.Text = "Customer" & Format(id, "000")

End If

End Sub

Protected Sub btnSubmit_Click(ByVal sender As Object, ByVal e As

System.EventArgs) Handles btnSubmit.Click

Try

Db.cmd.CommandText = "Insert Into CustomerTable Values('" & txtId.Text

& "','" & txtName.Text & "','" & ddGender.Text & "','" & txtAddress.Text & "','"
& txtContactNo.Text & "','" & txtEmailId.Text & "','" & txtPassword.Text & "')"

Db.cmd.ExecuteNonQuery()
 txtId.Text = ""

txtName.Text = ""

ddGender.SelectedIndex = 0

txtContactNo.Text = ""

txtEmailId.Text = ""

txtPassword.Text = ""

txtAddress.Text = ""

lblStatus.Text = "Customer Registration Successfull!"

Db.cmd.CommandText = "Select COUNT(Customer_Id) + 1 From

CustomerTable "

Dim id As Integer

id = Db.cmd.ExecuteScalar()

txtId.Text = "Customer" & String.Format("{0:000}", id)

Catch ex As Exception

lblStatus.Text = ex.Message

End Try

End Sub

End Class