You are on page 1of 21

Project Description

Our project entitled Seating arrangement system for college is to develop and setup
an application, which helps universities and college to reduce their human and manage the
examination seating arrangement for the students and also students can know their allotted room
at the time of examination. No of students allocated in a room, staff allocated for the exam
details and much more related information is maintained in an efficient manner in the database
and a user friendly graphical interface is created, so that the information about any room
allotment and staff allotment at the time of examination in colleges with their respective room
can be found in quick time and in less effort.
The overall project is designed and developed in regard to the need of the universities and
colleges where they can do seating arrangement for examination in computerized manner.
This project is meant for maintaining the examination details, student details who are all
attending the exams, Absentees details, Staff allotment for respective room are available in the
database. So we can retrieve the information from database to system at the time of examination.

Visual Basic 6:
VISUAL BASIC is a high level programming language which evolved from the earlier
DOS version called BASIC. BASIC means Beginners' All-purpose Symbolic Instruction Code. It
is a very easy programming language to learn. The code looks a lot like English Language.
Different software companies produced different versions of BASIC, such as Microsoft
QBASIC, QUICKBASIC, GWBASIC, IBM BASICA and so on. However, people prefer to use
Microsoft Visual Basic today, as it is a well-developed programming language and supporting
resources are available everywhere.
Now, there are many versions of VB exist in the market, the most popular one and still
widely used by many VB programmers is none other than Visual Basic 6. We also have VB.net,
VB2005, VB2008 and the latest VB2010. Both Vb2008 and VB2010 are fully object oriented
programming (OOP) language.
VISUAL BASIC is a VISUAL and events driven Programming Language. These are the
main divergence from the old BASIC. In BASIC, programming is done in a text-only
environment and the program is executed sequentially. In VB, programming is done in a
graphical environment. In the old BASIC, you have to write program code for each graphical
object you wish to display it on screen, including its position and its color. However, In VB , you
just need to drag and drop any graphical object anywhere on the form, and you can change its
color any time using the properties windows.
On the other hand, because the user may click on certain object randomly, so each object
has to be programmed independently to be able to response to those actions (events). Therefore,
a VB Program is made up of many subprograms, each has its own program code, and each can
be executed independently and at the same time each can be linked together in one way or
another.

The Control Properties


Before writing an event procedure for the control to response to a user's input, you have
to set certain properties for the control to determine its appearance and how it will work with the
event procedure. You can set the properties of the controls in the properties window or at
runtime.
Handling some of the common controls
The Text Box
The text box is the standard control for accepting input from the user as well as to display
the output. It can handle string (text) and numeric data but not images or pictures. String in a text
box can be converted to a numeric data by using the function Val(text). The following example
illustrates a simple program that processes the input from the user.
The Label
The label is a very useful control for Visual Basic, as it is not only used to provide
instructions and guides to the users, it can also be used to display outputs. One of its most
important properties is Caption. Using the syntax label.Caption, it can display text and numeric
data. You can change its caption in the properties window and also at runtime.
The Command Button
The command button is one of the most important controls as it is used to execute
commands. It displays an illusion that the button is pressed when the user click on it. The most
common event associated with the command button is the Click event, and the syntax for the
procedure is
The Picture Box
The Picture Box is one of the controls that is used to handle graphics. You can load a
picture at design phase by clicking on the picture item in the properties window and select the

picture from the selected folder. You can also load the picture at runtime using the LoadPicture
method. For example, the statement will load the picture grape.gif into the picture box.
The Image Box
The Image Box is another control that handles images and pictures. It functions almost
identically to the picture box. However, there is one major difference, the image in an Image Box
is stretchable, which means it can be resized. This feature is not available in the Picture Box.
Similar to the Picture Box, it can also use the LoadPicture method to load the picture. For
example, the statement loads the picture grape.gif into the image box.
The List Box
The function of the List Box is to present a list of items where the user can click and
select the items from the list. In order to add items to the list, we can use the AddItem method.
For example, if you wish to add a number of items to list box 1, you can key in the following
statements
The Combo Box
The function of the Combo Box is also to present a list of items where the user can click
and select the items from the list. However, the user needs to click on the small arrowhead on the
right of the combo box to see the items which are presented in a drop-down list. In order to add
items to the list, you can also use the AddItem method. For example, if you wish to add a
number of items to Combo box 1, you can key in the following statements
The Check Box
The Check Box control lets the user selects or unselects an option. When the Check Box
is checked, its value is set to 1 and when it is unchecked, the value is set to 0. You can include
the statements Check1.Value=1 to mark the Check Box and Check1.Value=0 to unmark the
Check Box, as well as use them to initiate certain actions. For example, the program will change
the background color of the form to red when the check box is unchecked and it will change to
blue when the check box is checked. You will learn about the conditional statement

If.Then.Elesif in later lesson. VbRed and vbBlue are color constants and BackColor is the
background color property of the form.

The Option Box


The Option Box control also lets the user selects one of the choices. However, two or
more Option Boxes must work together because as one of the Option Boxes is selected, the other
Option Boxes will be unselected. In fact, only one Option Box can be selected at one time. When
an option box is selected, its value is set to True and when it is unselected; its value is set to
False. In the following example, the shape control is placed in the form together with six
Option Boxes. When the user clicks on different option boxes, different shapes will appear. The
values of the shape control are 0, 1, and 2,3,4,5 which will make it appear as a rectangle, a
square, an oval shape, a rounded rectangle and a rounded square respectively.
The Drive List Box
The Drive ListBox is for displaying a list of drives available in your computer. When you
place this control into the form and run the program, you will be able to select different drives
from your computer as shown in Figure 3.3
The Directory List Box
The Directory List Box is for displaying the list of directories or folders in a selected
drive. When you place this control into the form and run the program, you will be able to select
different directories from a selected drive in your computer.
The File List Box
The File List Box is for displaying the list of files in a selected directory or folder. When
you place this control into the form and run the program, you will be able to shown the list of
files in a selected directory as shown in Figure 3.5

You can coordinate the Drive List Box, the Directory List Box and the File List Box to search for
the files you want. The procedure will be discussed in later lessons.

MICROSOFT ACCESS
MS Access is a powerful multi-user DBMS developed by Microsoft Corp. It can be used to store
and manipulate large amounts of information and automate repetitive tasks, such as maintaining
an inventory and generating invoices. By using Access, we can develop easy-to-use data input
forms and create meaningful reports.
FEATURES OF ACCESS
Windows-Based Application
Access is a Windows-based application and therefore has an interface similar to Windows.
We can cut copy and paste data from any Windows application to and from Access.
Wizards and Builders
A wizard is a utility that helps us to perform complex tasks by guiding us through the
process. Wizards ask questions about the content style and format of the object that we want
to create, such as a report or data-entry screen, and then generate them automatically
Built-in Function
Access includes small programs known as functions that perform simple calculations or data
formatting. Access includes mathematical, financial, date, time and string functions.
Macros

For those users who dont want to write programs, access provides macros. Macros let us
perform common tasks without user intervention. Macros let us manipulate data, open forms
and reports and automate any task that is repetitive or complex.
Context-Sensitive Help and Answer Wizard
Like Windows NT, Access provides online, context-sensitive help. Access also includes a
unique Answer Wizards that answer questions written in simple English.
Built-in Security
Since Access is a multi-user database, security features are built into the DBMS. We can
enable database security at various levels. We can assign a password for loading Access so
that only authorized users can use it
Database Objects
Access stores all the data tables and other objects in a single database. These database objects
are queries, Forms, Reports and Macros.
Queries
A query is used to extract information from a database. A query can select a group of records
that fulfill a certain condition. Most Access databases contain more than one table. We can
combine specific fields from multiple tables into one datasheet
Forms
Forms display and print data from a table or a query. Forms enable us view, edit and print
data in a custom format.
.
reports

Reports present our data in a printed format. We can create different types of reports with a
DBMS. Our reports can combine multiple tables to present complex relationships among
different sets of data.

SYSTEM STUDY
2.1 EXISTING SYSTEM
The existing system is carried out manually. The existing system includes the data entries in
unclear package and most complicated packages. It contains of policies that simply makes the
job more complicated and confusable storages in the system.
Demerits
The processing time is very high.
There is a chance for committing many mistakes.
Retrieval of information is very difficult.
Error detection and correction may take long time.
Wastages of physical efforts.

2.2 PROPOSED SYSTEM


The new proposed system, which has been designed with Microsoft Visual Basic 6.0 as the
Front-end, Microsoft Access 2003 as the Back-end and Data report, is very effective in
eliminating the problems encountered with the existing manual system.
Merits
It reduces tedious calculations.
Maintenance of the record is very easy.
Easy to implement at real time scenarios.
The total processing time is less.
User-friendly environment is provided.

2.3 FEASIBILITY STUDY


A feasibility study is a preliminary study undertaken before the real work of a project starts to
ascertain the likelihood of the project's success. It is an analysis of possible solutions to a
problem and a recommendation on the best solution to use. It involves evaluating how the
solution will fit into the corporation. It, for example, can decide whether an order processing be
carried out by a new system more efficiently than the previous one.
A feasibility study is defined as an evaluation or analysis of the potential impact of a proposed
project or program. A feasibility study is conducted to assist decision-makers in determining
whether or not to implement a particular project or program. The feasibility study is based on
extensive research on both the current practices and the proposed project/program and its impact
on the selected organization operation. The feasibility study will contain extensive data related to
financial and operational impact and will include advantages and disadvantages of both the
current situation and the proposed plan.
The feasibility study is conducted to assist the decision-makers in making the decision that will
be in the best interest of the school food service operation. The extensive research, conducted in
a non-biased manner, will provide data upon which to base a decision.
A feasibility study could be used to test a new working system, which could be used because:

The current system may no longer suit its purpose,


Technological advancement may have rendered the current system redundant,
The business is expanding, allowing it to cope with extra work load,
Customers are complaining about the speed and quality of work the business provides,
Competitors are not winning a big enough market share due to an effective integration of
a computerized system.

Although few businesses would not benefit from a computerized system at all, the process of
carrying out this feasibility study makes the purchaser/client think carefully about how it is going
to be used.
After request clarification, analyst proposes some solutions. After that for each solution it is
checked whether it is practical to implement that solution.

This is done through feasibility study. In this various aspects like whether it is technically or
economically feasible or not. So depending upon the aspect on which feasibility is being done it
can be categorized into four classes:

Technical Feasibility
Economic Feasibility
Operational Feasibility
Legal Feasibility
The outcome of the feasibility study should be very clear. It should answer the following issues.

Is there an alternate way to do the job in a better way?

What is recommended?

Technical Feasibility
In technical feasibility the following issues are taken into consideration.

Whether the required technology is available or not

Whether the required resources are available


o Manpower- programmers, testers & debuggers
o

Software and hardware

Once the technical feasibility is established, it is important to consider the monetary factors also.
Since it might happen that developing a particular system may be technically possible but it may
require huge investments and benefits may be less. For evaluating this, economic feasibility of
the proposed system is carried out.

Economic Feasibility
For any system if the expected benefits equal or exceed the expected costs, the system can be
judged to be economically feasible. In economic feasibility, cost benefit analysis is done in
which expected costs and benefits are evaluated. Economic analysis is used for evaluating the
effectiveness of the proposed system.
In economic feasibility, the most important is cost-benefit analysis. As the name suggests, it is an
analysis of the costs to be incurred in the system and benefits derivable out of the system. Click
on the link below which will get you to the page that explains what cost benefit analysis is and
how you can perform a cost benefit analysis.
Operational Feasibility
Operational feasibility is mainly concerned with issues like whether the system will be used if it
is developed and implemented. Whether there will be resistance from users that will affect the
possible application benefits? The essential questions that help in testing the operational
feasibility of a system are following.

Does management support the project?

Are the users not happy with current business practices? Will it reduce the time
(operation) considerably? If yes, then they will welcome the change and the new system.

Have the users been involved in the planning and development of the project? Early
involvement reduces the probability of resistance towards the new system.

Will the proposed system really benefit the organization? Does the overall response
increase? Will accessibility of information be lost? Will the system affect the customers
in considerable way?

Legal Feasibility

It includes study concerning contracts, liability, violations, and legal other traps frequently
unknown to the technical staff.

3. SYSTEM DESIGN
3.1 INPUT DESIGN
Input Design is the process of converting user-originated data to a computer based
format. Errors are controlled in the input design screen.
The goal of designing the Input Design is to make data entry as easy as possible.
Timely messages are given for every transaction and samples are shown in table
views. So objectives of Input Design are:

To produce cost effective method of Input


To achieve good accuracy
To ensure input is acceptable and understood by the user.

3.2 CODE DESIGN


A code is an ordered collection of symbols designed to provide unique identification of data. The
main purpose of performing the code design is to simplify the coding and to achieve better
performance. The coding is prepared in such a way that the internal procedures are utilized
properly, validation messages are also displayed.
The variable has been chosen for processing of data is meaningful to the context in which it is
used. The coding of variables is done in such a way that anyone other than person who
developed then package can understand its purpose. Thus the maintainability we made easier.
The purpose of code is to facilitate the identification and retrieval of items of information
Coding is done with objects that very quickly processing of data, simple to understand and easy
to debug the errors. Further development and modification in coding will do easily.
3.2.1 CHARACTERISTICS OF GOOD CODING:

Uniqueness

Meaningfulness

Stability

3.3 DATABASE DESIGN


The first step in the development of a project is to design a robust database. Before you design a
database, its a good idea to recapitulate the concepts related to a database. A database is a
repository of data, a place where you can store data and extract it whenever required. You can
store and extract data from a database in various ways. One of the ways is by using SQL
(structured query language) statements.
3.3.1 PRIMARY AND FOREIGN KEYS
To access data stored in a table, you need a way to identify each row stored in the table.
Therefore, the identifier must uniquely identify all data in the table. Such a unique identifier is
called a primary key.
A foreign key is a column or a combination of columns that creates a link between two tables.
Adding the primary key column of one table to another table creates a relationship between the
tables. This primary key column becomes the foreign key in the other table. When any two tables
are related, you cannot delete a record in one table if there is a related record for it in the other
table. This is known as referential integrity.
3.3.2 NORMALIZATION
Normalization refers to the process of reducing data redundancy. It usually involves splitting data
into two or more tables until repeating groups of data are placed in separate tables. To design a
database without having to encounter anomalies, you need to normalize the database.
The following rules help you design a robust database:

A table should have a unique identifier.


A table should not have repeating values or columns.
A table should store data for only a single type of entity.
A table should avoid columns with null values

3.4 OUTPUT DESIGN

The objective of the system is generation of reports for the queries posed. The output gives the
direct source of information to the user. The output design should be well formed so that it
contains all the required information and should be well formed to avoid any complexity in
getting information.
Well-designed output increases the efficiency and it should provide clarity to the user. The
output from the system communicates the results of process to the user. A brief description
should be given at end of each page. The output from the computer system communicates the
results of processing to the user

4. SYSTEM TESTING AND IMPLEMENTATION


4.1 SYSTEM TESTING
System testing is actually a series of different tests whose primary purpose is to fully exercise the
computer-based system. Although each test has a different purpose, all work to verify that all
system elements have been properly integrated and perform allocated functions. In the following
section, different system tests are discussed.
4.1.1 White Box Testing
White box testing focuses on the internal functioning of the product. For this different
procedures are tested. White box testing tests the following

Loops of the procedure

Decision points

4.1.2 Black Box Testing


Black box testing tests the overall functional requirements of product. Inputs are supplied to
product and outputs are verified. If the outputs obtained are same as the expected ones then the
product meets the functional requirements. In this approach internal procedures are not
considered. It is conducted at later stages of testing. Now we will look at black box testing
technique.
Black box testing uncovers following types of errors.

Incorrect or missing functions

Interface errors

External database access

Performance errors

Initialization and termination errors.

4.1.3 Unit Testing


We know that smallest unit of software design is a module. Unit testing is performed to check the
functionality of these units. it is done before these modules are integrated together to build the
overall system. Since the modules are small in size, individual programmers can do unit testing
on their respective modules. So unit testing is basically white box oriented. Procedural design
descriptions are used and control paths are tested to uncover errors within individual modules.
Unit testing can be done for more than one module at a time.
The following are the tests that are performed during the unit testing:

Module interface test: here it is checked if the information is properly flowing into the
program unit and properly coming out of it.

Local data structures: these are tested to see if the local data within unit(module) is
stored properly by them.

Boundary conditions: It is observed that much software often fails at boundary


conditions. That's why boundary conditions are tested to ensure that the program is
properly working at its boundary conditions.

Independent paths: All independent paths are tested to see that they are properly
executing their task and terminating at the end of the program.

Error handling paths: These are tested to check if errors are handled properly by them.

4.1.4 Integration Testing


Unit testing ensures that all modules have been tested and each of them works properly
individually. Unit testing does not guarantee if these modules will work fine if these are
integrated together as a whole system. It is observed that many errors crop up when the modules
are joined together. Integration testing uncovers an error that arises when modules are integrated
to build the overall system.

Integration testing is a systematic technique for constructing the program structure while
conducting tests to uncover errors associated with interfacing. The objective is to take unit tested
modules, integrate them, find errors, remove them and build the overall program structure as
specified by design.
4.1.5 Recovery Testing
Many computer-based systems must recover from faults and resume operation within a prespecified time. In some cases, a system may be fault tolerant; that is, processing faults must not
cause overall system function to cease. In other cases, a system failure must be corrected within a
specified period or severe economic damage will occur.
Recovery testing is a system test that forces the software to fail in a variety of ways and verifies
that recovery is properly performed. It the recovery is automated (performed by system itself),
re-initialization mechanisms, data recovery, and restart are each evaluated for correctness. If the
recovery requires human intervention, the mean time to repair is evaluated to determine whether
it is within acceptable limits.
4.1.6 Stress Testing
Stress tests are designed to confront program functions with abnormal situations. Stress testing
executes a system in a manner that demands resources in abnormal quantity, frequency, or
volume.
4.1.7 Security Testing
Any computer-based system that manages sensitive information or causes actions that can harm
or benefit individuals is a target for improper or illegal penetration.
Security testing attempts to verify that protection mechanism built into a system will protect it
from unauthorized penetration. During security testing, the tester plays the role of the individual
who desires to penetrate the system. The tester may attack the system with custom software
designed to break down any defenses that have been constructed; may overwhelm the system,

thereby denying service to others; may purposely cause system errors, hoping to find the key to
system entry; and so on.
Given enough time and resources, good security testing will ultimately penetrate a system. The
role of the system designer is to make penetration cost greater than the value of the information
that will be obtained in order to deter potential threats.

4.2 SYSYEM IMPLEMENTATION


Implementation is that stage of the project when the theoretical design is turned into working
system. At this stage of the main workload, the greatest up heaved and the major impact on the
existing practices shifts to the under department. A lot of planning has to go in for the successful
implementation o the system.
Being in mind that implementation is a project in itself ; care was taken to develop an effective
methodology for implementing the system. The major steps that are carried out in these stages
are summarized below:

Training was given to the user of the system both theoretically as well practically.

They were briefed on the lines on the objectives of the system how to operate if and
the benefits that would reaped from the system.

The system as test in the users environment and the user was prompted to give his
suggestions.

Existing data was converted into file structures compatible to the system.

The strategy user changeover of the system was parallel along with the automated
system to test the validity of the system.

4.3 SYSTEM MAINTENANCE


It is impossible to produce systems of any size, which do not need to be changed. Over
the lifetime of a system, its original requirements will be modified to reflect changing

user and customer needs. The system's environment will change as new hardware is
introduced. Error, undiscovered during system validation, may merge and require repair.
The process of changing of a system after it has been delivered and is in use is called Software
maintenance. The changes may involve simple changes to correct coding errors, more extensive
changes to correct design errors or significant enhancement to correct specification errors or
accommodate new requirements. Maintenance therefore, in this context, really means evolution.
It is the process of changing a system to maintain its ability to survive.
There are three types of software maintenance with very blurred distinction between them.
4.2.1 Corrective Maintenance
Corrective Maintenance is concerned with fixing reported errors in the software. Coding errors
are usually relatively cheap to correct; design errors are more expensive as they may involves the
rewriting of several programs components. Requirements errors are the most expensive to repair
because of the extensive system redesign with may be necessary.
4.2.2 Adaptive maintenance
Adaptive maintenance means changing the software to new environment such as different
hardware platform or for use with a different operating systems. The software functionality does
not radically change.
4.2.3 Perfective maintenance
Perfective maintenance involves implementing new functional or non-functional system
requirements. These are generated by software customers as their organizations are business
changes.

You might also like