SYNOPSIS

STUDENT INFORMATION
SYSTEM

Submitted By:
Lokesh Kumar (0702033)
Chanchal Yadav (0702015)
 CERTIFICATE

This is to certify that the synopsis entitled “STUDENT

INFORMATION SYSTEM” done by Mr. Lokesh Kumar, enrollment No.:
0702033 is an authentic work carried out by him at GURGAON
COLLEGE OF ENGINEERING, GURGAON under my guidance.
The matter embodied in this project work has not been submitted
earlier for the award of any degree or diploma to the best of my
knowledge and belief.

Date: Signature of Guide

 CERTIFICATE

This is to certify that the synopsis entitled “STUDENT

INFORMATION SYSTEM” done by Chanchal Yadav, enrollment No.:
0702015 is an authentic work carried out by him at GURGAON
COLLEGE OF ENGINEERING, GURGAON under my guidance.
The matter embodied in this project work has not been submitted
earlier for the award of any degree or diploma to the best of my
knowledge and belief.

Date: Signature of Guide

 ACKNOWLEDGEMENT

The satisfaction that accompanies that the successful completion of any task
would be incomplete without the mention of people whose ceaseless
cooperation made it possible, whose constant guidance and encouragement
crown all efforts with success.

We are extremely thankful to project guide Mr. PARMOD (Lect. CSE Dept.)
for the guidance, inspiration and constructive suggestions that helpful us in the
preparation of this project.

We are also thankful to the faculty of Gurgaon College of Engineering for

providing us computer lab without which the dream of our project could never
have been fulfilled. The lab is well equipped with systems having latest
softwares and Technology required for the development of the project.

Last but not the least our friends who proved out to be the backbone of the
project creation. It has been a wonderful experience to have such a good
surrounding of people who have helped us at each and every step.
 Table of Content

1. ABSTRACT

2. INTRODUCTION
 SOFTWARE REQUIREMENT

 HARDWARE REQUIREMENT

 FEASIBILITY STUDY

3. SYSTEM ANALYSIS

4. DESIGN

5. REFRENCES
 ABSTRACT

A Student Information System is a system that is used to maintain the all records of
students and faculties also. By using this anyone, on the based of his or her privileges can
perform mainly these operation such that: find a record, update a record, add a record, delete
a record etc.

This system will be installed on a computer system and by using that computer system
user can use all the services provided by the Student Information System. Security is the
main issue for this system so there will be password protected access for every user and these
passwords will be stored in an encrypted form so an unauthenticated user can’t get these
passwords.

The Student Information System has been developed using .Net as the Front End
and Micro Soft SQL Server as the Back End. It follows the three tier architecture with C# for
coding and ADO.Net providing the classes for database connectivity.
 INTRODUCTION

ABOUT THE PROJECT

The project has been developed for our college (G.C.E) in an effort to make the
database of student and faculty accessible from a computer system and make the database
easily accessible

And make the database secure..

The working of the project is as follows.

The first form provides several links. By using these links user can get access to the
database after entering the user name and password and his privileges will be granted to his
according to his designation.

User Login module helps the user to login to the system. For that he must type the
username and password correctly. The login provision in this form is done by the site
Administration and helps the user to directly access the database.

Member Registration module helps the new user to get register into the system. The
information entered by the Administration is added into the table student.

SOFTWARE REQUIREMENTS

OPERATING SYSTEM: WINDOWS XP/VISTA/SEVEN

DATABASE LAYER: ADO.NET
IDE: VISUAL STIDIO 2005
DATABASE SERVER: MICROSOFT SQL SERVER 2005

HARWARE REQUIREMENTS

PROCESSOR: PENTIUM 4
CLOCK SPEED: 2 GHz
SYSTEM BUS: 32 Bit
RAM: 256 MB
HDD: 40 GB
MONITOR: SVGA COLOR
KEYBOARD: 108 KEYS
MOUSE: PS/2

FEASIBLITY STUDY

Steps in feasibility analysis

Eight steps are involved in the feasibility analysis. They are:

1. Form a project team and appoint a project leader.

2. Prepare system flowcharts.
3. Enumerate potential proposed systems.
4. Define and identify characteristics of proposed system.
5. Determine and evaluate performance and cost effectiveness of each
proposed system.
6. Weight system performance and cost data.
7. Select the best proposed system.
8. Prepare and report final project directive to management

Type of feasibilities

1. Economic Feasibility

Economic analysis is the most frequently used technique for evaluating the
effectiveness of a proposed system. More commonly known as cost / benefit
analysis; in this procedure we determine the benefits and savings that are
expected from a proposed system and compare them with costs. We found the
benefits outweigh the costs; we take a decision to design and implement the
new proposed system.

2. Technical Feasibility

This is concerned with specifying equipment and software that will successfully
satisfy the user requirement. The technical needs of the system may vary
considerably, but might include:
· The facility to produce outputs in a given time.
· Response time under certain conditions.
· Ability to process a certain volume of transaction at a particular speed.
· Facility to communicate data to distant location.

After examining technical feasibility, we give more importance to the

configuration of the system than the actual make of hardware. The configuration
gives the complete picture about the system's requirements: Ten to twelve
workstations are required, these units should be interconnected through LAN so
that they could operate and communicate smoothly. They should have enough
speeds of input and output to achieve a particular quality of printing.

3. Operational Feasibility

It is mainly related to human organizational and political aspects. The points to

be considered are:

· what changes will be brought with the system?

· what organizational structures are disturbed?

· what new skills will be required? Do the existing staff members have these
skills?

· If not, can they be trained in due course of time?

Generally project will not be rejected simply because of operational infeasibility

but such considerations are likely to critically affect the nature and scope of the
eventual recommendations.

For operational feasibility study we appointed a small group of people who are
familiar with information system techniques, who understand the parts of the
business that are relevant to the project and are skilled in system analysis and
design process.

4. Social feasibility

Social feasibility is a determination of whether a proposed project will be

acceptable to the people or not. This determination typically examines the
probability of the project being accepted by the group directly affected by the
proposed system change.

5. Management feasibility

It is a determination of whether a proposed project will be acceptable to

management. If management does not accept a project or gives a negligible
support to it, the analyst will tend to view the project as a non-feasible one.
6. Legal feasibility

Legal feasibility is a determination of whether a proposed project infringes on

known Acts, Statutes, as well as any pending legislation. Although in some
instances the project might appear sound, on closer investigation it may be
found to infringe on several legal areas.

7. Time feasibility

Time feasibility is a determination of whether a proposed project can be

implemented fully within a stipulated time frame. If a project takes too much
time it is likely to be rejected
 SYSTEM ANALYSIS

2.1INTRODUCTION

System analysis is the process of gathering and interpreting facts,

diagnosing problems and using the information to recommend improvements on
the system. System analysis is a problem solving activity that requires intensive
communication between the system users and system developers.

System analysis or study is an important phase of any system

development process. The system is studied to the minutest detail and analyzed.
The system analyst plays the role of an interrogator and dwells deep into the
working of the present system. The system is viewed as a whole and the inputs
to the system are identified. The outputs from the organization are traced
through the various processing that the inputs phase through in the organization.

A detailed study of these processes must be made by various techniques

like Interviews, Questionnaires etc. The data collected by these sources must be
scrutinized to arrive to a conclusion. The conclusion is an understanding of how
the system functions. This system is called the existing system. Now, the
existing system is subjected to close study and the problem areas are identified.
The designer now functions as a problem solver and tries to sort out the
difficulties that the enterprise faces. The solutions are given as a proposal. The
proposal is then weighed with the existing system analytically and the best one
is selected. The proposal is presented to the user for an endorsement by the user.
The proposal is reviewed on user request and suitable changes are made. This
loop ends as soon as the user is satisfied with the proposal.
 E-R Diagram

Roll No.

Student

Address

Name
Branch

Father’s Sem
Name Administrator E-R Diagram:

Password

Other Details
Contact No.

User name password

administrator
 DESIGN

System Design Considerations

The system design process is not a step-by-step adherence of clear procedures and guidelines.
Though, certain clear procedures and guidelines have emerged in recent days, but still much
of design work depends on knowledge and experience of the designer.

When designer starts working on system design, he will face different type of problems.
Many of these will be due to constraints imposed by the user or limitations of the hardware
and software available in the market. Sometimes, it is difficult to enumerate the complexity
of the problems and solutions thereof since the variety of likely problems is so great and no
solutions are exactly similar. However, following considerations should be kept in mind
during the system-designing phase:

The primary objective of the design : Of course, is to deliver the requirements as

specified in the feasibility report. In general, the following design objectives should be kept
in mind:

a. Practicality: The system must be stable and can be operated by people with average +

b. Efficiency: This involves accuracy, timeliness and comprehensiveness of the system

output.

c. Cost: it is desirable to aim for a system with a minimum cost subject to the condition that
it must satisfy all the requirements.

d. Flexibility: The system should be modifiable depending on the changing needs of the
user. Such modifications should not entail
Student Tables

Table Name :- student

Primary Key:- rollno

Field Data Type Allow Null

Roll No. Bigint no
Name Varchar(50) no
Branch Varchar(50) no
Sem Varchar(50) no
Contact No. Bigint yes
Father’s Name Varchar(50) no
Address Varchar(max) no
Other Details Varchar(max) yes
Password Varchar(50) no

Administrator Table

Table Name :- admin

Primary Key;- user_name

Field Data Type Allow Null

User Name Varchar(50) no
Password Varchar(50) no

Data Flow Diagram:-

Student

login

Validation Invalid

View student
record

DFD for student login

 References:
 .NET programming Language – SL 275-- SUN MICROSYSTEMS
 􀂾 The Complete Reference To .NET –ROX Publication

Internet links:-
http://.NET.sun.com/docs/books/tutorial/
http://www.NET.com/Tutorial/.NET/Catalog.NET.htm