2. INTRODUCTION 2.1. ORGANIZATION PROFILE H-LINE SOFT INFORMATION TECHNOLOGIES Pvt.

Ltd
We started in 2000 as a team in New York of web designing software development research over this year; we have evolved into an end-to-end e-business solutions and software development company, catering to 500-plus global clientele across major industry verticals. HLine Soft IT has averaged 100% annual growth in terms of revenue, profits, turnover and client base. Since its inception in 2000, H-Line soft has provided a wide array of e-nnovative ebusiness solutions and services including Web solutions, and business process automation tools to "e"power business custom software/Web applications developments across the globe. H-line Soft the offshore development/out sourcing requirements of top 10 global IT/Web solutions companies. And our Exports Division is a 100% EOU (Export Oriented Unit), registered with the Software Technology Parks of India (STPI).

BUSINESS ACTIVITIES
H-LINE prepared to deliver the complete set of services required for enabling Information Technology business solutions:

Strategic Business Units:

ITO (Information Technology Outsourcing) BPO (Business Process Outsourcing) Software Development Consulting Academy of Excellence The Global Development Center (Hyderabad Unit) has a team of over 40 professionals and 10 executives, located at completely equipped premises with a built up area of 5000 Sq. ft. with suitable facilities for Software Development and IT Enabled Services.

2.2. OVERVIEW OF THE PROJECT 1. 2.

This is about one of the Silk ware Companies. As it is a traditional business, the companys business processes only rely on the manual work. Currently, the some companies has encountered problem in promoting its garments. One of the main problems is to advertise its products to the big cities, as market is becoming more prosperous, the number of competitors has also increased. Therefore the company has to make some changes and improvements with the help of IT. In the proposed E-commerce website, there will be two main users & administrators and the customers. The administrators will maintain and update the website with latest information while the customers can only view the information available on the website, make payments online or register as a member and enjoy its privileges. The proposed E-commerce website will help both company and their customers when they make transactions Advances in technology and the growth of E-commerce Services to provide online shopping with unique opportunities to enhance buying and viewing the products in higher level. This application serves as a forum to facilitate the exchange of information on the current research, development, and practice of E-Commerce sectors. This project gives the information about the Individual Product Informations, Calendar events, Fee structures and details for the particular course. Business to customer gives the information about the products listing which are relevant to the particular Categories. This project provides facility to the users for registering for the website and without the registration the user can have the facility to buy the products. Using the project the user can view the large scale image of the products and user will view the calendar events posted by the administrator. This project provide the information about the number of HITS of the current website to the administrator. 2

3.

4.

5.

2.3. MODULES
There are 2 main Modules in the project they are: Customer Module
o Customer can register online. o Customer can login using user name and password. o Can buy stocks. o Can view stocks available. o Can update Profile. o Can buy online through the PayPal.

Administrator Module
o Can login using User Name and Password. o Multi users can be provided for the admin. o View the complete list of customers or the users. o Registration details will be send to the users. o Activate or deactivate the user who unsubscribe. o Can view the ordered details of the users with all the items. o Can update the text in all pages using text editors. o Can add edit and delete the events using calendar application. o Can have the alerts for the events. o Can have the complete rights to add, edit, delete categories, Sub-Categories, products. o View and reply Feedback for the users or customers.

3. HARDWARE AND SOFTWARE REQUIREMENTS

Hardware Requirements:
Pentium lll processor(500MHz) or Above. 128MB RAM or Above.

8 GB Hard Disk or Above. Software Requirements:

Operating System Front-End Back-End Documentation tool AJAX 1.0. : Windows 2000/xp. : ASP.NET with C# coding. : SQL Server 2000.

IIS 5.0(internet information services). : MS- Word 2007.

4. Design Principles And Maintenance

DESIGN PRINCIPLES AND MAINTENANCE: SYSTEM DESIGN:
The purpose of the design phase is to plan a solution of the problem specified by the requirement document. This phase is the first step in moving from the problem domain to the solution domain. In other words, starting with what is needed; design takes us toward how to satisfy the needs. The design of a system is perhaps the most critical factor affection the quality of the software; it has a major impact on the later phases, particularly testing, maintenance. The output of this phase is the design document. This document is similar to a blueprint for the solution and is used later during implementation, testing and maintenance. The design activity is often divided into two separate phases System Design & Detailed Design. (REFERENCED from Introduction to System Analysis and Design by--I.T.Hawryskiewcz) System Design also called top-level design aims to identify the modules that should be in the system, the specifications of these modules, and how they interact with each other to produce the desired results. At the end of the system design all the major data structures, file formats, output formats, and the major modules in the system and their specifications are decided. During Detailed Design, the internal logic of each of the modules specified in system design is decided. During this phase, the details of the data structures and algorithmic design of each of the modules is specified. The logic of a module is usually specified in a high-level design description language, which is independent of the target language in which the software will eventually be implemented. In system design the focus is on identifying the modules, whereas during detailed design the focus is on designing the logic for each of the modules. In other words, in system design the attention is on what components are needed, while in detailed design how the components can be implemented in software is the issue.

METHODOLOGY:
The potential objects required are thoroughly analyzed for identifying the class types, class hierarchies etc. Having identified the class hierarchies the screens to be displayed are identified to see weather the system is behaving the way it should, giving the required results after feeding the required input. Therefore the classes are individually tested and subsequently integrated to form the overall system. . (REFERENCED from Introduction to System Analysis and Design by---I.T.Hawryskiewcz)

SYSTEM MAINTENANCE:
As the number of computer based systems, grieve libraries of computer software began to expand. In house developed projects produced tones of thousand software program statements. Software products purchased from the outside added hundreds and thousands of new statements. A dark cloud appeared on the horizon. All of these programs, all of these source statements had to be corrected when false were detected, modified as user requirements changed, or adapted to new hardware that was purchased. These activities were collectively called software maintenance.(REFERENCED from Software Engineering - A Practitioners Approach by---Roger S. Pressman). The maintenance phase focuses on change that is associated with error correction, adaptations required as the softwares environment evolves, and changes due to enhancements brought about by changing customer requirements.

5. CONCEPTS AND TECHNIQUES

Microsoft.NET Framework
The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the following objectives:

To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely. To provide a code-execution environment that minimizes software deployment and versioning conflicts. To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semi-trusted third party. To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments. To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications. To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code. (REFERENCED from Professional ASP.Net 1.0 by Wrox)

The .NET Framework has two main components: 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 following illustration shows the relationship of the common language runtime and the class library to your applications and to the overall system.

.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. (REFERENCED from Professional ASP.Net 1.0 by Wrox) 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. 9

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

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. (REFERENCED from Professional ASP.Net 1.0 by Wrox) 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.

10

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

11

.Net C# Tutorial Namespaces

A Namespace in Microsoft .Net is like containers of objects. They may contain unions, classes, structures, interfaces, enumerators and delegates. Main goal of using namespace in .Net is for creating a hierarchical organization of program. In this case a developer does not need to worry about the naming conflicts of classes, functions, variables etc., inside a project. In Microsoft .Net, every program is created with a default namespace. This default namespace is called as global namespace. But the program itself can declare any number of namespaces, each of them with a unique name. The advantage is that every namespace can contain any number of classes, functions, variables and also namespaces etc., whose names are unique only inside the namespace. The members with the same name can be created in some other namespace without any compiler complaints from Microsoft .Net. (REFERENCED from MSDN 2002) To declare namespace C# .Net has a reserved keyword namespace. If a new project is created in Visual Studio .NET it automatically adds some global namespaces. These namespaces can be different in different projects. But each of them should be placed under the base namespace System. The names space must be added and used through the using operator, if used in a different project.

INTRODUCTION TO ADO.NET:
Overview of ADO.NET:
ADO.NET provides consistent access to data sources such as Microsoft SQL Server, as well as data sources exposed through OLE DB and XML. Data-sharing consumer applications can use ADO.NET to connect to these data sources and retrieve, manipulate, and update data. ADO.NET cleanly factors data access from data manipulation into discrete components that can be used separately or in tandem. ADO.NET includes .NET Framework data providers for connecting to a database, executing commands, and retrieving results. Those results are either processed directly, or placed in an ADO.NET DataSet object in order to be exposed to the user in an ad-hoc manner, combined with data from multiple sources, or remoted between tiers. The

12

ADO.NET DataSet object can also be used independently of a .NET Framework data provider to manage data local to the application or sourced from XML. The ADO.NET classes are found in System.Data.dll, and are integrated with the XML classes found in System.Xml.dll. When compiling code that uses the System.Data namespace, reference both System.Data.dll and System.Xml.dll. For an example of compiling an ADO.NET application using a command line compiler, see ADO.NET Sample Application. ADO.NET provides functionality to developers writing managed code similar to the functionality provided to native COM developers by ADO. ADO.NET is a set of classes that expose data access services to the .NET programmer. It provides a rich set of components for creating distributed, data-sharing applications. It is an integral part of the .NET Framework, providing access to relational data, XML, and application data. Furthermore, it was designed to meet the needs of modern applications: disconnected data architecture, tight integration with XML, and common data representation with the ability to combine data from multiple and varied data sources. ADO.NET supports a variety of development needs, including the creation of front-end database clients and middle-tier business objects. It provides consistent access to data sources such as SQL Server, as well as data sources exposed through OLE DB and XML.

XML and ADO.NET

ADO.NET leverages the power of XML to provide disconnected access to data. ADO.NET was designed hand-in-hand with the XML classes in the .NET Framework both are components of a single architecture. (REFERENCED from Professional ASP.Net 1.0 by Wrox) ADO.NET and the XML classes in the .NET Framework converge in the DataSet object. The DataSet can be populated with data from an XML source, whether it is a file or an XML stream. The DataSet can be written as World Wide Web Consortium (W3C) compliant XML, including its schema as XML Schema definition language (XSD) schema, regardless of the source of the data in the DataSet. Because the native serialization format of the DataSet is XML, 13

it is an excellent medium for moving data between tiers making the DataSet an optimal choice for remoting data and schema context to and from an XML Web service. The DataSet can also be synchronized with an XmlDataDocument to provide relational and hierarchical access to data in real time. For more information, see Synchronizing a DataSet with an XmlDataDocument.

ADO.NET Components
The ADO.NET components have been designed to factor data access from data manipulation. There are two central components of ADO.NET that accomplish this: the DataSet, and the .NET Framework data provider, which is a set of components including the Connection, Command, DataReader, and DataAdapter objects. The ADO.NET DataSet is the core component of the disconnected architecture of ADO.NET. The DataSet is explicitly designed for data access independent of any data source. As a result it can be used with multiple and differing data sources, used with XML data, or used to manage data local to the application. The DataSet contains a collection of one or more DataTable objects made up of rows and columns of data, as well as primary key, foreign key, constraint, and relation information about the data in the DataTable objects. The other core element of the ADO.NET architecture is the .NET Framework data provider, whose components are explicitly designed for data manipulation and fast, forwardonly, read-only access to data. The Connection object provides connectivity to a data source. The Command object enables access to database commands to return data, modify data, run stored procedures, and send or retrieve parameter information. The DataReader provides a highperformance stream of data from the data source. Finally, the DataAdapter provides the bridge between the DataSet object and the data source. The DataAdapter uses Command objects to execute SQL commands at the data source to both load the DataSet with data, and reconcile changes made to the data in the DataSet back to the data source. You can write .NET Framework data providers for any data source. The .NET Framework ships with two .NET Framework data providers: the .NET Framework Data Provider for SQL Server and the .NET Framework Data Provider for OLE DB.

14

ASP.NET AJAX - Introduction

ASP.NET AJAX, previously called "Atlas", is a Microsoft implementation of an AJAX based framework, created for ASP.NET (although it can be used on other platforms as well). AJAX stands for Asynchronous JavaScript and XML, which, very simply put, is a way of transferring data between the server and client without the sending the entire page, and thereby creating a complete postback. This allows for a richer experience for the user, since loading dynamic content can be done in the background, without refreshing and redrawing the entire page. If you have ever used Gmail or Outlook Web Access, you have used an Ajax enabled web application, and especially Google have made Ajax very popular. AJAX features in ASP.NET enable you to build rich Web applications that have many advantages over Web applications that are completely server-based.

AJAX-enabled applications offer: Improved efficiency, because significant parts of a Web page's processing are performed in the browser. Familiar UI elements such as progress indicators, tooltips, and pop-up windows. Partial-page updates that refresh only the parts of the Web page that have changed. Client integration with ASP.NET application services for forms authentication, roles, and user profiles. Auto-generated proxy classes that simplify calling Web service methods from client script. A framework that lets you customize of server controls to include client capabilities. Support for the most popular and generally used browsers, which includes Microsoft Internet Explorer, Mozilla Firefox, and Apple Safari.

15

Architecture of AJAX Features in ASP.NET

The architecture of AJAX features in ASP.NET consists of two pieces: client-script libraries and server components. These pieces are integrated to provide a robust development framework. ASP.NET AJAX client and server architecture

AJAX Client Architecture

The client architecture includes libraries for component support, browser compatibility, networking, and core services.

Components
Client components enable rich behaviors in the browser without postbacks.

Browser Compatibility
The browser compatibility layer provides AJAX scripting compatibility for the most frequently used browsers (including Microsoft Internet Explorer, Mozilla Firefox,

16

and Apple Safari). This enables you to write the same script regardless of which supported browser you are targeting.

Networking
The networking layer handles communication between script in the browser and Web-based services and applications. It also manages asynchronous remote method calls. In many common scenarios, such as partial-page updates that use the UpdatePanel

Debugging and Error Handling

The core services include the Sys.Debug class, which provides methods for displaying objects in readable form at the end of a Web page. The class also shows trace messages, enables you to use assertions, and lets you break into the debugger.

AJAX Server Architecture

The server pieces that support AJAX development consist of ASP.NET Web server controls and components that manage the UI and flow of an application. The server pieces also manage serialization, validation, control extensibility, and so on. There are also ASP.NET Web services that enable you to access ASP.NET application services for forms authentication, roles, and user profiles.

Script Support
AJAX features in ASP.NET are implemented by using supporting scripts that are sent from the server to the client. Depending on what AJAX features that you enable, different scripts are sent to the browser. Script support for AJAX in ASP.NET is used to provide two important features: The Microsoft AJAX Library, which is a type system and a set of JavaScript extensions that provide namespaces, inheritance, interfaces, enumerations, reflection, and additional features Partial-page rendering, which updates regions of the page by using an asynchronous postback.

Server Controls
ASP.NET AJAX server controls consist of server and client code that integrate to produce rich client behavior. When you add an AJAX control to an ASP.NET Web page, the page automatically sends supporting client script to the browser for AJAX 17

functionality. You can provide additional client code to customize the functionality of a control, but this is not required.

ScriptManager
Manages script resources for client components, partial-page rendering, localization, globalization, and custom user scripts. The ScriptManager control is required in order to use the UpdatePanel , UpdateProgress and Timer controls.

UpdatePanel
Enables you to refresh selected parts of the page, instead of refreshing the whole page by using a synchronous postback.

UpdateProgress
Provides status information about partial-page updates in UpdatePanel controls.

Timer
Performs postbacks at defined intervals. You can use the Timer control to post the whole page, or use it together with the UpdatePanel control to perform partial-page updates at a defined interval.

Specifying UpdatePanel Control Content

You add content to an UpdatePanel control declaratively or in the designer by using the ContentTemplate property. In markup, this property is exposed as a ContentTemplate element. To add content programmatically, you use the ContentTemplateContainer property. When a page that contains one or more UpdatePanel controls is first rendered, all the contents of the UpdatePanel controls are rendered and sent to the browser. On subsequent asynchronous postbacks, the content of individual UpdatePanel controls might be updated. Updates depend on the panel settings, on what element caused the postback, and on code that is specific to each panel.

18

UpdateProgress control
The UpdateProgress control provides status information about partial-page updates in UpdatePanel controls. You can customize the default content and the layout of the UpdateProgress control. To prevent flashing when a partial-page update is very fast, you can specify a delay before the UpdateProgress control is displayed.

ASP.NET AJAX Client Life-Cycle Events

A Microsoft ASP.NET AJAX page raises the same server life-cycle events as an ASP.NET 2.0 Web page and also raises client life-cycle events. The client events enable you to customize the UI for both postbacks and for asynchronous postbacks (partial-page updates). The client events also help you manage custom script components during the lifetime of the page in the browser. The client events are raised by classes in the Microsoft AJAX Library. These classes are automatically instantiated when a page contains ASP.NET AJAX server controls. The client classes provide APIs that enable you to bind to events and to provide handlers for those events. Because the Microsoft AJAX Library is browser independent, the code you write for your handlers works the same in all supported browsers. The key event for initial requests (GET requests) and synchronous postbacks is the load event of the Application instance. When script in a load event handler runs, all scripts and components have been loaded and are available. When partial-page rendering with UpdatePanel controls is enabled, the key client events are the events of the PageRequestManager class. These events enable you to handle many common scenarios. These include the ability to cancel. postbacks, to give precedence to one postback over another, and to animate UpdatePanel controls when their content is refreshed. Client events are useful whether you are creating pages or writing components. If you are a page developer, you can provide custom script that is called when the page loads and unloads in the browser.

Client Classes
The two main Microsoft AJAX Library classes that raise events during the client life cycle of an ASP.NET AJAX Web page are the Application and PageRequestManager classes. The Application class is instantiated in the browser when the page contains a ScriptManager control. The Application class resembles the Page server control, which 19

derives from the Control class, but provides additional functionality for raising server events. Similarly, the Application class derives from the Sys.Component class, but raises client life-cycle events that you can handle. If a page contains a ScriptManager control and one or more UpdatePanel controls, the page can perform partial-page updates (if partial-page rendering is enabled and supported in the browser). In that case, an instance of the PageRequestManager class is automatically available in the browser. The PageRequestManager class raises client events that are specific to asynchronous postbacks.

Key parts in ADO: Data provider:

The data provider is used for connecting to a database, retrieving data, storing the data in the dataset, reading the retrieved data, updating the database.

There are two types of providers:

1. OLEDB data provider:- This type of data provider works with all the OLEDB providers such as SQLOLEDB provider, OracleOLEDB provider, and JETOLEDB provider. The OLEDB data provider classes are present in the System.Data.OleDb namespace. 2. SQL Server data provider:- This type of data provider is used to work specifically with Microsoft SQL Server. A SQL Server data provider is recommended for working with Microsoft SQL Server Data source, since a SQL Server Data provider allows fast access to a data source without going through an OLEDB or ODBC layer. The SQL Server Data provider classes are present in the System.Data.SqlClient namespace.

Connection:
This component is used to establish a connection with a data source. Two of the most common connection objects used are OleDbConnection and SqlConnection.

Data Adapter:
A data adapter is integral to the working of ADO.NET since data is transferred to and from a database through a data adapter. A data adapter retrieves data from a database into a dataset and updates the database. When you make changes to the dataset, the changes in the database are actually done by the data adapter. The data adapter first compares the data in the dataset with that in the database and then updates the database. You connect to a database by configuring a data adapter. There are two types of data adapter that can be configured to connect to a database in visual studio .NET.

20

1. SqlDataAdapter: This type of data adapter is configured to access data 2. OleDbDataAdapter: This type of data adapter is configured to access data from any database that is supported by an OleDbDataProvider.

Data Command:
A data command is a sql statement or stored procedure that is used to retrieve, insert, delete or modify data in a data source. A data command is an object of the OleDbCommand or SqlCommand class. A data command derived from the OleDbCommand class can be used to work with any OleDb provider whereas data command derived from the SqlCommand class can be used to access data from SQL Server.

Data Reader:
Data reader is used to retrieve data from a data source in a read-only and forward-only mode. A data reader uses the connection object to connect to the database, the command object to execute sql statement or procedures on the database and retrieves the data in a sequential mode. Using data reader results in faster access to data and less memory usage.

21

6. UML DIGRAMS
6.1. Usecase diagram
Case 1:

customer

B2C

Admin

Case 2:
Manage(events,products,editor) View/Buy(products,events,editor) Admin b2c customer

Case 3:
View /Buy Product View customer View Editor Manage Manage Admin Manage

calender

22

6.2. Sequence diagram

Admin

Cutomers

Products

Calender

Editor

login

Manage

Manage

Manage

View

View

login\register

Buy

View orders

View details

View

23

6.3.Class Diagram

24

7. SCREENS AND REPORTS

Administrator login

25

User of the Business to customer

26

User order Details for the admin in detail

27

Add Category

28

Add Product

29

Home Page of the admin

30

Add to cart page

31

User Login Details

32

User shipping & billing Details

33

8. SYSTEM TESTING Testing:

Testing is a set of activities that can be planned in advance and conducted systematically. For this reason, a template for software testing a set of steps into which we can place specific test case design techniques and testing methods - should be defined for the software processes. A number of software testing strategies have been proposed in the literature. All provide a software developer with a template for testing and all have the following general characteristics. Testing begins at the component level and works outward towards the integration of the entire computer based system. Different testing techniques are appropriate at different points in time. Testing is conducted by the developer or software and for large products, an independent test groups. Testing and debugging are different activities but debugging must be accommodated in any testing strategy. (REFERENCED from Software Engineering Roger S. Pressman) A strategy for software testing must accommodate low level tests that are necessary to verify that a small source code segment has been correctly implemented as well as high level tests that validate major system functions against customer requirements. Dynamic Analysis: Looks at the behavior of s/w while it is executing ,to provide information such as execution traces, timing profiles and test coverage information. Mainly two types of testing involve: Black Box Testing White Box Testing

Black Box Testing:

Black box test focus on verifying whether the actual behavior of the program or system matches the described in their specification. This is not an alternative to white box test but they will be a component with the aim of finding out different types of errors. Black box test try to find the following categories of fault. Incorrect or missing function Interface errors Error in data structures or in external data base access. Performance errors

34

 Initialization and termination errors While conducting above tests a few missing functions detected in connection establishment were incorporated.

White Box Testing

It comprises of following testing Statement testing: Test single statement (assignment, etc) Loop testing: Cause execution of the loop exactly to be skipped completely. Loop to be executed more than once Path testing: Make sure that all paths in the program are executed. Branch Testing: Make sure that each possible outcome from a condition is tested at least once. As the number of loops in the project is limited and not complicated no problems were encountered

35

9. TESTING STRATEGIES
Test cases are devised with the purpose of finding errors. A testcase is a set of data that the system will process as normal input. For this system, the test data is devised to check if the adjustments are done correctly. The other test cases devised is to check the situation in which no data is available for adjustment for a specific condition. There are many test cases designed with this mind .the flow of testing is as follows: Code testing Unit testing System testing

CODE TESTING:
Specification testing is done to check if the program does what it should do and how it should behave under various condition or combination and submitted for processing in the system and it is checked if any overlaps occur during the processing.

UNIT TESTING:
The first level of testing is called unit testing. Here different modules are tested against the specification produced during the design of the modules. Unit testing was done to test the working of the individual modules with test oracles.

SYSTEM TESTING
The next level of testing was system testing and acceptance testing. This testing was done to check if the system has met its requirements and to find the external behavior of the system.

36

10. Scope And Expansion

We can extend this project for Different kind of Marketing like Automobiles, Furnitures who are interested in further studies. We can add a online training facility for the lectures We can add a book details for subjects which are in the courses

11. Limitations:
To modify the project to Dot net 2.0 and extending this functionality to mobile internet platform using mobile ASP.Net platform by which the restrictions of the software and the hardware requirements can be scaled down which is possible.

12. Conclusion:
All the users in the organization have appreciated the project. It is easy to use, since it uses the GUI provided in the user dialog. User-friendly screens are provided. The usage of software increases the efficiency, decreases the effort. It has been thoroughly tested and implemented.

37

BIBLIOGRAPHY
The following books were referred during the analysis and execution phase of the project

INTRODUCTION TO SYSTEM ANALYSIS & DESIGN -- IT HAWRY SKIEWCZ SOFTWARE ENGINEERING -- BY ROGER.S. PRESSMAN UNIFIED MODELLING LANGUAGE USER GUIDE -- GRADE BOOCH -- JAMES RUMBAUGH -- JACBSON DATABASE MANAGEMENT SYSTEM -- RAGHU RAMA KRISHAN -- JOHANNES GEHRKE SQL FOR PROFESSIONALS -- BY JAIN

Professional ASP.NET 1.0 -- BY WROX MSDN 2002 By Microsoft

38