Cyber bidding gateway report on ASP .net

ABSTRACT
Auctions are among the least economic institutions in place. They have been used
since antiquity to sell a wide variety of goods, and their basic from has remained unchanged.
In this dissertation, we explore the efficiency of common auctions when values are
interdependent the values to particular bidder may depend on information available only to
others and a symmetric. In this setting, it is well known that sealed bid auctions do not
achieve efficient in allocations general since they do not allow the information held by
different bidders to be shared.
Typically in an auction, say of the kind used to sell art, the auctioneer sets a
relatively low initial price. This price is then increased until only one bidder is willing to buy
the object, and the exact manner in which this is done varies. In my model a bidder who
drops out at some price can “reenter” at a higher price.
Administration
This module handles the overall administration of the system.
Sellers
The seller’s module consisting of the product publishing and placing of the initial bid.
The sellers can watch the progress of their product’s bid.
Buyers
The buyer’s module handle the customers who want to participate on the bid. They can
view the product and can place bids for the products. When becoming a winner, they
can purchase the product using online banking.
Bidding
This module handles the bid placing by the buyers. The customers are allowed to place
the bid only within the duration of the bid.
Online banking and payment
This module demonstrates the online banking for payment, for the bid winners. This
include a number of WCF services that ensure security.

CYBER BIDDING GATEWAY DEPARTMENT OF COMPUTER SCIENCE
COLLEGE 2 | P a g e
CONTENTS
1. INTRODUCTION
1.1 PROJECT PROFILE
1.2 MODULES
1.3 OBJECTIVE OF THE PROJECT
1.4 LANGUAGES USED
2. SOFTWARE DESCRIPTION
2.1 INTRODUCTION TO JAVA
2.2 THE JAVA HISTORY TIMELINE
2.3 SPECIAL FEATURES OF JAVA
3. SYSTEM ANALYSIS
3.1 INTRODUCTION
3.2 EXISTING SYSTEM
3.3 LIMITATIONS OF EXISTING SYSTEM
3.4 PROPOSEDSYSTEM
3.5 FACT FINDING TECHNIQUES
3.6 FEASIBILITY STUDY
3.6.1 TECHNIICAL FEASIBILITY
3.6.2 ECONOMICAL FEASIBILITY
3.6.3 OPERATIONAL FEASIBILITY
4. SYSTEM SPECIFICATION
4.1 SOFTWARESPECIFICATION
4.2 HARDWARE SPECIFICATION
5. SYSTEM DESIGN

COLLEGE 3 | P a g e
5.1 INTRODUCTION TO SYSTEM DESIGN
5.2 INPUT DESIGN
5.3 OUTPUT DESIGN
5.4 DATABASE DESIGN
5.5 FORM DESIGN
5.6 ARCHITECTURAL DESIGN
5.7 SYSTEM MODULES
6. DATA FLOW DIAGRAM (DFD)
6.1 INTRODUCTION TO DATA FLOW DIAGRAM
7. TABLE STRUCTURE
7.1 INTRODUCTION TO TABLE STRUCTURE
8. SYSTEM TESTING
8.1 INTRODUCTION TO SYSTEM TESTING
8.2 UNIT TESTING
8.3 INTEGRATION TESTING
8.4 VALIDATION TESTING
9. SYSTEM IMPLEMENTAION
9.1 INTRODUCTION TO SYSTEM IMPLEMENTATION
10. CONCLUSION
11. APPENDIXES
11.1 APPENDIX A
11.2 APPENDIX B
11.3 APPENDIX C
12. BIBILOGRAPHY

COLLEGE 4 | P a g e
INTRODUCTION

COLLEGE 5 | P a g e
1.1 PROJECT PROFILE
The project “CYBER BIDDING GATEWAY” is a well prepared project in ASP.NET
with C# and SQL 2008 plat form. This software whose objective is to show the various
details and other allotment made for a good management.
This project aims at managing the bidding. The existing system is a manual system.
So it is difficult to manage. So the administrator wants to computerized one, so all the process
in auction is very easy.
This project is user friendly software. This computerization leads to several
advantages. They are fast, time saving, accurate, easy etc. This data based project has
database table which consist of various fields.
This system has administrative and user property, this provides security features to the
system, and it can prevent unauthorized access of software. All this features are
implementing in my software in very flexible manner.
1.2 MODULES
The software includes 5 modules,
1. Administration
2. Seller
3. Buyer
4. Bidding
5. Online banking and payment
1.3 OBJECTIVE OF THE PROJECT
1. The Cyber Bidding Gateway provides a platform to sell products and buy products
using bidding.
2. Cyber Bidding Gateway consists of a data base which stores entire details.
3. Replaces lack of security.
4. Save time.

COLLEGE 6 | P a g e
5. To overcome the limitations of existing system.
1.4 LANGUAGES USED
 Front End : Microsoft ASP.NET
 Back End : SQL Server 2008

COLLEGE 7 | P a g e
SOFTWARE DISCRIPTION

COLLEGE 8 | P a g e
2.1 INTRODUCTION TO ASP.NET
The Microsoft .NET Framework is a software framework that can be installed on
computers running Microsoft Windows operating systems. It includes a large library of coded
solutions to common programming problems and a virtual machine that manages the
execution of programs written specifically for the framework. The .NET Framework is a
Microsoft offering and is intended to be used by most new applications created for the
Windows platform.
ASP. Net, the next version of ASP, is a programming framework used to create
enterprise-class Web Applications. These applications are accessible on a global basis leading
to efficient information management. The advantage ASP. Net offers are more than just the
next version of ASP.
The .NET Framework was introduced with a vision to create globally distributed
software with Internet functionality and interoperability. The .NET Framework consists of
many class libraries, includes multiple language support and a common execution platform.
It’s a very flexible foundation on which many different types of top class applications can be
developed that do different things. Developing Internet applications with the .NET Framework
is very easy. ASP.NET is to build into this framework, we can create ASP.NET applications
using any of the built-in languages.
2.2 HISTORY
After four years of development, and a series of beta releases in 2000 and 2001,
ASP.NET 1.0 was released on January 5, 2002 as part of version 1.0 of the .NET Framework.
Even prior to the release, dozens of books had been written about ASP.NET [4] and
Microsoft promoted it heavily as part of its platform for Web services. Scott Guthrie became
the product unit manager for ASP.NET, and development continued apace, with version 1.1
being released on April 24, 2003 as a part of Windows Server 2003. ASP.NET is loosely
based on HTML. This release focused on improving ASP.NET's support for mobile devices.
2.3 SPECIAL FEATURES OF ASP.NET
1. ASP.NET makes development simpler and easier to maintain with an event-driven,
server-side programming model.

COLLEGE 9 | P a g e
2. ASP.NET pages are easy to write and maintain because the source code and HTML
are together.
3. The source code is executed on the server. The pages have lots of power and
flexibility by this approach.
4. The source code is compiled the first time the page is requested. Execution is fast
as the Web Server compiles the page the first time it is requested. The server saves the
compiled version of the page for use next time the page is requested.
5. The HTML produced by the ASP.NET page is sent back to the browser. The
application source code you write is not sent and is not easily stolen.
6. ASP.NET makes for easy deployment. There is no need to register components
because the configuration information is built-in.
7. The Web server continuously monitors the pages, components and applications
running on it. If it notifies memory leaks, infinite loops, other illegal software or
activities and restarts itself.
8. ASP.NET validates information (validation controls) entered by the user without
writing a single line of code.
9. ASP.NET easily works with ADO .NET using data-binding and page formatting
features.
10. ASP.NET applications run faster and counter large volumes of users without
performance problems.

COLLEGE 10 | P a g e
SYSTEM ANALYSIS

3.1 INTRODUCTION
System analysis is concerned with investigating, analyzing and evaluating the
information system under considerations. It is detailed study of the various operations
performed by a system and their relationships within and outside the system. It is the process
of gathering and interpreting facts, diagnosing problems and using the information to
recommended improvements on the system
System analysis involves:
 System planning and initial investigations
 Information gathering
 Feasibility study
 Cost/Benefit analysis
3.2 EXISTING SYSTEM
Present system is manual. The project metrics has to enter all the details of project,
documents, and tasks. It also maintenance the team information and also efforts estimation.
For this purpose the organization maintain the size of the document, sources code and update
the information about team member’s details manually. Which is much of time consuming
process and more importantly it is error prone.
3.3 LIMITATIONS OF EXISTING SYSTEM
The main disadvantages of existing systems are:
 Lack of security
 Using Out Dated technology
 Not user friendly
 Lack of information
 More timing, not efficient and less storing capacity
 Automatic fine calculation is not available

 Error correction is difficult
 Searching for particular data is very difficult
3.4 PROPOSED SYSTEM
The primary objective of the proposed system design is to overcome the drawbacks of
the existing system and reduce the manual work. We can achieve this objective by
computerizing the whole activities that are carried out manually. Computerization will reduce
manual work and produce desired information efficiently and quickly.
The “Cyber Bidding Gateway” has been design to reduce the manual work in the
following manner.
 Data entry screens are designed such that they are very user friendly and
minimum typing is required from the user.
 Novice user can also use the system without any training.
 System provides various information through reports quickly and accurately in
easily understandable formats.
 The new system is more user friendly due to GUI feature of ASP.NET
 The system supports security at operational level i.e. it gives access to view and
manipulate the information based on the user login.
 It aimed to be a paperless software. There is no unnecessary printing of particular
documents.
 Faster access information.
 Taking into the speed of computer access large data in less time and facilities
provided by access.
 Duplication of data will be avoided.
 Menu driven interface provides ease of use.

3.5 FACT FINDING TECHNIQUES
The specific method analysts use for collecting data about requirements are called
Fact finding. It encompasses all of that are go into the investigation, scoping and definition of
a new or altered system. The first activity in analysis phase is to do the preliminary
investigation. During preliminary investigation data collecting is a very important and for this
we can use the fact finding technique. The following fact finding techniques can be used for
collecting data.
 Data collection
 Correspondence & questionnaires
 Personal interviews
 Observation
 Research
Data Collection
In this fact-finding step, the analyst gathers and organizes all documentation related to
data carriers are forms, records, reports, manuals, procedures, and CRT display layouts. The
analyst cautious in relying upon the validity of collected documents.
Correspondence& Questionnaires
Correspondence enables the analyst to explain the purpose of investigation activities
and to inform people of what is expected from them. It is particularly important that
interviews be preceded by correspondence defining the subject area and the specific topics to
be reviewed. The questionnaire is an important and often effective type of correspondence.
Personal Interview
The personal interview is one of the most fruitful methods of obtaining information.
An interview is a person to person communication. The analyst is more of a receiver than a
sender when conducting an interview.
Observation
This is a skill which the analyst have to develop. The analyst have to identify the right
information and choose the right person and look at the right place to achieve his objective.

He should have a clear vision of how each departments work and work flow between them
and for this he should be a good observer. Observation allows analyst to gain information
they cannot obtain by any fact finding method.
3.6 FEASIBILITY STUDY
One of the important outcomes of the preliminary investigation is the determination of
the feasibility of the system. These are different aspects of the feasibility study in the
investigation phase. After the documents reviewing the selected personnel, investigating the
various resources the following are the results for the three feasibility.
Three key combinations are involved in the feasibility study
 Economic feasibility
 Technical feasibility
 Operational feasibility
3.6.1 Economic Feasibility
Economic analysis is the most frequently used method for evaluating the
effectiveness of a candidate system. More commonly known as cost/benefit analysis,
the procedure is to determine the benefit and saving that are expected from a
candidate system and compare them with the term of time by automating the process
of report generation.
The system can be developed technically and if installed would still be good for the
organization. The cost is found to be lesser compared to the benefits of the proposed system.
The workload of a user will decrease to half of the current workload. Hence the proposed
system is found to be economic feasible.
3.6.2 Technical Feasibility
Technical study is a study of hardware and software requirements. All the technical
issue related to the proposed system is dealt during feasibility stage of preliminary
investigation produced. Technical feasibility analysis makes a comparison between the levels
of technology available that is needed for the development of the project. The levels of

technology consist of factors like software tools, machine environment, platform developed
and so on.
The consideration that is normally associated with technical feasibility includes resources
availability of the organization, where the project is to be developed and implemented. By
taking these factors into consideration before developing, the resources available are
adequate. Thus the project is considered technically feasible for development.
3.6.3 Operational Feasibility
The developed system is completely driven and user friendly. Also the system is
developed in ASP.NET. There is little need skill for new user to operate the software. Reports
will be exactly as per the requirement. The maintenance and modification of the new system
needs very less human effort. Using command buttons throughout the application programs
enhances the operational feasibility. The new system is operationally feasible and makes the
operations simpler and quite easier.
At the beginning of preliminary investigation work all the personnel approached
responded positively this reduces the chance of resistance to the proposed system.
Considering all the issue stated above makes the proposed system operationally feasible.

SYSTEM SPECIFICATION

4.1 SOFTWARE SPECIFICATION
Operating System : Windows 7
Front End : ASP.NET 2012
Back End : Microsoft SQL Server 2008
Server Side Scripting : C#.NET
Browser : Any Browser with JavaScript & XML Support
4.2 HARDWARE SPECIFICATION
Processor : Intel Pentium IV
Processor Speed : 1GHz
Monitor : Compactable Monitor
RAM : 2 GB
Hard Disk : 40 GB (Including DB Requirements)
Keyboard : Multimedia Keyboard
Mouse : Optical Mouse

SYSTEM DESIGN

5.1 INTRODUCTION TO SYSTEM DESIGN
System designs main aim is to identify the modules that should be in the
system, and the specifications of these modules and how they interact with each other
to produce the desired results. At the end of the system design all the major data
structures, file formats and the major modules in the system and their specification are
decided.
Activities in the design phase are described briefly as follows:
Allocation of function: The data flow diagrams prepared during the study phase and
reviewed and expanded in order to allocate function between manual tasks, equipment
functions and computer program function.
Manual task definition: Requirements resulting from human interfaces with the computer-
based component of the system are described.
Reference manual identification: Reference manuals required by user personnel
programmers, and equipment operations are identified.
Equipment function definition: The functions to be performed by hardware (rather than by
computer programs or manual operations) are defined.
Equipment specification: The hardware configuration used to convert input data to
meaningful output information is described.
Computer program function definition: The specific functions of the computer program
component of the overall system are defined, and design requirements for external system
inputs are established.
Database design: The storage requirements of all the data elements on which the computer
programs operate are calculated, taking into account the size and volume of the records to be
stored and the methods of file organization and access.
5.2 INPUT DESIGN
The input is the set of values that is provided by the user to the system. The input
design must enable the user to provide the error free input to the system for efficient

processing. The input data have to be validated, edited, organized, and accepted by the
system before being proposed to produce the outputs.
The main objectives of input design are as follows:
 Produce effective method of input
 Achieve high level accuracy
 Ensure that the input is acceptable and understood by the user
The different types of input data handled by the system are:
External
They are the primary inputs to the system. The external input is what the user supplies
to the system. The user can give different types of external inputs in this project such as add
new thread, post reply etc.
Internal
When the external inputs are obtained from the user, these inputs are transferred to the
system as message. These message are captured and handled as input for further processing.
The necessary external inputs are given to the system by Graphical User Interface
(GUI) technology. The GUI system applied to this project enables the user to avoid error and
confusion arises while entering the input.
5.3 OUTPUT DESIGN
Outputs are the most important direct source of information to the user and to the
management. Efficient and eligible output design should improve the system’s relationship
with the user and help in decision making,
Output design generally deals with the results generated by the system i.e., reports.
These reports can be generated from stored or calculated values. Reports are displayed either
as screen window preview or printed form. Most end users will not actually operate the

information system or enter data through workstation, but they will use the output from the
system.
Outputs from computer systems are required primarily to communicate the results of
processing to the user. They are also used to provide a permanent copy of these results for
later consultation.
While designing output, the system analyst must accomplish the following:
 Determine what information to present
 Decide where to display
 Give each output a specific name or title
 Select the output medium
 Give facility to print the information if necessary
5.4 DATABASE DESIGN
Relationships between data elements, functions to be performed, and techniques for
file organization are studied in detail so the most appropriate storage device can be selected
and an efficient data base design can be achieved.
The storage requirements for all data elements on which the computer programs
operate are calculated, taking into account the size and volume of the records to be stored and
the methods of file organization and access. The interfaces between the system data base and
other data bases are identified by specifying the data that must flow between them.
Databases are designed to manage large bodies of information. One of the major
purpose of a data base system is to provide users with an abstract view of data. A database is
designed so that it can be used both to specify the overall logical structure of the database and
provide a higher level description of the implementation

5.5 FORM DESIGN
People read from forms, write on forms, and spend billions of hours handling forms
and filling forms. The data that forms carry comes from people, and the information output of
the system goes to people. So the form is a tool with a message, it is a physical carrier of the
data of information. It is also can constitute authority for action. Each form is a request for
action. It provides information for making decisions and improving operations.
Requirements of Form Design
Form design allows analyzing forms, evaluating present documents, and creating new
or improved forms. Bear in mind that detailed analysis occurs only after the problem
definition stage and the beginning of candidate system. Since the purpose of a form is to
communicate effectively through form design, there are several requirements:
 Reduced development time
 Increased reuse of code
 Enhanced user experience
Principles behind good form design
Layout should be simple and clear. Try to split your form into section with
appropriate subheadings. This will help the user understand what is being requested. It will
also encourage you to place data entries in a logical sequence, which is often what a user
expects. Prototypes are very helpful during the design process.
Details about Form Elements
There are a number of points to consider regarding form elements, as follow
 Limit the number of items in your select lists.
 Put the most often-selected entries at top of the selected list.
 When possible, use the size attribute with select lists.

 Don’t present long vertical lists of checkboxes or radio buttons.
 Avoid using Reset buttons except in applications that support continuous data
entry.
5.6 ARCHITECTURAL DESIGN
Architecture is an overall structure of a system. Architecture takes into consideration
the overall working of the system. Larger system can be decomposed into subsystems that
provide some related set of services. The initial design process of identifying these sub
systems and establishing a framework for subsystem control and communication is called
architecture design. Architecture design usually comes before detailed system specification.
Architecture decomposition is necessary to structure and organize the specification. There is
no generally accepted process depends on application knowledge and on the skill and
intuition of the system architect.
Assessment Collection System follows 2-tier architecture. In the client side, user select
forms and submits pages (first tier). Then it passes to the main server where the data and the
business process are stored (second tier). Then, server responds with appropriate information
as pages or text.
Architectural design is the back born for building successful software intensive
system. A good software structure design results in the development of a project working
system. For the development of the software, modules were identified. This software was
developed into separate named and addressable components that are integrated to satisfy the
problem requirements
5.7 SYSTEM MODULES
Registration
Add category
Approve Registration
Approve item
Add an item
View bid item
View winner
My uploads
View profile

DATA FLOW DIAGRAM

6.1 INTRODUCTION TO DATA FLOW DIAGRAM
Data flow diagram is a network that describes the flow of data throughout the system.
Data stores and the process that changed or transform data flows. The data flow diagram
network is logical abstract of a system that may have mainly possible physical configuration.
Data flow diagrams are constructed from four basic symbols. Using these symbols a
system analyst can construct a logic network that traces data streams throughout a system.
A level zero DFD is also called a fundamental system or context model, represents the entire
software element of a single bubble with input and output data indicated by incoming and
outgoing arrows. These are expanded level by level each explaining its process in detail.
Process are numbered for easy identification and are normally labeled in block letters. Each
data flow is labeled for easy understanding. The various symbols used are
Source or destination of data
Data flow
Process that transforms data flow
Data store
Te
ac
he
rs
Gr
adi
ng

TABLE STRUCTURE

7.1 INTRODUCTION TO TABLE STRUCTURE
Table is a collection of complete details about a particular subject. These data
are saved in rows and columns. The data of each row are different units. Hence, rows are
called RECORDS and Columns of each row are called FIELDS. Table design means how
data should be organized around user requirements. How data are organized depends on the
data and response requirements that determine hardware configurations. An integrated
approach to file design is the database. The general theme around in the database is to handle
information as an integrated whole.
Data is stored in tables, which is available in the back end. The items and data, which
are entered in the input, form id directly stored in this table using linking of database. We link
more than one table to input forms. We can collect the details from the different tables to
display on the output screen.

SYSTEM TESTING

8.1 INTRODUCTION TO SYSTEM TESTING
Software testing is a critical element of software quality assurance and represents the
ultimate reviews of specification, design and coding. Testing present an interesting anomaly
for the software. Testing is vital to the success of the system. Errors can be injected at any
stage during development. System testing makes a logical assumption that if all the parts of
the system are correct, the goal will be successfully achieved.
During testing, the program to be tested is executed with set of test data and the
output of the program for the test data is evaluated to determine if the program is performing
as expected. A series of testing are performed for the proposed system before the system is
ready for user acceptance testing.
8.2 UNIT TESTING
Unit testing focuses verification effort on the smallest unit of the software design, the
module this is known as module testing. Since the proposed system has modules the testing is
individually performed on each module.
Using the details description as a guide, important control paths are tested to uncover
errors within the boundary of the modules. This testing was carried out during programming
stage itself. In this testing step each module is found to be working satisfactorily as regards to
the expected output from the module .
Module interface is tested to ensure that the information properly flow and out of the program
under test.
 Data consistency is tested to ensure that the data stored maintains its integrity
during all steps in algorithm execution.
 All independent paths are examined to ensure that all the statement in the module
have been executed at least once.
8.3 INTEGRATION TESTING
Data can be test across an interface; one module can have adverse effect on another,
sub function when combined may not produce the desired function. Integration testing is a

systematic technique for constructing the program structure while at the same time
conducting test to uncover errors associated within the interface.
The objective is to take unit tested modules and built a program structure that has
been dictated by design. All modules are combined in this testing step. The entire program is
tested as a whole. Correction is difficult at this stage because the isolation of causes is
complicated by the vast expense of the program. Thus in the integration testing step all the
errors uncover are corrected for the next testing step.
8.4 VALIDATION TESTING
At the culmination of integration testing, software is completely assembled as a
package. Interfacing errors have been uncovered and corrected and a final series of software
test-validation testing begins. Validation testing can be defined in many ways, but a simple
definition is that validation succeeds when the software functions in manner that is
reasonably expected by the user. Software validation is achieved through a series of tests that
demonstrate conformity with requirement. After validation test has been conducted, one of
two conditions exists.
 The function or performance characteristics confirm to specifications and are
accepted.
 A validation from specification is uncovered and a deficiency created.
Deviation or error discovered at this step in this project is corrected prior to
completion of the project with the help of the user. Thus the proposed system under
consideration has been tested by using validation testing and found to be working
satisfactorily.

SYSTEM IMPLEMENTATION

9.1 INTRODUCTION TO SYSTEM IMPLEMENTATION
Implementation is the stage in the project where the theoretical design is turned into a
working system and is giving confidence on the new system for the users that it will work
efficiently and effectively. It involves careful planning, investigation of the current system
and its constraints on implementation, design of methods to achieve the changeover, an
evaluation, of change over methods.
Implementation is the final and important phase. The most critical stage in achieving a
successful new system and in giving the users confidence that the new system will work and
be effective. The system can be implemented only after thorough testing is done and if it
found to working according to the specification. This method also offers the greatest security
since the old system can take over if the errors are found or inability to handle certain type of
transactions while using the new system.
At the beginning of the development phase a preliminary implementation plan is
created to schedule and manage the many different activities must be integrated into plan.
The implementation plan is updated throughout the development phase, culminating in a
changeover plan for the operation phase. The major elements of implementation plan are
test plan, training plan, equipment installation plan and a conversion plan.
There are three types of implementation:
 Implementation of a computer system to replace a manual system.
 Implementation of a new computer system to replace an existing one.
Implementation of a modified application to replace an existing one, using the same
computer. Implementation includes all those activities that place to convert from the old
system to the new one. The new system may be totally new, replacing an external system
manual or automated system or it may be a modification to an external system. The process
of putting the developed system in actual use is called system implementation. This includes
all those activities that take place to convert to old system to new one.
The most crucial stage is achieving a new successful system and giving confidence in
new system that it will work efficiently and effectively. The system is implemented only after
through checking is done and if it is found working according to the specifications.

It involves careful planning, investigation of the current system and constrains on
implementation, design of methods to achieve. Two checking is done and if it is found
working according to the specification, major task of preparing the implementation are
educating, training the users. The more complex the system being implemented, the more
involved will be the system analysis and the design effort required just for implementation.
The method of implementation and the time scale adopted are found out initially. Next the
system is rested properly and the same time user are trained in the new product.
Issues to consider in the Evaluation of Information System
1. How have information systems changed the cost of operation?
2. How have information systems changed the way in which operations are
performed?
3. How have information systems changed the accuracy of information that users
receive?
4. How have information systems changed the timeliness of information and reports
users receive?
5. How has information systems brought about organization changes? Are these
changes for the better or for the worse?
6. How have information systems changed the completeness of the information?
7. How have information systems changed control or centralization? What is the
effect of such changes?
8. How have information systems changed the attitude of systems users or persons
affected by the system?
9. How have information systems changed the number of users?
10. How have information systems changed the interactions between members of the
organization?
11. How have information systems changed productivity?
12. How have information systems changed the efforts that must be expended to
receive information for decision making?
System Maintenance
The maintenance phase of the software cycle is the time in which a software product
performs the useful work. After a system is successfully implemented, it should be

maintained in a proper manner. System maintenance is an important aspect in software
development cycle.
The system should be maintained and upgraded according to the technological
advancements. It ensures the data control and security. The system must be protected from
fire and other natural calamities. The backup copies of data must be maintained daily so that
to prevent the loss of data due to various reasons.
Software maintenance is of course far more than finding mistakes we may define
maintenance by describing four activities that are undertaken to after a program is released
for use
Software maintenance activities can be classified in to
 Corrective maintenance
 Adaptive maintenance
 Perfective maintenance
 Preventive maintenance

CONCLUSION

10. CONCLUSION
The project entitled ‘Cyber Bidding Gateway’ is done to make manual process
easier by making it a computerized system for user registration and bidding. Cyber
bidding gateway is an integrated web application that handle the online
bidding.
The project was successfully completed within the time span allotted. The drawbacks
of the existing system as listed before are fully evacuated. All the existing inconsistencies are
fully solved as this system is implemented. This reduced the burden of the administration of
the system. All the modules are tested separately and put together to form the main system.
Finally the system is tested with real data and it worked successfully. Thus the system has
fulfilled the entire objective defined.
The system has been developed in an interactive manner; the reports generated by the
system are clear. The system is flexible, user friendly and has its own full data security and
all data recovery facility. The developed system has mainly for modules administrator, seller,
buyer, and bidding. It is developed using ASP.Net and Microsoft SQL Server.

APPENDIXES

11.1 APPENDIXA: TABLES
Table 1: tbl_login
Foreign Key: username
Field Name Data Type Description
username Varchar(50) To specify the username
password Varchar(50) To identify the user
role Varchar(50) To identify the role
Table 2: tbl_registration
Primary Key: username
firstname Varchar(50) To specify the first name
lastname Varchar(50) To specify the last name
house_name Varchar(50) To specify the address
location Varchar(50) To specify the location
Street Varchar(50) To specify the street
city Varchar(50) To specify city
pincode Int To specify the pin
district Varchar(50) To specify the district
state Varchar(50) To specify the state
Email_id Varchar(50) To specify the mail
mobile Bigint To specify the number
User_Name Varchar(50) To specify the username
status Bit Approve or not
Password Varchar(50) To identify the user

Table 3: tbl_categorys
Primary Key: categorys_id
Table 4: tbl_item
Primary Key: item_id
Category_id Int To specify the category id
Category_name Varchar(50) To specify the category
Item_id Int To specify the itemid
username Varchar(50) To specify the username
Category_id Int To specify the categoryid
Item_name Varchar(50) To specify the item name
Description Varchar(50) To specify the description
Min_rate Float To specify rate
Increment_value Int To specify the rate increment
Start_date Date To specify the bid start date
End_date Date To specify bid end date
status Bit To specify the status
bidstatus Int To specify the bidstatus

Table 5: tbl_image
Primary Key: image_id
Foreign key: item_id
Table 6: tbl_bid_details
Primary Key: bid_details_id
Bid_details_id Int To specify the biddetailsid
Username Varchar(50) To specify the username
Mobile Varchar(50) To specify the mobile
Email Varchar(50) To specify the email
bidrate Float To specify bidrate
Table 7: tbl_userbid
Primary Key: user_bid_id
Foreign key: item_id
Image_id Int To specify the imageid
Image_path Varchar(max) To specify the image path
User_bid_id Int To specify the bidid
Username Varchar(50) To specify the username
Rate Float To specify the rate
date Varchar(50) To specify the biddate

11.2 APPENDIXB: DFD
LEVEL 0

LEVEL 1
ADMI

USER
GUEST

LEVEL 2
ADMIN
USER

GUEST
11.1 APPENDIXB: SCREEN SHOTS

WELCOME PAGE
REGISTRATION

FORGET PASSWORD

LOGIN
USER-HOME PAGE

ADD ITEM

MY UPLOADS

CHANGE PASSWORD
UPDATE PROFILE

VIEW BID ITEMS

BUY BID ITEM

VIEW WINNER

PAYMENT
ADMIN-HOME PAGE

ADD CATEGORY
APPROVE REGISTRATION

APPROVE / UN APPROVE ITEM
APPROVE BID WINNER

LOGOUT

BIBLIOGRAPHY
12. BIBLIOGRAPHY

 Mastering visual c#.NET by Jason Price
 Professional visual studio 2010 by Bruce Johnson
 Sql server 2008 for Developers
 www.stackoverflow.com
 www.codeproject.com
 www.auction.indiatimes.com
 www.ubid.com
 www.msdn.com

Cyber bidding gateway report on ASP .net

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Similar to Cyber bidding gateway report on ASP .net

Similar to Cyber bidding gateway report on ASP .net (20)

More from Georgekutty Francis

More from Georgekutty Francis (12)

Recently uploaded

Recently uploaded (20)

Cyber bidding gateway report on ASP .net