A PROJECT ON

ONLINE SHOPPING

By:
Sanuj Singhal

Submitted To: Mr. Sunil Pandey

Department of Information Technology Moser Baer Projects Private Limited

Mr. Subodh Singh

Senior Manager-Corporate HR Moser Baer Projects Private Limited

CERTIFICATE This is to certify that dissertation entitled ONLINE SHOPPING, which is a partial fulfillment of the requirement for the award of the degree of Bachelor of Technology in information technology, Guru Tegh Bahadur Institute of Technology, New Delhi is an authentic record of the candidates own work carried out by them under the guidance of the department of information technology of Moser Baer Projects Private Limited. The matter embodied in this thesis is original and has not been submitted for any other degree.

Mr .Sunil Pandey
Department of Information Technology Moser Baer Projects Private Limited

ACKNOWLEDGEMENT With candor and pleasure we take opportunity to express our sincere thanks and obligation to our esteemed guide Mr .Sunil Pandey (Moser Baer Projects Private Limited). It is because of his able and mature guidance and co-operation without which it would not have been possible for us to complete our project. We again send our project. It is our pleasant duty to thank all the staff member of the information technology department who never hesitated to give there time during the project. Without their help we could not have presented this dissertation up to the present standard. We also take this opportunity to give thanks to all others who gave us support for the project or in other aspects of our study at Moser Baer Projects Private Limited heartiest thanks for helping us for the completion of our

Sanuj Singhal sanujsinghal01@gmail.com

ABSTRACT

Our project entitle ONLINE SHOPPING is designed that the Clients requirement deals with that will enable the client to mobilize its business through buying the different mobile, laptops and tablets in the website. It will enable a customer to have access to online shopping that is the site should be dynamic and more customer centric business procedure thereby maximizing the profit of the organization. This project contains following two modules:

1. Admin Module
This module contains all the information of the pages of the websites, products, sales and users. It manages all records of all the users. New products can be added using this module.

2. Customer Module
This module contains information of all the products available. It allows users to register and log in to shop a product.

List of Figures

Fig no. Figures

Page no

.
1. 2. 3. 4. 5. 6. Client Server Model....................19 CAD (context analysis diagram)..19 Level 1 DFD for Admin...20 Level 1 DFD for Customer..21 Entity Relationship Diagram of the System.22 User Case Diagram for the Login Process...23

CONTENTS Topics Page no

Certificate........................................................2 Acknowledgement...3 Abstract....4 List of figures...........................................................5

1. Introduction..8 1.1Online shopping .....8 1.2 WordPress. ............................9 2. System Study.........................................................................10 2.1 Existing System...............................10 2.1.1 Drawbacks in the Existing System....10 3. System Analysis.....11 3.1 Purpose of the System .......11 3.2 Scope ......12 3.3 Need for the Proposed System...............12 3.4 Feasibility Study.....12 3.4.1 Technical Feasibility ......12 3.4.2 Financial Feasibility.12 3.4.3 Operational Feasibility.....12 4. System Requirements Specification .........................14 4.1 User Class and Characteristics .........14 4.2 Functional Requirements......15 4.3 Performance Requirements.......15
6

4.4 Non Functional Requirements.....15 4.5 External Interfaces Requirements.....16 4.5.1 User Interface....16 4.5.2 Software Interface.16 4.5.3 Hardware Interface....16 4.6 General Constraints, Assumptions, Dependencies, Guidelines.....16 4.6.1 General Constraints16 4.6.2 Assumptions And Dependencies...17 5. System Design Specification.........................................................................18 5.1 Architectural Design..18 5.1.1 Data Flow Diagrams.....18 5.1.2 Database Tables23 5.1.3 User Case Diagrams......23 6. Testing....24 6.1 Unit Testing24 6.2 Integration Testing..24 6.3 Validation Testing...25 7. Website Quality Assurance Plan..26 8. Body of the Thesis.29 8.1 Types of Users...29 8.2 Flow of the Project with Screen Shot....29 9. Conclusion.31 10. Future Scope of Project........................................................31 11. References........................................................32 12 Appendixes.......................................................33
7

1.INTRODUCTION 1.1 Online shopping

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. In fact, people can purchase just about anything from companies that provide their products online. Books, clothing, household appliances, toys, hardware, software, and health insurance are just some of the hundreds of products consumers can buy from an online store. Many people choose to conduct shopping online because of the convenience. For example, when a person shops at a brick-and-mortar store, she has to drive to the store, find a parking place, and walk throughout the store until she locates the products she needs. After finding the items she wants to purchase, she may often need to stand in long lines at the cash register. Despite the convenience of online shopping, not everyone chooses to purchase items and services online. Some people like the idea of physically going to a store and experiencing the shopping process. They like to touch the merchandise, try on clothing, and be around other people. Online shopping doesn't permit shoppers to touch products or have any social interaction. It also doesn't allow them to take the merchandise home the same day they buy it. Online shopping allows you to browse through endless possibilities, and even offers merchandise that's unavailable in stores. If you're searching for a niche product that may not be distributed locally, you're sure to find what you're looking for on the internet. What's even more useful is the ability to compare items, similar or not, online. You can search through multiple stores at the same time, comparing material quality, sizes and pricing simultaneously. Shopping via the internet eliminates the need to sift through a store's products with potential buys like pants, shirts, belts and shoes all slung over one arm. Online shopping also eliminates the catchy, yet irritating music, as well as the hundreds, if not thousands, of other like-minded individuals who seem to have decided to shop on the same day. Say 'goodbye' to the days when you stood in line waiting, and waiting, and waiting some more for a store clerk to finally check out your items. Online shopping transactions occur instantlysaving you time to get your other errands done! Additionally, unlike a store, online shopping has friendly customer service representatives available 24 hours a day, 7 days a week to assist you with locating, purchasing and shipping your merchandise.

1.2 Wordpress
WordPress is a Content Management System (CMS): it allows you to create and maintain a website through an administrative interface, including an automatically-generated navigation structure (page menu bar etc), without needing to know HTML or learn any other tool. It is simple enough for a beginner to learn in a few hours, without sacrificing any power or flexibility. You can do virtually anything with it. WordPress is an Open Source Software: created by thousands of programmers all over the world and put into the public domain, so you do not have to pay to use it WordPress is a web-based application, written in PHP and MySQL, designed to run on Linux servers: PHP is a programming language for web applications, MySQL is a relational database (such as Microsoft Access), and Linux is an operating system for web servers all of these are also open-source. WordPress is, by far, the most popular CMS: over 200 million sites worldwide as of late 2009. WordPress is an excellent platform for creating a small business or professional website. Even though it was originally designed as a blogging platform, it works very well for creating ordinary (static) websites as well. Its also great for membership sites (sites where you sell you content for a fee). WordPress comes with thousands of free themes (templates or styles) and plugins (add-on applications). Changing your theme or adding a plugin is extremely easy. Many WordPress users and developers consider it the shangri-la of website development the elusive goal of simple and powerful website development for non-technical people is now here. Previous platforms were either too difficult to learn (Joomla and Drupal CMSs), proprietary and too limited (Godaddys Website tonight), or expensive.

History:
b2/cafelog, more commonly known as simply b2 or cafelog, was the precursor to WordPress. b2/cafelog was estimated to have been employed on approximately 2,000 blogs as of May 2003. It was written in PHP for use with MySQL by Michel Valdrighi, who is now a contributing developer to WordPress. Although WordPress is the official successor, another project, b2evolution, is also in active development.WordPress first appeared in 2003 as a joint effort between Matt Mullenweg and Mike Little to create a fork of b2. Christine Selleck Tremoulet, a friend of Mullenweg, suggested the name WordPress.In 2004 the licensing terms for the competing Movable Type package were changed by Six Apart and many of its most influential users migrated to WordPress. By October 2009 the 2009 Open Source content management system Market Share Report reached the conclusion that WordPress enjoyed the greatest brand strength of any open-source content-management systems.

2.1 EXISTING SYSTEM

The existing system was an automated system. But It was found to be inefficient in meeting the growing demands of population.

2.1.1 Drawbacks in the existing systems

Disadvantage of the existing system: Time Consuming Expensive Needed an agent We have to out for that.

10

3.SYSTEM ANALYSIS
System analysis is the study of the system or the analysis of the system. It gives in depth details of the system. It forms the basis of the system. 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. In fact, people can purchase just about anything from companies that provide their products online. Books, clothing, household appliances, toys, hardware, software, and health insurance are just some of the hundreds of products consumers can buy from an online store.. This system is all about the converting the shopping system from manual to online. Customer can buy products online after login to the site. Administrator is adding product to database. Administrator can edit or delete the products from the database. After buying and making payment the products are sent to the customers address that he has given. Customer can write feedback for the product or services. Admin can see daily sell and feedback given by customer. Administrator is adding the delivery report to the database. Both admin and customer can see the delivery report.

3.1 Purpose
Online shopping tries to enhance access to care and improve the continuity and efficiency of services. Depending on the specific setting and locale, case managers are responsible for a variety of tasks, ranging from linking clients to services to actually providing intensive shopping and delivery services themselves Main 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. No wait to see the products if someone is taking that. 11

3.2 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 Loginid 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.

3.3 Need for the proposed system

The online shopping (HOME SHOP) is an easy to maintain, ready to run, scalable, affordable and reliable cost saving tool from Software Associates suited for small, medium, and large shopping complex and shopping malls. Features and Benefits: Providing security Low cost Basic computer knowledge required Configurable and extensible application UI design

The proposed system can be used even by the nave users and it does not require any educational level, experience, and technical expertise in computer field but it will be of good use if the user has the good knowledge of how to operate a computer.

3.4 Feasibility study

A feasibility study is a short, focused study, which aims to answer a number of questions: Does the system contribute to the overall objectives of the organizations? Can the system be implemented using current technology and within given cost and schedule constrains? Can the system be integrated with systems which are already in place?

3.4.1 Technical Feasibility

Is the project feasibility within the limits of current technology? Does the technology exist at all? Is it available within given resource constraints (i.e., budget, schedule)?

12

3.4.2 Financial Feasibility:

Is the project possible, given resource constraints? Are the benefits that will accrue from the new system worth the costs? What are the savings that will result from the system, including tangible and intangible ones?

3.4.3 Operational Feasibility:

Define the urgency of the problem and the acceptability of any solution; if the system is developed, will it be used? Includes people-oriented and social issues: internal issues, such as manpower problems, labour objections, manager resistance, organizational conflicts and policies; also external issues, including social acceptability, legal aspects and government regulations.

13

4.SYSTEM REQUIREMENTS
System requirements are expressed in a software requirement document. The Software requirement specification (SRS) is the official statement of what is required of the system developers. This requirement document includes the requirements definition and the requirement specification. The software requirement document is not a design document. It should set out what the system should do without specifying how it should be done. The requirement set out in this document is complete and consistent. The software specification document satisfies the following:1 It specifies the external system behaviors. 2 It specifies constraints on the implementation. 3 It is easy to change. 4 It serves as reference tool for system maintainers. 5 It record forethought about the life cycle of the system. 6 It characterizes acceptable response to undesired events.

4.1 User Class and Characteristics

There are 3 types of user of this software1. General public: can use the system to see the product, their prices and quantity available. General user can not buy the products 2. Customers: are using for viewing and buying the products. Customer can also write feedbacks for products and services 3. Administrator: can add, edit& delete products and provide services to the customer. Administrator can see the daily sell. He can also see the feedback given by the customer. Administrator maintains the deliveries.

14

4.2 Functional Requirements

The System must provide following functionalities Keeping records of admission of customers. Keeping the records of products. Keeping the daily sale. Storing the feedback given by the customer. Keeping details about the product it is delivered or not etc. Storing the items selected by the customer in the temporary storage.

4.3 Performance Requirements

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

4.4 Non Functional Requirements

Following Non-functional requirements will be there in the Insurance on internet: i). Secure access of confidential data (customers details). ii). 24 X 7 availability. iii). Better component design to get better performance at peak time. iv). Flexible service based architecture will be highly desirable for future extension Non functional requirements define system properties and constraints It arise through user needs, because of budget constraints or organizational policies, or due to the external factors such as safety regulations, privacy registration and so on. Various other Non-functional requirements are: 1. Security 2. Reliability 3. Maintainability 4. Portability 5. Extensibility
15

6. Reusability 7. Application Affinity/Compatibility 8. Resource Utilization

4.5 External Interface Requirements 4.5.1 User Interface:

User of the system will be provided with the Graphical user interface, there is no command line interface for any functions of the product. The user will get 2 pages 1. Login page followed by Password

4.5.2 Software Interface:Software required to make working of product is:1. Operating System: Windows XP/vista/7 or later version, Linux OS which supports networking. 2. Web Browser such as Google Chrome, Mozilla Firefox etc

4.5.3 Hardware Interface:The system should have these hardware requirements The processor should be at least Pentium 3 or above The processor speed should be greater than 400 MHz Ram should be or greater than 512 MB

4.6 General Constraints, Assumptions, Dependencies, Guidelines 4.6.1 General Constraints

The interface will be in English only. GUI features available.

16

4.6.2 Assumptions and Dependencies

The product does require back-end database server MySQL for storing the username and password for different types of user of the system as well as various databases regarding various insurance information. Assumptions: User must be trained for basic computer functionalities. User must have the basic knowledge of English The system must be able to respond to database software within reasonable time.

Front-end (user interaction): The product will require a computer with an application program or with any other application program and an communication channel. The speed of the communication channel (if any) must be, at a minimum 28.8 kbps in order to support message transfer in reasonable time.

17

5.1 ARCHITECTURAL DESIGN 5.1.1 DATA FLOW DIAGRAMS:

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

A rectangle represents a data source or destination.

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

An enclosed figure, usually a circle or an oval bubble, represent a process that transforms data streams.

An open-ended rectangle represents data storage.

18

These are symbols that represent data flows, data sources, data transformations and data storage. The points at which data are transformed are represented by enclosed figures, usually circles, which are called nodes. The principle processes that take place at nodes are: combining data streams splitting data streams modifying data streams

FIGURE 1

Client server model

Gen. user Requests ests Customer Request Database Admin Server

FIGURE 2.

CAD(CONTEXT ANALYSIS DIAGRAM)

Admin

Online shopping

Customer

19

FIGURE 3.

LEVEL 1 DFD FOR ADMIN

Id & password

ADMIN ID & ADMIN

Data for verification

LOGIN TABLE

Rejected if not matched ADD PRODUC TS Categ ory details LOGIN

Verified data

VIEW CUSTOMER DETAIL

Customer details USER TABLE

EDIT PRODUC TS DELETE PRODUC TS VIEW DAILY SALE VIEW FEED BACK Feedback details

ADD& VIEW DELIEVERY REPORTS

CATEGORY TABLE

Product details

Sale details PRODUCT TABLE

Delivery details STORE TABLE

FEEDBACK SALE TABLE

20

FIGURE 4. LEVEL 1 DFD FOR CUSTOMER

21

FIGURE 5 ER DIAGRAM

category

price title

name

Product

Buy
Username

product
Billing address

passwor d

Customer details

Email id

Shipping address

Make payment

Write feedback

See delivery

Account
Feedback

Store
comment

Acc no

Bank name

Report Pin no Feedback type feedback 22 Order no

5.1. 2. DATABASE DESIGN:

A database design is a collection of stored data organized in such a way that the data requirements are satisfied by the database. The general objective is to make information access easy, quick, inexpensive and flexible for the user. There are also some specific objectives like controlled redundancy from failure, privacy, security and performance. A collection of relative records make up a table. To design and store data to the needed forms database tables are prepared. Two essential settings for a database are: Primary key: - The field that is unique for all the record occurrences. Foreign key: - The field used to set relation between tables. Normalization is a technique to avoid redundancy in the tables.

FIGURE 6. USER CASE DIAGRAM:

User case diagrams are used to model the functional interaction between u

Login

Validate User

USER-1

Request to the system

Perform next task

Information

Logout USER- 2

(User Case Diagram) 23

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

6.1 Unit Testing:

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

6.2 Integration Testing:

Integration testing, also known as integration and testing (I&T), is a software development process which program units are combined and tested as groups in multiple ways. In this context, a unit is defined as the smallest testable part of an application. Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution. Integration testing is a component of Extreme Programming (XP), a pragmatic method of software development that takes a meticulous approach to building a product by means of continual testing and revision.
24

There are two major ways of carrying out an integration test, called the bottom-up method and the top-down method. Bottom-up integration testing begins with unit testing, followed by tests of progressively higher-level combinations of units called modules or builds. In top-down integration testing, the highest-level modules are tested first and progressively lower-level modules are tested after that. In a comprehensive software development environment, bottom-up testing is usually done first, followed by top-down testing.

6.3 Validation testing:

At the validation level, testing focuses on user visible actions and user recognizable output from the system. Validations testing is said to be successful when software functions in a manner that can be reasonably expected by the customer. Two types of validation testing

Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers' site. Alpha testing is often employed for off-theshelf software as a form of internal acceptance testing, before the software goes to beta testing. Beta testing comes after alpha testing. Versions of the software, known as beta version, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Sometimes, beta versions are made available to the open public to increase the feedback field to a maximal number of future users Grey box testing Grey box testing is the combination of black box and white box testing. Intention of this testing is to find out defects related to bad design or bad implementation of the system.it is used for web application users and system.

25

7. WEBSITE QUALITY ASSURANCE PLAN

Quality Assurance (QA), according to the online Project Management glossary, is defined as "a planned and systematic pattern of all actions necessary to provide adequate confidence that the item or product conforms to established technical requirements." In other words, QA is a standardized method that ensures that everything works as it was intended to work and looks as it was intended to look. QA for the web should include an initial site-specific test plan, a round of browser testing, and a generous integration phase during which the client can evaluate functionality while entering content.

7.1 QUALITY ASSURANCE TEST PLANS

Every website built around a content management system (CMS) will have a significant amount of common functionality that will require testing. This kind of general evaluation might include anything from testing the CMS login to exporting website form data, but is not primarily concerned with how things appear visually. Of course, if something is radically out of place visually, it should be noted. However long the testing list, this first step should be to identify any flaws in the standard operation of the site and CMS and can probably be performed once the white screen is complete and before design application has occurred. The second step is to evaluate functionality specific to the website. Again, this stage is less concerned with how things appear visually than with how things operate. For example, an e-commerce website's store should be thoroughly tested with every relevant combination of products, accessories, and discount codes to make sure that even the most minor variable isn't overlooked. A site with a large content database that relies heavily upon an advanced search tool should be tested by running a large number of various search queries. A site with complex form options should have many test form submissions sent covering all options and combination of options, and so on. While the test plan should be drawn up by the team--naturally, those most familiar with how the site is intended to function--the person performing the test plan should be someone familiar with the technology, process, and purpose of QA, but new to the particular project being tested. Even if you don't have a dedicated QA role, you should endeavor to have fresh eyes on the site for this stage of QA.

26

7.2 BROWSER TESTING

Realistically, there is going to be some overlap between the test plan and browser testing. Common site functions, like form submissions, for example, can have unpredictable issues in different browsers. But once the site functionality has been thoroughly vetted, the site needs to be tested, page by page, in every browser you officially support. Browser testing can be done in a variety of ways, including running multiple physical machines, running virtual machines locally, running a centralized virtual machine server, or using a third-party testing service. We've been experimenting with using CrossBrowserTesting.com, which can test browser performance and some interactive functionality for any URL you submit. It can even generate screenshots of any URL in every current browser simultaneously (I ran this test on my blog page, which you can see in the image above). Plans range from as low as $19.95 per month to as high as $199.95 per month, but the value of being able to quickly check against the particularities of multiple browsers is well worth the cost. By the way, despite being nine years old and out of compliance with todays web standards, Internet Explorer 6 is still being used by a considerable portion of the population. While tools like CrossBrowserTesting.com make it easy to check out how a website looks in IE 6, they don't change the fact that it often requires a lot of extra effort to make a current site look and function correctly in it. At this point, it doesn't make much sense to do more than ensure that websites degrade well to IE 6; guaranteeing perfect performance in it is a losing battle. Even our site isn't perfect in IE 6!

7.3 INTEGRATION IS QA
Once the test plan is complete, the site is probably ready for content entry (we'll cover this a bit more in next month's article). Remember, this often happens before the design has been applied, so it's important that the client is prepared to see and use a work in progress. Though it's not officially considered a QA method, I believe that content entry, or integration, is one of the most effective and important QA efforts for any project. Typically, integration is the point in a project when a client is able to fully experience the reality of their site for the first time. While they have worked closely with the team on prototyping and design, the process of using the CMS to create and enter content is when all the "dots" are connected and made real, and often the first point at which expectations are clarified. No matter how thorough the prototype is, sometimes there are concepts or needs that cannot be communicated until you are immersed in an actual working and producing environment. This is similar to the "blank-slate-shopper" phenomenon: Have you ever seen a review of a book and thought that you'd like to purchase it, only to find that the next time you are actually in a bookstore you have no idea what you want or where to start? This is because we tend towards reactive rather than proactive thinking. We hear about a book and react to it with, "Yes, I'd like to read that," yet when we get to the store and are surrounded by thousands of books, we react to them all by drawing a blank. In web development, things are
27

reversed a bit. Prototyping can be like the store, offering lots of attractive options unrefined by the future reality of how a site will be used. "Yes, I'd like my site to do that!" But integration will always catch the flaws in a site, be they many or few, because users will quickly react when they can't do what they expected to be able to. "Sure, the slideshow is nice, but I need to change the address in the footer!" Finally, QA does not ensure that a project will be 100% bug free. While some bugs are due to sloppiness or haste and can be quickly identified by QA, others are the result of unforeseen functionality conflicts that may not become evident until a site has been used for a while--despite the best intentions and foresight of the team. As with any development project, bugs like these should be expected and encountered with patience. (Need I remind you of how buggy some expensive operating systems are when they launch?) While we hope that the various steps of QA will mitigate the frequency of any bugs occurring, we are definitely not surprised when they show up.

28

8.BODY OF THE THESIS 8.1 Types of users

1. Administrator 2. Customer 3. General Public

8.2Flow of the project with screenshots 1. Homepage: a) Navigation Bar: Home Shop About Cart Contact Checkout My Account

b) Side bar:
Connect to the web On sale now Search

2. About us page: Gives more details of the company including its policies, aims, goals etc. 3.Contact us page: Gives the contact information of the company so that the users can contact
the authorities incase of any query or to give their feedback

4. Shop page: categories of the products are shown in the menu, categories included are
mobiles, laptops and tablets. By selecting the category, all the products of that category will be shown on the page.

4.Cart page : It includes the products which are added by the customer for purchasing.

29

5. Checkout page: It includes the payment gateway for the user. Payment for the products in the cart will be made in this page. Customer needs to fill in his details for shipping and billing of the products. 6.My account page: This page includes view order, change password, change email address, lost password and log out for the user.

For accessing the site, user opens the home page and click on my account menu, where he will register himself of login if he registered earlier. Then customer goes on shop menu and select a category for the product to be purchased. Then user will be directed to products page, where all products will be shown with icons and price of the product on the icon. Then click on button add to cart to add this product to his cart or chooses an option if variable product is available. Then customer goes to checkout page to fill in his billing, payment and shipping details for home delivery of the product. User gets email for his order placed and after completion of the order. Customer can login anytime to track his order. Customer can visit about page to know details of the site. Contact page can be used for any queries by the customer where email will be sent to the admin of the site.

30

9. CONCLUSION
This is to conclude that the project that I undertook was worked upon with a sincere effort. Most of the requirements have been fulfilled up to the mark and the requirements which have been remaining, can be completed with a short extension.

10. FUTURE SCOPE OF PROJECT

The project made here is just to ensure that this product could be valid in today real challenging world. Here all the facilities are made and tested. Currently the system works for limited number of administrators to work. In near future it will be extended for many types of insurance policies so that efficiency can be improved.

31

11.REFERENCES
Websites referred:http://www.google.co.in http://www.wordpress.org/ http://www.bookos.org/

32

12.APPENDIX (Screen Shots) Home page

33

About page

34

Contact Page

35

Shop->Laptop Category Page

36

Shop->Tablets Category Page

37

Shop->Mobiles Category Page

38

Cart Page

39

Checkout Page

40