A

PROJECT REPORT

ON

BUS RESERVATION SYSTEM

APEX INSTITUTE OF MANAGEMANT & SCIENCE

.Net Mini Project MCA-452

SUBMITTED TO: SUBMITTED BY:

SIR, KESAV DAS GUPTA RAHUL KUMAR TIWARI
MCA-II YEAR
(SEMESTER-IV)
 A PROJECT REPORT ON

Taste buds-
The food ordering system

Submitted to RTU University for the partial fulfillment of the

Requirement for
MCA 4th Semester

Done by:

Miss Gurpreet Kaur

& Miss Shefali Sharma

Apex Institute of Management & Science

Jaipur.
 CERTIFICATE

This is to certify that Miss Gurpreet Kaur and miss Shefali Sharma, from

MCA 4th Semester have developed Software project titled “Taste Buds -

The Food Ordering System” for as a partial Fulfillment for the award of

the Degree of XXXXXXX.

HEAD OF DEPARTMENT PRINCIPAL

EXTERNAL
 ACKNOWLEDGMENT

My express thanks and gratitude and thanks to Almighty God, my parents and other family
members and friends without whose uncontained support, I could not have made this career in XXXX.

I wish to place on my record my deep sense of gratitude to my project guide, Mr. XXXXX, xxx
Software Solutions, Hyderabad for his constant motivation and valuable help through the project
work. Express my gratitude to Mr. XXXX, Director of XXXXX Institute of Management & Computer
Sciences for his valuable suggestions and advices through out the XXX course. I also extend my
thanks to other Faculties for their Cooperation during my Course.

Finally I would like to thank my friends for their cooperation to complete this project.

XXXXXXX
ABSTRACT
 To develop an efficient intranet food ordering application, which can be
associated to hotel administration software in a typical five star hotel.
1. Title of the project : Taste Buds – The food ordering solution
2. Abstract:
The main objective of this project is to develop a system for a Five Star Hotel in which
its customers can order online for recipes from anywhere. The system will help the users in
displaying the list of recipes items available in that restaurant along with the offers available
for those recipes items. The system will also display the images of the recipes items along
with the list of items. The accessibility to the system in the restaurant will be given to the
Administrator with the user name and password.

Features of the project:

 Provides option to the customers to order food online via internet

 Users can select items from a wide range of menu
 Items will be added to the cart, which can be reviewed and finalized at the time of
submitting order
 Ordered items can also be deleted
 Option given to customer to pay the bill separately for the items which he/she
orders, with this option this application can be easily integrated with any existing
hotel administration software.

3. Modules:
Current application is differentiated into the following modules which are closely
integrated to each other.
 Customers
 Recipes
 Order
 Shopping Cart

4. Requirements:

 Hardware requirements:

Content Description
HDD 20 GB Min
40 GB Recommended
RAM 1 GB Min
2 GB Recommended
 Software requirements:

Content Description
OS Windows XP with SP2 or Windows Vista
Database MS-SQL server 2005
Technologies ASP.NET with C#.NET
IDE Ms-Visual Studio .Net 2008
Browser IE

ORGANIZATION PROFILE
 CONTENTS

1. INTRODUCTION

INTRODUCTION TO PROJECT
PURPOSE OF THE PROJECT
PROBLEM IN EXISTING SYSTEM
SOLUTION OF THESE PROBLEMS

2. SYSTEM ANALYSIS

2.1. SYSTEM WORKFLOW

2.2. STUDY OF THE SYSTEM
2.3. HARDWARE & SOFTWARE REQUIRMENT
2.4. INPUT & OUTPUT
2.5. PROCESS MODELS USED WITH JUSTIFICATION

3. FEASIBILITY REPORT

3.1. TECHNICAL FEASIBILITY

3.2. OPERATIONAL FEASIBILITY
3.3. ECONOMIC FEASIBILITY

4. SOFTWARE REQUIREMENT SPECIFICATIONS

4.1. FUNCIONAL REQUIREMENTS

4.2. PERFORMANCE REQUIREMENTS

5. SELECTED SOFTWARE
5.1. INTRODUCTION TO .NET FRAMEWORK
5.2. ASP.NET
5.3. Java Script
5.4. IIS 6.0
5.5. C#.NET
5.6. SQL SERVER

6. SYSTEM DESIGN

6.1. INTRODUCTION
6.2. NORMALIZATION
6.3. E-R DIAGRAM
6.4. DATA FLOW DIAGRAMS
6.5. DATA DICTIONARY
7. OUTPUT SCREENS

8. SYSTEM TESTING AND IMPLEMENTATION

8.1. INTRODUCTION
8.2. TESTING OBJECTIVES
8.3. UNIT TESTING
8.4. TEST PLAN
8.5. IMPLEMENTATION

9. SYSTEM SECURITY

9.1. INTRODUCTION
9.2. SECURITY IN SOFTWARE

10. CONCLUSION

11. FUTURE IMPROVEMENT

12. BIBLIOGRAPHY
Chapter 1
 1. INTRODUCTION
1.1. INTRODUCTION & OBJECTIVES
The main objective of this project is to develop a system for a Five Star Hotel in which
its customers can order online for recipes from anywhere. The system will help the users in
displaying the list of recipes items available in that restaurant along with the offers available
for those recipes items. The system will also display the images of the recipes items along
with the list of items. The accessibility to the system in the restaurant will be given to the
Administrator with the user name and password.

1.2. PURPOSE OF THE PROJECT

The application should cater the following features:

 Provides option to the customers to order food online via internet

 Users can select items from a wide range of menu

 Items will be added to the cart, which can be reviewed and finalized at the time of
submitting order

 Ordered items can also be deleted

 Option given to customer to pay the bill separately for the items which he/she
orders, with this option this application can be easily integrated with any existing
hotel administration software.
1.3. PROBLEM IN EXISTING SYSTEM
• For ordering food, either user has to go to the restaurant manually or by making a
telephone call
• Hence the existing process is a time consuming process.
• In case if additional ordering has to be done, it’s an additional overhead again.

1.4. SOLUTION OF THESE PROBLEMS

• In order to issues in existing system, the current application is being developed, which
will enhance the activities and performances of the hotel food ordering thus reduces
the time taken to order the food.
• Besides that, information can be store and retrieve easily from computer database if
everything is computerizing by this proposed system.
Chapter 2
 2. SYSTEM ANALYSIS

2.1. SYSTEM WORK FLOW

Change the workflow according to your project
Index.aspx
Home page to login Main console for
,Enter User Id & coordinator
Password Submenu.aspx

Vulnerabilities_view.aspx A_vul_dur_peri (Cancellation)

od_param.aspx search.aspx
Allow to view the
vulnerabilities found To enter the two The search page to
for that site. dates input the search condit
ions for which cancel
ation is to be made

audit_vul_dur_peri
Risk_observation.aspx. od_frm.aspx
aspx View of statistical
data report
Allow to view the risk
and observation for Chart1.aspx
that app. No.

Bar chart for all ten

vulnerabilities for Hosting
safe,unsafe and NA statusnew.aspx

Vulnerabilities_detail The search page to

s.aspx input the search condit
ions for which modify
Allow to view the cation is to be made reauditassigndetail
details level wise. s.aspx
Lists the matching
Websites Modify_request.aspx

Allow to modify
selected website audit
request form details Assignment_page2.asp
x
Allow to mark a site for
random audit
2.2. STUDY OF THE SYSTEM
GUI’S
In the flexibility of the uses the interface has been developed a graphics concept in mind, associated
through a browses interface. The GUI’S at the top level have been categorized as
1. Administrative user interface
2. The operational or generic user interface
The administrative user interface concentrates on the consistent information that is practically, part
of the organizational activities and which needs proper authentication for the data collection. The
interfaces help the administrations with all the transactional states like Data insertion, Data deletion
and Date updation along with the extensive data search capabilities.
The operational or generic user interface helps the users upon the system in transactions through
the existing data and required services. The operational user interface also helps the ordinary users in
managing their own information helps the ordinary users in managing their own information in a
customized manner as per the assisted flexibilities.

NUMBER OF MODULES
• Customers
• Recipes
• Order
• Shopping Cart

Customers:
• This module performs registration and maintenance of customer information.
• This information can be very much useful for delivering the ordered ones avoiding any
confusion related to delivery address

Recipes:
• It contains
• Recipes
• Details about all recipes which are existing in the Taste-Buds
• Adding the new recipes and deleting the Recipes.

Order:
• It contains
• Orders List
 • Payments information
Paying type
Card
Cash
• Using this, adding new order and deleting a order

Shopping Cart:
• It contains
• Recipes types
• list of items and cost
• Adding new items under recipes

2.4. INPUT AND OUTPUT

OUTPUT DESIGN

Outputs from computer systems are required primarily to communicate the results of
processing to users. They are also used to provide 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:
The outputs should be defined in terms of the following points:

 Type of the output

 Content of the output
 Format of the output
 Location of the output
 Frequency of the output
 Volume of the output
 Sequence of the output
 It is not always desirable to print or display data as it is held on a computer. It should be
decided as which form of the output is the most suitable.
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.
 The location of the users
 The software and hardware available.
Keeping in view the above points 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.

Input Design:
Input design is a part of overall system design. The main objective during the input desings is
as given below:
 To produce a cost-effective method of input.
 To achieve the highest possible level of accuracy.
 To ensure that the input is acceptable and understood by the user.

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

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
 Portabilility

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.
2.5. PROCESS MODELS USED WITH JUSTIFICATION
SDLC MODEL:
Waterfall Model
Software products are oriented towards customers like any other engineering products. It is
either driver by market or it drives the market. Customer Satisfaction was the main aim in the 1980's.
Customer Delight is today's logo and Customer Ecstasy is the new buzzword of the new millennium.
Products which are not customer oriented have no place in the market although they are designed
using the best technology. The front end of the product is as crucial as the internal technology of the
product.
A market study is necessary to identify a potential customer's need. This process is also called
as market research. The already existing need and the possible future needs that are combined
together for study. A lot of assumptions are made during market study. Assumptions are the very
important factors in the development or start of a product's development. The assumptions which are
not realistic can cause a nosedive in the entire venture. Although assumptions are conceptual, there
should be a move to develop tangible assumptions to move towards a successful product.
Once the Market study is done, the customer's need is given to the Research and
Development Department to develop a cost-effective system that could potentially solve customer's
needs better than the competitors. Once the system is developed and tested in a hypothetical
environment, the development team takes control of it. The development team adopts one of the
software development models to develop the proposed system and gives it to the customers.
The basic popular models used by many software development firms are as follows:
A) System Development Life Cycle (SDLC) Model
B) Prototyping Model
C) Rapid Application Development Model
D) Component Assembly Model

A) System Development Life Cycle Model (SDLC Model):

This is also called as Classic Life Cycle Model (or) Linear Sequential Model (or) Waterfall
Method. This model has the following activities.

1. System/Information Engineering and Modeling

2. Software Requirements Analysis
3. Systems Analysis and Design
4. Code Generation
5. Testing
6. Maintenance

1) System/Information Engineering and Modeling

As software development is large process so work begins by establishing requirements for all
system elements and then allocating some subset of these requirements to software. The view of this
system is necessary when software must interface with other elements such as hardware, people and
other resources. System is the very essential requirement for the existence of software in any entity. In
some cases for maximum output, the system should be re-engineered and spruced up. Once the ideal
system is designed according to requirement, the development team studies the software requirement
for the system.

2) Software Requirement Analysis

Software Requirement Analysis is also known as feasibility study. In this requirement analysis
phase, the development team visits the customer and studies their system requirement. They examine
the need for possible software automation in the given software system. After feasibility study, the
development team provides a document that holds the different specific recommendations for the
candidate system. It also consists of personnel assignments, costs of the system, project schedule
and target dates.
The requirements analysis and information gathering process is intensified and focused
specially on software. To understand what type of the programs to be built, the system analyst must
study the information domain for the software as well as understand required function, behavior,
performance and interfacing. The main purpose of requirement analysis phase is to find the need and
to define the problem that needs to be solved.

3) System Analysis and Design

In System Analysis and Design phase, the whole software development process, the overall
software structure and its outlay are defined. In case of the client/server processing technology, the
number of tiers required for the package architecture, the database design, the data structure design
etc are all defined in this phase. After designing part a software development model is created.
Analysis and Design are very important in the whole development cycle process. Any fault in the
design phase could be very expensive to solve in the software development process. In this phase,
the logical system of the product is developed.
4) Code Generation
In Code Generation phase, the design must be decoded into a machine-readable form. If the
design of software product is done in a detailed manner, code generation can be achieved without
much complication. For generation of code, Programming tools like Compilers, Interpreters, and
Debuggers are used. For coding purpose different high level programming languages like C, C++,
Pascal and Java are used. The right programming language is chosen according to the type of
application.

5) Testing
After code generation phase the software program testing begins. Different testing methods
are available to detect the bugs that were committed during the previous phases. A number of testing
tools and methods are already available for testing purpose.

6) Maintenance
Software will definitely go through change once when it is delivered to the customer. There are
large numbers of reasons for the change. Change could happen due to some unpredicted input values
into the system. In addition to this the changes in the system directly have an effect on the software
operations. The software should be implemented to accommodate changes that could be happen
during the post development period.
DESIGN PRINCIPLES & METHODOLOGY:
Object Oriented Analysis and Design
When Object orientation is used in analysis as well as design, the boundary between OOA and
OOD is blurred. This is particularly true in methods that combine analysis and design. One reason for
this blurring is the similarity of basic constructs (i.e.,objects and classes) that are used in OOA and
OOD. Through there is no agreement about what parts of the object-oriented development process
belongs to analysis and what parts to design, there is some general agreement about the domains of
the two activities.
The fundamental difference between OOA and OOD is that the former models the problem
domain, leading to an understanding and specification of the problem, while the latter models the
solution to the problem. That is, analysis deals with the problem domain, while design deals with the
solution domain. However, in OOAD subsumed in the solution domain representation. That is, the
solution domain representation, created by OOD, generally contains much of the representation
created by OOA. The separating line is matter of perception, and different people have different views
on it. The lack of clear separation between analysis and design can also be considered one of the
strong points of the object-oriented approach the transition from analysis to design is “seamless”. This
is also the main reason OOAD methods-where analysis and designs are both performed.
The main difference between OOA and OOD, due to the different domains of modeling, is in
the type of objects that come out of the analysis and design process.

Features of OOAD:
 It users Objects as building blocks of the application rather functions
 All objects can be represented graphically including the relation between them.
 All Key Participants in the system will be represented as actors and the actions done by
them will be represented as use cases.
 A typical use case is nothing bug a systematic flow of series of events which can be well
described using sequence diagrams and each event can be described diagrammatically by
Activity as well as state chart diagrams.
 So the entire system can be well described using OOAD model, hence this model is
chosen as SDLC model.

THE GENESIS OF UML:

Software engineering has slowly become part of our everyday life. From washing machines to
compact disc player, through cash machines and phones, most of our daily activities use software,
and as time goes by, the more complex and costly this software becomes.
 The demand for sophisticated software greatly increases the constraints imposed on
development teams. Software engineers are facing a world of growing complexity due to the nature of
applications, the distributed and heterogeneous environments, the size of programs, the organization
of software development teams, and the end-users ergonomic expectations.
To surmount these difficulties, software engineers will have to learn not only how to do their
job, but also how to explain their work to others, and how to understand when others work is explained
to them. For these reasons, they have (and will always have) an increasing need for methods.

From Functional to Object-Oriented Methods

Although object-oriented methods have roots that are strongly anchored back in the 60s,
structured and functional methods were the first to be used. This is not very surprising, since
functional methods are inspired directly my computer architecture (a proven domain well known to
computer scientists). The separation of data and code, just as exists physically in the hardware, was
translated into the methods; this is how computer scientists got into the habit of thinking in terms of
system functions.
This approach is natural when looked at in its historical context, but today, because of its lack
of abstraction, it has become almost completely anachronistic. There is no reason to impose the
underlying hardware on a software solution. Hardware should act as the servant of the software that
is executed on it, rather than imposing architectural constraints.

TOWARDS A UNIFIED MODELLING LANGUAGE

The unification of object-oriented modeling methods became possible as experience allowed
evaluation of the various concepts proposed by existing methods. Based on the fact that differences
between the various methods were becoming smaller, and that the method wars did not move object-
oriented technology forward any longer, Jim Rumbaugh and Grady Booch decided at the end of 1994
to unify their work within a single method: the Unified Method. A year later they were joined by Ivar
Jacobson, the father of use cases, a very efficient technique for the determination of requirements.

Booch, Rumbaugh and Jacobson adopted four goals:

 To represent complete systems (instead of only the software portion) using object oriented
concepts.
 To establish an explicit coupling between concepts and executable code.
 To take into account the scaling factors that are inherent to complex and critical systems.
 To creating a modeling language usable by both humans and machines.
Chapter 3
 3. FEASIBILITY REPORT
3.1 TECHINICAL FEASIBILITY:
Evaluating the technical feasibility is the trickiest part of a feasibility study. This is because, at
this point in time, not too many detailed design of the system, making it difficult to access issues like
performance, costs on (on account of the kind of technology to be deployed) etc.
A number of issues have to be considered while doing a technical analysis.
i) Understand the different technologies involved in the proposed system:
Before commencing the project, we have to be very clear about what are the technologies that
are to be required for the development of the new system.
ii) Find out whether the organization currently possesses the required technologies:
Is the required technology available with the organization?
If so is the capacity sufficient?
For instance –
“Will the current printer be able to handle the new reports and forms required for the new system?”
3.2 OPERATIONAL FEASIBILITY:
Proposed projects are beneficial only if they can be turned into information systems that will
meet the organizations operating requirements. Simply stated, this test of feasibility asks if the system
will work when it is developed and installed. Are there major barriers to Implementation? Here are
questions that will help test the operational feasibility of a project:
 Is there sufficient support for the project from management from users? If the current system is
well liked and used to the extent that persons will not be able to see reasons for change, there
may be resistance.
 Are the current business methods acceptable to the user? If they are not, Users may welcome a
change that will bring about a more operational and useful systems.
 Have the user been involved in the planning and development of the project?
Early involvement reduces the chances of resistance to the system and in General and
increases the likelihood of successful project.
Since the proposed system was to help reduce the hardships encountered
In the existing manual system, the new system was considered to be operational feasible.

3.3 ECONOMIC FEASIBILITY:

Economic feasibility attempts 2 weigh the costs of developing and implementing a new system,
against the benefits that would accrue from having the new system in place. This feasibility study
gives the top management the economic justification for the new system.
 A simple economic analysis which gives the actual comparison of costs and benefits are
much more meaningful in this case. In addition, this proves to be a useful point of reference to
compare actual costs as the project progresses. There could be various types of intangible benefits on
account of automation. These could include increased customer satisfaction, improvement in product
quality better decision making timeliness of information, expediting activities, improved accuracy of
operations, better documentation and record keeping, faster retrieval of information, better employee
morale.
Chapter 4
 4. SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION

Purpose: The main purpose for preparing this document is to give a general insight into the analysis
and requirements of the existing system or situation and for determining the operating characteristics
of the system.

Scope: This Document plays a vital role in the development life cycle (SDLC) and it describes the
complete requirement of the system. It is meant for use by the developers and will be the basic during
testing phase. Any changes made to the requirements in the future will have to go through formal
change approval process.

DEVELOPERS RESPONSIBILITIES OVERVIEW:

The developer is responsible for:

 Developing the system, which meets the SRS and solving all the requirements of the system?
 Demonstrating the system and installing the system at client's location after the acceptance testing
is successful.
 Submitting the required user manual describing the system interfaces to work on it and also the
documents of the system.
 Conducting any user training that might be needed for using the system.
 Maintaining the system for a period of one year after installation.

4.1. FUNCTIONAL REQUIREMENTS:

The proposed system should possess the following features

 Provides option to the customers to order food online via internet

 Users can select items from a wide range of menu

 Items will be added to the cart, which can be reviewed and finalized at the time of
submitting order

 Ordered items can also be deleted

  Option given to customer to pay the bill separately for the items which he/she orders, with
this option this application can be easily integrated with any existing hotel administration
software.

4.2. PERFORMANCE REQUIREMENTS

Performance is measured in terms of the output provided by the application.
Requirement specification plays an important part in the analysis of a system. Only when the
requirement specifications are properly given, it is possible to design a system, which will fit into
required environment. It rests largely in the part of the users of the existing system to give the
requirement specifications because they are the people who finally use the system. This is because
the requirements have to be known during the initial stages so that the system can be designed
according to those requirements. It is very difficult to change the system once it has been designed
and on the other hand designing a system, which does not cater to the requirements of the user, is of
no use.

The requirement specification for any system can be broadly stated as given below:
 The system should be able to interface with the existing system
 The system should be accurate
 The system should be better than the existing system

The existing system is completely dependent on the user to perform all the duties.
Chapter 5
 5. SELECTED SOFTWARE
5.1 INTRODUCTION TO .NET FRAMEWORK
Microsoft .NET Framework was designed with several intentions:
Interoperability - Because interaction between new and older applications is commonly
required, the .NET Framework provides means to access functionality that is implemented in
programs that execute outside the .NET environment. Access to COM components is provided in the
System.Runtime.InteropServices and System.EnterpriseServices namespaces of the framework, and
access to other functionality is provided using the P/Invoke feature.

CLR
The Common Language Runtime (CLR) is the virtual machine component of Microsoft's .NET
initiative. It is Microsoft's implementation of the Common Language Infrastructure (CLI) standard,
which defines an execution environment for program code. The CLR runs a form of bytecode called
the Common Intermediate Language (CIL, previously known as MSIL -- Microsoft Intermediate
Language).

Developers using the CLR write code in a language such as C# or VB.Net. At compile-time, a
.NET compiler converts such code into CIL code. At runtime, the CLR's just-in-time compiler (JIT
compiler) converts the CIL code into code native to the operating system. Alternatively, the CIL code
can be compiled to native code in a separate step prior to runtime. This speeds up all later runs of the
software as the CIL-to-native compilation is no longer necessary.

Although some other implementations of the Common Language Infrastructure run on non-
Windows operating systems, the CLR runs on Microsoft Windows operating systems.
 The virtual machine aspect of the CLR allows programmers to ignore many details of the specific
CPU that will execute the program. The CLR also provides other important services, including the
following:
 Memory management
 Thread management
 Exception handling
 Garbage collection
 Security
CLS
The Common Language Infrastructure (CLI) is an open specification (published under ECMA-
335 and ISO/IEC 23271) developed by Microsoft that describes the executable code and runtime
environment that form the core of a number of runtimes including the Microsoft .NET Framework,
Mono, and Portable.NET. The specification defines an environment that allows multiple high-level
languages to be used on different computer platforms without being rewritten for specific architectures.

The CLI is a specification, not an implementation, and is often confused with the Common
Language Runtime (CLR), which contains aspects outside the scope of the CLI specification.

Among other things CLI specification describes the following four aspects:
The Common Type System (CTS)
A set of types and operations that are shared by all CTS-compliant programming languages.
Metadata
Information about program structure is language-agnostic, so that it can be referenced
between languages and tools, making it easy to work with code written in a language you are not
using.
Common Language Specification (CLS)
A set of base rules to which any language targeting the CLI should conform in order to
interoperate with other CLS-compliant languages.

Virtual Execution System (VES)

The VES loads and executes CLI-compatible programs, using the metadata to combine
separately generated pieces of code at runtime.

All compatible languages compile to Common Intermediate Language (CIL), which is an

intermediate language that is abstracted from the platform hardware. When the code is executed, the
platform-specific VES will compile the CIL to the machine language according to the specific
hardware.

Class library
The Base Class Library, sometimes incorrectly referred to as the Framework Class Library
(FCL) (which is a superset including the Microsoft.* namespaces), is a library of classes available to all
languages using the .NET Framework. The BCL provides classes which encapsulate a number of
common functions such as file reading and writing, graphic rendering, database interaction, XML
document manipulation, and so forth. The BCL is much larger than other libraries, but has much more
functionality in one package.
Security
.NET has its own security mechanism, with two general features: Code Access Security (CAS),
and validation and verification. Code Access Security is based on evidence that is associated with a
specific assembly. Typically the evidence is the source of the assembly (whether it is installed on the
local machine, or has been downloaded from the intranet or Internet). Code Access Security uses
evidence to determine the permissions granted to the code. Other code can demand that calling code
is granted a specified permission. The demand causes the CLR to perform a call stack walk: every
assembly of each method in the call stack is checked for the required permission and if any assembly
is not granted the permission then a security exception is thrown.
When an assembly is loaded the CLR performs various tests. Two such tests are validation
and verification. During validation the CLR checks that the assembly contains valid metadata and CIL,
and it checks that the internal tables are correct. Verification is not so exact. The verification
mechanism checks to see if the code does anything that is 'unsafe'. The algorithm used is quite
conservative and hence sometimes code that is 'safe' is not verified. Unsafe code will only be
executed if the assembly has the 'skip verification' permission, which generally means code that is
installed on the local machine.
.NET Framework uses appdomains as a mechanism for isolating code running in a process.
Appdomains can be created and code loaded into or unloaded from them independent of other
appdomains. This helps increase fault tolerance of the application, as faults or crashes in one
appdomain does not affect rest of the application. Appdomains can also be configured independently
with different security privileges. This can help increasing security of the application by separating
potentially unsafe code. However, the developer has to split the application into sub-domains; it is not
done by the CLR.
Memory management
The .NET Framework CLR frees the developer from the burden of managing memory
(allocating and freeing up when done); instead it does the memory management itself. To this end, the
memory allocated to instantiations of .NET types (objects) is done contiguously from the managed
heap, a pool of memory managed by the CLR. As long as there exists a reference to an object, which
might be either a direct reference to an object or via a graph of objects, the object is considered to be
in use by the CLR. When there is no reference to an object, and thus cannot be reached or used, it
becomes garbage. However, it still holds on to the memory allocated to it. .NET Framework includes a
garbage collector which runs periodically, on a separate thread than the application's thread, that
enumerates all the unusable objects and reclaims the memory allocated to them.
The .NET Garbage Collector (GC) is a non-deterministic, compacting, mark-and-sweep
garbage collector. The GC runs only when a certain amount of memory has been used or there is
enough pressure for memory on the system. Since it is not guaranteed when the conditions to reclaim
memory is reached, the GC runs are non-deterministic. Each .NET application has a set of roots ,
which are a set of pointers maintained by the CLR that point to objects on the managed heap
(managed objects). These include references to static objects and objects defined as local variables or
method parameters currently in scope, as well as objects referred to by CPU registers. When the GC
runs, it pauses the application, and for each objects referred to in the root, it recursively enumerates
all the objects reachable from the root objects and marks the objects as reachable. It uses .NET
metadata and reflection to discover the objects encapsulated by an object, and then recursively walk
them. It then enumerates all the objects on the heap (which were initially allocated contiguously) using
reflection and all the objects, not marked as reachable, are garbage. This is the mark phase. Since the
memory held by garbage is not of any consequence, it is considered free space. However, this leaves
chunks of free space between objects which were initially contiguous. The objects are then compacted
together, by using memcpy to copy them over to the free space to make them contiguous again. Any
reference to an object invalidated by moving the object is updated to reflect the new location by the
GC. The application is resumed after the garbage collection is over.
The GC used by .NET Framework is actually generational. Objects are assigned a generation;
newly created objects belong to Generation 0. The objects that survive a garbage collection are
tagged as Generation 1, and the Generation 1 objects that survive another collection are Generation 2
objects. The .NET Framework uses up to Generation 2 objects. Higher generation objects are garbage
collected less frequently then lower generation objects. This helps increase the efficiency of garbage
collection, as older objects tend to have a larger lifetime than newer objects. Thus, by removing older
(and thus more likely to survive a collection) objects from the scope of a collection run, fewer objects
need to be checked and compacted.

5.2. ASP.NET
Server Application Development
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 IIS and SQL Server can perform standard operations
while your application logic executes through the managed code.

SERVER-SIDE MANAGED CODE

ASP.NET is the hosting environment that enables developers to use the .NET Framework to
target Web-based applications. However, ASP.NET is more than just a runtime host; it is a complete
architecture for developing Web sites and Internet-distributed objects using managed code. Both Web
Forms and XML Web services use IIS and ASP.NET as the publishing mechanism for applications,
and both have a collection of supporting classes in the .NET Framework.
XML Web services, an important evolution in Web-based technology, are distributed, server-
side application components similar to common Web sites. However, unlike Web-based applications,
XML Web services components have no UI and are not targeted for browsers such as Internet
Explorer and Netscape Navigator. Instead, XML Web services consist of reusable software
components designed to be consumed by other applications, such as traditional client applications,
Web-based applications, or even other XML Web services. As a result, XML Web services technology
is rapidly moving application development and deployment into the highly distributed environment of
the Internet.
If you have used earlier versions of ASP technology, you will immediately notice the
improvements that ASP.NET and Web Forms offers. For example, you can develop Web Forms
pages in any language that supports the .NET Framework. In addition, your code no longer needs to
share the same file with your HTTP text (although it can continue to do so if you prefer). Web Forms
pages execute in native machine language because, like any other managed application, they take full
advantage of the runtime. In contrast, unmanaged ASP pages are always scripted and interpreted.
ASP.NET pages are faster, more functional, and easier to develop than unmanaged ASP pages
because they interact with the runtime like any managed application.
The .NET Framework also provides a collection of classes and tools to aid in development and
consumption of XML Web services applications. XML Web services are built on standards such as
SOAP (a remote procedure-call protocol), XML (an extensible data format), and WSDL ( the Web
Services Description Language). The .NET Framework is built on these standards to promote
interoperability with non-Microsoft solutions.
For example, the Web Services Description Language tool included with the .NET Framework
SDK can query an XML Web service published on the Web, parse its WSDL description, and produce
C# or Visual Basic source code that your application can use to become a client of the XML Web
service. The source code can create classes derived from classes in the class library that handle all
the underlying communication using SOAP and XML parsing. Although you can use the class library
to consume XML Web services directly, the Web Services Description Language tool and the other
tools contained in the SDK facilitate your development efforts with the .NET Framework.
If you develop and publish your own XML Web service, the .NET Framework provides a set of
classes that conform to all the underlying communication standards, such as SOAP, WSDL, and XML.
Using those classes enables you to focus on the logic of your service, without concerning yourself with
the communications infrastructure required by distributed software development.
Finally, like Web Forms pages in the managed environment, your XML Web service will run with the
speed of native machine language using the scalable communication of IIS.

ACTIVE SERVER PAGES.NET

ASP.NET is a programming framework built on the common language runtime that can be
used on a server to build powerful Web applications. ASP.NET offers several important advantages
over previous Web development models:
 Enhanced Performance. ASP.NET is compiled common language runtime code running on the
server. Unlike its interpreted predecessors, ASP.NET can take advantage of early binding, just-in-
 time compilation, native optimization, and caching services right out of the box. This amounts to
dramatically better performance before you ever write a line of code.
 World-Class Tool Support. The ASP.NET framework is complemented by a rich toolbox and
designer in the Visual Studio integrated development environment. WYSIWYG editing, drag-and-
drop server controls, and automatic deployment are just a few of the features this powerful tool
provides.
 Power and Flexibility. Because ASP.NET is based on the common language runtime, the power
and flexibility of that entire platform is available to Web application developers. The .NET
Framework class library, Messaging, and Data Access solutions are all seamlessly accessible
from the Web. ASP.NET is also language-independent, so you can choose the language that best
applies to your application or partition your application across many languages. Further, common
language runtime interoperability guarantees that your existing investment in COM-based
development is preserved when migrating to ASP.NET.
 Simplicity. ASP.NET makes it easy to perform common tasks, from simple form submission and
client authentication to deployment and site configuration. For example, the ASP.NET page
framework allows you to build user interfaces that cleanly separate application logic from
presentation code and to handle events in a simple, Visual Basic - like forms processing model.
Additionally, the common language runtime simplifies development, with managed code services
such as automatic reference counting and garbage collection.
 Manageability. ASP.NET employs a text-based, hierarchical configuration system, which
simplifies applying settings to your server environment and Web applications. Because
configuration information is stored as plain text, new settings may be applied without the aid of
local administration tools. This "zero local administration" philosophy extends to deploying
ASP.NET Framework applications as well. An ASP.NET Framework application is deployed to a
server simply by copying the necessary files to the server. No server restart is required, even to
deploy or replace running compiled code.
 Scalability and Availability. ASP.NET has been designed with scalability in mind, with features
specifically tailored to improve performance in clustered and multiprocessor environments. Further,
processes are closely monitored and managed by the ASP.NET runtime, so that if one
misbehaves (leaks, deadlocks), a new process can be created in its place, which helps keep your
application constantly available to handle requests.
 Customizability and Extensibility. ASP.NET delivers a well-factored architecture that allows
developers to "plug-in" their code at the appropriate level. In fact, it is possible to extend or replace
any subcomponent of the ASP.NET runtime with your own custom-written component.
Implementing custom authentication or state services has never been easier.
 Security. With built in Windows authentication and per-application configuration, you can be
assured that your applications are secure.

LANGUAGE SUPPORT
The Microsoft .NET Platform currently offers built-in support for three languages: C#, Visual
Basic, and JScript.

WHAT IS ASP.NET WEB FORMS?

The ASP.NET Web Forms page framework is a scalable common language runtime
programming model that can be used on the server to dynamically generate Web pages.
Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with existing
pages), the ASP.NET Web Forms framework has been specifically designed to address a number of
key deficiencies in the previous model. In particular, it provides:
 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 postback 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. These code
blocks execute in a top-down manner at page render time.
CODE-BEHIND WEB FORMS
ASP.NET supports two methods of authoring dynamic pages. The first is the method shown in
the preceding samples, where the page code is physically declared within the originating .aspx file. An
alternative approach--known as the code-behind method--enables the page code to be more cleanly
separated from the HTML content into an entirely separate file.

INTRODUCTION TO ASP.NET SERVER CONTROLS

In addition to (or instead of) using <% %> code blocks to program dynamic content, ASP.NET
page developers can use ASP.NET server controls to program Web pages. Server controls are
declared within an .aspx file using custom tags or intrinsic HTML tags that contain a runat="server"
attributes value. Intrinsic HTML tags are handled by one of the controls in the
System.Web.UI.HtmlControls namespace. Any tag that doesn't explicitly map to one of the controls
is assigned the type of System.Web.UI.HtmlControls.HtmlGenericControl.
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.
In addition to supporting standard HTML input controls, ASP.NET enables developers to utilize
richer custom controls on their pages. For example, the following sample demonstrates how the
<asp:adrotator> control can be used to dynamically display rotating ads on a page.
1. ASP.NET Web Forms provide an easy and powerful way to build dynamic Web UI.
2. ASP.NET Web Forms pages can target any browser client (there are no script library or cookie
requirements).
3. ASP.NET Web Forms pages provide syntax compatibility with existing ASP pages.
4. ASP.NET server controls provide an easy way to encapsulate common functionality.
5. ASP.NET ships with 45 built-in server controls. Developers can also use controls built by third
parties.
6. ASP.NET server controls can automatically project both uplevel and downlevel HTML.
7. ASP.NET templates provide an easy way to customize the look and feel of list server controls.
8. ASP.NET validation controls provide an easy way to do declarative client or server data validation.
5.3. JAVA SCRIPT
JavaScript is a script-based programming language that was developed by Netscape
Communication Corporation. JavaScript was originally called Live Script and renamed as JavaScript
to indicate its relationship with Java. JavaScript supports the development of both client and server
components of Web-based applications. On the client side, it can be used to write programs that are
executed by a Web browser within the context of a Web page. On the server side, it can be used to
write Web server programs that can process information submitted by a Web browser and then update
the browser’s display accordingly
Even though JavaScript supports both client and server Web programming, we prefer JavaScript at
Client side programming since most of the browsers supports it. JavaScript is almost as easy to learn
as HTML, and JavaScript statements can be included in HTML documents by enclosing the
statements between a pair of scripting tags
<SCRIPTS>... </SCRIPT>.
<SCRIPT LANGUAGE = “JavaScript”>
JavaScript statements
</SCRIPT>
Here are a few things we can do with JavaScript:
 Validate the contents of a form and make calculations.
 Add scrolling or changing messages to the Browser’s status line.
 Animate images or rotate images that change when we move the mouse over them.
 Detect the browser in use and display different content for different browsers.
 Detect installed plug-ins and notify the user if a plug-in is required.
We can do much more with JavaScript, including creating entire application.
JavaScript Vs Java
JavaScript and Java are entirely different languages. A few of the most glaring differences are:
 Java applets are generally displayed in a box within the web document; JavaScript can affect
any part of the Web document itself.
 While JavaScript is best suited to simple applications and adding interactive features to Web
pages; Java can be used for incredibly complex applications.
There are many other differences but the important thing to remember is that JavaScript and
Java are separate languages. They are both useful for different things; in fact they can be used
together to combine their advantages.
Advantages:
 JavaScript can be used for Sever-side and Client-side scripting.
 It is more flexible than VBScript.
JavaScript is the default scripting languages at Client-side since all the browsers supports it.

5.4. IIS 6.0

The IIS 6 process model is the default model on machines running Windows 2003 Server
operating system. It introduces several changes and improvements over the IIS 5 process model. One
of the biggest changes is the concept of application pools. On IIS 5.X all web applications, that is, all
AppDomains, were hosted by the ASP.NET worker process. To achieve a finer granularity over
security boundaries and personalization, the IIS 6 process model allows applications to run inside
different copies of a new worker process, w3wp.exe. Each application pool can contain multiple
AppDomains and is hosted in a single copy of the worker process. In other words, the shift is from a
single process hosting all applications to multiple processes hosting each an application pool. This
model is also called the worker process isolation mode.
Another big change from the previous model is the way IIS listens for incoming requests. With
the IIS 5 model, it was the IIS process, inetinfo.exe, who was listening on a specific TCP port for HTTP
requests. In the IIS 6 architecture, incoming requests are handled and queued at kernel level instead
of user mode via a kernel driver called http.sys; this approach has several advantages over the old
model and is called kernel-level request queuing.
The IIS 6.0 process model
 The above figure illustrates the principal components taking part in the request processing
when using the II 6 model. Once a request arrives the kernel level device driver http.sys routes it to
the right application pool queue. Each queue belongs to a specific application pool, and thus to a
specific copy of the worker process, which next receives the request from the queue. This approach
highly reduces the overhead introduced by named pipes used in IIS 5 model since no inter process
communication is taking place, but the requests are headed to the worker process directly from the
kernel level driver. This has many advantages concerning reliability, too. Since running in kernel
mode, the request dispatching isn’t influenced by crashes and malfunctions happing at user level, that
is, in the worker processes. Thereby, even if a worker process crashes, the system is still capable of
accepting incoming requests and eventually restarts the crashed process.
It’s the worker process who is in charge of loading the ASP.NET ISAPI extension, which, in
turn, loads the CRL and delegates all the work to the HTTP Runtime.
The w3wp.exe worker process, differently from the aspnet_wp.exe process used in IIS 5
model, isn’t ASP.NET specific, and is used to handle any kind of requests. The specific worker
process then decides which ISAPI modules to load according to the type of resources it needs to
serve.
A detail not underlined in Figure 3 for simplicity reasons is that incoming requests are
forwarded from the application pool queue to the right worker process via a module loaded in IIS 6
called Web Administration Service (WAS). This module is responsible for reading worker process –
web application bindings from the IIS metabase and forwarding the request to the right worker
process.

IIS Request Processing

This topic describes how a client request is processed on an IIS server.

Request Processing by Type of Request

The following table describes what happens once an IIS process receives a request to be executed.
Request Action
HTML Page IIS returns the page in HTML format.
A file whose extension IIS loads the appropriate DLL file and presents the request through the
is mapped to a Extension_Control_Block data structure. For example, the .asp
particular ISAPI extension is mapped to Asp.dll, so that all requests for files with an .asp
extension, such as extension will be directed to Asp.dll. The .stm and .shtm extensions are
Asp.dll mapped to the Ssinc.dll.
 IIS loads the ISAPI DLL (if it is not already running) and the request is
ISAPI extension sent to the extension through the EXTENSION_CONTROL_BLOCK
structure data structure.
IIS creates a new process. IIS will then provide the query string and
CGI application other parameters that are included with the request through the
environment and standard input (STDIN) handle for the process.
ISAPI filters are always loaded as long as the Web service is running and a request to the
server has been made. Preliminary Request Processing on IIS 6.0 in Worker Process Isolation Mode

Before an IIS process receives a request to execute, some preliminary processing occurs that
is described in the following steps:
1. A request arrives at HTTP.sys.
2. HTTP.sys determines if the request is valid. If the request is not valid, it sends a code for an
invalid request back to the client.
3. If the request is valid, HTTP.sys checks to see if the request is for static content (HTML)
because static content can be served immediately.
4. If the request is for dynamic content, HTTP.sys checks to see if the response is located in its
kernel-mode cache.
5. If the response is in the cache, HTTP.sys returns the response immediately.
6. If the response is not cached, HTTP.sys determines the correct request queue, and places the
request in that queue.
7. If the queue has no worker processes assigned to it, HTTP.sys signals the WWW service to
start one.
8. The worker process pulls the request from the queue and processes the request, evaluating
the URL to determine the type of request (ASP, ISAPI, or CGI).
9. The worker process sends the response back to HTTP.sys.
10. HTTP.sys sends the response back to the client and logs the request, if configured to
do so.
 The following future illustrates the request response process in pointing interaction between the
kernel and user.

Preliminary Request Processing on IIS 6.0 in IIS 5.0 Isolation Mode and Earlier Versions of IIS The
request processing of IIS 6.0 running in IIS 5.0 isolation mode is nearly identical to the request
processing in IIS 5.1, IIS 5.0, and IIS 4.0. Before an IIS process receives a request to execute, some
preliminary processing occurs that is described in the following steps:
1. A request arrives. If the requested application is running in-process, then Inetinfo.exe takes the
request. If not, then DLLHost.exe takes the request.
2. Inetinfo.exe or DLLHost.exe determines if the request is valid. If the request is not valid, it sends
a code for an invalid request back to the client.
3. If the request is valid, Inetinfo.exe or DLLHost.exe checks to see if the response is located in the
IIS cache.
4. If the response is in the cache, it is returned immediately.
5. If the response is not cached, Inetinfo.exe or DLLHost.exe processes the request, evaluating
the URL to determine if the request is for static content (HTML), or dynamic content (ASP,
ASP.NET or ISAPI).
The response is sent back to the client and the request is logged, if IIS is configured to do so.
 5.5. C#.Net:
C# is an object-oriented programming language developed by Microsoft as part of the .NET
initiative and later approved as a standard by ECMA and ISO. Anders Hejlsberg leads development of
the C# language, which has a procedural, object-oriented syntax based on C++ and includes aspects of
several other programming languages (most notably Delphi and Java) with a particular emphasis on
simplification.

Design goals

The ECMA standard lists these design goals for C#:

 C# is intended to be a simple, modern, general-purpose, object-oriented programming
language.
 Because software robustness, durability and programmer productivity are important, the
language should include strong type checking, array bounds checking, detection of attempts to
use uninitialized variables, source code portability, and automatic garbage collection.
 The language is intended for use in developing software components that can take advantage
of distributed environments.
 Programmer portability is very important, especially for those programmers already familiar with
C and C++.
 Support for internationalization is very important.
 C# is intended to be suitable for writing applications for both hosted and embedded systems,
ranging from the very large that use sophisticated operating systems, down to the very small
having dedicated functions.
 Although C# applications are intended to be economical with regards to memory and processing
power requirements, the language was not intended to compete directly on performance and
size with C or assembly language.

Features
The following description is based on the language standard and other documents listed in the
External links section.

By design, C# is the programming language that most directly reflects the underlying Common
Language Infrastructure (CLI). Most of C#'s intrinsic types correspond to value-types implemented by
the CLI framework. However, the C# language specification does not state the code generation
requirements of the compiler: that is, it does not state that a C# compiler must target a Common
Language Runtime (CLR), or generate Common Intermediate Language (CIL), or generate any other
specific format. Theoretically, a C# compiler could generate machine code like traditional compilers of
C++ or FORTRAN; in practice, all existing C# implementations target CLI.

C# differs from C and C++ in many ways, including:

 There are no global variables or functions. All methods and members must be declared within
classes.
 Local variables cannot shadow variables of the enclosing block, unlike C and C++. Variable
shadowing is often considered confusing by C++ texts.
 C# supports a strict boolean type, bool. Statements that take conditions, such as while and if,
require an expression of a boolean type. While C++ also has a boolean type, it can be freely
converted to and from integers, and expressions such as if(a) require only that a is convertible
to bool, allowing a to be an int, or a pointer. C# disallows this "integer meaning true or false"
approach on the grounds that forcing programmers to use expressions that return exactly bool
can prevent certain types of programming mistakes such as if (a = b) (use of = instead of ==).
 In C#, memory address pointers can only be used within blocks specifically marked as unsafe,
and programs with unsafe code need appropriate permissions to run. Most object access is
done through safe references, which cannot be made invalid. An unsafe pointer can point to an
instance of a value-type, array, string, or a block of memory allocated on a stack. Code that is
not marked as unsafe can still store and manipulate pointers through the System.IntPtr type, but
cannot dereference them.
 Managed memory cannot be explicitly freed, but is automatically garbage collected. Garbage
collection addresses memory leaks. C# also provides direct support for deterministic finalization
with the using statement (supporting the Resource Acquisition Is Initialization idiom).
 Multiple inheritance is not supported, although a class can implement any number of interfaces.
This was a design decision by the language's lead architect to avoid complication, avoid
dependency hell and simplify architectural requirements throughout CLI.
 C# is more typesafe than C++. The only implicit conversions by default are those which are
considered safe, such as widening of integers and conversion from a derived type to a base
type. This is enforced at compile-time, during JIT, and, in some cases, at runtime. There are no
implicit conversions between booleans and integers and between enumeration members and
integers (except 0, which can be implicitly converted to an enumerated type), and any user-
defined conversion must be explicitly marked as explicit or implicit, unlike C++ copy constructors
 (which are implicit by default) and conversion operators (which are always implicit).
 Enumeration members are placed in their own namespace.
 Accessors called properties can be used to modify an object with syntax that resembles C++
member field access. In C++, declaring a member public enables both reading and writing to
that member, and accessor methods must be used if more fine-grained control is needed. In C#,
properties allow control over member access and data validation.
 Full type reflection and discovery is available.

Unified type system

C# has a unified type system. This means that all types, including primitives such as integers,
are subclasses of the System.Object class. For example, every type inherits a ToString() method. For
performance reasons, primitive types (and value types in general) are internally allocated on the stack.
Boxing and unboxing allow one to translate primitive data to and from their object form. Effectively, this
makes the primitive types a subtype of the Object type. Primitive types can also define methods (e.g.,
42.ToString() calls the ToString() method on an integer), and in the programmer's perspective behave
like any other object.

C# allows the programmer to create user-defined value types, using the struct keyword. From
the programmer's perspective, they can be seen as lightweight classes. Unlike regular classes, and like
the standard primitives, such value types are allocated on the stack rather than on the heap. They can
also be part of an object (either as a field or boxed), or stored in an array, without the memory
indirection that normally exists for class types. Structs also come with a number of limitations. Because
structs have no notion of a null value and can be used in arrays without initialization, they are implicitly
initialized to default values (normally by filling the struct memory space with zeroes, but the
programmer can specify explicit default values to override this). The programmer can define additional
constructors with one or more arguments. This also means that structs lack a virtual method table, and
because of that (and the fixed memory footprint), they cannot allow inheritance (but can implement
interfaces).

Preprocessor
C# features "preprocessor directives"[8] (though it does not have an actual preprocessor) based
on the C preprocessor that allows programmers to define symbols but not macros. Conditionals such
as #if, #endif, and #else are also provided. Directives such as #region give hints to editors for code
folding.

XML documentation system

C#'s documentation system is similar to Java's Javadoc, but based on XML. Two methods of
documentation are currently supported by the C# compiler.

Single-line comments, such as those commonly found in Visual Studio generated code, are
indicated on a line beginning with ///.

Syntax for documentation comments and their XML markup is defined in a non-normative annex
of the ECMA C# standard. The same standard also defines rules for processing of such comments, and
their transformation to a plain XML document with precise rules for mapping of CLI identifiers to their
related documentation elements. This allows any C# IDE or other development tool to find
documentation for any symbol in the code in a certain well-defined way.

Code libraries
The C# specification details a minimum set of types and class libraries that the compiler expects to
have available and they define the basics required. In practice, C# is most often used with some
implementation of the Common Language Infrastructure (CLI), which is standardized as ECMA-335
Common Language Infrastructure (CLI).
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, DataReader, and

DataAdapter.

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 recordset 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 DataAdapter 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 DataAdapter, 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 (System.Data.OleDb and
System.Data.SqlClient) that are part of the .Net Framework provide four basic objects: the Command,
Connection, DataReader and DataAdapter. 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 resultsets 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.

DataReaders:
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 AND DATAADAPTERS:

DataSets
The DataSet object is similar to the ADO Recordset 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 GetChanges method of the DataSet object actually creates a second
DatSet that contains only the changes to the data. This DataSet is then used by a DataAdapter (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 WebServices. In
fact, a DataSet with a schema can actually be compiled for type safety and statement completion.

DATAADAPTERS (OLEDB/SQL)

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.
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 CommandBuilder object can generate
these at run-time based upon a select statement. However, this run-time 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
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,
DataReader, and DataAdapter.

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 recordset 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 DataAdapter 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 DataAdapter, 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 (System.Data.OleDb and System.Data.SqlClient) that are part of the .Net
Framework provide four basic objects: the Command, Connection, DataReader and
DataAdapter. 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 resultsets 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.

DataReaders:
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 AND DATAADAPTERS:

DataSets
The DataSet object is similar to the ADO Recordset 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 GetChanges method of the DataSet object actually creates a second
DatSet that contains only the changes to the data. This DataSet is then used by a
DataAdapter (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
WebServices. In fact, a DataSet with a schema can actually be compiled for type safety and
statement completion.
DATAADAPTERS (OLEDB/SQL)

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.
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 CommandBuilder object can generate these at run-time based upon a select
statement. However, this run-time 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.
7. ADO.NET is the next evolution of ADO for the .Net Framework.
8. 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.
9. ADO.NET can be used to get data from a stream, or to store data in a cache for updates.
10. There is a lot more information about ADO.NET in the documentation.
11. 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.
12. Also, you can use a DataSet to bind to the data, move through the data, and navigate data
relationships

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, DataReader, and

DataAdapter.

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 recordset 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 DataAdapter 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 DataAdapter, 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 (System.Data.OleDb and
System.Data.SqlClient) that are part of the .Net Framework provide four basic objects: the Command,
Connection, DataReader and DataAdapter. 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 resultsets 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.

DataReaders:
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 AND DATAADAPTERS:

DataSets
The DataSet object is similar to the ADO Recordset 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 GetChanges method of the DataSet object actually creates a second
DatSet that contains only the changes to the data. This DataSet is then used by a DataAdapter (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 WebServices. In
fact, a DataSet with a schema can actually be compiled for type safety and statement completion.

DATAADAPTERS (OLEDB/SQL)

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.
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 CommandBuilder object can generate
these at run-time based upon a select statement. However, this run-time 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.
13. ADO.NET is the next evolution of ADO for the .Net Framework.
14. 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.
15. ADO.NET can be used to get data from a stream, or to store data in a cache for updates.
16. There is a lot more information about ADO.NET in the documentation.
17. 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.
18. Also, you can use a DataSet to bind to the data, move through the data, and navigate data
relationships

5.6. SQL SERVER 2005

A database management, or DBMS, gives the user access to their data and helps them
transform the data into information. Such database management systems include dBase, paradox,
IMS, SQL Server and SQL Server. These systems allow users to create, update and extract
information from their database.
A database is a structured collection of data. Data refers to the characteristics of people, things
and events. SQL Server stores each data item in its own fields. In SQL Server, the fields relating to a
particular person, thing or event are bundled together to form a single complete unit of data, called a
record (it can also be referred to as raw or an occurrence). Each record is made up of a number of
fields. No two fields in a record can have the same field name.
During an SQL Server Database design project, the analysis of your business needs identifies
all the fields or attributes of interest. If your business needs change over time, you define any
additional fields or change the definition of existing fields.

SQL SERVER TABLES

SQL Server stores records relating to each other in a table. Different tables are created for the
various groups of information. Related tables are grouped together to form a database.

PRIMARY KEY
Every table in SQL Server has a field or a combination of fields that uniquely identifies each
record in the table. The Unique identifier is called the Primary Key, or simply the Key. The primary key
provides the means to distinguish one record from all other in a table. It allows the user and the
database system to identify, locate and refer to one particular record in the database.

RELATIONAL DATABASE
Sometimes all the information of interest to a business operation can be stored in one table.
SQL Server makes it very easy to link the data in multiple tables. Matching an employee to the
department in which they work is one example. This is what makes SQL Server a relational database
management system, or RDBMS. It stores data in two or more tables and enables you to define
relationships between the table and enables you to define relationships between the tables.

FOREIGN KEY
When a field is one table matches the primary key of another field is referred to as a foreign key.
A foreign key is a field or a group of fields in one table whose values match those of the primary key of
another table.

REFERENTIAL INTEGRITY
Not only does SQL Server allow you to link multiple tables, it also maintains consistency
between them. Ensuring that the data among related tables is correctly matched is referred to as
maintaining referential integrity.

DATA ABSTRACTION
A major purpose of a database system is to provide users with an abstract view of the data.
This system hides certain details of how the data is stored and maintained. Data abstraction is divided
into three levels.

Physical level: This is the lowest level of abstraction at which one describes how the data are actually
stored.

Conceptual Level: At this level of database abstraction all the attributed and what data are actually
stored is described and entries and relationship among them.

View level: This is the highest level of abstraction at which one describes only part of the database.

ADVANTAGES OF RDBMS

 Redundancy can be avoided

 Inconsistency can be eliminated
 Data can be Shared
 Standards can be enforced
 Security restrictions ca be applied
 Integrity can be maintained
 Conflicting requirements can be balanced
 Data independence can be achieved.
DISADVANTAGES OF DBMS
A significant disadvantage of the DBMS system is cost. In addition to the cost of purchasing of
developing the software, the hardware has to be upgraded to allow for the extensive programs and the
workspace required for their execution and storage. While centralization reduces duplication, the lack
of duplication requires that the database be adequately backed up so that in case of failure the data
can be recovered.

FEATURES OF SQL SERVER (RDBMS)

SQL SERVER is one of the leading database management systems (DBMS) because it is the
only Database that meets the uncompromising requirements of today’s most demanding information
systems. From complex decision support systems (DSS) to the most rigorous online transaction
processing (OLTP) application, even application that require simultaneous DSS and OLTP access to
the same critical data, SQL Server leads the industry in both performance and capability

SQL SERVER is a truly portable, distributed, and open DBMS that delivers unmatched performance,
continuous operation and support for every database.
SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially designed for online
transactions processing and for handling large database application.

SQL SERVER with transactions processing option offers two features which contribute to very high
level of transaction processing throughput, which are

 The row level lock manager

ENTERPRISE WIDE DATA SHARING

The unrivaled portability and connectivity of the SQL SERVER DBMS enables all the systems in
the organization to be linked into a singular, integrated computing resource.

PORTABILITY
SQL SERVER is fully portable to more than 80 distinct hardware and operating systems
platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary platforms. This
portability gives complete freedom to choose the database sever platform that meets the system
requirements.

OPEN SYSTEMS
SQL SERVER offers a leading implementation of industry –standard SQL. SQL Server’s open
architecture integrates SQL SERVER and non –SQL SERVER DBMS with industries most
comprehensive collection of tools, application, and third party software products SQL Server’s Open
architecture provides transparent access to data from other relational database and even non-relational
database.

DISTRIBUTED DATA SHARING

SQL Server’s networking and distributed database capabilities to access data stored on remote
server with the same ease as if the information was stored on a single local computer. A single SQL
statement can access data at multiple sites. You can store data where system requirements such as
performance, security or availability dictate.

UNMATCHED PERFORMANCE
The most advanced architecture in the industry allows the SQL SERVER DBMS to deliver
unmatched performance.

SOPHISTICATED CONCURRENCY CONTROL

Real World applications demand access to critical data. With most database Systems
application becomes “contention bound” – which performance is limited not by the CPU power or by
disk I/O, but user waiting on one another for data access . SQL Server employs full, unrestricted row-
level locking and contention free queries to minimize and in many cases entirely eliminates contention
wait times.

NO I/O BOTTLENECKS
SQL Server’s fast commit groups commit and deferred write technologies dramatically reduce
disk I/O bottlenecks. While some database write whole data block to disk at commit time, SQL Server
commits transactions with at most sequential log file on disk at commit time, On high throughput
systems, one sequential writes typically group commit multiple transactions. Data read by the
transaction remains as shared memory so that other transactions may access that data without reading
it again from disk. Since fast commits write all data necessary to the recovery to the log file, modified
blocks are written back to the database independently of the transaction commit, when written from
memory to disk.
Chapter 6
 6. SYSTEM DESIGN
6.1. INTRODUCTION
Software design sits at the technical kernel of the software engineering process and is applied
regardless of the development paradigm and area of application. Design is the first step in the
development phase for any engineered product or system. The designer’s goal is to produce a model
or representation of an entity that will later be built. Beginning, once system requirement have been
specified and analyzed, system design is the first of the three technical activities -design, code and test
that is required to build and verify software.

The importance can be stated with a single word “Quality”. Design is the place where quality is
fostered in software development. Design provides us with representations of software that can assess
for quality. Design is the only way that we can accurately translate a customer’s view into a finished
software product or system. Software design serves as a foundation for all the software engineering
steps that follow. Without a strong design we risk building an unstable system – one that will be difficult
to test, one whose quality cannot be assessed until the last stage.

During design, progressive refinement of data structure, program structure, and procedural
details are developed reviewed and documented. System design can be viewed from either technical or
project management perspective. From the technical point of view, design is comprised of four activities
– architectural design, data structure design, interface design and procedural design.

6.2. NORMALIZATION
It is a process of converting a relation to a standard form. The process is used to handle the
problems that can arise due to data redundancy i.e. repetition of data in the database, maintain data
integrity as well as handling problems that can arise due to insertion, updation, deletion anomalies.
Decomposing is the process of splitting relations into multiple relations to eliminate anomalies
and maintain anomalies and maintain data integrity. To do this we use normal forms or rules for
structuring relation.

Insertion anomaly: Inability to add data to the database due to absence of other data.

Deletion anomaly: Unintended loss of data due to deletion of other data.

Update anomaly: Data inconsistency resulting from data redundancy and partial update

Normal Forms: These are the rules for structuring relations that eliminate anomalies.

FIRST NORMAL FORM:

A relation is said to be in first normal form if the values in the relation are atomic for every
attribute in the relation. By this we mean simply that no attribute value can be a set of values or, as it is
sometimes expressed, a repeating group.
SECOND NORMAL FORM:

A relation is said to be in second Normal form is it is in first normal form and it should satisfy any
one of the following rules.
1) Primary key is a not a composite primary key
2) No non key attributes are present
3) Every non key attribute is fully functionally dependent on full set of primary key.

THIRD NORMAL FORM:

A relation is said to be in third normal form if their exits no transitive dependencies.

Transitive Dependency: If two non key attributes depend on each other as well as on the primary key
then they are said to be transitively dependent.
The above normalization principles were applied to decompose the data in multiple tables
thereby making the data to be maintained in a consistent state.

6.3. E – R DIAGRAMS
 The relation upon the system is structure through a conceptual ER-Diagram, which not only
specifics the existential entities but also the standard relations through which the system exists and
the cardinalities that are necessary for the system state to continue.
 The entity Relationship Diagram (ERD) depicts the relationship between the data objects. The ERD
is the notation that is used to conduct the date modeling activity the attributes of each data object
noted is the ERD can be described resign a data object descriptions.
 The set of primary components that are identified by the ERD are
 Data object  Relationships
 Attributes  Various types of indicators.
The primary purpose of the ERD is to represent data objects and their relationships.
(PASTE YOUR E – R DIAGRAM)
6.4. DATA FLOW DIAGRAMS

A data flow diagram is graphical tool used to describe and analyze movement of data through a
system. These are the central tool and the basis from which the other components are developed. The
transformation of data from input to output, through processed, may be described logically and
independently of physical components associated with the system. These are known as the logical
data flow diagrams. The physical data flow diagrams show the actual implements and movement of
data between people, departments and workstations. A full description of a system actually consists of
a set of data flow diagrams. Using two familiar notations Yourdon, Gane and Sarson notation develops
the data flow diagrams. Each component in a DFD is labeled with a descriptive name. Process is
further identified with a number that will be used for identification purpose. The development of DFD’S
is done in several levels. Each process in lower level diagrams can be broken down into a more
detailed DFD in the next level. The lop-level diagram is often called context diagram. It consists a
single process bit, which plays vital role in studying the current system. The process in the context
level diagram is exploded into other process at the first level DFD.
The idea behind the explosion of a process into more process is that understanding at one level
of detail is exploded into greater detail at the next level. This is done until further explosion is
necessary and an adequate amount of detail is described for analyst to understand the process.
Larry Constantine first developed the DFD as a way of expressing system requirements in a
graphical from, this lead to the modular design.
A DFD is also known as a “bubble Chart” 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 to the lowest level of detail. A DFD consists of a series of bubbles joined by data flows in
the system.

DFD SYMBOLS:
In the DFD, there are four symbols
1. A square defines a source(originator) or destination of system data
2. An arrow identifies data flow. It is the pipeline through which the information flows
3. A circle or a bubble represents a process that transforms incoming data flow into outgoing data
flows.
4. An open rectangle is a data store, data at rest or a temporary repository of data
 Process that transforms data flow.

Source or Destination of data

Data flow

Data Store

CONSTRUCTING A DFD:
Several rules of thumb are used in drawing DFD’S:

1. Process should be named and numbered for an easy reference. Each name should be
representative of the process.
2. The direction of flow is from top to bottom and from left to right. Data traditionally flow from source
to the destination although they may flow back to the source. One way to indicate this is to draw
long flow line back to a source. An alternative way is to repeat the source symbol as a destination.
Since it is used more than once in the DFD it is marked with a short diagonal.
3. When a process is exploded into lower level details, they are numbered.
4. The names of data stores and destinations are written in capital letters. Process and dataflow
names have the first letter of each work capitalized

A DFD typically shows the minimum contents of data store. Each data store should contain all
the data elements that flow in and out.
Questionnaires should contain all the data elements that flow in and out. Missing interfaces
redundancies and like is then accounted for often through interviews.
SAILENT FEATURES OF DFD’S
1. The DFD shows flow of data, not of control loops and decision are controlled considerations do not
appear on a DFD.
2. The DFD does not indicate the time factor involved in any process whether the dataflow take place
daily, weekly, monthly or yearly.
3. The sequence of events is not brought out on the DFD.
TYPES OF DATA FLOW DIAGRAMS
1. Current Physical
2. Current Logical
3. New Logical
4. New Physical
CURRENT PHYSICAL:
In Current Physical DFD proecess label include the name of people or their positions or the
names of computer systems that might provide some of the overall system-processing label includes an
identification of the technology used to process the data. Similarly data flows and data stores are often
labels with the names of the actual physical media on which data are stored such as file folders,
computer files, business forms or computer tapes.

CURRENT LOGICAL:
The physical aspects at the system are removed as mush as possible so that the current
system is reduced to its essence to the data and the processors that transform them regardless of
actual physical form.

NEW LOGICAL:
This is exactly like a current logical model if the user were completely happy with he user were
completely happy with the functionality of the current system but had problems with how it was
implemented typically through the new logical model will differ from current logical model while having
additional functions, absolute function removal and inefficient flows recognized.

NEW PHYSICAL:
The new physical represents only the physical implementation of the new system.
RULES GOVERNING THE DFD’S
PROCESS
1) No process can have only outputs.
2) No process can have only inputs. If an object has only inputs than it must be a sink.
3) A process has a verb phrase label.
DATA STORE
1) Data cannot move directly from one data store to another data store, a process must move data.
2) Data cannot move directly from an outside source to a data store, a process, which receives, must
move data from the source and place the data into data store
3) A data store has a noun phrase label.

SOURCE OR SINK
The origin and / or destination of data.

1) Data cannot move direly from a source to sink it must be moved by a process
2) A source and /or sink has a noun phrase land
DATA FLOW
1) A Data Flow has only one direction of flow between symbols. It may flow in both directions between
a process and a data store to show a read before an update. The later is usually indicated however
by two separate arrows since these happen at different type.
2) A join in DFD means that exactly the same data comes from any of two or more different processes
data store or sink to a common location.
3) A data flow cannot go directly back to the same process it leads. There must be atleast one other
process that handles the data flow produce some other data flow returns the original data into the
beginning process.
4) A Data flow to a data store means update (delete or change).
5) A data Flow from a data store means retrieve or use.

A data flow has a noun phrase label more than one data flow noun phrase can appear on a single
arrow as long as all of the flows on the same arrow move together as one package.

PASTE YOUR DFD’S HERE

6.5. DATA DICTONARY
After carefully understanding the requirements of the client the the entire data storage requirements are
divided into tables. The below tables are normalized to avoid any anomalies during the course of data entry.

(PASTE YOUR TABLES HERE)

Chapter 7
 7. OUTPUT SCREENS

Paste YOUR Screens Here

Chapter 8
 8. SYSTEM TESTING AND IMPLEMENTATION
8.1 INTRODUCTION
Errors are relevant only after the system is in use. A system that has been put to use with out
testing can be disastrous in terns of the application
The importance of software testing and its implications cannot be overemphasized. Software
testing is a critical element of Software Quality Assurance and represents the ultimate review of the
specifications, design and coding.

8.2 TESTING OBJECTIVES:

The main objective of testing is to uncover a host of errors, systematically and with minimum effort and
time. Stating formally, we can say,
 Testing is a process of executing a program with the intent of finding an error.
 A successful test is one that uncovers an as yet undiscovered error.
 A good test case is one that has a high probability of finding error, if it exists.
But there is one thing that testing cannot do (just to quote a very famous sentence) “Testing cannot
show the absence of defects, it can only show that software defects are presents.”
As the test results are gathered and evaluated they begin to give a qualitative indication of the reliability
of the software. If severe errors are detected, the overall quality of the software is a natural suspect. If,
on the other hand, all the errors, which are encountered, are easily modifiable, then one of the two
conclusions can be made:

 The tests are inadequate to detect possibly present errors.

 The software more or less confirms to the quality and reliable standards.
LEVELS OF TESTING
In order to uncover the errors present in different phases we have the concept of levels of
testing. The basic levels of testing are

Client Needs Acceptance Testing

Requirements System Testing

Design Integration Testing

Code Unit Testing

8.3. UNIT TESTING

Unit testing focuses verification effort on the smallest unit of software i.e. the module. Using the
detailed design and the process specifications testing is done to uncover errors within the boundary of
the module. All modules must be successful in the unit test before the start of the integration testing
begins.
In this project “Communication Media” each service can be thought of a module. There are so
many modules like fault registration, mailing, chatting. Each module has been tested by giving different
sets of inputs (giving wrong ID and password etc)when developing the module as well as finishing the
development so that each module works without any error. The inputs are validated when accepting
from the user.
Integration Testing:
After the unit testing we have to perform integration testing. The goal here is to see if modules
can be integrated properly, the emphasis being on testing interfaces between modules. This testing
activity can be considered as testing the design and hence the emphasis on testing module interactions
In this project ‘Communication Media’, the main system is formed by integrating all the modules.
When integrating all the modules I have checked whether the integration effects working of any of the
services by giving different combinations of inputs with which the two services run perfectly before
Integration.
SYSTEM TESTING
Here the entire software system is tested. The reference document for this process is the
requirements document, and the goal is to see if software meets its requirements.
Here entire ‘Communication Media’ has been tested against requirements of project and it is
checked whether all requirements of project have been satisfied or not.

ACCEPTANCE TESTING
Acceptance Test is performed with realistic data of the client to demonstrate that the software is
working satisfactorily. Testing here is focused on external behavior of the system; the internal logic of
program is not emphasized. In this project ‘XXXXXXXXXXX’ I have collected some data and tested
whether project is working correctly or not.
Test cases should be selected so that the largest number of attributes of an equivalence class is
exercised at once. The testing phase is an important part of software development. It is the process of
finding errors and missing operations and also a complete verification to determine whether the
objectives are met and the user requirements are satisfied.

8.4. TEST PLAN

This document describes the plan for testing the course scheduling software. All major testing
activities are specified here.
Test Units:
In this project we will perform two levels of testing Unit Testing and System Testing the basic
units to be tested are:
Fault Register module
Mail sending module
Mail receiving module
Chat module
Features to be tested:
All the functional features specified in the requirements document will be tested. No testing is
done for the performance requirements like response time.
Approach for Testing:
For unit testing structural testing based on the branch coverage criteria will be used. The goal is
to achieve branch coverage of more than 95%.System testing will be largely functional in nature.
Test Deliverables:
The following documents are required.
Unit Test Report for each Unit
Test case specification for system testing
Test report for system testing
The test case specification for system testing has to be submitted for review before system
testing commences
Schedule and Personnel Allocation
The entire testing is performed for a period of 10 days. Test case specifications for the system
testing are produced while unit testing is going on. The number of persons allocated for my project is
one.
TEST CASE REPORT
Here we specify all the test cases that are used for system testing. The different conditions that
need to be tested along with the test cases used for testing those conditions and the expected outputs
are given. The goal is to test the different functional requirements, as specified in the requirements
document. Test cases have been selected for both valid and invalid inputs.

SAMPLE TEST CASE REPORT

S.No Test case Condition being Expected output Actual Output
checked
1 Valid ID validity for Successful Login Successfully Logged in
registration
2 Invalid ID Validity for Login should fail Failed to login
registration

8.5. IMPLEMENTATION

Implementation is the stage where the theoretical design is turned into a working system.
The most crucial stage in achieving a new successful system and in giving confidence on the
new system for the users that it will work efficiently and effectively.

The system can be implemented only after thorough testing is done and if it is found to
work according to the specification.
 It involves careful planning, investigation of the current system and its constraints on
implementation, design of methods to achieve the change over and an evaluation of change
over methods a part from planning. Two major tasks of preparing the implementation are
education and training of the users and testing of the system.

The more complex the system being implemented, the more involved will be the systems
analysis and design effort required just for implementation.

The implementation phase comprises of several activities. The required hardware and
software acquisition is carried out. The system may require some software to be developed. For
this, programs are written and tested. The user then changes over to his new fully tested system
and the old system is discontinued.
Chapter 9
 9. SYSTEM SECURITY
9.1. INTRODUCTION
The protection of computer based resources that includes hardware, software, data, procedures
and people against unauthorized use or natural
Disaster is known as System Security.

System Security can be divided into four related issues:

 Security
 Integrity
 Privacy
 Confidentiality

SYSTEM SECURITY refers to the technical innovations and procedures applied to the hardware and
operation systems to protect against deliberate or accidental damage from a defined threat.

DATA SECURITY is the protection of data from loss, disclosure, modification and destruction.

SYSTEM INTEGRITY refers to the power functioning of hardware and programs, appropriate physical
security and safety against external threats such as eavesdropping and wiretapping.

PRIVACY defines the rights of the user or organizations to determine what information they are willing
to share with or accept from others and how the organization can be protected against unwelcome,
unfair or excessive dissemination of information about it.

CONFIDENTIALITY is a special status given to sensitive information in a database to minimize the

possible invasion of privacy. It is an attribute of information that characterizes its need for protection.

9.2. SECURITY IN SOFTWARE

System security refers to various validations on data in form of checks and controls to avoid the system
from failing. It is always important to ensure that only valid data is entered and only valid operations are
performed on the system. The system employees two types of checks and controls:
CLIENT SIDE VALIDATION
Various client side validations are used to ensure on the client side that only valid data is entered.
Client side validation saves server time and load to handle invalid data. Some checks imposed are:
 VBScript in used to ensure those required fields are filled with suitable data only. Maximum lengths
of the fields of the forms are appropriately defined.
 Forms cannot be submitted without filling up the mandatory data so that manual mistakes of
submitting empty fields that are mandatory can be sorted out at the client side to save the server
time and load.
 Tab-indexes are set according to the need and taking into account the ease of user while working
with the system.

SERVER SIDE VALIDATION

Some checks cannot be applied at client side. Server side checks are necessary to save the system
from failing and intimating the user that some invalid operation has been performed or the performed
operation is restricted. Some of the server side checks imposed is:
 Server side constraint has been imposed to check for the validity of primary key and foreign key. A
primary key value cannot be duplicated. Any attempt to duplicate the primary value results into a
message intimating the user about those values through the forms using foreign key can be
updated only of the existing foreign key values.
 User is intimating through appropriate messages about the successful operations or exceptions
occurring at server side.
 Various Access Control Mechanisms have been built so that one user may not agitate upon
another. Access permissions to various types of users are controlled according to the organizational
structure. Only permitted users can log on to the system and can have access according to their
category. User- name, passwords and permissions are controlled o the server side.
 Using server side validation, constraints on several restricted operations are imposed.
Chapter 10
 10. CONCLUSION
It has been a great pleasure for me to work on this exciting and challenging project. This project
proved good for me as it provided practical knowledge of not only programming in ASP.NET and
C#.NET web based application and no some extent Windows Application and SQL Server, but also
about all handling procedure related with “Taste Buds – The Food Ordering System”. It also
provides knowledge about the latest technology used in developing web enabled application and client
server technology that will be great demand in future. This will provide better opportunities and
guidance in future in developing projects independently.

BENEFITS:
The project is identified by the merits of the system offered to the user. The merits of this project are as
follows: -
 It’s a web-enabled project.
 This project offers user to enter the data through simple and interactive forms. This is very helpful
for the client to enter the desired information through so much simplicity.
 The user is mainly more concerned about the validity of the data, whatever he is entering. There
are checks on every stages of any new creation, data entry or updation so that the user cannot
enter the invalid data, which can create problems at later date.
 Sometimes the user finds in the later stages of using project that he needs to update some of the
information that he entered earlier. There are options for him by which he can update the records.
Moreover there is restriction for his that he cannot change the primary data field. This keeps the
validity of the data to longer extent.
 User is provided the option of monitoring the records he entered earlier. He can see the desired
records with the variety of options provided by him.
 From every part of the project the user is provided with the links through framing so that he can go
from one option of the project to other as per the requirement. This is bound to be simple and very
friendly as per the user is concerned. That is, we can sat that the project is user friendly which is
one of the primary concerns of any good project.
 Data storage and retrieval will become faster and easier to maintain because data is stored in a
systematic manner and in a single database.
 Decision making process would be greatly enhanced because of faster processing of information
since data collection from information available on computer takes much less time then manual
system.
 Allocating of sample results becomes much faster because at a time the user can see the records
of last years.
 Easier and faster data transfer through latest technology associated with the computer and
communication.
 Through these features it will increase the efficiency, accuracy and transparency,

LIMITATIONS:
 The size of the database increases day-by-day, increasing the load on the database back up and
data maintenance activity.
 Training for simple computer operations is necessary for the users working on the system.
Chapter 11
 11. FUTURE IMPROVEMENT
 Different online payments facilities will be provided via different payment gateways.
 Extending customer base by offering different deals/offers to them in future
 Expanding locations/ outlets to cover for better services.
 In the future the employee information and their payroll maintenance will also be included as
part of this application
Chapter 11
 12. BIBLIOGRAPHY

 FOR .NET INSTALLATION

www.support.mircosoft.com
 FOR DEPLOYMENT AND PACKING ON SERVER
www.developer.com
www.15seconds.com
 FOR SQL
www.msdn.microsoft.com
 FOR ASP.NET
www.msdn.microsoft.com/net/quickstart/aspplus/default.com
www.asp.net
www.fmexpense.com/quickstart/aspplus/default.com
www.asptoday.com
www.aspfree.com
www.4guysfromrolla.com/index.aspx