Professional Documents
Culture Documents
Furniture Management System Project Report1
Furniture Management System Project Report1
INTRODUCTION
An online furniture shop that allows users to check for various furniture available at the
online store and purchase online. The project consists of list of furniture products displayed in
various models and designs. The user may browse through these products as per categories. If
the user likes a product he may add it to his shopping cart. Once user wishes to checkout he must
register on the site first. He can then login using same id password next time. Now he may pay
through a credit card or cash on delivery. Once the user makes a successful transaction he gets a
copy of the shopping receipt on his email id. Here we use HTML, CSS, JavaScript, JQurey to
make the entire frontend. And XAMPP serves as a backend to store furniture lists and inventory
data Thus the online furniture shopping project brings an entire furniture shop online and makes
it easy for both buyer and seller to make furniture deals.
1
1.2 SYSTEM SPECIFICATION
Computer : Personal
Server-side applications in the managed world are implemented through runtime hosts.
Unmanaged applications host the common language runtime, which allows your custom
managed code to control the behavior of the server. This model provides you with all the features
of the common language runtime and class library while gaining the performance and scalability
of the host server.
The following illustration shows a basic network schema with managed code running in
different server environments. Servers such as AWS Access can perform standard operations
while your application logic executes through the managed code.
2
AWS is the hosting environment that enables developers to use the Various Framework to
target Web-based applications. However, ASW is more than just a runtime host; it is a complete
architecture for developing Web sites and Internet-distributed objects using managed code.
The ability to create and use reusable UI controls that can encapsulate common functionality
and thus reduce the amount of code that a page developer has to write.
The ability for developers to cleanly structure their page logic in an orderly fashion (not
"spaghetti code").
The ability for development tools to provide strong WYSIWYG design support for pages
(existing ASP code is opaque to tools).
ASP.NET Web Forms pages are text files with an .aspx file name extension. They can be
deployed throughout an IIS virtual root directory tree. When a browser client requests .aspx
resources, the ASP.NET runtime parses and compiles the target file into a .NET Framework
class. This class can then be used to dynamically process incoming requests. (Note that the .aspx
file is compiled only the first time it is accessed; the compiled type instance is then reused across
multiple requests).
An ASP.NET page can be created simply by taking an existing HTML file and changing
its file name extension to .aspx (no modification of code is required). For example, the following
sample demonstrates a simple HTML page that collects a user's name and category preference
and then performs a form post back to the originating page when a button is clicked:
ASP.NET provides syntax compatibility with existing ASP pages. This includes support
for <% %> code render blocks that can be intermixed with HTML content within an .aspx file.
3
These code blocks execute in a top-down manner at page render time.
Server controls automatically maintain any client-entered values between round trips to
the server. This control state is not stored on the server (it is instead stored within an <input
type="hidden"> form field that is round-tripped between requests). Note also that no client-side
script is required.
ASP.NET Web Forms provide an easy and powerful way to build dynamic Web UI.
ASP.NET Web Forms pages can target any browser client (there are no script library or
cookie requirements).
ASP.NET Web Forms pages provide syntax compatibility with existing ASP pages.
ASP.NET server controls provide an easy way to encapsulate common functionality.
ASP.NET ships with 45 built-in server controls. Developers can also use controls built by
third parties.
ASP.NET server controls can automatically project both up level and down-level HTML.
ASP.NET templates provide an easy way to customize the look and feel of list server
controls.
ASP.NET validation controls provide an easy way to do declarative client or server data
validation.
4
2.2 C#.NET
ADO.NET OVERVIEW
ADO.NET is an evolution of the ADO data access model that directly addresses user
requirements for developing scalable applications. It was designed specifically for the web with
scalability, statelessness, and XML in mind.
ADO.NET uses some ADO objects, such as the Connection and Command objects, and also
introduces new objects. Key new ADO.NET objects include the Dataset, Data Reader, and Data
Adapter.
The important distinction between this evolved stage of ADO.NET and previous data
architectures is that there exists an object -- the Dataset -- that is separate and distinct from any
data stores. Because of that, the Dataset functions as a standalone entity. You can think of the
Dataset as an always disconnected record set that knows nothing about the source or destination
of the data it contains. Inside a Dataset, much like in a database, there are tables, columns,
relationships, constraints, views, and so forth.
A Data Adapter is the object that connects to the database to fill the DataSet. Then, it
connects back to the database to update the data there, based on operations performed while the
Dataset held the data. In the past, data processing has been primarily connection-based. Now, in
an effort to make multi-tiered apps more efficient, data processing is turning to a message-based
approach that revolves around chunks of information. At the center of this approach is the Data
Adapter, which provides a bridge to retrieve and save data between a Dataset and its source data
store. It accomplishes this by means of requests to the appropriate SQL commands made against
the data store.
The XML-based Dataset object provides a consistent programming model that works
with all models of data storage: flat, relational, and hierarchical. It does this by having no
'knowledge' of the source of its data, and by representing the data that it holds as collections and
data types. No matter what the source of the data within the Dataset is, it is manipulated through
the same set of standard APIs exposed through the Dataset and its subordinate objects. While the
Dataset has no knowledge of the source of its data, the managed provider has detailed and
specific information. The role of the managed provider is to connect, fill, and persist the Dataset
to and from data stores. The OLE DB and SQL Server .NET Data Providers
5
(System.Data.OleDb and System.Data.SqlClient) that are part of the .Net Framework provide
four basic objects: the Command, Connection, DataReader and Data Adapter. In the remaining
sections of this document, we'll walk through each part of the Dataset and the OLE DB/SQL
Server .NET Data Providers explaining what they are, and how to program against them. The
following sections will introduce you to some objects that have evolved, and some that are new.
These objects are:
• Connections: For connection to and managing transactions against a database.
• Commands: For issuing SQL commands against a database.
• DataReaders: For reading a forward-only stream of data records from a SQL Server data
source.
• Datasets: For storing, Remoting and programming against flat data, XML data and
relational data.
• DataAdapters: For pushing data into a DataSet, and reconciling data against a database.
When dealing with connections to a database, there are two different options: SQL Server
.NET Data Provider (System.Data.SqlClient) and OLE DB .NET Data Provider
(System.Data.OleDb). In these samples we will use the SQL Server .NET Data Provider. These
are written to talk directly to Microsoft SQL Server. The OLE DB .NET Data Provider is used to
talk to any OLE DB provider (as it uses OLE DB underneath). Connections:
Connections are used to 'talk to' databases, and are represented by provider-specific
classes such as SqlConnection. Commands travel over connections and result sets are returned in
the form of streams which can be read by a DataReader object, or pushed into a DataSet object.
Commands :
Commands contain the information that is submitted to a database, and are represented
by provider-specific classes such as SqlCommand. A command can be a stored procedure call, an
UPDATE statement, or a statement that returns results. You can also use input and output
parameters, and return values as part of your command syntax. The example below shows how
to issue an INSERT statement against the Northwind database.
Data Readers :
6
The DataReader object is somewhat synonymous with a read-only/forward-only cursor over
data. The DataReader API supports flat as well as hierarchical data. A DataReader object is
returned after executing a command against a database. The format of the returned DataReader
object is different from a recordset. For example, you might use the DataReader to show the
results of a search list in a web page.
Datasets
The Dataset object is similar to the ADO Record set object, but more powerful, and with one
other important distinction: the Dataset is always disconnected. The Dataset object represents a
cache of data, with database-like structures such as tables, columns, relationships, and
constraints. However, though a Dataset can and does behave much like a database, it is important
to remember that Dataset objects do not interact directly with databases, or other source data.
This allows the developer to work with a programming model that is always consistent,
regardless of where the source data resides. Data coming from a database, an XML file, from
code, or user input can all be placed into Dataset objects. Then, as changes are made to the
Dataset they can be tracked and verified before updating the source data. The Get Changes
method of the Dataset object actually creates a second Dataset that contains only the changes to
the data. This Dataset is then used by a Data Adapter (or other objects) to update the original
data source.
The Dataset has many XML characteristics, including the ability to produce and consume XML
data and XML schemas. XML schemas can be used to describe schemas interchanged via Web
Services. In fact, a Dataset with a schema can actually be compiled for type safety and statement
completion.
The DataAdapter object works as a bridge between the DataSet and the source data.
Using the provider-specific SqlDataAdapter (along with its associated SqlCommand and
SqlConnection) can increase overall performance when working with a Microsoft SQL Server
databases. For other OLE DB-supported databases, you would use the OleDbDataAdapter object
and its associated OleDbCommand and OleDbConnection objects.
7
The DataAdapter object uses commands to update the data source after changes have been
made to the DataSet. Using the Fill method of the DataAdapter calls the SELECT command;
using the Update method calls the INSERT, UPDATE or DELETE command for each changed
row. You can explicitly set these commands in order to control the statements used at runtime to
resolve changes, including the use of stored procedures. For ad-hoc scenarios, a Command
Builder object can generate these at run-time based upon a select statement. However, this
runtime generation requires an extra round-trip to the server in order to gather required metadata,
so explicitly providing the INSERT, UPDATE, and DELETE commands at design time will
result in better run-time
Performance
1. ADO.NET is the next evolution of ADO for the .Net Framework.
2. ADO.NET was created with n-Tier, statelessness and XML in the forefront. Two new
objects, the DataSet and DataAdapter, are provided for these scenarios.
3. ADO.NET can be used to get data from a stream, or to store data in a cache for updates.
4. There is a lot more information about ADO.NET in the documentation.
5. Remember, you can execute a command directly against the database in order to do inserts,
updates, and deletes. You don't need to first put data into a DataSet in order to insert, update,
or delete it.
6. Also, you can use a DataSet to bind to the data, move through the data, and navigate data
relationships
The computer industry moves to more distributed environments and moves its data from
mainframe to servers; you need to understand the concepts behind a client/server database
environment.
In several respects, server databases such as Microsoft SQL Server are identical to
mainframe databases. The overwhelming majority of databases used on computer systems are
relational databases. Also, server databases such as relational databases on mainframe or
8
minicomputer systems support the use of Structured Query Language (SQL), as well as
proprietary tools for accessing data.
Two Key features of a server database become importing because of the client access to
data. The first feature provides single point of access to the data in the database. The second
feature device processing and manipulation between the client and server systems.
SQL Server permits client applications to control the information retrieve from
the server by using several specialized tools and techniques, including options such as stored
procedures server enforced roles and the triggers that permits processing to be done on the server
automatically. You don’t have to move all processing to the server, of course; you still can do
appropriate information processing on the client workstation .Perform the administration of the
databases Control access to data in the databases Control the manipulation of data in the
databases .You also can use a command line interface to perform all operations With SQL
Server.
Dr.E.F.Codd designed the model for relational databases in 1970, as a means of storing,
retrieving, and manipulating data more easily than in hierarchical and network databases.
Hierarchical and network databases were difficult to design, and it sometimes was difficult to
write proper queries for access to data.
Hierarchical and network databases were difficult to work with for several reasons. One
reason was that the physical and logical definitions of data storage in hierarchical and network
databases had to be written in a cryptic syntax.
9
Another difficulty of working with data definitions came from the fact that different types
of internal pointers, numeric references to data locations, and other low-level details had to be set
up and stored through the databases. The pointers were used for the subsequent direct retrieval
of data.
In Cod’s relational database model, the data is referenced as though it were stored in a
two-dimensional table. The actual physical storage of the data-although significant for the time
required to store, change, or retrieve data-is insignificant syntactically for reference. The
twodimensional table model permits data to be referenced as the rows and columns of the table.
In a Relational Database, data is referenced as the rows and columns of a table. We can
easily visualize data stored as a table, because we often encountered data stored in tables in every
day life. We reference train and plane schedules as a table, for example and we create typical
work sheets as a table.
Client/Server computing is a type of distributed model for data storage, access, and
processing. In a distributed processing system, multiple computers collectively perform a set of
operations. A Client/Server system uses at least two computers, one of which nearly always is a
personal computer.
Each system in a client/server model performs one or more of the data storage, access, or
processing operations. Client/Server computing can not be done with a system that uses
terminals or PC’s running terminal emulators that are connected to another computer. In this
arrangement, the terminal are the PC that’s used as a terminals is simply too passive; it only
sends and displays sets of characters. When PC’s and Servers are connected, the overall
processing should be divided between the server, main frame, or mini computer system and the
client system. The client and the server each process works with in its own capability. A form of
team work that contributes to the efficiency and speed of the overall operation.
Client/Server as the name implies, also involves an unequal division of processing. The in
equality results from the processing disparity between the server and the client. The larger and
10
faster server computer transfers data faster, stores greater qualities of data, and typically
performs more extensive processing than the client system.
Smaller PC Systems are used as Client in Client/Server systems because the PC’s
perform proportionally less of the overall work, relaying primarily on the server for heavy duty
data manipulation. Also , the PC’s key board and monitor allowed into work as an input device ,
by generating commands and data , and as on output device by displaying data to the user.
SQL Server provides the server software that install on the server system and some client
software that’s installed on the client PC systems Windows GUI application tools allow into
create , maintain and access the database and all objects from the client.
The Network software components required for the inter connection of clients and server
computer are built into the window’s NT system. Window’s NT also provides a choice of
network protocols for communication between the client and the server systems. A Client can
run windows ’95, which also contains built-in network software for connection with the
Windows.NT server system. The Window’95 Client and Windows.NT server systems support a
void range of network cards.
The core components of SQL Server are the Relational Database and its structure. SQL
Server is a power full, compressive database environment. This section points out certain
parameters for using SQL Server.
11
SQL Server allows view to define up to 32,767 databases. If we realize that a database is a
centralized repository for the storage of information, being overly constrained by the 32,767
database limit is difficult; we are not likely to encounter any situation in which we need to define
more than these very liberal limit. If we do, consider adding servers to our net work to help
balance the load. In a typical production installation, fewer than five application oriented
databases are in service on any given server.
1. SYSTEM STUDY
The existing system is manual system. Needs to be converted into automated system. As it
has a risk of mismanagement of data, less Security, no proper coordination between die rent
12
Applications and Users, fewer users - friendly, accuracy not guaranteed and not in reach of
distant users
In existing system Furniture shopping can done in a manual way, the customer has to go
for shopping, and then he is having the possibility to choose the products whatever he
wants.
It is a time consuming process.
Thus, the system has to be automated.
In Existing System the Customer is completely depending on the manual process for
buying the Furniture products.
Manual process is a time consuming factor. And when customer approaches for a manual
shopping directly, actually he/she does not have an idea about things like, price range,
items, etc.,
The time which has been spent by the customer in manual shopping can equates to
multiple number of shopping. As customer can sit at home and browse in a fraction of
seconds.
Thus we need to change to a system like “Online Furniture Shopping “.
PROPOSED SYSTEM:
13
Tracks purchases even if user clicks the back button
Tracks each customer by Shopper ID (SID) (does not use cookies)
14
3.1 DATAFLOW DIAGRAM
Data flow diagram is a structured analysis tool for showing the movement of data
through the different transformation or processes in the system. Named bubbles show the
processes and data named arrows, entering or leaving the bubbles, represent flows. A rectangle
represents a source or sinks and is a net originator or consumer of data. A source or sink is
typically outside the main system study. DFD can be hierarchically organized which helps in
partitioning and analyzing the large system, such system are called leveled DFD’s. For the
hierarchy to be consistence it is important that net input or output of a DFD for a process are the
same input and output of the process in the higher level DFD. The refinement stops until each
bubble is atomic.
The data flow diagram may be used to represent a system or software at any level of
abstraction. In fact, DFD may be partitioned into levels that represent increasing information
flow and functional detail. A level 0 DFD is called a Context Level DFD. This model represents
entire software element as a single bubble with input and output data indicated by incoming and
outgoing arrows respectively.
DFD is a Graphical representation of the flow data through an information system, modeling in
DFD primary steps is creates an overview of the system.
Types of DFD
1) Physical DFD
An information dependent view of the current system showing what the data’s are carried
out and how they are performed.
2) Logical DFD
An implementation independent view of the system focusing on the flow of data between
process without specified devices storage locations or people in the system.
DFD Components
Entity
15
An Entity is the source of destination of data the source in a DFD represents, these
entities that are outside the content of the system. Entities are represents rectangle.
Process
The process is the manipulation or work that transforms data, performing computation,
making decisions.
Data Store
A data store is a process stores data between processors for lateral retrieval by the same
process.
Data Flow
It’s a moment of data between the entity process and datastore.Data Flow is an interface
between the components of the DFD.It’s represents by an arrows.
16
3.2 INPUT DESIGN
The main inputs, outputs and major functions of the system are as follows
The main inputs, outputs and major functions of the system are as follows.
Inputs:
Registration module is responsible for member registration and login. While registration,
member will be prompted for his 1) login account details (username, password, hint question,
answer), 2) his personal details, 3) his contact address, 4) his company profile etc. At time of
sign in, Member has to provide username and password. In Message compose box, Member has
to provide Message to send with Email-ID (to whom message has to be sent.). In the chat
window, Member has to provide messages.
Input design is a part of overall system design. The main objective during the input design is as
given below:
INPUT STAGES:
The main input stages can be listed as below:
• Data recording
• Data transcription
• Data conversion
• Data verification
• Data control
• Data transmission
• Data validation
• Data correction
17
INPUT TYPES:
It is necessary to determine the various types of inputs. Inputs can be categorized as follows:
• External inputs, which are prime inputs for the system.
• Internal inputs, which are user communications with the system.
• Operational, which are computer department’s communications to the system?
• Interactive, which are inputs entered during a dialogue.
INPUT MEDIA:
At this stage choice has to be made about the input media. To conclude about the input
media consideration has to be given to;
• Type of input
• Flexibility of format
• Speed
• Accuracy
• Verification methods
• Rejection rates
• Ease of correction
• Storage and handling requirements
• Security
• Easy to use
• Portability
Keeping in view the above description of the input types and input media, it can be said
that most of the inputs are of the form of internal and interactive. As
Input data is to be the directly keyed in by the user, the keyboard can be considered to be the
most suitable input device.
18
Outputs from computer systems are required primarily to communicate the results of processing
to users. They are also used to provides a permanent copy of the results for later consultation.
The various types of outputs in general are:
• External Outputs, whose destination is outside the organization.
• Internal Outputs whose destination is with in organization and they are the User’s main
interface with the computer.
• Operational outputs whose use is purely with in the computer department.
• Interface outputs, which involve the user in communicating directly with
OUTPUT DEFINITION
For Example
Will decimal points need to be inserted Should leading zeros be suppressed.
Output Media:
In the next stage it is to be decided that which medium is the most appropriate for the
output. The main considerations when deciding about the output media are:
• The suitability for the device to the particular application.
• The need for a hard copy.
• The response time required.
19
• The location of the users
• The software and hardware available.
Keeping in view the above description the project is to have outputs mainly coming under the
category of internal outputs. The main outputs desired according to the requirement specification
are:
The outputs were needed to be generated as a hot copy and as well as queries to be viewed on the
screen. Keeping in view these outputs, the format for the output is taken from the outputs, which
are currently being obtained after manual processing. The standard printer is to be used as output
media for hard copies.
3.3 DATABASE DESIGN
ADO.NET and accessing the database through applets and ADO.NET API via an
intermediate server resulted server resulted in a new type of database model which is different
from the client-server model. Based on number of intermediate server through the request should
go it is named as single tire, two tire and multi tire architecture
Single Tier:
In a single tier the server and client are the same in the sense that a client program
that needs information (client) and the source of this type of architecture is also possible in java,
in case flat files are used to store the data. However this is useful only in case of small
applications. The advantage with this is the simplicity and portability of the application
developed.
20
Server and
client
Database
In two tier architecture the database resides in one machine and client in different
machine they are connected through the network. In this type of architecture a database
management takes control of the database and provides access to clients in a network. This
software bundle is also called as the server. Software in different machines, requesting for
information are called as the clients.
Server
Client
Client
Database
In the three-tier architecture, any number servers can access the database that resides on
server. Which in turn serve clients in a network. For example, you want to access the database
using java applets, the applet running in some other machine, can send request only to the server
from which it is down loaded. For this reason we will need to have a intermediate server which
will accept the requests from applets and them to the actual database server. This intermediate
21
server acts as a two-way communication channel also. This is the information or data from the
database is passed on to the applet that is requesting it. This can be extended to make n tiers of
servers, each server carrying to specific type of request from clients, however in practice only 3
tiers architecture is popular.
3.5 SYSTEM DEVELOPMENT
• User Registration: User can register on the system and get his online account on site.
• User Login: User can login to system and check various furniture data online.
• Product Categories: The furniture are arranged and can be viewed in categories.
• Credit card payment: After total bill is calculated user can pay via credit card online.
22
3. TESTING AND IMPLEMENTATION
It is the stage of implementation, which ensures that system works accurately and effectively
before the live operation Commences. It is a confirmation that all are correct and opportunity to
show the users that the system must be tested with data and show that the system will operate
successfully and produce expected results under expected conditions.
Before implementation, the proposed system must be tested with raw data to ensure that the
modules of the system works correctly and satisfactorily. The system must be tested with valid
data to achieve its objective.
The purpose of system testing is to identify and correct errors in the candidate system. Testing is
done to achieve the system goal. Testing is vital to the parts of the system are correct; the goal
will be successfully achieved. Inadequate testing or non-testing leads to errors that may not
appear until months later. The various types of testing done on the system are:
Unit Testing
Integration Testing
Validation Testing
Quality Assurance
UNIT TESTING
A program represents the logical elements of a system. For a program to run satisfactorily, it
must compile and test data correctly and tie in properly with other programs.
Achieving an error free program is the responsibility of the programmer. Program
statement that violates one or more rules of the language in which it is written. An
improperly defined field dimension or generated by the computer
INTEGRATION TESTING
Programs are invariable related to one another and interact in the total system. Each program is
tested to see whether it conforms to related programs in the system. Each portion of
the system is tested against the entire module with both the test data and the live data
before the entire system is tested as a whole.
23
VALIDATION TESTING
The validation testing is performed for all the data in the system. The data are completely
validated according to the company’s request and requirement. The function or
performance characteristic’s is confirm specification is uncovered and efficiency list is
created
QUALITY ASSURANCE
The Project is tested completely and various errors found are rectified.
Various validations are performed to ensure that important data are not missed.
Testing is performed with some sample inputs from the company and the output is
verified and found right.
4. CONCLUSION
The package was designed in such a way that future modifications can be
done easily. The following conclusions can be deduced from the development of the project.
Automation of the entire system improves the efficiency
It provides a friendly graphical user interface which proves to be better when
compared to the existing system.
It gives appropriate access to the authorized users depending on their permissions.
It effectively overcomes the delay in communications.
Updating of information becomes so easier.
System security, data security and reliability are the striking features.
The System has adequate scope for modification in future if it is necessary.
24
5. SCOPE FOR FUTURE ENHANCEMENT
This application avoids the manual work and the problems concern with it. It is an
easy way to obtain the information regarding the various products information that are present
in the Furniture Mart.
Well I and my team members have worked hard in order to present an improved
website better than the existing one’s regarding the information about the various activities. Still
,we found out that the project can be done in a better way. Primarily, when we request
information about a particular product it just shows the company, product id, product name and
no. of quantities available. So, after getting the information we can get access to the product
company website just by a click on the product name .
The next enhancement that we can add the searching option. We can directly
search to the particular product company from this site .These are the two enhancements that we
could think of at present.
7. BIBLIOGRAPHY
The following books were referred during the analysis and execution phase of the project.
25
MICROSOFT .NET WITH C#
Microsoft .net series
Wrox Publishers
Apress Publications
C# COOK BOOK
O reilly Publications
Novice to Professional.
WEBSITES:
www.google.com
www.microsoft.com
26
LOGIN PROCESS
User Id
LOGIN PROCESS SCREEN
Password
ERROR IN
INPUT
27
MAIN SCREEN PROCESS
MAIN
ADMIN SCREEN Add Emp
Add User
Reports
Add Order
Add Shoping
Report
Add Cart
28
Add Order
DATABASE
ADD User
Admin Plase DATA IS
Order ADDED
Add Shoping
DATABASE
Add DATA
Admin Shoping UPDATED
Cart
29
DATABASE
B.TABLE STRUCTURE
30
PRIMARY KEY: accno
31
32
D. FORM DESIGN
Home Page
About US
33
User Registration
34
User Login Page
35
User Home Page
36
Product Details
37
Buy Any Item
38
Admin login
39
Admin Home Page
40
Add Sofa Details
41
Remove Details
42
Edit Product
43
Product Report
44
User Details
45
46