Chapter 1

CHAPTER 1
INTRODUCTION
1.1 ABOUT THE PROJECT
Internet is a crucial source the company existence, its information and products to the
people around the world. Online sale and purchase, is a big and important part of the
internet in present life. In Food court we are providing all kinds of food items of all
cuisine. We are taking orders from the customers by showing our available food items.
We are having the facility of changing home content, changing about us content,
uploading the products (dishes), uploading images in gallery of our food court, generating
blogs by user, receiving orders from the website. The main purpose of creating the
website on this topic is to promote our restaurant and products online to make it in
everyone’s approach . The user required the basic knowledge of internet for usage.
Our website “FOOD COURT” is a site for promoting our products and online ordering
for Home delivery. The client can visit our site , view the products (dishes) and place the
order online. He /she doesn’t need to visit the shop for ordering the food. Our website is
having a user friendly environment and it is designed as per all web standards . user can
easily understand about its working and can browse the site as per their need. Effective
retrieval of data can save lot of precious time and hence makes it easier for user to fulfill
their requirements ,increase the productivity of the employee concerned and the
organization as whole. Not only that , through proper management of website’s section
and its we can serve our users better and enforce them to visit our website products.
1
1.2 TECHNOLOGY USED :Asp.Net
Asp.net is the technology used to develop the project . ASP.NET is a server-side Web
application framework designed for Web development to produce dynamic Web pages.
Active Server Pages (ASP), also known as Classic ASP, was introduced in 1998 as
Microsoft's first server side scripting engine. ASP is a technology that enables scripts in
web pages to be executed by an Internet server.ASP pages have the file extension .asp,
and are normally written in VBScript.
Why Asp.Net is used ?
1. ASP.NET dramatically reduces the amount of code needed to build large applications.
2. With built-in Windows authentication and application settings, and applications safe
and secure.
3. It provides higher performance by using early binding, just-in-time compilation, native

optimization, and caching services right out of the box.
4. ASP.NET framework is complemented by a rich and designer tools in Visual Studio

integrated development environment. WYSIWYG-editing, drag and drop controls,
firewall and automatic deployment are just some of the features of this powerful tool
provides.
5. ASP.NET provides a simple and easy to perform common tasks, from simple form
submission and client authentication configuration and deployment site.
6. The source code and HTML together, so that ASP.NET pages are easy to maintain and
write. In addition, the source code is executed on the server. It provides greater power and
flexibility to Web pages.
2
7. All processes are carefully controlled and managed by ASP.NET, so that if the process
is dead, the new process can be created in its place, which helps to keep your application
constantly available to handle requests.
8. This is purely server-side technologies, so that the ASP.NET code runs on the server
before being sent to the browser.
9. Be independent of the language, it allows you to select the language that best applies to
your application or partition applications in many languages.
10. ASP.NET makes for easy deployment. No need to register components because the
configuration information is embedded.
11. The Web server continuously monitors the pages, components and applications
running on it. If he notices any memory leaks, infinite loops, other illegal activities,
which immediately destroys the activity and restarts.
12. It is easy to work with ADO.NET using data binding and formatting of the page. This
is an application that works faster and counters large volumes of users without
performance problems
In short ASP.NET, the next generation version of Microsoft’s ASP, is a programming

framework used to generate enterprise-class sites, web applications, and technologies.
ASP.NET developed applications are available on a worldwide basis leading to efficient
knowledge management. Whether you are building a small business web-site or a huge
corporate web application distributed across multiple networks, ASP.NET will provide
you all the features you could possibly require and at an affordable cost: FREE!
3
1.2.1 LANGUAGE USED : c#
C# is a multi-paradigm programming language encompassing strong typing, imperative,

declarative, functional, procedural, generic, object-oriented (class-based), and
component-oriented programming disciplines. It was developed by Microsoft within its
.NET initiative and later approved as a standard by Ecma (ECMA-334) and ISO
(ISO/IEC 23270:2006). C# is one of the programming languages designed for the
Common Language Infrastructure.
C# is intended to be a simple, modern, general-purpose, object-oriented programming

language. Its development team is led by Anders Hejlsberg. The most recent version is
C# 5.0, which was released on August 15, 2012.
C# is an evolution of the C and C++ family of languages. However, it borrows features

from other programming languages, such as Delphi and Java. If you look at the most
basic syntax of both C# and Java, the code looks very similar, but then again, the code
looks a lot like C++ too, which is intentional. Developers often ask questions about why
C# supports certain features or works in a certain way. The answer is often rooted in it's
C++ heritage.
1.2.2 DEVELOPMENT TOOLS USED :
i. Visual Studio 2010: Microsoft Visual Studio is an integrated development

environment (IDE) from Microsoft. It is used to develop console and graphical
user interface applications along with Windows Forms or WPF applications, web
sites, web applications, and web services in both native code together with
managed code for all platforms supported by Microsoft Windows, Windows
Mobile, Windows CE, .NET Framework, .NET Compact Framework and
Microsoft Silverlight.
Visual Studio supports different programming languages by means of language

services, which allow the code editor and debugger to support (to varying
degrees) nearly any programming language, provided a language-specific service
4
exists. Built-in languages include C/C++[5] (via Visual C++), VB.NET (via Visual
Basic .NET), C# (via Visual C#), and F# (as of Visual Studio 2010[6]). Support for
other languages such as M, Python, and Ruby among others is available via
language services installed separately. It also supports XML/XSLT,
HTML/XHTML, JavaScript and CSS. Individual language-specific versions of
Visual Studio also exist which provide more limited language services to the user:
Microsoft Visual Basic, Visual J#, Visual C#, and Visual C++.
ii. SQL Server 2008: Microsoft SQL Server is a relational database

management system developed by Microsoft Inc.. As a database, it is a software
product whose primary function is to store and retrieve data as requested by other
software applications, be it those on the same computer or those running on
another computer across a network (including the Internet). There are at least a
dozen different editions of Microsoft SQL Server aimed at different audiences and
for different workloads (ranging from small applications that store and retrieve
data on the same computer, to millions of users and computers that access huge
amounts of data from the Internet at the same time). Its primary query languages
are T-SQL and ANSI SQL.
SQL Server 2008 (formerly codenamed "Katmai") was released on August 6,

2008 and aims to make data management self-tuning, self organizing, and self
maintaining with the development of SQL Server Always On technologies, to
provide near-zero downtime. SQL Server 2008 also includes support for
structured and semi-structured data, including digital media formats for pictures,
audio, video and other multimedia data. In current versions, such multimedia data
can be stored as BLOBs (binary large objects), but they are generic bit streams.
Intrinsic awareness of multimedia data will allow specialized functions to be
performed on them. According to Paul Flessner, senior Vice President, Server
Applications, Microsoft Corp., SQL Server 2008 can be a data storage backend
for different varieties of data: XML, email, time/calendar, file, document, spatial,
etc as well as perform search, query, analysis, sharing, and synchronization
across all data types.
5
CHAPTER 2
SOFTWARE REQUIREMENT SPECIFICATIONS
2.1 INTRODUCTION:
System requirements are expressed in a software requirement document. The
Software requirement specification (SRS) is the official statement of what is
required of the system developers. This requirement document includes the
requirements definition and the requirement specification. The software
requirement document is not a design document. It should set out what the system
should do without specifying how it should be done. The requirement set out in
this document is complete and consistent. The software specification document
satisfies the following:
1. It specifies the external system behaviors.

2. It specifies constraints on the implementation.
3. It is easy to change.
4. It serves as reference tool for system maintainers.
5. It record forethought about the life cycle of the system.
6. It characterizes acceptable response to undesired events.
2.2 USER CLASS AND CHARACTERISTICS:

There are 3 types of user of this software:
1. GENERAL PUBLIC : General public can use the system to see the product,
their prices and images available. General user are those who don’t buy the
products.
2. CUSTOMERS: Customers are using for viewing and buying the products.
Customer can also write blogs for products and services
3. ADMINISTRATOR: Administrators can add, edit & delete products and
provide services to the customer. Administrator can see the blogs given by
the customer. Administrator maintaining the deliveries.
6
2.3 FUNCTIONAL REQUIREMENTS:
The System must provide following functionalities:
1. Keeping the content of the website updated ( Home content , About content).
2. Keeping the records of products.
3. Keeping the records of gallery images
4. Reading of the blogs given by the customers.
5. Keeping details about the product it is delivered or not etc.
6. Keeping the records of the order form filled.
2.4 PERFORMANCE REQUIREMENTS:

In order to maintain an acceptable speed at maximum number of uploads allowed
from a particular customer will be any number of users can access the system at any
time. Also connections to the servers will be based on the criteria of attributes of the
user like his location, and server will be working whole 24X 7 times.
2.5 NON FUNCTIONAL REQUIREMENTS:

Following Non functional requirements will be there in the Insurance on internet:
i. Secure access of confidential data (customer’s details).
ii. 24 X 7 availability.
iii. Better component design to get better performance at peak time.
iv. Flexible service based architecture will be highly desirable for future extension.
Non functional requirements define system properties and constraints . It arise

through user needs, because of budget constraints or organizational policies, or due to
the external factors such as safety regulations, privacy registration and so on. Various
other Non functional requirements are:
1 SECURITY: The system use SSL (secured socket layer) in all transactions that
include any confidential customer information. The system’s back-end servers
7
shall only be accessible to authenticated administrators. Sensitive data will be
encrypted before being sent over insecure connections like the internet.
2 RELIABILITY: The system provides storage of all databases on redundant

computers with automatic switchover. The reliability of the overall program
depends on the reliability of the separate components. The main pillar of
reliability of the system is the backup of the database which is continuously
maintained and updated to reflect the most recent changes. Thus the overall
stability of the system depends on the stability of container and its underlying
operating system.
3 AVAILABILITY: The system should be available at all times, meaning the user
can access it using a web browser, only restricted by the down time of the server
on which the system runs. In case of a of a hardware failure or database
corruption, a replacement page will be shown. Also in case of a hardware failure
or database corruption, backups of the database should be retrieved from the
server and saved by the administrator. Then the service will be restarted. It means
24 X 7 availability.
4 MAINTAINABILITY: A commercial database is used for maintaining the

database and the application server takes care of the site. In case of a failure, a re-
initialization of the program will be done. Also the software design is being done
with modularity in mind so that maintainability can be done efficiently.
5 PORTABILITY: The application is HTML and scripting language based. So the

end-user part is fully portable and any system using any web browser should be
able to use the features of the system, including any hardware platform that is
available or will be available in the future. An end-user is using this system on
any OS; either it is Windows or Linux. The system shall run on PC, Laptops, and
PDA etc.
8
2.6 EXTERNAL INTERFACE REQUIREMENTS:
1. USER INTERFACE: User of the system will be provided with the Graphical user
interface, there is no command line interface for any functions of the product.
The user will get Blog page where he can write blogs and admin can view it. The
order now page where he can order the food.
2. HARDWARE INTERFACE:Hardware requirements for Insurance on internet will
be same for both the parties which are follows:
i. Processor: - Pentium I or above.
ii. RAM: - 128 MB or above.
iii. HD: 20 GB or above.
iv. NIC: For each party4.5.3
3. SOFTWARE INTERFACE: Software required to make working of product is:
i. Operating System: Windows XP/vista/7or later version, Linux OS which
supports networking.
ii. Asp.Net development tools : Visual studio 2010
4. COMMUNICATION INTERFACES: The two parties should be connected through
either by LAN or WAN for the communication.
COMMUNICATION CHANNELS
SENDER RECEIVER
5. GENERAL CONSTRAINTS, ASSUMPTIONS, DEPENDENCIES, GUIDELINES:

1. GENERAL CONSTRAINTS: The interface will be in English only.The system
is working for single server(Sender & Receiver).There is no maintainability
or backup so availability will get affected. The system is a single user system.
GUI features available.
9
2. ASSUMPTIONS AND DEPENDENCIES: The product does require back end
database server SQL SERVER 2008 for storing the blogs information and
current order information, gallery information, new products information for
different types of user of the system as well as various databases regarding
various insurance information.
ASSUMPTIONS: User must be trained for basic computer functionalities. User
must have the basic knowledge of English. The system must be able to
respond to database software within reasonable time.
FRONT END (user interaction):

The product will require a computer with an application program or with any
other application program and an communication channel.
The speed of the communication channel (if any) must be, at a minimum 28.8
kbps in order to support message transfer in reasonable time.
10
CHAPTER 3
DESIGN
INTRODUCTION:
System design is a process of developing specifications for a candidate system that meet
the criteria established in the system analysis. Major steps in system design are the
preparation of the input forms and the output reports in a form applicable to the user.
System design is a solution, a “how to” approach to the creation of a new system. The
term design describes a final system and the process by which it is developed. It provides
the understanding and procedural details necessary for implementing the system
recommended in the feasibility study. Emphasis on translating the performance
requirement into design specifications. Design goes through the logical and physical
stages of development. Logical design reviews the present physical system, prepares
input and output specification, and makes edit security and control specifications. The
physical design maps out the details of the physical system. Design includes construction
of programs, Dfds, use case diagrams, er diagrams, flow charts etc.
3.2 ARCHITECTURAL DESIGN:

DATA FLOW DIAGRAMS:Data flow diagrams (DFD) was first developed by LARRY
CONSTANTINE as way representing system requirements in a graphical form; this lead to
modular design. A DFD describes what data flow (logical) rather than how they are
processed, so it does not depend on hardware, software, data structure or file organization. It
is also known as ‘bubble chart’.A Data Flow Diagrams is a structured analysis and design
tool that can be used for flowcharting in place of, or in association with, information oriented
and process oriented systems flowcharts. A DFD is a network that describes the flow of data
and the processes that change, or transform, data throughout a system. This network is
11
constructed by using a set of symbols that do not imply a physical implementation. It has the
purpose of clarifying system requirements and identifying major transformations that will
become programs in system design. So it is the starting point of the design phase that
functionality decomposes the requirement specifications down to the lowest level of detail.
The symbols used to prepare DFD do not imply a physical implementation, a DFD can be
considered to an abstract of the logic of an information oriented or a process oriented system
flowchart. For these reasons DFDs are often referred to as logical data flow diagrams.
The four basic symbols used to construct data flow diagrams are shown below:
A rectangle represents a data source or destination.
A directed line represents the flow of data that is data stream.
An enclosed figure, usually a circle or an oval bubble, represent a

process that transforms data streams.
An open-ended rectangle represents data storage.
These are symbols that represent data flows, data sources, data transformations and data
storage. The points at which data are transformed are represented by enclosed figures,
usually circles, which are called nodes. The principle processes that take place at nodes
are:
1. combining data streams
2. splitting data streams
3. modifying data streams.
DESIGN FOR THE FUNCTIONING OF DIFFERENT USERS
General Request
User s
Server
12
Request
Customer Database
Admin
1 LEVEL DFD FOR ADMIN
Login table
Data for
ADMIN id & password LOGIN verification
rejected if not Login table

matched Data verified
Home Current
Order
About
Order
Gallary View Blog Products
EditDelete
Content
Blog
Blog Table
Delete
Add
Content Content
Add Delete Edit

Content 13
Content
Content
About Content
Gallary
Home Table
Add Image
Add Name Delete Edit
Gallary Table
Product
Add Image
Add Name Delete Edit

Add Rate
14
Product Table
Order
Edit
Enter Item
name Delete
Order Table
F.K Order
Edit
Enter Item
Rate Delete
15
F.K Order Table
1 LEVEL DFD FOR USERS
User
Blog
Order
Delivery
type
Name
Item Mobile No
Subject
Comment
Address
Name
Blog table Order Form table
16
ER DIAGRAM
Item Name
Id Item
Item rate
Order
Now
Mobile No Id
Order Name
Delievery Type
Address
User
Write blog
17
Subject Id
Blog
Comment Name
DATABASE DESIGN:
A database design is a collection of stored data organized in such a way that the data
requirements are satisfied by the database. The general objective is to make information
access easy, quick, inexpensive and flexible for the user. There are also some specific
objectives like controlled redundancy from failure, privacy, security and performance.
A collection of relative records make up a table. To design and store data to the needed
forms database tables are prepared. Two essential settings for a database are:
i. PRIMARY KEY: The field that is unique for all the record occurrences.
ii. FOREIGN KEY: The field used to set relation between tables. Normalization is a
technique to avoid redundancy in the tables.
DATABASE TABLE DESIGN
HOME CONTENT TABLE :
ABOUT CONTENT TABLE:
18
GALLARY TABLE:
BLOG TABLE:
PRODUCT TABLE:
19
ORDER TABLE:
F.K ORDER:
ORDER FORM TABLE:
20
LOGIN TABLE:
21
CHAPTER 4
CODING & TESTING
INTRODUCTION
The goal of the coding phase is to translate the design of the system into code in a given
programming language. For a given design, the aim of this phase is to implement the
design in the best possible manner. The coding phase affects both testing and
maintenance profoundly. A well written code reduces the testing and maintenance effort.
Since the testing and maintenance cost of software are much higher than the coding cost,
the goal of coding should be to reduce the testing and maintenance effort. Hence, during
coding the focus should be on developing programs that are easy to write. Simplicity and
clarity should be strived for, during the coding phase.
An important concept that helps the understandability of programs is structured

programming. The goal of structured programming is to arrange the control flow in the
program. That is, program text should be organized as a sequence of statements, and
during execution, the statements are executed in the sequence in the program.
For structured programming, a few single-entry-single-exit constructs should be used.

These constructs includes selection (if-then-else), and iteration (while - do, repeat - until
etc). With these constructs it is possible to construct a program as sequence of single -
entry - single - exit constructs. There are many methods available for verifying the code.
22
Some methods are static in nature that is, that is they do not involve execution of the
code. Examples of such methods are data flow analysis, code reading, code reviews,
testing (a method that involves executing the code, which is used very heavily). In the
coding phase, the entire system is not tested together. Rather, the different modules are
tested separately. This testing of modules is called "unit testing". Consequently, this
phase is often referred to as "coding and unit testing". The output of this phase is the
verified and unit tested code of the different modules.
USER INTERFACE CODING: This coding is done to design the website . it

generally tell us about the layout of the website
ADMIN INTERFACE:
Home:
<%@ Page Title="" Language="C#" MasterPageFile="~/Master_Pages/Admin.master"

AutoEventWireup="true" CodeFile="Admin.aspx.cs" Inherits="Admin_Admin" %>
<%@ Register Src="~/WebUserControl/WebUserControl.ascx" TagName="Menubarr"

TagPrefix="Menus" %>
<%@ Register Assembly="CKEditor.NET" Namespace="CKEditor.NET"

TagPrefix="CKEditor"%>
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<div id="Menu">
<Menus:Menubarr ID="menuar" runat="server" />
</div>
<div id="Center">
<div id="AllHomeContent">Home</div>
<div>
<%------------Starting Table------------------------------------------%>
23
<table style="color:Black; border:2px solid black; padding-left:30px; margin-
left:100px;" class="Gallarytab">
<tr>
<td>Enter Content</td>
<td>
<CKEditor:CKEditorControl ID="CKEditors" runat="server" Width="150px"
Height="50px"></CKEditor:CKEditorControl>
</td>
</tr>
<tr>
<td><asp:HiddenField ID="Hid" runat="server" Value="0"/> </td>
</tr>
<tr>
<td>Submit</td>
<td>
<asp:Button ID="Btn_Submit" runat="server" Text="Submit" ValidationGroup="S1"
onclick="Btn_Submit_Click1"/>
</td>
<td><asp:Label ID="lbl" runat="server"></asp:Label></td>
</tr>
</table>
</div>
<%------------------------Ending Table Data insertion------------------------%>
<%----------------------------Starting of Fetch
Content------------------------------%>
<div>
<asp:Repeater ID="Rpt" runat="server" onitemcommand="Rpt_ItemCommand">
<HeaderTemplate>
<table>
<tr>
<td class="Rpt1">HomeContent</td>
<td class="Rpt1">Delete?</td>
<td class="Rpt1">Edit</td>
</tr>
</HeaderTemplate>
<ItemTemplate>
<tr>
<td class="Rpt2"><%#Eval("HomeContent") %></td>
<td class="Rpt2"><asp:ImageButton ID="ImgDels" runat="server"
ImageUrl="~/Upload/MainImg/Del.jpeg" Width="30px" Height="30px"
CommandName="Delete" CommandArgument='<%#Eval("ID") %>' /></td>
<td class="Rpt2">
<asp:LinkButton ID="LinkButton1" runat="server" CommandName="Edit"
CommandArgument='<%#Eval("ID") %>'>Edit</asp:LinkButton> </td>
</tr>
24
</ItemTemplate>
<FooterTemplate>
</table>
</FooterTemplate>
<SeparatorTemplate>
</SeparatorTemplate>
</asp:Repeater>
</div>
</div>
</asp:Content>
ABOUT :

AutoEventWireup="true" CodeFile="About.aspx.cs" Inherits="Admin_About" %>
<%@ Register Src="~/WebUserControl/WebUserControl.ascx" TagName="Menu"

TagPrefix="Menubar" %>
<%@ Register Assembly="CKEditor.NET" Namespace="CKEditor.NET"

TagPrefix="CKEditor"%>

</asp:Content>
Runat="Server">
<div id="Menu">
<Menubar:Menu ID="Menus" runat="server" />
</div>
<div id="Center">
<div id="AllHomeContent">About Us</div>
<div>

<tr>
<td>Enter Content</td>
<td>
<CKEditor:CKEditorControl ID="CKEditors" runat="server" Width="150px"
Height="50px"></CKEditor:CKEditorControl>
</td>
</tr>
25
<tr>
<td><asp:HiddenField ID="Hid" runat="server" Value="0"/> </td>
</tr>
<tr>
<td>Submit</td>
<td>
<asp:Button ID="Btn_Submit" runat="server" Text="Submit"
ValidationGroup="S1"
onclick="Btn_Submit_Click1"/>
</td>
</tr>
</table>
</div>
<%--------------------------Ending Instion
Table---------------------------------------------------------------%>
<%---------------------------Starting Fetch
Rpt-------------------------------------------------------------------------------
%>
<div>
<HeaderTemplate>
<table>
<tr>
<td class="Rpt1">HomeContent</td>
</tr>
</HeaderTemplate>
<ItemTemplate>
<tr>
<td class="Rpt2"><%#Eval("AboutContent") %></td>
<td class="Rpt2"><asp:ImageButton ID="ImgDels"
runat="server" ImageUrl="~/Upload/MainImg/Del.jpeg" Width="30px" Height="30px"
CommandName="Delete" CommandArgument='<%#Eval("ID") %>'
/></td>
<td class="Rpt2">
<asp:LinkButton ID="LinkButton1" runat="server"
CommandName="Edit"
CommandArgument='<%#Eval("ID") %>'>Edit</asp:LinkButton>
</td>
</tr>
</ItemTemplate>
<FooterTemplate>
</table>
</FooterTemplate>
</asp:Repeater>
</div>
<%----------------------------------------Ending Fetch
Rpt------------------------------------------------------------------------------
%>
</div>
26
</asp:Content>
GALLERY:

AutoEventWireup="true" CodeFile="Gallary.aspx.cs" Inherits="Admin_Gallary" %>
<%@Register Src="~/WebUserControl/WebUserControl.ascx" TagName="Menu"
TagPrefix="Menubar"%>
</asp:Content>
Runat="Server">
<div id="Menu">
</div>
<div id="Center">
<div id="AllHomeContent">Gallary</div>
<div>
<tr>
<td>Enter Image</td>
<td><asp:FileUpload ID="FileUpload1" runat="server" /></td>
</tr>
<tr>
<td>Enter Name</td>
<td><asp:TextBox ID="TxtName" runat="server"></asp:TextBox></td>
<td><asp:HiddenField ID="Hid" runat="server" Value="0"/></td>
27
</tr>
<tr>
<td>save</td>
<td><asp:Button ID="BtnSave" runat="server" Width="50px" Height="20px"
Text="Save" onclick="BtnSave_Click"/></td>
</tr>
</table>
</div>
<%--//--------------------Fetch
Table--------------------------------------------------------%>
<div>

<HeaderTemplate>
<table>
<tr>
<td class="Rpt1">Name</td>
<td class="Rpt1">Img</td>
</tr>
</HeaderTemplate>
<ItemTemplate>
<tr>
<td class="Rpt2"><%#Eval("Name") %></td>
<td class="Rpt2">
<img src='<%#getimagepath(Eval("ImageGallery").ToString())
%>' width="100px" height="100px" alt="" />
</td>

/></td>
<td class="Rpt2">
<%--<asp:LinkButton ID="LinkButton1" runat="server"
CommandName="Edit"
CommandArgument='<%#Eval("ID") %>'>Edit</asp:LinkButton>
--%>
CommandName="Edit" CommandArgument='<%#Eval("ID")
%>'>Edit</asp:LinkButton>
</td>
</tr>
</ItemTemplate>
<FooterTemplate>
</table>
</FooterTemplate>
28
</asp:Repeater>
</div>
</div>
</asp:Content>
BLOG:

AutoEventWireup="true" CodeFile="Blog.aspx.cs" Inherits="Admin_Blog" %>
<%@ Register Src="~/WebUserControl/WebUserControl.ascx" TagName="Menubarr"

TagPrefix="Menus" %>

</asp:Content>
Runat="Server">
<div id="Menu">
<Menus:Menubarr ID="menuar" runat="server" />
</div>
<div id="Center">
<div id="AllHomeContent">Blog</div>
<div>
<HeaderTemplate>
<table>
29
<tr>
<td class="Rpt1">Subject</td>
<td class="Rpt1">Comment</td>
<td class="Rpt1">Delete</td>
</tr>
</HeaderTemplate>
<ItemTemplate>
<tr>
<td class="Rpt2"><%#Eval("Subject") %></td>
<td class="Rpt2"><%#Eval("Comment") %></td>
/></td>
</tr>
</ItemTemplate>
<FooterTemplate>
</table>
</FooterTemplate>
</asp:Repeater>
</div>
</div>
</asp:Content>
PRODUCT:

AutoEventWireup="true" CodeFile="Product.aspx.cs" Inherits="Admin_Product" %>
<%@register Src="~/WebUserControl/WebUserControl.ascx" TagName="Menu"

</asp:Content>
Runat="Server">
<div id="Menu">
</div>
<div id ="Center">
<div id="AllHomeContent">Product</div>
<div>
<tr>
<td> Enter Product Image</td>
<td><asp:FileUpload ID="FileUpload1" runat="server" /></td>
30
</tr>
<tr>
<td>Enter Product Name</td>
<td><asp:TextBox ID="TxtName" runat="server"></asp:TextBox></td>
</tr>
<tr>
<td>Enter Product Cost</td>
<td><asp:TextBox ID="TxtName2" runat="server"></asp:TextBox></td>
<%--<td><asp:HiddenField ID="Hid" runat="server" Value="0"/></td>--%>
</tr>
<tr>
<td>save</td>
<td><asp:Button ID="BtnSave" runat="server" Width="50px" Height="20px"
Text="Save" onclick="BtnSave_Click" /></td>
</tr>
</table>
</div>
<%--//--------------------Fetch
Table--------------------------------------------------------%>
<div>

<HeaderTemplate>
<table>
<tr>
<td class="Rpt1">ProductImage</td>
<td class="Rpt1">ProductName</td>
<td class="Rpt1">ProductCost</td>
</tr>
</HeaderTemplate>
<ItemTemplate>
<tr>
<td class="Rpt2">
<img src='<%#getimagepath(Eval("ProductImage").ToString())
%>' width="100px" height="100px" alt="" />
</td>
<td class="Rpt2"><%#Eval("ProductName") %></td>
<td class="Rpt2"><%#Eval("ProductCost") %></td>

/></td>
31
<td class="Rpt2">
</td>
</tr>
</ItemTemplate>
<FooterTemplate>
</table>
</FooterTemplate>
</asp:Repeater>
</div>
</div>
</asp:Content>
ORDER:

AutoEventWireup="true" CodeFile="Contact.aspx.cs" Inherits="Admin_Contact" %>

<%@ Register Assembly="CKEditor.NET" Namespace="CKEditor.NET" TagPrefix="CKEditor"
%>

</asp:Content>
Runat="Server">
<div id="Menu">
</div>
<div id="Center">
<div id="AllHomeContent">:-Order-:</div>
<div>
32
<table style="color:Black; padding-left:30px; margin-left:300px;">
<tr>
<td>EnterItemName</td>
<td><asp:TextBox ID="txtName" runat="server"></asp:TextBox></td>
</tr>
<tr>
<td>Submit</td>
<td>
<asp:Button ID="Btn_Submit" runat="server" Text="Submit"
ValidationGroup="S1"
onclick="Btn_Submit_Click" />
</td>
</tr>
</table>
</div>
<div>
<HeaderTemplate>
<table>
<tr>
<td class="Rpt1">ItemName</td>
<td class="Rpt1">Add More</td>
</tr>
</HeaderTemplate>
<ItemTemplate>
<tr>
<td class="Rpt2"><%#Eval("ItemName") %></td>
CommandName="Delete" CommandArgument='<
%#Eval("ID") %>' /></td>
<td class="Rpt2">
</td>
<%-- <td class="Rpt2"><a href="FK_Order.aspx?ID=<

%#Eval("ID") %>">Add More</a></td>
--%> </tr>
</ItemTemplate>
<FooterTemplate>
</table>
33
</FooterTemplate>
</asp:Repeater>
</div>
</div>
</asp:Content>
F.K ORDER:

AutoEventWireup="true" CodeFile="FK_Order.aspx.cs" Inherits="Admin_FK_Order" %>
<%@Register Src="~/WebUserControl/WebUserControl.ascx" TagName="Menu"

TagPrefix="Menubar"%>

</asp:Content>
Runat="Server">
<div id="Menu">
</div>
<div id="Center">
34
<div id="AllHomeContent">-:Rate:Order:-</div>
<div>
<table style="color:Black; padding-left:30px; margin-left:300px;">
<tr>
<td>
Select Item:
</td>
<td>
<asp:DropDownList ID="DDLItem" runat="server" Height="16px"
Width="120px" AutoPostBack="true">
</asp:DropDownList>
</td>
</tr>
<tr>
<td>Enter Item Rate</td>
<td><asp:TextBox ID="txtRate" runat="server"></asp:TextBox> </td>
<td><asp:HiddenField ID="Hid" runat="server" Value="0" /></td>
</tr>
<tr>
<td>Sumbit</td>
<td><asp:Button ID="Btn_Save" runat="server" Text="Save"
onclick="Btn_Save_Click"/></td>
</tr>
<tr>
</tr>
</table>
</div>
<div>
<HeaderTemplate>
<table>
<tr>
<td class="Rpt1">ItemName</td>
<td class="Rpt1">ItemRate</td>
</tr>
</HeaderTemplate>
<ItemTemplate>
<tr>
<td class="Rpt2"><%#Eval("ItemRate") %></td>
CommandName="Delete"
CommandArgument='<%#Eval("ID") %>' /></td>
35
<td class="Rpt2">
</tr>
</ItemTemplate>
<FooterTemplate>
</table>
</FooterTemplate>
</asp:Repeater>
</div>
</div>
</asp:Content>
CURRENT ORDER:

AutoEventWireup="true" CodeFile="CurrentOrder.aspx.cs"
Inherits="Admin_CurrentOrder" %>
</asp:Content>
Runat="Server">
<div id="Menu">
</div>
<div id ="Center">
<asp:Repeater ID="Rpt" runat="server">
36
<HeaderTemplate>
<table>
<tr>
<td class="Rpt1">Item Name</td>
<td class="Rpt1">Item Rate</td>
<td class="Rpt1">Address</td>
<td class="Rpt1">Mobile_No</td>
<td class="Rpt1">Delivery_Type</td>
</tr>
</HeaderTemplate>
<ItemTemplate>
<tr>
<td class="Rpt2"><%#Eval("ItemRate") %></td>
<td class="Rpt2"><%#Eval("Address") %></td>
<td class="Rpt2"><%#Eval("Mobile_No") %></td>
<td class="Rpt2"><%#Eval("Delivery_Type") %></td>
</tr>
</ItemTemplate>
<FooterTemplate>
</table>
</FooterTemplate>
</asp:Repeater>
</div>
</asp:Content>
FRONT END:
HOME:
<%@ Page Title="" Language="C#" MasterPageFile="~/Master_Pages/Common.master"

AutoEventWireup="true" CodeFile="Home.aspx.cs" Inherits="Home" %>
<%@ Register Src="~/WebUserControl/WebUserControl3.ascx" TagName="Jquery"

TagPrefix="Jquer" %>
<%@ Register Src="~/WebUserControl/WebUserControl2.ascx" TagName="Menb"

TagPrefix="Mens" %>

</asp:Content>
37
Runat="Server">
<div id="Imgbar">
<Jquer:Jquery ID="Jquer" runat="server" />
</div>
<div id="Menu">
<Mens:Menb ID="Menus" runat="server" />
</div>
<div id="Center">
<%------------------------Sidebar Images
Start------------------------------------------%>
<div id="CenterHome">
<div id="CenterHome2">
<marquee scrollamount="5" direction ="up" height="500px"
onmouseover="stop();" onmouseout="start();">
<img src="Upload/Home/1.jpg" width="200px" height="100" alt=""
class="imgs" />

class="imgs"/>

class="imgs"/>

class="imgs"/>

</marquee>
</div>
</div>
<%-------------------Ending Images
Marquee----------------------------------------------------------%>
<%-----------------------Starting In Repeater Control in

Content----------------------------------%>
<div id="CenterHome1">
<div id="CenterHomeMid">

<HeaderTemplate>
<table>
</HeaderTemplate>
<ItemTemplate>
<tr>
<td><%#Eval("HomeContent") %></td>
</tr>
</ItemTemplate>
<FooterTemplate>
38
</table>
</FooterTemplate>
</asp:Repeater>
</div>
<%---------------------Ending repeater control in Home
Content-----------------------------------------------------%>
<%---------------------Starting Home
Images--------------------------------------------------%>
<div id="HomeImages">
<div class="HomeImg"><img src="Upload/MainImg/thali.jpg" width="150px"
height="100px" alt="" /></div>
<div class="HomeImg1"><img src="Upload/MainImg/bbq-shrimp-and-grits.jpg"
width="150px" height="100px" alt="" /></div>
<div class="HomeImg1"><img src="Upload/MainImg/pizza.jpg" width="150px"
height="100px" alt=""/></div>
<div class="HomeImg1"><img src="Upload/MainImg/14.jpg" width="150px"
</div>
</div>
<%---------------------Ending
Images------------------------------------------------------------%>
</div>
</asp:Content>
ABOUT:

AutoEventWireup="true" CodeFile="About.aspx.cs" Inherits="About" %>
TagPrefix="Mens" %>

</asp:Content>
Runat="Server">
<div id="Imgbar">
39
</div>
<div id="Menu">
</div>
<div id="Center">
<div id="Aboutimg"><img src="Upload/MainImg/AboutUs.jpg" alt="" /></div>

<div id="AboutContent">

<HeaderTemplate>
<table>
</HeaderTemplate>
<ItemTemplate>
<tr>
<td><%#Eval("AboutContent") %></td>
</tr>
</ItemTemplate>
<FooterTemplate>
</table>
</FooterTemplate>
</asp:Repeater>
<asp:Label ID="lbl" runat="server"></asp:Label>
</div>
<div id="ImageAbout"><img src="Upload/MainImg/AboutUs2.jpg" alt="" /></div>
</div>
</asp:Content>
GALLERY:

AutoEventWireup="true" CodeFile="Gallary.aspx.cs" Inherits="Gallary" %>
<%@ Register Src="~/WebUserControl/WebUserControl3.ascx" TagName="Jquerys"

TagPrefix="JqueryPics" %>
<%@ Register Src="~/WebUserControl/WebUserControl2.ascx" TagName="Menus"

TagPrefix="Meus" %>
</asp:Content>
Runat="Server">
<div id="Imgbar"><JqueryPics:Jquerys ID="Jqueryr" runat="server" /></div>
40
<div id="Menu">
<Meus:Menus ID="Mes" runat="server" />
</div>
<div id="Center">
<%--------------------------------Starting on the Gallary

Images----------------------------------------------%>
<div id="Gallary1">
<div id="AllGallary"><h1>Gallery</h1></div>
<div>
<asp:DataList ID="Dlt" runat="server" CellSpacing="1"
RepeatColumns="6" RepeatDirection="Horizontal" ShowFooter="true">
<HeaderTemplate>
<table>
</HeaderTemplate>
<ItemTemplate>
<p style="font-size:15px;color:Green; padding-left:45px;

text-align:center;">
<img src='<%#getimagepath(Eval("ImageGallery").ToString())
%>' width="100px" height="100px" alt="" /></p>

text-align:center;"><%#Eval("Name") %></p>
</ItemTemplate>
<AlternatingItemTemplate>

<img src='<
%#getimagepath(Eval("ImageGallery").ToString()) %>' width="100px" height="100px"
alt="" /></p>
</p>
text-align:center;"><%#Eval("Name") %></p>
</AlternatingItemTemplate>
<FooterTemplate>
</table>
</FooterTemplate>
</asp:DataList>
</div>
41
</div>
</div>
</asp:Content>
BLOG:

AutoEventWireup="true" CodeFile="Blog.aspx.cs" Inherits="Blog" %>
TagPrefix="Mens" %>
</asp:Content>
Runat="Server">
<div id="Imgbar">
42
</div>
<div id="Menu">
</div>
<div id="Center">
<%------------------------Sidebar Images
Start------------------------------------------%>
<div id="BlogHome">
<div id="CenterBlog2">
<marquee scrollamount="5" direction ="up" height="500px"
onmouseover="stop();" onmouseout="start();">
class="imgs" />

class="imgs"/>

class="imgs"/>

class="imgs"/>

</marquee>
</div>
</div>
<%-------------------Ending Images
Marquee----------------------------------------------------------%>
<%-----------------------Starting In Repeater Control in

Content----------------------------------%>
<div id="CenterBlog1">
<div id="AllBlog"><h1>:Blog:</h1></div>
<div id="BlogHomeMid">
<table style="color:Black; padding-left:30px; margin-left:200px; margin-
top:10px;" class="Gallarytab">
<tr>
<td>Enter Name</td>
<td><asp:RequiredFieldValidator ID="Rfv1" runat="server"
ControlToValidate="txtName" ErrorMessage="*Required" ValidationGroup="B1"
ForeColor="Red">
</asp:RequiredFieldValidator></td>
</tr>
<tr>
<td>Enter Subject</td>
<td><asp:TextBox ID="txtSub" runat="server"></asp:TextBox></td>
43
ControlToValidate="txtSub" ErrorMessage="*Required" ValidationGroup="B1"
ForeColor="Red">
</tr>
<tr>
<td>Enter Comment</td>
<td><asp:TextBox ID="txtComment" runat="server"
TextMode="MultiLine"></asp:TextBox></td>
ControlToValidate="txtComment" ErrorMessage="*Required" ValidationGroup="B1"
ForeColor="Red">
</tr>
<tr>
<td>Save</td>
<td><asp:Button ID="Btn_Save" runat="server" Text="Submit"
ValidationGroup="B1"
onclick="Btn_Save_Click"/></td>
<td><asp:Label ID="lbl" runat="server"></asp:Label> </td>
</tr>
</table>
</div>
<%---------------------Ending Home
Content-----------------------------------------------------%>
</div>
</div>
</asp:Content>
PRODUCT:

AutoEventWireup="true" CodeFile="Product.aspx.cs" Inherits="Product" %>

TagPrefix="Meus" %>
</asp:Content>
44
Runat="Server">
<div id="Menu">
</div>
<div id="Center">
<%--------------------------------Starting on the Gallary
Images----------------------------------------------%>
<div id="Product1">
<div id="AllProduct"><h1>:All-Products:</h1></div>
<div>
<asp:DataList ID="Dlt" runat="server" CellSpacing="1"
RepeatColumns="6" RepeatDirection="Horizontal" ShowFooter="true">
<HeaderTemplate>
<table>
</HeaderTemplate>
<ItemTemplate>
<p style="font-size:15px;color:Black; padding-left:45px;

<img src='<%#getimagepath(Eval("ProductImage").ToString())
%>' width="100px" height="100px" alt="" /></p>

text-align:center;"><%#Eval("ProductName") %></p>
text-align:center;"><%#Eval("ProductCost") %></p>
</ItemTemplate>
<AlternatingItemTemplate>

<img src='<
%#getimagepath(Eval("ProductImage").ToString()) %>' width="100px" height="100px"
alt="" /></p>
</p>
text-align:center;"><%#Eval("ProductName") %></p>
text-align:center;"><%#Eval("ProductCost") %></p>
</AlternatingItemTemplate>
<FooterTemplate>
</table>
</FooterTemplate>
</asp:DataList>
45
</div>
</div>
</div>
</asp:Content>
ORDER NOW:

AutoEventWireup="true"
CodeFile="OrderNow.aspx.cs" Inherits="OrderNow" %>

46
TagPrefix="Meus" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" runat="Server">
<style type="text/css">
.style1
{
height: 50px;
}
.style2
{
height: 49px;
}
</style>
</asp:Content>
runat="Server">
<div id="Imgbar">
<JqueryPics:Jquerys ID="Jqueryr" runat="server" />
</div>
<div id="Menu">
</div>
<div id="Center">
<div id="CenterOrder"><img src="Upload/MainImg/orderpic.jpg" width="300px"
<div id="Centerorder">
<table style="color:Black; border:2px dotted #996633; padding-left:30px;

margin-left:100px; margin-top:50px;"
class="Gallarytab">
<tr>
<td class="style1">
Select Your Item:
</td>
<td class="style1">
<asp:DropDownList ID="DDLItem" runat="server"
AutoPostBack="True" OnSelectedIndexChanged="DDLItem_SelectedIndexChanged">
</asp:DropDownList>
</td>
<td class="style1"><asp:RequiredFieldValidator ID="Rfv"
runat="server"
ControlToValidate="DDLItem" ErrorMessage="Please Select The
DropDown" ValidationGroup="O1">
</tr>
<tr>
<td class="style1">
Enter Price:
</td>
<td class="style1">
<asp:DropDownList ID="DDLItemRate" runat="server"
AutoPostBack="True">
</asp:DropDownList>
</td>
47
<td class="style1"><asp:RequiredFieldValidator ID="Rfv1"
runat="server"
ControlToValidate="DDLItemRate" ErrorMessage="Please Select
The DropDown" ValidationGroup="O1">
</tr>
<tr>
<td class="style1">Enter Name</td>
<td class="style1"><asp:TextBox ID="txtName"
runat="server"></asp:TextBox></td>
<td class="style1"><asp:RequiredFieldValidator ID="Rqf2"
runat="server"
ControlToValidate="DDLItemRate" ErrorMessage="Please Fill
Name" ValidationGroup="O1">
</tr>
<tr>
<td class="style1">Enter Address</td>
<td class="style1"><asp:TextBox ID="txtAdd"
<td class="style1"><asp:RequiredFieldValidator ID="Rqf3"
runat="server"
Address" ValidationGroup="O1">
</tr>
<tr>
<td class="style1">Enter Mobile</td>
<td class="style1"><asp:TextBox ID="txtMobile"
<td class="style1"><asp:RequiredFieldValidator ID="Rqfv4"
runat="server"
Mobile No" ValidationGroup="O1">
</tr>
<tr>
<td class="style2">Enter Delievery_Type</td>
<td class="style2"><asp:TextBox ID="txtDel"
<td class="style2"><asp:RequiredFieldValidator ID="Rqfv"
runat="server"
Delivery Type" ValidationGroup="O1">
</tr>
<tr>
<td>
48
<asp:Button ID="btnSave" runat="server" Text="Order"
onclick="btnSave_Click"
Width="66px" />
</td>
</tr>
</table>
</div>
</div>
</asp:Content>
LOGIN:
49
AutoEventWireup="true" CodeFile="Login.aspx.cs" Inherits="Login" %>

TagPrefix="Meus" %>
</asp:Content>
Runat="Server">
<div id="Menu">
</div>
<div id="Center">
<div id="Login">

<tr>
<td>User Name</td>
<td><asp:RequiredFieldValidator ID="rfvs" runat="server"
ControlToValidate="txtName" ErrorMessage="*Required" ValidationGroup="U1"
ForeColor="Red"></asp:RequiredFieldValidator></td>
</tr>
<tr>
<td>Password</td>
<td><asp:TextBox ID="txtPass" runat="server"
TextMode="Password"></asp:TextBox> </td>
<td><asp:RequiredFieldValidator ID="Rfc" runat="server"
ControlToValidate="txtPass" ErrorMessage="*Required" ValidationGroup="U1"
</tr>
<tr>
<td>Save</td>
ValidationGroup="U1"
onclick="Btn_Save_Click1"/></td>
</tr>
<tr>
</tr>
</table>
</div>
</div>
</asp:Content>
CSS(CASCADING STYLE SHEETS):
50
It defines how to style sheets.There are three types of the style sheets .
1. Inline
2. Internal
3. External
We have used external style sheets because it is ideal when the style is to be appled on
many sheets. It can change the look of the entire websiteby changinh one file. Each page
must link to the style sheet using <link> tag.
ADMIN CSS:

AutoEventWireup="true" CodeFile="Login.aspx.cs" Inherits="Login" %>

TagPrefix="Meus" %>
</asp:Content>
Runat="Server">
<div id="Menu">
</div>
<div id="Center">
<div id="Login">

<tr>
<td>User Name</td>
<td><asp:RequiredFieldValidator ID="rfvs" runat="server"
ControlToValidate="txtName" ErrorMessage="*Required" ValidationGroup="U1"
</tr>
<tr>
<td>Password</td>
<td><asp:TextBox ID="txtPass" runat="server"
TextMode="Password"></asp:TextBox> </td>
<td><asp:RequiredFieldValidator ID="Rfc" runat="server"
ControlToValidate="txtPass" ErrorMessage="*Required" ValidationGroup="U1"
</tr>
<tr>
<td>Save</td>
ValidationGroup="U1"
onclick="Btn_Save_Click1"/></td>
</tr>
51
<tr>
</tr>
</table>
</div>
</div>
</asp:Content>
FRONT END CSS:
52
body
{
background-image:url('../Upload/MainImg/B_Main.jpeg');
background-attachment:fixed;
}
*
{
margin:0px 0px 4px 0px;
padding:0px;
}
#Main
{
width:1000px;
height:auto;
background-color:Transparent;
margin:auto;
}
#Header
{
width:1000px;
height:125px;
background-color:White;
}
#Head2
{
width:700px;
height:125px;
float:left;
text-align:center;
color:#6F4E37;
#Head3
{
width:300px;
height:125px;
float:left;
padding-top:20px;
font-size:20px;
text-align:center;
}
#Imgbar
{
width:1000px;
height:300px;
}
#Menu
53
{
width:1000px;
height:50px;
background-color:#6F4E37;
}
#Centerbar
{
width:1000px;
height:auto;
}
#Footer
{
width:1000px;
height:25px;
background-color:#6F4E37;
text-align:justify;
color:White;
font-size:15px;
float:left;
text-align:center;
}
#Center
{
width:1000px;
height:auto;
float:left;
}
#CenterOrder
{
width:300px;
height:500px;
background-color:Blue;
float:left;
}
#Centerorder
{
width:700px;
height:500px;
background-color:white;
float:left
}
#CenterHome
{
width:250px;
height:auto;
float:left;
}
#CenterHome1
54
{
width:750px;
height:auto;
float:left;
}
#CenterHomeMid
{
width:700px;
height:auto;
float:left;
margin-left:20px;
margin-top:20px;
}
#CenterBlogMid
{
width:700px;
height:350px;
float:left;
margin-left:20px;
margin-top:20px;
#CenterHome2
{
width:230px;
height:auto;
margin-left:8px;
}
#CenterBlog2
{
width:230px;
height:500px;
margin-left:8px;
}
.imgs
{
width:200px;
height:100px;
margin-left:13px;
}
#BlogImages
{
width:750px;
height:120px;
background-color:yellow;
float:left;
margin-top:3px;
55
}
#HomeImages
{
width:750px;
height:120px;
float:left;
margin-top:3px;
}
.HomeImg
{
width:150px;
height:100px;
background-color:Olive;
margin-top:5px;
margin-left:17px;
float:left;
}
.HomeImg1
{
width:150px;
height:100px;
background-color:Olive;
margin-top:5px;
margin-left:35px;
float:left;
}
#Abouts
{
width:900px;
height:auto;
margin:auto;
text-align:justify;
color:Black;
}
#Aboutimg
{
width:250px;
height:350px;
float:left;
margin-left:5px;
}
#AboutContent
{
width:450px;
height:auto;
margin-left:20px;
float:left;
}
#ImageAbout
{
width:250px;
56
height:350px;
float:left;
margin-left:20px;
#Gallary1
{
width:900px;
height:auto;
margin:auto;
}
#Product1
{
width:900px;
height:auto;
margin:auto;
}
#AllGallary
{
width:900px;
height:50px;
color:Black;
text-align:center;
}
#AllProduct
{
width:900px;
height:50px;
color:Black;
text-align:center;
}
#CenterBlog
{
width:1000px;
height:500px;
float:left;
}
#CenterBlog1
{
width:750px;
height:500px;
float:left;
}
#BlogHome
57
{
width:250px;
height:500px;
float:left;
}
#AllBlog
{
width:750px;
height:50px;
text-align:center;
color:Black;
}
#CenterContact
{
width:400px;
height:500px;
float:left;
}
#CenterContact1
{
width:600px;
height:500px;
float:left;
}
#Ctn
{
width:600px;
height:50px;
text-align:center;
color:Black;
font-size:20px;
}
#Login
{
width:500px;
height:500px;
margin:auto;
}
.logindec
{
text-decoration:none;
color:Black;
}
.list
{
display:block;
color:White;
padding-left:20px;
58
list-style-type:none;
width:160px;
margin-left:10px;
padding-top:10px;
float:left;
}
.List1
{
color:White;
}
.Gallarytab
{
text-align:justify;
}
59
DAL(DATA ACCESS LAYER);
A data access layer (DAL) in computer software, is a layer of a computer program

which provides simplified access to data stored in persistent storage of some kind, such
as an entity-relational database. This acronym is prevalently used in Microsoft ASP.NET
environments.
For example, the DAL might return a reference to an object (in terms of object-oriented
programming) complete with its attributes instead of a row of fields from a database
table. This allows the client (or user) modules to be created with a higher level of
abstraction. This kind of model could be implemented by creating a class of data access
methods that directly reference a corresponding set of database stored procedures.
Another implementation could potentially retrieve or write records to or from a file
system. The DAL hides this complexity of the underlying data store from the external
world.
For example, instead of using commands such as insert, delete, and update to access a
specific table in a database, a class and a few stored procedures could be created in the
database. The procedures would be called from a method inside the class, which would
return an object containing the requested values. Or, the insert, delete and update
commands could be executed within simple functions like register user or login user
stored within the data access layer.
Applications using a data access layer can be either database server dependent or
independent. If the data access layer supports multiple database types, the application
becomes able to use whatever databases the DAL can talk to. In either circumstance,
having a data access layer provides a centralized location for all calls into the database,
and thus makes it easier to port the application to other database systems (assuming that
100% of the database interaction is done in the DAL for a given application).
60
DAL CODING:
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Data.SqlClient;
using System.Data;
/// <summary>
/// Summary description for Dal
/// </summary>
public class Dal
{
public Dal()
{
//
// TODO: Add constructor logic here
//
}
private string strRate; // Bill order front

private string strItemName; //bill order front
private string strCustomer_Name;//bill order front
private string strAddress; //bill order front
private string Mobile_No; //bill order front
private string strDelivery_Type; //bill order front
private int int_FK_ID;
private string StrContent;

private string StrIMG;
private int IntID;
private string StrAboutContent; // About Form
private string StrImageGallery; //Gallery Form
private string StrName; // Gallery form
private string StrInsertContact; // ContactForm
private string StrProductImage;//product Form
private string StrProductName;// Prodct Form
private string StrProductCost;// Product Form
private string StrNames;//Blogs

private string StrSubject;// Blogs
private string StrComment;// Blogs
private string StrUserName;

private string StrPassword;
//Order
/// <summary>
/// bill order front
/// </summary>
public int P_int_FK_ID
61
{
get
{
return int_FK_ID;
}
set
{
int_FK_ID = value;
}
}
public string P_strRate
{
get
{
return strRate;
}
set
{
strRate = value;
}
}
public string P_strItemName
{
get
{
return strItemName;
}
set
{
strItemName = value;
}
}
public string P_Mobile_No

{
get
{
return Mobile_No;
}
set
{
Mobile_No = value;
}
}
public string P_str_Cus_Name

{
get
{
return strCustomer_Name;
}
set
{
62
strCustomer_Name = value;
}
}
public string P_strAddress

{
get
{
return strAddress;
}
set
{
strAddress = value;
}
}
public string P_str_Delivery_Type

{
get
{
return strDelivery_Type;
}
set
{
strDelivery_Type = value;
}
}
/// <summary>
/// ending of bill order front
/// </summary>
public string P_StrUserName
{
get
{
return StrUserName;
}
set
{
StrUserName = value;
}
}
public string P_StrPassword

{
get
{
return StrPassword;
}
set
{
StrPassword = value;
63
}
}
public string P_StrContent

{
get
{
return StrContent;
}
set
{
StrContent = value;
}
}
public string P_StrIMG

{
get
{
return StrIMG;
}
set
{
StrIMG = value;
}
}
public int P_IntID

{
get
{
return IntID;
}
set
{
IntID = value;
}
}
//----------Property About form----------
public string P_StrAboutContent

{
get
{
return StrAboutContent;
}
set
{
StrAboutContent = value;
}
64
}
//------------Ending Of The Property------------------
//-----------Property For Gallery form-----------------
public string P_StrImageGallery

{
get
{
return StrImageGallery;
}
set
{
StrImageGallery = value;
}
}
public string P_StrName

{
get
{
return StrName;
}
set
{
StrName = value;
}
}
//---------------Ending Of the gallery
Property------------------------------------------------
//---------------Property of Contact Form-----------------------------------
public string P_StrInsertContact

{
get
{
return StrInsertContact;
}
set
{
StrInsertContact = value;
}
}
//----------Property of product
-------------------------------------------------------------
public string P_StrProductImage

{
get
{
return StrProductImage;
65
}
set
{
StrProductImage= value;
}
}
public string P_StrProductName

{
get
{
return StrProductName;
}
set
{
StrProductName = value;
}
}
public string P_StrProductCost

{
get
{
return StrProductCost;
}
set
{
StrProductCost = value;
}
}
//---------------Ending Of Product Property--------------------------------
/// <summary>
/// /////////Blogs
/// </summary>
public string P_StrBlogNames

{
get
{
return StrNames;
}
set
{
StrNames = value;
66
}
public string P_StrSubject

{
get
{
return StrSubject;
}
set
{
StrSubject = value;
}
}
public string P_StrComments

{
get
{
return StrComment;
}
set
{
StrComment = value;
}
}
/////// Property of Bill order front
public string P_StrC

{
get
{
return StrComment;
}
set
{
StrComment = value;
}
}
//////////////////////Ending
Blogss/////////////////////////////////////////////////////////
//-----------------Ending Of Contact Form

-------------------------------------------------
//---------Insert Method of HomeContent-

public void InsertContent(Dal c)
67
{
string StrCon = Dal_Lib.GetConnection();
SqlConnection con = new SqlConnection(StrCon);
con.Open();
SqlCommand cmd = new SqlCommand("Mst_HomeCont", con);
SqlParameter param1 = new SqlParameter("@HomeContent", SqlDbType.NChar);
SqlParameter param2 = new SqlParameter("@ID", SqlDbType.Int);
param1.Value = c.P_StrContent;
param2.Value = c.P_IntID;
cmd.Parameters.Add(param1);
cmd.CommandType = CommandType.StoredProcedure;
cmd.ExecuteNonQuery();
}
//---------------Fetch Procedure Of Home Content-------------

public DataSet Fetch_HomeContent(Dal c)
{
con.Open();
SqlCommand cmd = new SqlCommand("Fetch_Content", con);
SqlDataAdapter sd = new SqlDataAdapter(cmd);
DataSet ds = new DataSet();
sd.Fill(ds);
return ds;
}
//----------------Starting of Delete
HomeContent------------------------------------
public void Del_Content(Dal c)
{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_Del", con);
SqlParameter param1 = new SqlParameter("@ID", SqlDbType.NChar);
}
public DataSet Edit_Content(Dal C) //Starting Code int Edit Update

Name,And Pic Indian Music////
{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_Edit_HomeContent", con);
68
param1.Value = C.P_IntID;
sd.Fill(ds);
return ds;
}
//-------------------Starting of Insert procedure AboutContent------
public void InsertAboutContent(Dal c)

{
string strconn = Dal_Lib.GetConnection();
SqlConnection con = new SqlConnection(strconn);
con.Open();
SqlCommand cmd = new SqlCommand("Mst_About", con);
SqlParameter param1 = new SqlParameter("@AboutContent", SqlDbType.NChar);
param1.Value=c.P_StrAboutContent;
cmd.CommandType= CommandType.StoredProcedure;
//-------------Function For Fetch

AboutContent--------------------------------------
public DataSet Fetch_About_Content(Dal c)

{
string strcon = Dal_Lib.GetConnection();
SqlConnection con = new SqlConnection(strcon);
con.Open();
SqlCommand cmd = new SqlCommand("Mst_Fetch_Content", con);
sd.Fill(ds);
return ds;
}
//------------function for del about
content---------------------------------------------
public void DelAbout(Dal c)

{
69
con.Open();
SqlCommand cmd = new SqlCommand("Mst_AboutDel", con);
public DataSet EditAbout(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_AboutEdit", con);

sd.Fill(ds);
return ds;
}
///------------------Method insert img

Gallery------------------------------------------
public void InsertIMGGallery(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_Gallary", con);

SqlParameter param1 = new
SqlParameter("@ImageGallery",SqlDbType.VarChar,100);
SqlParameter param2 = new SqlParameter("@Name", SqlDbType.VarChar,100);
SqlParameter param3 = new SqlParameter("@ID",SqlDbType.Int);
param1.Value = c.P_StrImageGallery;
param2.Value = c.P_StrName;
70
}
//--------------------Fetch Image
Gallery-----------------------------------------------------
public DataSet Fetch_Image_Gallery(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_Fetch_IMG_Gallary", con);
sd.Fill(ds);
return ds;
}
//-------------Delete Image Gallery-------------------------------------
public void Del_Img_Gallery(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_Del_IMG_Gallery", con);
}
public DataSet Edit_IMG_Gallery(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_Edit_IMG_Gallery", con);

sd.Fill(ds);
return ds;
71
}
//------------Method for contact

Insert------------------------------------------------
public void InsertContact(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_InsertContact", con);

SqlParameter param1 = new SqlParameter("@ContactContent",
SqlDbType.NChar);
param1.Value = c.P_StrInsertContact;
public void insert_Product(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_InsertProduct", con);

SqlParameter param1 = new SqlParameter("@ProductImage",
SqlDbType.VarChar,1000);
SqlParameter param2 = new SqlParameter("@ProductName", SqlDbType.VarChar,
50);
SqlParameter param3 = new SqlParameter("@ProductCost", SqlDbType.VarChar,
50);
param1.Value = c.P_StrProductImage;
param2.Value = c.P_StrProductName;
param3.Value = c.P_StrProductCost;
/// <summary>
/// Fetch Product
/// </summary>
72
/// <param name="c"></param>
/// <returns></returns>
public DataSet Fetch_Product(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_FetchProducts", con);
sd.Fill(ds);
return ds;
}
//-------------Delete Product-------------------------------------
public void DelProduct(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_DelProduct", con);
}
//---------Edit Product------------------------------------
public DataSet Edit_Product(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_EditProduct", con);

sd.Fill(ds);
return ds;
}
73
//////////////////////////////////////////////////////////////////////////////
//
public void InsertBlogs(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_Blog", con);
SqlParameter param1 = new SqlParameter("@Name", SqlDbType.VarChar,100);
SqlParameter param2 = new SqlParameter("@Subject", SqlDbType.VarChar,100);
SqlParameter param3 = new SqlParameter("@Comment", SqlDbType.NChar);
param1.Value = c.P_StrBlogNames;
param2.Value = c.P_StrSubject;
param3.Value = c.P_StrComments;
}
public DataSet Bloged(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Fetch_Blog", con);

sd.Fill(ds);
return ds;
}
public DataSet Fetch_Login(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_Login", con);
SqlParameter param1 = new SqlParameter("@UserName",SqlDbType.VarChar,100);
SqlParameter param2 = new SqlParameter("@Password",SqlDbType.VarChar,100);
param1.Value = c.P_StrUserName;
param2.Value = c.P_StrPassword;
74

sd.Fill(ds);
return ds;
}
//-----------------------------Delete blog
public void DelBlog(Dal c)
{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_DelBlog", con);
}
//---------Insert Method of Order Information-
public void InsertOrder(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_Order", con);
SqlParameter param1 = new SqlParameter("@ItemName",
SqlDbType.VarChar,100);
param1.Value = c.P_strItemName;
}
public DataSet FetchOrder(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Fetch_Order", con);
// SqlParameter param1 = new SqlParameter("@ID",SqlDbType.Int);
//param1.Value = c.P_IntID;
//cmd.Parameters.Add(param1);
75
SqlDataAdapter ad = new SqlDataAdapter(cmd);
ad.Fill (ds);
return ds;
}
//-------------Delete Order -------------------------------------
public void Del_Order(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_DelOrder", con);
}
public DataSet Edit_Order(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Mst_Edit_Order", con);
sd.Fill(ds);
return ds;
}
/// <summary>
/// ///////////////Ending Order Information///////////////////////////
/// </summary>
//////////////////////////////////////////////////////////////////////////////
///////////////
/// <summary>
/// //////////////////////////FK
_Order //////////////////////////////////////////////////
/// </summary>
public void InsertOrdIns(Dal c)

{
76
con.Open();
SqlCommand cmd = new SqlCommand("InsertTxn_Ord", con);
SqlParameter param1 = new SqlParameter("@FK_ID", SqlDbType.Int);
SqlParameter param2 = new SqlParameter("@ItemName", SqlDbType.VarChar,
100);
SqlParameter param3 = new SqlParameter("@ItemRate", SqlDbType.VarChar,
100);
param1.Value = c.P_int_FK_ID;
param3.Value = c.P_strRate;
}
public DataSet Fetch_Txn_Order(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Fetch_Txn", con);
SqlDataAdapter ad = new SqlDataAdapter(cmd);
ad.Fill(ds);
return ds;
}
//-------------Delete FK Order -------------------------------------
public void Del_FK_Order(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Txn_Del_Order", con);
}
public DataSet Edit_FK_Order(Dal c)

{
77
con.Open();
SqlCommand cmd = new SqlCommand("Txn_Edit_Order", con);
sd.Fill(ds);
return ds;
}
public DataSet Front_Order(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("Pro_Change", con);
sd.Fill(ds);
return ds;
}
/// <summary>
/// ///////////////Ending FK_Order Information///////////////////////////
/// </summary>
/////////////////////////////////////////////////
/// <summary>
/// ////////Insertion Front Code Billing Information///
/// </summary>
public void InsertBillingSystem(Dal c)

{
con.Open();
SqlCommand cmd = new SqlCommand("InsertBilling", con);
78
SqlParameter param2 = new SqlParameter("@ItemName", SqlDbType.VarChar,
100);
SqlParameter param3 = new SqlParameter("@ItemRate", SqlDbType.VarChar,
100);
SqlParameter param4= new SqlParameter("@Name", SqlDbType.VarChar, 50);
SqlParameter param5 = new SqlParameter("@Address", SqlDbType.VarChar, 50);
SqlParameter param6= new SqlParameter("@Mobile_No", SqlDbType.VarChar,50);
SqlParameter param7= new SqlParameter("@Delivery_Type", SqlDbType.VarChar,
50);
param3.Value = c.P_strRate;
param4.Value = c.P_str_Cus_Name;
param5.Value = c.P_strAddress;
param6.Value = c.P_Mobile_No;
param7.Value = c.P_str_Delivery_Type;
}
public DataSet Fetch_Billing(Dal C)

{
con.Open();
SqlCommand cmd = new SqlCommand("Fetch_Bill", con);
sd.Fill(ds);
return ds;
}
}
79
DAL Lib CODING:
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Configuration;
/// <summary>
/// Summary description for Dal_Lib
/// </summary>
public class Dal_Lib
{
public Dal_Lib()
{
//
// TODO: Add constructor logic here
//
}
public static string GetConnection()

{
return ConfigurationSettings.AppSettings["strconnection"];
}
public static string GetBaseSiteUrl()

{
return ConfigurationSettings.AppSettings["BaseSiteUrl"];
}
80
TESTING:
Software Testing is an empirical investigation conducted to provide stakeholders with

information about the quality of the product or service under test, with respect to the
context in which it is intended to operate. Software Testing also provides an objective,
independent view of the software to allow the business to appreciate and understand the
risks at implementation of the software. Test techniques include, but are not limited to,
the process of executing a program or application with the intent of finding software
bugs. It can also be stated as the process of validating and verifying that a software
program/application/product meets the business and technical requirements that guided
its design and development, so that it works as expected and can be implemented with the
same characteristics.
Software Testing, depending on the testing method employed, can be implemented

at any time in the development process, however the most test effort is employed after the
requirements have been defined and coding process has been completed.
UNIT TESTING: The primary goal of unit testing is to take the smallest piece of testable
software in the application, isolate it from the remainder of the code, and determine
whether it behaves exactly as you expect. Each unit is tested separately before integrating
them into modules to test the interfaces between modules. Unit testing has proven its
value in that a large percentage of defects are identified during its use.
81
Unit testing is a software verification and validation method where the programmer
gains confidence that individual units of source code are fit for use. A unit is the smallest
testable part of an application. In procedural programming a unit may be an individual
program, function, procedure, etc., while in object-oriented programming, the smallest
unit is a class, which may belong to a base/super class, abstract class or derived/child
class.
Ideally, each test case is independent from the others: substitutes like method stubs, mock
objects, fakes and test harnesses can be used to assist testing a module in isolation. Unit
tests are typically written and run by software developers to ensure that code meets its
design and behaves as intended. Its implementation can vary from being very manual
(pencil and paper) to being formalized as part of build automation.
INTEGRATION TESTING: Integration testing, also known as integration and testing

(I&T), is a software development process which program units are combined and tested
as groups in multiple ways. In this context, a unit is defined as the smallest testable part
of an application. Integration testing can expose problems with the interfaces among
program components before trouble occurs in real-world program execution. Integration
testing is a component of Extreme Programming (XP), a pragmatic method of software
development that takes a meticulous approach to building a product by means of
continual testing and revision.
There are two major ways of carrying out an integration test, called the bottom-up
method and the top-down method. Bottom-up integration testing begins with unit testing,
followed by tests of progressively higher-level combinations of units called modules or
builds. In top-down integration testing, the highest-level modules are tested first and
progressively lower-level modules are tested after that. In a comprehensive software
development environment, bottom-up testing is usually done first, followed by top-down
testing.
VALIDATION TESTING : At the validation level, testing focuses on user visible actions
and user recognizable output from the system. Validations testing is said to be successful
82
when software functions in a manner that can be reasonably expected by the customer.
Two types of validation testing :
ALPHA TESTING: IT is simulated or actual operational testing by potential

users/customers or an independent test team at the developers' site. Alpha testing is often
employed for off-the-shelf software as a form of internal acceptance testing, before the
software goes to beta testing.
BETA TESTING: IT comes after alpha testing. Versions of the software, known as beta
version, are released to a limited audience outside of the programming team. The
software is released to groups of people so that further testing can ensure the product has
few faults or bugs. Sometimes, beta versions are made available to the open public to
increase the feedback field to a maximal number of future users.
GRAY BOX TESTING: Grey box testing is the combination of black box and white box
testing. Intention of this testing is to find out defects related to bad design or bad
implementation of the system. It is used for web application.
83
CHAPTER-5
MAINTENANCE
Software maintenance in software engineering is the modification of a software product
after delivery to correct faults, to improve performance or other attributes.
A common perception of maintenance is that it merely involves fixing defects. However,

one study indicated that the majority, over 80%, of the maintenance effort is used for non-
corrective actions. This perception is perpetuated by users submitting problem reports
that in reality are functionality enhancements to the system. More recent studies put the
bug-fixing proportion closer to 21%.
Software maintenance and evolution of systems was first addressed by Meir M. Lehman
in 1969. Over a period of twenty years, his research led to the formulation of Lehman's
Laws (Lehman 1997). Key findings of his research include that maintenance is really
evolutionary development and that maintenance decisions are aided by understanding
what happens to systems (and software) over time. Lehman demonstrated that systems
continue to evolve over time. As they evolve, they grow more complex unless some
action such as code refactoring is taken to reduce the complexity.
The key software maintenance issues are both managerial and technical. Key
management issues are: alignment with customer priorities, staffing, which organization
84
does maintenance, estimating costs. Key technical issues are: limited understanding,
impact analysis, testing, and maintainability measurement.
Software maintenance is a very broad activity that includes error correction,

enhancements of capabilities, deletion of obsolete capabilities, and optimization. Because
change is inevitable, mechanisms must be developed for evaluation, controlling and
making modifications.
So any work done to change the software after it is in operation is considered to be

maintenance work. The purpose is to preserve the value of software over the time. The
value can be enhanced by expanding the customer base, meeting additional requirements,
becoming easier to use, more efficient and employing newer technology. Maintenance
may span for 20 years, whereas development may be 1-2 years.
PLANNING
An integral part of software is the maintenance one, which requires an accurate

maintenance plan to be prepared during the software development. It should specify how
users will request modifications or report problems. The budget should include resource
and cost estimates. A new decision should be addressed for the developing of every new
system feature and its quality objectives. The software maintenance, which can last for 5–
6 years (or even decades) after the development process, calls for an effective plan which
can address the scope of software maintenance, the tailoring of the post
delivery/deployment process, the designation of who will provide maintenance, and an
estimate of the life-cycle costs. The selection of proper enforcement of standards is the
challenging task right from early stage of software engineering which has not got definite
importance by the concerned stakeholders.
PROCESS:
This section describes the six software maintenance processes as:
1. The implementation process contains software preparation and transition

activities, such as the conception and creation of the maintenance plan; the
85
preparation for handling problems identified during development; and the follow-
up on product configuration management.
2. The problem and modification analysis process, which is executed once the
application has become the responsibility of the maintenance group. The
maintenance programmer must analyze each request, confirm it (by reproducing
the situation) and check its validity, investigate it and propose a solution,
document the request and the solution proposal, and finally, obtain all the required
authorizations to apply the modifications.
3. The process considering the implementation of the modification itself.
4. The process acceptance of the modification, by confirming the modified work

with the individual who submitted the request in order to make sure the
modification provided a solution.
5. The migration process (platform migration, for example) is exceptional, and is not
part of daily maintenance tasks. If the software must be ported to another platform
without any change in functionality, this process will be used and a maintenance
project team is likely to be assigned to this task.
6. Finally, the last maintenance process, also an event which does not occur on a
daily basis, is the retirement of a piece of software.
CATEGORIES:
E.B. Swanson initially identified three categories of maintenance: corrective, adaptive,

and perfective.[9] These have since been updated and ISO/IEC 14764 presents:
 Corrective maintenance: Reactive modification of a software product performed

after delivery to correct discovered problems.
 Adaptive maintenance: Modification of a software product performed after

delivery to keep a software product usable in a changed or changing environment.
86
 Perfective maintenance: Modification of a software product after delivery to
improve performance or maintainability.
 Preventive maintenance: Modification of a software product after delivery to

detect and correct latent faults in the software product before they become
effective faults.
CHAPTER: 6
FUTURE SCOPE
The project made here is just to ensure that this product could be valid in today real
challenging world. Here all the facilities are made and tested. Currently the system works
for limited number of administrators to work. In near future it will be extended for many
types of insurance policies so that efficiency can be improved.
87

Chapter 1

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Chapter 1

Caricato da

Copyright:

Formati disponibili

CHAPTER 1

1.1 ABOUT THE PROJECT

Why Asp.Net is used ?

3. It provides higher performance by using early binding, just-in-time compilation, native

4. ASP.NET framework is complemented by a rich and designer tools in Visual Studio

In short ASP.NET, the next generation version of Microsoft’s ASP, is a programming

C# is a multi-paradigm programming language encompassing strong typing, imperative,

C# is intended to be a simple, modern, general-purpose, object-oriented programming

C# is an evolution of the C and C++ family of languages. However, it borrows features

1.2.2 DEVELOPMENT TOOLS USED :

i. Visual Studio 2010: Microsoft Visual Studio is an integrated development

Visual Studio supports different programming languages by means of language

ii. SQL Server 2008: Microsoft SQL Server is a relational database

SQL Server 2008 (formerly codenamed "Katmai") was released on August 6,

SOFTWARE REQUIREMENT SPECIFICATIONS

1. It specifies the external system behaviors.

2.2 USER CLASS AND CHARACTERISTICS:

2.4 PERFORMANCE REQUIREMENTS:

2.5 NON FUNCTIONAL REQUIREMENTS:

Non functional requirements define system properties and constraints . It arise

2 RELIABILITY: The system provides storage of all databases on redundant

4 MAINTAINABILITY: A commercial database is used for maintaining the

5 PORTABILITY: The application is HTML and scripting language based. So the

5. GENERAL CONSTRAINTS, ASSUMPTIONS, DEPENDENCIES, GUIDELINES:

FRONT END (user interaction):

3.2 ARCHITECTURAL DESIGN:

A rectangle represents a data source or destination.

A directed line represents the flow of data that is data stream.

An enclosed figure, usually a circle or an oval bubble, represent a

An open-ended rectangle represents data storage.

DESIGN FOR THE FUNCTIONING OF DIFFERENT USERS

rejected if not Login table

Add Delete Edit

Add Name Delete Edit

Add Name Delete Edit

1 LEVEL DFD FOR USERS

Blog table Order Form table

DATABASE TABLE DESIGN

HOME CONTENT TABLE :

ABOUT CONTENT TABLE:

ORDER FORM TABLE:

An important concept that helps the understandability of programs is structured

For structured programming, a few single-entry-single-exit constructs should be used.

USER INTERFACE CODING: This coding is done to design the website . it

<%@ Page Title="" Language="C#" MasterPageFile="~/Master_Pages/Admin.master"

<%@ Register Src="~/WebUserControl/WebUserControl.ascx" TagName="Menubarr"

<%@ Register Assembly="CKEditor.NET" Namespace="CKEditor.NET"

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

<%------------------------Ending Table Data insertion------------------------%>

<%@ Page Title="" Language="C#" MasterPageFile="~/Master_Pages/Admin.master"

<%@ Register Src="~/WebUserControl/WebUserControl.ascx" TagName="Menu"

<%@ Register Assembly="CKEditor.NET" Namespace="CKEditor.NET"

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

<table style="color:Black; border:2px solid black; padding-left:30px; margin-

<%@ Page Title="" Language="C#" MasterPageFile="~/Master_Pages/Admin.master"

<asp:Repeater ID="Rpt" runat="server" onitemcommand="Rpt_ItemCommand">

<td class="Rpt2"><asp:ImageButton ID="ImgDels"

<%@ Page Title="" Language="C#" MasterPageFile="~/Master_Pages/Admin.master"

<%@ Register Src="~/WebUserControl/WebUserControl.ascx" TagName="Menubarr"

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

<%@ Page Title="" Language="C#" MasterPageFile="~/Master_Pages/Admin.master"

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

<asp:Repeater ID="Rpt" runat="server" onitemcommand="Rpt_ItemCommand">