[attachment=2431]

eTRADE
MINI PROJECT REPORT
Submitted by MARY ALIAS JABINA JABBAR NEENA ELSA JOSE PRAKASH
ABSTRACT
eTRADE is a leading website eTrade is designed to provide a practical guide for small businesses wishing to gain a better understanding of online trading, identify opportunities and consider a range of implementation options. Implementing online trading strategies has the potential to provide substantial benefits for small business.
While there are many potential benefits of online trading, there are also business issues that should be considered prior to implementing online trading strategies. e-Trade provides information on the key business issues that should be considered, particularly those related to privacy and security of conducting electronic financial transactions over the internet.
With the fast changing trends in the industry, today, the Internet has become one of the most happening places. Keeping swift pace with this trend, we, at indiaoptions.com have not only made our presence felt but well recognized and respect too. To this end, a dynamic, multipurpose, totally user- friendly web site has been set up for Indians anywhere.
Computers are now influencing every sphere of human activities. Almost every company has entered into the field of computer. They have computerized most of their departments to aid them in their day-to-day transaction.
Computer systems are not only to imitate manual system but also to blend the capabilities of both humans and computers. The main advantages of the computerized system are based on the capabilities of computers. It is difficult to maintain and retrieve the details from the manual book recording, which takes a lot of time and labor, it allows for human errors.
TABLE OF CONTENTS
CHAPTER TITLE PAGE NO
LIST OF TABLES viii
LIST OF FIGURES ix
1. INTRODUCTION 1
1.1 ABOUT THE WEBSITE 1
1.2 ABOUT THE PROJECT 1
2. PROBLEM DEFINITION 3
2.1 EXISTING SYSTEM 3
2.2 PROPOSED SYSTEM 4
3. SYSTEM STUDY 5
3.1 SYSTEM ANALYSIS 5
4. PRELIMINARY INVESTIGATION 7
5. REQUIREMENT SPECIFICATION 8
5.1 FEASIBILITY STUDY 8
5.1.1 Operation Feasibility 8
5.1.2 Technical Feasibility 8
5.1.3 Economic Feasibility 9
CHAPTER TITLE AGE NO
5.2 HARDWARE REQUIREMENTS 9
5.3 SOFTWARE REQUIREMENTS 10
5.4 TECHNOLOGY SPECIFICATION 10
6. SYSTEM DESIGN 12
6.1 LOGICAL DESIGN 12
6.2 INPUT DESIGN 13
6.3 OUTPUT DESIGN 13
6.4 PHYSICAL DESIGN 14
6.5 MODULAR DESIGN 14
7. DATABASE DESIGN 15
7.1 NORMALIZATION 16
8. SYSTEM IMPLEMENTATION 17
8.1 IMPLEMENTATION METHODS 17
8.2 IMPLEMENTATION PLAN 18
9. EDUCATION & TRAINING 19
9.1 POST IMPLEMENTATION REVIEW 19
10. SYSTEM TESTING 21
10.1 UNIT TESTING 22
10.2 MODULE LEVEL TESTING 23
10.3 INTEGRATION & SYSTEM TESTING 23
10.4 REGRESSION TESTING 23
11 MAINTENANCE 24
CHAPTER TITLE PAGE NO
12 TABLES 25
13 FIGURES 30
14 CONCLUSION 48
APPENDICES 49
RESUME 56
REFERENCES 57
LIST OF TABLES
TABLE TABLE NAME PAGE
12.1 BUY_LOGIN 25
12.2 BUY_DETAILS 25
12.3 PRODUCTS 26
12.4 SEL_LOGIN 26
12.5 SEL_DETAILS 27
12.6 SUBCAT 27
12.7 CATEGORY 28
12.8 BANK 28
12.9 ACCOUNT 28
12.10 CREDIT 28
12.11 CART 29
LIST OF FIGURES
FIGURE FIGURE NAME PAGE
13.1 CONTEXT LEVEL 29
13.2 LEVEL 0 DFD 29
13.3 LEVEL 1 DFD 30
13.4 LEVEL 2 DFD 31
13.5 LEVEL 3 DFD 32
13.6 LEVEL 4 DFD 33
13.7 HOME PAGE 34
13.8 SELLER REGISTRATION FORM 35
13.9 SELLER LOGIN 36
13.10 SELLER HOME 37
13.11 PRODUCT REGISTRTION 38
13.12 EXISTING PRODUCT VIEW 39
13.13 PRODUCT UPDATION 40
13.14 BUYER REGISTRATION 41
13.15 BUYER LOGIN 42
13.16 FORGOT PASSWORD 43
13.17 PRODUCT SEARCH 44
13.18 BILL 45
13.19 PAYMENT OPTION 46

CHAPTER 1 INTRODUCTION
1.1 ABOUT THE WEBSITE
eTRADE is a leading website eTrade is designed to provide a practical guide for small businesses wishing to gain a better understanding of online trading, identify opportunities and consider a range of implementation options. Implementing online trading strategies has the potential to provide substantial benefits for small business.
While there are many potential benefits of online trading, there are also business issues that should be considered prior to implementing online trading strategies. e-Trade provides information on the key business issues that should be considered, particularly those related to privacy and security of conducting electronic financial transactions over the internet.
With the fast changing trends in the industry, today, the Internet has become one of the most happening places. Keeping swift pace with this trend, we, at indiaoptions.com have not only made our presence felt but well recognized and respect too. To this end, a dynamic, multipurpose, totally user- friendly web site has been set up for Indians anywhere.
1.2 ABOUT THE PROJECT
Computers are now influencing every sphere of human activities. Almost every company has entered into the field of computer. They have computerized most of their departments to aid them in their day-to-day transaction.
Computer systems are not only to imitate manual system but also to blend the capabilities of both humans and computers. The main advantages of the computerized system are based on the capabilities of computers. It is difficult to maintain and retrieve the details from the manual book recording, which takes a lot of time and labor, it allows for human errors.
Moreover, the different persons to save time do different operations. This may leads to wrong entries and confusion to whether the particular process is over. The implemented computerized of the existing system and also overcome the shortcoming of the manual system.
e-Trade is designed to provide a practical guide for small businesses wishing to gain a better understanding of online trading, identify opportunities and consider a range of implementation options. Implementing online trading strategies has the potential to provide substantial benefits for small business.
Some of these benefits include:
¢ 24 hrs a day/7 days a week trading capability
¢ Potential global reach
¢ Lower transaction costs resulting from less paperwork and streamlined buying and selling processes
¢ Easier, more efficient and lower cost communication methods
¢ Low cost and constant marketing to the world
¢ A potential to deliver digital products and services
¢ Online financial transactions
¢ Easy access to real-time information
¢ Expanded communication and information capability
¢ Increased productivity by replacing manual processes with automated electronic processes
¢ Opportunities to page link manufacturers and customers directly
CHAPTER 2 PROBLEM DEFINITION
eTRADE is very helpful to users. The aim of this project is to provide quick, immediate and easy way for selling and buying products. It can provide special advantages to the seller/buyer that can't be found anywhere else through partnerships with agencies which are providing e-shopping. Its working is that buyer/seller allow to register for their transaction. This will continue to grow - ultimately providing a wide breadth of services for benificial to the buyer/seller.
Login helps the seller/buyer to login to the site. For that he/she must type the username and password correctly. The login provision in this page helps the already registered user to directly access the site and there is a page link for registration to a user who is new to this site.
Seller module is mainly for the seller. This helps the seller to register, register his products, update, and view his products. On registration of a new seller, name, address, phone no, email-id, username, password should be entered.
Buyer module is mainly for the buyer. . This helps buyer to register,product search(category, subcategory). On registration of a new buyer, name, address, phone no, email-id, username, password should be entered.
Payment module is mainly used for payment . It can be done by two ways. One by credit card and another by banking transaction.
2.1 EXISTING SYSTEM
The organization for the whole process maintains a manual system of working. There is no need to describe that how tedious will be the record keeping. Different details are entered on different registers. The various registers are kept and maintained by different persons in an organization. The latent delay of information flow causes dissatisfaction among customers and concerned officers do the various calculations as well as the authorization process manually. This causes a great delay in generating reports. Also when related data is to be retrieved several registers has to be accessed, checked and verifications need to be made. This causes delay in decision-making process. Updating or modification of entries is also a fatiguing process. Many limitations were identified on the existing system.
2.2 PROPOSED SYSTEM
The primary objective of the newly proposed system is to overcome the drawbacks of the existing system. The features of the proposed system are as follows:
¢ GLOBAL MARKETING
The proposed system takes the shop from local to global competition with the help of
Internet
¢ ANYTIME, ANYWHERE MOBILE SHOPPING
The proposed system enables the user to purchase phones round-the clock from anywhere
¢ SEARCHING FACILITIES
The proposed system has the facility to search the product by the product name. This will help the user to find the required product easily and quickly.
¢ MODES OF PAYMENT
The proposed system gives the user, a mode of payment-credit card or bank, where the transaction is made electronically.
¢ AUTOMATED ORDER PROCESSING
The proposed system reduces the time taken by the manual order processing by replacing with fully automated order processing.
CHAPTER 3
SYSTEM STUDY
The system study phase involves the initial investigation of the structure of the System, which is currently in use, with the objective of identifying the problem and difficulties with the existing system. The major steps involved in this phase included defining the user requirements and studying the present system to verify the problem. The performance expected by the new system was also defined in this phase in order to meet the user requirements. The information gathered from various documents were analyzed and evaluated and the findings reviewed in order to establish specific system objectives.
3.1 SYSTEM ANALYSIS
System analysis is the way of studying a system with an eye on solving its problem using computer. It is the most essential part of the development of a project of a system analysis. System analysis consists of system element, process and technology.
To analyze a system, has to study the systems in details. The analyst has to understand the functioning and concept of the system in detail, before design the appropriate computer based system that will meet all the requirements of the existing system. The system analyst has to carry out a customary approach to use the computer for problem solving.
System analysis includes the following basic concepts
¢ Preliminary investigation
¢ Requirements specification
¢ Feasibility study
¢ Detailed investigation
¢ Drawing up of strategies
¢ Design and coding
¢ Testing and training
¢ Implementation
The above steps constitute the logical framework for the system analysis. After the preliminary investigation and feasibility study, the scope of the defined and comparable items are set forth and hence detailed investigation is executed. This allows the system analyst to comprehend the full scope of the project. Soon after the implementation of the newly developed system, followed by the training of the users, the system analysis is included.
CHAPTER 4 PRELIMINARY INVESTIGATION
A request to receive assistance from information system can be made for many reasons, but in case a manager, employee or system specialist initiates the request. When that request is made, the first system activity preliminary investigation begins. The activity has three parts
> Request clarification: the request from employee may not be well stated. Sometimes the request may not be well defined. Therefore before any system investigation can be considered, the project request must be examined to determine precisely the actual requirements of the organization.
> Feasibility study: the basic idea of feasibility study is to determine whether the requested project is feasible.
> Request approval: all projects that are requested are not desirable or feasible .some organization receive so many projects requests from employee that only a few of them can be pursued. However those projects that are feasible and desirable should put into a schedule. The management decides request that are most important. After a project request is approved the cost priority, the completion time and the personal required are estimated. Once the request is approved, the collection of data and determination of requirements can be started.
CHAPTER 5 REQUIREMENT SPECIFICATION
The primary goal of the system analyst is to improve the efficiency of the existing system. For that the study of specification of the requirements is very essential. For the development of the new system, a preliminary survey of the existing system will be conducted. Investigation done whether the upgradation of the system into an application program could solve the problems and eradicate the inefficiency of the existing system.
5.1 FEASIBILITY STUDY
The initial investigation poi nts to the question whether the project is feasible. A feasibility is conducted to identify the best system that meets the all the requirements. This includes an identification description, an evaluation of the proposed systems and selection of the best system for the job
The requirements of the system are specified with a set of constraints such as system objectives and the description of the out puts. It is then duty of the analyst to evaluate the feasibility of the proposed system to generate the above results. Three key factors are to be considered during the feasibility study.
5.1.1 Operation Feasibility
An estimate should be made to determine how much effort and care will go into the developing of the system including the training to be given to the user. Usually, people are reluctant to changes that come in their progression. The computer initialization will certainly affected the turn over, transfer and employee job status. Hence an additional effort is to be made to train and educate the users on the new way of the system.
5.1.2 Technical Feasibility
The main consideration is to be given to the study of available resources of the organization where the software is to be implemented. Here the system analyst evaluates the technical merits of the system giving emphasis on the performance.
By taking the consideration before developing the proposed system, the resources availability of the organization was studied. The organization was immense computer facilities equipped with sophisticated machines and the software hence this technically feasible.
5.1.3 Economic Feasibility
Economic feasibility is the most important and frequently used method for evaluating the effectiveness of the proposed system. It is very essential because the main goal of the
proposed system is to have economically better result along with increased efficiency. Cost benefit analysis is usually performed for this purpose. It is the comparative study of the cost verses the benefit and savings that are expected from the proposed system. Since the organization is well equipped with the required hard ware, the project was found to be economically.
5.2 HARDWARE REQUIREMENTS
PROCESSOR : PENTIUM IV
CLOCK SPEED : 2GHZ
SYSTEM BUS : 32 BIT
RAM : 256 MB
HDD : 80GB
MONITOR : SVGA COLOR
KEY BOARD : 108 KEYS
MODEM : 56 KBPS
MOUSE : PS/2
FDD : 1.44 MB
5.3 SOFTWARE REQUIREMENTS

OPERATING SYSTEM BROWSER FRONT END BACKEND WEB SERVER

: WINDOWS XP
: INTERNET EXPLORER 6.0 OR ANY HTTP BROWSER : ASP.NET
: SQL SERVER 2000 : IIS

SERVER SIDE SCRIPTING : C#.NET

CONNECTION PROTOCOL

: TCP / IP
: HTTP, SMTP, POP3,WAP

5.4 TECHNOLOGY SPECIFICATION
1. Client-Server Architecture
Typical client-server systems are based on the 2-tiered architecture, whereby there is a clear separation between the data and the presentation/business logic. These are generally data driven, with the application existing entirely on the client machine while the database server is deployed somewhere in the organization.
2. 2-Tier Architecture
In a traditional 2- Tiered application, the processing load is given to the client PC while the server simply acts as a traffic controller between the application and data. As a result, not only does the application performance suffer due to the limited resources of the PC, but the network traffic tends increase as well.
3. 3- Tier Architecture
In 3- Tier architecture an application is broken into three separate logical layers, each with a well defined set of interfaces. The first tier is referred to as the presentation layer and typically consists of graphical user interface of some kind. The middle tier, or business layer, consists of application or business layer and the third layer- the data layer contains the data that is needed for the application. The middle tier is basically the code that the user calls upon to retrieve the desired data. The presentation layer then receives the data and formats it for display. This separation of application logic from the user interface adds enormous flexibility to the design of application. The third tier contains the data that is needed for the application.
4. n- Tier Architecture
In an n - tier architecture the application logic is divided by function rather than physically. N - Tier architecture then breaks down like this:
> A user interface that handle the user's interaction with the application; this can be web browser running through a firewall, a heavier desktop application or even a wireless device
> Presentation logic that defines what the user interface displays and how a user's requests are handled- depending on what user interfaces are supported we need to have slightly different versions of the presentation logic to handle the client appropriately.
> Business logic that models the application's business rules, often through the interaction with the application's data.
> Interface services that provide additional functionality required by the application components, such as messaging, transactional support etc.
> The Data layer where the enterprise's data resides.
CHAPTER 6
SYSTEM DESIGN
System design is the solution to the creation of a new system. This phase is composed of several systems. This phase focuses on the detailed implementation of the feasible system. It emphasis on translating design specifications to performance specification. System design has two phases of development logical and physical design.
During logical design phase the analyst describes inputs (sources), out puts (destinations), databases (data sores) and procedures (data flows) all in a format that meats the uses requirements. The analyst also specifies the user needs and at a level that virtually determines the information flow into and out of the system and the data resources. Here the logical design is done through data flow diagrams and database design.
The physical design is followed by physical design or coding. Physical design produces the working system by defining the design specifications, which tell the programmers exactly what the candidate system must do. The programmers write the necessary programs that accept input from the user, perform necessary processing on accepted data through call and produce the required report on a hard copy or display it on the screen.
6.1 LOGICAL DESIGN
Logical design of an information system shows the major features and also how they are related to one another. The first step of the system design is to design logical design elements. Design of proposed system produces the details of the state how the system will meet the requirements identified during the system analysis that is, in the design phase we have to find how to solve the difficulties faced by the existing system. The logical design of the proposed system should include the details that contain how the solutions can be implemented. It also specifies how the database is to be built for storing and retrieving data, what kind of reports are to be created and what are the inputs to be given to the system. The logical design includes input design, output design, and database design and physical design
6.2 INPUT DESIGN
The input design is the page link between the information system and the user. It comprises the developing specification and procedures for data preparation and those steps are necessary to put transaction data into a usable form for processing data entry. The activity of putting data into the computer for processing can be achieved by inspecting the computer to read data from a written or printed document or it can occur by having people keying the data directly into the system. The design of input focuses on controlling the amount of input required, controlling errors, avoiding delay, avoiding extra steps and keeping the process simple.
The system needs the data regarding the asset items, depreciation rates, asset transfer, physical verification for various validation, checking, calculation and report generation.. The error raising method is also included in the software, which helps to raise error message while wrong entry of input is done. So in input design the following things are considered.
What data should be given as input
¢ How the data should be arranged or coded
¢ The dialogue to guide the operating personnel in providing input.
¢ Methods for preparing input validations and steps to follow when error occur
¢ The samples of screen layout are given in the appendix.
6.3 OUTPUT DESIGN
Computer output is the most important and direct information source to the user. Output design is a process that involves designing necessary outputs in the form of reports that should be given to the users according to the requirements. Efficient, intelligible output design should improve the system's relationship with the user and help in decision making. Since the reports are directing referred by the management for taking decisions and to draw conclusions they must be designed with almost care and the details in the reports must be simple, descriptive and clear to the user. So while designing output the following things are to be considered.
¢ Determine what information to present
¢ Arrange the presentation of information in an acceptable format
¢ Decide how to distribute the output to intended receipts
Depending on the nature and future use of output required, they can be displayed on the monitor for immediate need and for obtaining the hardcopy. The options for the output reports are given in the appendix.
6.4 PHYSICAL DESIGN
The process of developing the program software is referred to as physical design. We have to design the process by identifying reports and the other outputs the system will produce. Coding the program for each module with its logic is performed in this step. Proper software specification is also done in this step.
6.5 MODULAR DESIGN
A software system is always divided into several sub systems that makes it easier for the development. A software system that is structured into several subsystems makes it easy for the development and testing. The different subsystems are known as the modules and the process of dividing an entire system into subsystems is known as modularization or decomposition.
A system cannot be decomposed into several subsystems in any way. There must some logical barrier, which facilitates the separation of each module. The separation must be simple but yet must be effective so that the development is not
affected.
The system under consideration has been divided into several modules taking in consideration the above-mentioned criteria. The different modules are Buyer Module, Seller Module and Payment module.
CHAPTER 7
DATABASE DESIGN
The overall objective in the development of database technology has been to treat data as an organizational resource and as an integrated whole. DBMS allow data to be protected and organized separately from other resources. Database is an integrated collection of data. The most significant form of data as seen by the programmers is data as stored on the direct access storage devices. This is the difference between logical and physical data.
Database files are the key source of information into the system. It is the process of designing database files, which are the key source of information to the system. The files should be properly designed and planned for collection, accumulation, editing and retrieving the required information.
The organization of data in database aims to achieve three major objectives: -
¢ Data integration.
¢ Data integrity.
¢ Data independence.
The proposed system stores the information relevant for processing in the MS SQL SERVER database. This database contains tables, where each table corresponds to one particular type of information. Each piece of information in table is called a field or column. A table also contains records, which is a set of fields. All records in a table have the same set of fields with different information. There are primary key fields that uniquely identify a record in a table. There are also fields that contain primary key from another table called foreign keys.
7.1 NORMALIZATION
Normalization is a technique of separating redundant fields and braking up a large table in to a smaller one. It is also used to avoid insertion, deletion and updating anomalies. All the tables have been normalized up to the third normal form. In short the rules for each of the three normal forms are as below.
¢ First normal form
A relation is said to be in 1NF if all the under lying domain of attributes contain simple individual values.
¢ Second normal form
The 2NF is based on the concept of full functional dependency. A relation said to be in 2NF if and only if it is in 1NF and every non-key attribute is fully functionally dependent on candidate key of the table.
¢ Third normal form
The 3NF is based on the concept of transitive dependency. A relation in 2NF is said to be in 3NF if every non-key attribute is non-transitively.
CHAPTER 8
SYSTEM IMPLEMENTATION
Implementation includes all those activities that take place to convert from the old system to the new. The old system consists of manual operations, which is operated in a very different manner from the proposed new system. A proper implementation is essential to provide a reliable system to meet the requirements of the organizations. An improper installation may affect the success of the computerized system.
8.1 IMPLEMENTATION METHODS:
There are several methods for handling the implementation and the consequent conversion from the old to the new computerized system.
The most secure method for conversion from the old system to the new system is to run the old and new system in parallel. In this approach, a person may operate in the manual older processing system as well as start operating the new computerized system. This method offers high security, because even if there is a flaw in the computerized system, we can depend upon the manual system. However, the cost for maintaining two systems in parallel is very high. This outweighs its benefits.
Another commonly method is a direct cut over from the existing manual system to the computerized system. The change may be with in a week or with in a day. There are no parallel activities. However, there is no remedy in case of a problem. This strategy requires careful planning.
A working version of the system can also be implemented in one part of the organization and the personnel will be piloting the system and changes can be made as and when required. But this method is less preferable due to the loss of entirety of the system.
8.2 IMPLEMENTATION PLAN:
The implementation plan includes a description of all the activities that must occur to implement the new system and to put it into operation. It identifies the personnel responsible for the activities and prepares a time chart for implementing the system. The implementation plan consists of the following steps.
o List all files required for implementation.
o Identify all data required to build new files during the implementation. o List all new documents and procedures that go into the new system.
The implementation plan should anticipate possible problems and must be able to deal with them. The usual problems may be missing documents; mixed data formats between current and files, errors in data translation, missing data etc.
CHAPTER 9 EDUCATIONS AND TRAINING
The implementation of the proposed system includes the training of system operators. Training the system operators includes not only instructions in how to use the equipment, but also in how to diagnose malfunctions and in what steps to take when they occur. So proper training should be provided to the system operators. No training is complete without familiarizing users with simple system maintenance activities. Since the proposed system is developed in a GUI, training will be comparatively easy than systems developed in a non-GUI. There are different types of training. We can select off-site to give depth knowledge to the system operators.
Success of the system depends on the way in which it is operated and used. Therefore the quality of training given to the operating person affects the successful implementation of the system. The training must ensure that the person can handle all the possible operations.
Training must also include data entry personnel. They must also be given training for the installation of new hardware, terminals, how to power the system, how to power it down, how to detect the malfunctions, how to solve the problems etc. the operators must also be provided with the knowledge of trouble shooting which involves the determination of the cause of the problem.
The proposed system requires trained personnel for operating the system. Data entry jobs must be done utmost carefully to avoid errors. This will reduce the data entry errors considerably. It is preferable to provide the person with some kind of operating manuals that will explain all the details of the system.
9.1 POST IMPLEMENTATION REVIEW
After the system is implemented, a review should be conducted to determine whether the system is meeting expectations and where improvements are needed. System quality, user confidence and operating systems statistics are accessed through such technique event logging, impact evaluation and attitude surveys. The review not only assesses how well the proposed system is designed and implemented, but also is a valuable source of information that can be applied to a critical evaluation of the system.
The reviews are conducted by the operating personals as well as the software developers in order to determine how well the system is working, how it has been accepted and whether adjustments are needed. The review of the system is highly essential to determine the future enhancements required by the system. The system can be considered successful only if information system has met it objectives. The review analyses the opinion of the employees and identifies the attitudes towards the new computerized system. Only when the merits and demerits of the implemented system are known, one can determine what all additional features it requires are. The following are the issues to be considered in the evaluation of the system.
CHAPTER 10
SYSTEM TESTING
System testing is a critical aspect of Software Quality Assurance and represents the ultimate review of specification, design and coding. Testing is a process of executing a program with the intent of finding an error. A good test is one that has a probability of finding an as yet undiscovered error. The purpose of testing is to identify and correct bugs in the developed system. Nothing is complete without testing. Testing is the vital to the success of the system.
In the code testing the logic of the developed system is tested. For this every module of the program is executed to find an error. To perform specification test, the examination of the specifications stating what the program should do and how it should perform under various conditions.
Unit testing focuses first on the modules in the proposed system to locate errors. This enables to detect errors in the coding and logic that are contained within that module alone. Those resulting from the interaction between modules are initially avoided. In unit testing step each module has to be checked separately.
System testing does not test the software as a whole, but rather than integration of each module in the system. The primary concern is the compatibility of individual modules. One has to find areas where modules have been designed with different specifications of data lengths, type and data element name.
Testing and validation are the most important steps after the implementation of the developed system. The system testing is performed to ensure that there are no errors in the implemented system. The software must be executed several times in order to find out the errors in the different modules of the system.
Validation refers to the process of using the new software for the developed system in a live environment i.e., new software inside the organization, in order to find out the errors. The validation phase reveals the failures and the bugs in the developed system. It will be come to know about the practical difficulties the system faces when operated in the true environment. By testing the code of the implemented software, the logic of the program can be examined. A specification test is conducted to check whether the specifications stating the program are performing under various conditions. Apart from these tests, there are some special tests conducted which are given below:
Peak Load Tests: This determines whether the new system will handle the volume of activities when the system is at the peak of its processing demand. The test has revealed that the new software for the agency is capable of handling the demands at the peak time.
Storage Testing: This determines the capacity of the new system to store transaction data on a disk or on other files. The proposed software has the required storage space available, because of the use of a number of hard disks.
Performance Time Testing: This test determines the length of the time used by the system to process transaction data.
In this phase the software developed Testing is exercising the software to uncover errors and ensure the system meets defined requirements. Testing may be done at 4 levels
¢ Unit Level
¢ Module Level
¢ Integration & System
¢ Regression
10.1 UNIT TESTING
A Unit corresponds to a screen /form in the package. Unit testing focuses on verification of the corresponding class or Screen. This testing includes testing of control paths, interfaces, local data structures, logical decisions, boundary conditions, and error handling. Unit testing may use Test Drivers, which are control programs to co-ordinate test case inputs and outputs, and Test stubs, which replace low-level modules. A stub is a dummy subprogram.
10.2 MODULE LEVEL TESTING
Module Testing is done using the test cases prepared earlier. Module is defined during the time of design.
10.3 INTEGRATION & SYSTEM TESTING
Integration testing is used to verify the combining of the software modules. Integration testing addresses the issues associated with the dual problems of verification and program construction. System testing is used to verify, whether the developed system meets the requirements.
10.4 REGRESSION TESTING
Each modification in software impacts unmodified areas, which results serious injuries to that software. So the process of re-testing for rectification of errors due to modification is known as regression testing. Installation and Delivery
Installation and Delivery is the process of delivering the developed and tested software to the customer. Refer the support procedures Acceptance and Project Closure
Acceptance is the part of the project by which the customer accepts the product. This will be done as per the Project Closure, once the customer accepts the product; closure of the project is started. This includes metrics collection, PCD, etc.
CHAPTER 11
MAINTENANCE
Maintenance is making adaptation of the software for external changes (requirements changes or enhancements) and internal changes (fixing bugs). When changes are made during the maintenance phase all preceding steps of the model must be revisited.
There are three types of maintenance:
1. Corrective (Fixing bugs/errors)
2. Adaptive (Updates due to environment changes)
3. Perfective (Enhancements, requirements changes)
CHAPTER 12
TABLES
Table 12.1 BUYLOGIN
Sl.No Column Name Data Type Length Description
1. BUY_ID Int 4 Buyer
identification
2. BUYNAME Varchar 15 Buyer name
3. BUYPWD Varchar 15 Password of buyer
Table 12.2 BUYDETAILS
Sl.No Column Name Data Type Length Description
1. BUY_ID Int 4 Buyer
identification
2. BUYFNAME Varchar 15 First name of buyer
3. BUYLNAME Varchar 15 Last name of buyer
4. BUYADD Varchar 50 Present Address
5. BUY_SQ Varchar 50 Secret Question
6. BUYPHONE Varchar 15 Phone number of buyer
7. BUYEMAIL Varchar 15 Email address of buyer
8. BUYANS Varchar 50 Secret Answer
Table 12.3 PRODUCTS
Sl.No
Column Name Data Type Length Description
1. SEL_ID Int 4 Seller identification
2. PDT_ID Int 4 Product ID
3. CATNAME Varchar 15 Category ID of product
4. SUBCATNAME Varchar 15 Sub category Id of product
5. PDTNAME Varchar 15 Product Name
6. IMGE Varchar 15 Path of the saved image of product
7. QTY Int 4 Number of products
8. RATE Int 4 Price of product
Table 12.6 SUBCAT
SLno Column Name Data Type Length Description
1. SUBCATID Int 4 Sub Category Identity
2. CAT_ID Int 4 Category Identity
3. SUBCATNAME Varchar 15 Sub Category Name
Table12.7 CATEGORY
SLno Column Name Data Type Length Description
1. UNAME Varchar 15 User Name
2. PWD Varchar 15 Password
3. BANKNM Varchar 15 Bank Name
4. ACCNO Int 4 Bank Account No
Table12.9 ACCOUNT
SLno Column Name Data Type Length Description
1. ACCNO Int 4 User Acc No.
2. AMOUNT Float 8 Amount In Account
3. SEL_ID Int 4 Seller ID
4. BNKNAME Varchar 15 Bank Name
Table12.10 CREDIT
SLno Column Name Data Type Length Description
1. BUY_ID Int 4 Buyer ID
2. PDT_ID Varchar 15 Product ID
3. QTY Int 4 Quantity
4. SEL_ID Int 4 Seller ID
5. T_ID Int 4 Transaction ID
6. TOTAL Float 8 Total
CHAPTER 13 FIGURES

Fig 13.1 CONTEXT LEVEL

Buyer
Seller


Fig13.3 LEVEL 1 DFD

Order

Fig13.4 LEVEL 2 DFD


Seller


Fig 13.7 HOME PAGE
This is the home page that the user sees whenever he/she open this site.


Fig13.8 SELLER REGISTRATION FORM
Registration of new seller is performed through this form.
3 seller Microsoft Internet Explorer EM)®
File Edit View Favorites Tools Help
Back ' O E M & ^Search <j jjj Favorites ^
Address .& |http://localhost:3394/5NGC_ETR/seller,aspx
v Q Go Links >J
f New Seller Register here

Mobile Top0

Existing Seller
jeen
USER NAME PASSWORD
Forgot Your Password
Login

Fig 13.9 SELLER LOGIN
Seller can login through this form.
'3 selhome - Microsoft Internet Explorer
File Edit View Favorites Tools Help
QBack - j 0 ^ ij] p Search Favorites ^ 0. ^ ' H ^

Existing Product View Product updation Category Registration Subcategory Registration Product regitration

Fig 13.10 SELLER HOME
Seller operations are performed through the above table.
H products - Microsoft Internet Explorer
File Edit View Favorites Tools Help
©Back Q @ g] & p Search ^Favorites 0 g , £ l'UI^|4

PRODUCTS

v Q So Links


Select Category Select Subcategory Existing Mode h Add Model Name
Rate Quantity

FRIDGE
F1DDD
F11
F44
10009
70

<3
add property

Fig 13.11 PRODUCT REGISTRATION

Seller can register his products through this form.

Fig 13.12 EXISTING PRODUCT VIEW
Seller can view his products through this form.


Fig 13.13 PRODUCT UPDATION
Seller can update his product through this page.

Fig 13.14 BUYER REGISTRATION
New buyer can implement registration through this page.

Fig 13.15 BUYER LOGIN
Buyer can login through this page.

Fig 13.16 FORGET PASSWORD

User can use this page if he forgot his password.

Fig 13.17 PRODUCT SEARCH
User can search products through this form.

Fig 13.18 BILL
Bill is displayed in this form.


Fig 13.19 PAYMENT OPTION
Payment option can be made here.
CHAPTER 14
CONCLUSION
The project report entitled "eTRADE" has come to its final stage. The system has been developed with much care that it is free of errors and at the same time it is efficient and less time consuming. The important thing is that the system is robust. Also provision is provided for future developments in the system. We have tried our best to make the system user friendly. The entire system is secured.

APPENDICES
OVERVIEW OF MICROSOFT .NET
Microsoft .NET is software that connects information, people, systems, and devices. It spans clients, servers, and developer tools, and consists of:
The .NET Framework 1.1, used for building and running all kinds of software, including Web-based applications, smart client applications, and XML Web services”components that facilitate integration by sharing data and functionality over a network through standard, platform-independent protocols such as XML (Extensible Markup Language), SOAP, and HTTP.
Developer tools, such as Microsoft Visual Studio® .NET 2003 which provides an integrated development environment (IDE) for maximizing developer productivity with the .NET Framework.
A set of servers, including Microsoft Windows® Server 2000, Microsoft SQL Server„¢, and Microsoft BizTalk® Server, that integrates, runs, operates, and manages Web services and Web-based applications.
Client software, such as Windows XP, Windows CE, and Microsoft Office XP, that helpsdevelopers deliver a deep and compelling user experience across a family of devices and existing products. What Is the .NET Framework
The .NET Framework is an integral Windows component for building and running the next generation of software applications and Web services. The .NET Framework: Supports over

20 different programming languages. Manages much of the plumbing involved in developing software, enabling developers to focus on the core business logic code. Makes it easier than ever before to build, deploy, and administer secure, robust, and high-performing applications. The .NET Framework is composed of the common language runtime and a unified set of class libraries.
Common Language Runtime (CLR) Class Libraries
Base classes provide standard functionality such as input/output, string manipulation, security management, network communications, thread management, text management, and user interface design features.
The ADO.NET classes enable developers to interact with data accessed in the form of XML through the OLE DB, ODBC, Oracle, and SQL Server interfaces. XML classes enable XML manipulation, searching, and translations. The ASP.NET classes support the development of Web-based applications and Web services. The Windows Forms classes support the development of desktop-based smart client applications.
Together, the class libraries provide a common, consistent development interface across all languages supported by the .NET Framework
Visual Studio .NET 2003
Visual Studio .NET 2003 includes a range of new features and enhancements for every type of developer, and offers key improvements directed at mobile device developers and enterprise developers.
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 server. Unlike its interpreted predecessors, ASP.NET can take advantage of early binding, just-in-time compilation, native optimization, and caching services right out of the box. This amounts to dramatically better performance before you ever write a line of code World-Class Tool Support.
The ASP.NET framework is complemented by a rich toolbox and designer in the Visual Studio integrated development environment. WYSIWYG editing, drag-and-drop server controls, and automatic deployment are just a few of the features this powerful tool provides: Power and Flexibility.
Because ASP.NET is based on the common language runtime, the power and flexibility of that 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 languages. Simplicity.
ASP.NET makes it easy to perform common tasks, from simple form submission and 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 events in a simple, Visual Basic - like forms processing model. Additionally, the common language runtime simplifies development, with managed code services such as automatic reference counting and garbage collection Manageability.
ASP.NET employs a text-based, hierarchical configuration system, which simplifies applying settings to your server environment and Web applications. 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 applications as well. An ASP.NET Framework application is deployed to a server simply by copying the necessary files to the server. 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 applications constantly available to handle requests
Customizability and Extensibility.
ASP.NET delivers a well-factored architecture that allows developers to "plug-in" their code at the appropriate level. In fact, it is possible to extend or replace any subcomponent of the ASP.NET runtime with your own custom-written component. Security.
With built in Windows authentication and per-application configuration, you can be assured that your applications are secure. Language Support
The Microsoft .NET Platform currently offers built-in support for three languages: C#, Visual Basic, and JScript. The exercises and code samples in this tutorial demonstrate how to use C#, Visual Basic, and JScript to build .NET applications. Language Compatibility
The differences between the VBScript used in ASP and the Visual Basic .NET language used in ASP.NET are by far the most extensive of all the potential migration issues. Not only has ASP.NET departed from the VBScript language to "true" Visual Basic, but the Visual Basic language itself has undergone significant changes in this release.
TOOL SELECTED: VISUAL C#. NET
Visual C# .Net is designed to be a fast and easy way to create .NET applications, including Web services and ASP.NET Web applications. Applications written in Visual C# are built on the services of the common language runtime and take full advantage of the .NET Framework.
It is a simple, elegant, type-safe, object-oriented language recently developed by Microsoft for building a wide range of applications. Anyone familiar with C and similar
languages will find few problems in adapting to C#. C# is designed to bring rapid development to the C++ programmer without sacrificing the power and control that are a hallmark of C and C++. Because of this heritage, C# has a high degree of fidelity with C and C++, and developers familiar with these languages can quickly become productive in C#. C# provides intrinsic code trust mechanisms for a high level of security, garbage collection, and type safety.
It is fully integrated with the .NET Framework and the common language runtime, which together provide language interoperability, garbage collection, enhanced security, and improved versioning support. C# simplifies and modernizes some of the more complex aspects of C and C++, notably namespaces, classes, enumerations, overloading, and structured exception handling. C# also eliminates C and C++ features such as macros, multiple inheritance, and virtual base classes. For current C++ developers, C# provides a powerful, high-productivity language alternative.
Visual C# provides prototypes of some common project types, including:
¢ Windows Application.
¢ Class Library.
¢ Windows Control Library.
¢ ASP.NET Web Application.
¢ ASP.NET Web Service.
¢ Web Control Library.
¢ Console Application.
¢ Windows Service.
DATABASE
Microsoft SQL Server 2000
SQL Server 2000 exceeds dependability requirements and provides innovative capabilities that increase employee effectiveness, integrate heterogeneous IT ecosystems, and maximize capital and operating budgets. SQL Server 2000 provides the enterprise data management platform your organization needs to adapt quickly in a fast-changing environment.
With the lowest implementation and maintenance costs in the industry, SQL Server 2000 delivers rapid return on your data management investment. SQL Server 2000 supports the rapid development of enterprise-class business applications that can give your company a critical competitive advantage.
Benchmarked for scalability, speed, and performance, SQL Server 2000 is a fully enterprise-class database product, providing core support for Extensible Markup Language (XML) and Internet queries.
Easy-to-Use Business Intelligence
These tools Through rich data analysis and data mining capabilities that integrate with familiar applications such as Microsoft Office, SQL Server 2000 enables you to provide all of your employees with critical, timely business information tailored to their specific information needs. Every copy of SQL Server 2000 ships with a suite of BI services. Self-Tuning and Management Capabilities
Revolutionary self-tuning and dynamic self-configuring features optimize database performance, while management tools automate standard activities. Graphical tools and wizards simplify setup, database design, and performance monitoring, allowing database administrators to focus on meeting strategic business needs. Data Management Applications and Services
Unlike its competitors, SQL Server 2000 provides a powerful and comprehensive data management platform. Every software license includes extensive management and development tools, a powerful extraction, transformation, and loading (ETL) tool, business intelligence and analysis services, and new capabilities such as Notification Services. The result is the best overall business value available. SQL Server 2000 Enterprise Edition(64 bit)
Enterprise Edition (64-bit) provide the most scalable data platform to take advantage of the class of Intel Itanium-based servers. Addressing more memory than any other edition of SQL Server, it scales to the performance levels required to support the largest Data warehousing and analysis applications, ecommerce websites and Enterprise business systems. Supporting up to 8 nodes in failover clustering, SQL Server 2000 (64-bit) provides a high level of reliability and availability for your mission-critical applications
SQL Server 2000 Enterprise Edition
Enterprise Edition includes the complete set of SQL Server data management and analysis features and is uniquely characterized by several features that make it the most scalable and available edition of SQL Server 2000. It scales to the performance levels required to support the largest Web sites, Enterprise Online Transaction Processing (OLTP) systems and Data Warehousing systems. Its support for failover clustering also makes it ideal for any mission critical line-of-business application. Additionally, this edition includes several advanced analysis features that are not included in SQL Server 2000 Standard Edition. There are four main areas in which the additional features of SQL Server 2000 Enterprise Edition are most evident: Scalability Availability/uptime Performance Advanced analysis
SQL Server 2000 Standard Edition
Standard edition is an affordable option for small and medium-sized organizations. It includes the core functionality needed for non-mission-critical e-commerce, data warehousing, and line-of-business solutions. For instance, all of the XML features present in Enterprise Edition are also included in Standard Edition. And while a handful of advanced OLAP features are reserved for Enterprise Edition, all data mining features and the core OLAP functionality are included in SQL Server 2000 Analysis Services in Standard Edition. Similarly, components that other database vendors charge for as separate add-on products for their highest-end editions are included in Standard Edition: Data Transformation Services (DTS) Replication (snapshot, transactional, and merge) Full-Text Search English Query Stored procedure development and debugging tools SQL Profiling and performance analysis tools

RESUME
The developed system is flexible and changes can be made easily. The system is developed with an insight into the necessary modification that may be required in the future. Hence the system can be maintained successfully without much rework.
One of the main future enhancements of our system is to add a images so that buyer can see the images of the products while searching. Such that the system can be made more user friendly.

1. microsoftmsdn
2. w3schools.com
3. msdn.microsoft.com
4. apress.com
5. wrox.com