CHAPTER 1

INTRODUCTION

1.1 PROBLEM STATEMENT

1.1.1 Existing System:

In existing system we can only see what are the projects available. If

we want to bid on a particular project we have to send the bid document through the

post. The time taken by the whole process is too long. The administrator should

include extra labour and therefore labour cost increases.

1.1.2 Proposed System:

The proposed System is easy to use there is no necessary to train ,the

users with a little bit of knowledge of computer can handle the system.There is a

opportunity for all to bid also from home online and brought a drastic change like

never seen before by this.We can also change the bid value utill the enddate

specified by the customer is finished.The security in this system is more.No one can

change bid value with out right login.

1.2 FEASIBILITY STUDY

Once the problem is clearly understood, the next step is to conduct feasibility study,

which is high-level capsule version of the entered systems and design process. The

objective is to determine whether or not the proposed system is feasible.

1

The three tests of feasibility have been carried out.

Technical Feasibility

Economical Feasibility

Operational Feasibility

Technical Feasibility:

In Technical Feasibility study, one has to test whether the proposed

system can be developed using existing technology or not. It is planned to implement

the proposed system using java technology. It is evident that the necessary hardware

and software are available for development and implementation of the proposed

system. Hence, the solution is technically feasible.

Economical Feasibility:

As part of this, the costs and benefits associated with the proposed

system compared and the project is economically feasible only if tangible or

intangible benefits outweigh costs. The system development costs will be significant.

So the proposed system is economically feasible.

Operational Feasibility:

It is a standard that ensures interoperability with out stifling

competition and innovation among users, to the benefit of the public both in terms of

cost and service quality. The proposed system is acceptable to users. So the proposed

system is operationally feasible.

2

CHAPTER 2

LITERATURE OVERVIEW

2.1 JAVA

Java was conceived by James Gosling, Patrick Naughton, Chris

Warth, Ed Frank, and Mike Sherdian at Sun Microsystems in 1991.

Features of Java:

Simple & Secure

Robust

Multi-Threaded

Distributed

Dynamic

Encapsulation

Inheritance

Polymorphism

2.2 JAVA SCRIPT

Java script is a scripting language used for webpages, with javascript you

have many possibilities for enhancing your HTML page with interesting

elementsJavaScript is a script-based programming language that was developed by

3

Netscape Communication Corporation. JavaScript was originally called Live Script and

renamed as JavaScript to indicate its relationship with Java. JavaScript supports the

development of both client and server components of Web-based applications. On the

client side, it can be used to write programs that are executed by a Web browser within

the context of a Web page.

On the server side, it can be used to write Web server programs that can

process information submitted by a Web browser and then updates the browser’s display

accordingly. Even though JavaScript supports both client and server Web programming,

we prefer JavaScript at Client side programming since most of the browsers supports it.

JavaScript is almost as easy to learn as HTML, and JavaScript statements can be

included in HTML documents by enclosing the statements between a pair of scripting

tags

<SCRIPTS>.. </SCRIPT>.

<SCRIPT LANGUAGE = “JavaScript”>

JavaScript statements

</SCRIPT>

Here are a few things we can do with JavaScript:

Validate the contents of a form and make calculations.

Add scrolling or changing messages to the Browser’s status line.

Animate images or rotate images that change when we move the mouse over

them.

Detect the browser in use and display different content for different browsers.

Detect installed plug-ins and notify the user if a plug-in is required.

4

2.3 JSP

JavaServerPages (JSP) technology allows us to easily create web

content that has both static and dynamic components. JSP technology makes

available all the dynamic capabilities of Java Servlet technology but provides a more

natural approach to creating static content.

The main features of jsp technology are

A language for developing JSP pages, which are text-based documents that

describe how to process a request and construct a response.

An expression language for accessing server-side objects

JSP is a java based Server-side scripting language that allows static

HTML to be mixed with dynamically-generated HTML.Behind scenes, a JSP is

compiled into a java servlet and processed by a java-enabled web Server.

The JSP engine transforms JSP tags, java code and static HTML

content into java code which is then automatically organized by the JSP engine into

an underlying Java servlet, after which the servlet is then automatically complied

into java byte codes.

The commonly used tags in this application are:

Directive Tags

Declaration Tags

Expression Tags

Script Tags

2.4 ORACLE

5

2.4.1 Oracle Security

To Protect against unauthorized use, oracle provides fail-safe security and

monitor data access. These are used to manage the data and for providing security.

2.4.2 SQL – The Structured Query Language

SQL is a simple, powerful database access language that is the standard

language for relational database management system. The SQL implemented by

Oracle Corporation.

2.4.3 SQL statements

All operations on the information in an oracle database are performed using

SQL statements. A SQL statement is a string of SQL text that is given to oracle to

execute.

SQL statements are divided into the following categories:

Data Definition Language(DDL) statements

Data Manipulation Language (DML) statements.

Transaction Control statements.

Session Control statements.

Embedded SQL statements.

2.5 JAVA DATABASE CONNECTIVITY

6

2.5.1 What Is JDBC?

JDBC is a Java API for executing SQL statements. (As a point of

interest, JDBC is a trademarked name and is not an acronym; nevertheless, JDBC is

often thought of as standing for Java Database Connectivity. It consists of a set of

classes and interfaces written in the Java programming language. JDBC provides a

standard API for tool/database developers and makes it possible to write database

applications using a pure Java API.

Using JDBC, it is easy to send SQL statements to virtually any relational database.

One can write a single program using the JDBC API, and the program will be able to

send SQL statements to the appropriate database. The combinations of Java and

JDBC lets a programmer write it once and run it anywhere.

What Does JDBC Do? Simply put, JDBC makes it possible to do three things:

Establish a connection with a database

Send SQL statements

Process the results.

2.5.2 JDBC Driver Types:

The JDBC drivers that we are aware of at this time fit into one of four categories:

JDBC-ODBC bridge plus ODBC driver

Native-API partly-Java driver

JDBC-Net pure Java driver

Native-protocol pure Java driver

2.5.3 JDBC-ODBC Connectivity

7

Seven basic steps to JDBC:

There are seven basic steps to use JDBC to accessing a database.

1. Importing the java.sql package.

2. Load and register the driver.

3. Establish a connection to the database server.

4. Create a statement.

5. Execute the statement.

6. Retrieve the results.

7. Close the statement and connection.

.

8

CHAPTER 3

SYSTEM REQUIREMENTS SPECIFICATION

3.1 PROCESS MODEL

To solve actual problems in an industry setting, a software engineer or a team

of engineers must incorporate a development strategy that encompasses that process,

methods, and tools. This strategy is often referred to as process model or a software

engineering paradigm.

A process model for software engineering is chosen based on the nature of

the project and application, the methods and tools to be used and the controls and the

deliverables that are required.

So, our application is based on the Object Oriented Approach. In this

model we

design the UML diagrams like Use case, Activity, Sequence, Collaboration and

Class diagrams.

3.2 SYSTEM REQUIREMENTS

3.2.1 Functional Requirements:

1. Output Design: outputs from computer systems are required primarily to

communicate the results of processing to users. They are also to provide a

permanent copy of the results for later consultation.

9

2. Output Definition: outputs should be defined in terms of type, content,

format, location, frequency, volume and sequence. For example decimal

points need to be inserted.

3. Output media: Main considerations are suitability for the device to

particular application, need for hard copy, response time required.

4. Input design: Main objective is to produce a cost effective method of input,

achieve highest possible level of accuracy.

5. Input Stages: Input stages are data recording, data transcription, data

conversion, data verification, data control, data transmission, data validation,

data correction.

6. Input Types: Inputs are external, internal, operational, and interactive.

7. Input media: considers type of input, flexibility of format, speed, accuracy,

verification, rejection rates, ease of correction, security.

3.2.2 Non Functional Requirements:

Software Requirements:

Operating System : Windows XP/2000

User Interface : HTML, CSS

Client-side Scripting : JavaScript

Programming Language : Java

Web Applications : JSP

Database : Oracle

Hardware Requirements:

Processor : Pentium IV

Hard Disk : 40GB

10

RAM : 256MB

3.3 APPLICATION FEATURES

Moduls in Online Tender Handling System:

1.Login

2.Registration

3.Post Tender Details

4.View Tender Details

5.Bidding The Tender

Login:

The function of this module is for the users to login into their account. In this

system there are two types of users Customers and Vendors.They login into their

account by using their username and password.The username is unique for each user.

Regisration:

The users who are not registered in our system are registered in this module.

Here the users must fill the registration form which contains username ,password,

company details,e-mail id etc.

Post Tender Details:

This module is for the Customers who post their tenders.Here they fill the

tender details like domain,tender name,end-date,and a file which contains the brief

description about the tender.

View Tender Details:

11

All the users can view the tenders list by using this module.The guesr users

also can view the tender details by using this module.

Bidding The Tender:

The vendors can bid the selected tenders by using this module.The Vendor

can bid any number of tenders.

12

CHAPTER 4

SYSTEM ANALYSIS

4.1 USE CASE DIAGRAM

4.1.1 UML Approach:

UML stands for unified modeling language. UML is a language for

specifying, visualizing and documenting the system. This step while developing the

product after analysis. The goal from this is to produce a model of the entities that

are to used in the product been developed need to be designed.

Software design is a process that gradually changes as various new, better and

more complete methods with broader understanding of the whole problem in general

come in to existence. There are various types if methods in software design.

4.1.2 Usecase Diagram:

Use-case diagrams graphically depict system behavior.These

diagrams present a high level view of how the system is used as viewed from an

outsider’s (actor’s) perspective. Usecase diagram consists of usecases and actors

and shows the interaction between the usecases and actors. The purpose is to show

13

the interactions between usecases and actors to represent the system requirement

from user’s perspective. It must be remembered that the usecases are the function

that are to be performed in the module. An actor could be the end user of the system

or the external system.

Actor: Actor represents the role a user plays with respect to the system. An actor

interacts with, but has no control over the use cases.

An actor is someone or something that:

Interacts with or uses the system.

Provides input to and receives information from the system.

The Main Actors identified in OTHS are:

Administrator

Customer

Vendor

The Main UseCases Identified in OTHS are:

Login

Register

Post Tenders

View Tenders

Bid The Tender

View Bids

Maintain Contact Details

14

4.2 FLOW OF EVENTS:

A flow of events is a sequence of transactions (or events) performed by

the system. They typically contain very detailed information, written in terms of

what the system should do, not how the system accomplishes the task. Flow of

events are created as separate files or documents in your favorite text editor and then

attached or linked to a use case using the Files tab of a model element.

A flow of events should include:

When and how the use case starts and ends

Use case/actor interactions

Data needed by the use case

Normal sequence of events for the use case

Alternate or exceptional flows

15

Use case diagrams for Online Tender Handling System:

Maintain Contact Details

View tenders list

Vendor

Register

Login

View Bids

Customer

Bid the Tender

Administrator

Post tenders

Fig 4.2.1 Use Case diagram

16

4.3 ER-diagram for Online Tender Handling System:

registration

uname

pdomain

pname

uname

End-datePfile

Bid ampount

End-date

pname

vendor

customer

Email id

Company details

lnamefname

password

Biddingbidding

Bids

n

postsn

Refno

Post tendersRefno

Fig 4.3.1 ER-Diagrm for Online Tender Handling System

17

CHAPTER 5

SYSTEM DESIGN

5.1 ACTIVITY DIAGRAM

Activity diagrams provide a way to model the workflow of a business

process, code-specific information such as a class operation. The transitions are

implicitly triggered by completion of the actions in the source activities. The main

difference between activity diagrams and state charts is activity diagrams are activity

centric, while state charts are state centric. An activity diagram is typically used for

modeling the sequence of activities in a process, whereas a state chart is better suited

to model the discrete stages of an object’s lifetime.

Actions on activities can occur at one of four times:

On entry ---- The "task" must be performed when the object enters

the state or activity.

18

On exit ---- The "task" must be performed when the object exits the

state or activity.

Do ---- The "task" must be performed while in the state or

activity and must continue until exiting the state.

On event ---- The "task" triggers an action only if a specific event is

received.

Activity Diagrm For Online Tender Handling System:

19

Fig 5.1.1 Activity Diagram for Online Tender Handling System

5.2 SEQUENCE DIAGRAMS:

20

A sequence diagram is a graphical view of a scenario that shows object interaction in

a time-based sequence what happens first, what happens next. Sequence diagrams

establish the roles of objects and help provide essential information to determine

class responsibilities and interfaces.

There are two main differences between sequence and collaboration

diagrams: sequence diagrams show time-based object interaction while collaboration

diagrams show how objects associate with each other.

A sequence diagram has two dimensions: typically, vertical placement represents

time and horizontal placement represents different objects.

Object: An object has state, behavior, and identity. The structure and behavior of

similar objects are defined in their common class. Each object in a diagram indicates

some instance of a class. An object that is not named is referred to as a class

instance.

The object icon is similar to a class icon except that the name is underlined:

An object's concurrency is defined by the concurrency of its class.

Message: A message is the communication carried between two objects that trigger

an event. A message carries information from the source focus of control to the

destination focus of control.

The synchronization of a message can be modified through the message

specification.

Synchronization means a message where the sending object pauses to wait for

results.

Link: A link should exist between two objects, including class utilities, only if there

is a relationship between their corresponding classes. The existence of a relationship

between two classes symbolizes a path of communication between instances of the

classes: one object may send messages to another. The link is depicted as a straight

line between objects or objects and class instances in a collaboration diagram. If an

object links to itself, use the loop version of the icon.

21

Sequence diagram for Login:

: Login : User : Registration : Member Details

1: Enter UserName and Password

2: Submit The Details

5: Successfully login for valid user

6: You are not valid user please Register

3: Check the details

4: Forward the details

Fig 5.2.1 Sequence diagram for Login

Sequence diagram for Registration :

22

: User : Login : Member Details : REgistration

6: Login into account

3: Fill the details

4: Account is created

1: Request for Registration

2: Send the Registration form

5: Account is added to Member Details

Fig 5.2.2 Sequence diagram for Registration

Sequence diagram for Post Tenders :

23

: Administrator : Customer : Tender Control : publishing

4: Publish The tender for bids

2: store the tender

1: Post The Tender Details

3: Forward The Tender Details

Fig 5.2.3 Sequence diagram for Post Tenders

Sequence diagram for Bid Tenders:

24

: Customer : Vendor : Bidding : Tender Control

3: Bid the selected tenders

5: Select the Bid

1: View the tenders

2: Select The Tender To Bid

4: Forward The Bidding Details

Fig 5.2.4 Sequence diagram for Bid Tenders

5.3 COLLABORATION DIAGRAMS

Collaboration diagrams and sequence diagrams are alternate

representations of an interaction. A collaboration diagram is an interaction diagram

25

that shows the order of messages that implement an operation or a transaction. A

sequence diagram shows object interaction in a time-based sequence.

Collaboration diagrams show objects, their links, and their messages. They can also

contain simple class instances and class utility instances. Each collaboration diagram

provides a view of the interactions or structural relationships that occur between

objects and object-like entities in the current model.

Differences between sequence and Collaboration diagrams are:

1. Sequence diagram is easy to read.

2. Collaboration diagram can be used to indicate how objects are statically

connected.

3. There is no numbering in sequence diagram.

4. Sequence diagram shows the links between objects in a time based sequence.

5. Collaboration diagram shows how the objects associate with each other

Collaboration Diagrams for Login:

26

: Login : User

: Registration : Member Details

1: Enter UserName and Password

2: Submit The Details

3: Check the details

4: Forward the details

5: Successfully login for valid user

6: You are not valid user please Register

Fig 5.3.1 Collaboration Diagrams for Login

Collaboration Diagrams for Registration:

27

: User : Login

: Member Details : REgistration

1: Request for Registration

2: Send the Registration form

3: Fill the details

4: Account is created

5: Account is added to Member Details

6: Login into account

Fig 5.3.2 Collaboration Diagrams for Registration

Collaboration Diagrams for Post Tender Details:

28

: Administrator : Customer

: Tender Control

: publishing

2: store the tender

4: Publish The tender for bids

1: Post The Tender Details3: Forward The Tender Details

Fig 5.3..3 Collaboration Diagrams for Post Tender Details

Collaboration Diagrams for Post Bid Details:

29

: Customer

: Vendor

: Bidding : Tender Control

5: Select the Bid

2: Select The Tender To Bid

3: Bid the selected tenders1: View the tenders

4: Forward The Bidding Det...

Fig 5.3.4 Collaboration Diagrams for Post Bid Details

5.4 CLASS DIAGRAM

30

This is one of the most important of the diagrams in development.

The diagrams break the class into three layers. One has the name, second describes

its attributes and third its methods. A padlock to the left of the name represents the

private attributes.

The relationships are drawn between the classes. Developers use the class

diagram to develop the classes. Analysis uses it to show the details of the system.

Architects look at the class diagram to see if any class has too many functions and

see if they are required to be split.

Class Diagram For Online Tender Handling System:

Tender ControlTenderName : StringTenderNumber : String

UpdateTender()StoreTender()

Publishing

PublishTenders()

VendorVendor UserID : StringVendorPassword : String

ViewTenders()SelectTenders()BidTenders()

11

11

BiddingBidAmount : Integer

StoreBiddingInformation()UpdateBiddingInformation()Forward Bidding Information()

1..n1

1..n1

CustomerCustomerUserID : SingleCustomerPassword : String

PostTenderSpecifications()ViewResponse()EvaluateTenderResponse()

1..n

1

1..n

1

Registration

CreateAccount()

1

1

1

1

1

1

1

1

AdministratorSubmission Date : Date

PublishTheTenders()MaintainContactInformation()

1

1

1

1

1..n

1

1..n

1

Member Details

VerifyLoginDetails()StoreregistrationDetails()GetUserDetails()

1

1

1

11

11

1

LoginUserName : StringPassword : String

RequestUserName&Password()CheckDetails()

1

1

1

1

11

11

11

11

Fig 5.4.1 Class Diagram

31

5.5 ARCHITECTURAL DESIGN:

5.5.1 3-Tier Architecture:

The three-tier software architecture (a.k.a. three layer architectures) emerged

in the 1990s to overcome the limitations of the two-tier architecture. The third tier

(middle tier server) is between the user interface (client) and the data management

(server) components. This middle tier provides process management where business

logic and rules are executed and can accommodate hundreds of users (as compared

to only 100 users with the two tier architecture) by providing functions such as

queuing, application execution, and database staging

Fig 5.5.1 3-Tier Architecture

The three tier architecture is used when an effective distributed

client/server design is needed that provides (when compared to the two tier)

increased performance, flexibility, maintainability, reusability, and scalability, while

hiding the complexity of distributed processing from the user. These characteristics

have made three layer architectures a popular choice for Internet applications and

net-centric information systems.

32

5.5.2 Technical Details:

A three tier distributed client/server architecture includes a user system

interface top tier where user services (such as session, text input, dialog, and display

management) reside.

Fig 5.5.2 three tier distributed client/server architecture depiction

Advantages of Three-Tier:

Separates functionality from presentation.

Clear separation - better understanding.

Changes limited to well defined components.

Can be running on WWW.

Effective network performance.

5.5.3 Functional Architecture:

1. Functional View of Registration:

A request for Registration is sent to the server from the client.

These client details from registration server are stored in database.

The server retrieves the Employee details and sends it back to the

client after registration is done successfully.

33

Fig 5.5.3 : Functional View Of Registration

2. Functional view of Login:

The Authentication of the user is provided using user name and password is

sent to the server.

The database stores the username,password and checks whether he is the

valid user when the registration takes place.

The server sends the response o the client from the server indicating

whether he is a valid user or not.

Fig 5.5.4: Functional View Of Login

34

Request ForRegistration

ResponseEmployee Details

Stores Employee details

SERVERRDBMS

CLIENT

Authenticatiion of user

Valid / InvalidUser

Valid / InvalidUser

Checks for Authenticatiion

SERVERRDBMS

CLIENT

3. Technical Diagram:

Fig 5.5.5 : Technical Diagram

5.6 DATABASE DESIGN:

What is SQL?

SQL, the Structured Query Language is an ANSI (American National

Standards (Institute) standard for accessing database systems. SQL statements

are used to retrieve and update data in the database. SQL works with database

programs like Access, DB2, Informix, Microsoft SQL Server, Oracle, Sybase

and many others.

SQL Queries

With SQL the user can query a database and have a result returned in a tabular

form.

SQL Data Manipulation:

35

HTTPrequest

HTTP Response

JDBC

JDBC

SERVER RDBMSCLIENT

As the name indicates, SQL is syntax for executing queries. But the

SQL language also indicates syntax to update records, insert new records and

delete existing records. These query and update commands together form the

Data Manipulation Language (DML) part of SQL.

SELECT-extracts data from a database.

UPDATE-updates data in a database.

DELETE-deletes data from a database.

INSERT-inserts new data into a database.

SQL Data Definition:

The Data Definition Language (DDL) part of SQL permits database

tables to be created or deleted. Also indices can be defined, and links can be

specified between tables.

The most important DDL statements in SQL are:

CREATE TABLE-Creates a new database table.

ALTER TABLE-Alter a database table.

DROP TABLE-Deletes a database table.

CREATE INDEX-Creates an index (Search key).

DROP INDEX-Deletes an index.

5.7 PERSISTENCE:

36

Tables:

The tables that are created in the database to implement this system are:

Registration Table:

Attribute Data Type Size Constraints

Fname Varchar2 10 Not Null

Lname Varchar2 10 Not Null

Uname Varchar2 10 Not Null

Paswd Varchar2 10 Not Null

Authority Varchar2 10 Not Null

Cdetails Varchar2 100 Not Null

Primary key:uname

TABLE 5.7.1 Registration

Tender Details Table:

Attribute Data Type Size Constraints

Pdomain VarChar2 15 Not Null

Pname VarChar2 20 Not Null

EndDate VarChar2 20 Not Null

Uname VarChar2 10 Not Null

RefNo Varchar2 10 Not Null

Primary key:Refno

Foreign Key:Uname

TABLE 5.7.2 Project Details Table

Bid Details Table:

37

Attribute Data Type Size Constraints

Pdomain Varchar2 15 Not NullPname Varchar2 20 Not NullEndDate Varchar2 20 Not NullCompany Varchar2 20 Not NullBidAmount Number 10 Not NullVendor Varchar2 10 Not NullCustomer Varchar2 10 Not NullRefNo Varchar2 10 NotNull

Primary key:Refno

Foreign Key:Uname

Table 5.7.3 Bid Details

38

CHAPTER 6

USER INTERFACE SCREENS

Home Page Of Our System:

39

The List Of Availabe Tenders:

40

Registration Form:

Registration Confirmation:

41

Customer Home Page:

Post Tenders Details:

42

Tender Posting Confirmation:

View Tender Details:

43

View Individual Tendor Details:

See The Tendor File:

44

View The Bids:

If the Last Date is Not Reached:

45

Vendor Home Page:

View The Tendor Details:

46

View Individual Tendor Details:

Bid On The Project:

47

Confirmation Of Posting Of Bid:

48

Changing Of Bid:

49

Confirmation Of Changing The Bid:

Administrator Home Page:

50

List Of Customers:

Delete a Customer:

51

List Of Vendors:

Delete a Vendor:

52

Confirmation Of Deletion:

If the usrname is Invalid:

53

CHAPTER 7

TESTING

Testing is the process of detecting errors. Testing performs a very

critical role for quality assurance and for ensuring the reliability of software. The

results of testing are used later on during maintenance also

7.1 Psychology of Testing

The aim of testing is often to demonstrate that a program works by

showing that it has no errors. The basic purpose of testing phase is to detect the

errors that may be present in the program. Hence one should not start testing with the

intent of showing that a program works, but the intent should be to show that a

program doesn’t work. Testing is the process of executing a program with the intent

of finding errors.

7.2 Testing Objectives

The main objective of testing is to uncover a host of errors,

systematically and with minimum effort and time. Stating formally, we can say,

Testing is a process of executing a program with the intent of finding

an error.

A successful test is one that uncovers an as yet undiscovered error.

A good test case is one that has a high probability of finding error, if

it exists.

The tests are inadequate to detect possibly present errors.

The software more or less confirms to the quality and reliable

standards.

54

7.3 Different Types Of Testing used in our system:

7.3.1 Unit Testing:

Unit testing focuses verification effort on the smallest unit of software i.e.

the module. Using the detailed design and the process specifications testing is done

to uncover errors within the boundary of the module. All modules must be successful

in the unit test before the start of the integration testing begins.

In this project each service can be thought of a module. There are so many

modules like Login, registration,Add tenders,bid on tenders. Giving different sets of

inputs has tested each module. When developing the module as well as finishing the

development so that each module works without any error. The inputs are validated

when accepting from the user.

Software units in a system are the modules and routines that are assembled

and integrated to form a specific function. Unit testing is first done on modules,

independent of one another to locate errors. This enables to detect errors. Through

this errors resulting from interaction between modules initially avoided.

7.3.2 Integration Testing:

After the unit testing we have to perform integration testing. The goal here

is to see if modules can be integrated properly, the emphasis being on testing

interfaces between modules. This testing activity can be considered as testing the

design and hence the emphasis on testing module interactions.

In this project integrating all the modules forms the main system. When

integrating all the modules I have checked whether the integration effects working of

any of the services by giving different combinations of inputs with which the two

services run perfectly before Integration.

55

7.3.3 System Testing:

Here the entire software system is tested. The reference document for this

process is the requirements document, and the goal as to see if software meets its

requirements.

7.4 Results of Testing for our Application:

7.4.1.Registration Test Case:

Table 7.4.1 registration test case

7.4.2. Login Test Case:

56

Result: Success

Conditions Verified: yes

Expected Results: Confirming the storage of all the details of user

Action Performed: Entering the details of User

Pre Conditions: Database Connectivity

Test Description: To verify the Registration of user

Test Case: Checking Registration

Result : Success

Conditions Verified : yes

Expected Results : Login name and password are verified and for wrong user display mismatch errors

Action Performed : entered the login name and password

Test Environment :no special devices are required

Pre Conditions : Database Connectivity

Test Description : To verify user ID of the user

Test Case : logged in to the system

Table 7.4.2 login test case

7.4.3. Posting Tender Test Case:

Table 7.4.3 post project test case

7.4.4. Bidding for the Tender TestCase:

Table 7.4.4 :bid project test case

57

Result: Success

Conditions Verified: yes

Expected Results: Display of the screen indicating posted successfully

Action Performed: Entering the details required for posting the project

Pre Conditions: Database Connectivity

Test Description: To post a project of the customer

Test Case: Posting a Project

Result : Success

Conditions Verified : yes

Expected Results : screen display indicating bidding successfully completed

Action Performed : Entered details for bidding for the project

Test Environment : no devises are required

Pre Conditions : Database Connectivity

Test Description : To bid for the Tender selected by the Vendor

Test Case : Bidding for the Tender

CHAPTER 8

MAINTENANCE

Corrective maintenance:

This acts to correct errors that are uncovered after the software is in use.

Adaptive maintenance:

This is applied when changes is the external environment precipitate

modifications to software.

Preventive maintenance:

This improves future maintainability and reliability and provides basis for

future enhancements.

58

CHAPTER 9

CONCLUSION AND FUTURE WORK

CONCLUSION:

The ONLINE TENDER HANDLING SYSTEM developed by us has

made the best possible efforts to satisfy the needs of the customers who post their

tenders and vendors who bid on the tenders. This project is being a web-based and is

easily accessible to all the users in the organization. This system has been designed

as user-friendly. It will certainly reduce the tender cycle-time. It provides the user

flexibility.

FUTURE WORK:

This application is capable of managing the Tenders posting,Bid submission,

changing of bid amount with in end-date.The future work includes the customer will

select the suitable bid for his tender and intimate that to the particular vendor.The

search option to the users to search the tenders based on their names or reference

numbers. The online money transaction between the customers and the vendors

59

REFERENCES

Book References:

Ali Bahrami (2003),”Object Oriented Analysis And Design using UML”, 2nd

Edition Tata McGraw-Hill.

Herbert Schildt (2002),”Java 2 Programmers Reference”, 1st edition,

MCGraw -Hill companies.

Roger S.Pressman (2002),”Software Engineering: A Practioners Approach”,

5th Edition, Tata MCGraw-Hill..

Elamasri , Navathe (2002) , “Fundamental of database system” , 3rd edition ,

Pearson Education Asia.

Herbert Schildt (2002),”The Complete Reference Java2”, 5th edition, TATA

MCGraw -Hill edition.

Websites:

www.java.sun.com

www.w3schools.com

www.javascript-coder.com

www.tenders.gov.in

www.tenders.indiatimes.com.

60