Sie sind auf Seite 1von 21

Index

Acknowledgements Introduction 1.1Goal 1.2 Need of the application 1.3Scope

Aims and Objectives


Analysis 2.1ERDiagram 2.2Data Flow Diagram 2.3Use case Diagram Testing File Design H/w and s/w requirement Modules 4.1Shop products module 4.2Product Description Module 4.3shoping cart Details Module Conclusions 5.1 Limitations 5.2 Scope for Future Work

INTRODUCTION
1.1 Goal
Shopping has long been considered a recreational activity by many. Shopping online is no exception. The goal of this application is to develop a web based interface for online retailers. The system would be easy to use and hence make the shopping experience pleasant for the users. The goal of this application is To develop an easy to use web based interface where users can search for products, view a complete description of the products and order the products. A search engine that provides an easy and convenient way to search for products specific to their needs. The search engine would list a set of products based on the search term and the user can further filter the list based on various parameters. An AJAX enabled website with the latest AJAX con trols giving attractive and interactive look to the web pages and prevents the annoying post backs. Drag and Drop feature which would allow the users to add a product to or remove a product from the shopping cart by dragging the product in to the shopping cart or out of the shopping cart. A user can view the complete specification of the product along with various images and also view the customer reviews of the product. They can also write their own reviews.

1.2 Need of the application


There are large numbers of commercial Online Shopping websites offering large number of products tailored to meet the shopping interests of large number of customers. These online marketplaces have thousands of products listed under various categories.

1.2.1 Problem:
The basic problems with the existing systems are the non-interactive environment they provide to the users. The use of traditional user interfaces which make continuous post backs to the server; each post back makes a call to the server, gets the response and then refreshes the entire web form to display the result. This scenario adds an extra trade off causing a delay in displaying the results A search engine that would display the results without allowing the users to further filter the results based on various parameters. Use of traditional and non user friendly interfaces that are hard to use

1.2.2 Solution:
The motive of this Online Shopping Web Application is to allow the user to play with the search tool and create different combinatorial search criterion to perform exhaustive search. Making the application AJAX enabled gets rid of these u nnecessary delays letting the user to perform exhaustive search. The users of this application can easily feel the difference between the Ajax empowered user interfaces vs. traditional user interfaces. Provide Interactive interface through which a user can interact with different areas of application easily. A search engine that provides an easy and convenient way to search for products specific to their needs. The search engine would list a set of products based on the search term and the user can further filter the list based on various parameters. Provide Drag and Drop feature thereby allowing the user to add products to or remove products from the shopping cart by dragging the products in to or out of the shopping cart.

1.3 Scope
The current system can be extended to allow the users to create accoun ts and save products in to wish list. The users could subscribe for price alerts which would enable them to receive messages when price for products fall below a particular level. The current system is confined only to the shopping cart process. It c an be extended to have a easy to use check out process. Users can have multiple shipping and billing information saved. During checkout they can use the drag and drop feature to select shipping and billing information .

Aims and Objectives


The primary aim of this project is to demonstrate that with better interactive features in clothing web sites could improve sales for online retailers. The objectives of the project are as follows:

To learn about the Online Apparel Shopping industry. To investigate potential problems with Online Apparel Shopping. To create a prototype web site focusing on one of the many problems that arises within Online Apparel Shopping. To evaluate the prototype with an existing online clothing retailer.

The classic tale of the tortoise and the hare, provided by Freedman, gave the inspiration that Online Apparel Shopping is one the main markets that needs to be tapped in. Freedmans prediction is that, slower starters or early laggards may prove to be some of the strongest categories online long term.

Within this dissertation, facts about Online Apparel Shopping are gathered to demonstrate whether Freedmans prediction is correct.

Analysis
In day to day life, we will need to buy lots of goods or products from a shop. It may be food items, electronic items, house hold items etc etc. Now a days, it is really hard to get some time to go out and get them by ourselves due to busy life style or lots of works. In order to solve this, B2C ECommerce websites have been started. Using these websites, we can buy goods or products online just by visiting the website and ordering the item online by making payments online. This existing system of buying goods has several disadvantages. It requires lots of time to travel to the particular shop to buy the goods. Since everyone is leading busy life now a days, time means a lot to everyone. Also there are expenses for travelling from house to shop. More over the shop from where we would like to buy some thing may not be open 24*7*365. Hence we have to adjust our time with the shopkeepers time or vendors time. In order to overcome these, we have e-commerce solution, i.e one place where we can get all required goods/products online. The proposed system helps in building a website to buy, sell products or goods online using internet connection. Purchasing of goods online, user can choose different products based on categories , online payments , delivery services and hence covering the disadvantages of the existing system and making the buying easier and helping the vendors to reach wider market.

2.1 ER Diagram:

2.2 Data Flow Diagram:

2.3 Use Case Diagram:

Figure 1.3.1: Use case diagram for user

DATA FLOW DIAGRAM

Data flow-oriented modeling continues to be one of the most widely used analysis notations today. The DFD takes an input-process-output view of a system. That is, data objects flow into the software, are transformed by processing elements.

Data flow diagrams provide a logical model of the system and show the flow of data and the flow of logic involved. The Data Flow Diagram (DFD) clarifies system requirements and identifies major transformations that will become programs in system design. With only four symbols, you can use data flow diagrams to represent both physical and logical information systems. Data flow diagrams (DFDs) are not as good as flowcharts for not very useful for depicting purely logical information flows. In fact, flowcharting has been criticized by proponents of structured analysis and structured design because it is too physically oriented. Data flow diagram shows how data travels from one point to another point in the diagram. The flow is shown as an arrowed line with the arrowhead showing the direction of flow.

Data Flow Diagram (DFD) has the following basic characteristics:

They show the passage of data through the system. They focus on the processes that transform incoming data flow (input) into outgoing data flows (outputs). The processes that perform this transformation normally create as well as use data. External entities send and receive data flows from the system. Data flow diagram is also known as Bubble Chart.

DFD supports a top-down approach for analysis, i.e. the analyst begins with a general understanding of the system, and then further draws each components details.

Symbols Used In Data Flow Diagram

Testing Approach

Errors are relevant only after the system is in use. A system that has been put to use without testing can be disastrous in terms of the application. The importance of software testing and its implications cannot be overemphasized. Software testing is a critical element of Software Quality Assurance and represents the ultimate review of the specifications, design and coding.

Testing Objectives
The main objective of testing is to uncover a host of errors, systematically and with minimum effort and time. Stating formally, we can say, 1. Testing is a process of executing a program with the intent of finding an error. 2. A successful test is one that uncovers an as yet undiscovered error. 3. A good test case is one that has a high probability of finding error, if it exists.

But there is one thing that testing cannot do (just to quote a very fa mous sentence) Testing cannot show the absence of defects, it can only show that software defects are presents.

As the test results are gathered and evaluated they begin to give a qualitative indication of the reliability of the software. If severe errors are detected, the overall quality of the software is a natural suspect. If, on the other hand, all the errors, which are encountered, are easily modifiable, then one of the two conclusions can be made: The tests are inadequate to detect possibly present errors. The software more or less confirms to the quality and reliable standards.

Levels of Testing

In order to uncover the errors present in different phases we have the concept of levels of testing. The basic levels of testing are Client Needs Acceptance Testing

Requirements

System Testing

Design

Integration Testing

Code

Unit Testing

Unit testing
Unit testing focuses verification effort on the smallest unit of software i.e. the module. Using the detailed design and the process specifications testing is done to uncover errors within the boundary of the module. All modules must be successful in the unit test before the start of the integration testing begins. Each module has been tested by giving different sets of inputs (giving wrong ID and password etc) when developing the module as well as finishing the development so That each module works without any error. The inputs are validated when accepting from the user.

Integration

Testing

After the unit testing we have to perform integration testing. The goal here is to see if modules can be integrated properly, the emphasis being on testing interfaces between Modules. This testing activity can be considered as testing the design and hence the emphasis on testing module interactions. Integrating all the modules forms the main system. When integrating all the modules I have checked whether the integration effects working of any of the services by giving different combinations of inputs with which the two services run perfectly before Integration.

System Testing
Here the entire software system is tested. The reference document for this process is the requirements document, and the goal is to see if software meets its requirements. It has been tested against requirements of project and it is checked whether all requirements of project have been satisfied or not.

Acceptance Testing
Acceptance Test is performed with realistic data of the client to demonstrate that the software is working satisfactorily. Testing here is focused on external behavior of the system; the internal logic of program is not emphasized. Test cases should be selected so that the largest number of attributes of an equivalence class is exercised at once. The testing phase is an important part of software development. It is the process of finding errors and missing operations and also a complete verification to determine whether the objectives are met and the user requirements are satisfied.

Test Plan
This document describes the plan for testing the course scheduling software. All major testing activities are specified here. The test-plan is basically a list of test cases that need to be run on the system. Some of the test cases can be run independently for some components (report generation from the database, for example, can be tested independently) and some of the test cases require the whole system to be ready for their execution. It is better to test each component as and when it is ready before integrating the components. It is important to note that the test cases cover all the aspects of the system (i.e., all the requirements stated in the RS document).

FILE DESIGN

File Design: File design is the design of the database and it contains information about the files used in the system. In database design the tables constructed, fields in the tables their data types and in the other part it tells about the extensions of the file used in the development. Database will contain: 1. 2. 3. 4. 5. 6. 7. 8. Website Index New Collection Customer Login All Products: Clothing, Shoes, Lingeries, Swim, Accesiories, Gifts Product Details Buying Procedure Special Contact us

H/W AND S/W REQUIREMENT


3.1 Hardware Specification
Processor P IV RAM 512 MB Minimum Space Required 100 MB Display 16 bit color Keyboard Mouse

3.2 Software Requirements.

Operating System Front End tools Backend Browser

: : : :

Windows XP/Vista Operating System. HTMl/ Java Sql Server 2005 Internet Explorer 6 or above

Modules
4.1 Shop Products Module
This module starts when the user visits the home page or when a user searches for a product by entering a search term. This part of the application includes displaying all the products that are available or the products that match the search term entered by the user. The user can then filter these products based on various parameters like manufacturer, product type, operating system supported or a price range. The user browse through the products and each product would be displayed with an image and its features like operating system supported, number of user licenses and if it is a full version or an upgrade version. A user can add a product to the cart either by dragging the product and dropping it in the cart or by clicking a button. The user would be able to see the shopping cart summary.

4.2 Product Description Module


This module starts when a user visits the product description page. A user can view various images of the product of different sizes. The use can see an enlarged image in a popup window. The user can view the complete specification of the product like its features, operating system supported, system requirements etc. A user can also view the manufacturer information and also information about rebates, exchange policies etc. A user can also view the reviews of the product. A user can also write a review for the product.

4.3 Shopping Cart Module


This module starts when the user views the shopping cart. All the products that have been added to the shopping cart by the user are listed along with their price and the quantity. The total price of all the products added to cart is displayed. A user can edit the quantity of each product or remove the product from the shopping cart. A user can remove the product from the cart by clicking a button or by dragging the product and dropping it outside the cart. The total price changes accordingly when a user edits the quantity of a product or when a product is removed from the cart.

Conclusions
The Online Shopping is designed to provide a web based application that would make searching, viewing and selection of a product easier. The search engine provides an easy and convenient way to search for products where a user can Search for a product interactively and the search engine would refine the products available based on the users input. The user can then view the complete specification of each product. They can also view the product reviews and also write their own reviews. Use of Ajax components would make the application interactive and prevents annoying post backs. Its drag and drop feature would make it easy to use.

5.1 Limitations:
This application does not have a built in check out process. An external checkout package has to be integrated into this application. Also users cannot save the shopping carts so that they can access later i.e. they cannot create wish lists which they can access later. This application does not have features by which user can set price ranges for products and receive alerts once the price reaches the particular range.

5.2 Scope for Future Work:


The following things can be done in future. The current system can be extended to allow the users to create accounts and save products in to wish list. The users could subscribe for price alerts which would enable them to receive messages when price for products fall below a particular level. The current system is confined only to the shopping cart process. It can be Extended to have an easy to use check out process. Users can have multiple shipping and billing information saved. During Checkout they can use the drag and drop feature to select shipping and billing information.