PROJECT RAILWAY RESERVATION

ELECTION MANAGEMENT

A Project Report

Submitted for the partial fulfillment of the degree of

Master of Computer Applications

(5yrs Integrated Course)

IN

DIRECTORATE OF DISTANCE EDUCATION

GURU JAMBHESHWAR UNIVERSITY

SCIENCE AND TECHNOLOGY, HISAR

Under the Supervision of: Submitted By:

VIRENDRA KUMAR VISHAL MALHOTRA

Roll no. 06031241015

DIRECTORATE OF DISTANCE EDUCATION

GURU JAMBHESHWAR UNIVERSITY OF

SCIENCE AND TECHNOLOGY,

HISAR-125 001

2008-09

ELECTION MANAGEMENT

Submitted By

VISHAL MALHOTRA

Enrolment No. 06031241015

Softdot Hi-Tech Educational & Training Institute

ACKNOWLEDGEMENT

As with any project, the effort is widely collaborative, so I have many people to thank. This project itself is an acknowledgement to the inspiration drive and technical assistance contributed to it by many individuals.

This project would never have seen the light of day without help and guidance that I have received.

I express my sincere thanks to Mrs. Bharti Gupta, for his eminent support.

First and foremost I am extremely grateful to my parents who have been source of inspiration for me during these days, without which I would not have been able to complete this project.

I would like to thank Mr. Virendra Kumar my project guide, who helped me in great way by giving his precious time.

The project has been thoroughly edited and tested so I believe this project likely to be error-free.

CERTIFICATE

This is to certify that Mr. VISHAL MALHOTRA Regn. No:-06031241015 has worked under my supervision to prepare her project report entitled ELECTION MANAGEMENT. The work embodied in this report is original and was conducted at Softdot Hi-Tech Educational & Training Institute from 12-09-08 to 14-11-08. This work has not been submitted in part or full or any other university for the award of any other degree or diploma.

Signature of Supervisor:Name: Virendra Kumar: Designation: Faculty (IT-Department) Organization/Institute: Softdot Hi-Tech Educational & training InstituteDECLARATIONI hereby declare that the minor project work entitled ELECTION MANAGEMENT submitted for the MCA (5yrs course) is my original work carried out by me under the guidance of Mr. Virendra Kumar for the partial fulfillment of the award of the degree of the Master of Computer Applications. The matter embodied in this report has not submitted anywhere else for the award of any other degree/diploma.Place:Date: Signature of the candidate

INDEX

1.Objectives2.Introduction

3.Definition of Problem (Problem Analysis)

4.Need of Proposed system

5.Feasibility Study

6.System Analysis

7.System Design

a) Physical Design

b) Flow Charts

c) DFDs

d) ER-Diagram

e) Output screens

f) Database and file design

g) Program file design

8.Coding

9.Validation Checks

10.System Implementation Requirement

11.Scope of Improvement

12.Conclusion

13.User Manual

OBJECTIVESOBJECTIVES

Objective of this software is to computerize the Election system of Indian states, so that all the working becomes fast and there should not be any error in calculations, reports, and keeping records. It keeps records of thousands of voters and candidates. It provides reports whenever user wants and remembers each and every record. The project provides such user friendliness and easy understandability that even a novice user will find it easy to use the package and grasp its essence.

INTRODUCTIONIntroduction

Developing such systems expedites problem solving and improves the quality of decision-making. This is where the role of systems analysts becomes crucial. They are confronted with the challenging task of creating new systems and planning major changes in the organization. Like architects, they work with users to identify the goal(s), agree on a procedure and a timetable, and deliver a system that meets the user's requirements.

This chapter focuses on the stages of the system development life cycle, sometimes referred to as a system study. The systems analyst gives a systems development project meaning and direction. A candidate system is approached after the analyst has a thorough understanding of user needs and problems, has developed a viable solution to these problems, and then communicates the solution(s) through the installation of a candidate system. Candidate systems often cut across the boundaries of users in the organization. For example, a billing system may involve users in the sales order department, the warehouse, and the accounting department. To make sure that all users needs are met a project team that represents each user works with the analyst to carry out a system development project. In complex projects representatives from other user areas influenced by the candidate system as well as information systems specialists may also be included.

The system Development Life Cycle

To understand system development, we need to recognize that a candidate system has a life cycle, just like a living system or a new product. Systems analysis and design are keyed to the system life cycle. The stages are shown in the below Figure. The analyst must progress from one stage to another methodically, answering key questions and achieving results in each stage.

A word of caution regarding life cycle activities. We isolate and sequence these activities for learning purposes, but in real life they overlap and are highly interrelated. For example, when the analyst is evaluating an existing operation, he/she is probably thinking about an alternative way that would improve the system or wondering whether a given piece of hardware would be critical cost item to consider for a candidate system. Therefore, there can easily be overlap during any phase of the cycle. In fact, it may act as a basis for modifying earlier steps taken. We now describe each of these steps.

FIGURE:

DEFINITIONOFPROBLEMDEFINITION OF PROBLEM(Problem Analysis)

One of the most difficult tasks of system analysis is developing a clear, in-depth under- standing of the problem being investigated, without which it becomes impossible to specify the requirements for a new project with any accuracy. Several questions should be posed for this.

Some of those may be:

What is the problem?

How complex is it?

What are its likely causes?

Why is it important that the problem be solved?

What are possible solutions to the problem?

What types of benefits can be expected once the problem is solved?

It takes considerable skill to determine the true cause of a systems problem. A systems analyst might begin to define the problem by determining if the problem can be classified ac- cording to one or more common types of systems problems. With knowledge of the Common types of problems, the analyst can diagnose a problem by examining its characteristics.

Organizations usually face problems or have opportunity due to the following:

a new product or plant or branch

a new market or new process

failure of an existing system

inefficiency of an existing system

structural error in the existing system, etc.

For identifying problems/opportunities, we scan the following:

the performance of the system

the information being supplied and its form

the economy of processing

the control of the information processing

the efficiency of the existing system

the security of the data and software

the security of the equipment and personnel, etc.

After identification of the problem, it is defined and a general direction or method for solving this problem is also determined. Then project boundaries are defined. The management establishes the term of reference as well as the resources to be provided for the project. System development is an iterative process and the first identifiable stage of it is Problem Definition, whose final output is Terms of Reference.

Careful analysis of this system suggests a number of different problems:

1. Problem of Reliability: Current system is not reliable. It seems to vary in quality and results from one Election to the, next. Some times it gives good output, but some times the output is worst.

2. Problem of Accuracy: There are too many mistakes in reports and calculations of votes.

3. Problem of timeliness: In the current system the reports and output produced is mostly late and in most of the cases it is useless because it is not on time.

4. Problem of Validity: The output and reports mostly contains misleading information. The transactions and calculations are sometimes not valid.

5. Problem of Economy: The current system is very costly. We have to spend lots of money in manual filing, calculations and remembering the information, but still not get the desired results.

6. Problem of Capacity: The current system is suffering from problem of capacity also. The workload is too much. Few peoples cannot handle all the working.

NEEDOFPROPOSEDSYSTEMNEED OF PROPOSED SYSTEM1. Voter Details: The new proposed system stores and maintains the entire voter details automatically and accurately. It remembers all the records and can immediately produces the required reports at any time without any errors.2. Candidate Details: The new proposed system stores and maintains the Candidate details also. It remembers all the records of candidate and can immediately produces the required reports at any time without any errors.

3. Calculations: The new proposed system calculates votes given by voters and shows the final result of election and it is very fast and accurate.

4. Registers: There is no need of keeping and maintaining voter and candidates register manually. It remembers each and every record and we can get any report related to election, candidate and voters at any time.

5. Speed: The new proposed system is very fast with 100% accuracy and saves time.

6. Manpower: The new proposed system needs less manpower. Less people can do the large work.

7. Daily transactions: The new proposed system maintains daily transactions like voter and candidate information, issue voter card, calculating votes, setting election dates etc.

FEASIBILITYFEASIBILITY STUDY

Steps in feasibility analysis

Eight steps are involved in the feasibility analysis. They are:

1. Form a project team and appoint a project leader.

2. Prepare system flowcharts.

3. Enumerate potential proposed systems.

4. Define and identify characteristics of proposed system.

5. Determine and evaluate performance and cost effectiveness of each proposed system.

6. Weight system performance and cost data.

7. Select the best proposed system.

8. Prepare and report final project directive to management

Type of feasibilities

1. Economic Feasibility

Economic analysis is the most frequently used technique for evaluating the effectiveness of a proposed system. More commonly known as cost / benefit analysis; in this procedure we determine the benefits and savings that are expected from a proposed system and compare them with costs. We found the benefits outweigh the costs; we take a decision to design and implement the new proposed system.

2. Technical Feasibility

This is concerned with specifying equipment and software that will successfully satisfy the user requirement. The technical needs of the system may vary considerably, but might include:

The facility to produce outputs in a given time.

Response time under certain conditions.

Ability to process a certain volume of transaction at a particular speed.

Facility to communicate data to distant location.

After examining technical feasibility, we give more importance to the configuration of the system than the actual make of hardware. The configuration gives the complete picture about the system's requirements.

3. Operational Feasibility

It is mainly related to human organizational and political aspects. The points to be considered are:

what changes will be brought with the system?

what organizational structures are disturbed?

what new skills will be required? Do the existing staff members have these skills?

If not, can they be trained in due course of time?

Generally project will not be rejected simply because of operational infeasibility but such considerations are likely to critically affect the nature and scope of the eventual recommendations.

For operational feasibility study we appointed a small group of people who are familiar with information system techniques, who understand the parts of the business that are relevant to the project and are skilled in system analysis and design process.

4. Social feasibility

Social feasibility is a determination of whether a proposed project will be acceptable to the people or not. This determination typically examines the probability of the project being accepted by the group directly affected by the proposed system change.

5. Management feasibility

It is a determination of whether a proposed project will be acceptable to management. If management does not accept a project or gives a negligible support to it, the analyst will tend to view the project as a non-feasible one.

6. Legal feasibility

Legal feasibility is a determination of whether a proposed project infringes on known Acts, Statutes, as well as any pending legislation. Although in some instances the project might appear sound, on closer investigation it may be found to infringe on several legal areas.

7. Time feasibility

Time feasibility is a determination of whether a proposed project can be implemented fully within a stipulated time frame. If a project takes too much time it is likely to be rejected.

SYSTEM ANALYSISSYSTEM ANALYSIS

Systems analysis and design refers to the process of examining a business situation with the intent of improving it through better procedures and methods. Systems development can generally be thought of as having two major components: Systems Analysis and Systems Design. Systems design is the process of planning a new system or replace or complement an existing system. But before this planning can be done, we must thoroughly understand the existing system and determine how computers can best be used to make its operation more effective. Systems analysis, then, is the process of gathering and interpreting facts, diagnosing problems and using the information to recommend improvement to the system. In brief, we can say that analysis specifies what the system should do. Design states hew to accomplish the objective.

In this project we have used Rapid Application Development (RAD) model. RAD is an incremental software development process model that emphasizes an extremely short development cycle. The following phases are encompassed:

Business modeling: All the information about the business functioning of the Airways department is collected, how the data and information is flow from one end to another end using the following questions: What information drives the department process? What information is generated? Who generates it? Where does the information go? Who process it? Data modeling: The information collected in Business modeling phase is refined into a set of data objects that are needed to support the project. The attributes of each object are identified and the relationships between these objects defined. Process modeling: Processing descriptions and functions like maintaining voter and candidate records, issuing voter cards, setting election date, calculating votes, printing reports, providing information, file handling etc. are created. Application generation: The fourth generation techniques are used to generate application, like reusing the predefined functions or creating reusable components.Testing: Most of the functions are already tested, as they are predefined functions. However, new components or functions are also tested after application generation.SYSTEM DESIGNSYSTEM DESIGN

The systems objectives outlined during the feasibility study serve as the basis from which the work of system design is initiated. Much of the activities involved at this stage is of technical nature requiring a certain degree of experience in designing systems, sound knowledge of computer related technology and thorough understanding of computers available in the market and the various facilities provided by the vendors. Nevertheless, a system cannot be designed in isolation without the active involvement of the user. The user has a vital role to play at this stage too. As we know that data collected during feasibility study will be utilized systematically during the system design. It should, however, be kept in mind that detailed study of the existing system is not necessarily over with the completion of the feasibility study. Depending on the plan of feasibility study, the level of detailed study will vary and the system design stage will also vary in the amount of investigation that still needs to be done. Sometimes, but rarely, this investigation may form a separate stage between Feasibility Study and Computer System Design. Designing a new system is a creative process, which calls for logical as well as lateral thinking. The logical approach involves systematic moves towards the end product keeping in mind the capabilities of the personnel and the equipment at each decision making step. Lateral thought implies encompassing of ideas beyond the usual functions and equipment. This is to ensure that no efforts are being made to fit previous solutions into new situations.

System Design Considerations

The system design process is not a step-by-step adherence of clear procedures and guidelines. Though, certain clear procedures and guidelines have emerged in recent days, but still much of design work depends on knowledge and experience of the designer.

When designer starts working on system design, he will face different type of problems. Many of these will be due to constraints imposed by the user or limitations of the hardware and software available in the market. Sometimes, it is difficult to enumerate the complexity of the problems and solutions thereof since the variety of likely problems is so great and no solutions are exactly similar. However, following considerations should be kept in mind during the system-designing phase:

The primary objective of the design: Of course, is to deliver the requirements as specified in the feasibility report. In general, the following design objectives should be kept in mind:

a. Practicality: The system must be stable and can be operated by people with average +

b. Efficiency: This involves accuracy, timeliness and comprehensiveness of the system output.

c. Cost: it is desirable to aim for a system with a minimum cost subject to the condition that it must satisfy all the requirements.

d. Flexibility: The system should be modifiable depending on the changing needs of the user. Such modifications should not entail extensive reconstructing or recreation of software. It should also be portable to different computer systems.

e. Security: This is very important aspect of the design and should cover areas of hardware reliability, fall back procedures, physical security of data and provision for detection of fraud and abuse.

System design involves first logical design and then physical construction of the system. The logical design describes the structure and characteristics of features, like the outputs, inputs, files, databases and procedures. The physical construction, which follows the logical design, produces actual program software, files and a working system.

The designer normally will work under following constraints:

1. Hardware: The existing hardware will obviously affect the system design.

2. Software: The available software (operating system, utilities, language etc.) in the market will constrain the design.

3. Budget: The budget allocated for the project will affect the scope and depth of design.

4. Time-scale: The new system may be required by a particular time (e.g. the start of a financial year). This may put a constraint on the designer to find the best design.

5. Interface with other systems: The new system may require some data from another computerized system or may provide data to another system in which case the files must be compatible in format and the system must operate with a certain processing cycle.

Processing Techniques

The processing options available to the designer are:

- Batch processing

- Real-time processing

- On-line processing

- A combination of all the above

You are already aware of these techniques. It is quite interesting to note, however, that a combination of these is often found to be ideal in traditional data processing applications. This increases throughput of the system as also brings down the response time of on-line activities. In most of die business applications, 24-hour data is acceptable enough and hence it is possible to update voluminous data after office-hours in batch mode.

PHYSICAL

DESIGN

DESIGN METHODOLOGIES

The scope of the systems design is guided by the framework for the new system developed during analysis. More clearly defined logical method for developing system that meets user requirements has led to new techniques and methodologies that fundamentally attempt to do the following:

- improve productivity of analysts and programmers

- improve documentation and subsequent maintenance and enhancements.

- cut down drastically on cost overruns and delays

- improve communication among the user, analyst, designer, and programmer.

STRUCTURED DESIGN

Structured design is a data flow based methodology. The approach begins with a system specification that identifies inputs and outputs and describes the functional aspects of the system. The specifications then are used as a basis for the graphic representation. The next step is the definition of the modules and their relationships to one another in a form called a structure chart, using a data dictionary and other structured tools.

Logical design proceeds from the top down. General features, such as reports and inputs are identified first. Then each is studied individually and in more detail. Hence, the structured design partitions a program into small, independent modules. They are arranged in a hierarchy that approximates a model of the business area and is organized in a top-down manner. Thus, structured design is an attempt to minimize the complexity and make a problem manageable by subdividing it into smaller segments, which is called Modularization or decomposition.

A design is said to be top-down if it consists of a hierarchy of modules, with each module having a single entry and a single exit subroutine.

The primary advantages of this design are as follows:

Critical interfaces are tested first.

Early versions of the design, though incomplete, are useful enough to resemble the real system.

Structuring the design, perse, provides control and improves morale.

Major System Design Activities

Several development activities are carried out during structured design. They are data base design, implementation planning, system test preparation, system interface specification, and user documentation.

a. Data base design: This activity deals with the design of the physical database. A key is to determine how the access paths art to be implemented.

b. Program design: In conjunction with database design is a decision on the programming language to be used and the flowcharting, coding, and debugging procedure prior to conversion. The operating system limits the programming languages that will run of the system.

c. System and program test preparation: Each aspect of the system has a separate test requirement. System testing is done after all programming and testing completed The test cases cover every aspect of the proposed system, actual operations, user interface and so on. System and program test requirements become a part of design specifications - a pre requisite to implementation.

In contrast to the system testing is acceptance testing, which puts the system through a procedure design to convince the user that the proposed system will meet the stated n requirements.

Flowcharts

Prepare System Flowcharts

The next step in the feasibility study is to prepare generalized system flowcharts for the system. Information-oriented charts and data flow diagrams prepared in the initial investigation are also reviewed at this time. The charts bring up the importance of inputs, outputs and data flow among key points in the existing system. All other flowcharts needed for detailed evaluation are completed at this point.FLOW CHART

DFDS

PROCESS MODELING

Graphical description of a system's data and how the processes transform the data is known as Data Flow Diagram (or DFD).

Unlike detail flowcharts, DFDs do not supply detailed descriptions of modules but graphically describe a system's data and how the data interact with the system.

To construct data flow diagrams, we use:

i. arrows,

ii. circles,

iii. open-ended boxes, and

iv. squares

An arrow identifies data flow - data in motion. It is a pipeline through which information flows. Like the rectangle in flowcharts, circles stand for a process that converts data/into in- formation. An open-ended box represents a data store-data at rest, or a temporary repository of data. A square defines a source (originator) or destination of system data.

The following seven rules govern construction of data flow diagrams (DFD):

1. Arrows should not cross each other.

2. Squares, circles, and files must bear names.

3. Decomposed data flows must be balanced (all data flows on the decomposed diagram must reflect flows in the original diagram).

4. No two data flows, squares, or circles can have the same name.

5. Draw all data flows around the outside of the diagram.

6. Choose meaningful names for data flows, processes, and data stores. Use strong verbs followed by nouns.

7. Control information such as record counts, passwords, and validation requirements are not pertinent to a data-flow diagram.

If too many events seem to be occurring at a given point, an analyst can decompose a data conversion (circle). The new data conversions form a parent-child relationship with the original data conversion: the child circle

1st Level DFD

2nd Level DFD

3rd Level DFD

ER-DIAGRAM

ER-DIAGRAM

OUTPUT

SCREENS

MAIN SCREEN

DELETION OF CANDIDATE

ISSUE VOTING CARDS

ADDITION OF CANDIDATES

ADDITION OF VOTERS

SET NEW ELECTION DATE

DELETION OF VOTER

OPTIONS

ELECTION

CANDIDATE INFORMATION

DATABASE AND FILE DESIGNDATABASE AND FILE DESIGNDATABASE DESIGN/DATA DICTIONARY

Data dictionary stores description of data items and structures as well as systems processes. It is intended to be used to understand the system by analyst who retrieves the details and descriptions stores. He takes the help of data dictionary during system design, when information about such concerns as data length, alternate names (aliases) and data use in particular processes must be available. The data dictionaries have also validation information in storage to help the analysts in specifying controls for the system's acceptance of data. The dictionary also contains definitions of data flows, data stores and processes. They also perform cross-reference checking and error detection.

A data dictionary defines each term (called a data element) encountered during the analysis and design of a new system. Data elements can describe files, data flows, or processes.

Three files have been used in this project:

1. VOTER.DAT (Stores all information for voter)

voter no (char)

:

Voter no. of the voter.

name (char)

:

Name of the voter.

address (char)

:

Address of the voter.

status (int)

:

Vote given by voter or not.

card status (int)

:

Card issued to voter or not.

2. CAN.DAT (Stores all information for Candidate)

name (char)

:

Name of the Candidate.

symbol (char)

:

Symbol of the candidates party.

votes (int)

:

No. of votes he gets.

3. ELEDATE.DAT (Stores information for Election date)

dd, mm, yy (int)

:

Date of the Election.

PROGRAM

FILE

DESIGN

PROGRAM FILE DESIGN

This program is having four classes:

VOTER

CANDIDATE

VOTING_DATE

DRAW

List of Modules in class VOTER:

ADD_VOTER()

FUNCTION TO ADD THE VOTERS IN VOTERS FILE

VOTER_INFORMATION ()

FUNCTION TO DISPLAY THE VOTER INFORMATION

VOTER_LIST ()

FUNCTION TO DISPLAY THE VOTER'S LIST

ISSUE_VOTING_CARD()

FUNCTION TO ISSUE THE VOTING CARDS TO THE VOTERS

RESET_STATUS()

FUNCTION TO RESET ALL THE STATUS IN THE VOTER'S FILE

DELETE_VOTER()

FUNCTION TO GIVE THE VOTER NAME TO DELETE VOTER RECORD

ELECTION()

FUNCTION TO GIVE VOTES BY THE VOTERS

VOTE_CALCULATION

FUNCTION TO CALCULATE THE VOTES GIVEN BY THE VOTERS

DELETE_RECORD()

FUNCTION TO DELETE VOTER RECORD FOR THE GIVEN VOTER NAME

List of Modules in class CANDIDATE:

ADD_CANDIDATE()

FUNCTION TO ADD CANDIDATE RECORD IN THE CANDIDATE FILE

CANDIDATE_INFORMATION()

FUNCTION TO DISPLAY THE CANDIDATE INFORMATION

VOTING_LIST()

FUNCTION TO DISPLAY THE LIST OF THE VOTES RECEIVED BY CANDIDATE

ADD_VOTES()

FUNCTION TO ADD VOTES IN THE FAVOUR OF GIVEN CANDIDATE

RESET_STATUS()

FUNCTION TO RESET VOTES RECEVIED BY CANDIDATE TO ZERO

DELETE_CANDIDATE()

FUNCTION TO GIVE CANDIDATE SNO. TO DELETE RECORD

DELETE_RECORD()

FUNCTION TO DELETE RECORD OF THE GIVEN CANDIDATE

List of Modules in class VOTING_DATE:

SET_DATE()

FUNCTION TO SET THE DATE FOR THE NEW ELECTION

VALID_DATE()

FUNCTION TO RETURN THE VALIDITY OF THE TODAY DATE

RETURN_DATE()

FUNCTION TO RETURN THE ELECTION DATE

List of Modules in class DRAW:

LINE_HOR()

FUNCTION TO DRAW HORIZONTAL LINE

LINE_VER()

FUNCTION TO DRAW VERTICAL LINE

CODINGCODING

//**********************************************************

//PROJECT ELECTION

//**********************************************************

//**********************************************************

//INCLUDED HEADER FILES

//**********************************************************

#include

#include

#include

#include

#include

#include

#include

#include

#include

//**********************************************************

// THIS CLASS CONTROL ALL THE FUNCTIONS RELATED TO VOTER

//**********************************************************

class VOTER

{

public:

void ADD_VOTER(void) ;

void VOTER_INFORMATION(void) ;

void VOTER_LIST(void) ;

void ISSUE_VOTING_CARD(void) ;

void RESET_STATUS(void) ;

void DELETE_VOTER(void) ;

void ELECTION(void) ;

void VOTE_CALCULATION(void) ;

void CALCULATE(char []) ;

protected :

int DELETE_RECORD(char []) ;

char voterno[6], name[26], address[36] ;

int status, cardstatus ;

} ;

//**********************************************************

// THIS CLASS CONTROL ALL THE FUNCTIONS RELATED TO CANDIDATE

//**********************************************************

class CANDIDATE

{

public :

void ADD_CANDIDATE(void) ;

void CANDIDATE_INFORMATION(void) ;

void VOTING_LIST(void) ;

int ADD_VOTES(int) ;

void RESET_STATUS(void) ;

void DELETE_CANDIDATE(void) ;

protected :

int DELETE_RECORD(int) ;

char name[26], symbol[15] ;

int votes ;

} ;

//**********************************************************

// THIS CLASS CONTROL ALL THE FUNCTIONS RELATED ELECTION

// DATE

//**********************************************************

class VOTING_DATE

{

public :

void SET_DATE(void) ;

int VALID_DATE(void) ;

char *RETURN_DATE(void) ;

private :

int dd, mm, yy ;

} ;

//**********************************************************

// THIS CLASS CONTROL ALL THE FUNCTIONS TO DRAW LINES,

// BOXES, ETC.

//**********************************************************

class DRAW

{

public :

void LINE_HOR(int, int, int, char) ;

void LINE_VER(int, int, int, char) ;

} ;

//**********************************************************

// FUNCTION TO DRAW HORIZONTAL LINE

//**********************************************************

void DRAW :: LINE_HOR(int column1, int column2, int row, char c)

{

for ( column1; column1