Você está na página 1de 32

A Project Report On

Online shopping
Submitted in partial fulfilment of the requirement for the award

Of BACHELOR OF BUSINESS ADMINISTRATION (CAM)


SUBMITTED BYShubham Pal BBA CAM 2nd ( Evening ) 02321001910

UNDER THE GUIDANCE OF


Ms. Shivani Gupta Asst. Prof. ( IT )

IDEAL INSTITUTE OF MANAGEMENT AND TECHNOLOGY

(Guru Gobind Singh Indraprastha University)

Acknowledgement

An undertaking such as this is never the work of a single person and this study is no exception. I, At a very outset thanks and express my gratitude to all those who directly or indirectly helped me a lot in the completion of the present project work and encouraged, inspired and enthusiasts me in the moments of and made it possible for this report to be in your hand today. First of all I wish to express my profound feeling of gratitude and indebtedness to my project guide MS. SHIVANI GUPTA ASST. PROFESSOR IIMT for sparing her time during completion of this project work. I thank her whole hearted.

Shubham Pal BBA CAM 2nd (Evening) Enroll no: 02321001910

CERTIFICATE

This is to certify that SHUBHAM PAL pursuing B.B.A (CAM) from IDEAL INSTITUTE OF MANAGEMENT AND TECHNOLOGY has completed this file under my supervision and guidance. He has taken care of all necessary aspects and shown interest and utmost sincerity during the completion of the project file to my full satisfaction. I clarify that the project is up to my expectation as per the guidance laid down by the GURU GOBIND SINGH INDRAPRASTHA UNIVERSITY (GGSIPU).

Ms. SHIVANI GUPTA ( ASST.PROFESSOR,IT)

CONTENTS
S.NO 1. INTRODUCTION CONTENTS

2.

FEASIBILITY STUDY 2.1 ECONOMIC FEASIBILITY 2.2 TECHNICAL FEASIBILITY 2.3 LEGAL FEASIBILITY

3. 4.

PROJECT REQUIREMENT SYSTEM ANALYSIS 4.1 USE CASE DIAGRAM 4.2 ACTIVITY DIAGRAM 4.3 DFD

5.

PLANNING 5.1 PROJECT PLAN

6.

DESIGN 6.1 PROCESS 6.2 METHODOLOGY 6.3 DATA BASE DESIGN 6.4 LOGIN DESIGN

7. 8. 9.

IMPLEMENTATION TESTING CONCLUSION

10. APPENDIX 11. BIBLOGRAPHY 12. SYNOPSIS

1. INTRODUCTION
A process in which images or listings of goods and services are viewed remotely via electronic m e a n s , e . g , a v e n d o r ' s website, i t e ms a r e s e l e c t e d f o r p u r c h a s e , a n d th e t r a n s a c t i o n i s completed electronically with a credit card or an established credit account. Various encryptions schemes may be, and usually are, used to reduce the risks of sending sensitive information , such as credit-card numbers, over the Internet or other telecommunications facility. A wallet is a small software program used for online purchase transactions. Many payment solution companies, such as Cyber Cash, offer free Wallet software that allows several methods of payment to be defined within the wallet (for example, several different credit cards). Here's h o w i t w o r k s : Wh e n yo u o r d e r s o me t h i n g , t h e o r d e r i s s e n t t o t h e me r c h a n t . Th e me r c h a n t (actually, the merchant's server) sends back an invoice and asks the consumer to launch the Wallet in his computer (or to download it quickly if the consumer doesn't have it yet).When the consumer selects "Pay," the Cyber Cash software on the merchant server sends a message back to the consumer's PC that activates the "Wallet" software. The consumer selects one of the cards defined in the Wallet and clicks. The transaction includes real-time credit card authorization. Cyber Cash says" Soon we will incorporate an electronic "Cash" and "Coin" system to use for transactions that are considered small for credit cards. Online shopping is

the process consumers go through to purchase products or services over the Internet. An online shop, e-shopping, e-store, internet shop, web shop, web store, online store, or virtual store evokes the physical analogy of buying products or services at a bricks-and-mortar retailer or in a mall. The metaphor of an online catalog is also used, by analogy withmail order catalogs. All types of stores have retail web sites, including those that do and do not a l s o h a v e p h ys i c a l s t o r e f r o n t s a n d p a p e r c a t a l o g s . O n l i n e s h o p p i n g i s a t yp e o f electronic commerce used for businessto- business(B2B) and business-to-consumer (B2C) transactions. The term " Webshop" also refers to a place of business where web development, web hosting and other types of web related activities take place (Web refers to the World Wide Web and "shop" has a colloquial meaning used to describe the place where one's occupation is carried out).

2. FEASIBILITY STUDY
2.1 Economic feasibility: In the system, the organization is most satisfied by economic feasibility. Because, if the organization implements this system, it does not require any additional hardware resources as well as it will be saving lot of time.

2.2 Technical feasibility: Technical feasibility centres on the existing manual system of the test Management process and to what extent it can support the system. According to feasibility analysis procedure the technical feasibility of the system is analyzed and the technical requirements such as software facilities, procedure, inputs are identified. It is also one of the important phases of the system development activities. 2.3 Behavioural feasibility: People are inherently resistant to change and computer has been known to facilitate changes. An estimate should be made of how strong the user is likely to move towards the development of computerized system. These are various

levels of users in order to ensure proper authentication and authorization and security of sensitive data of the organizat

3. Software Requirement
3.1 Introduction
3.1.1 Purpose This document is meant to delineate the features of OSS, so as to serve as a guide to the developers on one hand and a software validation document for the prospective client on the other. The Online Shopping System (OSS) for furniture shop web application is intended to provide complete solutions for vendors as well as customers through a single get way using the internet. It will enable vendors to setup online shops, customer to browse through the shop and purchase them online without having to visit the shop physically. The administration module will enable a system administrator to approve and reject requests for new shops and maintain various lists of shop category. 3.1.2 Scope

This system allows the customers to maintain their cart for add or remove the product over the internet. 3.1.3 Definitions

OSS- Online shopping System (for furniture shop) SRS- Software Requirement Specification GUI- Graphical User Interface Stockholder- The person who will participate in system Ex. Customer, Administrator, Visitor etc.

3.1.4 Overview This system provides an easy to solution customers to buy the without go to the shop and also shop owner to sale the product. 3.1.5 Additional Information The system work on internet server, so it will operated by any end user for the buying purpose. product

3.2 General Description


The Online Shopping system (OSS) application enables vendors to set up online shops, customers to browse through the shops, and a system administrator to approve and reject requests for new shops and maintain lists of shop categories. Also the developer is designing an online shopping site to manage the items in the shop and also help customers purchase them online without having to visit the shop physically.The online shopping system will use the internet as the sole method for selling goods to its consumers.

3.3 Functional Requirement


This section provides requirement overview of the system.Various functional modules that can be implemented by the system will be 3.3.1 Description 3.3.2 Registration

If customer wants to buy the product then he/she must be registered, unregistered user cant go to the shopping cart. 3.3.3 Login Customer logins to the system by entering valid user id and password for the shopping. 3.3.4 Changes to Cart Changes to cart means the customer after login or registration can make order or cancel order of the product from the shopping cart. 3.3.5 Payment For customer there are many type of secure billing will be prepaid as debit or credit card, post paid as after shipping, check or bank draft. The security will provide by the third party like Pay-Pal etc.

3.3.6 Logout After the payment or surf the product the customer will logged out. 3.3.7 Report Generation After all transaction the system can generate the portable document file (.pdf) and then sent one copy to the customers Email-address and another one for the system data base to calculate the monthly transaction . 3.3.8 Technical Issues This system will work on client-server architecture. It will require an internet server and which will be able to run PHP application. The system should support some commonly used browser such as IE etc.

3.4. Interface Requirement


Various interfaces for the product could be1. Login Page 2. Registration Form

3. There will be a screen displaying information about product that the shop having. 4. If the customers select the buy button then another screen of shopping cart will be opened. 5. After all transaction the system makes the selling report as portable document file (.pdf) and sent to the customer E-mail address. 3.4.1 GUI 1. Login Page

2. Registration Form

3. Product Page

4. Shopping Cart

5. Portable Document file (.pdf) buying report

3.4.2 Hardware Interface

The System must run over the internet, all the hardware shall require to connect internet will be hardware interface for the system. As for e.g. Modem, WAN LAN, Ethernet Cross-Cable. 3.4.3 Software Interface The system is on server so it requires the any scripting language like PHP, VBScript etc.The system require Data Base also for the store the any transaction of the system like MYSQL etc. system also require DNS(domain name space) for the naming on the internet. At the last user need web browser for interact with the system.

3.5 Performance Requirement


There is no performance requirement in this system because the server and response is depended on the end user internet connection. request

3.6 Design Constrain


The system shall be built using a standard web page development tool that conforms to Microsofts GUI standards like HTML, XML etc.

3.7 Other non Functional requirement


3.7.1 Security

The system use SSL (secured socket layer) in all transactions that include any confidential customer information. The system must automatically log out all customers after a period of inactivity. The system should not leave any cookies on the customers computer containing the users password. The systems back-end servers shall only be accessible to authenticated administrators. Sensitive data will be encrypted before being sent over insecure connections like the internet. 3.7.2 Reliability

The system provides storage of all databases on redundant computers with automatic switchover. The reliability of the overall program depends on the reliability of the separate components. The main pillar of reliability of the system is the backup of the database which is continuously maintained and updated to reflect the most recent changes. Thus the overall stability of the system depends on the stability of container and its underlying operating system. 3.7.3 Availability

The system should be available at all times, meaning the user can access it using a web browser, only restricted by the down time of the server on which the system runs. In case of a of a hardware failure or database corruption, a replacement page will be shown. Also in case of a hardware failure or database corruption, backups of the database should be retrieved from the server and saved by the administrator. Then the service will be restarted. It means 24 X 7 availability.

3.7.4 Maintainability A commercial database is used for maintaining the database and the application server takes care of the site. In case of a failure, a re-initialization of the program will be done. Also the software design is being done with modularity in mind so that maintainability can be done efficiently. 3.7.5 Portability The application is HTML and scripting language based. So The end-user part is fully portable and any system using any web browser should be able to use the features of the system, including any hardware platform that is available or will be available in the future. An end-user is use this system on any OS; either it is Windows or Linux. The system shall run on PC, Laptops, and PDA etc.

3.8 Operational Scenario

The customer wants to buy item. The system shows all product categories to customer. If customer select item then they listed in shopping cart for buying. The payment will made with credit card or bank check. If customer wants to cancel the order before shipping then he or she can cancel it. Customer can see the buying report on account detail.

3.9 Preliminary Schedule


An online shopping system that permits a customer to submit online orders for items and/or services from a store that serves both walk-in customers and online customers. The online shopping system presents an online display of an order cut off time and an associated delivery window for items selected by the customer. The system accepts the customer's submission of a purchase order for the item in response to a time of submission being before the order cut off time. The online shopping system does not settle with a credit supplier of the customer until the item selected by the customer is picked from inventory but before it is delivered. Therefore, the customer can go online and make changes to the order. In addition, available service windows are presented to the customer as a function of customer selected order and service types and further, the order picking is assigned in accordance with a picker's preference. When ordering goods, many shopping systems provide a virtual shopping cart for holding items selected for purchase. Successive items selected for purchase are placed into the virtual shopping cart until a customer completes their shopping trip. Virtual shopping carts may be examined at any time, and their contents can be edited or deleted at the option of the customer. Once the customer decides to submit a purchase order, the customer may print the contents of the virtual shopping basket in order to obtain a hard copy record of the transaction.

4. SOFTWARE ANALYSIS 4.1 Use Case Diagram


A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. The use case is made up of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal. It consists of a group of elements (for example, classes and interfaces) that can be used together in a way that will have an effect larger than the sum of the separate elements combined. The use case should contain all system activities that have significance to the users.

4.2.1 Zero Level Diagram

4.2 Data Flow Diagram


A data flow diagram (DFD) is a graphical representation of the "flow" of data
through an information system, modeling its process aspects. Often they are a preliminary step used to create an overview of the system which can later be elaborated. DFDs can also be used for the visualization of data processing (structured design). A DFD shows what kinds of data will be input to and output from the system, where the data will come from and go to, and where the data will be stored. It does not show information about the timing of processes, or information about whether processes will operate in sequence or in parallel (which is shown on a flowchart).

4.3 Activity diagram


Activity diagram is another important diagram in UML to describe dynamic aspects of the system. Activity diagram is basically a flow chart to represent the flow form one activity to another activity. The activity can be described as an operation of the system. So the control flow is drawn from one operation to another. This flow can be sequential, branched or concurrent. Activity diagrams deals with all type of flow control by using different elements like fork, join etc.

4.4 Entity-Relationship Diagram


An entity-relationship (ER) diagram is a specialized graphic that illustrates the relationships between entities in a database. ER diagrams often use symbols to represent three different types of information. Boxes are commonly used to represent entities. Diamonds are normally used to represent relationships and ovals are used to represent attributes.

5. PLAN
GANTT CHART
A Gantt chart is very useful tool used for planning and scheduling projects. A Gantt chart helps in identifying the tasks involved, the estimated length of time each task will take and the sequence in which those tasks have to be performed. It is a graphic display of the duration of a set of activities constructed with a horizontal axis representing the total time span of the project, broken down and increments and a vertical axis representing the tasks that make up the project. Horizontal bars of varying lengths represent the sequences, timing and time span for each task. The Gantt chart representing the project schedule is given below:

6. DESIGN
Design activity begins when the requirement document for the software is developed. Desigining is the first step in moving from the problem domain towards the solution domain.It is essentially the bridge between the requirement specification and final solution for satisfying the requirement.The goal of the design process is to produced a model or representation of a system which can be used later to build that system. The produced model is called the design of the system.The design of the system is essentially a blue print or a plan for a solution for the system. 6.1 DESIGN PROCESS HAS TWO LEVELS: SYSTEM DESIGN DETAILED DESIGN SYSTEM DESIGN:System design is also known as top level design. At this level the focus is on deciding which modules are needed for the system, specification of these modules and how these modules should be interconnected. DETAILED DESIGN:In this level the internal design of the module or how the specification of the module can be satisfied is decided. This level is also known as logic design. It I 6.2 DESIGN METHODOLOGY:It is the systematic approach to creating a design by applying a set of techniques and guidelines. The input to the design phase is the specification for the system to be design. These specifications must be stable have been approved complete consistent and unambiguous. The output of the top level design phase is the architectural design, for the software system to be built.

6.2.1 THE DESIGN CAN BE: FUNCTIONAL DESIGN OBJECT ORIENTED

FUNCTION DESIGN:In function oriented design, the design consist of module definition with each module supporting a functional abstraction. The system is viewed as transformation function, Transforming the input to the desire output. The purpose of the design phase is to specify the component for this transformation function, so that each component is also a transformation function.Hence the basic output of the system design phase is the definition of all the measure data structure, all the major module of the system and how these modules interact with each other.

OBJECT ORIENTED DESIGN:Object Oriented has clearly become the buzzword of choice in the industry. Almost everyone talks about it. Almost everyone claims to be doing it, and almost everyone says it is better than traditional function oriented design. Object oriented design is the result of focusing attention not on the function performed by the program, but instead on the data that are to be manipulated by the program. Thus, it is orthogonal to function oriented design.Object oriented design begins with an examination of the real world Things that are part of the problem to be solved. These things( which we will call objects ) are characterized individually in terms of their attributes (transient state information) and behavior (functional process information). Each object maintains its own states , and offers a set of services to others object share data areas are eliminated and objects communicate by message .Passing (e.g. parameters ) . Objects are independent entities that may readily be changed because all state and representation information is held within the objects itself.

7. Implementation

Once the design is complete most of the major decisions about the system have been made. The goal of the implementation phase is to translate the design of the system into code in a given programming language. The implementation phase affects both testing and maintenance profoundly. Well-written code can reduce the testing and maintenance effort. Because the testing and maintenance cost of the software are much higher than the coding cost. The goal of the coding should be to reduce the testing and maintenance effort. Simplicity and clarity should be strived for during the implementation phase.

Coding starts once the design phase is over. During the design phase, it is not decided that which language will be chosen and how the different modules will be written. In the coding phase the system design is converted into a code using programming language. During the coding the focus should be on the developing programs that are easy to read and understand and not simply on developing programs that are easy to write.

The coding of the system is done in PHP scripting language. JavaScript is used for validation. All the forms are designed in HTML. MySQL is used for creating database.

7.1 Coding Guidelines: Coding for the development has been done keeping in view the following guidelines: 1. Descriptive Comments 2. Describe blocks of code, rather than commenting every line. 3. Be correct, an incorrect or misleading comment is worse than no comment at all. 4. Indentation will be used to ensure that the code is readable. 5. Naming conventions (for variables, subroutines, etc.) - these will follow the project naming conventions documented in the project file. 6. Complexity should be minimized and modules sub-divided when required, simplifying the code.

8. Testing
Software testing is the process of testing software in a controlled manner to ensure that it behaves the way it is expected to behave. Software testing is, thus a critical element of software quality assurance. Testing requires that the developer discards preconceived notices of the correctness of the software just developed and overcome the conflict of interest that occurs when errors are revealed. The levels of testing that software usually goes through are

ACCEPTANCE TESTING. Testing to verify a product meets customer specified requirements. A customer usually does this type of testing on a product that is developed externally. BLACK BOX TESTING. Testing without knowledge of the internal workings of the item being tested. Tests are usually functional. COMPATIBILITY TESTING. Testing to ensure compatibility of an application or Web site with different browsers, OSs, and hardware platforms. Compatibility testing can be performed manually or can be driven by an automated functional or regression test suite. CONFORMANCE TESTING. Verifying implementation conformance to industry standards. Producing tests for the behavior of an implementation to be sure it provides the portability, interoperability, and/or compatibility a standard defines. FUNCTIONAL TESTING. Validating an application or Web site conforms to its specifications and correctly performs all its required functions. This entails a series of tests which perform a feature by feature validation of behavior, using a wide range of normal and erroneous input data. This can involve testing of the product's user interface, APIs, database management, security, installation, networking, etcF testing can be performed on an automated or manual basis using black box or white box methodologies.

INTEGRATION TESTING. Testing in which modules are combined and tested as a group. Modules are typically code modules, individual applications, client and server applications on a network, etc. Integration Testing follows unit testing and precedes system testing. LOAD TESTING. Load testing is a generic term covering Performance Testing and Stress Testing. PERFORMANCE TESTING. Performance testing can be applied to understand your application or WWW site's scalability, or to benchmark the performance in an environment of third party products such as servers and middleware for potential purchase. This sort of testing is particularly useful to identify performance bottlenecks in high use applications. Performance testing generally involves an automated test suite as this allows easy simulation of a variety of normal, peak, and exceptional load conditions. REGRESSION TESTING. Similar in scope to a functional test, a regression test allows a consistent, repeatable validation of each new release of a product or Web site. Such testing ensures reported product defects have been corrected for each new release and that no new quality problems were introduced in the maintenance process. Though regression testing can be performed manually an automated test suite is often used to reduce the time and resources needed to perform the required testing. SMOKE TESTING. A quick-and-dirty test that the major functions of a piece of software work without bothering with finer details. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire. STRESS TESTING. Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. A graceful degradation under load leading to non-catastrophic failure is the desired result. Often Stress Testing is performed using the same process as Performance Testing but employing a very high level of simulated load.

SYSTEM TESTING. Testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic. UNIT TESTING. Functional and reliability testing in an Engineering environment. Producing tests for the behavior of components of a product to ensure their correct behavior prior to system integration.

WHITE BOX TESTING. Testing based on an analysis of internal workings and structure of a piece of software. Includes techniques such as Branch Testing and Path Testing. Also known as Structural Testing and Glass Box Testing.

9. Conclusion
This project was a challenge for me from the very beginning of the project. I was imagined that could I able to finish the project or not. But my friends give me the inspiration to finish the project, but the most important person, without whose help I was really unable to finish the project without help of my Programming teacher Ms. Shivani Gupta (Asst. Prof. , IT). I want to give her special thanks. I want to give thanks to my friends also. All Staff of the shops where Ive investigated and take informat ion ware very much helpful. Without their help it was impossible for me to understand the problems & techniques of Point of Sales system. The tried their best to understood me their system. If I would not be able to understand the system then I was fully unable to develop their system. So I want to give them Thanks also. Now I have finished my project successfully and I am feeling glad by thinking that I have really done a god job.

10.BIBLIOGRAPHY

To bring the project to a fruitful completion we have consulted several websites and books. We are giving a list of the important books and websites. These were the initial points of our research for this project.

Software Engineering by K.K. Aggarwal Software Engineering by Roger S. Pressman www.wikianswers.com/q?id=320019/online_shopping

10. Project Synopsis


The Online Shopping application enables vendors to set up online shops, customers to browse through the shops, and a system administrator to approve and reject requests for new shops and maintain lists of shop categories. Also on the agenda is designing an online shopping site to manage the items in the shop and also help customers purchase them online without having to visit the shop physically. Our online shopping will use the internet as the sole method for selling goods to its consumers. The consumer will be in complete control of his/her shopping experience by using the unique storefront concept. Shopping will be highly personalized and the provider provides lower prices than most competitors. This, in brief, is a description of our product which will showcase a complete shopping experience in a small package.