You are on page 1of 90

Project report

On
Online Shopping Website
At

As a Partial Fulfillment of the degree of

“Masters in Computer Application”

For the year 2010-11


Table of Content
Sr. No. Topic Page No.
1 Certificate 002
2 Acknowledge 006
3 Project Profile 007
4 Organization Profile 010

SECTION – I
Part – I Online Shopping Website
5 CH – 1 Introduction
1. Project Summary 014
2. Purpose 016
3. Scope 016

6 CH – 2 Project Management
1. Project Planning and Scheduling 017
2. Risk Management 019

7 CH – 3 System Analysis
1. Study of Current System 022
2. feasibility Study 025
3. System Requirements 023
4. Requirements Validation 026

8 CH – 4 Technology Used 028


9 CH – 4 System Design
1. Design Approach 046
2. UML Diagrams 056
3. Class Diagram 066
4. Data Dictionary 067

10 CH – 5 Implementation Detail
1. Program/Module Specification 071
2. Implementation Result 074

11 CH – 6 Testing
1. Testing 075
2. Testing Plan 077
3. Testing Method 077
4. Test Cases 081

12 CH – 7 User Manual 086

PREFACE
It gives me great pleasure in placing in the hands of my esteemed Faculties this individual report
which, we believe, will go through the documentation of the project work done by me.
The objective of this report is to provide both a conceptual understanding of the system as well as
working guide.
Surely no other technology as Information Technology is proven as the driving force of the
Nation. I.T. not only decides the present but also the future. The need for website development today is a
competence in a G.U.I based front-end tool as far as the database programming is concerned.
A typical scenario today involves an application consisting of a visual front end for presenting
data options to the enterprise users, and a connection to a database for piping data to controls such as text
boxes, tables, and list boxes. These applications typically feature reporting functions to provide
documentation to teachers and administrative.
As a student of MCA when we acquire all the theoretical knowledge, it is both necessary and
advisable to acquaint the students with the real situation through, well-planned project in relevant fields.
Using all the theoretical knowledge and applying into the real application the student learns to develop
efficient real world application at the time of project training.
So, the project training is very important for the student for self-development and self-confident.
Also student learns organizational structure, rules and regulations and management in a real sense, which
helps student to get discipline in life.
Aimed for providing the reader with easier and in-depth knowledge of all the basic as well as
important aspects related to the systems having the functionality's of their respective fields in form of
report.
The report contains the literature of almost all the things, which I have gone through from the
point of view of any system development life cycle.
Moreover I have found DBMS/RDBMS to be the most exciting environment to work with,
especially when the G.U.I Tool like Visual studio (asp.net) 3.5 with C#.
A Master of Computer Applications (MCA) is a three year full time course. It covers various
topics associated with the area of computer science. In the fourth semester students have to develop a
project. During a project on “Online Shopping (Readymade Garments)” for “Shree Jaysukhalal
Vadher Institute of Management Studies, Jamnagar”.
An effort has been made to exhaustively deal with every part of the website developed and at the
appropriate position, so that a user can easily maintain the Record and all the information.

ACKNOWLEDGEMENT
This project work has been the most practical and exciting part of my learning experience, which
would be an asset for me for my future carrier.
We are thankful to Mr. Pavan Jain for providing us the project information from HCL CDC
PVT. LTD.

No Portal is created entirely by an individual. Many people have helped to create this website and
each of their contribution has been valuable. Proper organization of concept and analysis of the system is
due to keen interest and helping hand of my teachers and colleagues.
We are sincere thanks to Mr. -------- (Head of Department), who was a constant source of
inspiration not only during this project, but also in the last two years, spent in pursuing our MCA degree
at our college.
We are deeply thankful to Mr. ----------- (Training & Placement Officer) who are moldings our
thoughts and vision towards all the subjects, we was studying in all these two years.
Our most sincere thanks to our Project Guide Mr. Shyama Bhattacharya, for his kind co-
operation and who has always been guiding, encouraging and motivating us throughout the Project.
We are also greatly thankful to the entire HCL Career Development Centre Members and our
college faculty who have helped us in completion of this project directly or indirectly.

INTRODUCTION OF COMPANY
HCL CDC Pvt. Ltd is a fast growing Information Technology company, playing its part in
transforming the way the world does business.

1.1.1 Company Profile

 Name : - HCL CDC Pvt.Ltd.


 Contact Person :- Mr. Pawan Jain
 Address :- ‘Shalin Building’,3rd Floor, Near Nehru
Bridge, Ashram Road, Ahmedabad-380 015

 Phone :- 079-26565103/4/9
 Email :- info@hclcdc.com

“INFORMATION TECHNOLGY” has emerged as a bubbling and a progressive field since the last
decade. It is the key factor for transforming the world into, what we now know as, “A Global Village”,
making the sharing of knowledge and information just a click away. Computers and Information
Technology is soon to be a part-and-parcel of our daily lives.

For us, at HCL CDC PVT.LTD, Customer Satisfaction holds top priority. We pay a great deal of
attention to our customer’s needs and what is good for them. When it comes to computing, a reliable, fast,
cost-effective and top of the line sales and services of computer becomes essential. We offer the best and
the most appropriate solutions to our clients and customers. We make it work for them.

1.1.2 TECHNICAL SKILS

 Computer Hardware

Computers – Desktop PCs, Laptops, Servers, Work stations

Peripherals – Modems, Printers, Scanners, All in ones

Networking – All types of LAN/WAN cabling including site preparation

Consulting – Site Preparation, Modular Furniture Repairs Maintenance and Services

Annual Maintenance Contracts

Computer Stationery – CD and Floppy media, Printer, Cartridges

 Authorized OF

IBM / Lenovo

Compaq-HP

Wipro
HCL

ACER

 Computer Software

Standard software packages and products like Microsoft, Adobe, Macromedia, UNIX,
Linux, Novell, etc.

Customized software solutions for office automation, billing financial accounting,


inventory, signature verification, etc. as per customer requirements.

Customized software solutions for Income Tax Dept. for their different requirements.
Customized software solutions for Central Excise (Service Tax Division) as per their
requirements.

Web Designing and Web enabled applications. Web hosting, consulting and maintenance
of web sites.

 Maintenance

We have been handling the maintenance of Computers of CCIT Ahmedabad Charge


including Bangalore, Chennai, Rajkot and Baroda since the last 5 years.

We have also handled the maintenance of computer hardware,` software and networking
in various co-operative banks.

We are providing Facility Management Services (On Site Hardware/Software Engineer)


for daily Support

 Miscellaneous

Data Entry – We provide man-power to perform data entry operations at various places
including Excise Dept.

Training – We provide corporate training at various places thereby helping our customers to
learn the know-how of different software programs.
Project Profile
 Online Shopping Site: (Website)
This material for the report of “online Shopping (gkstools.com)” gives a detailed idea about
analysis and design of the project. The given problem statement for the project has been
completely analyzed and the objectives have been set for the project.

The “gkstools.com” is an E-Commerce application. Keeping in view of the potential for web-
based shopping process, the online shopping system for the web has been designed to perform all
possible important functions.

The function include the product Catalog, Special Offers, Customer Login And Registration,
Shopping cart, place order, customer services and other facilities for the web customers. The
administrator functional areas include the Category Master, Sub Category Master, Product
Master, User Master, User Login.
Online Shopping Website

1. Introduction
2. Project Management
3. System Analysis
4. System Design
5. Implementation Details
6. Testing
7. Screen Shots
1. – INTRODUCTION

1. Project Summary
2. Purpose
3. Scope

1.1 PROJECT SUMMARY

 Also the concept of Business-to-Business and business-to-customer to find out the target
people for the specific product.
 Creating the Code Strategy for Business Logic and designing Structure of this Website.
o In the shopping Cart the Any Customer can add, delete the product in the cart.
And customer also Change the number of quantity of the product in the cart. And
it will check out. Then the customer will click on the check out then it must be the
registered will us. For this customer registration facility is available.
o In this site the customer is also show your cart by clicking on the view cart. In the
view cart the customer is show the product ID, Product image, Product Price and
Shipping Charge and quantity of product. The customer is also increase or
decrease the quantity.
o In this site the cart is maintain with the help of two table like Cart Master and Cart
Detail:
 In the cart master is store the customer detail, Total amount and shipping
charge information.
 In the cart Detail is stored the Detail about the product like Category ID,
Subcategory ID , Product ID, Product Price, Product Shipping Charge, and
other important detail about the Product.
o If any customers have any kind of inquiry then it will send the inquiry to the
owner. For this I have designed the inquiry page in this page the customer is write
its inquiry and press the submit. Then the customer is press the submit then the
customer query is directly Emailed to the Owner mail address.
o Finally the Customer is checkout then it will generate the Bill report for the user
in which it displays all the information about the Purchase. And it will also give
the facility to print out this bill or report.
 All the Products Details of this site is authorized by the Owner. It will Change any
product in Control Panel.
o The entire website is updated through the control panel of this website. In the
Control Panel of this website have different pages like Category entry,
Subcategory Entry, Product Entry, User Entry, Special Offer Entry, etc.
 In the Category Entry the Owner is Enter or stored the Value of different
types of Product Category.
 In the subcategory Entry the owner is Enter or store the value of different
types of Subcategory in different Category wise.
 In the Product Entry the Owner is Stored the all the information about the
product like Product ID, Product Name, It’s description, Price, shipping
charge, Image. for the Product image we create the upload image with the
help of this the owner itself upload the product image and it will display
on the website. It is useful for owner. He can not need to call any other to
change, add, or delete the product on the website. All the product is
categorized with the category ID and Subcategory ID.
 In the Special Offer Entry is used for any kind of special offer available in
the product. Which product is stored in the Special Offer entry it Display
on the Home page of the website.
 User entry is used to handle the control panel of the website. If the user is
registered or authorized with us then and then it will allow to login the
control panel and change the any product.
 In the Control panel all the pages have a facility to navigate the record
with the help of first, last, next, and previous button. And it will also
provide the facility to directly find the any record.
 Entire Website is fully dynamically. The entire product, Menu is display dynamically.
1.2 PURPOSE

The objective of the system is t provide generic trading system that contains the basic
functionality of any Business to customer and business to business online shopping website.

The provides the reusable software components that can be used by any client for rapid
application development and encouraging reuse of pre-developed system pieces rather than
building from scratch.

1.2.1 Provide online Product selling


1.2.2 Provide administrator module for database handling.
1.2.3 Other

1.3 SCOPE

The trend in the organization in to use E-Commerce as path towards global market. Many
organizations provide online shopping. The basic functionality remains common for this kind
of shopping so it is very beneficial to develop reusable pieces of software solution that can
provide this basic functionality.

This kind of component based Application development provides rapid application


development of complex system. Component based development also provides better
scalability and maintainability.

Online shopping website provides these kinds of basic components that can be reused and
can tailor to the requirement of the organization.
2 . - Project management

2.1 Project Planning and Scheduling


2.1.1 Project Development Approach
2.1.2 Project Planning
2.1.3 Schedule Representation

2.2 Risk Management


2.2.1 Risk Identification
2.2.2 Risk Analysis
2.2.3 Risk Planning

2.1 Project Planning and Scheduling


2.1.1 Project Development Approach

This project is given to me by company to fulfill the client’s requirement. Now-a-days E-


Business and online Shopping is very growing industry. So everybody wants that his business is
becomes global and worldwide. Our client wants to develop the website that can provide facility
to their customer to buy the product online. For the website an extra-ordinary and attractive look
is very much necessary for attract the new customer and second thing is very goof
functionalities. The user can easily find the product through the category and subcategory wise.
The user can also show the full description about the product and also it is place order, and pay
the bill online. Like this various other features can be executed with the minimum efforts and
accordingly database design has been setup for this website.
Software process model

To solve actual problems in industry setting, software engineer or a team of engineers


must incorporate a development strategy that encompasses the process, methods and tools
layers and generic phases. This strategy is often referred to as process model or a
software engineering paradigm. A process model for software engineering chosen based
on the nature of the project and application, the method and tools to be used, and the
controls and deliverables are required.

2.1.2 Project Planning

“Software Project scheduling is an activity that distributes estimated efforts across the
planned duration by allocating the efforts to specific software engineering tasks.”

For this project, we have collected the project requirements from client. Also the
requirements are examined from different aspects of the developments requirements. Then the
whole project is divided in to modules and according to that modules the development work has
been done. The DDs are designed according to the requirements. For each module, the designs
have been developed and then it is implemented.

2.1.3 Schedule representation

HCL INFOSYSTEMS LTD.

Name: Suresh Nakum, Riddhi Bhatti, Falguni Desai Group No: ED12011-3
Project: E-Post Office System (E-Post Office Web-Based Application)

Gantt Chart

Sr. Dec 2010 Jan 2011 Feb 2011 Mar 2011 Apr 2011
Phases Start Finish Duration
No 26/12 2/1 9/1 16/1 23/1 30/1 6/2 13/2 20/2 27/2 6/3 13/3 20/3 27/3 3/4 10/4

1 Task 1 Number of weeks


Text (12/20/10 to 4/20/11)
12/20/2010 3/17/2011 12.57w

2 Training of ASP.net with C# 12/20/2010 1/23/2011 5w

13 Feasibility & System Study 12/20/2010 12/26/2010 1w

24 System analysis & Specification 12/27/2010 1/2/2011 1w

System Design
35 1/3/2011 1/16/2011 2w

System Implementation &


46 coding 1/17/2011 3/20/2011 9w

57 System verification & testing 3/21/2011 3/31/2011 1.5w

68 Deployment 4/1/2011 4/4/2011 .5w

9 Maintenance 4/5/2011 4/20/2011 2.2w


2.2 Risk Management:
Risk management is the process of measuring, or assessing, risk and developing
strategies to manage it. Strategies include transferring the risk to another party avoiding
the risk, reducing the negative effect of the risk, and accepting some or all of the
consequences of a particular risk. Traditional risk management focuses on risks stemming
from physical or legal causes (e.g. natural disaster or fires, accidents, death and lawsuits).
Financial risk management, on the other hand, focuses on risk that can be managed using
traded financial instruments.

In ideal risk management, a prioritization process is followed whereby the risks


with lower probability of occurring are handled first, and risk with lower probability of
occurrence and lower loss are handled later.

Step in the risk management process establishing the context involves

 Planning the remainder of the process.


 Mapping out the following: the scope of the exercise, the identity and objectives of
stakeholders and the basis upon which risks will be evaluated.
 Defining a framework for the process and an agenda for the Identification.
 Developing an analysis of risk involved in the process.

2.2.1 Risk Identification:


After establishing the context, the next step in the process of managing risk is to
identify potential risks. Risks are about events that, when triggered, cause problems.
Hence, risk identification can start with the source of problems, or with the problem
itself.

In this project there can be following risks:


The order risk is associated with the software. If in the software the wrong user is
authorized by mistake then he may do changes that cause the system in dangerous mode.
There can be risk of natural threats.

2.2.2 Risk Analysis:


Once risks have been identified, they must then be assessed as to their potential
severity of loss and to the probability of occurrence. Regardless of the prevention
techniques employed, possible threats that could arise inside and outside the organization
need to be assessed. Regardless of the type of threat, the goals of the business recovery
planning are to ensure the safety of customers, employees and other personal during the
following a disaster.
The relative probability of a disaster occurring should be determined. Here by the
first risk can occur because of the less of communication with all branches of Apollo for
requirement fulfillment. For example, the company may not have interacted with the
branch of Apollo in U.S.A. and that branch needs some additional functionality of the
software.
If by mistake any person threat Administrator password then he can change the
data in software and can leak information. Same thing occurs if the wrong user is
authorized. The software may be in problem by natural threat e.g. internal flooding,
External flooding, internal fire, external fire etc.

2.2.3 Disaster Prevention:


Because a goal of business recovery planning is to ensure the safety of personnel
and assets during the following a disaster, a critical aspect of the risk analysis process is
to identify the preparedness and preventive measures in place at any point in time. Once
the potential areas of high exposure to the organization are identify, additional
preventative measures can be considered for implementation.
Disaster prevention and preparedness begins at the top of organization. The
attitude of senior management toward security and prevention should permeate the entire
organization. Therefore, management’s support of disaster planning can focus attention
on good security and prevention techniques and better prepare the organization for
unwelcome and unwanted.
Disaster prevention techniques include two categories
 Procedural prevention
 Physical prevention

Procedural prevention relates to activities performed on a day-to-day, month-to-


month, or annual basis, relating to security and recovery. Procedural prevention begins
with assigning responsibility for overall security of the organization to an individual with
adequate competence and authority to meet the challenges. The objective of procedural
prevention is to define activities necessary to prevent various types of disasters and
ensure that these activities are performed regularly.

Physical prevention and preparedness for disaster beings when a site is constructed.
It includes special requirement for building construction, as well as fire protection for
various equipment components. Special considerations include: computer area, fire
detection and extinguishing system, records protection, air conditioning, heating, and
ventilation, electrical supply and UPS system, emergency procedures, vault storage
area(s), archival systems.
2.2.4 Risk Planning:
Once risks have been identified and assessed, all techniques to manage the risk
fall into one or more of these four major categories:
 Tolerate (retention)
 Treat (mitigation)
 Terminate (elimination)
 Transfer (buying insure)

Ideal use of these strategies may not be possible. Some of them may involve tread-offs
that are not acceptable to the organization or a person making the risk management
decisions.

2.2.5 Risk avoidance:


Includes not performing an activity that could carry risk. An example would be
not buying a property or business in order to not take on the liability that comes with it.
Another would be not flying in order to not to take the risk that the airplanes was to be
hijacked. Avoidance may seem the answer to all risk, but avoiding risk also means losing
out on the potential gain that accepting (retaining) the risk may have allowed, not
entering a business to avoid the risk of loss also avoid the possibility of earning profits.

2.2.6 Risk reduction:


Involves methods that reduce the severity of the loss. Examples include sprinklers
designed to put out a fire to reduce the risk of loss by fire. This method may cause a
greater loss by water damage and therefore may not be suitable. Hal on fire suppression
systems may mitigate that risk, but the cost may be prohibitive as a strategy. Modern
software development methodologies reduce risk by developing and delivering software
incrementally. Early methodologies suffered from the fact that they only delivered
software in the final phase of development; any problems encountered in earlier phases
meant costly rework and often jeopardized the whole project. By developing in iteration,
software project can limit effort wasted to a single iteration. A current trend in software
development, spearheaded by the extreme programming community, is to reduce the size
of iteration to the smallest size possible, sometimes as little as one week is allocated to an
iteration.
3 . - System Analysis

1.2 Objective
A key objective of this system is that it consolidates the data in one central
location. This will enable easy management of all information and ensure data integrity
across the entire breadth of the system. The online order management system will
provide such a facility for ordering any product so that he can easily get the product and
also can inquiry online. And it is also very useful to customers because it saves their
time and money.
 To shopping via Internet and online.
 Customer can see all the items which available in the shop. And get the full detail
information about the particular product.
 Customer has no need to gone for a shopping in outside the home.
 It is save the time of the customer.
 Customer can also pay for the purchased Product.
 To provide facility for if product not found then give detail of this product to admin.
Admin best try for provide that product.
The main objective of the project is to create a system that allows users to order the
product based on name of that product. The selected products are displayed in a tabular
format and the user can order their products online through credit card Payment.

1.3 Current Scenario


Currently the system is static so the customer can just see the product online but
they can’t order it. Customer has to do it manually and payment is also manually done.
So we are trying to make it dynamic and we will replace the current ordering system to
the latest technology.
Drawback of current system
Since the ordering of the products is done offline currently it is time consuming.
Customer has to pay somewhat more also.
1.4 Proposed solution
The system will be made such that the customer can order the product online and
payment of that can also be done online through credit card, visa card etc. So the new
system will save time and money of the customer.
1.5 Preliminary Analysis
1.1.1 Scope
 Due to Internet access customers uses Internet more and more for their shopping
needs. They also save time and money by doing so, and for more of their work
related activity.
 This system should provide facility to register online for online ordering.
 The system should provide the facility for inquiry if the customer has any query.
 The system should provide facility for online payment.
 This System should be able to generate customer related report.

1.1.2 Feasibility Study


A feasibility study is carried out to select the best system that meets performance
requirements. A feasibility study is designed to provide an over view of the primary
issues related to a business idea. The purpose is to identify any “make or break” issues
that would prevent your business from being successful in the market place. In other
words, a feasibility study determines whether the ideas make sense.

Feasibility study provides a lot of information necessary for the business plan. For
example a good market is necessary in order to determine the project’s feasibility. This
information provides the basis for the market section of the business plan.

Technical Feasibility

The system will be hosted on the internet so company need internet connection in
that organization, as well as they need MS access to store the data related to products and
customers.

System can be accessed by any platform no concern with open source community
or Microsoft Technology, only thing needed is that .Net Framework must be installed at
application server. I am able to complete the project within specified time.

This system can be easily supported by the hardware and software requirements
of any system. The system can also produce its required output.

The proposed system must provide adequate responses to inquires, regardless of


the number or locations of the users. There must be technical guarantees of accuracy,
reliability, ease of access, and data security.

Economical Feasibility:
Economical feasibility addresses to the following issues:

software resource requirement of the proposed system is .NET Framework 2.0


and MS Access that are already owned by the organization and do not require additional
Investment.
For declaring that the system is economically feasible, the benefits obtain from
the system has to be related against the cost incurred to actually develop the system
because the software which are used here is already owned by the company. It needs the
server which can run this system which is already company has.
The hardware requirement of the system is at least a PC for an administrator to
handle the site from admin panel. The development cost of the project is not much
higher.

Behavioral Feasibility:

Proposed system will behave according to the requirement made or not.


Responses time of the system must be noticed because it is a web based system whether it
takes too much time to response or give quick response or response in the specific period
of time this consideration is most important. Time consuming processes are possible to
run on this environment or not it is also important.

Operational Feasibility:

The proposed system will meet the operational requirements like system
Performance, accessibility of information, client acceptance and efficient solutions to the
queries of the user.

If user has some basic knowledge of Internet, user can operate this application easily.
It provides easy user interface.
Operational feasibility has been considered from the user’s point of view. This
application once deployed, can run easily without any maintenance at this point of time.
After the inclusion of database in future, the database might need some clean up after
some period of time. If the database size becomes large, then it might need some changes
in handling of the application and might require some optimization so that application
runs faster and retrieves data faster.

1.6 System Requirements


Hardware Configuration:
 Server Configuration:
Standard Pentium series processor.
Minimum 4 MB RAM.
HDD storage capacity of 360GB with 5400 rpm or more.

 Client Configuration:
Any computer system with normal speed.
Internet Connectivity

Software Requirements:
 Server Software:
Visual Studio .Net 2005 (Frame work 2.0)
Windows 2000 or higher OS.
 Client Software:
VGA or higher resolution monitor,
IE 6.0+,Fire fox 2.0+, Flash.

 System Requirement Study:


The requirements can be classified as below.

1) Functional requirements.
2) Non-functional requirements.

 Functional Requirements:

 DATABASE FUNCTION
1) Inserting the product and customer information.
2) Retrieval of the stored data according to the user needs.
3) Delete of stored information of outdated products which are out of market and
customer needs.
4) Updating the stored information according to the changes in products change and
customer information.

 SYSTEM FUNCTIONS
Main features of the system are as follows.
1) To provide the facility to register a new customer.
2) To provide the facility to customer to add product to cart, remove product from cart,
and also to provide the facility to calculate total price.
3) To provide the facility to conform order and shipping.
4) To provide facility to customer to see account, edit account; edit credit card detail,
change password.
5) To provide facility to administrator to add customer, add category, add product, edit
bill info, edit credit card info, View daily order, edit ship info.
6) To provide the facility to customer for the inquiry of product.

 Non Functional Requirements:

 Efficiency
The system must provide easy and fast access without consuming time and
resources.

 Reliability
User should never be surprised by the behavior of the system and it should also
provide meaningful feedback when occur and provide context sensitive user help facility
so that user can recover from the errors. The system should be available whenever user
demanding for the service.

 Portability
The system must be platform independent, network independent, and hardware
independent. For example for running the system not any extra hardware is required.

 Constraints:
 Payment through e-check/DD needs gateway services as of high cost.
 In credit card validation, all the visa card, master card and American express card
provided primary level validation but secondary level validation is of high cost.
 The user has to agree with the policies of the retailer.
 The Customer must have some ID like passport, Social security number, voting card,
PAN card etc.
There is wide use of images low range of RAM is little inconvenient to make it faster. To
get result very fast and appropriate it needs to have high speed of RAM.

4 .- Technology Used
 Introduction to .NET

Visual Studio .NET is a complete set of development tools for building ASP Web
applications, XML Web services, desktop applications, and mobile applications. Visual
Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same integrated development
environment (IDE), which allows them to share tools and facilitates in the creation of mixed-
language solutions. In addition, these languages leverage the functionality of the .NET
Framework, which provides access to key technologies that simplify the development of ASP
Web applications and XML Web services.

Clients Applications

Web Form Web Service

.NET Framework

Windows

The Internal .NET Third-Party .NET Enterprise


Web Service Foundation Web Services Servers
Web Services
The .NET Framework is an integral Windows component that supports building and
running the next generation of applications and XML Web services. The .NET Framework is
designed to fulfill the following objectives:

 To provide a consistent object-oriented programming environment whether object code is


stored and executed locally, executed locally but Internet-distributed, or executed
remotely.
 To provide a code-execution environment that minimizes software deployment and
versioning conflicts.
 To provide a code-execution environment that promotes safe execution of code, including
code created by an unknown or semi-trusted third party.
 To provide a code-execution environment that eliminates the performance problems of
scripted or interpreted environments.
 To make the developer experience consistent across widely varying types of applications,
such as Windows-based applications and Web-based applications.
 To build all communication on industry standards to ensure that code based on the .NET
Framework can integrate with any other code.

The .NET Framework has two main components: the common language runtime and the
.NET Framework class library. The common language runtime is the foundation of the .NET
Framework. You can think of the runtime as an agent that manages code at execution time,
providing core services such as memory management, thread management, and remoting, while
also enforcing strict type safety and other forms of code accuracy that promote security and
robustness. In fact, the concept of code management is a fundamental principle of the runtime.
Code that targets the runtime is known as managed code, while code that does not target the
runtime is known as unmanaged code. The class library, the other main component of the .NET
Framework, is a comprehensive, object-oriented collection of reusable types that you can use to
develop applications ranging from traditional command-line or graphical user interface (GUI)
applications to applications based on the latest innovations provided by ASP.NET, such as Web
Forms and XML Web services.

The .NET Framework can be hosted by unmanaged components that load the common
language runtime into their processes and initiate the execution of managed code, thereby
creating a software environment that can exploit both managed and unmanaged features. The
.NET Framework not only provides several runtime hosts, but also supports the development of
third-party runtime hosts.

For example, ASP.NET hosts the runtime to provide a scalable, server-side environment
for managed code. ASP.NET works directly with the runtime to enable ASP.NET applications
and XML Web services, both of which are discussed later in this topic.
Internet Explorer is an example of an unmanaged application that hosts the runtime (in
the form of a MIME type extension). Using Internet Explorer to host the runtime enables you to
embed managed components or Windows Forms controls in HTML documents. Hosting the
runtime in this way makes managed mobile code (similar to Microsoft® ActiveX® controls)
possible, but with significant improvements that only managed code can offer, such as semi-
trusted execution and isolated file storage.

The following illustration shows the relationship of the common language runtime and
the class library to your applications and to the overall system. The illustration also shows how
managed code operates within a larger architecture.

 .NET Framework in context

The following sections describe the main components and features of the .NET
Framework in greater detail.
 Features of the Common Language Runtime (CLR)

The common language runtime manages memory, thread execution, code execution, code
safety verification, compilation, and other system services. These features are intrinsic to the
managed code that runs on the common language runtime.

With regards to security, managed components are awarded varying degrees of trust,
depending on a number of factors that include their origin (such as the Internet, enterprise
network, or local computer). This means that a managed component might or might not be able
to perform file-access operations, registry-access operations, or other sensitive functions, even if
it is being used in the same active application.

The runtime enforces code access security. For example, users can trust that an
executable embedded in a Web page can play an animation on screen or sing a song, but cannot
access their personal data, file system, or network. The security features of the runtime thus
enable legitimate Internet-deployed software to be exceptionally feature rich.

The runtime also enforces code robustness by implementing a strict type-and-code-


verification infrastructure called the common type system (CTS). The CTS ensures that all
managed code is self-describing. The various Microsoft and third-party language compilers
generate managed code that conforms to the CTS. This means that managed code can consume
other managed types and instances, while strictly enforcing type fidelity and type safety.

In addition, the managed environment of the runtime eliminates many common software
issues. For example, the runtime automatically handles object layout and manages references to
objects, releasing them when they are no longer being used. This automatic memory
management resolves the two most common application errors, memory leaks and invalid
memory references.

The runtime also accelerates developer productivity. For example, programmers can
write applications in their development language of choice, yet take full advantage of the
runtime, the class library, and components written in other languages by other developers. Any
compiler vendor who chooses to target the runtime can do so. Language compilers that target the
.NET Framework make the features of the .NET Framework available to existing code written in
that language, greatly easing the migration process for existing applications.

While the runtime is designed for the software of the future, it also supports software of
today and yesterday. Interoperability between managed and unmanaged code enables developers
to continue to use necessary COM components and DLLs.

The runtime is designed to enhance performance. Although the common language


runtime provides many standard runtime services, managed code is never interpreted. A feature
called just-in-time (JIT) compiling enables all managed code to run in the native machine
language of the system on which it is executing. Meanwhile, the memory manager removes the
possibilities of fragmented memory and increases memory locality-of-reference to further
increase performance.

Finally, the runtime can be hosted by high-performance, server-side applications, such as


Microsoft® SQL Server™ and Internet Information Services (IIS). This infrastructure enables
you to use managed code to write your business logic, while still enjoying the superior
performance of the industry's best enterprise servers that support runtime hosting.

 Compilation Process of .Net Technology

Source Code in Source Code in Source Code in


VB 2005 C# Another .NetLanguage

VB 2005 Compiler C# Compiler Appropriate


(vbc.exe) (csc.exe) Compiler

DLL or EXE file in IL


(intermediate
language code)

JIT (just-in-time
compiler)

Native Machine
Code

Execute

Figure 2 Language Compilation in .NET


 .NET Framework Class Library

The .NET Framework class library is a collection of reusable types that tightly integrate
with the common language runtime. The class library is object oriented, providing types from
which your own managed code can derive functionality. This not only makes the .NET
Framework types easy to use, but also reduces the time associated with learning new features of
the .NET Framework. In addition, third-party components can integrate seamlessly with classes
in the .NET Framework.

For example, the .NET Framework collection classes implement a set of interfaces that
you can use to develop your own collection classes. Your collection classes will blend
seamlessly with the classes in the .NET Framework.

As you would expect from an object-oriented class library, the .NET Framework types
enable you to accomplish a range of common programming tasks, including tasks such as string
management, data collection, database connectivity, and file access. In addition to these common
tasks, the class library includes types that support a variety of specialized development scenarios.
For example, you can use the .NET Framework to develop the following types of applications
and services:

 Console applications.
 Windows GUI applications (Windows Forms).
 ASP.NET applications.
 XML Web services.
 Windows services.

For example, the Windows Forms classes are a comprehensive set of reusable types that
vastly simplify Windows GUI development. If you write an ASP.NET Web Form application,
you can use the Web Forms classes.

 Accessing data with ADO.NET

ADO.NET provides consistent access to data sources such as Microsoft SQL Server, as
well as data sources exposed through OLE DB and XML. Data-sharing consumer applications
can use ADO.NET to connect to these data sources and retrieve, manipulate, and update data.

ADO.NET cleanly factors data access from data manipulation into discrete components
that can be used separately or in tandem. ADO.NET includes .NET Framework data providers
for connecting to a database, executing commands, and retrieving results. Those results are either
processed directly, or placed in an ADO.NET Dataset object in order to be exposed to the user
in an ad-hoc manner, combined with data from multiple sources, or remote between tiers. The
ADO.NET Dataset object can also be used independently of a .NET Framework data provider to
manage data local to the application or sourced from XML.

The ADO.NET classes are found in System.Data.dll, and are integrated with the XML
classes found in System.Xml.dll. When compiling code that uses the System.Data namespace,
reference both System.Data.dll and System.Xml.dll.

ADO.NET provides functionality to developers writing managed code similar to the


functionality provided to native COM developers by ADO.

 ADO.NET Components

The ADO.NET components have been designed to factor data access from data
manipulation. There are two central components of ADO.NET that accomplish this: the Dataset,
and the .NET Framework data provider, which is a set of components including the Connection,
Command, DataReader, and DataAdapter objects.

The ADO.NET Dataset is the core component of the disconnected architecture of


ADO.NET. The Dataset is explicitly designed for data access independent of any data source.
As a result it can be used with multiple and differing data sources, used with XML data, or used
to manage data local to the application. The Dataset contains a collection of one or more
DataTable objects made up of rows and columns of data, as well as primary key, foreign key,
constraint, and relation information about the data in the DataTable objects.

The other core element of the ADO.NET architecture is the .NET Framework data
provider, whose components is explicitly designed for data manipulation and fast, forward-only,
read-only access to data. The Connection object provides connectivity to a data source. The
Command object enables access to database commands to return data, modify data, run stored
procedures, and send or retrieve parameter information. The DataReader provides a high-
performance stream of data from the data source. Finally, the DataAdapter provides the bridge
between the DataSet object and the data source. The DataAdapter uses Command objects to
execute SQL commands at the data source to both load the DataSet with data, and reconcile
changes made to the data in the DataSet back to the data source.

You can write .NET Framework data providers for any data source. The .NET
Framework ships with two .NET Framework data providers: the .NET Framework Data Provider
for SQL Server and the .NET Framework Data Provider for OLE DB.

The following diagram illustrates the components of ADO.NET architecture.ADO.NET


architecture
 Platform Invoke (Windows API)

Platform invoke relies on metadata to locate exported functions and marshal their
arguments at run time. The following illustration shows this process.

A platform invoke call to an unmanaged DLL function

When platform invoke calls an unmanaged function, it performs the following sequence
of actions:

1. Locates the DLL containing the function.


2. Loads the DLL into memory.
3. Locates the address of the function in memory and pushes its arguments onto the stack,
marshaling data as required.

 Why we Use C#.Net:


 It supports Client/Server Architecture. C#.Net also provides Database Objects like
ADO.Net which is very useful for making Client/server application. It gives more
facility like disconnected database structure with classes like Data Adapter, Data
connection.

 C#.Net is object oriented language which is providing facility of Inheritance,


constructors, destructors, multithreading etc. C#.Net provides many data types which
are giving flexibility in programming. It also provides the Crystal Report support to
make report this is the advantage of C#.Net. In our application reports are very
important part with graphical representation.

 The most important feature of C#.Net is disconnected database structure. That


features is very much useful in our application and it also give speed and accuracy to
the client/server model.

 Features of C#.Net:

 Inheritance: C Sharp .Net supports inheritance by allowing you to define classes that
serve as the basis for derived classes. Derived classes inherit and can extend the
properties and methods of the base class. They can also override inherited methods
with new implementations. All classes created with Visual Basic .Net are inheritable
by default. Because the forms you design are really classes, you can use inheritance to
define new forms based on existing ones.

 Exception Handling: C Sharp .Net supports structured exception handling, using and
enhanced version of the Try…Catch…Finally syntax supported by other languages
such as c++. Structured exception handling combines a modern control structure with
exceptions, protected blocks of code and filters. Structured exception handling makes
it easy to create and maintain programs with robust comprehensive error handlers.

 Overloading: Overloading is the ability to define properties, methods, or procedures


that have the same name but use different data types. Overloaded procedures allow
you to provide as many implementations as necessary to handle different kinds of
data, while giving the appearance of a single, versatile procedure.

 Overriding Properties and Methods: The overrides keyword allows derived objects
to override characteristics inherited from Parent objects. Overridden members have
the same arguments as the members inherited form the base class, but different
Implementations. A member’s new implementation can call the original
implementation in the parent class by preceding the member name with My Base.
 Constructors and Destructors: Constructors are procedures that control
initialization of new instances of a class. Conversely, destructors are methods that
free system resources when a class leaves scope or is set to nothing. C Sharp .Net
supports constructors and destructors using the sub new and sub finalize procedures.

 Data Types: C Sharp .Net introduces three new data types. The char data type is and
unsigned 16-bit quantity used to store Unicode characters. It is equivalent to the .Net
Framework System. Char data type.

 Interfaces: Interfaces describe the properties and methods of classes, but unlike
classes, do not provide implementations. The interface statement allows you to
declare interfaces, while the implements statement lets you write code that puts the
items described in the interface into practice.

 Shared Members: Shared members are properties, procedures, and fields that are
shared by all instances of a class. Shared data members are useful when multiple by
objects need to use information that is common to all. Shared class methods can be
used without first creating and object form a class.

 References: References allow you to use objects defined in other assemblies. In C


Sharp .Net, references point to assemblies instead of type libraries.

 Namespaces: Namespaces prevent naming conflicts by organizing classes, interfaces,


and methods into hierarchies.

 Assemblies: Assemblies replace and extend the capabilities of type libraries by,
describing all the required files for a particular component or application. An
assembly can contain one or more namespaces.

 Attributes: Attributes enable you to provide additional information about program


elements. For example, you can use an attribute to specify which methods in a class
should be exposed when the class is used as a XML Web service.

 Multithreading: C Sharp .Net allows you to write applications that can perform
multiple tasks independently. A task that has the potential of holding up other tasks
can execute on a separate thread, a process known as multithreading. By causing
complicated tasks to run on threads that are separate from your user inter face,
multithreading makes your applications more responsive to user input.

 Bit Shift Operators: C Sharp .Net now supports arithmetic left and right shift
operations on integral data types. Arithmetic shifts are not circulars, which means the
bits shifted off one end of the result are not reintroduced at the other and. The
corresponding assignment operators are provided as well.

 MS SQL SERVER 2005 Express Edition

 Overview

Microsoft SQL Server 2005 Express Edition extends the performance, reliability,
quality, and ease-of-use of Microsoft SQL Server version 7.0. Microsoft SQL Server
2005 Express Edition includes several new features that make it an excellent database
platform for large-scale online transactional processing (OLTP), data warehousing, and e-
commerce applications. The OLAP Services feature available in SQL Server version 7.0
is now called SQL Server 2005 Express Edition Analysis Services. The term OLAP
Services has been replaced with the term Analysis Services. Analysis Services also
includes a new data mining component

Microsoft SQL Server 2005 Express Edition is a set of components that work
together to meet the data storage and analysis needs of the largest Web sites and
enterprise data processing systems. The topics in SQL Server Architecture describe how
the various components work together to manage data effectively.

 Internet Integration

The SQL Server 2005 Express Edition database engine includes integrated XML
support. It also has the scalability, availability, and security features required to operate
as the data storage component of the largest Web sites. The SQL Server2005 Express
Edition programming model is integrated with the Windows DNA architecture for
developing Web applications, and SQL Server 2005 Express Edition supports features
such as English Query and the Microsoft Search Service to incorporate user-friendly
queries and powerful search capabilities in Web applications.

 Scalability and Availability

The same database engine can be used across platforms ranging from laptop
computers running Microsoft Windows 98 through large, multiprocessor servers running
Microsoft Windows 2000 Data Center Edition. SQL Server 2005 Express Edition
supports features such as federated servers, indexed views, and large memory support
that allow it to scale to the performance levels required by the largest Web sites.

 Enterprise-Level Database Features

The SQL Server 2005 Express Edition relational database engine supports the
features required to support demanding data processing environments. The database
engine protects data integrity while minimizing the overhead of managing thousands of
users concurrently modifying the database.

SQL Server 2005 Express Edition includes a set of administrative and


development tools that improve upon the process of installing, deploying, managing, and
using SQL Server across several sites. SQL Server 2000 also supports a standards-based
programming model integrated with the Windows DNA, making the use of SQL Server
databases.

 Data warehousing

SQL Server 2005 Express Edition includes tools for extracting and analyzing
summary data for online analytical processing. SQL Server also includes tools for
visually designing databases and analyzing data using English-based questions.

 Database Architecture

Microsoft SQL Server 2005 Express Edition data is stored in databases. The data
in a database is organized into the logical components visible to users. A database is also
physically implemented as two or more files on disk.

By using a database, it is possible to work primarily with the logical components


such as tables, views, procedures, and users. The physical implementation of files is
largely transparent. Typically, only the database administrator needs to work with the
physical implementation.

Each instance of SQL Server has four system databases (master, model, tempdb,
and msdb) and one or more user databases. Some organizations have only one user
database, containing all the data for their organization. Some organizations have different
databases for each group in their organization, and sometimes a database used by a single
application.

It is not necessary to run multiple copies of the SQL Server database engine to
allow multiple users to access the databases on a server. An instance of the SQL Server
Standard or Enterprise Edition is capable of handling thousands of users working in
multiple databases at the same time.
When connecting to an instance of SQL Server, the connection is associated with
a particular database on the server. This database is called the current database. The user
is usually connected to a database defined as the default database by the system
administrator, although its uses connection options in the database APIs to specify
another database.

SQL Server 2005 Express Edition allows detaching databases from an instance of
SQL Server, then reattaching them to another instance, or even attaching the database
back to the same instance. If there is SQL Server database file, it is possible to attach that
database file with a specific database name.

 Relational Database components:

The database component of Microsoft SQL Server 2005 Express Edition is a


Structured Query Language (SQL)–based, scalable, relational database with integrated
Extensible Markup Language (XML) support for Internet applications. Each of the
following terms describes a fundamental part of the architecture of the SQL Server2005
Express Edition database component:

 Database

A database is similar to a data file in that it is a storage place for data. Like a data
file, a database does not present information directly to a user; the user runs an
application that accesses data from the database and presents it to the user in an
understandable format. Database systems are more powerful than data files in that data is
more highly organized.

In a well-designed database, there are no duplicate pieces of data that the user or
application must update at the same time. Related pieces of data are grouped together in a
single structure or record, and relationships can be defined between these structures and
records.

 Relational Database

Although there are different ways to organize data in a database, relational


databases are one of the most effective. Relational database systems are an application of
mathematical set theory to the problem of effectively organizing data. In a relational
database, data is collected into tables (called relations in relational theory).
 Scalable

SQL Server 2005 Express Edition supports having a wide range of users access it
at the same time. An instance of SQL Server 2005 Express Edition includes the files that
make up a set of databases and a copy of the DBMS software. Applications running on
separate computers use a SQL Server 2005 Express Edition communications component
to transmit commands over a network to the SQL Server 2005 Express Edition instance.
When an application connects to an instance of SQL Server 2005 Express Edition, it can
reference any of the databases in that instance that the user is authorized to access. The
communication component also allows communication between an instance of SQL
Server 2005 Express Edition and an application running on the same computer.

 Structured Query Language

To work with data in a database, the user have to use a set of commands and
statements (language) defined by the DBMS software. Several different languages can be
used with relational databases; the most common is SQL. The American National
Standards Institute (ANSI) and the International Standards Organization (ISO) define
software standards.

 Extensible Markup Language

XML is the emerging Internet standard for data. XML is a set of tags that can be
used to define the structure of a hypertext document. XML documents can be easily
processed by the Hypertext Markup Language, which is the most important language for
displaying Web pages.

 Database Design Considerations

Designing a database requires an understanding of both the business functions


you want to model and the database concepts and features used to represent those
business functions.

It is important to accurately design a database to model the business because it


can be time consuming to change the design of a database significantly once
implemented. A well-designed database also performs better.

 Database Architecture

Microsoft® SQL Server™ 2005 Express Edition data is stored in databases. The data in a
database is organized into the logical components visible to users. A database is also physically
implemented as two or more files on disk.
When using a database, you work primarily with the logical components such as tables,
views, procedures, and users. The physical implementation of files is largely transparent.
Typically, only the database administrator needs to work with the physical implementation.

Each instance of SQL Server has four system databases (master, model, tempdb, and
msdb) and one or more user databases. Some organizations have only one user database,
containing all the data for their organization. Some organizations have different databases for
each group in their organization, and sometimes a database used by a single application. For
example, an organization could have one database for sales, one for payroll, one for a document
management application, and so on. Sometimes an application uses only one database; other
applications may access several databases.

It is not necessary to run multiple copies of the SQL Server database engine to allow
multiple users to access the databases on a server. An instance of the SQL Server Standard or
Enterprise Edition is capable of handling thousands of users working in multiple databases at the
same time. Each instance of SQL Server makes all databases in the instance available to all users
that connect to the instance, subject to the defined security permissions.

When connecting to an instance of SQL Server, your connection is associated with a


particular database on the server. This database is called the current database. You are usually
connected to a database defined as your default database by the system administrator, although
you can use connection options in the database APIs to specify another database. You can switch
from one database to another using either the Transact-SQL USE database_name statement, or
an API function that changes your current database context.

SQL Server 2000 allows you to detach databases from an instance of SQL Server, then
reattach them to another instance, or even attach the database back to the same instance. If you
have a SQL Server database file, you can tell SQL Server when you connect to attach that
database file with a specific database name.
 MS Visio 2003
Microsoft Visio is a Graphical tool used for the Flow chart, DFD and ER. It contains all
the shapes for the Flow chart, DFD, ER etc. that a user can drag and drop onto the drawing page
to create a drawing, without having to draw anything manually. Shapes can have online Help to
assist a user in using them correctly.

The following visual solutions are included:

 Block Diagram Includes the Basic, Block, and Block with Perspective templates. These
are useful for showing all types of relationships and hierarchies and provide the basic
arsenal of information graphics tools.
 Brainstorming Includes the new Brainstorming diagram that allows you to capture,
arrange, and expand ideas generated by a group or yourself. These diagrams display
hierarchical relationships and allow exportation to Word for a more linear view, or to an
Extensible Markup Language (XML) file for reuse elsewhere.
 Business Process The new Business Process category provides a collection of templates
you can use for specific business process documentation efforts, including Six Sigma,
SAP, and International Organization for Standardization (ISO).
 Building Plan Provides a quick way to design accurate, to-scale office and furniture
layouts.
 Charts and Graph Formerly Forms and Charts. Includes templates for designing
business forms; creating quick pie, line, and bar charts and graphs; and creating
marketing diagrams.
 Flowchart Includes templates for creating audit diagrams, basic flowcharts, cause and
effect diagrams, cross-functional flowcharts, mind mapping diagrams, total quality
management (TQM) charts, and workflow diagrams.
 Map Includes templates for creating simple street maps and attractive 3-D maps.
 Network Includes shapes designed to resemble common network topology and devices.
Useful for planning and documenting small to medium-sized networks.
 Organization Chart Includes intelligent shapes that “know” their position in an
organization, so that reporting structures stay in place. You can even use the Organization
Chart Wizard to automatically build a chart from a spreadsheet or database without
having to draw a thing.
 Project Schedule Includes templates for creating PERT charts, Gantt charts, timelines,
and calendars, so you can keep your projects on track.
 Building Plan Includes templates for creating plan-view drawings of corporate offices
and industrial manufacturing facilities. Designed for space planners and building
engineers, this solution lets you create floor plans, home plans, plant layouts, reflected
ceiling plans, site plans, and the building services schematics that support them.
 Database Includes templates for communicating database designs using multiple
notations intended for database professionals. With the Database Model Diagram
template, you can even reverse engineer and get support for leading client/server and
desktop databases.
 Electrical Engineering Includes a variety of templates used by electrical engineers for
creating electrical and electronic schematics, wiring diagrams, and logic diagrams.
 Mechanical Engineering Includes templates for diagramming fluid power control
systems and hydraulic or pneumatic circuits as well as part and assembly drawings.
 Network Includes further templates for creating high-level, logical diagrams and for
designing local area networks (LANs), wide area networks, wiring closets, server rooms,
and telecommunications structures. In addition, you can create diagrams of Microsoft
Active Directory, Novell Directory Services (NDS), and other LDAP-based directory
structures.
 Process Engineering Includes templates for assembling detailed piping and
instrumentation diagrams (P&IDs) and process flow diagrams (PFDs) used by many
chemical and industrial engineers.
 Software Includes templates for major object-oriented software notations, including the
full Unified Modeling Language (UML) 1.2 notation. In addition, you can diagram data
flows, Windows user interfaces, COM and OLE objects, and more.
 Web Diagram Includes templates for automatically mapping Web sites and conceptual
shapes for planning new designs
5. - System Design

Use Case Diagrams:

Online Shopping Website

«uses» Sign UP & Order

Sign In & Order


User

«uses»

«uses»
Manage Account

«uses»
Customer

Maintain Site from Administrator


Backhand

Use Case Diagram for Login

User Account Use Case:


User Account Use Case

«extends»
Check Account
Change Password
Status

«uses»
«extends»
Create Account Change Password

«uses»
«uses» Add Product to Cart

«extends»
Customer

«extends»
«uses» Manage Shoping Select Shipping

«extends»

«uses»

«uses» Remove Product


from Cart
User

Inquiry

Payment

User Account Use Case Diagram

Administrator Account Use Case:


Administrator Account Use Case

Add Category /
SubCategory

«extends»

Edit / Update
«extends»
Category / SubCategory
Manage Category /
SubCategory «extends»

Find Category /
«extends»
SubCategory

Delete Category /
SubCategory

«uses»

Add Product

«extends»

Edit / Update
«extends»
Product

«uses» Manage Product


«extends»

«extends» Find Product

Administrator «uses»
Delete Product

«uses»

«extends»
Manage Shipping
Register Order
«uses» Charge

Add Offer to
«extends» Product

Manage Category «extends»

Remove Offer to
Product

Manage Payment

3.2 Use Case Description:


Create Account Use Case Description:

Create Account :

Description: To create an account so that the customer can order the products
online using system.

Actor(s) : User

Pre-Condition : None.

Post-Condition 1. The Account is Create Successfully.


:

Main Success 1. User goes to the Account creation page and creates account
Scenario : over there.
2. User enters specified details.
3. System validates the information.
4. System creates a User account with above details.
5. System displays success message.
Data Captured: 2a. Create Account details

A. Common Details:
1. User Name: User name with which the new account is
created.
2. Login Id: Login Id using which a customer can access his
account and also use the other functionalities of the system.
3. Address: Address to which shipping can be done whenever
customer does the order.
4. Email Id: Email Id of the customer to which mail can be sent
whenever required.
5. Phone No: Customer’s contact number.

Exceptional 3a. System fails to validate the information


Flow(s) :
1. System rejects the user's request by displaying an
appropriate error message in case of Invalid input.
2. The user may retry entering the system create
account page or may cancel.
Alternate None
Flow(s):

External None
System
Dependencies:

Open Issue(s): None

Non-Functional None
Requirement(s):

Manage Account Use Case Description:

Manage Account

Description: A customer can check his account status. He can also change his
password.

Actor(s) : Customer

Pre-Condition : Customer is registered with this system.

Post-Condition 1 The Account is updated successfully.


: 2. Customer will be provided it’s new password and also the
status of his account.
Main Success 2. The Customer goes to the manage account page in the
Scenario : system.
3. Customer enters specified details.
4. System validates the information.
5. System Updates account with the new details.
6. System displays success message.
Data Captured: 2a. Customer account details.

B. Common Details :
1. Customer ID: Valid Customer ID to access the account.
2. Password: Password from the Customer so that he can access
to his account also can update his account.
3. Customer Name: Specifies the name to be used to create the
account with this name.
4. Customer Address: Address of the Customer Where the
shipping of the products can be done.
5. Mobile No: To Contact the customer.
Exceptional 3a. System fails to validate the information
Flow(s) :
1. System rejects the customer's request by
displaying an appropriate error message in case
of Invalid input.
2. The Customer may retry entering the system
again.
Alternate None
Flow(s):

External None
System
Dependencies:

Open Issue(s): None

Non-Functional None
Requirement(s):

Example usage:

Manage Shopping Cart Use Case Description:


Manage Shopping Cart

Description: A customer can add or remove the products he want to order


from the shopping cart.

Actor(s) : Customer

Pre-Condition : Customer is registered with this system.

Post-Condition : 1. Select Shipping Charge.


2. The shopping cart is updated successfully.
3. Customer will be provided his shopping detail and
payment information also .
Main Success 1. The Customer goes to the product page in the system.
Scenario : 2. Customer add or removes product from that page.
3. System updates the shopping cart with new products.
4. System displays the success message.
Data Captured: Common Details :
1. Product Id: The Id of the product which the customer
want to add or remove from the cart.
2. Product Quantity: The Number of one particular product
he want to order.
3. Product Price: The Price of the product to be sold.
4. Product Name: The name of the Product to be sold.
Exceptional Flow(s)
:

Alternate Flow(s): None

External System None


Dependencies:

Open Issue(s): None

Non-Functional
Requirement(s):
None

Payment Use Case Description:


Payment :

Description: A customer do the payment for the products he ordered.

Actor(s) : Customer

Pre-Condition : Customer is registered with this system.

Post-Condition 1. The payment will be done from his credit card


: successfully.
2. Customer will be provided a message of conformation of
payment.
Main Success 1. The Customer goes to the product page in the system.
Scenario : 2. Customer enters specified details.
3. System validates the information.
4. System takes the payment and deducts that much amount
from the credit card account.
5. System displays success message.
Data Captured: 2a. Customer payment details.

Common Details :

Customer credit card Number: Valid credit card number to


do the payment from that account.

Exceptional 3a. System fails to validate the information


Flow(s) :
a. System rejects the customer's request by displaying an
appropriate error message in case of insufficient balance
in his account.
Alternate None
Flow(s):

External None
System
Dependencies:

Open Issue(s): None

Non-Functional
Requirement(s):
None

Manage Products Use Case Description:


Manage Products

Description: A administrator can add new products or remove old products


from the site.

Actor(s) : Administrator

Pre-Condition : Administrator is logged in with this system.

Post-Condition: 1. The product page will be updated successfully.

Main Success 1. The Administrator goes to the update products page in the
Scenario : system.
2. Administrator enters specified details.
3. System validates the information.
4. System Updates the page with the new details.
5. System displays success message.
Data Captured: 2a. Product details.

A. Common Details :
1. Product ID: Product ID of the product to be added or
removed.
2. Product Name: Name of the new Product.
3. Product Price: Price of the new product.
4. Product Image: Image of the new product.
Exceptional Flow(s) : 3a. System fails to validate the information

1. System rejects the Administrator's request by displaying


an appropriate error message in case of Invalid input.
2. The Administrator may retry entering the system again.
Alternate Flow(s): None

External System None


Dependencies:

Open Issue(s): None

Non-Functional None
Requirement(s):

Register Order and Manage Shipping Use Case Description:


Register Order and Manage Shipping:

Description: A administrator can register the order made by the customer


from the site.

Actor(s) : Administrator

Pre-Condition : Administrator is logged in with this system.

Post-Condition: 1. The Order will be taken successfully.

Main Success 2. The Administrator goes to the Order detail page in the
Scenario : system.
3. Administrator takes specified details.
4. Administrator validates the information.
5. Administrator uspdates the customer account with the
new details.
6. System displays success message.
Data Captured: 2a. Order details from customer.

Common Details :
1. Product ID: Product ID of the product to be ordered.
2. Product Name: Name of the Product.
3. Customer Id: Id using which the customer registered with
the system.
4. Customer Address: Address of the customer to which the
shipping can be done.
5. Customer Email Id: Email id of the customer to contact
him through mail.
Exceptional Flow(s) : 3a. System fails to validate the information

a. System rejects the Administrator's request by displaying


an appropriate error message in case of any system
failure.
b. The Administrator may retry entering the system again.
Alternate Flow(s): None

External System None


Dependencies:

Open Issue(s): None

4.3 Activity Diagram:


Activity Diagram For Ordering Process:

Select Product

Add to Shopping Cart

Select Shipping Detail

Return to Catalogue
Main
Land UK Outside
& UK UK

Calculate Any Sub Total Inquiry for Shipping

Continue
Shopping Checkout

Return to Catalogue

Not Already
Registered Registered

Register New Account Login

Process to Payment

Activity Diagram For Payment Process:


Enter Payment / Creadit Card Info.

Enter Shipping Info.

Process To Payment

Payment
Payment Not
Accepted Accepted

Display Payment Confirmation Display Error Information

4.4 Sequence Diagram


Sequence Diagram For Customer Registration:

Online Customer System Check Customer Customer Record

Register Register

Check Duplicate

Match

return

Duplicate Show Error MEssage

Duplicate Show Error MEssage

Generate Customer ID

Register

Create

return
Registration Message

Display Registration Message

Sequence Diagram For Order & Payment Process:


cart item cart payment
customer

Add to cart Add to cart()

cart id

calculate cost()

Save cart()

verify cartid()

verify custid()

save cart msg

Login

checkout user()

Payment card detail

check custid()

check cardid()
payment conformation msg

Manage Category Sequence Diagram


admin category database

Managecategory()
Addcategory()

category Id

category Id

Remove category()

remove category msg

remove category msg


Find category()

category name, Id

category name, Id

Manage Subcategory Sequence Diagram


admin sub category database

Managesubcategory()

Addsubcategory()

subcategory Id

subcategory Id

Removesubcategory()

remove subcategory msg

remove subcategory msg

Findsubcategory()

subcategoryname, Id

subcategoryname, Id

 Manage Products Sequence Diagram


admin product database

ManageProduct()

AddProduct()

product Id

product Id

RemoveProduct()

remove product msg

remove product msg

FindProduct()

product Id, Name

product Id, Name

addoffer()

offer Id

offer Id

removeoffer()

remove offer msg

remove offer msg

4.5 Collaboration Diagram


Collaboration Diagram For Customer Registration:

1.Register 6.Generate
5.Dublicate Customer
Online Customer System Id
Show Error

9 Display Message

2.Check duplicate

Show Error
4.duplicate

7.Register

Check 3.Match
Customer Customer
8.Create Record

Collaboration Diagram For Order & Payment:


4.Ge
t Tota
l

Shopping
System
cart
12.Show Message

6.If the User Login


9.If Pay By Card

5.Get User Detail

10
.Fo
11

rw

3.Add To Cart
.G

ard
et

to
Co

Pa
nfo

yP
rm

al
ati
on
1.View product
Online Customer 2.Fo
r Ea c h
ITEM Product to
7.Retrive Detail
8.If Found Return

Purchase

PayPal

DataBase

4.6 State Chart Diagram


State Chart Diagram For Order Process:

Order Received

Un Processed Order

[Reject] [Accept]
Checked Checked

Rejected Order Accepted Order

[Some items Not [All items are


Avavilable] Avavilable]
Unprocessed processed

All Items Available


New Supply
Pending Order Fullfilled Order

4.7 Class Diagram:


 Data Dictionary
 Table Name : User_Mst (User Master)

Field Name Data Type Constraints Description

UserId Varchar(50) Primary Key Unique User Id (it User for


Login to Control Panel)
Password Varchar(50) Not Null Used for login password
User Name Varchar(100) Allow Null Name of the user /
Administrator
User Address Varchar(max) Allow Null Address of the Administrator /
User.
City Varchar(50) Allow Null City of the Administrator /
User.
State Varchar(50) Allow Null State of the Administrator /
User.
Country Varchar(50) Allow Null Country of the Administrator /
User.
Contact No. Varchar(50) Allow Null Contact No. of the
Administrator / User.
Email Address Varchar(50) Allow Null Email of the Administrator /
User.
Created By Varchar(50) Allow Null Store the name of person who is
created this category.
Created Date Datetime Allow Null Store the date of category is
created.
Modify By Varchar(50) Allow Null Store the name of person who is
modify this category.
Modify Date Datetime Allow Null Store the Date of Category is
modified.

 Table Name : Category_Mst (Category Master)


This table is used to store the different type of category detail. This category is used to
categorize the product.

Field Name Data Type Constraints Description

Category Id int Primary Key Category Identity no.


Category Name Varchar(100) Allow Null Name of the Category
Category Varchar(100) Allow Null Description about the Category
Description
Created By Varchar(50) Allow Null Store the name of person who is
created this category.
Created Date datetime Allow Null Store the date of category is
created.
Modify By Varchar(50) Allow Null Store the name of person who is
modify this category.
Modify Date datetime Allow Null Store the Date of Category is
modified.

 Table Name : Product_Mst (Product Master)

Field Name Data type Constraints Description


Category Id int Reference to Category Identity no.
Category Master
Product Code int Not Null Product Identity No (Auto
Generated).
Product Name Varchar(100) Allow Null Name of the product
Product Price Decimal(18,2) Not Null Price of the Product
Product Image Path Varchar(max) Allow Null Image path of the Product
Image
Show in Home Varchar(10) Allow Null If offer is available in that
particular Product
Created By Varchar(50) Allow Null Store the name of person who is
created this category.
Created Date datetime Allow Null Store the date of category is
created.
Modify BY Varchar(50) Allow Null Store the name of person who is
modify this category.
Modify Date datetime Allow Null Store the Date of Category is
modified.

 Table Name : Customer_Mst (Customer Master)

Field Name Data type Constraints Description


Customer ID Decimal(10,0) Not Null Unique Indentity No of every
Customer (Auto Increment)
Customer Name Varchar(100) Allow Null Name of the customer
Customer Address Varchar(100) Allow Null Address of the customer

Customer City Varchar(50) Allow Null City Name of the Customer


Customer State Varchar(50) Allow Null State name of the Customer is
live.
Customer Country Varchar(100) Allow Null Country name when the
customer is live.
Customer Ph No Decimal(20,0) Allow Null Phone no. of the Customer
Customer Mobile Decimal(20,0) Allow Null Mobile No. of the Customer
No
Customer Fax Decimal (20,0) Allow Null Fax No. of the Customer
Customer Email Varchar(100) Allow Null Email Id of the Customer
Customer Login Id Varchar(50) Primary Key Login Id for the Customer
Login
Customer Password Varchar(50) Not Null Login Password of the
Customer
Created By Varchar(50) Allow Null Store the name of person who is
created this category.
Created Date datetime Allow Null Store the date of category is
created.
Modify BY Varchar(50) Allow Null Store the name of person who is
modify this category.
Modify Date datetime Allow Null Store the Date of Category is
modified.

 Table Name : Product_Image_Detail


Field Name Data type Constraints Description
Image Id int Not Null
Category Id int Reference to Category Identity no.
Category Master
Product Id int Not Null Product Identity No (Auto
Generated).
Product Image Varchar(max) Allow Null Image of the Product Image

Product_ImageCP Varchar(max) Allow Null Image of Product_ImageCP

 Table Name : Page_Mst (Page Master)

This table is used to store the different type of Page detail. This Page is used to categorize
the product.

Field Name Data Type Constraints Description

Page Id int Not Null Page Identity no.


Page Name Varchar(100) Allow Null Name of the Page
Page Description Varchar(max) Allow Null Description about the Page

Created By Varchar(50) Allow Null Store the name of person who is


created this Page.
Created Date datetime Allow Null Store the date of Page is created.

Modify By Varchar(50) Allow Null Store the name of person who is


modify this page.
Modify Date datetime Allow Null Store the Date of page is
modified.

 Table Name : Cart_Mst

Field Name Data type Constraints Description


Card Id Int PK Card Identity no.
Card Date datetime Allow Null Card Date
Customer Id Varchar(50) Not Null Customer Identity No

Cart Total Amount Decimal(18,2) Allow Null Total Amount Of Cart

Cart Additional Decimal(18,2) Allow Null Others Additional Cart Charges


Charge
Cart Shipping Decimal(18,2) Allow Null Shipping Charge of the Cart.
Charge
Cart Remark Varchar(100) Allow Null Remarks of the Cart.

Created By Varchar(50) Allow Null Store the name of person who is


created this cart.
Created Date datetime Allow Null Store the date of Cart is created.
Modify BY Varchar(50) Allow Null Store the name of person who is
modify this cart.
Modify Date datetime Allow Null Store the Date of Cart is modified.

 Table Name : Cart_Detail

Field Name Data type Constraints Description


Id int Not Null
Cart Id int Reference to Category Identity no.
Category Master
Product Category Id int Product category identity no.

Product Id int Not Null Product Identity No (Auto


Generated).
Product Name Varchar(100) Allow Null Name of the Product.

Product Image Varchar(max) Allow Null Image of the Product Image


Product Qty Varchar(50) Allow Null Quantity of the Product.
Product Price Decimal(18,2) Not Null Price of the Product
6. - Implementation Details

1. Program / Modules Specification


2. Implementation Result

1. Program / Module Specification

These are the different Modules of our System

 Administrator Module
 Customer Service
 Customer Inquiry to Mail
 Special Offers
 Home Page
 Products Catalogue
 Shopping Cart
 Select Shipping Charge
 Sign Up
 Sign In

 Product Catalogue

This module represents or contains the wide range of Products and enhancements. It
Provides customer to select & purchase the products. It also gives the brief description of
products. If provides navigation facilities to customer.

 Shopping Cart

This module provides customers to carry their overall shopping. It contains the all
products that are purchased by the customer at a same time. It contains the name of products,
their prices per product, shipping charge per product, quantity per product & overall bill amount
that has to pay by the customer. It Provides adding & removing products from the shopping cart
and also provide the facilities to increase or decrease the no. of quantity in the shopping cart.
 Check Out

When the customer completes his/her shopping he/she will go for checkout This module
we directly connected with the PayPal. In PayPal customer has three type of functionality like

 Customer Login :

This Page the customer forces to enter their subscriber Id related to our System. If
customer has valid Customer Id then & then customer can able to put their order successfully.
Due to that customer must be subscribed with the PayPal. If customer does not have register with
the PayPal then customer has to go for the registration process.

 Registration Process :

In the registration process is provide the facilities to membership in PayPal. It will


take the information of customer & if the all information is valid then & then customer can be
able to submit his/her information.

If customer is successfully submitting information then customer can get


Customer Login ID for PayPal through which customer can put orders & get other facilities.

 Payments :

If each information regarding to the payment type are valid then any then
customer can successfully get the order No. & get order placed confirmation otherwise order will
be rejected.

 Sign In

The function of this module is to provide the log in facility to user by assepting User ID
& Password.

 Sign Up

The function of this module is to provide new login Id to the User The User requires
filling some necessary information or the registration process.

 Customer Services :

This module is managing the communication process between end user & system
administrator. It provides following Information & facilities:

1. Shipping Information
2. Policy Information
3. Contact Us
4. Sending Inquiry directly to System administrator.
 Special Offers
This modules is provides the information of the any special offer can given by the system
administrator. Is maintain by the administrator and display in the home page.

 Administrator :

This module can help administrator to manage the system. It contain administrator login
page. If administrator is valid then administrator can manipulate the data in the system. IT also
called the Control Panel. In the control panel the administrator can add, update or delete the
Product category, Product sub category and Product. It deals with database of the system.

The valid administrator has a power to give another person to change or manage the
control panel and entire system. For which the administrator can create new user in user entry
form.

 Implementation result
With the help of above analysis and design we have implemented the project and tried
out our best to fulfill the most of the general requirement. The customer can go through product
catalogues very easily. The customer can easily create the login through registration process and
log into his account. She/he can add the selected Product into his shopping cart and increase or
decrease the quantity and can also remove the selected product from the cart. Whenever he/she
can try to add the product into the cart then system will ask to select the shipping information
customer will select shipping information the it will display appropriate Message. In the system
will display special offers in the home page of the website. He / She can check out by placing
order for the product present in the cart. He/ She can send the inquiry to the administrator
through the inquiry page. In Inquiry When the customer send the inquiry will send mail to the
administrator mail address.

The administrator part Control panel is working perfectly. In the control panel the
administrator add, update & delete the category, Sub category and product information and also
upload the product image and store the detail in the database table. The administrator can
maintain the order information very easily from the paypal. The administrator is Manage all the
site very successfully.

 Future Enhancement
 The Page User level security in the control panel. Only authorized person can see
the particular page.
 Searching facilities of the product in the website. In the categoroy wise,
subcategory and directly to the name wise search of the product.
 Auction can be supported.
 Live help can be supported.

7. - Testing
 Testing
 Testing Plan
 Testing Method
 Test cases

 Testing
“Errors are more common, more pervasive and more troublesome in software than with
other technologies.”

Software Testing has a duel function, it is used to establish the presence of defects in
program and it is used to help judge whether or not the program is usable in practice.
Thus software testing is used for validation and verification, which ensure that software
conforms to its specification and meets the need of the software customer.

Developer resorted Alpha testing, which usually comes in after the basic design of the
program has been completed. The project scientist will look over the program and give
suggestion and ideas to improve or to correct the design. They also reports and give ideas
to get rid of around any major problems. There is bound to be a number of bugs after a
program have been created.

5.1 Software Inspection

Analyze and check system representation such as the requirements document, design
diagram and the program source code. They may be applied at all stages of the process.
Unit
Testing

Module
Testing

Sub-system
Testing

System
Testing

Acceptance
Testing

Figure Testing Process

5.2 Test Plan

 The Testing Process:


Developer tests the software process activities such as Design, Implementation,
and Requirement Engineering. Because, design errors are very costly to repair one system
has been started to operate. Therefore, it is quite obvious to repair them at early stage of
the system. So analysis is the most process of any process.

 Requirements Tractability:

As most interested portion is weather the system is meeting its requirements or


not, for that testing should be planned so that all requirements are individually tested.
Developer checked the output of certain combination of input, which gives desirable
result, or not. Strictly stick to your requirement specifications, give you the path to get
desirable result from the system.

 Tested Items:

Our tested items are like image reading, plotting, color-shedders, and distance
between any two selected points on the image, query system. This portion is very
interesting, first of all put the mouse curser on a specific point and note down the
elevation, then after put that height value into the text box for the query processing, then
at particular height bearing areas will be separated out from the other regions of the map
by other color, and likewise.

 Testing Schedule:

Developer is tested each procedure back-to-back so that errors and omissions can
be found as early as possible. Once the system has been developed fully developer tested
it on other machines, which differs in configuration.

5.3 Testing Methods

Software testing involves executing an implementation of the software with the test data
and examining the output of the software and its operational behavior to check that it is
performing as required.

 Statistical Testing:
Statistical Testing is used to test the program’s performance and reliability and to check
how it works under operational conditions. Tests are designed to reflect the actual user
inputs and there frequency.

The stages involved in the static analysis for the systems are follows.

 Control flow analysis


1. Unreachable code.
2. Unconditional branches into loops.

 Data use analysis


1. Variable used before initialization.
2. Variables declared but never used.
3. Variables assigned twice but never used between assignments.
4. Possible array bound violations.
5. Declared variables.

 Interface Analysis
 Parameter type mismatches.
 Parameter number mismatches.
 Non-uses of the result of function.
 Uncalled function and procedures.

 Storage management faults


 Images not stored in resources.
 Program’s non-volatile memory out of Bound.

 Defect Testing:

Defect Testing is intended to find inconsistencies between a program and its


specification. These consistencies are usually due to the program faults or defect.

 Black-Box Testing:
In Black-Box Testing or Functional Testing, Developer is concerned about the
output of the module and the software, i.e. weather the software gives dropper output as
per the requirement or not. In another words, these testing aims to test a program’s
behavior against it specification without making any reference to the internal structure of
the program or the algorithms used. Therefore the source code is not needed, so even
purchased modules can be tested. The program just gets a certain input and its
functionality is examined by observing the output.

This can be done in the following way:


1. Input Interface
2. Processing
3. Output Interface
The tested program gets certain inputs. Then the program does its job and generates a
certain output, which is collected by a second interface. This result is then compared to
the expected output, which has been determined before the test.

 White-Box Testing:
White box testing is used as an important primary testing approach. Here code is
inspected to see what it does, test are designed to exercise the code. Code is testing uses
code scripts, driver, etc which are employed to directly interface with the drive the code.
The tester can analyze the code and use the knowledge about the stricter of a component
to derive the test data.

 Structural Testing:
Developer has done path testing to exercise every independent execution path
through a component or program. If every independent path is executed then all
statements in the component must have been executed at least once. The structure of our
program is also checked.

 Integration Testing :
After our individual modules developer tested out developer go to the integrated
to create a complete system. This integration process involves building the system and
testing the resultant system for problems that arise from component interactions.
Developer has applied top down strategy to validate high level components of a system
before design and implementations have been completed. Because, our department
process started with high level components and developer worked down the component
hierarchy.

 Performance Testing:
Performance testing is designed to test the run time performance of the system
within the context of the system. These tests Developer performed as module level as
Developer as system level. Individual modules Developers tested for required
performance.

 Condition Testing:
Condition testing is a test case design method that exercises the logical conditions
contained in a program module. If the condition is incorrect, then as least one part of the
condition is incorrect. It may include.
 Boolean variable error
 String Index out of Bound error
 Null Pointer Assignment
 Input Output Connection Exceptions
 Images or Map Unloaded errors
 Parsing (conversion) errors
 Arithmetic expression error

 Interface Testing :
Interface testing is integral part of Integration testing. Therefore Developer checked for
the
o Interface misuse
o Interface misunderstanding

Developer examined the code to be tested and explicitly list each call to an external
component. In the system, standards tests for GUIs have been performed, which are as
follows.
 The position and related labels for all controls checked.
 All menu functions and sub functions verified for correctness.
 Validations for all inputs done.
 Each menu functions tested, whether it invokes the corresponding functionality
properly.
 Pull down controls was verified for proper functionality.
 Whether the non-editable text control is disabling and it was also verified that it
doesn’t exceed the maximum length.
 Whether the system prompts the user with appropriate message as and when invalid
information is entered.
 All required fields aren’t left blank.

 Object Testing:
Object testing is to test object as individual components, which are often larger than
single function. Here following activities have taken placed.
 Testing the individual operations associated with object.
 Testing individual object classes.
 Testing cluster of objects.
 Testing object-oriented system.

5.4 Test Cases

I have used test case based on equivalence partitioning in our project.

 Equivalence Partitioning
Valid input System Valid output

Equivalence partitioning shown an ellipse input equivalence partitioning is set of data


where all of the set member should processed in an equivalent way. Output equivalence
partitions are program output that has common characteristics so can be considered as a
distinct class.

Using the program specification of user documentation may identify the equivalence
partitioning and by the tester using experience to product which classes of input value are
likely to detect error.

Deriving equivalence partitioning from the system specification there are various testing
cases that can also be used. These test cases are below:

 Test software with sequence that has only single value.


 Different sequence of different size in different tests. These decrease the chance that
program with defect will accidently produce a correct output because of some
accidental characteristic of the input.
Derive test so that the first, middle, and last element of the sequence are accessed this
approach reveals problems at partition boundaries.

 Purpose:
The purpose of the test cases is to test the various input and see the output
produce any error or not. There are different test cases according to the system. It is
tested with different types of value like single value multiple value and see it can
generate expected output.

 Reliability Of The System:


There are three approaches to reliability of the system.

 Error Avoidance :
Error avoidance is impossible in any system, as it points to prevention of errors
from occurring in system. In our system, we cannot prevent occurrence of errors because,
if user does not call methods properly and does not input appropriate parameters, we are
unable to avoid errors.

 Error Detection and Correction:


Error detection corresponds to reorganization of errors when they are
encountered. In the system, developer use message boxes to prompt errors to users. We
also use try catch structure to prompt errors. Message box shown to users are in well
understood forms. System prompt varicose error message like file does not exist,
whenever the user tries to open any other file instead of image file. However, system
does not support correction of errors; it is user’s responsibility to take appropriate action.
 Error Tolerance :
Error Tolerance refers to reorganize of errors when they occur, but enables system
to keep running through degraded system. In system will never shutdown automatically
due to errors, but is it possible that because of errors it may not work efficiently. For
example, if invalid image is given then system will prompt error and it will not shutdown.
Furthermore, if user does not add image file, in that case, that layer is not displayed nor
activated and any further operations are not done.

There are two level of reliability:


o First Level
o Second Level

o First Level:

During the project development, we performed a thorough and effective


determination of system requirements. This is necessary to satisfy the reliability at
first level. Our system is meeting right requirement and thus it is reliable at first
level.

o Second Level:

During the testing phase of system, it does not produce unexpected output
unless and until the user make some mistake. Moreover, a chance of system
failure is almost zero, so system is meeting second level reliability too. Hence, we
can say that system is reliable.

Finally there’s only one amazing statement that means everything in itself….

“Testing never ends, it just gets transmitted from you to your customer, every time your
customer uses the software, a test is being conducted.”
Test Case 1
Number
Name Valid User Test
Description This test case will check weather User ID and Password is valid or not. If
not then it will not allow the user to operate the system.
Input Data 1) Valid ID and Password which is already defined.
2) Valid ID but wrong Password.
3) Wrong ID and Wrong Password.
Expected 1) System allow login
Output 2) System Prompts error that user is not valid.
3) System Prompts error that user is not valid.
Actual System Allow login.
Output

Test Case 2
Number
Name Valid Credit card Transaction
Description This test case will check weather money transferred properly from buyer
account to seller account.
Input Data Valid Credit card type, credit card number, expiry date.
Expected 1) Money transferred from buyer account to seller account.
Output 2) Transaction Fail.

Actual Money transferred properly from buyer account to seller account.


Output
Pass/Fail? Pass
Test Case 3
Number
Name Calculate total in cart.
Description This test case will check quantity entered in the quantity textbox according
to total price is right or not.
Test Data Quantity and total price column of cart_mst table.
Used
Expected 1) Total is display properly according to quantity.
Output 2) Total display is wrong.

Actual 1) Total is display properly according to quantity.


Output
Pass/Fail? Pass
Test Case 4
Number
Name Inquiry from user is received or not.
Description This test case will check inquiry send by user is properly sent to admin or
not.
Input Data Filled Inquiry form by User.
Expected 1) Inquiry properly received by admin.
Output 2) Inquiry is not received by admin.

Actual Inquiry Properly received by admin.


Output
Pass/Fail? Pass

Test Case 5
Number
Name Forgot password is send by mail.
Description This test will check if some one forgot password then his/her password is
send by mail to his email id, so to check mail receive or not.
Input Data Filled forgot password form.
Expected 1) Forgot password mail is received.
Output 2) Forgot password mail is not received.

Actual Forgot password mail is received.


Output
Pass/Fail? Pass
Test Case 6
Number
Name ID and Blank field validation.
Description This test will check weather all the fields in the form are filling or not. And
ID is entered properly or not.
Input Data Fill the various field of the form.
Expected 1) Shows message like field must not be blank or invalid email id.
Output 2) Message of success.

Actual Shows message like field must not be blank or invalid email id.
Output
Pass/Fail? Pass
7. – Screen Shots

Admin Part

1. Login Page(Admin)

In this page user(admin) can login in the site.


2. Main Page
Admin can be handle the all functionality in this page.

3. Change Password :
User Can be change the password & set New Password.
4. Page Entry:
In this page the User Can be Add ,edit, delete the pages.

5. User Entry:
In this page the User Can also create new user.
6. Category Entry :
In this Page the User Can be add, update, or delete the category.

7. Product Entry:
Admin can add, delete, edit the product in the Category Master.
Customer Part

8. Home Page:
This is Home page. The Customer can login with this page.
9. Product Details :
Customer can see all the items which available in the shop. And get the full detail
information about the particular product.
10. Customer register:
In this page the customer can be registered in the shopping cart.
11. Add Cart:
In this page the customer who is login can be bye the product online.

12. View Cart :


In the shopping Cart the logined Customer can add, delete the product in the cart.
And customer also Change the number of quantity of the product in the cart.
13. Inquiry Form :
Any customers have any kind of inquiry then it will send the inquiry to the owner.

14. Check out:


The customer will click on the check out then it must be the registered will us.
15. Contact Us:
In this page give the information about this shopping palace.

16. About Us:


In this page gives information about us .
 CONCLUSION
We have working from the last 4 months on Online Shopping
Website. We have creating a this Site as per the requirement of company
HCL Info systems Pvt. Ltd. we learn about the session, designing CSS, file
uploading, photo uploading and how to work with the Data Base.

 BIBLIOGRAPHY
o The Best Search Engine:-
www.google.com

o For Complexity and Coding:-

www.w3schools.com

You might also like