SYSTEM ANALYSIS:

PROBLEM DEFINITION:

The introduction of any unauthorised material or device into the examination room constitutes an
examination offence and may result in disciplinary action being taken against you. Please be aware
that if unauthorised material is found on your person during an exam, it will be confiscated and
submitted to your department, together with a report, for them to consider any disciplinary action

EXISTING SYSTEM:

You are not allowed to communicate by word of mouth or otherwise with other
candidates (this includes the time when answer scripts are being collected).
Please raise your hand if you wish to communicate with an invigilator.
Unless granted permission by an invigilator, you are not allowed to leave your seat.
Once you have entered the examination hall, you will not be allowed to leave the
hall until one hour after the examination has commenced.
If, for any reason, you are given permission to leave the hall temporarily, you must be
accompanied by an invigilator throughout your absence from the examination hall. You are
required to leave your handphone on the examination desk when you leave the hall temporarily.
All answers, with the exception of graphs, sketches, diagrams, etc. should be written in
pen. Answers written in pencil will not be marked. The blank pages in the answer book
are to be used only for candidates' rough work. Solutions or any other materials written
on these blank pages will not be marked.
Do not write on, mark, highlight or deface any reference materials provided for the
examination. If found doing so, the reference materials will be removed from your use for
the rest of the examination and you will be made to pay for the cost of the materials that
have to be replaced

LIMITATIONS OF EXISTING SYSTEM:

The introduction of any unauthorised material or device into the examination room constitutes an
examination offence and may result in disciplinary action being taken against you. Please be aware
that if unauthorised material is found on your person during an exam, it will be confiscated and
submitted to your department, together with a report, for them to consider any disciplinary action.
Examination Clashes
If you discover that you have two examinations on the same day, please inform your department as
soon as possible. They will liaise with the central Exams Office who will contact you before the start
of the exams to confirm arrangements put in place for you

ADVANTAGES OF PROPOSED SYSTEM:

If you fall ill during your examination, please raise your hand and an invigilator will attend to you. You

must submit a doctor's certificate to your School / department as soon as possible and not more than

seven days after the date of the examination. The certificate must define the nature of the illness and

the period it covers

A student who is registered for an award and has satisfactorily completed the prescribed period of

study will be regarded as eligible for admission to the relevant examination. Students will be

expected to attend the exam unless satisfactory evidence of illness or other good cause is provided

to your School/department

PROCESS FLOW DIAGRAMS FOR EXISTING AND PROPOSED

SYSTEM:

FEASIBILITY STUDY:

The feasibility of the project is analyzed in this phase and business proposal is put forth with a
very general plan for the project and some cost estimates. During system analysis the feasibility
study of the proposed system is to be carried out. This is to ensure that the proposed system is
not a burden to the company. For feasibility analysis, some understanding of the major
requirements for the system is essential.

Three key considerations involved in the feasibility analysis are

ECONOMICAL FEASIBILITY

TECHNICAL FEASIBILITY

SOCIAL FEASIBILITY
ECONOMICAL FEASIBILITY

This study is carried out to check the economic impact that the system will have on the
organization. The amount of fund that the company can pour into the research and development
of the system is limited. The expenditures must be justified. Thus the developed system as well
within the budget and this was achieved because most of the technologies used are freely
available. Only the customized products had to be purchased.

TECHNICAL FEASIBILITY

This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the available
technical resources. This will lead to high demands on the available technical resources. This
will lead to high demands being placed on the client. The developed system must have a modest
requirement, as only minimal or null changes are required for implementing this system.

OPERATIONAL FEASIBILITY

The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity. The level of acceptance by the
users solely depends on the methods that are employed to educate the user about the system and
to make him familiar with it. His level of confidence must be raised so that he is also able to
make some constructive criticism, which is welcomed, as he is the final user of the system.

HARDWARE AND SOFTWARE REQUIREMENTS:

HARDWARE REQUIREMENTS:
 System : CORE2DUO , DUAL CORE
Hard Disk : 40 GB.
Monitor : 15 VGA Colour.
Ram : 512 Mb.

SOFTWARE REQUIREMENTS:

Operating system : Windows XP, Windows 8

Coding Language : VB.NET
Tools : .NET FRAMEWORK

FUNCTIONAL REQUIREMENTS:

Functional requirements specify which output file should be produced from the given file they
describe the relationship between the input and output of the system, for each functional
requirement a detailed description of all data inputs and their source and the range of valid
inputs must be specified.

NON FUNCTIONAL REQUIREMENTS:

Describe user-visible aspects of the system that are not directly related with the functional
behavior of the system. Non-Functional requirements include quantitative constraints, such as
response time (i.e. how fast the system reacts to user commands.) or accuracy ((.e. how precise
are the systems numerical answers.)

PSEUDO REQUIREMENTS:

The client that restricts the implementation of the system imposes these requirements. Typical
pseudo requirements are the implementation language and the platform on which the system is
to be implemented. These have usually no direct effect on the users view of the system.
LITERATURE SURVEY:
Literature survey is the most important step in software development process. Before developing
the tool it is necessary to determine the time factor, economy n company strength. Once these
things re satisfied, ten next steps are to determine which operating system and language can be
used for developing the tool. Once the programmers start building the tool the programmers need
lot of external support. This support can be obtained from senior programmers, from book or
from websites. Before building the system the above consideration r taken into account for
developing the proposed system.

module
The Examination Seating Module (ESM) provides a facility to manage the complex and time
consuming tasks associated with the.organisation of examinations. This Agresso QLS module is
an essential labour saving tool for Examination Officers which automates the process of
resolving clashes, organising seating for candidates and the production of reports such as seating
plans and candidate timetables.
The ESM is integrated to other data in Agresso QLS including examination and paper
definitions, candidate entries and room definitions. All data on paper dates and times, whether
imported via EDI or through direct data entry, is utilised to assist in the process.
Examination Clashes module
This complex task can be broken down into three main areas:
Resolving examination clashes
Organising examinations
Producing supporting documentation for candidates,
invigilators and examination officers The Modify Timetable form identifies candidate clashes
and allows the user to resolve clashes by changing (displacing) the dates and/ or times of the
paper sittings for that candidate. This section displays the papers to be modified for the selected
date
range. Depending on the radio button selection, the papers displayed
can be either all papers or just those where there are clashes. This section is used to view the
candidates for the chosen paper. Depending on the radio button selection, either all candidates
are displayed or just those candidates with clashes. Candidates with clashes are shown in bold.

Viewing and updating candidate details module

Using this, candidate details, including paper dates, times and displacement times, can be
reviewed and edited. The ESM allows any room to be flagged as available for examinations.
This also allocates a seating range to each of those rooms.
Seating Candidates module
This form allows users to allocate candidates to a room and seat number. Seating arrangements
can be totally user defined to ensure the seating plan fully maximises the capacity of the room
whilst fulfilling awarding body requirements such as spacing of candidates. Available space is
readily highlighted so that additional unseated candidates can be accommodated.
By choosing the Seat radio button all unseated candidates are displayed, whilst when choosing
the Unseat radio button all seated candidates are displayed. A full range of relevant reports
written in Crystal is available to support this process
including:
Attendance Sheets
Seating Labels
Clash Reports
Candidate Timetables
Examination Schedules
Reports can either be printed to paper, or by utilising the power of Agresso QLx technology,
analysed in the Agresso QLx grid.

SYSTEM DESIGN:
Data Flow Diagram / Use Case Diagram / Flow Diagram:

The DFD is also called as bubble chart. It is a simple graphical formalism that can be
used to represent a system in terms of the input data to the system, various processing
carried out on these data, and the output data is generated by the system

The data flow diagram (DFD) is one of the most important modeling tools. It is used to
model the system components. These components are the system process, the data used
by the process, an external entity that interacts with the system and the information flows
in the system.

DFD shows how the information moves through the system and how it is modified by a
series of transformations. It is a graphical technique that depicts information flow and the
transformations that are applied as data moves from input to output.
 DFD is also known as bubble chart. A DFD may be used to represent a system at any
level of abstraction. DFD may be partitioned into levels that represent increasing
information flow and functional detail.
NOTATION:

SOURCE OR DESTINATION OF DATA:

External sources or destinations, which may be people or organizations or other entities.

DATA SOURCE:
Here the data referenced by a process is stored and retrieved.

PROCESS:
People, procedures or devices that produce data. The physical component is not identified.

DATA FLOW:

Data moves in a specific direction from an origin to a destination. The data flow is a packet of
data.

MODELING RULES:

There are several common modeling rules when creating DFDs:

1. All processes must have at least one data flow in and one data flow out.
2. All processes should modify the incoming data, producing new forms of outgoing data.
3. Each data store must be involved with at least one data flow.
4. Each external entity must be involved with at least one data flow.

A data flow must be attached to at least one process.

SDLC:

SPIRAL MODEL: PROJECT ARCHITECTURE:

UML DIAGRAMS:

USE CASE DIAGRAMS:

CLASS DIAGRAMS:
SEQUENCE DIAGRAMS:
ACTIVITY DIAGRAMS:
ER DIAGRAM DIAGRAMS:
DATA FLOW DIAGRAM

Ss
PROCESS SPECIFICATION:

INPUT DESIGN:

The input design is the link between the information system and the user. It comprises the
developing specification and procedures for data preparation and those steps are necessary to put
transaction data in to a usable form for processing can be achieved by inspecting the computer to
read data from a written or printed document or it can occur by having people keying the data
directly into the system. The design of input focuses on controlling the amount of input required,
controlling the errors, avoiding delay, avoiding extra steps and keeping the process simple. The
input is designed in such a way so that it provides security and ease of use with retaining the
privacy. Input Design considered the following things:

What data should be given as input?

How the data should be arranged or coded?
The dialog to guide the operating personnel in providing input.
Methods for preparing input validations and steps to follow when error occur.

OBJECTIVES:

1.Input Design is the process of converting a user-oriented description of the input into a
computer-based system. This design is important to avoid errors in the data input process and
show the correct direction to the management for getting correct information from the
computerized system.

2. It is achieved by creating user-friendly screens for the data entry to handle large volume of
data. The goal of designing input is to make data entry easier and to be free from errors. The data
entry screen is designed in such a way that all the data manipulates can be performed. It also
provides record viewing facilities.
3.When the data is entered it will check for its validity. Data can be entered with the help of
screens. Appropriate messages are provided as when needed so that the user
will not be in maize of instant. Thus the objective of input design is to create an input layout that
is easy to follow

OUTPUT DESIGN:

A quality output is one, which meets the requirements of the end user and presents the
information clearly. In any system results of processing are communicated to the users and to
other system through outputs. In output design it is determined how the information is to be
displaced for immediate need and also the hard copy output. It is the most important and direct
source information to the user. Efficient and intelligent output design improves the systems
relationship to help user decision-making.
1. Designing computer output should proceed in an organized, well thought out manner; the right
output must be developed while ensuring that each output element is designed so that people will
find the system can use easily and effectively. When analysis design computer output, they
should Identify the specific output that is needed to meet the requirements.
2.Select methods for presenting information.
3.Create document, report, or other formats that contain information produced by the system.
The output form of an information system should accomplish one or more of the following
objectives.
Convey information about past activities, current status or projections of the
Future.
Signal important events, opportunities, problems, or warnings.
Trigger an action.
Confirm an action