ONLINE TENDER MANAGEMENT SYSTEM PROJECT REPORT

PROJECT REPORT

ONLINE TENDER MANAGEMENT SYSTEM PROJECT REPORT

ONLINE TENDER MANAGEMENT SYSTEM PROJECT REPORT

PROJECT SOURCE CODE

ONLINE TENDER MANAGEMENT SYSTEM PROJECT SOURCE CODE

FREE DOWNLOAD ALL THE PROJECT REPORTS WITH SOURCE CODE FROM HERE
ONLINE TENDER MANAGEMENT SYSTEM PROJECT REPORT

This is a plan to make tender publishing online. As a part of it, tender data is recorded along with particulars of the products, their specifications and conditions. Tenders published will be visible to the visitors of the site till the closing date of tender.

                       Many huge enterprises handle large/huge projects of government and other private enterprises. In all such projects thousands of employees would be working on them. Such enterprise requires purchases from various vendors for different purposes. The employees would float tenders globally by advertising in reputed news papers. Advertising in news papers involves lot of cost, searching in news papers is time-consuming, communication gap between buyers and suppliers (only way is through phone or mail), receiving bids and finalizing tenders takes a lot of time. So we make this whole process of tendering online which is efficient and consumes very less  time .

                    PROBLEM IDENTIFICATION

 Existing System:- ONLINE TENDER MANAGEMENT SYSTEM PROJECT

Present System: Many huge enterprises handle large/huge projects of government and other private enterprises. In all such projects thousands employees would be working on them.Such enterprise requires purchases from various vendors for different purposes. The employees would float tenders globally by advertising in reputed news papers.

Disadvantages:

• Advertising in news papers involves lot of cost.
• Once the paper is lost, you cannot view them.
• Searching in news papers is time-consuming.
• Communication gap between buyers and suppliers(only way is through phone or mail)
• Receiving bids and finalizing tenders takes a lot of time.

 Proposed System:-

           Here, the entire process of tendering is done online.

• Buyers publish tenders.
• Tenders consist of product name, its specifications, quantity etc.
• Suppliers log in and view the tender details.
• If the supplier is new, he registers in the website.
• Supplier can pose queries if he has any.
• Buyers answer the queries posed by suppliers.
• If interested, supplier bids for the product. Buyers view the bid and select the best bid.

Advantages:

• No cost for advertising in news papers.
• Tenders can be viewed anywhere and anytime.
• Suppliers can ask queries immediately.
• Bidding through online saves a lot of time.

Buyers can answer queries posed by suppliers immediately.

FEASIBILITY STUDY - ONLINE TENDER MANAGEMENT SYSTEM PROJECT

The next step in analysis is to verify the feasibility of the proposed system. “All projects are feasible given unlimited resources and infinite time“. But in reality both resources and time are scarce. Project should be confirmed to time bounce and should be optimal in there consumption of resources. This places a constant approval of any project. Feasibility which is applied to E-Tendering pertains to the following areas:

Technical feasibility
Operational feasibility
Economical feasibility

TECHNICAL FEASIBILITY:

                       To determine whether the proposed system is technically feasible, we should take into consideration the technical issues involved behind the system. E-Tendering uses the web technologies, which is rampantly employed these days worldwide. The world without the web is incomprehensible today. That goes to proposed system technically.

OPERATIONAL FEASIBILITY:

To determine the operational feasibility of the system we should take into consideration the awareness level of the users. This system is operational feasible since the users are familiar with the technologies and hence there is no need to gear up the personnel to use system. Also the system is very friendly and to use.

 ECONOMIC FEASIBILITY:

To decide whether a project is economically feasible or not, we have to consider various factors as:

• Cost benefit analysis
• Long-term returns
• Maintenance cost

Ø  The proposed   E-Tendering is computer based. It requires average computing capabilities and access to internet, which are very basic requirements and can be afforded by any organization hence it doesn’t incur additional economic overheads, which renders the system economically feasible.

SYSTEM ANALYSIS - ONLINE TENDER MANAGEMENT SYSTEM PROJECT

SOFTWARE REQUIREMENT SPECIFICATION:-

Ø  What is SRS?

              Software Requirement Specification (SRS) is the starting point of the software developing activity. As system grew more complex it became evident that the goal of the entire system cannot be easily comprehended.  Hence the need for the requirement phase arose.  The software project is initiated by the client needs. 

TheSRS is the means of translating the ideas of the minds of clients (the input) into a formal document (the output of the requirement phase.)

The SRS phase consists of two basic activities:

1)    Problem/Requirement Analysis: The process is order and more nebulous of the two, deals with understand the problem, the goal and constraints.

2)    Requirement Specification: Here the focus is on specifying what has been found giving analysis such as representation, specification languages and tools, and checking the specifications are addressed during this activity.

Document Conventions:

                     We have used Times New Roman (text size 12).Bold Font is used for Main Headings (text size of 20). Bold, Underline and Italicized font is used for Modules (text size of 14).Underlining is done for technically important words……

Intended Audience and Reading Suggestions:

                     

                   This document is for better understanding of E-TENDERING for various Mailing technologies. Mainly intended for Hod sir, Internal guide, Staff members, Users and colleagues. This detail given below guides every normal user to how to go through this document for better understanding .The sequence to follow for better understanding is here Purpose, Scope , Features of E-TENDERING Software, Operating requirements, Modules present in the project, Advantages, References etc…

              The Requirement phase terminates with the production of the validate SRS document. Producing the SRS document is the basic goal of this phase.

ROLE OF SRS:

The purpose of the Software Requirement Specification is to reduce the communication gap between the clients and the developers.  Software Requirement Specification is the medium though which the client and user needs are accurately specified.  It forms the basis of software development.  A good SRS should satisfy all the parties involved in the system.

SCOPE:

            This software is used for tender management and posted tenders can be viewed anywhere and anytime. Suppliers can ask queries immediately. Bidding online saves a lot of time and buyers can answer queries posted by suppliers immediately.

                                         

DATA FLOW DIAGRAMS

INTRODUCTION:

           The system specification is produced at the culmination of the analysis task.  The function and Performance allocated the software as part of the system engineering are refined by the established a complete information of performance requirements and design constraints, appropriate validation criteria, and others data pertaining to requirements. The tools that are used in this system analysis are data flow diagram and data dictionary.

DATA FLOW DIAGRAMS: ONLINE TENDER MANAGEMENT SYSTEM PROJECT

            A Data Flow Diagram (DFD) is a graphical technique that depicts information flow and the transforms that are applied as data move from input to output.

            Data flow diagram is a logical model of a system. The model does not depend on hardware, software, and data structure or file organization. It only shows the data flow between modules to module of the entire system. Data flow diagrams can be completed using only four notations as follows,

Data Flow Diagrams are of two types:

1)    Physical Data Flow Diagrams:  These are implementation-dependent i.e.,    they show the actual devices, departments, people, etc., involved in the system.

2)    Logical Data Flow Diagrams: These diagrams describe the system independently of how it is actually implemented, they show what takes places, rather than how an activity is accomplished.

Ø Data Flow: Data move in a specific direction from an origin to destination. The data flow is a “packet” of data.

                                                     

Ø Process: People, procedures or devices that produce data. The physical component is not identified.

 

Ø Source or Destination of Data: External sources or destinations of data, which may be people or organizations or other entities.

Ø Data Source: Here a process references the data in the system

HARDWARE AND SOFTWARE REQUIREMENTS - ONLINE TENDER MANAGEMENT SYSTEM PROJECT

Hard Ware Requirements:-

·         Processor:: Pentium-II(or) Higher

·         Ram:: 512MB (or) Higher

·         Cache:: 512MB

·         Hard disk:: 10GB

Soft Ware Requirements:-

·         Web Server	:	Tomcat 5.5
·         Server-side Technologies	:	Java, Java Server Pages
·         Client-side Technologies	:	Hyper Text Markup Language, Cascading Style Sheets, Java Script, AJAX
·         Database Server	:	MS Access
·         Operating System	:	Windows (or) Linux (or) Mac any version

  

SYSTEM DESIGN - ONLINE TENDER MANAGEMENT SYSTEM PROJECT

            System design is transition from a user oriented document to programmers or data base personnel. The design is a solution, how to approach to the creation of a new system. This is composed of several steps. It provides the understanding and procedural details necessary for implementing the system recommended in the feasibility study. Designing goes through logical and physical stages of development, logical design reviews the present physical system, prepare input and output specification, details of implementation plan and prepare a logical design walkthrough.

         The database tables are designed by analyzing functions involved in the system and format of the fields is also designed. The fields in the database tables should define their role in the system. The unnecessary fields should be avoided because it affects the storage areas of the system. Then in the input and output screen design, the design should be made user friendly. The menu should be precise and compact.

SOFTWARE DESIGN  : -

In designing the software following principles are followed:

1. Modularity and partitioning: Software is designed such that, each system should consists of hierarchy of modules and serve to partition into separate function.

2. Coupling: Modules should have little dependence on other modules of a system.

3. Cohesion: Modules should carry out in a single processing function.

4. Shared use: Avoid duplication by allowing a single module be called by other that need the function it provides.

MODULE DESIGN:-

The major modules of the project are:

·         Security and Accounts module

·         Product Management module

·         Tender Management module

·         Querying and Bidding Module

Security and Accounts Module:

               

              This specification is provided with privacy to prevent access to the unauthorized user accounts. This can be enhanced with a Pretty Good Privacy to provide security to various accounts.

Product Management module:

         Here the Administrator publishes tenders online. As a part of it, tender data is recorded along with the particulars of products, their specifications and conditions. Tenders recorded will be visible to the visitors of the site on a particular date as mentioned in the data. 

Tender Management module:

         Here the administrator modifies the tender if required, that is the particulars of products their specifications and conditions can be modified.

Querying and Bidding Module:

               Here suppliers login and view the tenders details. If the suppliers are new, he/she registers in the website. Suppliers can pose queries if he/she has any. Then buyers answer the queries posed by the suppliers. Here if interested, suppliers bid the product. Buyers view the bid and select the best bid

DATABASE TABLE - ONLINE TENDER MANAGEMENT SYSTEM PROJECT

Table Name: admin                                           

 Field Name                                      Data Type                                Constraints

                                           

Un	VARCHAR2 (20)	REFERENCE
Pwd	VARCHAR2 (20)	NOT NULL

Table Name : suppliers

   FieldName                                  Data Type                                                                       Constraints

Un	NUMBER(4)	NOT NULL
pwd	VARCHAR2 (20)	NOT NULL
company	VARCHAR2 (20)	NOT NULL
address	VARCHAR2 (20)	PRIMARY KEY
contact	VARCHAR2 (20)	NOT NULL

Table Name : master_product

Field Name                                           Data Type                            Constraints

Product_id	VARCHAR2 (20)	REFERENCE
Product_name	VARCHAR2 (1)	NOT NULL

 Table Name   : master_specification

Field Name                                        Data Type                                 Constraints

Product_id	VARCHAR2 (100)	NOT NULL
S_name	DATE	NOT NULL
S_units	DATE	NOT NULL

Table Name   : tender

Field Name                                       Data Type                                                                   Constraints

T_no	DATE	NOT NULL
Prod_name	DATE	NOT NULL
quntity	VARCHAR2 (10)	NOT NULL
P_date	VARCHAR2 (20)	REFERENCE
C_date	VARCHAR2(20)	REFERENCE

Table Name  : tender_specification

Field Name                                          Data Type                               Constraints

T_no	VARCHAR2 (20)	REFERENCE
Prod_name	VARCHAR2 (10)	NOT NULL
S_name	VARCHAR2 (20)	REFERENCE
S_value	VARCHAR2 (500)	NOT NULL
units	VARCHAR2 (10)	NOT NULL

Table Name : query

Field Name                                           Data Type                            Constraints

T_no	VARCHAR2 (20)	REFERENCE
Prod_name	VARCHAR2 (500)	NOT NULL
query	VARCHAR2 (2000)	NOT NULL
Answer	VARCHAR2 (20)	REFERENCE

Table Name  :  bids

                                                      

Field Name                                         Data Type                               Constraints

T_no	NUMBER(3)	COMPOSITE PRIMARY KEY
Prod_name	VARCHAR2 (20)
un	VARCHAR2 (500)	NOT NULL
Quoted_value	VARCHAR2 (50)	NOT NULL
detail	VARCHAR2 (50)	NOT NULL

INPUT/OUTPUT DESIGN - ONLINE TENDER MANAGEMENT SYSTEM PROJECT

                     

 Input design: considering the requirements, procedures to collect the necessary input data in most efficiently designed. The input design has been done keeping in view that, the interaction of the user with the system being the most effective and simplified way.Also the measures are taken for the following

• Controlling the amount of input
• Avoid unauthorized access to the classroom.
• Eliminating extra steps
• Keeping the process simple
• At this stage the input forms and screens are designed.

Output design: All the screens of the system are designed with a view to provide the user with easy operations in simpler and efficient way, minimum key strokes possible. Instructions and important information is emphasized on the screen. Almost every screen is provided with no error and important messages and option selection facilitates. Emphasis is given for speedy processing and speedy transaction between the screens. Each screen assigned to make it as much user friendly as possible by using interactive procedures. So to say user can operate the system without much help from the operating manual.

  JAVA Script

                                                                                                                                                                                                                      Java script originally supported by Netscape navigator is the most popular web scripting language today. Java script lets you embedded programs right in your web pages and run these programs using the web browser.  You place these programs in a Ø  Writeln:  

                      Document.writeln() is a method, which is used to write some text to the current web page.

Ø  onClick:

    Occurs  when an element is clicked.

Ø  onLoad:

      Occurs when the page loads.

Ø  onMouseDown:

    Occurs  when a mouse button goes down.

Ø  onMouseMove:

    Occurs when the mouse is moved.

Ø  onUnload:

 Occurs  when a page is unloaded.

ORACLE DATABASE - ONLINE TENDER MANAGEMENT SYSTEM PROJECT

          Oracle is a relational database management system, which organizes data in the form of tables. Oracle is one of many database servers based on RDBMS model, which manages a seer of data that attends three specific things-data structures, data integrity and data manipulation. With oracle cooperative server technology we can realize the benefits of open, relational systems for all the applications. Oracle makes efficient use of all systems resources, on all hardware architecture; to deliver unmatched performance, price performance and scalability. Any DBMS to be called as RDBMS has to satisfy Dr.E.F.Codd’s rules.

DISTINCT FEATURES OF ORACLE:-

• ORACLE IS PORTABLE:

                 The Oracle RDBMS is available on wide range of platforms ranging from PCs to super computers and as a multi user loadable module for Novel NetWare, if you develop application on system you can run the same application on other systems without any modifications.

• ORACLE IS COMPATIBLE:

               Oracle commands can be used for communicating with IBM DB2 mainframe RDBMS that is different from Oracle, that is Oracle compatible with DB2. Oracle RDBMS is a high performance fault tolerant DBMS, which is specially designed for online transaction processing and for handling large database applications.

• MULTITHREADED SERVER ARCHITECTURE:

Oracle adaptable multithreaded server architecture delivers scalable high performance for very large number of users on all hardware architecture including symmetric multiprocessors (sumps) and loosely coupled multiprocessors. Performance is achieved by eliminating CPU, I/O, memory and operating system bottlenecks and by optimizing the Oracle DBMS server code to eliminate all internal bottlenecks.

FEATURES OF ORACLE:-

Most popular RDBMS in the market because of its ease of use

• Client/server architecture.
• Data independence.
• Ensuring data integrity and data security.
• Managing data concurrency.
• Parallel processing support for speed up data entry and online transaction processing used for applications.

DB procedures, functions and packages.

Testing; - ONLINE TENDER MANAGEMENT SYSTEM PROJECT

           Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and code generation.

TESTING OBJECTIVES: ONLINE TENDER MANAGEMENT SYSTEM PROJECT

• To ensure that during operation the system will perform as per specification.
• TO make sure that system meets the user requirements during operation
• To make sure that during the operation, incorrect input, processing and output will be detected
• To see that when correct inputs are fed to the system the outputs are correct
• To verify that the controls incorporated in the same system as intended
• Testing is a process of executing a program with the intent of finding an error
• A good test case is one that has a high probability of finding an as yet undiscovered error

                    

                       The software developed has been tested successfully using the following testing strategies and any errors that are encountered are corrected and again the part of the program or the procedure or function is put to testing until all the errors are removed. A successful test is one that uncovers an as yet undiscovered error. Note that the result of the system testing will prove that the system is working correctly. It will give confidence to system designer, users of the system, prevent frustration during implementation process etc.,

TEST CASE DESIGN:

White box testing

         White box testing is a testing case design method that uses the control structure of the procedure design to derive test cases. All independents path in a module are exercised at least once, all logical decisions are exercised at once, execute all loops at boundaries and within their operational bounds exercise internal data structure to ensure their validity. Here the customer is given three chances to enter a valid choice out of the given menu. After which the control exits the current menu.

Black Box Testing - ONLINE TENDER MANAGEMENT SYSTEM PROJECT

           Black Box Testing attempts to find errors in following areas or categories, incorrect or missing functions, interface error, errors in data structures, performance error and initialization and termination error. Here all the input data must match the data type to become a valid entry.

The following are the different tests at various levels:

Unit Testing:

                Unit testing is essentially for the verification of the code produced during the coding phase and the goal is test the internal logic of the module/program. In the Generic code project, the unit testing is done during coding phase of data entry forms whether the functions are working properly or not. In this phase all the drivers are tested they are rightly connected or not.

Integration Testing:

                All the tested modules are combined into sub systems, which are then tested. The goal is to see if the modules are properly integrated, and the emphasis being on the testing interfaces between the modules. In the generic code integration testing is done mainly on table creation module and insertion module.

Validation Testing

            This testing concentrates on confirming that the software is error-free in all respects. All the specified validations are verified and the software is subjected to hard-core testing. It also aims at determining the degree of deviation that exists in the software designed from the specification; they are listed out and are corrected.

System Testing - ONLINE TENDER MANAGEMENT SYSTEM PROJECT

              This testing is a series of different tests whose primary is to fully exercise the computer-based system. This involves:

• Implementing the system in a simulated production environment and testing it.
• Introducing errors and testing for error handling.

TEST CASES

TEST CASE 1:

   Test case for Login form:

                         When a user tries to login by submitting an incorrect ID or an incorrect Password   then it displays an error   message “NOT A VALID USER NAME”.

Test case 1: Verifying Authentication.	Priority (H, L): High
Test Objective: For Verifying Authentication.
Test Description: “User (admin/supplier) enters username and password and presses submit button”,  client program contacts with server, server contacts with the database, database checks for authentication and sends result as a valid user.
Requirements Verified: Yes
Test Environment:  Apache tomcat server must be in running state, Database Should contain appropriate table and link must be established between server and client program.
Test Setup/Pre-Conditions: Apache server should be in running state. Username and Password fields should be entered.
Actions	Expected Results
The user will select Login button to access application.	“Service Found”, “.Displays Homepage of Corresponding user.
Pass: Yes                                 Conditions pass: Yes                                Fail: No
Problems / Issues: NIL
Notes: Successfully Executed

  TEST CASE   2:

 Test case for User Registration form:

                           When a user enters user id to register and ID already exists, then this result in displaying error message “USER ID ALREADY EXISTS”.

Requirements Verified: Yes
Test Environment:  Apache tomcat server must be in running state, Database Should contain appropriate table and link must be established between server and client program.
Test Setup/Pre-Conditions: Apache server should be in running state. Values should be entered in all the  fields should be entered.
Actions	Expected Results
The supplier enters all the details and clicks submit button to access application.	“Service Found”, “.Displays supplier registration successful.
Pass: Yes                                 Conditions pass: Yes                                Fail: No
Problems / Issues: NIL
Notes: Successfully Executed

TEST CASE 3:

 Test case for Change Password:When the old password does not match with the new password,then this results in displaying an error message as “ OLD PASSWORD DOES NOT MATCH WITH THE NEW PASSWORD”.

Test case for Forget Password: When a user forgets his password he is asked  to enter Login name, ZIP code, Mobile number. If these are matched with the already stored ones then user will get his Original password.

TEST CASE 4:       

Test case for modification:    When the buyer  want to modify the tender correctly   we get a message “MODIFIED THE TENDER”.

TEST CASE 5:           

Validation cases :

If any data field which accept the data from the user are not filled then the corresponding error messages are generated.

CONCLUSION - ONLINE TENDER MANAGEMENT SYSTEM PROJECT

The E-Tendering project has been successfully completed. The goal of the system is achieved and the problems are solved. This project is developed in a manner that is user friendly and required help is provided at different levels.

The primary objective is to provide the interactive service to all the users. Different types of services are provided to both the supplier and buyer. This system certainly provides a better interface which can be helpful for both the supplier and buyer to make their working smooth.

LIMITATIONS

The present system is developed takes into account that the tenders posted are genuine in validation is done with respect to this.The system also does not verify the buyer’s identification.As the memory capacity is limited to server’s memory we can’t accommodate infinite number of users.

FUTURE ENHANCEMENTS - ONLINE TENDER MANAGEMENT SYSTEM PROJECT

In future the buyer’s identity can be verified. In future the suppliers past supply details can be stored which the buyers can view to decide whether to give them the tender or not.

-->