Você está na página 1de 82

A PROJECT REPORT ON

WEB SHOPPING
SUBMITTED FOR PARTIAL FULLFILMENT OF AWARD OF BACHELOR OF TECHNOLOGY DEGREE
IN

INFORMATION TECHNOLOGY
(UTTARAKHNAD TECHNICAL UNIVERSITY, DEHRADUN, UTTARAKHAND)

By: Manish Negi(07300103026) Rakesh(07300103043) Chandrashekhar Thapa(07300103065) Saurav Bangwal(07300103062)

UNDER THE GUIDENCE OF Mr. SANDEEP RANA


(LECT. IN INFORMATION TECHNOLOGY DEPARTMENT)

UTTARANCHAL INSTITUTE OF TECHNOLOGY, DEHRADUN

2010-2011

CERTIFICATE
This is to certify that Project entitled WEB SHOPPING has been carried out by Manish Negi,Rakesh,Chandrashekhar Thapa,Saurav Bangwal students of BTech Final Year in Information Technology from Uttarakhand Technical University, Dehradun. It is a record of their own work carried out by them under our guidance and supervision in the department during the academic session 20092010.

Guided by

Mr. SANDEEP RANA


(Lect. in Information Technology Deptt.)

ACKNOWLEDGEMENT

We are thankful to Almighty God who has given us the opportunity of accomplishing this project work. Our sincere gratitude to our college U.I.T. Dehradun, to our respected director Prof. S.C.Joshi, Mr. Sanjeev Sharma Head of Department of Information Technology, Project Incharge Mr. Neeraj Kumar Pandey & our project guide Mr. Rahul Sharma for the continuous help, encouragement and guidance throughout the project. We would like to thank him for giving unrestricted access to the laboratory facilities. We are thankful to our parents & family members who constantly inspired us to imbibe into the project work. We would like to thank all our classmates for their cooperation and help.

Project Team Manish Negi Rakesh Saurav Bangwal Chandrashekhar Thapa

ABSTRACT

As internet spread so increasingly in every aspect so now for an organization to run successfully and efficiently it's very important that it have efficient control over web and to use it's resources very well specially web advertising, web marketing etc. So one of the important goals of an organization is to get its own website that can attract others to take interest in the organization.

So for a organization which is in the shopping business there should be a proper online shopping process management system so that all the activities and shopping procedure can be carried out effectively without losing its transparency. An on-line shopping system will be of great help in carrying out shopping operations and with this very objective in mind this Web Shopping has been made. In this web base shopping system we will manage all such activities (like select items, buy items, get actual knowledge about the items, collection of many items at a single time) that will save time, manpower and the biggest advantage of being it web based.

This web based system will provide better prospective for the enhancement of organization regarding to quality and transparency.

Table of Contents
Chapter No.
1. INTRODUCTION a. INTRODUCTION b. ABOUT PROJECT 2. PROJECT ANALYSIS a. FEASIBILITY STUDY i. ECONOMICAL ii. TECHNICAL (H/W & S/W SPECIFICATION) iii. OPERATIONAL b. REQUIREMENT ANALYSIS i. Hardware Requirement ii. Software Requirement iii. Peripherals 3. SOFTWARE REQUIREMENT SPECIFICATION(SRS) i. ii. iii. iv. v. vi. Environmental Characteristics Non functional requirement Interface Description Behavioral Aspect Goal of Implementation Module and their functions

5. DESIGN a. DESIGN PHASE i. ER- DIAGRAMs ii. DFDs iii. Flow Chart 6. DATABASE DESIGN TABLES i. DATA DISCRIPTION OF DIMENSION

7. TESTING 8. SNAPSHOTS 9. CONCLUSION 10. BIBLIOGRAPHY

INTRODUCTION

Introduction
In system software, a web application is an application that is accessed over a network such as the Internet or an intranet. The term may also mean a computer software application that is hosted in a browser-controlled environment (e.g. a Asp Dot Net ) or coded in a browser-supported language (such as Asp Dot Net), combined with a browser-rendered markup language like HTML) and reliant on a common web browser to render the application execution. Web applications are popular due to the ubiquity of web browsers, and the convenience of using a web browser as a client, sometimes called a thin client. The ability to update and maintain web applications without distributing and installing software on potentially thousands of client computers is a key reason for their popularity, as is the inherent support for cross-platform compatibility. Common web applications include webmail, online sales, online auctions, wikis and many other functions. . Our staff is always ready to help their clients & users any time of the day. They will guide & teach you to surf and post your requirements on the website as many times as you wish. Further queries are answered in a much better and polite way. This site is extremely well planned, with all information very easy to access. It provide the better performance to by the any product easily in short time period at home .Provides convenience to those who are looking to buy product in India. In fact, It is a portal that addresses customers every need in relation to Real Estate. It provides best product an easy and convenient link with buyers, promoters and fellow agents have got for the product. The client can get the benefit of the system by retrieving various product information, that can be managed by the administrator Services provided to the administrator by the system include keeping track of the products with their necessary details such as product quantity, price, type etc. Also Online Shopping is an online application that allows the client to shop various products online. It will be user friendly website for shopping as well as sales in this era of internet shopping.

1.b)ABOUT PROJECT

Description:Online shopping is an online application, a website that the user can access to shop multiple items of his choice over the internet at a time. The client is free to browse through the number of products made available by the administrator. If he likes any products he may select them to his cart. The item and its quantity can be selected by the client. The client can get the benefit of the system by retrieving various product information, that can be managed by the administrator Services provided to the administrator by the system include keeping track of the products with their necessary details such as product quantity, price, type etc. Also the administrator is allowed to add or remove products from the website. The SQL Server database is used to store all the information of the products and the transactions done by the customers. All the tables used in the project are normalized to avoid redundancy and efficient storage of the large volume data. Asp Dot Net server page and are used to handle the request of the user, the request is processed by the Asp container and the appropriate response is send back to the user. The system is secure to access and is scalable as many products can be added by the administrator.
The proposed website can be used even by the naive clients 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. It is a three tier application where the web browser through which the client accesses the website is the front end, The requests from the client are sent to the web server, which is the middle tier. Finally the database stored in the SQl server is handled by the third tier.

PROJECT ANALYSIS

2.a) FEASIBILITY STUDY :When complex problem and opportunities are to be defined, it is generally desirable to conduct a preliminary investigation called a feasibility study. A feasibility study is conduct to obtain an overview of the problem and to roughly assess whether feasible solution exists prior to committing substantial resources to a project. During a feasibility study, the system analyst usually works with representatives from the departments(s) expected to benefit from the solution.

Every project is feasible if given unlimited resource and infinite time. Unfortunately, the development of computer based systems is more likely to be plagued by scarcity of resources and difficult delivery of data it is both necessary and prudent to evaluate the feasibility of a project at the earliest possible time. Precious time and money can be saved and untold professional embarrassment can be averted if an ill conceived system is recognized early in the definition phase. So a detailed study is carried out to check the workability of the system.handled by the automated Feasibility study is undertaken to evaluate its workability, impact on the organization, ability to meet user needs, and effective use of resources. The main objective of feasibility study is to test the technical, operational and economical feasibility of developing the computer system. Thus, during feasibility analysis for this project the following three primary areas of interest were considered very carefully. The feasibility study is carried out to test if the proposed system is worth being implemented. Given unlimited resources and infinite time, all projects are feasible. After performing a Preliminary Investigation, gathering and interpreting data and details concerning the project, a Feasibility Check is done which involves a series of steps to check the Technical, Financial and Operational feasibilities.

During this phase, various solutions to the existing problems were examined for each of these solutions the Cost and Benefits were the major criteria to be examined before deciding on any of the proposed systems.

These Solutions would provide coverage of the following: 1. Specification of information to be made available by the system. 2. A clear cut description of what tasks will be done manually and what needs to be system 3. Specifications of new computing equipment needed.
The feasibility of a project can be ascertained in terms of technical factors, economic factors, or both. A feasibility study is documented with a report showing all the ramification of the project.

Aspect of conducting Feasibility Study:


Economic Feasibility. Technical Feasibility Operational Feasibility.

2.a.i) ECONOMIC FEASIBILTY:A systems development project may be regarded as economically feasible or good value to the organization if its anticipated benefits outweigh its estimated costs. However, many of the organizational benefits arising from record keeping projects are intangible and may be hard to quantify. In contrasts, many development costs are easier to identify. These costs may include the time, budget and staff resources invested during the design and implementation phase as well as infrastructure, support, training and maintenance costs incurred after implementation. In these high risk situations it may be appropriate assessments of financial feasibility. The proposed system can be easily developed using the resources available in the organization and they do not invest in procurement of additional hardware or software. The cost of developing the system, including all the phases have been taken into account and it is strict minimum. Hence the system is economically feasible.

This feasibility has great importance as it can outweigh other feasibilities because costs affect organization decisions. The concept of Economic Feasibility deals with the fact that a system that can be developed and will be used on installation must be profitable for the Organization. The cost to conduct a full system investigation, the cost of hardware and software, the benefits in the form of reduced expenditure are all discussed during the economic feasibility.

Return on Investment
i. There will be revenue in terms of more Customer Subscriptions. ii. There will be cost reduction in terms of maintaining huge amounts of paper records, stationary, humans. iii. There will be tracking of the Subscribers from a centralized database. iv. There will be awareness among not only the Subscribers ,but general public regarding the good points of the issue. v. Subscriber satisfaction will lead to more upgrades and reduce the downgrades.

Cost of No Change

The cost will be in terms of utilization of resources leading to the cost to the company. Since our cost of project is our efforts, which is obviously less than the long-term gain for the company, the project should be made.

COST- BENEFIT ANALYSIS


A cost-benefit analysis is necessary to determine economic feasibility. The primary objective of the cost benefit analysis is to find out whether it is economically worthwhile to invest in the project. If the returns on the investment are good, then the project is considered economically

worthwhile. Cost benefit analysis is performed by first listing all the costs associated with the project cost which consists of both direct costs and indirect costs. Direct costs are those incurred by buying software, hiring people, cost of consumable items , rent for accommodation etc. Indirect costs include those involving time spent by user in discussing problems with system analysts , gathering data about problem etc.

2.a.ii) TECHNICAL FEASIBILTY:-

A systems development project may be regarded as technically feasibility or practical if the organization has the necessary expertise and infrastructure to develop, install, operate and maintain the proposed system. Organizations will need to make this assessment based on: Knowledge of current and emerging technological solutions.

Availability of technically qualified staff in house for the duration of t subsequent maintenance phase.

he project and

Availability of infrastructure in house to support the development and maintenance of the proposed system.

Where necessary, the financial and/or technical capacity to procure appropriate infrastructure and expertise from outside.

Capacity of the proposed system to accommodate increasing levels of use over the medium term and capacity of the proposed system to meet initial performance expectations and accommodate new functionality over the medium term.

It is related to the software and equipment specified in the design for implementing a new system. Technical feasibility is a study of function, performance and constraints that may affect the ability to achieve an acceptable system. During technical analysis, the analyst evaluates the technical merits of the system, at the same time collecting additional information about performance, reliability, maintainability and productivity. Technical feasibility is frequently the most difficult areas to assess. The main technical issue raised during feasibility is the existence of necessary technology and whether the proposed equipment has the capacity to hold required data. The technical guarantee of accuracy, reliability, ease and data were also investigated.

The existing computer system has a good hardware configuration and good software facilities in such a way that any alteration can be implemented with slight modifications of the existing process. Hence this project is technically feasible.

The proposed website can be easily developed using resources available in the organization. Hence it is technically feasible.

Hardware Specification
Processor:2.93 GHz Pentium
processor(core2duo) or higher processor.

Operating System:Window2000, Windows Xp, Windows Vista or higher version .

RAM: Minimum 512MB, Recommended 2GB or more.

Hard disk : Minimum 5400 Revolutions per minute(RPM) , Recommended


7200 Revolutions per minute

Software Specification
Web Server: SQl Server or above Development Tool: Visual Studio 2010 Database: SQL Sever

2.a.iii) OPERATIONAL FEASIBILITY STUDY


A systems development project is likely to be operationally feasible if it meets the needs and expectations of the organization. User acceptance is an important determinant of operational feasibility.

The system has been developed after extensive discussion with the end user and all the operational requirements has been taken into account during the planning and implementation stages. Hence the system is operationally feasible. Operation feasibility is a measure of how people feel about the system. Operational Feasibility criteria measure the urgency of the problem or the acceptability of a solution. Operational Feasibility is dependent upon determining human resources for the project. It refers to projecting whether the system will operate and be used once it is installed. If the ultimate users are comfortable with the present system and they see no problem with its continuance, then resistance to its operation will be zero. Behaviorally also the proposed system is feasible. A particular application may be technically and but may fail to produce the forecasted benefits, because the company is not able to get it to work. For the system, it is not necessary that the user must be a computer expert, but any computer operator given a little bit of knowledge and training can easily operate. Our Project is operationally feasible since there is no need for special training of staff member and whatever little instructing on this system is required can be done so quite easily and quickly as it is essentially This project is being developed keeping in mind the general people who one have very little knowledge of computer operation, but can easily access their required database and other related information. The redundancies can be decreased to a large extent as the system will be fully automated.

REQUIREMENT ANALYSIS

2.b) Requirement Analysis Hardware Requirement


Processor: 2.93 GHz Pentium
processor (core2duo) or higher processor.

Operating System:Window2000, Windows Xp, Windows Vista.

RAM: Minimum 512MB, Recommended 2GB or more.

Hard disk : Minimum 5400 Revolutions per minute(RPM) , Recommended


7200 Revolutions per minute

Software Requirement
Web Server: SQl Server or above Development Tool: Visual Studio 2010 Database: SQL Sever

Peripherals
Input Device: Keyboard Output Device: Visual Display Unit

In the implementation of image classification code, we did not need to add any type of additional peripheral.

SRS (Software Requirement Specification)

3.i) Environment characteristic


Hardware Specification Processor:2.93 GHz Pentium
processor(core2duo) or higher processor.

Operating System:Window2000, Windows Xp, Windows Vista.

RAM: Minimum 512MB, Recommended 2GB or more.

Hard disk : Minimum 5400 Revolutions per minute(RPM) , Recommended


7200 Revolutions per minute

Software Specification:
Software Engineering is a planned and systematic approach to the development of software. It is a discipline that consists of methods, tools and techniques used for developing and maintaining software

To solve actual problems in an industry setting, a software engineer or a team ofengineers must incorporate a development strategy that encompasses the process, methods and tool layers and generic phases. This strategy is often referred to as a process model or Software Engineering paradigm. For developing a software product, user requirements are identified and the design is made based on these requirements. The design is then translated into a machine executable language that can be interpreted by a computer. Finally, the software product is tested and delivered to the customer.

These are mainly required softwareWeb Server: SQl Server 2005


or above

Development Tool: Visual Studio 2010 Database:SQL Sever 2005

3.ii) Non Functional Requirements

Portability:
Portability is one of the key concepts of high-level programming. Portability is the software code base feature to be able to reuse the existing code instead of creating new code when moving software from an environment to another. The pre requirement for portability is the generalized abstraction between the application logic and system interfaces. When one is targeting several platforms with the same application, portability is the key issue for development cost reduction.

The Online Shopping website is built on Asp Dot Net, and hence it is portable and is not browser specific. Thus it can be accessed on any platform and using any browser.

Reusability:
The modular components of the Online Shopping is designed that it captures the essence of the functionality expected. This single-minded purpose renders the components reusable wherever there are similar needs in other designs.

Traceability:

The Online Shopping is traceable enough because the origin of each of its requirements is clear. It fulfils the condition of backward Traceability and Forward traceability because each requirement explicitly references its sources in earlier documents.

Scalability:

The online shopping is scalable as it can be used by as many number of clients and as many products as the administrator wants to sell can be added.

Robustness:

It is the quality of being able to withstand stresses, pressures, or changes in procedure or circumstance. A system, organism or design may be said to be "robust" if it is capable of coping well with variations (sometimes unpredictable variations) in its operating environment with minimal damage, alteration or loss of functionality.

Maintainability:

It involves correcting errors that were not discovered during the product development phase, enhancing the software according to the customers requirements and porting the software to work in a new environment.

3.iii) Interface Description

Interface with Operating System:


This website works well in the Windows XP. Windows XP brims with new features, improved programs, and tools. Windows XP contains accessories, and communications and entertainment programs

Microsoft Management Console:


Microsoft Management Console (MMC) hosts administrative tools that you can use to administer networks, computers, services, and other system components.

Interface with Devices:


The devices such as keyboard and mouse are sufficient for the proper accessing of the website. A single click to the hyperlink will fetch us with desired results.

Interface with Databases:


The Database Engine is the core service for storing, processing and securing data. The Database Engine provides controlled access and rapid transaction processing to meet the requirements of the most demanding data consuming applications within your enterprise. The Front End is Asp Dot Net, and Back End is SQL SEVER, which handles all the database processing. ODBC Drivers are the interfaces for the Front and Back End.

Interface with Peripherals:


ACPI Advanced Configuration and Power Interface (ACPI) is an open industry specification that defines a flexible and extensible hardware interface for the system board. Software designers use this specification to integrate power management features throughout a computer system, including hardware, the operating system, and application software. This integration enables Windows to determine which applications are active and handle all of the power management resources for computer subsystems and peripherals.

ACPI enables the operating system to direct power management on a wide range of mobile, desktop and server computers, and peripherals. ACPI is the foundation for the On Now industry initiative that allows system manufacturers to deliver computers that start at the touch of a key on a keyboard.

ACPI design is essential to take full advantage of power management and Plug and Play in Windows. If you are not sure whether your computer is ACPI-compliant, check your manufacturer's documentation. To change power settings that take advantage of ACPI, use Power Options in Control Panel. During Windows Setup, ACPI is installed only if all components present during Setup support power management. Some components, especially legacy components, do not support power management and can cause erratic behavior with Advanced Power Management (APM), or may prevent ACPI from being installed. Examples of such components are Industry Standard Architecture (ISA) components and out-of-date BIOS.

3.iv) Behavioral Aspects


System States to define

State 1:

Accessing Navigation Links

When the user hover the mouse over the link and clicks it, the desired page opens and the user simply gets the desired information. Input: A mouse click to Hyperlink Output: Main page is displayed.

State 2: Client Browsing and Selection of Products. Here the Client browses the website and selects the products which he wants to buy. These products are added to his shopping cart. Input: Client selects the products and quantity of it. Output: The selected product is added to the cart.

State 3: Client checks out. Here the Client goes to his cart and clicks on proceed to check out. He then gets the bill. Input: Click on proceed to check out. Output: Bill for the complete shopping is displayed. State 4: Administrators login. Here the Administrator logs into his account, and view the transactions which have happened, also he can add and delete the products as deemed. Input: Administrator logs in. Output: Manipulated website data as done by the administrator.

Events and Actions:


On clicking any of the navigation we can easily move to desired location in the site. Admin only has the privilege to edit the databases. For that username and required password is needed.

Actions Events

User selects products Click proceed to check out Admin id and password Click on view order Add/Delete Logout

The products are added to the cart. The bill is generated for the products Admin login. Admin can see the transactions. Admin can add or remove products. Admin is logged out.

3.v) Goals Of Implementation


To help the client, to do shopping sitting at home. To help the client in buying Brands demanded the most. Main objective is to reduce workload of client, to go to the shop and make the best deals. We provide the best amongst the best. This project will be able to sustain the changing demands of the customers which may be according to the market trends or due the climatic changes. Hence its future is secure. There is an administrator to update website according to changing needs.

3.iv) MODULES AND THEIR FUNCTIONS:

There are four functional modules in our project which have different types of functions to be performed.

1. Shop

This is the main module containing the links to other modules. It provides user with various product categories hyperlinks and associated information about products. Clicking on any category hyperlink of his choice he will get list of all products in the associated category.

2. Cart

This module stores details regarding the products that the customer has purchased, their quantity, rice, Id, etc. Provides option like proceed to checkout (clicking on it you will get a form asking shipping address and other details required to send the order and prepare your bill.), Another option is continue shopping (to go back to shop area and keep on adding products to existing cart).

3. Admin

Provides you with various options to regulate the website like adding, deleting products, viewing orders made and related information about customer.

4. about us:

Provides information about various people behind this project and their objective to develop this project.

Database is maintained in SQL Sever. Four tables are maintained to manage this project. 1. Category: stores various product categories details. 2. Product: stores information about various products available. 3. Order Details: stores information regarding various transactions. 4. Order: stores information about their customer and their transaction.

DESIGNING

DESING PHASE
Design is an activity of translating the specifications generated in the software requirements analysis into specific design. The design involves designing a system that satisfies customer requirements. In order to transform requirements into a working system, we must satisfy both the customer and the system builders on development team. The customer understands what the system is to do. At the same time, the system builders must understand how the system is to work. For this reason, system design is really a two-part process. First, we produce a system specification that tells the customer exactly what the system will do. This specification is sometimes called a conceptual system design . This mirrors the two parts of requirement description. The conceptual design concentrates on the function of the system, while the technical design describes the form the system will take.

CONCEPTUAL DESIGN:

The conceptual design tells the customer what the system will do. The system is described in terms of its boundary, entities, attributes, and relationships. In the conceptual designing phase we have considered the following questions: Where will the data come from? What will happen to it in the system? What will the system look like to user? What choices will user be offered? What will the reports and screen look like?

Moreover, the system is described in language that the customer can understand, rather than in computer jargon and technical terms. For example, the customers of the system have been told that a menu on display screen will give users access to the system functions. The system description may even list acceptable user responses and the actions that may result. However, the customer is not told how the data are stored in the system or what kind of database management system is used for data manipulation. At the time of conceptual design, we have written in the clients language, which does not contain technicalities. It describes the functions of the systems and incorporates all requirements in adequate details.

TECHNICAL DESIGN:

The technical design explains the system to those hardware and software experts who will implement it. The design describes the hardware configuration, the software needs, the communication interfaces, the input and output of the system and anything else that translates the requirements into a solution to the customers problem. The design description is a technical picture of the system specification. Thus we include the following items in the technical design: The System Architecture: A description of the major hardware components and their functions. The System Software Structure: The hierarchy and function of the software components. The data structure and flow through the system.

DESIGN APPROACH:

Modular approach has been taken into consideration. Design is the determination of the modules and inter modular interfaces that satisfy a specified set of requirements. A design module is a functional entity with a well-defined set of inputs and outputs. Therefore, each module can be viewed as a component of the whole system, just as each room is a component of a house. A module is well defined if all the inputs to the module are essential to the function of the module and all outputs are produced by some action of the module. Thus if one input will be left out, the module will not perform its full function. There are no unnecessary inputs, every input is used in generating the output. Finally, the module is well defined only when each output is a result of the functioning of the module and when no input becomes an output without having the transformed in some way by the module.

Modularity:

Modularity is a characteristic of good system design. High level modules give us the opportunity to view the problem as whole and hide details that may distract us. By being able to reach down to a lower level for more detail when we want to, modularity provides the flexibility , trace the flow of data through the system, and target the pockets of complexity. These all are interrelated with each other and also self sufficient among themselves and help in running the system in an efficient and complete manner.

Level of Abstraction:

Abstraction an information hiding allows us to examine the way in which modules are related to one another in the overall design the degree to which the modules are independent of one another is a measure of how good the system design is. Independence is desirable for two reasons.

First it is easier to understand how a module works if its function is not tied to others. It is much easier to modify a module if it is independent of others. Often a change in requirements

or in a design decision means that certain modules must be modified. Each change affects data or function or both. If the modules depend heavily on each other, a change to one module may mean changes module that are affected by the change.

Coupling:

Coupling is a measure of how modules depend on each other. Two modules are highly coupled if there is a great deal of dependence between them. Loosely couple modules have no interconnection at all. Coupling depends on several things The references made from one module to another.

The amount of data passed from one module to another. The amount of control one module has over the other.

The degree of complexity in the interface between one module and another.

Thus, coupling really represents a range of dependence, from complete dependence to complete independence. We want to minimize the dependence among modules for several reasons. First, if an element is affected by a system action, we always want to know which module causes an effect at a given time. Second, modularity helps in tracking the cause of the system errors. If an error occurs during the performance of particular function, independence of modules allows us to isolate the defective module more easily.

Cohesion:
cohesion refers to the internal glue with which a module is constructed. The more cohesive a module, the more related are the internal parts of the module to each other and to the functionality of the module. In other words, a module is cohesive if all elements of the module are directed towards and essential for performing the same function.

For example the various triggers written for the Subscription entry form are performing the functionality of the module like querying the old data, saving the new data, updating records etc. So its a highly cohesive system.

Scope of control and effect:

Finally we want to be sure that the modules in our design do not affect other modules over which they have the control. The modules controlled by the given module are collectively referred to as the scope of effect. No module should be in scope of effect if it not in scope control. Thus in order to make the system easier to construct, test, correct, and maintain our goals had been: Low coupling of modules High cohesive modules Scope of effect of a module limited to its scope of control

It was decided to store data in different tables in SQL Server. The tables were normalized and various modules identified so as to store data properly create designed reports and on screen queries were written. A menu driven (user friendly) package has been designed containing understandable and presentable menus. Table structures are enclosed. Input and output details were made which are enclosed herewith.

The specifications in our design include User interface Design screens and their description Entity Relationship Diagrams
Our system can be basically divided into 4 modules

Number of modules and their description:

Subscription Process:

This is one of the most important modules. It forms the core of the Sale and Dispatch System. It involves the most basic functions starting from the entry of Subscriber details, their processing to auto-generation of a unique Subscription Id.

Complaint Handling Process:

This function has been added keeping in view the customer feedback regarding the product. This process involves complaint handling in efficient and through manner so as to establish long lasting customer satisfaction.

Report Generation Process:

Any large-scale operation involves generation of tremendous amount of data, which needs to be analyzed by the management in order to have a clear and concise picture of operation being carried out. Keeping in view this essential requirement, there is a provision of Report Generation.

Proof of Delivery(POD) Process:

The concept behind this module is totally customer oriented in which details of Proof of Delivery(POD) are requested by the organization to ensure that the product has been delivered to the customer in an orderly and timely fashion.

4.i) Entity Relationship Diagram(E-R Diagram

Description ProductId

Picture Small
Product Name

Add to cart

stores Product Cart


Price

CategoryId Picture Large

shop

SaveOrder

Manage Website

shopping

Fig:

Admin

user

View orders Delete Product

Add Product

4.ii) DATA FLOW DIAGRAM:


The design phase included the designing of DFD as well as declaration and description of the modules and their functions respectively. Level 0 DFD-In the Customer Bill purchase

Shopping Centre 0

Website Management

website Activity

Admin

Fig: Level-0 DFD

Level 1 DFD
1

Categories Information

Process Shopping

Customer

products of particular category Products

D2

D1

Category

CategoryId

Customer

2
Process Add Product To Cart

D3 Order Details

3
Process C customer Details

Fig:L
Bill

Level 1 DFD

Updating WebsitAdd Product Admin

Delete Pr

D2 Product

Process Updating Website

5 Admin Viewing dat abase Process View Orders Input Start Date and End Date

Details of orders From Start Date to End Date

D4 Order

Fig:Level -1 DFD

Level -2 DFD

Customer

Process Shopping 1.2


Customer

1 .1

1 .3 Get Products By CategoryId

0.3.1
Set Details

Get All Categories

D1

CategoryD2 Order Details

Customer

Process Add To Cart 2.2

2 .1

Add Product to cart

2 .3

Get Products

Save Order

D1

Product

D3 Order Details

3 Customer

Process Customer Details 3.2


Bill

Proceed To Check Out & Get

0.3. 1

3 .1

3 .3

Customer Details

Set Details

D2

Order DetailsD2 Order

Level -2 DFD

Admin 4.1

Process Updating Website

4 .3 Input Details of Product

Updating Website

Add Product Details

4.2
Delete Product D2 Product

5
Admin

Process Viewing Orders

5.2 5 .1 Get Details of Orders

Order List

Input Start And End Date

0.3.1

Viewing Database Details

D4 Orders

Fig :Level-2 DFD

4.iii)FLOW CHART

Go to the url address of the shopping site

Client or Administrator

Client Go to Shop

Administrator Login Administrator

Browse the products and put them in the cart

View Orders

Add or Delete Products from the site

Finished selecting

Logout Administrator

Proceed to checkout, and fill in the details to get the particulars of the bill.

Close the Website

Fig: Flow Chart

Database design tables

There are Three Category of Table

Category Table Table order detail Table order Table product

5.a) DATA DISCRIPTION OF DIMENSION:Category Table

Column Name Categoryid CategoryName Description

Data Type INT(10) VARCHAR(20) VARCHAR(230)

Fig: Table Category

Table Ordedetails
Column Name Transactionid Orderld Productid Price Quantity Data Type INT(10) INT(10) INT(10) INT(10) INT(10)

Table Order Details

Fig: Table_Orderdetails

Table Orders
Column Name Orderid OrderDate UserId Data Type INT(10) DATETIME VARCHAR(50)

Table Orders

Fig:Table_Orders

Table Product

Column Name Productid Title Description Categoryld PictureUrlSmall PictureUrlLarge Price PictureUrlMedium Deleted

Data Type INT VARCHAR(150) VARCHAR(230) INT(10) VARCHAR(150) VARCHAR(150) MONEY VARCHAR(150) CHAR(10)

Table Product

Fig:Table_Product

TESTING

Testing:

Software testing is the process used to help identify the correctness, completeness, security and quality of developed computer software. With that in mind, testing can never completely establish the correctness of arbitrary computer software. In computability theory, a field of computer science, an elegant mathematical proof concludes that it is impossible to solve the halting problem, the question of whether an arbitrary computer program will enter an infinite loop, or halt and produce output. In other words, testing is criticism or comparison that is comparing the actual value with expected one.

There are a wide variety of types of software tests that may be used for building energy simulation software, each with a different objective or scope. Tests may be performed on the entire program or on individual subroutines or algorithms. The goal of software testing is to cost effectively identify and communicate as many potential problems with the software as possible and iterate with the development team until the identified bugs are eliminated. This goal is consistent with the goal of the development team to provide high quality software that is free of errors. Please note that creating bug free software is not an obtainable goal, since there are too many possible inputs and too many possible paths through the program. From the development teams perspective a successful test is one that reveals problem, all other tests are unnecessary. Unfortunately, determining beforehand which tests reveal problems is impossible, and that is why tests are so exhaustive. From the users perspective, a successful test is one that shows that the software results match some type of standard with an adequate level of accuracy.
There are many approaches to software testing, but effective testing of complex products is essentially a process of investigation, not merely a matter of creating and following rote procedure. One definition of testing is "the process of questioning a product in order to evaluate it", where the "questions" are things the tester tries to do with the product, and the product answers with its behavior in reaction to the probing of the tester. Although most of the intellectual processes of testing are nearly identical to that of review or inspection, the word testing is connoted to mean the dynamic analysis of the product putting the product through its paces. The quality of the application can, and normally does, vary widely from system to system but some of the common quality attributes include reliability, stability, portability, maintainability and usability.

TYPES OF TESTING:

Unit Testing:
The first level of testing is called unit testing. In this different modules are tested against the specifications produced during design of the modules. Unit testing is essentially for verification of the code produced during coding phase, and hence the goal is to test the internal logic of the modules. The programmer of the module typically does it. Others consider a module for integration and use only after it has been unit tested satisfactorily. Due to its close association with coding, the coding phase is frequently called coding and unit testing. As the focus of this testing level is on testing code, structural testing is best suited for this level. In fact, as structural testing is not very suitable for large programs, it is used mostly at the unit testing level.

Integration Testing:
The next level of testing is often called integration testing. In this, many unit-tested modules are combined into subsystems, which are then tested. The goal is here to see if the modules can be integrated properly. Hence, the emphasis is on testing interfaces between modules. The testing activity can be considered testing the design. The integration plan specifies the steps and order in which modules are combined to realize the full system. After each integration step, the partially integrated system is tested. An important factor that guides the integration is the module dependency graph.

System Testing: System tests are designed to validate a fully developed system to assure that it
meets its requirements. There are essentially three main kinds of system testing:

Alpha testing: alpha refers to the system testing carried out by the test team within the developing organization. Beta testing: beta testing is the system testing performed by a select group of friendly customer. Acceptance testing: Acceptance testing is the system testing performed by the customer to determine whether to accept or reject the delivery of the system.

System testing is normally carried in a planned manner according to the system plan document. System plan identifies all testing related activities that must be performed, specifies the schedule of testing, and allocates resources. Immediately after requirement specification phase, a system test plan can be prepared which documents the plan for system testing. System test plan can be prepared on the basis of SRS document. The result of system and integration testing are documented in the form of test report.

TEST CASES:
This is a BLACK BOX approach since the test case is designed using only the functional specification of the software i.e without any knowledge of the internal structure of the software. s

Test Case Title

Description

Expected Outcome Shop.asp page displays all available categories


Shows all product under a particular category

Result Pass/Fail Pass

Get all categories

Displays all Categories on Shop.asp page.


On clicking hyperlink of any category available on shop.asp page we will get list of all product products of that category On clicking hyperlink buy the product must be added to cart. On clicking hyperlink the customer will move to shop.asp and can add more products to cart Ask customer to submit personal information for preparing bill. Enter correct username and password to Login.

Get product by categoryId

Pass

Add Product To Cart

Continue Shopping

Product is added to cart and can be seen on cart.asp page Back to shop.asp and continue shopping

Pass

Pass

Proceed to checkout

Enter Admin Area

Add Product Product View Orders

or

Bill is generated containing transaction information Admin area is opened to the Authentic Person Delete On Entering Admin Area Alteration is possible a person can add or delete Products On Entering Admin Area Database view is a person can view orders possible between a start date and end date

Pass

Pass

Pass

Pass

SNAPSHOTS

Fig-HOME PAGE

Fig-LOGIN PAGE

Fig-CATEGORY PAGE

Fig: DELETE PRODUCT FROM CART.

Fig-PRODUCT DETAIL

Fig-FINALIZE ORDER

Fig-PRODUCT

Goals Of Implementation
To help the client, to do shopping sitting at home.

To help the client in buying Brands demanded the most. Main objective is to reduce workload of client, to go to the shop and make the best deals. We provide the best amongst the best. This project will be able to sustain the changing demands of the customers which may be according to the market trends or due the climatic changes. Hence its future is secure. There is an administrator to update website according to changing needs.

MAINTINANCE

NEED OF MAINTAINANCE:
The mention of word maintenance brings up the image of a screwdriver-wielding mechanics with soiled hands holding onto a bagful of spare part. It is the objective of this chapter to clear up this misconception, provide some Intuitive understanding of the software maintenance projects, and to familiarize the readers with the latest technique in software maintenance. Software maintenance denotes any changes made to a software product after it has been delivered to the customer. Maintenance is inevitable for almost any kind of product. However most of the product need maintenance due to the ware and tear cause by use. On the other hand, software products do not need maintenance on this count, but need maintenance to correct error; enhance features, port to new platform, etc. Maintenance work is based on existing software, as compared to development work that creates new software. Consequently, maintenance revolves around understanding existing software and maintenance spends most of their time trying to understand the software they have to modify. Understanding the software involves understanding not only the code but also the related documents. During the modification of the software, the effects of the change have to be clearly understood by the maintainer because introducing undesired side effects in the system during modification is easy.

PROBLEM ENCOUNTERED:

Software maintenance work is presently much more expensive than what it should be and take more time to implement than what is affordable. The reason for this situation is the following. Software maintenance work is one of the neglected areas of software engineering and is mostly carried out using ad hoc techniques, rather than through systematic and planned activities. During maintenance it is necessary to thoroughly understand someone elses work and then carry out the required modification and extension. Another problem associated with maintenance work is that the majority of software products needing maintenance are legacy products.

TYPES OF SOFTWARE MAINTENANCE:

The requirements of software maintenance arise on account of the three main reasons:

Corrective:
Corrective maintenance of software product becomes necessary to rectify the bugs observed while the system is in use.

Adaptive:
A software product might need maintenance when the customers need the product to run on new platforms, on new operating systems, or when they need the product to be interfaced with new hardware or software.

Perfective:
A software product needs maintenance to support the new features that users want it to support, to change different functionalities of the system according to customer demands or to enhance the performance of the system.

VALIDATION

Software testing entails running software products under known conditions with defined inputs and documented outcomes that can be compared to their predefined expectations. It is a time consuming, difficult, and imperfect activity. As such, it requires early planning in order to be effective and efficient. Test plans and test cases should be created as early in the software development process as feasible. They should identify the schedules, environments, resources (personnel, tools, etc.), methodologies, cases (inputs, procedures, outputs, and expected results), documentation, and reporting criteria. The magnitude of effort to be applied throughout the testing process can be linked to complexity, critically, reliability, and/or safety issues (e.g., requiring functions or modules that produce critical outcomes to be challenged with intensive testing of their fault tolerance features).

Implementation of software testing and its implications with respect to software quality cannot be over emphasized. Software testing is a critical element of the software quality assurance and represents the ultimate review of specification, design and coding.

A software testing process should be based on principles that foster effective examinations of a software product. Applicable software testing tenets include:

The expected test outcome is predefined. A good test case has a high probability of exposing an error. A successful test is one that finds an error. There is independence from coding. Both application (user) and software (programming) expertise are employed. Testers use different tools from coders Examining only the usual case is insufficient.

In order to provide a through and rigorous examination of a software product, development testing is typically organized into levels. As an example, a software products testing can organized into unit, integration, and system levels of testing

Performance Bound:
(1) (2) (3) ID: this text-field takes only integers having Authenticated Id of the Admin. Password: To enter Admin Area you have to type Correct Password with Id. Name: this text-field takes at least 2 characters and at most 20 characters.

CONCLUSION,LIMATIONAND FUTURE SCOPE

Conclusion

It was a nice experience working on this project. It is based on Dot net platform. It explores many features of Dot net like asp's; etc. It involves use of css also. This is meant for managing details of product sold .It provides help in maintaining records of product sold which in turn helps the user to know which brands are more demanded and their regular customer. This aims at selling products, maintaining product to be sold. The Admin module is used to store information about products sold and the shop module is used to retrieve information about products from database.

Limitation

When SQL Sever is used with standard tables (table type MyISAM), then locking, that is, the temporary blocking of access to or alteration of database information, is in operation only for entire tables (table locking). You can circumvent the table-locking problem by implementing transaction-capable table formats, such as InnoDB, that support row locking. In using MyISAM tables, SQL Sever is not able to execute hot backups, which are backups during operation without blocking the tables with locks. Here again, the solution is InnoDB, though here the hot backup function is available only in the form of a commercial supplement.

Many database systems offer the possibility of defining custom data types. SQL Sever does not support such functionality, nor is any currently planned. SQL Sever has up to now ignored the general XML trend. It is not clear when SQL Sever will support direct processing of XML data. Numerous commercial database systems offer considerably more functionality in this area, and even the SQL:2003 standard provides for a host of XML functions

SQL Sever is in fact a very fast database system, but it is very limited in its usability for real-time applications, and it offers no OLAP functions. OLAP stands for online analytical processing, and refers to special methods for the management and analysis of multidimensional data. OLAP-capable database systems are often called data warehouses. SQL Sever supports, since version 5.0, stored procedures and triggers, but these functions have not yet fully matured (this applies especially to triggers) and do not yet have the same stability and plenitude of functions offered by commercial database systems.

Future Scope

This web application inculcates the properties of Asp Dot Net and is built on Dot Net platform. The website is scalable and Object oriented.The code is reusable and can be used by websites like e-bay and other shopping sites. This logic can also be used by new administrators who want to sell their products online.

BIBLIOGRAPHY

[1] Books

Beginning Web Development, Silverlight, and ASP.NET. ASP DOT NET and Dot Net Tutorial. SQL,PL/SQL The Programming Language Of Oracle (by IVAN BAYROSS) 2nd edition.

[2] Websites

www.Asp Dot Net.com www.wikipedia.com

Você também pode gostar