ELECTION MANAGEMENT SYSTEM

Introduction

STUDENT ID CARD MANAGENT SYSTEM

Introduction
Our project is about the student management system of UIIT in which we
deals about the student Identity card of the department of UIIT of
UAAR(University of arid agriculture Rawalpindi).

1.1 Purpose & Scope

This software is for the automation of student id card system at UIIT. It
provides following:

Admin
Can enter the details related to the particular Student, class with and can
also retrieve the information related to the class and Student. His/her class
performance can be analyzed with the reports available online at the website.
Admin can also read & write information about any center and can create
,update ,delete center as per the requirement and implementation plans.

Students
Students can only read the various reports and data and can only get the
information about the particular class and other information relating to the
student.

1.2 Technologies to be used

This Software is developed with:

Oracle 10g for windows NT using Structured Query Language(SQL) for

back end

Java for interface form.

Smart draw for ERD.

1.3 Assumption
Customized data will be used in this application.
 Student does not have right to write, they only right to read .

Only administrator has the right to register the student.

1.4 System Requirements

Minimum RAM - 128 MB
Hard Disk - 40 GB
Processor - Intel Pentium 4
Operating System - Window XP Service Pack 2

1.5 Overview
Project is related to student id card management system of Uiit.

Main faculties available by this project for :

On line registration (form filling).

In this project collection of data about different student will be automatic.

Data captured by students will be automatically updated.

Related reports will be an available after the monthly data entered.

System Development Life Cycle (SDLC)

If we talk about making software and we ignore the process f the SDLC, it
will be impossible to the software efficient and effective. To make the software
efficient, effective and successful we have to follow the process of the SDLC. In
which there is a hierarchy of steps which helps us in making the complex
software so easily and it also help us in saving our time , money and resources.
Following are the phases that are involved in the process of the SDLC:

I. Feasibility Study

II. Planning

III. Analysis

IV. Logical Design

V. Physical Design

VI. Implementation

VII. Maintenance
Feasibility Study
In feasibility study phase we had undergone through various steps, which
are described as under: How feasible is the system proposed? This was
analyzed by comparing the following factors with both the existing system and
proposed system.

Economical Feasibility

In economical feasibility study we had searched the market and observe

the cost of our software and estimate the cost that will be charged on the new
automated system. We compare the cost of the existing system and the cost of
the proposed system. After the comparison we are able to know that the cost
required in the proposed system is comparatively less to the existing system.

Technical Feasibility

This project is technical feasible as required softwares are easily

available with our team. In this stage we used some softwares that help us in
making our software which we have discussed above i.e. Oracle 10g for
windows NT using Structured Query Language(SQL) for back end, Java for
interface form, Smart draw for ERD.

Behavioral Feasibility

In the existing system the number of staff required for completing the
work is more while the new system will require quite less number of staff.

Time

Also the time required generating a report or for doing any other work
will be comparatively very less than in the existing system. Record finding and
updating will take less time than the existing system.

planning
When student get admit to the university .We will provide them a form to
each student to fill that form. with the help of that form we will be able to get
or collect the desire data about the students. we will done this with the help of
E-R diagram. We will mentioned these data on a single card which is called the
student I-D card of the department of UIIT.

Scope and aim

 Our basic idea is to facilitate the new comer student who are select after
conducting an entry test from hundreds of applicant. Our basic aim is to fulfill the
security measures that every institute is facing now-a-days.

For example, the student identity card help the security forces to differentiate
between the students and the terrorists in case of any attack from the terrorists on the
institute, and the Police or Army get fought with them. If the student hang his/her
student identity card then he/she can escape securely from the terrorists.

Resources
The basic pillar of any project or task is its resources. Without any resource you
cannot complete any task or project. For example, if you want to build a building you
will need some resources to complete the task like Man resources, Financial resources
and information resources.

Same here we are also required some resources to fulfill our task or project. We
will require a high level information resources about the students.

Analysis
After we have complete the first phase planning, now it is analysis turn; in
analysis step we will briefly breaks our gather information into different parts and after
that we give each of them a specific name which identify the whole information about
the data what we gather in short we called them (HEADING) from the information form
of the students. Which includes the following:

a. Name of the student.

b. Students Father name .

c. Registration Number.

d. Degree/course in which he get admission

e. Department UIIT

f. Validity date of the id card

g. Emergency phone number which will be helpful in case of card loss or any
emergency situation.

h. Finally, the address of the student.

Logical design
Now in logical design phase we collect the rough data from of each analysis
part and try to collect them each in one platform . Our scheme is to maintain the data
in rows and columns . We will make relations between entities using tables. We have
gather some data as we have discuss that in the analysis phase. We put the data in
the logical design roughly have a look on it.
 Syed Rehan ,Syed Zill-e-Ali, M.Asad Iqbal, Bushra Shaukat, Bs(CS), Bs(IT),
09-arid-668,09-arid-670,09-arid-635,09-arid-608,two photos of each student.

Physical design
Now in physical design we will insert the data we have gather through analysis
and logical design into tables in rows and columns in an appropriate order or
sequence. Like first we will put the student name then father name then reg No. then
degree or course in which the student take admission. Then the department of UIIT
name, then validity of that I-D card, then emergency phone number for any
emergency condition or incase of card loss, and in the end the address of the student.
Like we have shown the rough exhibit of the data; in physical design we will insert the
data orderly. We have the data of a student which we put in physical design Shown
below:

Student name : Syed Rehan

Father name :Syed Afsar Ali Shah

Reg No. :09-arid-668

Degree :Bs(Cs)

Dept : UIIT

Valid up to : 31-08-2013

Address :H#06-St# 07-A-Block Soan gardens Islamabad

Emergency tell No. :03365274398

Two small size photos of each student.

Implementation
After performing all the formalities of gathering data from the students and
inserting these data into table forms and after doing all the steps of SDLC that
includes Planning , Analysis, Logical design and physical design now it is
implementation turn in which we will use some language through which we could able
to work efficiently. We have select the structure query language (SQL).

Maintenance
After the id cards has been issue to the student and the process has been done
now its maintenance turn. In maintenance phase we will check and test to find
whether the id cards are in correct form or the data about the student we have
entered in the card is correct or not and if there is any error on the card we will correct
these error in this phase. Like we have given the data related to one student above if
the name of the student or any of the data that is related to that student is in correct
e.g. if we write the name of student Syed Rehman instead of Syed Rehan and
after issuing the id cards o the students if the related student come to us or contact us
and complained about the error then we will go and fix his problem.

Existing System

Working of the Present System

After student form filling process, the admin have to store the data about
a particular student in the traditional system of registers.

Disadvantages of the Current System

The s which he/she has assigned According to their area. Both capturing
will be happened in this System. Transportation charges will be high. Time
consuming process.

Proposed System
It is a web enabled application so that student can get registered his/her self
from anywhere. It will take less time as compare to existing system. It reduces the
time for manual errors and there corrections highly secured system , Easy user
interface and timeliness Booth capturing would be stopped. Transportation charges
will be reduced. It requires less Man power.

Database design
In this section of our project we will discuss some logical and physical design
process of our project which we had discussed early in the software developing
life cycle(SDLC). According to our project and our E-R-D( which we have
discussed below) we have the following tables:

I. Student

II. Admin

III. Estate care office

IV. Id card

V. Department
 Entity Relation Diagram
Student
E.C.O
S_name Admin
Form No
F_name Form No (Fk)
(Fk)
Form No E_id (Pk)
(PK) Will A_name
Will E_rank
sub
Address A_id (pk) proc
mit
eed
the
Contact # the
form
form
D.O.B s
s to
to
Gender

N.I.C

Will
Mana
ge
Departme and
nt distri
bute
Belon Form No
gs to (Fk)
Id card
D_name
Regt.No
D_location (FK)
D_id (PK) Form No
d (Fk)

Validity_da
Morning
te

BsCs Emergency
Shift Evening
BsIT #
BSCS Will
Mcs Blood
receive
Mcs
M.IT group
 name

Modular decomposition
Every project or systems have some major types in which they are dived.
Same here our project has also two major parts which we have
decompose in two modules

I. Student.

II. Id card.

I. Student

students will fill a form in which all the data about student will be
entered and students will be submit it to the admin

Then the admin will proceed it to the estate care office (E.C.O).

Then the E.C.O will check all the information that is on the form of
student.

II. Id card

I. After checking the forms and performing all the formalities by E.C.O, if
the information is correct then they will distribute the id cards among the
students according to their form number.

The system Architecture

System architecture of any project or system tells us about the flow of
any project or system. Our proposed systems architecture is as followed:
 System architecture of student id card
management system
Normalization
Normalization is the process of decomposing relations with anomalies to
produce smaller, well-structured relations. It has three types 1st normal form, 2nd
normal form, 3rd normal form

Un normalized data 3rd Normal form

Student Student

S_name S_name
F_name F_name
Form No Form No (PK)
Address Address
Contact # Contact #
D.O.B D.O.B
Gender Gender
N.I.C N.I.C
Admin Admin

Form No Form No (Fk)

A_name
A_id A_name
E.C.O A_id (pk)
Form No E.C.O
E_id
E_rank Form No (Fk)
Department
E_id (Pk)
D_name
D_location E_rank
D_id
Department
Regt.No
Form No Form No (Fk)
Validity_date
Emergency# D_name
Blood group
Course name D_location

D_id (PK)