Project Report

On
“Book Store”

Submitted to the Rajasthan S.S Jain Subodh PG College In

Partial fulfillment of the requirement for the degree of

MASTER OF COMPUTER APPLICATIONS

Submitted By:
(Sunil Kumar Hurkat)

Name of Internal Guide Name of Training Incharge

(Mr. Mahendra Kumar) (DVS Web InfoTech)

Department of Computer Science

S.S Jain Subodh PG College ,jaipur(Raj.)
Session 2016-2017
 CERTIFICATE
This is to certify that the Project report entitled “Book Store” undertaken at the ‘S.S
Jain Subodh PG College, jaipur’ is a bona-fide record of the original work done by
Sunil Kumar Hurkat.
This project is being submitted in fulfillment of the requirement for submitting .NET
project in Masters of Computer Application 6th Semester of Computer Science of the
S.S Jain Subodh PG College, jaipur.
Date:
Place:
Name of Project Guide-
Director
Department of Computer Science
S.S Jain Subodh PG College
 Acknowledgement

I would like to thank respected Ms. Madhu for giving me such a wonderful opportunity
to expand my knowledge for my own branch and giving me guidelines to present a
seminar report. It helped me a lot to realize of what we study for.

Secondly, I would like to thank my parents who patiently helped me as I went through
my work and helped to modify and eliminate some of the irrelevant or un-necessary
stuffs.

Thirdly, I would like to thank my friends who helped me to make my work more
organized and well-stacked till the end.

Next, I would thank Microsoft for developing such a wonderful tool like MS Word. It
helped my work a lot to remain error-free.

Last but clearly not the least, I would thank The Almighty for giving me strength to
complete my report on time.
BOOK STORE
 Table of Contents

1) Introduction

2) Project Plan
2.1 Risk management Planning
2.2 Cost planning
2.3 Schedule Planning
2.4 Environment Planning
2.5 Resource Planning

3) System Analysis
3.1 Study of the problem
3.2 Preliminary Investigation

4) Feasibility Study
4.1 Technical feasibility
4.2 Financial feasibility
4.3 operational feasibility

5) System Requirement Specification

5.1 Hardware requirements
5.2 Software requirements
5.3 Technology Specification

6) Cost Estimation
7) Website Model Description
7.1 User Identificaiton
7.2 Select Service
7.3 Record Purchase
7.4 Record Sales
7.5 Search For Existing books
7.6 Calculate budget
7.7 Prepare Stock Evaluation
7.8 Display Stock Details

8) UML Diagram
8.1 Context level Diagram
8.2 Zero level Diagram
8.3 ER- Diagram
8.4 Architectural Diagram
9) Testing
9.1 Integration Testing
9.2 White Box Testing
9.3 Black Box Testing
9.4 Security Testing
9.5 Performance Testing

10) Implementation and Maintenance

10.1 Implementation
10.2 Maintenance

11) SNAPSHOT’S
12) Database Design
13) Conclusion
14) Future Scope of Project
 INTRODUCTION

A fictitious mail-order bookseller specializing in titles from Microsoft® Press has

decided to expand its business reach by launching a Web site, Online Bookstore.
Because the company has an established order-processing system with large
investments in mid-range and mainframe systems, it has decided to create a Web-
commerce solution that will leverage these existing systems.
The key motivation for the project is to get a presence on the Web as soon as possible,
because sales have declined following the advent of other online booksellers. This is
the first endeavor of its kind for this company; therefore, project goals include
keeping overall lifetime project costs low by utilizing existing infrastructure when
possible and providing a low-cost-to-support solution. Performance is important but
secondary to supportability costs and a short-term rollout schedule. If successful, the
company will revisit the design to identify areas for improvement.
As a result of mergers and acquisitions, the company’s enterprise data resides in a
variety of data stores. For instance, customer information is kept in an Oracle 8
database running on a Sun SPARC/Solaris system. Order and inventory data is stored
in an IBM DB2 database running on an IBM MVS system inherited from a merger
with another bookseller. CICS programs on this system are used to process credit card
authorizations. The company’s shipping system is run from an IBM AS/400, with the
shipping data stored in keyed, physical files.
 PURPOSE

This Web Application provides facility to conduct online examination world wide.

 It saves time as it allows number of students to give the exam at a time and
displays the results as the test gets over, so no need to wait for the result. It is
automatically generated by the server.

 Administrator has a privilege to create, modify and delete the test papers and
its particular questions.

 User can register, login and give the test with his specific id, and can see the
results as well.
 Project Plan

A project plan is the planning document, capturing the entire project end-to-end,
covering all project phases, from initiation through planning, execution and closure.

There are the some planning’s which we have discussed before making an Online
Examination System-

2.1 Risks Management Planning:

Since Risk index, methods to identify and evaluate risks, risk mitigation and
contingency planning. In this project we have used different types of validations
which will serve us from many types of risks.

2.2 Cost Planning:

We have calculated the total cost of our project by Combo Model and have find that
this cost is feasible according to our budget. This plan of cost will identify the total cost
in term of price economically.

2.3 Schedule Planning:

We are working on this project report from Feb 2017. There are two Members in our
team and each has played big role during making this project report. Scheduling of
Indiaface project development is done by dividing project in different parts.

2.4 Environment Planning:

This is the planning which identifies the environments for this project. We have
used .NET technology to make this system and IIS sever for processing. We have also
used SQL SERVER 2008 as back-end and .NET for front-end.

2.5 Resources Planning:

The planning of resources will be the planning of hardware plans, documentation plans
or software plans which are used in this project. The hardware resources like computer
which will be the main component while doing this.
 System Analysis
3.1 Study of the problem

System Analysis is an investigation into a problem and how a new system will solve
it. It is the most essential part of the development of a project of a system analysis.
System analysis consists of system element, process and technology.

To analyze a system, has to study the systems in details. The analyst has to understand
the functioning and concept of the system in detail, before design the appropriate
computer based system that will meet all the requirements of the existing system. The
system analyst has to carry out a customary approach to use the computer for problem
solving.

System analysis includes the following basic concepts

• Preliminary investigation
• Requirements specification
• Feasibility study
• Detailed investigation
• Drawing up of strategies

• Design and coding

• Testing and training
• Implementation

The above steps constitute the logical framework for the system analysis. After the
preliminary investigation and feasibility study, the scope of the defined and
comparable items are set forth and hence detailed investigation is executed. This
allows the system analyst to comprehend the full scope of the project. Soon after the
implementation of the newly developed system, followed by the training of the users,
the system analysis is included.
 3.2 Preliminary Investigation

A request to receive assistance from information system can be made for many
reasons, but in case a manager, employee or system specialist initiates the
request. When that request is made, the first system activity preliminary
investigation begins. The activity has three parts

> Request clarification: the request from employee may not be well stated.
Sometimes the request may not be well defined. Therefore before any system
investigation can be considered, the project request must be examined to
determine precisely the actual requirements of the organization.

> Feasibility study: the basic idea behind feasibility study is to determine
whether the project is feasible or not.

> Request approval: all projects that are requested are not desirable or feasible
.some organization receive so many projects requests from employee that only a
few of them can be pursued. However those projects that are feasible and
desirable should put into a schedule. The management decides request that are
most important. After a project request is approved the cost priority, the
completion time and the personal required are estimated. Once the request is
approved, the collection of data and determination of requirements can be
started.
 Feasibility Study
The basic idea behind feasibility study is to determine whether the project is feasible
or not. A feasibility is conducted to identify a best system that meets all the
requirements. This includes an identification ,description, an evaluation of the
proposed systems and selection of the best system for the job .

The requirements of the system are specified with a set of constraints such as system
objectives and the description of the out puts. It is then duty of the analyst to evaluate
the feasibility of the proposed system to generate the above results. Three key factors
are to be considered during the feasibility study.

4.1 Operational Feasibility

An estimate should be made to determine how much effort and care will go into the
developing of the system including the training to be given to the user. Usually,
people are reluctant to changes that come in their progression. The computer
initialization will certainly affected the turn over, transfer and employee job status.
Hence an additional effort is to be made to train and educate the users on the new way
of the system.

4.2 Technical Feasibility

The main consideration is to be given to the study of available resources of the

organization where the software is to be implemented. Here the system analyst
evaluates the technical merits of the system giving emphasis on the performance,
reliability, maintainability and productivity.

By taking the consideration before developing the proposed system, the resources
availability of the organization was studied. The organization was immense computer
facilities equipped with sophisticated machines and the software hence this
technically feasible.

4.3 Economic Feasibility

Economic feasibility is the most important and frequently used method for evaluating
the effectiveness of the proposed system. It is very essential because the main goal of
the proposed system is to have economically better result along with increased
 efficiency. Cost benefit analysis is usually performed for this purpose. It is the
comparative study of the cost verses the benefit and savings that are expected from
the proposed system. Since the organization is well equipped with the required hard
ware, the project was found to be economically.

System Requirement Specification

The purpose of this SRS document is to write the functional and non functional user or
system requirements that represent the characteristics of On-Line Exam System.

The scope and limitation of this system is:

 The on-line exam system design to educational institutes.

 Hold all operation and generate reports to student, teachers and administrator.
 Support multiple choices questions.
 Allow the student to prochoice the answer and to see his mark.
 Verify a security, authority and safety.

HARDWARE REQUIREMENTS

PROCESSOR : INTEL CORE 2 DOU

CLOCK SPEED : 800 MHZ
SYSTEM BUS : 32 BIT
RAM : 500MB or more
HDD : 40GB
MONITOR : SVGA COLOR
KEY BOARD : 101 KEYS
MODEM : 56 KBPS/ADSL Broadband
MOUSE : PS2/ Serial
FDD : 1.44 MB

SOFTWARE REQUIREMENTS

OPERATING SYSTEM : WINDOW 10

BROWSER : GOOGLE CHROME OR FIREFOX
DATABASE : SQL SERVER-2012
WEB SERVER : IIS 5
SERVER SIDE SCRIPTING : ASP.NET
CLIENT SIDE SCRIPTING : JAVA SCRIPT
CONNECTION : ADO.NET
PROTOCOL : HTTP , SMTP

TECHNOLOGY SPECIFICATION

 Client-Server Architecture
Typical client-server systems are based on the 2-tiered architecture, whereby there is a
clear separation between the data and the presentation/business logic. These are
generally data driven, with the application existing entirely on the client machine
while the database server is deployed somewhere in the organization.

 2-Tier Architecture

In a traditional 2- Tiered application, the processing load is given to the client PC

while the server simply acts as a traffic controller between the application and data.
As a result, not only does the application performance suffer due to the limited
resources of the PC, but the network traffic tends to increase as well.

 3- Tier Architecture

In 3- Tier architecture an application is broken into three separate logical layers, each
with a well - defined set of interfaces. The first tier is referred to as the presentation
layer and typically consists of graphical user interface of some kind. The middle tier,
or business layer, consists of application or business layer and the third layer- the data
layer contains the data that is needed for the application. The middle tier is basically
the code that the user calls upon to retrieve the desired data. The presentation layer
then receives the data and formats it for display. This separation of application logic
from the user interface adds enormous flexibility to the design of application. The
third tier contains the data that is needed for the application.

Cost Estimation
An estimate is a prediction based upon probabilistic assessment. It is the responsibility
of the project manager to make accurate estimations of effort and cost. This is
particularly true for projects subject to competitive bidding where a bid too high
compared with competitors would result in losing the contract or a bid too low could
result in a loss to the organization. This does not mean that internal projects are
unimportant. From a project leaders estimate the management often decide whether to
proceed with the project. Industry has a need for accurate estimates of effort and size at
a very early stage in a project. However, when software cost estimates are done early in
the software development process the estimate can be based on wrong or incomplete
requirements. A software cost estimate process is the set of techniques and procedures
that organizations use to arrive at an estimate. An important aspect of software projects
is to know the cost. The major contributing factor is effort.

Why SCE is difficult and error prone?

 Software cost estimation requires a significant amount of effort to perform it

correctly.

 SCE is often done hurriedly, without an appreciation for the effort required.

 You need experience at developing estimates, especially for large projects.

 Human bias i.e. An Estimator is likely to consider how long a certain portion
of the system would take, and then to merely extrapolate this estimate to the rest
of the system, ignoring the non-linear aspects of software development.

The causes of poor and inaccurate estimation

 New software projects are nearly always different form the last.

 Software practitioners don't collect enough information about past projects.

 Estimates are forced to match the resources available.

Cost and Pricing
Our project is of high range and is highly efficient which can satisfy the shopping
calculation for almost all software companies. The chances of error occurrence is very
limited and so our costs around Rs 10, 00,000(app).

 A team of 11 members is required for completing the task.

 It takes a time span of 3 weeks to shape the project.

There are no specific environmental constraints

Web Site Model Description

There are three sub modules in this phase.

 Candidate module.
 Administrator module.

The functionality of each module is as follows:

 Candidate module: The candidate will logon to the software and take
his examination. He can also check his previous examinations marks
and his details. The candidate will get result immediately after the
completion of the examination.

 Administrator module: The administrator collects all the results after

successful completion of the examination and sends to the headquarters
as and when required.

The features that are available to the Administrator are:

 The administrator has the full fledged rights over the OES.
 Can create/delete an account.
 Can view the accounts.
 Can change the password.
 Can hide any kind of features from the both of users.
 Insert/delete/edit the information of available on OES.

 Can access all the accounts of the faculty members/students.

The features available to the Students are:

 Can view the different categories of Test available in their

account.

 Can change password.

 Can view their marks.

 Can view the various reading material.

 Can view and modify its profile but can modify it to some
limited range.

The features available to the Examiner are:

 Can view the different categories of Test conducted by users.

 Can change password.

 Can view their marks.

 Can view and modify Results.

UML DAIGRAM
 DATA FLOW DIAGRAM
Data flow diagram can define the different type of customer of a system various
ways that they interact with system.
 Show the processes that change or transform data
 Show the movement of data between processes
 Represent a system as a network of processes which transform data
flowing between them
The user screen flow shows what a user of the community will see. After
Successfully logging on , the user will be given various links(such as search user,
search boards, view mail, etc.) and be able to select options from there, or go back to
their home.
Context Diagram
The highest level data flow diagram is the context diagram .
 The context diagram shows the interaction of the system with its environment
in terms of data flows.
 The context diagram defines the boundary of the system (the scope of the
system)
 Only the data flows which leave the system and the data flows which come
from outside the system are shown.

0 Level DFD: A level 0 DFD, also called a fundamental system model or context
diagram represent s the entire software element as a single bubble with input and
output data indicated by incoming and outgoing arrows, respectively.
ENTITY-RELATIONSHIP Diagram

E-R (Entity-Relationship) Diagram is used to represents the relationship between

entities in the table.

The symbols used in E-R diagrams are:

SYMBOL PURPOSE

Represents Entity sets.

Represent attributes.

Represent Relationship Sets

Structured analysis is a set of tools and techniques that the analyst.
To develop a new kind of a system:

The traditional approach focuses on the cost benefit and feasibility analysis,
Project management, and hardware and software selection an personal
considerations.
Use Case Diagrams
Asp.Net OverView
ASP.NET is a unified Web development model that includes the services necessary for
you to build enterprise-class Web applications with a minimum of coding. ASP.NET is
part of the .NET Framework, and when coding ASP.NET applications you have access
to classes in the .NET Framework. You can code your applications in any language
compatible with the common language runtime (CLR), including Microsoft Visual
Basic and C#. These languages enable you to develop ASP.NET applications that
benefit from the common language runtime, type safety, inheritance, and so on.
If you want to try ASP.NET, you can install Visual Web Developer Express using
the Microsoft Web Platform Installer, which is a free tool that makes it simple to
download, install, and service components of the Microsoft Web Platform. These
components include Visual Web Developer Express, Internet Information Services
(IIS), SQL Server Express, and the .NET Framework. All of these are tools that you use
to create ASP.NET Web applications. You can also use the Microsoft Web Platform
Installer to install open-source ASP.NET and PHP Web applications.
This topic describes the following features of ASP.NET and of Visual Web Developer,
the development environment for creating ASP.NET applications.
 The Three Flavors of ASP.NET: Web Forms, MVC, and Web Pages
 Visual Web Developer
 ASP.NET Web Sites and ASP.NET Web Application Projects
 ASP.NET API Reference
 Page and Controls Framework
 ASP.NET Compiler
 Security Infrastructure
 State-Management Facilities
 ASP.NET Configuration
 Health Monitoring and Performance Features
 Debugging Support
 Web Services Framework
 Extensible Hosting Environment and Application Life-Cycle Management
  Extensible Designer Environment
 Web Applications Based on the MVC Pattern
 ASP.NET Dynamic Data

The Three Flavors of ASP.NET: Web Forms, MVC, and Web Pages
ASP.NET offers three frameworks for creating web applications: ASP.NET Web
Forms, ASP.NET MVC, and ASP.NET Web Pages. All three frameworks are stable and
mature, and you can create great web applications with any of them.

Each framework targets a different audience or type of application. Which one you
choose depends on a combination of your web development experience, what
framework you’re most comfortable with, and which is the best fit for the type of
application you’re creating. All three frameworks will be supported, updated, and
improved in future releases of ASP.NET.

Here's an overview of each of the frameworks and some ideas for how to choose
between them.

ASP.NET Web Forms (.aspx pages)

The Web Forms framework targets developers who prefer declarative and control-
based programming, such as Microsoft Windows Forms (WinForms) and
WPF/XAML/Silverlight. It offers a WYSIWYG designer-driven (drag-and-drop)
development model, so it's popular with developers looking for a rapid application
development (RAD) environment for web development. If you’re new to web
programming and are familiar with the traditional Microsoft RAD client development
tools (for example, for Visual Basic and Visual C#), you can quickly build a web
application without having expertise in HTML and JavaScript.

In particular, the Web Forms model provides the following features:

 An event model that exposes events which you can program like you would

program a client application like WinForms or WPF.

 Server controls that render HTML for you and that you can customize by
setting properties and styles.
  A rich assortment of controls for data access and data display.

 Automatic preservation of state (data) between HTTP requests, which makes it

easy for a programmer who is accustomed to client applications to learn how
to create applications for the stateless web.

Web Forms works well for small teams of Web developers and designers who want to
take advantage of the large number of components available for rapid application
development. In general, creating a Web Forms application requires less programming
effort than creating the same application by using the ASP.NET MVC framework. The
components (the Page class, controls, and so on) are tightly integrated and usually
require less code than ASP.NET MVC applications. However, Web Forms is not just
for rapid application development. There are many complex commercial apps and app
frameworks built on top of Web Forms.

Because a Web Forms page and the controls on the page automatically generate much
of the markup that's sent to the browser, you don't have the kind of fine-grained control
over the HTML that the other ASP.NET models offer. An event-driven, control-focused
model hides some of the behavior of HTML and HTTP. For example, it's not always
possible to specify exactly what markup might be generated by a control.

The Web Forms model doesn't lend itself as readily as ASP.NET MVC to patterns-
based development, separation of concerns, and automated unit testing. If you want to
write code factored that way, you can; it’s just not as automatic as it is in the ASP.NET
MVC framework. The ASP.NET Web Forms MVP project shows an approach that
facilitates separation of concerns and testability while maintaining the rapid
development that Web Forms was built to deliver. As an example of this in action,
Microsoft SharePoint is built using Web Forms MVP.

ASP.NET MVC
ASP.NET MVC targets developers who are interested in patterns and principles
like test-driven development, separation of concerns, inversion of control (IoC),
and dependency injection (DI). This framework encourages separating the business
logic layer of a web application from its presentation layer.

By dividing the application into the model (M), views (V), and controllers (C),
ASP.NET MVC can make it easier to manage complexity in larger applications. With
ASP.NET MVC, you can have multiple teams working on a web site because the code
for the business logic is separate from the code and markup for the presentation layer
— developers can work on the business logic while designers work on the markup and
JavaScript that is sent to the browser.

With ASP.NET MVC, you work more directly with HTML and HTTP than in Web
Forms. Web Forms tends to hide some of that by mimicking the way you would
program a WinForms or WPF application. For example, Web Forms can automatically
preserve state between HTTP requests, but you have to code that explicitly in MVC.
The MVC model enables you to take complete control over exactly what your
application is doing and how it behaves in the web environment.

MVC was designed to be extensible, providing power developers the ability to

customize the framework for their application needs. In addition, the ASP.NET MVC
source code is available under an OSI license.

MVC 4 includes a feature that helps you develop HTTP services that reach a broad
range of clients, including browsers and mobile devices. For more information,
see Getting Started with ASP.NET Web API. MVC 4 also helps you develop single-
page applications (SPAs) that use client-side JavaScript for responsive client
interaction. For more information, see Single Page Application Overview.
For more information about ASP.NET MVC, see ASP.NET MVC.
 ASP.NET Web Pages (.cshtml and .vbhtml files)

ASP.NET Web Pages targets developers who want a simple web development story,
along the lines of PHP. In the Web Pages model, you create HTML pages and then add
server-based code to the page in order to dynamically control how that markup is
rendered. Web Pages is specifically designed to be a lightweight framework, and it's
the easiest entry point into ASP.NET for people who know HTML but might not have
broad programming experience — for example, students or hobbyists. It's also a good
way for web developers who know PHP or similar frameworks to start using ASP.NET.
Like Web Forms, Web Pages is oriented toward rapid development. Web Pages
provides components called helpers that you can add to pages and that let you use just
a few lines of code to perform tasks that would either be tedious or complex. For
example, there are helpers to display database data, add a Twitter feed, log in using
Facebook, add maps to a page, and so on.
Web Pages provides a simpler approach than Web Forms. If you look at a .cshtml or
.vbhtml file, you can generally think of the logic as executing top-to-bottom in the file,
as you would with PHP, SHTML, etc. And because .cshtml and .vbhtml files are
essentially HTML files that have additional ASP.NET code in them, they lend
themselves easily to adding client-side functionality via JavaScript and jQuery.
For more information about ASP.NET Web Pages, see ASP.NET Web Pages on the
ASP.NET web site.

General Notes
All three ASP.NET frameworks are based on the .NET Framework and share core
functionality of .NET and of ASP.NET. For example, all three frameworks offer a login
security model based around a membership API, and all three share the same facilities
for managing requests, handling sessions, and so on that are part of the core ASP.NET
functionality.
In addition, the three frameworks are not entirely independent, and choosing one does
not preclude also using another. For example, MVC views are often written as .cshtml
or .vbhtml files (using "Razor" syntax), which means they can take advantage of some
of the Web Pages features like helpers. Since the frameworks can also coexist in the
same web application, it's not uncommon to see individual components of an
application written using different frameworks. For example, the bulk of a site might
be written in MVC, but the data access portion of the site might be written using Web
Forms because it’s such an easy framework in which to perform data access. In these
cases, the developers choose the hybrid solution that plays to their strengths and makes
their lives the easiest for their particular scenarios.
As of March 28, 2012, Microsoft has placed ASP.NET MVC 4, ASP.NET Web API,
and ASP.NET Web Pages v2 (Razor syntax) under the open source Apache 2.0 license.
ASP.NET Web Forms is not included. For more information, see ASP.NET MVC, Web
API, Razor and Open Source (ScottGu’s blog) and ASP.NET MVC 4, ASP.NET Web
API and ASP.NET Web Pages v2 (Razor) now all open source with contributions (Scott
Hanselman’s blog).
The remaining sections of this topic provide an overview of ASP.NET features that are
common to all three ASP.NET frameworks or unique to Web Forms.
Visual Web Developer
Visual Web Developer is a full-featured development environment for creating
ASP.NET Web applications. Visual Web Developer offers you the following features:
 Web page design A powerful Web page editor that includes WYSIWYG
editing and an HTML editing mode with IntelliSense and validation.
 Page design features Consistent site layout with master pages and

consistent page appearance with themes and skins.

 Code editing A code editor that enables you to write code for your dynamic
Web pages in Visual Basic or C#. The code editor includes syntax coloration
and IntelliSense.
  Testing and Debugging A local Web server for testing and a debugger that
helps you find errors in your programs.
 Deployment Tools to automate typical tasks for deploying a Web application
to a hosting server or a hosting provider.

Testing and Debugging

Visual Web Developer provides an ideal environment in which to build Web sites and
then publish them to a hosting site. Using the development tools in Visual Web
Developer, you can develop ASP.NET Web pages on your own computer. Visual Web
Developer includes a local Web server that provides all the features you need to test
and debug ASP.NET Web pages, without requiring Internet Information Services (IIS)
to be installed.
When your site is ready, you can publish it to the host computer using the built-in Copy
Web tool, which transfers your files when you are ready to share them with others.
Alternatively, you can precompile and deploy a Web site by using the Build Web
Site command. The Build Web Sitecommand runs the compiler over the entire Web
site (not just the code files) and produces a Web site layout that you can deploy to a
production server.
Finally, you can take advantage of the built-in support for File Transfer Protocol (FTP).
Using the FTP capabilities of Visual Web Developer, you can connect directly to the
host computer and then create and edit files on the server.

ASP.NET Web Sites and ASP.NET Web Application Projects

Using Visual Studio, you can create different types of ASP.NET projects, which
includes Web sites, Web applications, Web services, and AJAX server controls.
There is a difference between Web site projects and Web application projects. Some
features work only with Web application projects, such as MVC and certain tools for
automating Web deployment. Other features, such as Dynamic Data, work with both
Web sites and Web application projects. For more information about the differences
between Web application projects and Web site projects,.

MYSQL

Introduction
This article will introduce SQL Server, what it is, and why to use it. We’ll examine
when to use a database as well when not to. In addition, we’ll introduce some of the
key terms used with SQL Server.

What is a SQL Server?

SQL Server is a Microsoft product used to manage and store information. Technically,
SQL Server is a “relational database management system” (RDMS). Broken apart, this
term means two things. First, that data stored inside SQL Server will be housed in a
“relational database”, and second, that SQL Server is an entire “management system”,
not just a database. SQL itself stands for Structured Query Language.

This is the language used to manage and administer the database server.

Relational Database
So now that SQL Server has been broken into two terms, a “relational database” and a
“management system”, let’s explore the first. There is a very technical definition for
what is or is not a relational database. For details on this definition, do an internet
search for the terms “Edgar Codd” (who first proposed the relational model), or the
terms “relational database tuples”. While there are databases that are not relational,
most of the products on the market today (SQL Server, Oracle, MySQL, and MS
Access to name a few) are relational database products. This means that data is stored
inside a structure called a “Table”, which uses Rows and Columns (like a spreadsheet).
Unlike a spreadsheet though, the data rows stored inside a Table is not in any particular
order. To explain this last statement, think of a typical spreadsheet column, if we
wanted to sort the data in the first column of a spreadsheet alphabetically, we would
simply click the first column and then would click the Sort button. The Rows of data
would change their order so they were now sorted the way we wished, as shown in the
before and after images below:

Notice that the data actually moved. The name “Dave” moved from the third row to the
first. In a Database Table, this never happens. The data would not be rearranged. If we
wanted a sorted list like this, we would ask the database to present us with a display
copy of the data sorted the way we wanted. This request to see the data is called a
Query. So when we run a Query, we see our own personalized display copy of the data,
the actual data items are not rearranged.

When discussing SQL Server, the term “Database”, can sometimes be thrown around
loosely, meaning different things to different people. This happens because a database
is a core, central component to SQL Server. Therefore, the term has become a slang
shortcut way of meaning SQL Server as a whole. In actuality, SQL Server is RDBMS
(Relational Database Management System). Its job is managing databases.

A “Database” is a logical container object. It’s used for storing like types of
information together, to help with organization. Also, a Database can be used as an
easy security boundary. Usually, though not a rule, databases separate applications
from each other. For example, all the Accounting system information may be
contained in one database, while all the Marketing information is in another. Again,
this is not a SQL Server rule; you could have all your corporate information contained
in a single database. It would be very confusing from an organization perspective, but
SQL Server would allow it. Conversely, you could separate each little group of
information into their own database, having hundreds or even thousands of databases
inside a single SQL Server. This scenario would be a management nightmare, but there
are no SQL Server rules preventing it. Usually, a common sense rule is applied for
determining what a database should contain. If the data and objects are related to each
other, and it would be helpful to apply security to the group as a whole, than this is a
good candidate to be its own database. A single SQL Server can contain over 32,000
separate databases.

When a new database is created, two physical files are created on the hard drive. One
file holds all the objects and data, the other contains a log of all the database changes.
These files are proprietary to SQL Server and cannot be opened by Word, Excel,
Notepad, or any other application. The file size of a database can be over 500,000
Terabytes.

Why use a Database?

So, now that we know SQL Server is an application for storing information inside a
“table” structure, let’s examine the reasons why you would use a Database rather than a
spreadsheet or some other program for data storage.

Imagine you’re creating an application for storing sales transactions. We’ll start by
saving just a few columns of information such as the Item Sold, Quantity, Price, Sale
Date, and the Customer sold to. One of the first storage options to consider is saving
this information in a large text file. There are benefits to text file saves such as quick
write times. The problem with text files is during a read, if the text file is large, it can
take quite a bite of time to open and scan the contents of the file looking for what we
want. Also, if we wanted to see all the sales to a specific customer, the entire text file
would have to be read, and every line occurrence of the customer name would need to
be saved in some temporary place until we had them all. If we saved to a spreadsheet
instead of a text file, we would have a Sort feature built in. So we may be able to find
all the sales to a specific customer quicker, but again, if the file was large, opening the
spreadsheet could take a great deal of time.

In addition, what if we wanted to save the customers address as well as their name,
now instead of saving five pieces of information (Item Sold, Quantity, Price, Sale Date,
and the Customer sold to), we’ll be saving nine columns of information (all the
previous plus Address, City, State, and Zip). This means were going to almost double
the size of our text file or spreadsheet to accommodate this additional customer data.
However, if we used a database, we could save the sales data and the customer address
data in two separate places, so the size of the sales data wouldn’t get any larger. When
we wanted a report showing the customers’ address, we could “Relate” or link the
address data to the sales data.

Not only would our sales information be smaller in a database, but the actual address
data would be smaller as well. In a spreadsheet or text file, each sales line would
include a complete address. In a database, the address would only be recorded once. It
wouldn’t matter if the customer made 100 or 100,000 purchases. All sales records
would point to, or “Relate” to, that same single address line.

This “Relating” of data, so sizes stay small is one benefit of a database. In addition,
reading and writing to database is very fast. Plus, many databases support having
multiple users access the same data at the same time. Something text files and
spreadsheets don’t do. Also, the amount or volume of information a database can store
is almost unlimited, unlike a spread sheet where there is a fixed number or rows that
can be saved.

Why Not Use a Database?

There are some problems with using a database. First, time must be taken to learn the
new system. A database is not as intuitive as a spreadsheet. In addition, if there is only
a small amount of data that doesn’t need to be changed over time, it’s probably simpler
to save it in a file. Unfortunately, most business problems are neither simple nor small,
so a database is usually the best tool for the job.

Management System
The second term in our SQL Server definition is “Management System”. This means
that SQL Server is more than just an application to hold data; it also includes the tools
needed to structure, manipulate, and manage that data. In addition, when you install
SQL Server, there are options for including Report Writing tools, Data Import Export
applications, Analysis tools, and Management Interfaces.
 Conclusion

SQL Server is a Relational Database Management System. Data is stored is Tables

consisting of columns and rows. Tables can be linked, or “Related”, to one another.
Tables and objects that belong to the same family or require similar security are
collectively stored in a Database.

TESTING
 Testing is a process of executing a program with the intent of finding an error. A good
test case is the one that has a probability of finding an as yet undiscovered error. If
testing is conducted successfully (according to the objective stated) it will uncover
errors in the software. As secondary benefit, testing demonstrates that software
function appears to be working according to the specification that performance
requirements appear to have been met. In addition data collected as testing is
conducted provides a good indication of software reliability and some indication of
software quality as a hole.

Here the System testing involved is the most widely used testing process consisting of
five stages as shown in the figure. In general, the sequence of testing activities is
component testing, integration testing, and then user testing. However, as defects are
discovered at any one stage, they require program modifications to correct them and
this may require other stages in the testing process to be repeat.

Fig (Testing Model)

(Component testing) (Integration testing) (User testing)

Testing is the process of detecting errors. Testing performs a very critical role for
quality assurance and for ensuring the reliability of the software. The results of testing
are used later on during maintenance also. Testing is vital to the success of the system.
System testing makes a logical assumption that if the parts of the system are correct,
the goal will be successfully achieved. In adequate testing or non-testing leads to errors
that may not appear until months or even years.

This creates two problems:

1. The time lag between the cause and the appearance of the problem.

2. The time interval effect of the system errors on files and the records on the
system.

 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.
 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

Clients Needs Accepting Testing

Requirements System Testing

Design Integration Testing

 Integration Testing
After 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 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.

 White Box Testing

This is a unit testing method, where a unit will be taken at a time and tested thoroughly
at a statement level to find the maximum possible errors.

I tested step wise every piece of code, taking care that every statement in the code is
executed at least once. The white box testing is also called Glass Box Testing.

I have generated a list of test cases, sample data, which is used to check all possible
combinations of execution paths through the code at every module level.

White-box test focuses on the program control structure. Test cases are derived to
ensure that all statement in the program control structure. Test cases are derived to
ensure that all statement in the program control structure. Test cases are derived to
ensure that all statement in the program has been executed at least once during testing
and that all logical conditions have been exercised. Basis path testing, a white box
technique, makes use of program graphs (or graph matrices) to derive the set of
linearly independent test that will ensure coverage. Condition and data flow testing
further exercising degrees of complexity.

 Black Box Testing

This testing method considers a module as a single unit and checks the unit at interface
and communication with other modules rather getting into details at statement level.
Here the module will be treated as a block that will take some input and generate
output. Output for a given set of input combinations are forwarded to other
modules.Black-box test are designed to uncover errors functional requirement without
regard to the internal workings of a program. Black-box testing techniques focus on the
information domain of the software, deriving test cases by partitioning the input and
output domain of a program in manner that provides through test coverage. The black-
box test is used to demonstrate that software functions are operational, that input is
properly produced, and that the integrity of external information are maintained. A
black-box test examines some fundamental aspect of a system with little or no regard
for the integral logical structure of the software.

Graph based testing methods explore the relationship between and behavior of
program objects.

 Security Testing

It incorporates a series of tests designed to exploit vulnerabilities in the Mobile

application and its environment. The intent is to demonstrate that a security breach is
possible.

E.g. Validation security for valid User

Login

Verify Email &

USER
Password

Correct InCorrect

Enter in Go Back to
Application to login Page with
use the service invalid user
message

Fig - validation security for valid user

 GUI Testing Input/Output Testing:

GUI testing is done to ensure the uniform look on feel of the user interface
components across the application. All major elements of the graphical
interface such as windows, mouse operations etc. were validated during GUI
testing, various selections were made through mouse and keyboard to ensure
that it works both ways.It was tested that appropriate message appear to guide
the user through the course of action.

 Configuration Testing
It attempts to uncover errors that are specific to a particular client or server environment. A
cross reference matrix that defines all probable operating systems, browsers, hardware
platforms and communication protocols is created. Tests are then conducted to uncover errors
associated with each possible configuration. The job of configuration testing is not to exercise
only client side; rather it is to test a set of probable client side and server side configuration.

 Performance Testing
It encompasses a series of tests that are designed to assess 1.how Mobile app response
time and reliability are affected by increased user traffic,2.which Mobile app
components are responsible for performance degradation and what usage
characteristics cause degradation to occur and how performance degradation impacts
overall Mobile app objectives and requirements.

 Content Testing
It attempts to uncover errors in content. This testing activity is similar in many respects
to copy-editing for a written document. In fact, a large web site might enlist the
services of a professional copy editor to uncover typographical errors, grammatical
mistakes, errors in content consistency, errors in graphical representations and cross
referencing errors.

 Interface Testing
It exercises interaction mechanisms and validates aesthetic aspects of the user
interface. The intent is to uncover errors that result from poorly implemented
interaction mechanisms or omissions, inconsistency or ambiguities that have been
introduced into the interface inadvertently.

Implementation and Maintenance

Implementation is the process of having systems personnel check out and put new
equipment into use, train users, install the new application and construct any files of
 data needed to use it. This phase is less creative than system design. Depending on the
size of the organization that will be involved in using the application and the risk
involved in its use, systems developers may choose to test the operation in only one
area of the firm with only one or two persons. Sometimes, they will run both old and
new system in parallel way to compare the results. In still other situations, system
developers stop using the old system one day and start using the new one the next.
The implementation phase is less creative than system design. It is primarily with user
training, site preparation and file conversion. When the candidate system is linked to
terminals or remote sites, the telecommunication network and test of the network
along with system are included under the implementation. During final testing, user
acceptance is tested, followed by user training. Depending on the nature of the
system, extensive user training may be required. Conversion usually takes place at
about the same time the user is being trained. .

Aspects of Implementation

The two aspects of implementation are:

 Training Personnel
 Conversion Procedures
 Training
Even well designed and technically elegant systems can succeed or fail because of
the way they are used. Therefore the quality of the training received by the
personnel involved with the system in various ways helps or hinders, and may
even prevent, the successful implementation of an information system. Since,
Human Resource Recruitment Process is web-based and user friendly, not much
effort was required in training process.

 Conversion:
Conversion is the process of changing from the old system to the new system. There
are two methods of handling systems conversion:

1. Parallel Run

2. Immediate cut-off

MAINTENANCE
Maintenance will cover a wide range of activities including correcting coding and
design errors, updating documentation and test data and upgrading user support. Many
activities classified as maintenance actually fall under enhancements. Hence in
maintenance of system enhancement also takes place. Therefore in maintenance
addition, modification, re-developing of code will take place to support changes in
specification. Maintenance is the enigma of system development. It holds the software
industry captive, typing up programming resources. Analysts and programmers spend
far more time maintaining programs than they do writing them.

It basically includes the following activity:

 Correcting design errors

 Correcting coding errors

 Updating, documentation and test data

 Adding , modifying or redeveloping the code

 Regular acceptance and validation testing

Maintenance or enhancement can be classified as:-

 Corrective

 Adaptive

 Perfective

Corrective maintenance means repairing processing or performance failures or

making changes because of previously uncorrected problems or false assumptions.
Adaptive maintenance means changing the program function. Perfective maintenance
means enhancing the performance or modifying the program(s) to respond to the
user’s additional or changing needs. Maintenance is actually the implementation of
the post implementation review plan. As important as it is, many programmers and
analysts are reluctant to perform or identify themselves with the maintenance effort.
There are psychological, personality and professional reasons for this. In any case, a
first class effort must be made to ensure that software changes are made properly and
in time to keep the system in tune with user specifications. Maintenance is costly. One
way to reduce maintenance costs is through maintenance management and software
modification audits. Software modification consists of program rewrites system level
updates, and re-audits of low ranking programs to verify and correct the soft spots.
 SNAPSHOT’S

Home.aspx
Book_Cat.aspx

SignUp.aspx
Category.spx

Itemdetails.aspzx
CartPage.aspx

Shipping.aspx
Cartinfo.aspx
Orderitem.aspx

printDetails

Database Design
Book Table

bookCat Table
Cartinfo Table

Customer Registration Table

Login Table
Mail Table

Order item Table

Shiipping Order Table

User Account Table

User Per Info Table

CONCLUSION
This Web Application provides facility to conduct Book Store world
wide. It saves time as it allows number of students to give the exam
at a time and displays the results as the test gets over, so no need to
wait for the result. It is automatically generated by the server.
Administrator has a privilege to create, modify and delete the test
papers and its particular questions. User can register, login and give
the test with his specific id, and can see the results as well.