Visual C++ Program for the Implementation of Automated Auction Maintenance System | IT1253 - Software Engineering Laboratory


ABSTRACT:
This project implements the auction process. It’s an application that which maintains all the details of the auctioneers who have auctioned the particular area during the auctioning process. Here the records of the auctioneers are maintained. The current system makes use of notebooks or ledgers to maintain the details. All the records are entered and accessed manually. While maintaining the details in ledgers it becomes very difficult to view the records.  Moreover it is very much essential to be aware of all records. Now in this application MS ACCESS & C are used to store & retrieve the records. Information recorded automatically updated into the database accordingly to the data needs. The objectives of the proposed system are to have a detailed review of the auctioneers at present. The input to the application is the details of the auctioneers based on the places auctioned. The output is the details that are collected from the application and are given out under specific conditions.

REQUIREMENTS ANALYSIS:
  It results in the specification of software’s operational characteristics, indicates software’s interface with other system elements and establishes constraints that software must meet. The aim of analysis is to understand the problem with a view to eliminate any deficiencies in the requirement specification such as incompleteness, Inconsistencies, etc. The model which
we are trying to build may be or may not be ready.

OVERALL OBJECTIVES AND PHILOSOPHY:

USER REQUIREMENT:

•    Details of the places that are to be auctioned
•    The current condition of that place
•    How many places are there to be auctioned
•    How many have been auctioned

DEVELOPER REQUIREMENT:
•    The details of the auctioned places
•    The details of the auctioneers
•    How many auctioneers are there
•    For what amount was the place auctioned
•    Software and hardware requirements as mentioned above.

SOFTWARE REQUIREMENT SYSTEM (SRS):
FUNCTIONAL REQUIREMENTS:
The functional requirements of a system mainly comprises of the following strategies:
•    Auctioning operation that is being performed.
•    Properties that has been auctioned.
•    Rate at which the property has been auctioned.
The software requirements of the application are:
•    FRONTEND: VC++
•    BACKEND: MSACCESS
•    DRIVER: ODBC
The hardware requirements of the application are:
•    INTEL PENTIUM 3
•    MINIMUM 128 RAM

Goal of implementation:
The primary goal of this application is to maintain a perfect record of the auctioneers who have auctioned the properties at different places. This is achieved by the above mentioned requirements.

DESIGN:
Software design deals with transforming the customer requirements, as described in the SRS document, into a form (a set of documents) that is suitable for implementation in a programming language. A good software design is seldom arrived by using a single step procedure but rather through several iterations through a series of steps. Design activities can be broadly classified into two important parts:

• Preliminary (or high-level) design and
      • Detailed design.

 The aim of design is to produce a model that will provide a seamless transition to the coding phase, i.e. once the requirements are analyzed and found to be satisfactory, a design model is created which can be easily implemented.

Characteristics of a good software design:
The characteristics are listed below:

• Correctness: our application has got a perfect design that which correctly implement all the functionalities identified in the SRS document.

• Understandability: our application is easily understandable.

• Efficiency: our application is highly efficient.

• Maintainability: It is easily amenable to change.

High level design of the application (auction):
 

Detailed design of the application (auction)::


AUCTIONEERS DETAILS:
 This module comprises of the detail of the auctioneers. The main attributes of this module are NAME, ADDRESS & the ID of the auctioneers. The ID of the auctioneer is acting as a primary key for identification.



PROPERTY DETAILS:
 This module gives out the details about the properties auctioned. The attributes of this particular module are LOCATION about where the land is located & also the PRICE nothing but the amount for which the land is being auctioned.


RECORD MAINTANANCE:
This module makes use of both the first and second module mentioned. It collects the details about the auctioneers and also the property, combines it and maintains the record in the database.

MODELING:
This activity encompasses the creation of models that allow the developer and the customer to better understand software requirements and the design that will achieve those requirements.

LEVEL 0 DATA FLOW DIAGRAM:



TESTING:
Testing a program consists of providing the program with a set of test inputs (or test cases) and observing if the program behaves as expected. If the program fails to behave as expected, then the conditions under which failure occurs are noted for later debugging and correction.

Unit testing:
Unit testing is undertaken after a module has been coded and successfully reviewed. Unit testing (or module testing) is the testing of different units (or modules) of a system in isolation.
In order to test a single module, a complete environment is needed to provide all that is necessary for execution of the module. That is, besides the module under test itself, the following steps are needed in order to be able to test the module:

• The procedures belonging to other modules that the module under test calls.

• Nonlocal data structures that the module accesses.

 • A procedure to call the functions of the module under test with appropriate parameters

System testing:
System tests are designed to validate a fully developed system to assure that it meets its requirements.

There are essentially three main kinds of system testing:

• Alpha Testing. Alpha testing refers to the system testing carried out by the test team within the developing organization.

• Beta testing. Beta testing is the system testing performed by a select group of friendly customers.

• Acceptance Testing. Acceptance testing is the system testing performed by the customer to determine whether he should accept the delivery of the system.

CONCLUSION:

         Thus our application- auctioning process is successfully automated with the mentioned software and hardware requirements. The records that are entered in are automatically updated in the database with the ODBC driver. The above mentioned testing techniques are also performed and our application is finally deployed to our customers. This automated system has the advantage of maintaining the records properly without any manual stress. Hence it becomes easier for the user to automate the property auctioned. The maintenance of our system wholly depends on the customer’s risk.
Previous
Next Post »

Still not found what you are looking for? Try again here.