Introduction:

The purpose of this examination seating planning is to describe all the requirements for the
Examination in charge .The intended audience include in the potential system. These
include, but are not necessarily limited to, the following: Exam hall, date sheet, roll list and
room list. We are consult this examination seating planning and its revisions as the only
source

of requirements for

the

project.

They

should

not

consider

any requirements statements, written or verbal as valid until they appear in this documents
or

revision.

The

this document and

examination
its

management

revisions

as

the

and

its

primary

team

members

means

to

should

use

communicate

confirmed requirements to the development team. The development team expects many
face-to-face

conversations

that

will

undoubtedly

be

about requirements and

ideas

for requirements. Please note that only the requirements that appear in this document or a
future revision, however, will be used to define the scope of the system.
Current system and problem statement:
The present working of the organization is outdated the methodologies used in the working of
organization is traditional and is not efficient. Presently the organization is recording all its all
information of sitting planning on paper documents and books which is old method of recording
of all information. The present system is slow and involves too much clerical and official work
which is prone to errors and unorganized manner of recording University data the present system
do not support updating and edition to the existing system the whole work is to be carried again

Proposed System:

The proposed system is to design an application program for the Examination

Sitting Planning System. This is required to make the working process of the
organization easy and fast. The proposed system is really going to prove a
helpful tool for recording all information of the University in a systematic manner
all the records can be stored in a tabular form through tables which enables ease
of retrieval of data and information. The proposed system is much better in
working and efficiency than the current system.
Benefits:
The developed project has many advantages over the current system of record keeping the
developed project is more economical in terms of man power, less error prone, accurate
seating planning, it is more reliable and recording of all student information is more
systematic and retrieval of data is more easy and systematic.

Faster
Reliable

Accurate
Involves less man power
Systematic data recording
Ease in updating and editing of data

Objective:
The objective of this examination seating plan and jumbling of questions is to give a detail
description about the requirement and need for proposed system
The examination seating planning system and jumbling of questions will be helpful in the
following ways:

Easy storage and retrieval of data

Less time, Do more
Plan generation with less effort and high accuracy
Report generation with less effort and high accuracy
Secrecy and less chance of change or loss of data
Easy generation of reports

Survey:
In the university, i visit in my university departments and met teachers. Also discussed with
the Examination Seating plan Authority that how they manage the arrangement, either
through software or by hand written planning.
Although conclusion of all survey claim that all these work need so much time to manage.

References:
Khawaja Tahir Lecturer Computer Science Department & Project Coordinator
Federal Urdu University Islamabad.
Naeem Akhter Malik, Lecturer Computer Science Department & Leading
Examination arrangements authority.
Dr.Abdul Mateen HOD Computer Science Department
Modules & Sub Modules:

Seating Arrangments Class wise

Schedule exams for different standards by setting subjects exams along with their date and time

Time table scheduling.

Duty Roster
Automatic Email sender to inform Students and teachers

Tools & technologies used:

VB.Net / C#
UPPAAL
DiVinE

System Design Approach:

Process Model Used:
We will use agile system development cycle. We will adopt the sprint method for
development of software.
Limitations/ Constraints:
The potential software only generate state machine diagram. Other diagrams will be
generated in later versions.