A Project Report on WEB COMPILER (Minor Project) submitted in partial fulfillment of the requirement for the award of the

Degree of Bachelor of Technology (Mody Institute of Technology and Science, Lakshmangarh) in Computer Science and Engineering/ Information Technology

Under the supervision of

Mr Mohit Goswami

Submitted by
Parul Jain 080457 1

Anshika Gupta 080406

November 2011 Mody Institute of Technology and Science ( a Deemed University Under Section 3 of the UGC Act 1956)

Formerly Known as Mody College of Engineering and Technology

Lakshmangarh-332311 (Dist.-Sikar)

Mody Institute of Technology & Science (a Deemed University Under Section 3 of the UGC Act 1956)

( and Technology

Formerly Known as Mody College of Engineering

Lakshmangarh 332311, Distt. Sikar (Rajasthan) Phones: (01573) 225001 to 225012 (12 lines) Fax: (01573) 225042

CERTIFICATE 2

This is to certify that Ms. Parul Jain, Ms. Anshika Gupta are students of B.Tech. VII semester and have submitted their project entitled Web Complier under my guidance.

Guide

Project Approval

The Project entitled Web Compiler by Ms. Parul Jain and Ms. Anshika Gupta is approved in partial fulfillment of the requirement of the Degree of Bachelor of Technology of the MITS University.

HOD

Examiner (Internal)

Examiner (External)

ACKNOWLEDGEMENT

It is our profound privilege to express our deep sense of gratitude towards our institute Mody Institute of Technology and Science, Lakshmangarh.

We would also like to thank honorable Vice Chancellor Prof.(Dr.) N.V.Subba Reddy , Dr. P.K.Das, Dean FET, Dr. A.K.Sharma, HOD CSE/IT and Mr. Ajay Kumar, project coordinator for their encouragement and appreciation.

We wish to extend our gratitude in all sincerity to Mr. Niranjan Lal our project guide who gave us an opportunity to work under his guidance. He has been a source of inspiration and without his guidance the project would not have been successful. We would also like to thank all other faculty members who provided us help and support regarding the project.

At last, we are also thankful to our Lab technician and friends who helped us with whole heartedness during the development of our project.

Akshara Singhal (080402) Gargi Tripathi ( 080420) Aditi Singh (080624) CS&E (4th year)

1.1 ORGANISATION PROFILE

V SUPPORT is a Software Service company incorporated in the year 2005, having its registered office in Madurai, the temple city and hub of the southern part of Tamilnadu state, India.

This company was promoted by a band of young professionals with excellent experience and expertise in the field of Information Technology and Management. This group has been in the IT business for over a decade with the main thrust being Software Training and Event Management.

V SUPPORT was started with an aim of producing high quality software solutions for the Global markets. The company is committed to update its knowledge base and technical infrastructure to effectively meet the demands and challenges of its clients so that they may keep abreast with the technology revolution changing the global scenario. The bedrock credo of the management is ethically principled longterm relationship with clients, business Partners, resellers and employee force.

V SUPPORT has the advantage of guidance by highly reputed professional management and technical consultants in all its operations. The company enjoys the collaboration and alliance of international companies to provide hi-tech solutions to its clientele, which is a remarkable testimonial of its business competency and acumen.

V SUPPORT No. 5, Moosa Street, T. Nagar, Chennai 6000 17 Ph : 044-55211691

1.2 SYSTEMS DEVELOPMENT LIFE CYCLE

1.2.1 Definition

The system development life cycle is the process, involving multiple stages (from establishing the feasibility to carrying out post implementation reviews), used to convert a management need into an application system, which is custom-developed or purchased or is a combination of both.

In general, an SDLC methodology follows the following steps:

1. The existing system is evaluated. Deficiencies are identified. This can be done by interviewing users of the system and consulting with support personnel. 2. The new system requirements are defined. In particular, the deficiencies in the existing system must be addressed with specific proposals for improvement. 3. The proposed system is designed. Plans are laid out concerning the physical construction, hardware, operating systems, programming, communications, and security issues. 4. The new system is developed. The new components and programs must be obtained and installed. Users of the system must be trained in its use, and all aspects of performance must be tested. If necessary, adjustments must be made at this stage. 5. The system is put into use. This can be done in various ways. The new system can phased in, according to application or location, and the old system gradually replaced. In some cases, it may be more cost-effective to shut down the old system and implement the new system all at once.

6.

Once the new system is up and running for a while, it should be

exhaustively evaluated. Maintenance must be kept up rigorously at all times. Users of the system should be kept up-to-date concerning the latest modifications and procedures.

1.2.2 Factors Influencing the SDLC

The

SDLC

for

an

application

system

would

depend

on

the

chosen

acquisition/development mode. Application systems could be acquired/developed through various modes, which include:
y y

Custom development using internal resources Custom development using fully or partly outsourced resources located onsite or offsite (locally or in an offshore location)

y y

Vendor software packages implemented as-is with no customisation Vendor software packages customised to meet the specific requirements

At times, large complex applications may involve a combination of the above.

Some organisations use specific SDLC methodologies and processes, either custom- or vendor-developed. These generally prescribe standard processes for different modes of acquisition with the facility to customise the process design for specific application systems. These may be supported by appropriate tools to manage the SDLC. In such cases, the SDLC would depend on the methodology/tool.

1.2.3 CRM USES :

The Method that has been used widely to develop the projects is the most acceptable and flexible cycle called WATERFALL CHART method. In this method the developed products cascade from one level to the next in smooth progression. This 9

method involves project planning, which shows what type of life cycle method to be used, the organizational structure for the project, the preliminary cost and resource estimates, staffing requirements, tools and techniques and standard practices to be followed.

The phased model or waterfall chart is valid model of the development process in situation where it is possible to write reasonably complete set of specification for the software product at the beginning of the life cycle.

The phase used in waterfall method in this project is shown diagrammatically below. System Analysis

System Requirement

System Design

Coding

Testing

Acceptance

10

11

2. PROJECT DESCRIPTION
CRM (CUSTOMER RELATIONALSHIP MANAGEMENT) is System Software for small business in the market. The CRM is an integration of sales,

production, marketing with the customer to empower them with their capacities being actually made to quicken the operational level duties performed by all. Integration between various operation levels of the company will make each level immensely responsible for the development of the company and will enhance the importance of that level for the company. An efficient CRM cannot be defined without taking in account of the customers views. The customer and his view must be the driving force for the whole system and inspirational aspect for any companys development. The communication between the client and the company must be the two way communication, which forms the basis of any CRM.

CRM software comes packaged with every thing users business needs to create a dynamic customer relationship management system. The customers will be delighted with the support they get from the software. The administrator will notice the

difference that sales management task makes in freeing up their time. CRM concepts applied for sales and marketing for company product, customer service provided and feedback of the valued customer received being on important asset in the companys development. CRM designed to facilitate interaction between the clients and the

company, which is promoting many products for business. This process is involves various modules like  Login  Administrator  Transaction  Search Engine

12

Login module contains two sub modules  Administrator Login  User Login Administrator module contains four sub modules  Product Information  Customer Information User module contains four modules:  TRANSACTION  SEARCH ENGINE Each Module has been contains Sub Module. TRANSACTION MODULE  Enquiry Entry.  Booking Entry.  Feedback Entry. SEARCH ENGINE MODULE  Product Search.  Customer Info Search.

13

2.1 TRANSACTION MODULE

2.1.1 Enquiry Entry This page provides information about enquiry details like  Enquiry no  Customer name  Customer email-id  Enquiry date  Description By seeing this information customer can give enquiry or description about product details here the user can add and modify the records. No others fields are kept empty otherwise it will prompt for error and gives the alert message, after entering all the fields it first checks for Enquiry no if any other fields are invalid it will give an alert message and it wont allow to proceed further, if all the information are valid then it adds the records to the database. If there are any modifications, then the user can then modify the records.

2.1.2 Booking Entry This page displays about product booking details, so the any customer can easily book the products from the Internet it gives information about,  Booking id  Customer name  Customer email-id  Product id  Product name  Product price  Purchase date  Delivery 14

By seeing this information the customer can book the products in that he wants. No others fields are kept empty otherwise it will prompt for error and gives the alert message, after entering all the fields it first checks for Booking no if any other fields are invalid it will give an alert message and it wont allow to proceed further if all the information are valid then it adds the records to the database. If there are any modifications, then user can then modify the records.

2.1.3 Feedback Entry: This page provides information about feedback details so the customer can give his suggestion to the company.  Enquiry no  Customer name  Customer email-id  Date  Suggestion By providing this information the customer can write his feedback to the company. No others fields are kept empty otherwise it will prompt for error and gives the alert message, after entering all the fields it first checks for Enquiry no, if any other fields are invalid it will give an alert message and it wont allow to proceed further, if all the information are valid then it adds the records to the database. If there are any modifications, then user can then modify the records.

15

2.2 SEARCH ENGINE MODULE

2.2.1 Product Search Entry: This page gives information about current availability products. By giving the products name it first checks the given product name and lists and displays what are the current products in their company, how many stocks are available up to date. So the Search engine module helps the customer to easily purchase the product from the net. So it simply searches and gives the lists about current availability products and it displays about        Product Code Product Model Product Name Product Price Product Color Purchase Date Total no of Stocks

2.2.2 Customer Info Search Entry: This page give information about customer details, so by giving this details the company can look over individual customer address and other details. By giving the customer name it first checks the given name and lists the available information as       Customer Name Customer Email-id Customer Address Customer Phone no Product Purchased Purchase Date

So by seeing the customer name it searches and displays the individual customer information. 16

17

3 SOFTWARE DESCRIPTION

OPERATING SYSTEM CONFIGURATION

3.1 WINDOWS XP

Windows XP is a popular Operating System produced by Microsoft. It supports has lot of external drivers that supports lot of hardware's. It has high graphics support tools.

Windows XP itself contains IIS software, which is required to install the Visual Studio.NET in a computer.

3.2 INTRODUCTION TO ASP.NET

3.2.1 What is ASP.Net? ASP.NET is a programming framework built on the common language runtime that can be used on a server to build powerful web applications. ASP.NET offers several important advantages over previous web development models:

Enhanced performance ASP.NET is compiled common language runtime code running on the sever. Unlike its interpreted predecessors, ASP.NET can early binding, Just in time compilation, native optimization and catching service right out of the box. This amounts to dramatically better performance before you ever writer a line of code.

3.2.2 Word-Class Tool Support: The ASP.NET framework is complement by a rich toolbox and designer in the Visual Studio integrated development environment. WYSIWYG editing, drag-and-drop server

18

controls and automatic development are just a few of the features this powerful tool provides.

3.2.3 Power and Flexibility: Because ASP.NET is based on the common language runtime, the power and flexible of the entire platform is available to web application developers. The .Net Framework class library, Messaging and Data Access solutions are all seamlessly accessible from the web. ASP.NET is also language-independent, so you can choose the language that best applies to your application or partition your application across many language. Further, common language runtime interoperability guarantees that you existing investment in COM-based development is preserved when migration to ASP.NET.

3.2.4 Simplicity: ASP.NET makes it easy to perform common tasks from simple form submission client authentication to deployment and site configuration. For example, the ASP.NET page framework allows you to build user interfaces that cleanly separate application logic from presentation code and to handle evens in a simple, visual basic like forms processing model. Additionally, the common language runtime simplifiers

development, with managed code services such as automatic reference counting and garbage collection.

3.2.5 Manageability: ASP.NET employs a text-based, hierarchical configuration system, which simplifies applying settings to your server environment and web application. Because configuration information is stored as plain text, new settings may be applied without the aid of local administration tools. This Zero local administration philosophy extends to deploying ASP.NET Framework application as well. An ASP.NET Framework application is deployed to server simply by copying the necessary files to the server. No server restart is deployed to as server simply by copying the necessary 19

files to the server. No server restart is required, even to deploy or replace running compiled code.

3.2.6 Scalability and Availability: ASP.NET has been designed with scalability in mind, with features specifically tailored to improve performance in clustered and Multiprocessor environments. Further, processes are closely monitored and managed by the ASP.NET runtime, so that if one misbehaves (leaks, deadlocks), a new process can be created in its place, which helps keep your application constantly available to handle requests.

3.2.7 Customizability and Extensibility: ASP.NET delivers a well factored architecture that allows developers to plug-in their code at the appropriate level. Infect, it is possible to extend or replace any subcomponent. Implementing custom authentication or state services has never been easier. Security, with built in windows authentication and per-application configuration, you can be assured that your application are secure. 3.2.8 FEATURES: ASP.Nets features for enhancing web page development combined with the .Net frameworks support for web services, make it the perfect tool for building web services:

i.

The code behind model separates HTML (the presentation layer) from program logic (server side code). This eliminates the dangerous practice of writing spaghetti code that is prone to error.

ii.

An even driven program model allows you to write your events and create handlers for them.

iii.

Server controls automatically render HTML appropriate for any client browser.

iv.

Server controls manage client state by using View State. 20

v. vi.

Code is compiled, thereby enhancing performance. Application logic can be written in any CLS-compliant programming Language, such as Visual Basic .Net, Managed C++ .NET, or C# .NET.

vii.

Web form development is simplified by using Visual Basic .NET as a RAD tool.

The Framework supports web services and web forms through namespaces that host classes, such as System.Web.Ui and System.Web.Ui.WebControls. The

System.Web.UI namespaces contains classes and interfaces that allows us to create controls and pages that appear in your web applications us user interfaces on a web page. A major advantage offered by ASP.NET is running the controls on the server rather than on the client so you programmatically control then at runtime.

3.2.9 System.Web.Ui Namespace The System.Web.UI namespaces hosts the classes and interfaces especially designed for rendering elements on web form. You can view al classes in the System.Web.UI namespaces as a hierarchical tree beginning with the control class. This is the mother of all controls. Buttons, text boxes, dropdown list boxes and so on derive from the control class. It encapsulates both functionality and user interface properties for all member controls residing in this namespace. Class properties include controls, context, parent, site, unique ID. A collection of classes, interfaces, enumerations and delegates makes up the namespace and are essential for developers to understand so that they can take full advantage of ASP.NET.

3.2.10 Delegates The final item in the System.Web.UI namespaces, delegates contains one item. It describes the method that handles any events raised when a user clicks on an image based ASP.NET server control. Also a delegate is referenced type that encapsulates a method that contains a specific signature and return type. 21

ASP.NET pages begin as code in a text file with an .aspx extension. They lie within Internet Information Services(IIS) virtual directory located somewhere on your LAN or on a remote server. Pages are instantiation classes derived from the parent page class. For example, you can write your code using any text editor such as Notepad or preferably, Visual Studio.NET, the text file becomes a valid ASP.NET page only when a client sends a request to the server to render the pate to the client browser.

The page compiles to a class. It is created at runtime as a page object and is subsequently cached in memory. It naturally follows that the page object serves as a naming container for all server controls implementing the naming container interface.

ASP.NET functionally lies primarily with the page class. Every page derives from the page class, thereby inheriting all the methods and properties the page class exposes. The following list describes several members of this class.

i.

The ASP objects such as Application, Session, Request, Response, Server and context are implemented in ASP.NET as class instances, which are exposed as properties of a specified page.

ii.

The controls collection provides access to the set of controls defined for a specific page. With this collection, you can add or alter controls.

iii.

The IsPostBack property is used to determine whether the current request is a GET request or a POST request.

iv. v.

The user property provides information about the logged in user. The cache property enables access the ASP.NET cache engine. You can see this property to allow data to be cache for later retrieval.

vi.

The find control property allows you to locate a control in the controls collection specifying the ID attribute property. 22

vii.

The view state property allows you to store a pages in a hidden from fiels (key value pair) between client requests.

viii.

The clear child view state property allows you to delete view state information for any child controls residing on a page.

Each ASP.NET page contains a server side <form> tag. These tags direct the page to post back to it when a client submits the form. The form type events include Load, Draw, Render and Unload.

ASP.NET controls

also render JavaScript to the client, enabling actions such as

selecting a specified item from a dropdown list, thereby causing PostBack to the server. The ASP.NET runtime also renders a hidden from field to the page and allows it ti preserve its state between client requests. Because ASP.NET is event driven, client and page interaction allows the pate to be reconstructed on the server. It also permits code execution in response to events raised by users and any changes occurring in the hidden fields.

The initials event begins with an HTTP URL client request for rendering a specific page to a clients browser. The load event fires next. Here is where the CLR uses reflection to examine the .aspx page through user interaction with a button or some other page control. If the event is a first time request, the code is converted to a class. Subsequently, the class compiles to an assembly and is stored in a valid internet information server virtual directory where the page can be located. ASP.NET restores any data residing in hidden fields and passes the information to the server. The control event triggering the post back then fires. At this point, all control events are initiated.

The changes events fire first; those events are stored in the browser and execute only when the client sends the page back to the server. After a control event fires the pate is rendered to the browser.

23

Before page Unload() unloads the page from server memory, a final event performs any cleanup tasks before the unload method dispose of the page. ASP.NET has added numerous directives for controlling page behavior, page configuration, and many other tasks. Following table presents a partial list of new directives included with ASP.NET.

24

25

4.1 SYSTEM DESIGN

The Design is concerned with identifying software components, Specifying relationships among Components, Specifying software structure, maintaining a record of design and others, providing a blue Print of the implementation phase. It consists of the structured, input, output and database designs.

4.1.1 INPUT DESIGN: Input design is the part of the overall system design. The main goal of the design is to achieve easy data entry flawless. The input screen users options for selecting the values from the drop down combo boxes and list boxes to prevent typographic errors.

Validations are done for each and every data entered in the screen for data accuracy. The screens are designed in such a way that no necessary data are omitted. There are several validations involved during the data entry. The inputs to the system have been designed effectively in such a way the manual forms and the inputs are coordinated where the data elements are common to the source document and to the input.

4.1.2 OBJECTIVES OF INPUT DESIGN: The quality of system input determines the quality of the system output. Input

specifications describe the manner in which data enter the system processing. Input design features can ensure the reliability of the system and produce results from accurate data or they can result in the production of erroneous information. The input design also determines whether the user can interact efficiently with the system.

Five objectives guiding the design of the input focuses on:  Effectiveness  Accuracy  Easy to use 26

 Consistency  Attractiveness 4.1.3 CODE DESIGN: A code is an ordered collection of symbolic designed to provide unique identification of an entity or attribute. The main purpose of the code is to facilitate the identification and retrieval of the information, to simplify and to achieve coding. A variable name should be chosen in such manner that its Scope, data type and reflects could be easily and clearly understood. 4.1.4 OUTPUT DESIGN: Outputs are the direct source of information to the user. They provide a consolidated and permanent copy of records, which helps in decision-making. Output is information delivered to users through the information system. Without quality output, the entire system may appear to be unnecessary that users will avoid using it. Users generally merit the systems analyst works closely with the user through interactive process, until the result is considered to be satisfactory. Therefore, an effective output design is an important feature of design specification. In the report layout, the important items are highlighted so that they are easier to find. 4.1.5 OBJECTIVES OF OUTPUT DESIGN: Since useful output is essential for gaining use and acceptance of the system, the system analyst should try and follow the following objectives, which are useful for designing acceptable outputs.  Design output to serve the intended purpose  Design output to fit the user  Deliver the appropriate quantity of output  Assure that output is where it is needed  Provide output on time  Chose the right output method 27

4.2 SYSTEM FLOW CHART

HOME PAGE

ADMIN_LOGIN PAGE

USER_LOGIN PAGE

ADMINISTRATOR

USER LOGIN ENTRY

PRODUCT DETAILS CUSTOMER DETAILS

TRANACTION ENTRY
ENQUIRY ENTRY BOOKING ENTRY FEEDBACK ENTRY

SEARCH MODULE
PRODUCT INFO SEARCH

CUSTOMER INFO SEARCH

28

4.3 DATA FLOW DAIGRAM (DFD)

Figure 1 : HOME PAGE

HOME PAGE

ADMIN_LOGIN

USER_LOGIN

Figure 2 : ADMIN_LOGIN PAGE

Admin Login Page

Validate UserName and Password

Admin_Login

Invalid Admin Page

Administrator Menu Page

Figure 3 : USER LOGIN

USER LOGIN

USER_LOGIN

Check Password Valid User Login Module

Invalid Login InValid

29

Figure 4 : NEW CUSTOMER

Registation Module

NEW_USER

Registation Module

User Login Module

4.3.1 ADMINISTRATOR ENTRY Customer details

ADMIN LOGIN ENTRY

ADMIN_LOGIN

ADMINISTRATOR

ENTRY

LogOut

Product details

30

4.3.1.1 CUSTOMER DETAILS

ADMINISTATOR ENTRY

CUSTOMER DETAILS

Customer_details

Inserting,Updating and Deleting

View Customer Information

4.3.1.2 PRODUCT DETAILS

ADMINISTATOR ENTRY

PRODUCT DETAILS

Product_details

Inserting,Updating and Deleting

View Product Information

31

4.3.2 TRANSACTION ENTRY

Enquiry Entry

Booking Entry

USER LOGIN ENTRY

USER_LOGIN

TRANSACTOR ENTRY

LogOut

Feedback Entry

4.3.2.1 ENQUIRY ENTRY

TRANSACTION ENTRY

ENQUIRY DETAILS

ENQUIRY_ ENTRY

Inserting and Clear

View Enquiry Information

32

4.3.2.2 BOOKING ENTRY

TRANSACTION ENTRY

BOOKING DETAILS

BOOKING_ENTRY

Inserting and Clear

View Booking Information

4.3.2.3 FEEDBACK ENTRY

TRANSACTION ENTRY

FEEDBACK DETAILS

FEEDBACK_ ENTRY

Inserting and Clear

View Feedback Information

33

4.3.3 SEARCH REPORT

Product Info Search

USER LOGIN ENTRY

USER_LOGIN

SEARCH REPORT

Customer Info Search

34

4.3.3.1 PRODUCT SEARCH

SEARCH REPORT

PRODUCT SEARCH

Produt_details

View Product Reports

4.3.3.2 CUSTOMER INFO SEARCH SEARCH REPORT

CUST_INFO SEARCH

Cust_details

View Cust Reports

35

4.4 DATABASE DESIGN

A database can be defined as a stored collection of data, organized on the basis of relationships in the data. It is not a replacement for files. A set of program is necessary to facilitate adding new data as well as modifying and retrieving existing data within a database. This set of programs is referred to as a Data Base Management System

(DBMS). A database system merge data into one pool shared by all systems so that any change automatically affects all relevant systems.

4.4.1 ADVANTAGES OF DATABASE: 1. File Consolidation: Pooling data reduces redundancy and inconsistency and promotes cooperation among different users. Since databases link records together logically, a data change in one system will cascade through all other system using the data.

2. Program and File Independence: This feature separates the definition of the files from their programs, allowing a programmer to concentrate on the logic of the program instead of precisely how to store and retrieve data.

3. Access Versatility: Users can retrieve data in many ways. They enjoy the best of both worlds-sequential access for reporting data in a prescribed order and random access for rapid retrieval of a specific record.

4. Data Security: Usually a DBMS includes a password system that controls access to sensitive data. By limiting their access to read-only, write-only, or specified records, or even fields in records, passwords can prevent certain users from retrieving unauthorized data. 36

5. Program Development: Programmers must use standard names for data items rather than invent their own from program to program. This allows the programmer to focus on desired function.

6. Program Maintenance: Changes and repairs to a system are relatively easy.

7. Special Information: Special-purpose report generators can produce reports with minimum effort.

4.4.2 OBJECTIVES OF DATABASE DESIGN:  Eliminate redundant data as much as possible  Integrate existing data files  Share data among all users  Incorporate changes easily and quickly  Simplify the use of data files  Lower the cost of storing and retrieving data  Improve accuracy and consistency  Provide data security from unauthorized use  Exercise central control over standards 4.4.3 Logical and Physical View of Data: In database design, several views of data must be considered along with the persons who use them. The logical view is what the data look like. Regardless of how they are stored. The physical view is the way data exist in physical storage. It deals with how data are stored, accessed, or related to other data in storage. There are four views of data out of which three are logical and one is physical. The logical views are the users view, the programmers view and the overall logical view, called a schema.

37

Schema: Schema is a description of the data structure, which is separate from the data itself. The schema describes the areas, their identifiers and page sizes, and indicates how these are related to the records and sets. Schema is the view of the data, the overall logical data structure that is held by DBMS. Each time a program requires data, the DBMS will look up in the schema for the details of the structure of the data requested. Sub-Schema: In a database system, it is not always possible to allow programmers to write the data division of their choice for reasons of security or control. It is more useful to provide the programmer with a standard description of the logical data to be used in a particular application. All references to data within the program will be for this description, which is called a Subschema and is similar to the Schema in structure. The DBMS has the job of matching data requests on a subschema and data requests based on the schema.

38

4.5 TABLE DESIGN

ADMIN-LOGIN TABLE TABLE 4.5.1 : ADMIN_ID FIELD Admin_Id Password DATA TYPE Text Text DESCRIPTION ADMINISTATOR ID PASSWORD

USER-LOGIN- TABLE TABLE 4.5.2 : New_User FIELD Cust_Id Name Address Email_Id Phone Password DATATYPE NUMBER(6) TEXT (30) TEXT(50) TEXT(30) NUMBER(25) TEXT(10) PRIMARY KEY Y DESCRIPTION CUSTOMER ID CUSTOMER NAME CUSTOMER ADDRESS CUSTOMER EMAILID CUSTOMER PHONE NUMBER PASSWORD

39

ADMINISTOR TABLE TABLE 4.5.3 : PRODUCT DETAIL

FIELD PRODUCT CODE PRODUCT MODEL PRODUCT NAME PRODUCT PRICE QUANTITY PRODUCT COLOR AVAILABILTY

DATA TYPE NUMBER(10) TEXT(10) TEXT(50) NUMBER(6) NUMBER(10) TEXT(7) TEXT(30)

PRIMARY KEY Y

DESCRIPTION PRODUCT CODE PRODUCT MODEL PRODUCT NAME PRODUCT PRICE QUANTITY PRODUCT COLOR AVAILABILTY

TABLE 4.5.4 : CUSTOMERDETAIL FIELD Cust_Id Cust_Name Cust_EmailId Cust_Address Post DOB NOD PhoneNumber DATA TYPE TEXT(10) TEXT(30) TEXT(30) TEXT(50) NUMBER(10) TEXT(25) TEXT(30) NUMBER(25) PRIMARY KEY Y DESCRIPTION CUSTOMER ID NO CUSTOMER NAME CUSTOMER EMAILID CUSTOMER ADDRESS POST DATE OF BIRTH NAME OF DISTRICT PHONENUMBER

40

TRANSACTION TABLE TABLE 4.5.5 : ENQUIRYENTRY FIELD ENQUIRYNO CUSTOMERNAME CUSTOMEREMAILID ENQUIRYDATE DESCRIPTION DATA TYPE NUMBER(10) TEXT(50) TEXT(50) TEXT(25) TEXT(50) PRIMARY KEY Y DESCRIPTION ENQUIRY NO CUSTOMER NAME CUSTOMER EMAIL-ID ENQUIRY DATE DESCRIPTION

TABLE 4.5.6 : BOOKINGENTRY FIELD BOOKINGID CUSTOMERNAME CUSTOMEREMAILID PRODUCTID PRODUCTNAME PRODUCTPRICE PURCHASEDATE CREDIT CASH DELIVERY DATA TYPE NUMBER(15) TEXT (20) TEXT (20) NUMBER(10) TEXT (20) NUMBER(15) TEXT (20) TEXT (5) TEXT (5) TEXT (20) PRIMARY KEY Y DESCRIPTION BOOKINGID CUSTOMER NAME CUSTOMER EMAILID PRODUCT ID PRODUCT NAME PRODUCT PRICE PURCHASE DATE CREDIT CASH DELIVERY

41

TABLE 4.5.7 : FEEDBACKENTRY FIELD ENQUIRYNO CUSTOMERNAME CUSTOMEREMAIL-ID DATE SUGGESTION DATATYPE NUMBER(10) TEXT (50) TEXT (30) TEXT (30) TEXT (30) PRIMARY KEY DESCRIPTION ENQUIRY NO CUSTOMER NAME CUSTOMER EMAIL-ID FEEDBACK DATE CUSTOMERS SUGGESTION

42

43

5. SYSTEM TESTING
The system was tested using the following strategies: 5.1 UNIT TESTING: Each of the modules developed where tested independently. The following were

considered during the unit test the module interface is tested to ensure the information properly flows in an out of the unit under test. The local data structure is examined to ensure that data stored temporarily maintains integrity throughout the unit lifetime. Boundary conditions are tested. All independent paths through the control structure are exercised to ensure that all statements in the module have been executed atlases once all error-handling paths are tested.

5.2 INTEGRATION TESTING: Integration testing was done to verify the co-existence of the modules and forms involved. Bottom-up integration testing strategy was used for this purpose. After unit testing of each of the modules they are integrated from the bottom up by communicating each of the units into clusters. Dummy driver modules are added to simulate the upper level modules and these clusters were tested.

Finally when all of the modules were developed and integrated they were tested with the live data supplied by the user.

What to do we test for the first test of the system is whether it is producing the correct output? No other test can be more crucial; following this is a variety of other tests are conducted to verify different objectives.

5.3 Volume Testing: This is made to check whether the hardware and software are functioning correctly when a large amount of data is supplied. The user is called to provide test data for volume testing. 44

5.4 Stress Testing: The purpose of stress testing is proving that the system does nap malfunction under peak loads. Unlike volume testing, where time is not a factor we subject the system to a high volume of the data over a short period of time.

5.5 Recovery Testing: A forced system failure is induced to test the back up recovery procedure accurate data are entered to see how the system responds in time of enter deduction and protection.

5.6 Usability Documentation: This is to verify the user friendliness nature of the system. Normal operating and error handling procedures are related to this for example one aspect of user friendliness is accurate and complete documentation.

5.7 The nature of the Test Data: There are two very different sources of test data, live and artificial, both have distinct advantages for the tester.

Live test data are those that are actually entreated from organization files. It is difficult to obtain live data in sufficient amount to conduct intensive testing. Hence such data generally will not test all the combinations or formats that can enter the system.

The artificial data, which can be quickly prepared by a data generating utility program in the information system make possible the testing of all login and control path through the program. Hence the proper choice of test data is as important as the test itself.

45

46

6. CONCLUSION
Project is the mirror that reflects my abilities, skill, and knowledge. This Computerized CUSTOMER RELATIONSHIP MANAGEMENT has been developed for V Support Pvt Limited. The design and testing of the system is successfully done and testing in to account all the requirements laid down by the company

The system developed in Asp.Net and Ms-Access 2003 is user-friendly offering a wide range of choice. The entire input screen in this software is made simple. So that even a layman can feed data into it. This software also provides option for further enhancement if needed in this ever- changing environment.

47

48

7. BIBLIOGRAPHY
 NET FRAMEWORK ESSENTIALS Thuan Thai and Hoang Lam, Oreilly Publishing, Wrox Press.,  SPECIAL EDITION USING MICROSOFT SQL SERVER 2000 Mark Spenik and Orryan sledge, Macmillan Computer Publishing,  Sams Teach Yourself Microsoft Access 2000 Wordware Publishing, Julitta Korol  ASP.NET 1.1 with VB.NET2003 Chris Ullman, Johnkauffman, Chris Hart, David Sussman

WEBSITES:
www.asp.net.com www.aspemail.com www.asp.net

49

50

8.1 SCREEN LAYOUT

HOME PAGE

51

ADMIN LOGIN PAGE

52

ADMINISTRATOR ENTRY

53

CUSTOMER DETAILS

54

USER LOGIN

55

NEW USER PAGE

USER MENU PAGE

56

USER ENTRY

ENQUIRY ENTRY

57

TRANSACTION

58

ENQUIRY ENTRY

59

BOOKING ENTRY

60

FEEDBACK ENTRY

61

SEARCH MENU PAGE

62

PRODUCT INFO SEARCH REPORT

63

CUSTOMER INFO SEACH REPORT[INDIVIDUAL WISE]

REPORT MENU PAGE

64