dhani2

Cost Co Shoppers Paradise

A

Project Report

On

“Cost Co Shoppers Paradise”

Developed For

ACESOFT Consulting, Aurangabad.

Submitted To

Bhusawal Arts, Science And P.O.Nahata Commerce College,

Bhusawal,Jalgaon.

For Partial Fulfillment of the degree

MASTER OF COMPUTER SCIENCE (M.Sc.)

Submitted By

Miss.Dhanashri Bhikari Bodade

Affiliated To

North Maharashtra University,Jalgaon

2011-2012

ACESOFT Consulting Page 1


BHUSAWAL ARTS,SCIENCEAND P.O.NAHATA COMMERCCOLLEGE,BHUSAWAL

NAAC Re-Accredited ‘A’ Grade

CERTIFICATE

To whom so ever it may concern

This is to certify that Miss.Bodade Dhanashri Bhikari,the M.Sc (Computer Science) student of Bhusawal Arts, Science & P.O.Nahata Commerce College,Bhusawal has successfully completed the fulltime Industrial training with project title“CostCoShoppersParadise”at ACESOFT Consulting(Aurangabad).Andhassubmitted satisfactorily in partialFulfillment of requirementfor the degree of M.Sc. during academicyear2011-2012.

External Examiner ExternalExaminer

Head of the Department of Computer Science




Acknowledgement

We take it is opportunity to thank all those who has directly inspired, directed and helped us towards successful completion of this project report.



I express my profound thanks to my Project Manager Mr. sirand sir,Provided me with the necessary resource and facilities and theirundivided .Attention and support without this project could not have been asuccess.

I would like to thank to my college head of our computer department Mr.G.R.Wani Sir as well as the staff member of college who helped me a lot.I also would like to thank teaching & non teaching staff also without whom I would not have achieved this level.

Last but not the least; I would like to extend my gratitude towards my parents, who Have always been my source of inspiration and motivation.

With Warm Rearguards

Dhanashri Bhikari Bodade.

TABLE OF CONTENT

1. INTRODUCTION Need and Motivation Company Profile Project Introduction



2. SYSTEM STUDY No. of modules Module description

3. SYSTEM REQUIREMENT AND ANALYSIS Project Overview Purpose

4. FEASIBILITY STUDY Introduction Economical Feasibility Technical Feasibility Operational Feasibility

5. SYSTEM DESIGN Preliminary Design Use Cases Data Flow Diagrams Entity Relationship Diagram System Table

6. SOFTWARE DEVELOPMENT Technology used System Requirement



7. TESTING Unit Testing Integration Testing Validation Testing Black Box Testing White Box Testing Acceptance Testing

8. SCREENSHOTS

9. LIMITATIONS& CONCLUSION Prominent features of the System Limitations of the System Conclusion

10.REFERENCE

Books Websites


1.INTODUCTION


1.1 Need and Motivation:

Now days life is being fast. Any type of information and Work should be completed a short time to survive in the world.whearas, using a computer system user can get the information quickly.

Using computerized system we can easily get the information.for achieving best performance ,computerization is mostimportant .it is much simpler for the operates the software of online shopping process.he doesn’t have

To deal with those registers during the online shopping generation, here all the process are product categories, manufacture,offers,giving a very simple interface to the end user.


1.INTODUCTION


The system involves the information about thepurchase product that provides for the prod_id,price,quality and the shipping this product.

This are the 2 modules 1 for general user another for admin.In general user section the user will search for the product its price & fill the cut accordingly to proceed product & its quantity.finally billing is made & shipping address is given to dispatch the order.

Second module administration will maintaining product categories & adding a new product into these categories also updating the updates on day to day offers monthly offers manually purchase tedious task for that physically have to go to market & purchase the product from there.

Shipping or purchase some items from home & get delivery at home.

1.2Introduction to company:

Profile:

ACESOFT Consulting started its operations in 2000,ACE Soft Consulting we gather the best of breed analysts, designers and programmers. Each of our team members comes with a fire-in-the-belly attitude to make IT happen. Each one of us believes in using IT to help our customers get solutions that they once dreamed of! When you outsource your development project to us, you gain an entire team dedicated to fulfilling your requirements. From Concept to Completion, Our team is Your team : a highly qualified and energetic team of experienced software developers, test engineers and project managers to create a quality solution to meet your every IT requirement.



Our quality conscious developers and managers constantly strive for excellence in mastering cutting edge technologies. This coupled with our professional and customer centric approach helps us provide best value solutions to our customers. The corporate environment at ACE Soft Consulting promotes and rewards personal responsibility, empowerment and collaboration. We not only believe in doing things rights the first time, but doing it right EVERY time. We understand that to achieve that we need to create procedures and apply them.

Introduction:

ACE Soft Consulting is a specialized Software Development, Web site Development and IT Consulting Company based in Aurangabad, India. ACE Soft Consulting is into development of products .The range of services and solution include software development, product development and building dynamic, database-driven, Custom web sites. Please take time to explore our site and find out more about what we can do for you and how you may take advantage of the offshore development strategy.

Integrated approach :

ACESOFT Consulting has system integration approach that ability to architect innovative solution, providing best quality services,providing best quality product, accerate your business with us.

Introduction to Project:

The main objective behind developing “COST CO SHOPPERS PARADISE”.is that to help administration to manage the maintain product categories & adding a new product into these categories also updating the updates on day to day offers monthly offers.manuallypurchase this task for that physically have to go to market& purchase the product from there.the project handles all the



product & the shopping or purchase some items from home & get delivery at home.Time and cost saving to reach to people.Time saving for persons of remote places for their product search and also provides the convenience of searching for products anywhere at any point of time.

Shows the information and description of the product. Provides the searching facilities based on various

factors. Sells the products online. Managing the suppliers of raw materials to the

companies.


2.STUDY OF THE SYSTEM


No.of modulesModule description

STUDY OF THE SYSTEM:

In the flexibility of the uses the interface has been developed a graphics concept in mind, associated through a browses interface. The GUI’S at the top level have been categorized as

1.Administrative user interface

2.The operational or generic user interface

The administrative user interface concentrates on the consistent information that is practically, part of the organizational activities and which needs proper authentication for the data collection. The interfaces help the administrations with all the transactional states like Data insertion, Data deletion and Date updating along with the extensive data search capabilities.

The operational or generic userinterface helps the users upon the system in transactions through the existing data and required services. The operational user interface also helps the ordinary users in managing their own information helps the ordinary users in managing their own information in a customized manner as per the assisted flexibilities. ACESOFT Consulting Page 11


2.1 NUMBER OF MODULES

Visitor Interface User interface Administrator Interface Credit Card Interface Discussion Board Interface Entertainment Interface Shopping Cart Interface Sales Report Interface

2.2Module Description:

Visitor Interface

This page of the Costco application will be the first page to be displayed, when a person visits the Costco application. This page will display a welcome message to facilitate navigation through the application. The functionalities provided by the visitor interface is

User Interface

The user home page is displayed to a user, when the user logs on to the Costco application. Only registered users can view this home page. If non-registered users try to login then the application should display the error message, and it has to provide a facility to register with the site. This page has to show how the welcome message to the user and in addition it will display various menus to facilitate navigation through the application.

Administrator Interface

The administrator home page is displayed to administrator logs on to the Costco application. Application has to automatically identify the administrator and also show the administrator related



functionalities. Administrator interface category will have the following functionalities.

Credit Card Interface

Through this interface, application will validate credit card. Costco application will allow three types of credit card. They are Visa Card, Master Card, and Amex card (American Express). Application will validate these cards in two levels. Validate credit card at client side using “LUHN algorithm”. Check with Bank Database.

Discussion Board Interface

Discussion board interface provides a communication facility between the users and administrator. After purchasing the products if user getting any miner problem with the product then he can send the message to the administrator for suggestion. The administrator sends reply to users. This interface contains the three functionalities, they are:

1. This interface provides the information about top ten films, new film etc. User can view the new films and he/she can search the films based on film name or film id. User can vote for his favorite films. Entertainment page contains the four types of functionalities.

Shopping Cart Interface

Shopping cart contains the items that a user has selected for buying. The shopping cart page of the Cost Co application will display a list of products selected by the user. User can add the items to their wish list by clicking the check box next to the items and then clicking on the add to wish list button, they can also specify the quality of the items.



Sales Report Interface

The Cost CO application will allow administrator to view sales reports. It has the functionalities.

Project overview purpose


3.System requirement and

analysis


3.1 Project overview

online shopping are use the two mdules.general user will search for the processing its price & fill the cut accordinglyto proceed products& its quantity. Finally billing is made& shipping address is given to dispatch the order.

Finding a various products & there prices from given various categories & selecting the product for purchase.

Filling the cut shopping cart. Providing shipping details for order delivery.

The administration will maintaining product categories & adding a new product into these categories also updating the updates on day to day offers,monthlyoffers.manually purchase task for that physically have to go to market & purchase the product from there.shopping or purchase some items from home & get delivery at home.

Creating various product categories &adding product into there respective categories .

Generating new offers & showing them onwebpages . Changing rules & regulation for static files.

3.2PURPOSE OF THE SYSTEM:

The Cost Co application is an Online Website for an Organization. It

is a virtual showcase for different types of products like Books,

popular music, DVD, Apparel, Toys , Computers, sports, Software,



HealthCare, Jeweler , Kids Ware etc. The main aim of this project is

to make Online shopping very easily. The Special thing about this

project is it provides different types of products to purchase.

Technical Feasibility Operational Feasibility Economical Feasibility


4. FEASIBILITY STUDY


4.1 What is Feasibility?

Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation:

1) Technical Feasibility

2) Operational Feasibility

3) Economical Feasibility

4.2 Technical Feasibility

The technical issue usually raised during the feasibility stage of the investigation includes the following:Does the necessary technology exist to do what is suggested?

Do the proposed equipments have the technical capacity to hold the data required to use the new system?

Will the proposed system provide adequate response to inquiries, regardless of the number or location of users?

Can the system be upgraded if developed? Are there technical guarantees of accuracy, reliability, ease of

access and data security?

Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation System’. The current system developed is technically feasible. It is a web based user interface for audit workflow at NIC-CSD. Thus it provides an easy access to the users.



The database’s purpose is to create, establish and maintain a workflow among various entities in order to facilitate all concerned users in their various capacities or roles. Permission to the users would be granted based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability and security. The software and hard requirements for the development of this project are not many and are already available in-house at NIC or are available as free as open source. The work for the project is done with the current equipment and existing software technology. Necessary bandwidth exists for providing a fast feedback to the users irrespective of the number of users using the system.

4.3 Operational Feasibility

Proposed projects are beneficial only if they can be turned out into information system. That will meet the organization’s operating requirements. Operational feasibility aspects of the project are to be taken as an important part of the project implementation. Some of the important issues raised are to test the operational feasibility of a project includes the following: -

Is there sufficient support for the management from the users? Will the system be used and work properly if it is being

developed and implemented? Will there be any resistance from the user that will undermine

the possible application benefits?

This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the management issues and user requirements have been taken into consideration. So there is no question of resistance from the users that can undermine the possible application benefits.



The well-planned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status.

4.4 Economical Feasibility

A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility, the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. Financial benefits must equal or exceed the costs. The system is economically feasible. It does not require any addition hardware or software. Since the interface for this system is developed using the existing resources and technologies available at NIC, There is nominal expenditure and economical feasibility for certain.



Preliminary design Use cases Data flow diagrams Entity relationship diagram System tables

5.1 Preliminary system


5.System design


ARCHITECTURAL FLOW

The current application is being developed by taking the 3-tier

architecture as a prototype. The 3-tier architecture is the most

common approach used for web applications today. In the typical

example of this model, the web browser acts as the client, IIS handles

the business logic, and a separate tier MS-SQL Server handles

database functions.

Although the 3-tier approach increases scalability and

introduces a separation of business logic from the display and

database layers, it does not truly separate the application into

specialized, functional layers. For prototype or simple web

applications, the 3-tier architecture may be sufficient. However, with

complex demands placed on web applications, a 3-tiered approach

falls short in several key areas, including flexibility and scalability.

These shortcomings occur mainly because the business logic tier is

still too broad- it has too many functions grouped into one tier that

could be separated out into a finer grained model.



The proposed system can be designed perfectly with the three tier

model, as all layers are perfectly getting set as part of the project. In

the future, while expanding the system, in order to implement

integration touch points and to provide enhanced user interfaces, the

n-tier architecture can be used. The following diagram will represent

the typical n-tier architecture.



5.2 USE CASE DIAGRAM:

Case diagram for admin


Add category


5.3 DATA FLOW DIAGRAMS :

Data flow diagrams (DFD) was first developed by LARRY CONSTANTINE as way representing system requirements in a graphical form; this lead to modular design. A DFD describes what data flow (logical) rather than how they are processed, so it does not depend on hardware, software, data structure or file organization. It is also known as ‘bubble chart’.


Admin

Add product

Add banner

Manufacture

Offers

News letters

Managing users

Transaction


A Data Flow Diagrams is a structured analysis and design tool that can be used for flowcharting in place of, or in association with, information-oriented and process-oriented systems flowcharts. A DFD is a network that describes the flow of data and the processes that change, or transform, data throughout a system. This network is constructed by using a set of symbols that do not imply a physical implementation. It has the purpose of clarifying system requirements and identifying major transformations that will become programs in system design. So it is the starting point of the design phase that functionality decomposes the requirement specifications down to the lowest level of detail. 20 The symbols used to prepare DFD do not imply a physical implementation, a DFD can be considered to an abstract of the logic of an information-oriented or a process-oriented system flow-chart. For these reasons DFDs are oftenreferred to as logical data flow diagrams. The four basic symbols used to construct data flow diagrams are shown below:

A rectangle represents a data source or destination.

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

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



An open-ended rectangle represents data storage

These are symbols that represent data flows, data sources, data transformations and data storage. The points at which data are transformed are represented by enclosed figures, usually circles, which are called nodes.

CONTEXT LEVEL DFD

Context Flow Diagram

admindfd


USER

COST Co- A Shoppers

ParadiseADMINISTRATOR

Admin Login

Category

Produt

Banner

Manufat

Offer

News letter

User

tranctionStatic files

Home page

Log out

Categor

Product table

Banner

manufact

offer

User table

Transction

Static

logout

News letter


User dfd

Open home pageselect the

Next product

5.4Entity Relationship Diagram: ACESOFT Consulting Page 27

user Home page

See the product

Add the cart

Checkout

Shipping address

Shop by


Login

Open home

Categories next product

Selectthe product


User ID

Online Shopping System

Home

Produ

UsePr

Pro

pric

man

im

keofferShi

disc

Bes

Cat

C des Pa

HM

Home

Shop by category

Add the

checkoShip

Password


System tables:

1.Login

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSUser_id int Primary keyUsername Nvarchar(20) Not nullPassword Nvarchar(10) Not null

2.Category_info table

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYS ACESOFT Consulting Page 29


Cat_id Int Primary keyCat_name Nvarchar(30) Not nullCat_desc Nvarchar2(100) Not nullParent_id Int Not nullHas_sub Int Not nullMain_category bit Not null

3.Product_info

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSProduct_Id Int Primary keyCat_Id Int Primary keyProduct_Code Nvarchar(10) Not nullProduct_Name Nvarchar(100) Not nullProduct_Desc Nvarchar(2500) Not nullPrice Nvarchar(50) Not nullDiscount Float Not nullShip_Charges Float Not nullTax Float Not nullManufacturer Nvarchar(50) Not nullKeywords Nvarchar(200) Not nullActive Bit Not nullNew_Arrival Bit Not nullImagePath Nvarchar(50) Not nullOffer1 Bit Not nullOffer2 Bit Not nullOffer3 Bit Not nullfeatured_product Bit Not nullbest_seller Bit Not null

4.Product_ attribute

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE Keys ACESOFT Consulting Page 30


att_id Int Primary keyatt_name Nvarchar(100) Not nullatt_value Nvarchar(200) Not nullproduct_code Nvarchar(10) Not null

5.free Product

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSfreeProudct_Id Int Primary keyfProduct_Id Int Primary keyfProduct_Name Nvarchar(50) Not nullfProduct_Price Float Not nullfProduct_Desc Nvarchar(300) Not nullfImagePath Nvarchar(50) Not nullfActive bit Not null

6.Key features

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSKey_id Int Primary keyKey_Feature Nvarchar(500) Not nullProduct_Code Nvarchar(10) Not null

7.Admin banner

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSBanner_Id Int Primary keyBanner_Name Nvarchar(50) Not nullBanner_Url Nvarchar(100) Not nullBanner_Path Nvarchar(50) Not nullBanner_Position Int Not nullStatus Bit Not null

8.Manufacture



DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSManufacturer_Id Int Primary keyManufacturer_Name Nvarchar(50) Not null

9.special offers

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSSpecial_id Int Primary keySpecial_Name Nvarchar(50) Not nullSpecial_Desc Nvarchar(100) Not nullSpecial_Path Nvarchar(50) Not nullSpecial_Position Int Not nullStatus bit Not null

10.Order

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSid Int Primary keyorderid Nvarchar(50) Not nulluserid Int Not nullshipping int Not nulltotal Decimal(18,0) Not nullorderdate Datetime Not nullxid Nvarchar(100) Not nullstatus Nvarchar(10) Not null

11.order product

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSid Int Primary keyorderid Nvarchar(100) Not null



productid Int Not nullproductname Nvarchar(100) Not nullamount Decimal(18,0) Not nullshipping Decimal(18,0) Not nulldiscount Decimal(18,0) Not nullorderdate Datetime Not nullstatus Bit Not null

12.Registration

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSReg_Id Int (5) Primary keyTitle Nvarchar(50) Not nullFirst_Name Nvarchar(50) Not nullLast_Name Nvarchar(50) Not nullEmail Nvarchar(50) Not nullStreet Nvarchar(50) Not nullCity Nvarchar(50) Not nullState Nvarchar(50) Not nullCountry Nvarchar(50) Not nullPost_Code Nvarchar(50) Not nullPhone Nvarchar(50) Not nullDay_Phone Nvarchar(50) Not nullEve_Phone Nvarchar(50) Not nullUsername Nvarchar(50) Not nullRPassword Nvarchar(50) Not nullTerms_Cond Int Not nullSend_Mails Int Not nullAcc_Type Nvarchar(100) Not nullStatus bit Not null

13.favourites

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSfav_id Int Primary keyuser_id Int Not nullproduct_id int Not null



14.specification

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSsp_id Int Primary keySpecification Nvarchar(500) Not nullProduct_Code Nvarchar(10) Not null

15.tempbanners

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSBanner_Id Int Primary keyBanner_Name Nvarchar(50) Not nullBanner_Name Nvarchar(50) Not nullBanner_Path Nvarchar(50) Not nullBanner_Position Int Not nullStatus bit Not null

16.tempmails

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSemail_id Int Primary keytitle Navrchar(50) Not nullfirst_name Nvarchar(50) Not null



last_name Nvarchar(50) Not nullemailid Nvarchar(50) Not null

17.shipdetails

DATA NAMES DATA INTEGRITY CONSTRAINTSFIFLEDS DATA TYPE KEYSShip_Id int Primary keyReg_Id Navrchar(50) Not nullShip_Name Navrchar(50) Not nullAddress1 Navrchar(50) Not nullAddress2 Navrchar(50) Not nullCity Navrchar(50) Not nullState Navrchar(50) Not nullCountry Navrchar(50) Not nullPhone Navrchar(20) Not nullZip Navrchar(20) Not nullFax Navrchar(20) Not nullEmail Navrchar(50) Not null



6.software development

Technology used

System requirement

6.SOFTWARE DEVELOPMENT

Technology used:



Microsoft.NET Framework

The .NET Framework is a new computing platform that

simplifies application development in the highly distributed

environment

To provide a consistent object-oriented

programming environment whether object code is

stored and executed locally, executed locally but

Internet-distributed, or executed NET.

To provide a code-execution environment that

minimizes software deployment and versioning

conflicts.


guarantees safe execution of code, including code

created by an unknown or semi-trusted third party.


eliminates the performance problems of scripted or

interpreted environments.

To build all communication on industry standards to

ensure that code based on the .NET Framework can

integrate with any other code.

The .NET Framework has two main components: the common

language runtime and the .NET Framework class library. The

common language runtime is the foundation of the .NET

Framework. You can think of the runtime as an agent that

manages code at execution time, providing core services such

as memory management, thread management, and remoting,

while also enforcing strict type safety and other forms of code



accuracy that ensure security and robustness. In fact, the

concept of code management is a fundamental principle of the

runtime. Code that targets the runtime is known as managed

code, while code that does not target the runtime is known as

unmanaged code. The class library, the other main component

of the .NET Framework, is a comprehensive, object-oriented

collection of reusable types that you can use to develop

applications ranging from traditional command-line or graphical

user interface (GUI) applications to applications based on the

latest innovations provided by ASP.NET, such as Web Forms

and XML Web services.

The .NET Framework can be hosted by unmanaged components

that load the common language runtime into their processes

and initiate the execution of managed code, thereby creating a

software environment that can exploit both managed and

unmanaged features. The .NET Framework not only provides

several runtime hosts, but also supports the development of

third-party runtime hosts.

For example, ASP.NET hosts the runtime to provide a scalable,

server-side environment for managed code. ASP.NET works

directly with the runtime to enable Web Forms applications and

XML Web services, both of which are discussed later in this

topic.

Internet Explorer is an example of an unmanaged application

that hosts the runtime (in the form of a MIME type extension).

Using Internet Explorer to host the runtime enables you to

embed managed components or Windows Forms controls in

HTML documents. Hosting the runtime in this way makes

managed mobile code (similar to Microsoft® ActiveX®



controls) possible, but with significant improvements that only

managed code can offer, such as semi-trusted execution and

secure isolated file storage.

The following illustration shows the relationship of the common

language runtime and the class library to your applications and

to the overall system. The illustration also shows how managed

code operates within a larger architecture.

FEATURES OF THE COMMON LANGUAGE RUNTIME

The common language runtime manages memory, thread

execution, code execution, code safety verification,

compilation, and other system services. These features are

intrinsic to the managed code that runs on the common

language runtime.

With regards to security, managed components are awarded

varying degrees of trust, depending on a number of factors that

include their origin (such as the Internet, enterprise network, or

local computer). This means that a managed component might

or might not be able to perform file-access operations, registry-

access operations, or other sensitive functions, even if it is

being used in the same active application.

The runtime enforces code access security. For example, users

can trust that an executable embedded in a Web page can play

an animation on screen or sing a song, but cannot access their

personal data, file system, or network. The security features of

the runtime thus enable legitimate Internet-deployed software

to be exceptionally feature rich.

The runtime also enforces code robustness by

implementing a strict type- and code-verification



infrastructure called the common type system (CTS).

The CTS ensures that all managed code is self-

describing. The various Microsoft and third-party

language compilers generate managed code that

conforms to the CTS. This means that managed code can

consume other managed types and instances, while

strictly enforcing type fidelity and type safety.

In addition, the managed environment of the runtime

eliminates many common software issues. For example, the

runtime automatically handles object layout and manages

references to objects, releasing them when they are no longer

being used. This automatic memory management resolves the

two most common application errors, memory leaks and invalid

memory references.

The runtime also accelerates developer productivity. For

example, programmers can write applications in their

development language of choice, yet take full advantage of the

runtime, the class library, and components written in other

languages by other developers. Any compiler vendor who

chooses to target the runtime can do so. Language compilers

that target the .NET Framework make the features of the .NET

Framework available to existing code written in that language,

greatly easing the migration process for existing applications.

While the runtime is designed for the software of the future, it

also supports software of today and yesterday. Interoperability

between managed and unmanaged code enables developers to

continue to use necessary COM components and DLLs.

The runtime is designed to enhance performance. Although the

common language runtime provides many standard runtime



services, managed code is never interpreted. A feature called

just-in-time (JIT) compiling enables all managed code to run in

the native machine language of the system on which it is

executing. Meanwhile, the memory manager removes the

possibilities of fragmented memory and increases memory

locality-of-reference to further increase performance.

Finally, the runtime can be hosted by high-performance, server-

side applications, such as Microsoft® SQL Server™ and Internet

Information Services (IIS). This infrastructure enables you to

use managed code to write your business logic, while still

enjoying the superior performance of the industry's best

enterprise servers that support runtime hosting.

.NET FRAMEWORK CLASS LIBRARY

The .NET Framework class library is a collection of

reusable types that tightly integrate with the common

language runtime. The class library is object oriented,

providing types from which your own managed code can

derive functionality. This not only makes the .NET

Framework types easy to use, but also reduces the time

associated with learning new

features of the .NET Framework. In addition, third-party

components can integrate seamlessly with classes in the .NET

Framework.

For example, the .NET Framework collection classes implement

a set of interfaces that you can use to develop your own



collection classes. Your collection classes will blend seamlessly

with the classes in the .NET Framework.

As you would expect from an object-oriented class library,

the .NET Framework types enable you to accomplish a range of

common programming tasks, including tasks such as string

management, data collection, database connectivity, and file

access. In addition to these common tasks, the class library

includes types that support a variety of specialized

development scenarios. For example, you can use the .NET

Framework to develop the following types of applications and

services:

Console applications.

Scripted or hosted applications.

Windows GUI applications (Windows Forms).

ASP.NET applications.

XML Web services.

Windows services.

For example, the Windows Forms classes are a comprehensive

set of reusable types that vastly simplify Windows GUI

development. If you write an ASP.NET Web Form application,

you can use the Web Forms classes.

CLIENT APPLICATION DEVELOPMENT

Client applications are the closest to a traditional style of

application in Windows-based programming. These are the

types of applications that display windows or forms on the

desktop, enabling a user to perform a task. Client applications

include applications such as word processors and spreadsheets,

as well as custom business applications such as data-entry

tools, reporting tools, and so on. Client applications usually



employ windows, menus, buttons, and other GUI elements, and

they likely access local resources such as the file system and

peripherals such as printers.

Another kind of client application is the traditional ActiveX

control (now replaced by the managed Windows Forms control)

deployed over the Internet as a Web page. This application is

much like other client applications: it is executed natively, has

access to local resources, and includes graphical elements.

In the past, developers created such applications using C/C++

in conjunction with the Microsoft Foundation Classes (MFC) or

with a rapid application development (RAD) environment such

as Microsoft® Visual Basic®. The .NET Framework incorporates

aspects of these existing products into a single, consistent

development environment that drastically simplifies the

development of client applications.

The Windows Forms classes contained in the .NET Framework

are designed to be used for GUI development. You can easily

create command windows, buttons, menus, toolbars, and other

screen elements with the flexibility necessary to accommodate

shifting business needs.

For example, the .NET Framework provides simple properties to

adjust visual attributes associated with forms. In some cases

the underlying operating system does not support changing

these attributes directly, and in these cases the .NET

Framework automatically recreates the forms. This is one of

many ways in which the .NET Framework integrates the

developer interface, making coding simpler and more

consistent.



Unlike ActiveX controls, Windows Forms controls have semi-

trusted access to a user's computer. This means that binary or

natively executing code can access some of the resources on

the user's system (such as GUI elements and limited file

access) without being able to access or compromise other

resources. Because of code access security, many applications

that once needed to be installed on a user's system can now be

safely deployed through the Web. Your applications can

implement the features of a local application while being

deployed like a Web page.

CLIENT APPLICATION DEVELOPMENT

Client applications are the closest to a traditional style of

application in Windows-based programming. These are the

types of applications that display windows or forms on the

desktop, enabling a user to perform a task. Client applications

include applications such as word processors and spreadsheets,

as well as custom business applications such as data-entry

tools, reporting tools, and so on. Client applications usually

employ windows, menus, buttons, and other GUI elements, and

they likely access local resources such as the file system and

peripherals such as printers.

Another kind of client application is the traditional ActiveX

control (now replaced by the managed Windows Forms control)

deployed over the Internet as a Web page. This application is

much like other client applications: it is executed natively, has

access to local resources, and includes graphical elements.



In the past, developers created such applications using C/C++

in conjunction with the Microsoft Foundation Classes (MFC) or

with a rapid application development (RAD) environment such

as Microsoft® Visual Basic®. The .NET Framework incorporates

aspects of these existing products into a single, consistent

development environment that drastically simplifies the

development of client applications.

The Windows Forms classes contained in the .NET Framework

are designed to be used for GUI development. You can easily

create command windows, buttons, menus, toolbars, and other

screen elements with the flexibility necessary to accommodate

shifting business needs.

For example, the .NET Framework provides simple properties to

adjust visual attributes associated with forms. In some cases

the underlying operating system does not support changing

these attributes directly, and in these cases the .NET

Framework automatically recreates the forms. This is one of

many ways in which the .NET Framework integrates the

developer interface, making coding simpler and more

consistent.

Unlike ActiveX controls, Windows Forms controls have semi-

trusted access to a user's computer. This means that binary or

natively executing code can access some of the resources on

the user's system (such as GUI elements and limited file

access) without being able to access or compromise other

resources. Because of code access security, many applications

that once needed to be installed on a user's system can now be

safely deployed through the Web. Your applications can ACESOFT Consulting Page 45


implement the features of a local application while being

deployed like a Web page.

SERVER APPLICATION DEVELOPMENT

Server-side applications in the managed world are

implemented through runtime hosts. Unmanaged applications

host the common language runtime, which allows your custom

managed code to control the behavior of the server. This model

provides you with all the features of the common language

runtime and class library while gaining the performance and

scalability of the host server.

The following illustration shows a basic network schema with

managed code running in different server environments.

Servers such as IIS and SQL Server can perform standard

operations while your application logic executes through the

managed code.

Server-side managed code

ASP.NET is the hosting environment that enables developers to

use the .NET Framework to target Web-based applications.

However, ASP.NET is more than just a runtime host; it is a

complete architecture for developing Web sites and Internet-

distributed objects using managed code. Both Web Forms and

XML Web services use IIS and ASP.NET as the publishing

mechanism for applications, and both have a collection of

supporting classes in the .NET Framework.

XML Web services, an important evolution in Web-based

technology, are distributed, server-side application components



similar to common Web sites. However, unlike Web-based

applications, XML Web services components have no UI and are

not targeted for browsers such as Internet Explorer and

Netscape Navigator. Instead, XML Web services consist of

reusable software components designed to be consumed by

other applications, such as traditional client applications, Web-

based applications, or even other XML Web services. As a

result, XML Web services technology is rapidly moving

application development and deployment into the highly

distributed environment of the Internet.

If you have used earlier versions of ASP technology, you will

immediately notice the improvements that ASP.NET and Web

Forms offers. For example, you can develop Web Forms pages

in any language that supports the .NET Framework. In addition,

your code no longer needs to share the same file with your

HTTP text (although it can continue to do so if you prefer). Web

Forms pages execute in native machine language because, like

any other managed application, they take full advantage of the

runtime. In contrast, unmanaged ASP pages are always scripted

and interpreted. ASP.NET pages are faster, more functional,

and easier to develop than unmanaged ASP pages because

they interact with the runtime like any managed application.

The .NET Framework also provides a collection of classes and

tools to aid in development and consumption of XML Web

services applications. XML Web services are built on standards

such as SOAP (a NET procedure-call protocol), XML (an

extensible data format), and WSDL ( the Web Services

Description Language). The .NET Framework is built on these



standards to promote interoperability with non-Microsoft

solutions.

For example, the Web Services Description Language tool

included with the .NET Framework SDK can query an XML Web

service published on the Web, parse its WSDL description, and

produce C# or Visual Basic source code that your application

can use to become a client of the XML Web service. The source

code can create classes derived from classes in the class library

that handle all the underlying communication using SOAP and

XML parsing. Although you can use the class library to consume

XML Web services directly, the Web Services Description

Language tool and the other tools contained in the SDK

facilitate your development efforts with the .NET Framework.

If you develop and publish your own XML Web service, the .NET

Framework provides a set of classes that conform to all the

underlying communication standards, such as SOAP, WSDL,

and XML. Using those classes enables you to focus on the logic

of your service, without concerning yourself with the

communications infrastructure required by distributed software

development.

Finally, like Web Forms pages in the managed environment,

your XML Web service will run with the speed of native machine

language using the scalable communication of IIS.

SQL SERVER 2005

SQL Server is a relational database management system RDBMS from Microsoft that's designed for the enterprise environment. SQL Server runs on T-SQL (Transact -SQL), a set of programming extensions from Sybase and Microsoft that add several features to standard


http://searchenterpriselinux.techtarget.com/definition/Sybase

http://searchcio-midmarket.techtarget.com/definition/extension

http://searchsqlserver.techtarget.com/definition/SQL

http://searchsqlserver.techtarget.com/definition/T-SQL

http://searchwinit.techtarget.com/definition/enterprise

http://searchwinit.techtarget.com/definition/Microsoft


SQL, including transaction control, exception and error handling, row processing, and declared variables.

Code named Yukon in development, SQL Server 2005 was released in November 2005. The 2005 product is said to provide enhanced flexibility, scalability, reliability, and security to database applications, and to make them easier to create and deploy, thus reducing the complexity and tedium involved in database management. SQL Server 2005 also includes more administrative support.

The original SQL Server code was developed by Sybase; in the late 1980s, Microsoft, Sybase and Ashton-Tate collaborated to produce the first version of the product, SQL Server 4.2 for OS/2. Subsequently, both Sybase and Microsoft offered SQL Server products. Sybase has since renamed their product Adaptive Server Enterprise.

In the business world, everything is about being "better, faster and cheaper" than the competition -- and SQL Server 2005 offers many new features to save energy, time and money. From programming to administrative capabilities, this version of SQL Server tops all others and it enhances many existing SQL Server 2000 features. Here I'll outline the 10 most significant new features in order of importance:

1. T-SQL (Transaction SQL) enhancementsT-SQL is the native set-based RDBMS programming language offering high-performance data access. It now incorporates many new features including error handling via the TRY and CATCH paradigm, Common Table Expressions (CTEs), which return a record set in a statement, and the ability to shift columnsto rows and vice versa with the PIVOT and UNPIVOT commands.

2. CLR (Common Language Runtime)The next major enhancement in SQL Server 2005 is the integration of a .NET compliant language such as C#, ASP.NET or VB.NET to build objects (stored procedures, triggers, functions, etc.). This enables you to execute .NET code in the DBMS to take advantage of the .NET functionality. It is expected to replace extended stored procedures in the SQL Server 2000 environment as well as expand the traditional relational engine capabilities.

3. Service BrokerThe Service Broker handles messaging between a sender and receiver in a loosely coupled manner. A message is sent, processed and responded to, completing the transaction. This greatly expands the capabilities of data-driven applications to meet workflow or custom business needs.

4. Data encryptionSQL Server 2000 had no documented or publicly supported functions to encrypt data in

a table natively. Organizations had to rely on third-party products to address this need. SQL Server 2005 has native capabilities to support encryption of data stored in user-defined databases.

5. SMTP mailSending mail directly from SQL Server 2000 is possible, but challenging. With SQL


http://whatis.techtarget.com/definition/0,,sid9_gci1131078,00.html

http://searchwinit.techtarget.com/definition/Microsoft


http://searchsqlserver.techtarget.com/definition/database-management-system

http://searchsqlserver.techtarget.com/definition/database

http://searchsecurity.techtarget.com/definition/security

http://searchdatacenter.techtarget.com/definition/scalability

http://searchsqlserver.techtarget.com/definition/Yukon


http://searchsoftwarequality.techtarget.com/definition/error-handling


Server 2005, Microsoft incorporates SMTP mail to improve the native mail capabilities. Say "see-ya" to Outlook on SQL Server!

6. HTTP endpointsYou can easily create HTTP endpoints via a simple T-SQL statement exposing an object that can be accessed over the Internet. This allows a simple object to be called across the Internet for the needed data.

7. Multiple Active Result Sets (MARS)MARS allow a persistent database connection from a single client to have more than one active request per connection. This should be a major performance improvement, allowing developers to give users new capabilities when working with SQL Server. For example, it allows multiple searches, or a search and data entry. The bottom line is that one client connection can have multiple active processes simultaneously.

8. Dedicated administrator connectionIf all else fails, stop the SQL Server service or push the power button. That mentality is finished with the dedicated administrator connection. This functionality will allow a DBA to make a single diagnostic connection to SQL Server even if the server is having an issue.

9. SQL Server Integration Services (SSIS)SSIS has replaced DTS (Data Transformation Services) as the primary ETL (Extraction, Transformation and Loading) tool and ships with SQL Server free of charge. This tool, completely rewritten since SQL Server 2000, now has a great deal of flexibility to address complex data movement.

10. Database mirroringIt's not expected to be released with SQL Server 2005 at the RTM in November, but I think this feature has great potential. Database mirroring is an extension of the native high-availability capabilities. So, stay tuned for more details…. For now, here's

Two technologies that cannot be left out of any SQL Server 2005 top 10 list are Analysis Services and Reporting Services. Although neither technology will be introduced with SQL Server 2005, combining them with SQL Server Integration Services rounds off Microsoft's core business intelligence suite. These technologies are essential to business intelligence success. Learn about the new functionality and how organizations are implementing it with Project Real.

1. Requirements:

Hardware requirements:

Content Description

HDD 20 GB Min

40 GB Recommended



RAM 1 GB Min

2 GB Recommended

Software requirements:

Content Description

OS Windows XP with SP2 or Windows Vista

Database MS-SQL server 2005

Technologies ASP.NET with VB.NET

IDE Ms-Visual Studio .Net 2008

Browser IE



7.SOFTWARE TESTING

Unit Testing Integration Testing Validation Testing Black Box Testing White Box Testing Acceptance Testing



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

7.1 UNIT TESTING:

The primary goal of unit testing is to take the smallest piece of testable software in the application, isolate it from the remainder of the code, and determine whether it behaves exactly as you expect. Each unit is tested separately before integrating them into modules to test the interfaces between modules. Unit testing has proven its value in that a large percentage of defects are identified during its use.

Unit testing is a software verification and validation method where the programmer gains confidence that individual units of source code are fit for use. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual program, function, procedure, etc., while in object-oriented programming, the smallest unit is a class, which may belong to a base/super class, abstract class or derived/child class. Ideally, each test case is independent from the others: substitutes like method stubs, mock objects, fakes and test harnesses can be used to assist testing a module in isolation. Unit tests are typically written and run by software developers to ensure that code meets its design and behaves as



intended. Its implementation can vary from being very manual (pencil and paper) to being formalized as part of build automation.

7.2 INTEGRATION TESTING

Integration testing, also known as integration and testing (I&T), is a software development process which program units are combined and tested as groups in multiple ways. In this context, a unit is defined as the smallest testable part of an application. Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution. Integration testing is a component of Extreme Programming (XP), a pragmatic method of software development that takes a meticulous approach to building a product by means of continual testing and revision. There are two major ways of carrying out an integration test, called the bottom-up method and the top-down method. Bottom-up integration testing begins with unit testing, followed by tests of progressively higher-level combinations of units called modules or builds. In top-down integration testing, the highest-level modules are tested first and progressively lower-level modules are tested after that. In a comprehensive software development environment, bottom-up testing is usually done first, followed by top-down testing.

7.3 VALIDATION TESTING

At the validation level, testing focuses on user visible actions and user recognizable output from the system. Validations testing is said to be successful when software functions in a manner that can be reasonably expected by the customer. Two types of validation testing Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers' site. Alpha testing is often employed for off-the-



shelf software as a form of internal acceptance testing, before the software goes to beta testing.

Beta testing comes after alpha testing. Versions of the software, known as beta version, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Sometimes, beta versions are made available to the open public to increase the feedback field to a maximal number of future users

Gray box testing Grey box testing is the combination of black box and white box testing. Intention of this testing is to find out defects related to bad design or bad implementation of the system.it is used for web application



9.LIMITATION& CONCLUSION

Prominent features of the system Future Enhancement Conclusion



9.1 Prominent features of the system

The Features provided by the Project are as follows.

For accessing SQL Server from other machines in the network The Internet Appliances takes care of the requirements put

forward by the customers through web. Shows the information and description of the products. Provides the searching facilities based on various factors. Sells the Products online. Keeps track of the Transaction. It deals with monitoring the information and transactions. Managing the suppliers of raw materials to the companies. Provides the administrator facilities to update the list of

products online without FTP. Provides the Credit Card interface for accepting and validating

various Credit Cards through the Banks. Take care Securities for the Credit Card information. User trusted site.

9.3 future Enhancement



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

Conclusion:

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



10.REFERENCES

Books

websites



System Analysis and Design

Senn

Database System Design

Elmasree

Korth


dhani2

Documents

unlike activex controls

adjust visual attributes

native machine language

accommodate shifting business

ace soft consulting

traditional activex control

making coding simpler

nahata commerce college