Online shopping Report

ONLINE SHOPPING
A PROJECT REPORT
Submitted by
PRAGNYA DASH
Under the guidance of
Prof. Sabyasachi Patra
in partial fulfillment for the award of the degree
of
Bachelor of Technology
in
INFORMATION TECHNOLOGY
Of
COMPUTER SCIENCE AND ENGINEERING DEPARTMENT
INTERNATIONAL INSTITUTE OF INFOFMATION TECHNOLOGY
BHUBANESWAR – 751003, INDIA
December, 2014

CERTIFICATE
This is to certify that the dissertation entitled “ONLINE SHOPPING” submitted by PRAGNYA DASH(B411031) is approved for the award of Degree of Bachelor of Technology in Information Technology.
CO-ORDINATOR
DEPARTMENT OF CSE AND IT PROJECT GUIDE
IIIT BHUBANESWAR DATE-2-12-2014
DATE-2-12-2014

ACKNOWLEDGEMENT
I express my deepest gratitude to my guide Prof.Sabyasachi Patra for his exemplary guidance and constant encouragement all through the making of the project.
2-12-2014
Pragnya Dash
IIIT Bhubaneswar

CONTENTS:
1) INTRODUCTION
1.1. Introduction
1.2. Project Objective
1.3. Project Scope
2) PROJECT ANALYSIS
2.1. Hardware & Software Specifications
2.2. Project Instructions
3) FEASIBILITY REPORT
3.1. Economic Feasibility
3.2. Operational Feasibility
3.3. Technical Feasibility
4) SOFTWARE REQUIRMENT SPECIFICATION
4.1. Requirement Specification
4.2. Developers Responsibilities Overview
4.3. Functional Requirements
4.4. Output Definition
4.5. Input Design
4.6. Input Stages
5) SELECTED SOFTWARE
5.1. Microsoft Visual Studio
5.2. Microsoft.NET Framework
5.3 Features of the Common Language Runtime
5.4. C#.NET, ADO.NET Overview
5.5.ASP.NET
6) PROJECT DESIGN
6.1. SOFTWARE ENGINEERING PARADIGM APPLIED
6.2. Reliable System
6.3. Maintenance:
6.4. Output Design:
6.5. Data Dictionary
6.6. ER Diagram
6.7. Data Flow Diagram (DFD)
6.8. Use case Diagram
6.9. Class Diagram
6.10. Sequence Diagram
6.11. Activity Diagram

7) SCREEN SHOTS
8) PROJECT TESTING
8.1. COMPILING TEST
8.2. EXECUTION TEST
8.3. OUTPUT TEST
8.4. ACCEPTANCE TEST
8.5. VALIDATION CHECK
9) IMPLEMENTATION
10) FUTURE IMPROVEMENT
11) CONCLUSION
12) BIBILOGRAPHY

CHAPTER-1
INTRODUCTION
1.1.INTRODUCTION:
Online shopping is the process whereby consumers directly buy goods, services etc. from a seller interactively in real-time without an intermediary service over the internet. Online shopping is the process of buying goods and services from merchants who sell on the Internet. Since the emergence of the World Wide Web, merchants have sought to sell their products to people who surf the Internet. Shoppers can visit web stores from the comfort of their homes and shop as they sit in front of the computer. Consumers buy a variety of items from online stores.
1.2.OBJECTIVE:
 To shop wile in the comfort of your own home ,without having to step out of the door.
 Sell at lower rate due to less over head.
 Provide home delivery free of cost.
 Secured Transaction.
1.3.SCOPE:
This product has great future scope. Online shopping Internet software developed on and for the Windows and later versions environments and Linux OS. This project also provides security with the use of Login-id and Password, so that any unauthorized users can not use your account. The only Authorized that will have proper access authority can access the software.

CHAPTER-2
PROJECT ANALYSIS:
2.1.SOFTWARE REQUIREMENT:
 Operating system :- Windows XP SP-3 / 7/8
 Database :- MYSQL
 Web Browser:- Internet Explorer 6.0/7.0,Google Chrome,Mozilla Firefox
 Web Page Style sheet: - Html, Java Script, and Ajax, WebServer6.0
 Program Code:-C#
2.2.HARDWARE REQUIREMENT:
 Minimum 512MB Main Memory.
 CPU speed: 2.6GHz.
 Monitor: EGA / SVGA (display), 800X600 24 bits True Color.
 Standard Keyboard: 106 Keys with Separate Function Keys & Numeric Pad.
 Mouse: PS /2 Optical mouse.
 CD-RO : Required
2.3.Project Instructions:
 Based on the given requirements, conceptualize the Solution Architecture. Depict the various architectural components, show interactions and connectedness and show internal and external elements. Design the web services, web methods and database infrastructure needed both and client and server.
 Provide an environment for up gradation of application for newer versions that are available in the same domain as web service target.

CHAPTER-3
FEASIBILITY REPORT
Feasibility is an important phase in the software development process it enables the developers to have an assessment of the product being developed It refers to the feasibility study of the product in terms of outcomes of the product, operational required for implement ting it. Feasibility study should be performed on the basic of various criteria and parameters. The various feasibility studies are:-
 Economic Feasibility
 Operational Feasibility
 Technical Feasibility
3.1.Economic Feasibility:
It refers to the benefits or outcomes we are deriving from the product as compared to the total cost we are spending for developing the benefits are more or less the same as the older system then it is not feasible to develop the product.
The product is economical feasible. The E-governance provides the following benefits to primary school of Orissa.
 Reduces the processing time
 Reduces the work load
 Administrative will be effective
3.2.Operational Feasibility:
It refers to the feasibility of the product to be operational. Some products may work very well at the design and implementation but many fail in the real time environment. It introduces the study of human resources required and their technical expertise.

This product is operationally feasible as it is designed specifically for E-Governance. This provides consistent and integrated data management. It also provides information at all levels of people.
3.3.Technical Feasibility:
The system is self-explanting and does not need any entire sophisticated training. A system has been built by concentrating on the graphical uses interface concepts, the application can also be handled very easily with a novice uses. The overall time that a user needs to get trained is less than 15 minutes.
The system has been added with features of menu device and button interaction methods, which makes him the master as he starts working through the environment. As the software that were used as developing this application are very economical and are readily available is the market the only time that is lost by the customer is just installation time.

CHAPTER-4
SOFTWARE REQUIREMENT SPECIFICATION
REQUIREMENT SPECIFICATION:
System requirements are expressed in a software requirement document. The Software requirement specification (SRS) is the official statement of what is required of the system developers. This requirement document includes the requirements definition and the requirement specification. The software requirement document is not a design document. It should set out what the system should do without specifying how it should be done. The requirement set out in this document is complete and consistent.
Developers Responsibilities Overview:
The developer is responsible for:
 Developing the system, which meets the SRS and solving all the requirements of the systems?
 Demonstrating the system and installing the system at client’s location after the acceptance testing is successful.
 Submitting the required user manual describing the system interfaces to work on it and also the documents of the system.
 Conducting any user training that might be needed for using the system.
 Maintain the system for a period of one year after installation.
Functional Requirements:
OUTPUT DESIGN
Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provide a permanent copy of the results for later consultation. The various types of outputs in general are:
 External Outputs, whose destination is outside the organization.
 Internal Outputs whose destination is within the organization and they are the user’s main interface with the computer.
 Operational outputs whose use is purely within the computer department.

Interface outputs, which involve the user in communicating directly with
OUTPUT DEFINATION
The outputs should be defined in terms of the following points:
 Type of the output
 Content of the output
 Format of the output
 Location of the output
 Frequency of the output
 Volume of the output
 Sequence of the output
It is not always desirable to print or display data as it is held on a computer. It should be decided as which form of the output is the most suitable.
For Example
 The decimal points need to be inserted.
 It should leading zeros be suppressed.
Outputs Media:
In the next stage it is to be decided that which medium is the most appropriate for the output. The main considerations when deciding about the output media are:
 The suitability for the device to the particular application.
 The need for a hard copy.
 The response time required.
 The location of the users.
 The software and hardware available.
Keeping in view the above description the project is to have outputs mainly coming under the category of internal outputs.
The main outputs desired according to the requirements specification are:

The outputs were needed to be generated as a hot copy and as well as quires to be viewed on the screen. Keeping in view these outputs, the format for the output is taken from the outputs, which are currently being obtained after manual processing. The standard printer is to be used as output media for hard copies.
INPUT DESIGN
Input design is a part of overall system design. The main objective during the input design is as given below:
 To produce a cost-effective method of input.
 To archive the highest possible level of accuracy.
 To ensure that the input is acceptable and understood by the user.
INPUT STAGES
The main input stages can be listed as below
 Data Recording
 Data transcription
 Data conversion
 Data verification
 Data control
 Data transmission
 Data validation
 Data correction
INPUT TYPES:
It is necessary to determine the various types of inputs. Inputs can be categorized as follows
 External inputs, which are prime inputs for the system.
 Internal inputs, which are user communications with the system.
 Operational, which are computer department’s communications to the system
 Interactive, which are inputs entered during a dialogue.

INPUT MEDIA:
At this stage choice has to be made about the input media. To conclude about the input media consideration has to be given to
 Type of input
 Flexibility of format
 Speed
 Accuracy
 Verification methods
 Rejection rates
 Easy of correction
 Storage and handling requirements
 Security
 Easy to use
 Portability
Keeping in view the above description of the input types and input media, it can be said that most of the inputs are of the form of internal and nteractive. As input data is to be the directly keyed in by the user, the keyboard can be considered to be most suitable input device.
ERROR AVIDANCE
At this stage care is to be taken to ensure that input data remains accurate from the stage at which it is recorded unto the stage in which the data is accepted by the system. This can be achieved only by means of careful control each time the data is handled.
ERROR DECTION
Even though every effort is make to avoid the occurrence of errors, still a small proportion of errors are always likely to occur these types of errors can be discovered by using validations to check the input data.

DATA VALIDATION
Procedures are designed to detect errors in data at a lower level of detail. Data validations have been included in the system in almost every area where there is a possibility for the user to commit errors. The system will not accept invalid data. Whenever an invalid data is keyed in the system immediately prompts the user and the user has to again key in the data and the system will accept the data only if the data is correct. Validations have been including where necessary.
The system is designed to be a user friendly one. In other words the system has been designed to communicate effectively with the user. The system has been designed with pop up menus.
USERINTERFACE DESIGN
It is essential to consult the system users and discuss their needs while designing the user interface.
USER INTERFACE SYSTEM CAN BE BROADLY CLASSIFIED AS
1. User initiated interface the user is in charge, controlling the progress of the user/computer dialogue. In the computer-initiated interface, the computer selects the next stage in the interaction.
2. Computer initiated interfaces
In the computer initiated interfaces the computer guides the progress of the user/computer dialogue. Information is displayed and the user response of the computer takes action or displays further information.
USER-INITIATED INTERFACES
User initiated interfaces fall into approximate classes
1. Command driven interfaces: In this type of interface the user inputs commands or queries which are interpreted by the computer.
2. Forms oriented interfaces the user calls up an image of the form to his/her screen and fills in the form. The forms oriented interface is chosen because it is the best choice.

COMPUTER-INITIATED INTERFACES
The following computer-initiated interfaces were used:
1. The menu system for the user is presented with a list of alternatives and the user chooses one; of alternatives.
2. Questions-answer type dialog system where the computer asks question takes action based on the basis of the users reply.
Right from the start the system is going to be menu driven, the opening menu displays the available options. Choosing one option gives another popup menu with more option. In this way every option leads the users to data entry from where the user can key in the data.
ERROR MESSAGE DESIGN:
The designing of error messages is an important part of the user interface design. As user is bound to commit some errors or other while designed to be helpful by providing the user with information regarding the error he/she has committed.
This application must be able to produce output at different modules for different inputs.
PERFORMANCE REQUIREMENTS:
Performance is measured in terms of the output provided by the application. Requirement specification plays an important part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a system, which will fit into required environment. It rests largely in the part of the users of the existing system to give the requirement specifications because they are the people who finally use the system. This is because the requirements have to be known during the initial stages so that the system can be designed according to those requirements. It is very difficult to change the system once it has been designed and on the other hand designing a system, which does not to the requirements of the user, is of no use.

The requirement specification for any system can be broadly stated as given below
 The system should be able to interface with the existing system
 The system should be accurate
 The system should be better than the existing system
The existing system is completely dependent on the user to perform all the duties.

CHAPTER-5
SELECTED SOFTWARE
5.1. MICROSOFT VISUAL STUDIO :-
Microsoft Visual Studio is Microsoft’s flagship software development product for computer programmers. It centers on an integrated distribution environment which has programmers create stand alone, and web services that run on any platforms supported by Microsoft’s .Net Framework (for all versions after 6). Supported platforms include Microsoft windows, servers and workstations, Pocket PC, Smart Phones and World Wide Web browsers not the Java Virtual Machine that all other java tools target.
5.2. Microsoft.NET Framework:-
The .NET framework is an integral windows component that supports building and running the next generation of applications and XML web services. The key component of the .NET frame work are the common language run time and the. NET frame work class library, which includes ADO.NET, ASP.NET and windows forms. The .NET framework provides a wide variety of programming languages.
OVERVIEW OF THE .NET FRAME WORK
The .NET framework is a new computing platform that simplifies application development in the highly distributed environment of the internet. The .NET framework is designed to fulfill following objectives:
To provide a consistent object oriented programming environment whether object code is stored and 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 guarantees 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 problem of scripted or interpreted environments.
 To make the developer experience consistent across widely types of application, 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, and remote while also enforcing strict type safely and other forms of code accuracy that ensure 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 frameworks is a comprehensive, object-oriented collection reusable types that you can use to develop applications ranging from traditional command line or graphical user interface (FGUI) applications to application base d on the latest innovations provided by ASP.NET, such as web forms and XML web services.
The .NET framework can be hosted by unmanaged component that load the common language runtime into their processes and initiate the execution of managed code. ASP.NET works directly with the runtime to enable ASP.NET application and XML web services, both of which are discussed later in this topic, Internet explorer is an example of unmanaged application that hosts the runtime (in the form of a MIME type extension). Using internet explorer to the host runtime enables you to embed managed components or windows forms controls in HTML documents. Hosting the runtime in this way makes mobile code 9similar to Microsoft Active Xr controls) possible, but with significant improvement that only managed code can offer, such as semi-trusted execution and secure isolated file storage.
5.3. COMMON LANGUAGE RUNTIME (CLR)
The common language runtime (CLR) is responsible for runt-time services such as language integration; security enforcement; and memory, process and thread management. In addition, it has a roll at development time when features such as life cycle management strong type naming, cross-language exception handling, dynamic binding and so on, reduce the amount of code that a developer must write to turn the business logic the reusable component. The runtime can be hosted by high performance, server-side applications, such as Microsoft Internet Information

Services (IIS) for building web applications with ASP.NE and the next release of Microsoft SQL Server. This infrastructure enables you to use code “managed “ by the .NET framework to write your business logic, while still enjoying the superior performance of the industry’s best enterprises servers that support runtime hosting.
5.4. ADO.NET
ADO.NET provides consistent access to data sources such as Microsoft SQL Server and XML, as well as to data sources exposed through OLE DB and ODBC. Data sharing consumer applications can use ADO.NET to connect to these data sources and retrieve, manipulate and update the data that they contain.
ADO.NET separates data access from data manipulation into discrete components that can be used separately or in tandem. ADO.NET includes .NET Frame work data providers for connecting to a database, executing commands and retrieving results. Those results are either processed directly, placed in and ADO.NET Dataset objects in order to be exposed to the used in an ad hoc manner, combined with data from multiple sources or remoted 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 provided functionality to developers writing managed code similar to the functionality provided to native component object model (COM) developers by ActiveX Data Objects (ADO).
5.5 ASP.NET
ASP.NET is a set of Microsoft.NET framework technologies used for building web applications and XML Web services. ASP.NET page execute on the server and generate markup such as HTML, WML or XML that is sent to a desktop or mobile browser. ASP.NET pages use a compiled, event-driven programming model that improves performance and enables the separation of application logic and user interface. Both ASP.NET pages and ASP.NET web services files contain server-side (as opposed to client side logic) written in Visual basic .NET, C#.NET or any .NET compatible language, Web applications and XML Web Services take advantage of the features of the common language runtime, such as type safety, inheritance, language, interoperability, versioning, and integrated security.

CHAPTER-6
PROJECT DESIGN
SOFTWARE ENGINEERING PARADIGM APPLIED
Reliable System
There are two levels of reliability. The first is meeting the right requirement. A carefully and through systems study is needed to satisfy this aspect of reliability. The second level of systems reliability involves the actual working delivered to the user. At this level, the systems reliability is interwoven with software engineering and development. There are three approaches to reliability.
1. Error avoidance: Prevents errors from occurring in software.
2. Error detection and correction: In this approach errors are recognized whenever they are encountered and correcting the error by effect of error of the system does not fail.
3. Error tolerance: In this approach errors are recognized whenever they occur, but enables the system to keep running through degraded perform or Appling values that instruct the system to continue process.
Maintenance:
The key to reducing need for maintenance, while working, if possible to do essential tasks.
1. More accurately defining user requirement during system development.
2. Assembling better systems documents.
3. Using some effective methods for designing, processing, login and communicating information with project team members.
4. Making better use of existing tools and techniques.
5. Managing system engineering process effectively.

Output Design:
One of the most important factors of an information system for the user is the output the system produces. Without the quality of the output, the entire system may appear unnecessary that will make us avoid using it possible causing it to fail. Designing the output should process the in an organized well throughout the manner. The right output must be developed while ensuring that each output element is designed so that people will find the system easy to use effectively.
The term output applying to information produced by an information system whether printed or displayed while designing the output we should identify the specific output that is needed to information requirements select a method to present the formation and create a document report or other formats that contains produced by the system.
Types of output
Whether the output is formatted report or a simple listing of the contents of a file, a computer process will produce the output.
 A Document
 A Message
 Retrieval from a data store
 Transmission from a process or system activity
 Directly from an output sources
Layout Design:
It is an arrangement of items on the output medium. The layouts are building a mock up of the actual reports or document, as it will appear after the system is in operation. The output layout has been designated to cover information. The outputs are presented in the appendix.
Input design and control:
Input specifications describe the manner in which data enter the system for processing. Input design features will ensure the reliability of the systems and produce results from accurate data or thus can be result in the production of

erroneous information. The input design also determines whenever the user can interact efficiently with this system.
Objectives of input design:
Input design consists of developing specifications and produces for data preparation, the steps necessary to put transactions data into a usable from for processing and data entry, the activity of data into the computer processing. The five objectives of input design are
 Controlling the amount of input
 Avoiding delay
 Avoiding error in data
 Avoiding extra steps
 Keeping the process simple
Controlling the amount of input:
Data preparation and data entry operation depend on people, because lab our costs are high, the cost of preparing and entering data is also high. Reducing data requirement expense. By reduce input requirement the speed of entire process from data capturing to processing to provide results to users.
Avoiding delay:
The processing delay resulting from data preparation or data entry operations is called bottlenecks. Avoiding bottlenecks should be one objective of input.
Avoiding errors:
Through input validation we control the errors in the input data.
Avoiding extra steps:
The designer should avoid the input design that cause extra steps in processing saving or adding a single step in large number of transactions saves a lot of processing time or takes mere time to process.
Keeping process simple:
If controls are more people may feel difficult in using the systems. The best- designed system fits the people who use it in a way that is comfortable for them.

NORMALIZATION
It is a process of converting a relation to a standard form. The process is used to handle the problems that can arise due to data redundancy. i.e. repetition of data in the database, maintain data integrity as well as handling problems that can arises due to insertion, updation, deletion anomalies.
Decomposing is the process of splitting relations to eliminate anomalies and maintain anomalies and maintain data integrity. To do this we use normal forms or rules for structuring relation.
Insertion anomaly: Inability to add data to the database due to absence of other data.
Deletion anomaly: Unintended loss of data due to deletion of other data.
Update anomaly: Data inconsistency resulting from data redundancy and partial update.
Normal Forms
First Normal Form:
A relation is said to be in first normal form if the values in the relation are atomic for every attribute in the relation. By this we mean simply that no attribute value can be a set of values or as it is sometimes expressed a relating group.
Second Normal Form:
A relation is said to be in second Normal Form is it is in first normal form and it should satisfy any one of the following rules.
1. Primary key is not a composite primary key
2. No non key attributes are present
3. Every non key attribute is fully functionally dependent on full set of primary key.
Third Normal Form:
A relation is said to be in third normal form if there exists no transitive dependencies.

Transitive Dependency:
If two non-key attributes depend on each other as well as on the primary key then they are said to be transitively dependent.
The above normalization principles were applied to decompose the data in multiple tables thereby making the data to be maintained in a consistent state.
DATA DICTONARY
After carefully understanding the requirements of the requirements of the client the entire data storage requirements are divided into table. The below tables are normalized to avoid any anomalies during the course of data entry.
ER Diagram:
“E-R diagram are used to organize data as a relation, normalizing relations and finally obtaining a relational database model”.
Elements of an E-R diagram are:
1. ENTITY: This specifies the real life objects & is represented as:
2. RELATIONSHIPS: These connect entities & establish meaningful dependencies between them and are represented by:
3. ATTRIBUTES: They specify the properties of entities & are represented by

ONLINE SHOPPING SYSTEM ER DIAGRAM
Onlineshop
p
ing
Product
Customer
Product
Category
Order
Customer Address
Name
MobNo
E
mail
Order Date
Custome_ Id
Category_Id
Order
Id
P
_id
P
_Image
Cat_Description
Cat_Feature
P_Name
P_
Name
Gives
Has
Has
Password
price
discount

6.4 DATA FLOW DIAGRAM
A Data Flow Diagram (DFD) is a diagram that describes the flow of data and the processes that change data throughout a system. It’s a structured analysis and design tool that can be used for flowcharting in place of or in association with information. Oriented and process oriented system flowcharts. When analysts prepare the Data Flow Diagram, they specify the user needs at a level of detail that virtually determines the information flow into and out of the system and the required data resources. This network is constructed by using a set of symbols that do not imply physical implementations. The Data Flow Diagram reviews the current physical system, prepares input and output specification, specifies the implementation plan etc.
Four basic symbols are used to construct data flow diagrams. They are symbols that represent data source, data flows, and data transformations and data storage. The points at which data are transformed are represented by enclosed figures, usually circles, which are called nodes.
DATA FLOW DIAGRAM SYMBOLS:-
Source or Destination of data
- Data Flow
- Process
- Storage

Steps to Construct Data Flow Diagrams:-
o Four steps are commonly used to construct a DFD
o Process should be named and numbered for easy reference. Each name should be representative of the process.
o The destination of flow is from top to bottom and from left to right.
o When a process is exploded in to lower level details they are numbered.
o The names of data stores, sources and destinations are written in capital letters.
Rules for constructing a Data Flow Diagram
o Arrows should not cross each other.
o Squares, circles and files must bear names.
o Decomposed data flow squares and circles can have same names.
o Draw all data flow around the outside of the diagram.

DATA FLOW DIAGRAM
Context Flow Diagram - 0 DFD
Admin_login
Product_id
Product_Name
Product_Image
Product_Feature
Product_Price
Category
EmailId
Name
Password
ContactNumber
Address
User
User_name
Password
Online
Shopping
Product
Sub_
Category

LEVEL 1.0 DFD FOR ADMINISTRATOR
ADD NEW
PRODUCT
MODIFY PRODUCT
Product_
C
ategory
USERNAME
AND
PASSWORD
ADMIN
Admin_login

LEVEL 1.1 DFD FOR ADMINISTRATOR
Raise FeedBack
Change
Feedback
FeedBack
LOGIN WITH
AND
PASSWORD
Customer
USER
VIEW Feeback
USERNAME
AND
PASSWORD
ADMIN
Admin_login

Booking Prduct
Sell Product
billing
LOGIN WITH
AND
PASSWORD
User
Register1
category
sub

ONLINE SHOPPING ACTIVITY DIAGRAM

CHAPTER-7
SNAP SHOTS
default.aspx

addproduct.aspx
manageproduct.aspx

viewfeedback.aspx
TABLES:-
USERS

CHAPTER-8
TESTING
Testing is the process of executing the program with the intention of finding out errors. During testing, the program to be tested is executed with a set of test cases and the output of the programs for the test case is evaluated to determine if the program is performing as it is expected to be.
The success of testing in revealing errors in program depends critically on the test cases. In software system the use of testing is not limited to the testing phase. The results of testing are used later on during maintenance also. During testing a test suite can be used to see that modification doesn’t have any undesirable effect
The basic levels of testing are:
Unit testing
Integration testing
System testing
Acceptance testing
These different levels of testing attempt to detect different types of faults. The relation of faults introduced in different phases and the different levels of testing are as shown in fig;
Client Needs Acceptance Testing
Requirements System Testing
Design Integration Testing
Code Unit Testing
Levels of Testing

1. Unit Testing:
The level of testing is called unit testing. In this, different modules are tested against the specifications produced during design for the modules. Unit testing is essential for verification of the code produced during the coding phase, and hence the goal is set to test the internal logic of the modules.
2. Integration Testing:
The next level of testing is often called the integration testing. In this, many tested modules are combined into subsystems, which are then tested. The goal here is to see if the modules can be integrated properly, the emphasis being on testing interface between modules. This testing activity can be considered as testing design, and hence the emphasis on testing modules interactions.
3. System Testing:
During system testing, the system is used experimentally to ensure that the software doesn’t fail, i.e. it will run according to its specifications and in the way users expect, special test data input for processing, and the results examined. A limited number of users may be allowed to use the system can see whether they try to use it in unforeseen ways.
4. Acceptance Testing:
It is sometimes performed with realistic data of the client to demonstrate that the software is working properly. Testing here focuses on the external behavior of the system. The internal logic of the program is not emphasized.
5. Validation Check:
During testing section validations checks are made. Appropriate actions are taken after testing.

CHAPTER-9
IMPLEMENTATION
Implementation is the stage of the project when the theoretical design turned into a working system. At this stage the main workload, the up heal and the major impact on the existing practices shift to user department. If the implementation stage is not carefully planned and controlled, it can cause chaos. Thus it can be considered to be the most crucial stage in achieving a new successful system and in giving the users confidence that the users confidence that the new system will work and be effective.
The implementation view of software requirements presents the real worlds manifestation of processing functions and information structures. In some cases a physical representation is developed as the first step in software design. However most computer based systems are specified in a manner that dictates accommodation of certain implementation details.
Implementation involves careful planning, investigation of current system and constraints on implementation, design of methods to achieve the changeover, training of staff in the changeover procedures and evaluation of changeover methods. The first task is the implementation planning i.e. deciding the methods and time scale to be adopted.
Once the planning has been completed, the major effort in the computer department is to ensure that the programs in the system are working properly. At the same time the user department must concentrate on training user staff. What the staffs have been trained, a full system test can be carried out, involving both the computer and clerical procedures.
The main step of implementation includes:
1. Installing client machine.
2. Installing the software in the client machine.
3. Training the operational staff.

CHAPTER-10
FUTURE IMPROVEMENT
 As the system is scalable, more modules can be added as and when required
 The database that is used in the system can be connected to the any online examination system.
 It can be browser independent so that the site can be opened in any browser.
 The system contents can be modified to accept new attributes for any criterion.

CHAPTER-11
CONCLUSION
The project has been appreciated by all the users in the organization.
It is easy to use, since it uses the GUI provided in the user dialog.
User friendly screens are provided.
The usage of software increases the efficiency, decreases the effort.
It has been efficiently employed as a Site management mechanism.
It has been thoroughly tested and implemented.

CHAPTER-12
BIBILIOGRAPHY
1.SOFTWARE ENGINEERING By Roger.s.pressman.
2.SQL FOR PROFESSIONALS BY Jain.
3.VISUAL BASIC.NET Black Book By Evangeleous Petereous.
4.ASP.NET Professional By Wrox Publications.
5.MSDN 2002 By Microsoft
.

Online shopping Report

More Related Content

What's hot

Viewers also liked

Similar to Online shopping Report

Recently uploaded

Online shopping Report