STUDENT PROCTOR SYSTEM

SYNOPSIS
Proctorial student information system provides a simple interface for the maintenance of
student information. To maintain the records of students easily. In manual system record are
difficult to maintain .It is overcome by using Proctorial Student Information System. This system
focuses on presenting information in an easy and intelligible manner.
This is a tracking application where at a time we can see all the year’s result in a single sheet and
a choice of viewing the candidates result separately is also possible. The proposed system t-
sheets are designed in an organized manner. The t-sheets occupy comparatively lesser space, so
memory can be organized in a proper way. Also, the time taken to retrieve the result is faster
compared to the existing system.
The main objective of the project is to provide the examination result to the student in a
simple way. This project is useful for students and institutions for getting the results in simple
manner. By a result analyzer with subject status and marks is an application tool for displaying
the results in secure way. The system is intended for the student. And the privileges that are
provided to student are to read and execute his/her result by providing user name and password
for secure login and in case of new student the registration is available. And the guest user has
the privilege only to read. The whole result analyzer will be under the control of the administrator
and the admin as the full privileges to read, write and execute the result. And admin gives the
privileges to the Teacher and student and the guest user to access the result. The student can
download his/her result.

Modules

 Student Details
 Staff Details
 Subject details
 course details
 Result details
 reports
SYSTEM SPECIFICATION

HARDWARE CONFIGURATION

Processor : intel Pentium III or Higher

RAM : 1 GB RAM or More

Keyboard : 104 keys

Hard Disk : 40 GB.

Monitor : 14’ Colour Monitor.

Mouse : Optical Mouse.

SOFTWARE SPECIFICATION

Front End : Visual Basic.NET 2010

Back End : MS-SQL Server 2005

MODULE DESCRIPTION

The system should be designed in such a way that only authorized people should be allowed

to access some particular modules. The records should be modified by only administrators and no

one else. The user should always be in control of the application and not the vice versa. The user

interface should be consistent so that the user can handle the application with ease and speed. The

application should be visually, conceptually clear

ADMINISTRATOR MODULE:

 Student Details:

In this module deals with the allocation of roll no and personal details for new batch. It

will generate of personal details of student and academic details of the students with the photos.

Using these module admin can able to perform add update and delete the details of students. In

this module contains student id, admission id, father’s name, mother’s name, hsc details such as

hsc mark registration id, last school studied. This module captures student profiles and optionally

automates student selection process.User is allowed to access advanced query options to view

student data and generate reports based on different criteria

 Staff Details:

In this staff details module deals with staff records. In this module admin can able to

maintain day to day staff records. Admin can able to add update and delete these details. It contain

staff id, staff name, educational qualifications, work experience details etc. using these module
admin can easily track the staff who are work in which department . User is allowed to access

advanced query options to view staff data and generate reports based on different criteria

Subject details:

In this subject module used for manage the details about subject details. Using this module

admin can able to add update delete the subject details. With the use of these subject module admin

can know which subject allocated to which department. These module can the details such as

subject id, subject name etc. The subject details form is designed for entering the different subject

available in the campus and other relevant details.

Course details:

It will retrieve the course and department information from the college such as department

name, department id etc. This module captures course details and optionally automates course

selection process. User is allowed to access advanced query options to view student data and

generate reports based on different criteria

Result details:

It will retrieve the result information from the examination database and assign mark to

the students. It will help the admin, staff to make the entry of mark allotted for particular student

in particular class. Using this result module admin and student can knows the students’

performance. It includes internal and external mark details. In this module the result status can be

automatically filled depends upon internal and external total. When total gets 40. And above

Automatically set result as pass. Otherwise it gets failed

SOFTWARE FEATURES

VISUAL BASIC.NET
Visual Baic.Net has revolutionized windows programming windows programming and
with an object based, event driven approach to software designs. Visual basic.Net applications act
as a front end to the database. Visual basic.Net application provides the interface between the user
and the database. Sophisticated features that make the language truly object oriented and interfaces
it with the latest in the database technology.

.NET provides a new, object-oriented API as a set of classes that will be accessible from
any programming language. This book describes this framework of classes and provides a
reference to what is available and how you can use this framework to write Windows applications
in the brave new world of .NET.

Microsoft .NET Framework is a computing platform for developing distributed applications

for the Internet. Following are the design goals of Microsoft .NET Framework:

1. To provide a very high degree of language interoperability

2. To provide a runtime environment that completely manages code execution
3. To provide a very simple software deployment and versioning model
4. To provide high-level code security through code access security and strong type checking
5. To provide a consistent object-oriented programming model
6. To facilitate application communication by using industry standards such as SOAP and
XML.
7. To simplify Web application development

Visual basic.net lets the user to add menus, text boxes, command buttons, option buttons,
check boxes, list boxes, scroll bars, and file directory boxes to blank windows. Visual basic.net
has many different tools.
The Common Language Runtime

The CLR is the mechanism through which .NET code is executed. It is built upon a single,
common language—IL—into which source languages are compiled and includes mechanisms for
executing the compiled code. This includes code verification and just-in-time (JIT) compilation,
garbage collection and enforcement of security policies, and the provision of profiling and
debugging services.

The CLR provides a lot of added value to the programs it supports. Because it controls how
a .NET program executes and sits between the program and the operating system, it can implement
security, versioning support, automatic memory management through garbage collection, and
provide transparent access to system services

IMPORTANT FEATURES:

 The application is a graphical user interface.

 Client-Server architecture benefits picture and image box can be easily
handled using bit mapped files and icons.
 Bit mapped files and icons are used as simple debugging tools.
 With the advent of .NET, Microsoft has introduced many new technologies
that make writing component-based distributed systems easier, more
flexible, and more powerful than ever before.
 It is now easier than it has ever been to write components in any
programming language that can interoperate with components on other
machines, which may not be Windows-based at all.
SQL SERVER 2005

The purpose of this document is to help you migrate your applications when you are migrating the

underlying database from Microsoft SQL Server to Some other Database. Most of the issues encountered

when migrating applications to use an Sql Server Database are related to database incompatibility. This

paper presents these incompatibilities and provides solutions for many issues.

You should familiarize yourself with this document prior to migrating your databases. The

choices made about how to migrate your application affect how you migrate the underlying

database from Microsoft SQL Server to some other Database.

If the application uses the Microsoft OLE DB Provider for SQL Server or a third-party

OLE DB Provider to connect the Microsoft SQL Server database, use the Sql Server Provider for

OLE DB (SQLOLEDB) to connect to the migrated Database.

SQL Server Security

Login Authentication.
Windows NT Authentication
SQL Server Authentication

Permissions validation on user database.

 T-SQL statements sent to SQL Server.
SQL server checks user permissions on receipt of T-SQL statements
FEATURES

 Created by Microsoft and Sybase in the 80s.

 Is SQL Compliant - Uses ANSI SQL

 Supports SQL – 92 standards - Uses T-SQL

 Stores data in a central location and delivers it to clients on request

 New Server Architecture

 Graphic Administration Tools

 Maintains ANSI standards and 6.x Compatibility

 Data integrity means reliability and accuracy of data.

 Integrity rules keep data consistent.

 Supports Client/Server model.

 Request response dialog.

 workload is split between the client and the server.

 Operating System compatibility.

 Runs on Win 95/98 NT, Netware, UNIX, OS/2, Appletalk, Banyan VINES.

 SQL Server must have Service Pack 4 (SP4) to run on Windows NT 4.0.

 Multiple protocol compatibility.

 SQL Server supports these protocols - Appletalk, TCP/IP.

 SMP Compatibility and Scalability

 Supports multiple processors. SMP leads to scalability.

SYSTEM STUDY
EXISTING SYSTEM:
The Existing system is a manual entry for the students. Here the result will be carried out in the
hand written registers. It will be a tedious job to maintain the record for the user. The human effort is more
here. The retrieval of the information is not as easy as the records are maintained in the hand written
registers. This application requires correct feed on input into the respective field. Suppose the wrong inputs
are entered, the application resist to work. So the user find it difficult to use.

• In existing system the institution follows manual procedure in which faculty should manually enters
all the details of the students.

• There is a chance of misplacing or loss of the records.

PROPOSED SYSTEM:
To overcome the drawbacks of the existing system, the proposed system has been evolved. This
project aims to reduce the paper work and saving time to generate accurate results from the student’s
attendance. The system provides with the best user interface. The efficient reports can be generated by using
this proposed system.

2.3.1 Advantages of Proposed System

• In this system, there is no loss of data due to student data are stored in the database.

• This application makes more flexible to access information.

• Every student academic performance is updated into database easily.

• It is trouble-free to use.
• It is a relatively fast approach to enter attendance
• Is highly reliable,
• approximate result from user
• Best user Interface
• Efficient reports
 CHAPTER-4

4.3 INPUT DESIGN

Input design is a part of overall design, which requires very careful attention. Input designs
are mainly concerned about designing user-friendly screens. The data should be validated in the
input phase itself. Therefore the screens are designed to enter the data. Messages are included for
the errors that occur during data entry.

The goal of designing input is to make data entry easier and to be free from error. These
forms collect the information needed for producing the report and store it in respective master
tables after data validation. Once the data is applicable for being appended into the master tables,
it can be used to produce acceptable outputs and stored for future verifications.

The main objective of the input design is to create input layout that is easy to follow and avoid
operator errors. Effective input design minimizes errors made by data entry operator. It also
provides record viewing facilities.
 ER DIAGRAM:

usernam
e password
Admin_I
Sub_Code
d
Tot Student_Id Dep_Id
a Admin
l Status
Ele_I Sub_Code
Subject
d Name

Result Subjects
Manag
e

DepName

year
Dep_I
d
Announ
ce Section
Batch

Department
Update

Ele_I
StudentE d
Addres mail Electiv
s e
Student_Id paper
Ins
Sem
Students
Elective
View Subject
TABLE DESIGN

Table name : admin

Primary key : admin_id

Description : This table is to store the admin login details.

Field Name Data Type Width Description

admin_id Varchar 10 The unique identification

username Varchar 25 User name or doctor name

password Varchar 25 Login Password
updation_date Date - Update date

Table name : tbldepartments

Primary key : dep_id

Description : This table is to store the departments details.

Field Name Data Type Width Description

dep_id Varchar 10 The unique identification

DepartmentName Varchar 25 Department Name

Bach_section Varchar 20 Bach section
DepartmentCode Date - Department Code
Table name : tblstudent

Primary key : sud_id

Description : This table is to store the departments details.

Field Name Data Type Width Description

sud_id Varchar 11 The unique identification

Name Varchar 25 Student Name

Rolla number Varchar 25 Roll number
EmailId Varchar 25 Emai Id
Password Varchar 10 Password
Gender Varchar 06 Gender
Dob Date - Dob
Bach_section Varchar 20 Bach section
proctor Text 50 Proctor
Tutor Varchar 15 Tutor
Phonenumber Int 13 Phone number

Table name : tblleaves

Primary key : lev_id

Description : This table is to store the departments details.

 Field Name Data Type Width Description
lev_id Varchar 10 The unique identification

LeaveType Varchar 25 Leave Type

ToDate Varchar 25 To Date
FromDate Date - From Date
Description Varchar 25 Description
PostingDate Date - Posting Date
AdminRemark Varchar 20 Admin Remark
AdminRemarkDate Date - Admin Remark Date
Status Varchar 02 Status
IsRead Varchar 20 Is Read
Sud_id Varchar 11 Student id

Table name : tblleavetype

Primary key : id

Description : This table is to store the departments details.

Field Name Data Type Width Description

id Varchar 10 The unique identification

LeaveType Varchar 25 Department Name

A. DATA FLOW DESIGN

CONTEXT LEVEL DIAGRAM:

Students
Manage
Result
Login managem Announcement
Admin
ent

Update

Result
LEVEL 1 DFD OF ADMIN:

Login
Admin
ID

Invalid Login ID Control Manage Students

panel /
View user list
Update /
alert view
report

Dep_db View /
Department manage

Sub_db
Subjects

ele_db
Elective subject

result_db
Result
LEVEL 2 DFD OF USER:

Login
Student
ID

Invalid Login ID Result View Students

panel
View user list
View

result_db View
Result
4.4 OUTPUT DESIGN

The ultimate goal of this project is to produce effective outputs. The output system is the vital part
and it plays an important role. It helps in decision making for the higher-level management. The
results have to be presented the user in understandable form with all user requirements.

 To ensure that during operation the system will perform as per specification.
 TO make sure that system meets the user requirements during operation
 To make sure that during the operation, incorrect input, processing and output will be
detected
 To see that when correct inputs are fed to the system the outputs are correct
 To verify that the controls incorporated in the same system as intended
 Testing is a process of executing a program with the intent of finding an error
 A good test case is one that has a high probability of finding an as yet undiscovered error

The software developed has been tested successfully using the following testing strategies and any
errors that are encountered are corrected and again the part of the program or the procedure or
function is put to testing until all the errors are removed. A successful test is one that uncovers an
as yet undiscovered error.