Beruflich Dokumente
Kultur Dokumente
The project entitled E-Furniture House is a web based application which has been
designed and devloped by using ASP.Net 2010 as front end tool and Microsoft SQL Server
2008 as back end tool. The software mainly developed for retail furniture showrooms.
E-Furniture House is a powerful and easy software that eliminates the tedious and time-
consuming tasks associated with a furniture stores daily operations (agging the sales floor,
resolving customer service problems, keeping track of special orders. The ease and flexibility
of the special order system appeals to all types of retailers.
The system designed with four major roles such as Administrator, Customer,
Management and Staff. Each role has been designed with mutiple features. The administrator
can add new products, update the existing stock items, add new customer data and supplier
data, fix customer wise rate fixing and supplier wise rate fixing, maintain scrap takers database,
add carpenters details, vehicle details and track staff billing hisory.
The staff can access only the billing section. Before accessing the billing section, the
staff has to register and get log in to the system. The customer have to register and get log into
the system before view the product catalog. In the product catalog, the customer has been
allowed to select the products and the selected products has been added to cart section. Once
the cart section over, the customer has been redirected to payment gateway to settle out the
payment through their bank debit card or credit card. In addition, the customer can mark the
favourite products also for future reference.
The management can get several reports such as datewise billing, Product Wise Billing,
Customer Wise Billing, overall stock value and scrap value.
The system has additional feature of Email services to customer as well as to the
management. The system can be further extended based on the needs of the management and
the user friendliness of the software.
CHAPTER -1
1. INTRODUCTION
About Us
Krishnaa Timbers was established in the year 1961 in the name of Sakthi Timbers
founded by brothers Mr.R.Krishnaswamy Naidu and Mr.R.Govindaswamy Naidu near
Krishnamudaliyar Road opposite to Brookfield plaza located at Coimbatore.After 10 years
later, they shifted their company to Thadagam Road, Edayarpalayam,Coimbatore. In later
1993, Krishnaswamy Naidu third son Mr.K.Mohan Kumar started his career in concentrating
his father business and his innovative policy of reviewing units at regular intervals has
enhanced company status as a modern production unit
Team :
We are backed by a team of knowledgeable and trained professionals. Our team works day and
night to provide our customers with the best of products. Our team works in close association
with the client in understanding their business needs
Clientele :
With our dedication, we have earned a loyal client base all over Indian Marketers and other
international marketers as well. We design products according to the client specifications. By
providing clients with their ordered consignments within specified timeframe, we have become
a preferred business partner for them.
Quality Assurance :
We have a special team of quality control that keeps an eye on the entire manufacturing process
ensuring that all our products are of the finest quality. Furthermore, all our products are
undergone stringent quality tests at all levels of manufacturing starting from procuring the raw
materials to the final stage of packing.
Our quality control team checks products on the following parameters :
The company abides by the safety and quality standards and follows the safety norms
strictly. We are a performance driven company that never compromises with the quality of
products and bound by the essence of team spirit that helps us in delivering outstanding results.
Payment Mode :
To facilitate our large client base we accept payments in
Money transfer through bank
Cash
Demand draft
Name of the Proprietor : Mr.K.Mohan Kumar
www.krishnaatimbers.in
PROJECT OBJECTIVE
The main objective of the project is
1. To computerize the furniture retail showroom process into a single unified software.
2. To integrate the customer, management, staff and the administrator roles together.
3. To summarize the data and generate multiple reports to the management.
4. To solve the existing problems faced inside the furniture retail showroom.
MODULES DESCRIPTION
In the product creation page, the administrator can create category wise
products with re-order level settings for each product. The administrator can add
the existing stock of the products also.
3. Comforts
The comforts section holds three main ledgers such as scrap takers,
carpenters ledger and load vehicle ledger. In the scrap takers page, the
administrator can add the scrap takers contact details which includes the bulk
scrap takers as well as the passing scrap takers. Likewise in the carpenters page,
the administrator can add and maintain the carpenters contact details. The
carpenters are mainly used for furniture works. The administrator can have the
facility to add the weight carrying load vehicle driver details, so that while
delivering products to the customer, the company can easily utilize the load
vehicle driver details for delivery support.
4. Product catalog and Cart
In the product catalog and cart details, the customer can view the products,
mark their favourite products, select the products, add to cart section and proceed
to payment form.
5. Payment Form
In the payment form, the customer can pay the amount through their
bank debit and credit card details. Once the payment has been received in the
server side, an acknowledged mail has been sent to the customer side.
6. Management Zone
In the management Zone, the system list out the non-sold products and the
total dead stock value. In addition, the system generates a random best combo
offer festival sale suggesting products taken from non-sold products list.
7. Reports
Datewise Billing
Product Wise Billing
Customer Wise Billing
Stock Value List
Scrap Value List
1.4 HARDWARE CONFIGURATION
Processors will continue to get faster, smaller and cheaper, whereas memory will
continue to get faster, larger and cheaper. The trend except to have a reasonable
memory to a powerful processor.
When an application project is considered the three basic software requirements are
the platform in which the project is developed, the front-end tool that provides the
interaction with the users and the back-end tool that stores the data.
WINDOWS 8
CHARACTERISTICS
ASP.NET Web pages, known officially as Web Forms, are the main building blocks
for application development.[6] Web forms are contained in files with a ".aspx" extension;
these files typically contain static (X)HTML markup, as well as markup defining server-side
Web Controls and User Controls where the developers place all the rc content[further
explanation needed] for the Web page. Additionally, dynamic code, which runs on the server,
can be placed in a page within a block <% -- dynamic code -- %>, which is similar to other
Web development technologies such as PHP, JSP, and ASP. With ASP.NET Framework 2.0,
Microsoft introduced a new code-behind model which allows static text to remain on the .aspx
page, while dynamic code remains in an .aspx.vb or .aspx.cs or .aspx.fs file (depending on the
programming language used).
RENDERING TECHNIQUE
ASP.NET uses a "visited composites" rendering technique. During compilation, the
template (.aspx) file is compiled into initialization code which builds a control tree (the
composite) representing the original template. Literal text goes into instances of the Literal
control class, and server controls are represented by instances of a specific control class. The
initialization code is combined with user-written code (usually by the assembly of multiple
partial classes) and results in a class specific for the page. The page doubles as the root of the
control tree.
Actual requests for the page are processed through a number of steps. First, during the
initialization steps, an instance of the page class is created and the initialization code is
executed. This produces the initial control tree which is now typically manipulated by the
methods of the page in the following steps. As each node in the tree is a control represented as
an instance of a class, the code may change the tree structure as well as manipulate the
properties/methods of the individual nodes. Finally, during the rendering step a visitor is used
to visit every node in the tree, asking each node to render itself using the methods of the visitor.
The resulting HTML output is sent to the client.
After the request has been processed, the instance of the page class is discarded and
with it the entire control tree. This is a source of confusion among novice ASP.NET
programmers who rely on the class instance members that are lost with every page
request/response cycle.
STATE MANAGEMENT
ASP.NET applications are hosted by a Web server and are accessed using the stateless
HTTP protocol. As such, if an application uses stateful interaction, it has to implement state
management on its own. ASP.NET provides various functions for state management.
Conceptually, Microsoft treats "state" as GUI state. Problems may arise if an application needs
to keep track of "data state"; for example, a finite-state machine which may be in a transient
state between requests (lazy evaluation) or which takes a long time to initialize. State
management in ASP.NET pages with authentication can make Web scraping difficult or
impossible.
APPLICATION
Application state is held by a collection of shared user-defined variables. These are set
and initialized when the Application_OnStart event fires on the loading of the first instance of
the application and are available until the last instance exits. Application state variables are
accessed using the Applications collection, which provides a wrapper for the application state.
Application state variables are identified by name.Application is state management.
SESSION STATE
Server-side session state is held by a collection of user-defined session variables that
are persistent during a user session. These variables, accessed using the Session collection, are
unique to each session instance. The variables can be set to be automatically destroyed after a
defined time of inactivity even if the session does not end. Client-side user session is
maintained by either a cookie or by encoding the session ID in the URL itself.
ASP.NET supports three modes of persistence for server-side session variables
In-process mode
The session variables are maintained within the ASP.NET process. This is the fastest
way; however, in this mode the variables are destroyed when the ASP.NET process is recycled
or shut down.
2. SYSTEM STUDY