This document describes a student management system project report submitted by four students to fulfill the requirements for a Bachelor of Technology degree. The project aims to develop a computerized student management system to handle all details related to students, academics, exams and generate various reports. It discusses the various modules of the system - college and department details, login and subjects, student details, exam details. It also provides details of the tables used to store information in each module and screenshots of the proposed system.

1. STUDENT MANAGEMENT SYSTEM
PROJECT REPORT
Submitted by
FALCON FRANCIS
MANJU V RAVINDRAN
RANJITH KIRAN K
VINU K THANKACHAN
in partial fulfillment for the award of the degree
of
BACHELOR OF TECHNOLOGY
in
COMPUTER SCIENCE AND ENGINEERING
SREE NARAYANA GURUKULAM COLLEGE OF ENGINEERING
KADAYIRUPPU KOLENCHERY 682311
MAHATMA GANDHI UNIVERSITY: KOTTAYAM 686580
AUGUST 2007

2. SREE NARAYANA GURUKULAM COLLEGE OF ENGINEERING,
KOLENCHERY
CERTIFICATE
Certified that this project report “STUDENT MANAGEMENT SYSTEM” is
the bonafide work done by “FALCON FRANCIS, MANJU V RAVINDRAN,
RANJTH KIRAN K, VINU K THANKACHAN” in partial fulfillment of
award of B.Tech Degree in “COMPUTER SCIENCE AND ENGINEERING”.
Saini Jacob Soman Parvathy Jyothy, Lecturer, CSE
HEAD OF THE DEPARTMENT GUIDE
Submitted for the Viva-Voce examination on …………………………………….
Name and Signature of Name and signature of
Internal Examiner External Examiner

3. TABLE OF CONTENTS
CHAPTER TITLE PAGE NO
ACKNOWLEDGEMENT i
ABSTRACT ii
LIST OF TABLES iii
LIST OF FIGURES iv
1. INTRODUCTION 1
2. MODULES 2
3. SYSTEM STUDY 10
3.1 STUDY OF EXISTING SYSTEM 10
3.2 STUDY OF PROPOSED SYSTEM 10
3.3 INTRODUCTION TO .NET 10
3.3.1 ADVANTAGES OF .NET 11
3.3.1.1 Consistent programming model 11
3.3.1.2 Direct support for security 12
3.3.1.3 Simplified development efforts 12
3.3.1.4 Easy application deployment and maintenance 13
3.3.2 .NET FRAME WORK 13
3.4 INTRODUCTION TO SQL SERVER 2005 15
4 SYSTEM ANALYSIS 16
4.1 FEASIBILITY STUDY 16
4.1.1 Operation Feasibility 16
4.1.2 Technical Feasibility 16
4.1.3 Economic Feasibility 17
5 SYSTEM SPECIFICATION 18
5.1 HARDWARE REQUIREMENTS 18
5.2 SOFTWARE REQUIREMENTS 18
5.3 LANGUAGES USED 18

4. 6 SYSTEM DESIGN 20
6.1 LOGICAL DESIGN 20
6.2 INPUT DESIGN 21
6.3 OUTPUT DESIGN 21
6.4 PHYSICAL DESIGN 22
6.5 MODULAR DESIGN 22
6.6 DATABASE DESIGN 23
6.6.1 Normalization 24
7 CODING 25
8 SYSTEM TESTING AND IMPLEMENTATION 26
8.1 SYSTEM TESTING 26
8.1.1 Unit testing 27
8.1.2 Module level testing 28
8.1.3 Integration & system testing 28
8.1.4 Regression testing 28
8.2 SYSTEM IMPLEMENTATION 28
8.2.1 Implementation methods 28
8.2.2 Implementation plan 29
9 FIGURES 30
9.1 DATA FLOW DIAGRAM 30
9.2 SCREEN SHOTS 32
10 CONCLUSION 45
RESUME 46
REFERENCES 47

5. ACKNOWLEDGEMENT
First of all we thank Almighty for all His blessings .Our sincere thanks to Principal Prof.
K Rajendran for supporting in all our activities. We like to express our sincere thanks to management of
SNGCE.
Our sincere thanks to Mr Sainy Jacob Soman, Assistant Professor of Computer Science department
SNGCE, for granting his kind consents for carrying out our suggested project. Our sincere thanks to Ms
Parvathy Jyothy as our guide and provided all the required guidance in the project.
We would like to express our heartily gratitude to all teachers and staff’s of SNGCE for their
cooperation and help to complete our project.
We extend our deep sense of gratitude to our Lecturers of Computer Science and Engineering
Department for their valuable guidance as well as timely advice, which helped us a lot in completing the
project successfully. Finally I would like to express my gratitude to Sree Narayana Gurukulam College of
Engineering for providing me with all the required facilities without which the project would not have been
possible. Last but not least we thank our all friends for their moral support and encouragement.
i

6. ABSTRACT
Student Management System deals with all kind of student details, academic related reports, college
details, course details, curriculum, batch details and other resource related details too. It tracks all the details
of a student from the day one to the end of his course which can be used for all reporting purpose, tracking of
attendance, progress in the course, completed semesters years, coming semester year curriculum details, exam
details, project or any other assignment details, final exam result; and all these will be available for future
references too.
Our program will have the databases of Courses offered by the college under all levels of graduation
or main streams, teacher or faculty’s details, batch execution details, students’ details in all aspects.
This program can facilitate us explore all the activities happening in the college, even we can get to
know which teacher / faculty is assigned to which batch, the current status of a batch, attendance percentage
of a batch and upcoming requirements of a batch.
Different reports and Queries can be generated based of vast options related to students, batch, course,
teacher / faculty, exams, semesters, certification and even for the entire college.

7. ii
LIST OF TABLES
TABLE PAGE NUMBER
SMS_College 2
SMS_Category 3
SMS_Login 3
SMS_Sub 3
SMS_Studacademic 5
SMS_Studpersonal 5
SMS_Examdetail 8
SMS_Finalreport 8
SMS_Studparti 9
iii

8. LIST OF FIGURES
NAME OF FIGURES PAGE NUMBER
LEVEL 1 DFD 31
LEVEL 2 DFD 31
COLLEGE DETAILS 32
DEPARTMENT DETAILS 33
SIGNUP DETAILS 34
SIGNIN DETAILS 35
CHANGE PASSWORD 36
SUBJECT DETAILS 37
PERSONAL DETAILS 38
PARENT DETAILS 39
ACADEMIC DETAILS 40
EXAM DETAILS 41
STUDENT PARTICULARS 43
FINAL REPORT 44
iv

9. CHAPTER 1
INTRODUCTION
About the project
The student management system is an automated version of manual Student Management System. It
can handle all details about a student. The details include college details, subject details, student personnel
details, academic details, exam details etc...
In case of manual system they need a lot of time, manpower etc…Here almost all work is
computerized. So the accuracy is maintained. Maintaining backup is very easy. It can do with in a few
minutes. Our system has two type of accessing modes, administrator and user. Student management system is
managed by an administrator. It is the job of the administrator to insert update and monitor the whole process.
When a user log in to the system. He would only view details of the student. He can’t perform any changes
.The system has four modules. They are
 College and Department details
 Login and subject
 Student Details
 Exam Details

10. CHAPTER 2
MODULES
Student Management System is expected to maintain a number of details. The needed modules are
given below.
 College and Department details
This module deals with the college details and different departments in the college. The college
details are stored in the table SMS_College. And department details are stored in SMS_Category. It deals with
the details of college and department.
TABLE: SMS_College
Field Type Constraints
SMS_Coll_Collegeid varchar(50) Not Null
SMS_Coll_Collegename varchar(300) Not Null
SMS_Coll_Address varchar(300) Not Null
SMS_Coll_Pincode varchar(50) Not Null
SMS_Coll_District varchar(50) Not Null
SMS_Coll_State varchar(50) Not Null
SMS_Coll_Phone1 varchar(50) Not Null
SMS_Coll_Phone2 varchar(50) Not Null
SMS_Coll_Fax varchar(50) Not Null
SMS_Coll_Email varchar(100) Not Null
SMS_Coll_Website varchar(100) Not Null
SMS_Coll_Emblem varchar(100) Not Null
This table is used to store the details of college like college name, address, phone numbers, fax, e-
mail id, website. This table is filled at first.

11. TABLE: SMS_Categoryl
Field Type Constraints
SMS_Cat_Catagory varchar(50) Not Null
SMS_Cat_Department varchar(50) Not Null
SMS_Cat_Duration int Not Null
This table is used to store the details of different department and its category. Category specifies the
course is bachelor or master degree. Department gives the various departments. Duration specifies the number
of semesters.
 Login and subject
This module based with the login process and subject details. The login process specifies the
user mode such as administrator or user. This module consist of two tables, SMS_Login and SMS_Sub . It
contains the details of login process and subject details. Login process includes sign in sign up, sign out,
change password.
TABLE: SMS_Login
Field Type Constraints
SMS_Log_Category varchar(50) Not Null
SMS_Log_Department varchar(50) Not Null
SMS_Log_Username varchar(20) Not Null
SMS_Log_Password varchar(20) Not Null
SMS_Log_Privilege varchar(20) Not Null
The table stores the values like category, department, username, password and privilege. The privilege
specifies the user mode is administrator or user.
TABLE: SMS_Sub
Field Type Constraints
SMS_Sub_Category varchar(50) Not Null
SMS_Sub_Department varchar(50) Not Null

12. SMS_Sub_Semester varchar(50) Not Null
SMS_Sub_Noofsubjects int Not Null
SMS_Sub_Sub1 varchar(50)
SMS_Sub_Code1 varchar(50)
SMS_Sub_Sub2 varchar(50)
SMS_Sub_Code2 varchar(50)
SMS_Sub_Sub3 varchar(50)
SMS_Sub_Code3 varchar(50)
SMS_Sub_Sub4 varchar(50)
SMS_Sub_Code4 varchar(50)
SMS_Sub_Sub5 varchar(50)
SMS_Sub_Code5 varchar(50)
SMS_Sub_Sub6 varchar(50)
SMS_Sub_Code6 varchar(50)
SMS_Sub_Sub7 varchar(50)
SMS_Sub_Code7 varchar(50)
SMS_Sub_Sub8 varchar(50)
SMS_Sub_Code8 varchar(50)
SMS_Sub_Sub9 varchar(50)
SMS_Sub_Code9 varchar(50)
SMS_Sub_Sub10 varchar(50)
SMS_Sub_Code10 varchar(50)
SMS_Sub_Sub11 varchar(50)
SMS_Sub_Code11 varchar(50)
SMS_Sub_Sub12 varchar(50)
SMS_Sub_Code12 varchar(50)
This table shows the details of the category, department, semester, and number of subjects in semester
and different subjects in various department and semesters.

13.  Student Details
This module deals with the student academic details and personnel details.
This module consists of the tables SMS_Studacademic and SMS_Studpersonal.
TABLE: SMS_Studacademic
Field Type Constraints
SMS_Studaca_Admino varchar(50) Not Null
SMS_Studaca_Batch varchar(50) Not Null
SMS_Studaca_Category varchar(50) Not Null
SMS_Studaca_Department varchar(50) Not Null
SMS_Studaca_Sem varchar(50) Not Null
SMS_Studaca_Name varchar(50) Not Null
SMS_Studaca_Edulquali1 varchar(50)
SMS_Studaca_Percentage1 float
SMS_Studaca_Edulquali2 varchar(50)
SMS_Studaca_Percentage2 float
SMS_Studaca_Entrancerank varchar(50)
SMS_Studaca_Photo varchar(50)
This table shows the values like admission number, batch, category, department, joining semester,
his/her name, their qualifications, entrance rank and photo.
TABLE: SMS_Studpersonal
Field Type Constraints
SMS_Studaca_Admino varchar(50) Not Null
SMS_Studper_Dob varchar(50)
SMS_Studper_Religion varchar(50)
SMS_Studper_Caste varchar(50)
SMS_Studper_Gender varchar(50)
SMS_Studper_Bloodgroup varchar(50)

14. SMS_Studper_Dayscholororhostler varchar(50)
SMS_Studper_Studentemail varchar(50)
SMS_Studper_Temadd varchar(200)
SMS_Studper_Temphone1 varchar(50)
SMS_Studper_Peradd varchar(200)
SMS_Studper_Perphone1 varchar(50)
SMS_Studper_Fathername varchar(50)
SMS_Studper_Fatheraddress varchar(200)
SMS_Studper_Fatherphone varchar(50)
SMS_Studper_Fatherjob varchar(50)
SMS_Studper_Foffadd varchar(200)
SMS_Studper_Foffphone varchar(50)
SMS_Studper_Mothername varchar(50)
SMS_Studper_Motheraddress varchar(200)
SMS_Studper_Motherphone varchar(50)
SMS_Studper_Motherjob varchar(50)
SMS_Studper_Moffadd varchar(200)
SMS_Studper_Moffphone varchar(50)
SMS_Studper_Annualincome varchar(50)
This table stores the admission number, the personnel details like date of birth, religion, cast, gender,
blood group, day scholar or hosteller, e-mail, address, parent details and annual income.
 Exam Details
This module deals with the student exam details, student particular such as various activities,
final report. The tables comes in this modules are SMS_Examdetail, SMS_Finalreport and SMS_Studparti.
TABLE: SMS_Examdetail
Field Type Constraints
SMS_Exam_Studcode varchar(50) Not Null
SMS_Exam_Regno varchar(50)

15. SMS_Exam_Sem varchar(50)
SMS_Exam_Monthandyear varchar(50)
SMS_Exam_Internalmax varchar(50)
SMS_Exam_Externalmax varchar(50)
SMS_Exam_Externalminimum varchar(50)
SMS_Exam_Total varchar(50)
SMS_Exam_Passout varchar(50)
SMS_Exam_Sub1 varchar(50)
SMS_Exam_Emark1 varchar(50)
SMS_Exam_Imark1 varchar(50)
SMS_Exam_Total1 varchar(50)
SMS_Exam_Sub2 varchar(50)
SMS_Exam_Emark2 varchar(50)
SMS_Exam_Imark2 varchar(50)
SMS_Exam_Total2 varchar(50)
SMS_Exam_Sub3 varchar(50)
SMS_Exam_Emark3 varchar(50)
SMS_Exam_Imark3 varchar(50)
SMS_Exam_Total3 varchar(50)
SMS_Exam_Sub4 varchar(50)
SMS_Exam_Emark4 varchar(50)
SMS_Exam_Imark4 varchar(50)
SMS_Exam_Total4 varchar(50)
SMS_Exam_Sub5 varchar(50)
SMS_Exam_Emark5 varchar(50)
SMS_Exam_Imark5 varchar(50)
SMS_Exam_Total5 varchar(50)
SMS_Exam_Sub6 varchar(50)
SMS_Exam_Emark6 varchar(50)
SMS_Exam_Imark6 varchar(50)

16. SMS_Exam_Total6 varchar(50)
SMS_Exam_Sub7 varchar(50)
SMS_Exam_Emark7 varchar(50)
SMS_Exam_Imark7 varchar(50)
SMS_Exam_Total7 varchar(50)
SMS_Exam_Sub8 varchar(50)
SMS_Exam_Emark8 varchar(50)
SMS_Exam_Imark8 varchar(50)
SMS_Exam_Total8 varchar(50)
SMS_Exam_Sub9 varchar(50)
SMS_Exam_Emark9 varchar(50)
SMS_Exam_Imark9 varchar(50)
SMS_Exam_Total9 varchar(50)
SMS_Exam_Sub10 varchar(50)
SMS_Exam_Emark10 varchar(50)
SMS_Exam_Imark10 varchar(50)
SMS_Exam_Total10 varchar(50)
SMS_Exam_Sub11 varchar(50)
SMS_Exam_Emark11 varchar(50)
SMS_Exam_Imark11 varchar(50)
SMS_Exam_Total11 varchar(50)
SMS_Exam_Sub12 varchar(50)
SMS_Exam_Emark12 varchar(50)
SMS_Exam_Imark12 varchar(50)
SMS_Exam_Total12 varchar(50)
This table stores the values stud code, register number, semester, month and year of exam, internal and
external maximum marks, the marks obtained for various subjects like its internal, external and total mark.
This table gives the performance of students in various exams.
TABLE: SMS_Finalreport

17. Field Type Constraints
SMS_Final_Adminno varchar(50) Not Null
SMS_Final_Miniprojectworkdone varchar(MAX)
SMS_Final_Mainprojectworkdone varchar(MAX)
SMS_Final_Techinicalactivity varchar(50)
SMS_Final_Neatness varchar(50)
SMS_Final_Characterandconduct varchar(50)
SMS_Final_Remarks varchar(50)
This table stores the values of admission number, mini project done, main project done, technical
activities, neatness and standard of lab record, character and conduct and remarks.
TABLE: SMS_Studparti
Field Type Constraints
SMS_Studaca_Admino varchar(50) Not Null
SMS_Studparti_sem varchar(50) Not Null
SMS_Studparti_arts varchar(50)
SMS_Studparti_athletics varchar(50)
SMS_Studparti_games varchar(50)
SMS_Studparti_scholarship varchar(50)
SMS_Studparti_disaction varchar(50)
SMS_Studparti_coursestar varchar(50)
SMS_Studparti_tutor varchar(50)
This table stores the values of extra curricular details, admission number , scholarship, disciplinary
action , starting of course, tutor.

18. CHAPTER 3
SYSTEM STUDY
System study aims at establishing requests for the system to be acquired, developed and installed. It
involves studying and analyzing the ways of an organization currently processing the data to produce
information. Analyzing the problem thoroughly forms the vital part of the system study. In system analysis,
prevailing situation of problem carefully examined by breaking them into sub problems. Problematic areas are
identified and information is collected. Data gathering is essential to any analysis of requests. It is necessary
that this analysis familiarizes the designer with objectives, activities and the function of the organization in
which the system is to be implemented.
3.1 STUDY OF EXISTING SYSTEM
Today in colleges student details are entered manually. The student details in separate records are
tedious task. Referring to all these records and updating is needed. There is a chance for more manual errors.
3.2 PROPOSED SYSTEM
By developing the system we can attain the following facilities.
 Easy to handle and feasible.
 Cost reduction.
 Fast and convenient.
3.3 INTRODUCTION TO .NET
This proposed software is going to be developed using the latest technology from Microsoft called
Microsoft. NET and it is the software that connects information, people, systems, and devices. It spans clients,
servers, and developer tools, and consists of:
• The .NET Framework 1.1, used for building and running all kinds of software, including Web-based
applications, smart client applications, and XML Web services—components that facilitate integration
by sharing data and functionality over a network through standard, platform-independent protocols
such as XML (Extensible Markup Language), SOAP, and HTTP.
• Developer tools, such as Microsoft Visual Studio.NET 2003, which provides an integrated

19. development environment (IDE) for maximizing developer productivity with the .NET Framework.
• A set of servers, including Microsoft Windows Server 2003, Microsoft SQL Server, and Microsoft
BizTalk Server, that integrates, runs, operates, and manages Web services and Web-based
applications.
Client software, such as Windows XP, Windows CE, and Microsoft Office XP, that helps developers
deliver a deep and compelling user experience across a family of devices and existing products
3.3.1 ADVANTAGES OF .NET
The .NET Framework offers a number of advantages to developers. The following paragraphs describe
them in detail.
3.3.1.1 Consistent programming model
Different programming languages have different approaches for doing a task. For example, accessing
data with a VB 6.0 application and a VC++ application is totally different. When using different programming
languages to do a task, a disparity exists among the approach developers use to perform the task. The
difference in techniques comes from how different languages interact with the underlying system that
applications rely on.
With .NET, for example, accessing data with a VB .NET and a C# .NET looks very similar apart from
slight syntactical differences. Both the programs need to import the System. Data namespace, both the
programs establish a connection with the database and both the programs run a query and display the data on a
data grid. The VB 6.0 and VC++ example mentioned in the first paragraph explains that there is more than
one way to do a particular task within the same language. The .NET example explains that there's a unified
means of accomplishing the same task by using the .NET Class Library, a key component of the .NET
Framework.
The functionality that the .NET Class Library provides is available to all .NET languages resulting in a
consistent object model regardless of the programming language the developer uses.
3.3.1.2 Direct support for security

20. Developing an application that resides on a local machine and uses local resources is easy. In this
scenario, security isn't an issue as all the resources are available and accessed locally. Consider an application
that accesses data on a remote machine or has to perform a privileged task on behalf of a nonprivileged user.
In this scenario security is much more important as the application is accessing data from a remote machine.
With .NET, the Framework enables the developer and the system administrator to specify method
level security. It uses industry-standard protocols such as TCP/IP, XML, SOAP and HTTP to facilitate
distributed application communications. This makes distributed computing more secure because .NET
developers cooperate with network security devices instead of working around their security limitations.
3.3.1.3 Simplified development efforts
Let's take a look at this with Web applications. With classic ASP, when a developer needs to present
data from a database in a Web page, he is required to write the application logic (code) and presentation logic
(design) in the same file. He was required to mix the ASP code with the HTML code to get the desired result.
ASP.NET and the .NET Framework simplify development by separating the application logic and
presentation logic making it easier to maintain the code. You write the design code (presentation logic) and
the actual code (application logic) separately eliminating the need to mix HTML code with ASP code.
ASP.NET can also handle the details of maintaining the state of the controls, such as contents in a textbox,
between calls to the same ASP.NET page.
Another advantage of creating applications is debugging. Visual Studio .NET and other third party
providers provide several debugging tools that simplify application development. The .NET Framework
simplifies debugging with support for Runtime diagnostics. Runtime diagnostics helps you to track down bugs
and also helps you to determine how well an application performs. The .NET Framework provides three types
of Runtime diagnostics: Event Logging, Performance Counters and tracing.
3.3.1.4 Easy application deployment and maintenance
The .NET Framework makes it easy to deploy applications. In the most common form, to install an
application, all you need to do is copy the application along with the components it requires into a directory
on the target computer. The .NET Framework handles the details of locating and loading the components an
application needs, even if several versions of the same application exist on the target computer. The .NET

21. Framework ensures that all the components the application depends on are available on the computer before
the application begins to execute.
3.3.2 .NET FRAMEWORK
The Microsoft .NET Framework is a software component that can be added to or is included with the
Microsoft Windows operating system. It provides a large body of pre-coded solutions to common program
requirements, and manages the execution of programs written specifically for the framework. The .NET
Framework is a key Microsoft offering, and is intended to be used by most new applications created for the
Windows platform.
The pre-coded solutions that form the framework's class library cover a large range of programming
needs in areas including: user interface, data access, database connectivity, cryptography, web application
development, numeric algorithms, and network communications. The functions of the class library are used
by programmers who combine them with their own code to produce applications.
Programs written for the .NET Framework execute in a software environment that manages the
program's runtime requirements. This runtime environment, which is also a part of the .NET Framework, is
known as the Common Language Runtime (CLR). The CLR provides the appearance of an application virtual
machine, so that programmers need not consider the capabilities of the specific CPU that will execute the
program. The CLR also provides other important services such as security mechanisms, memory
management, and exception handling. The class library and the CLR together compose the .NET Framework.
The framework is intended to make it easier to develop computer applications and to reduce the vulnerability
of applications and computers to security threats.
First released in 2002, it is included with Windows XP SP2, Windows Server 2003 and Windows
Vista, and can be installed on most older versions of Windows.
Microsoft .NET Framework was designed with several intentions:
• Interoperability - Because interaction between new and older applications is commonly
required, the .NET Framework provides means to access functionality that is implemented in programs that
execute outside the .NET environment. Access to COM components is provided in the
System.Runtime.InteropServices and System.EnterpriseServices namespaces of the framework, and access to
other functionality is provided using the P/Invoke feature.

22. • Common Runtime Engine - Programming languages on the .NET Framework compile into an
intermediate language known as the Common Intermediate Language, or CIL (formerly known as Microsoft
Intermediate Language, or MSIL). In Microsoft's implementation, this intermediate language is not
interpreted, but rather compiled in a manner known as just-in-time compilation (JIT) into native code. The
combination of these concepts is called the Common Language Infrastructure (CLI), a specification;
Microsoft's implementation of the CLI is known as the Common Language Runtime (CLR).
• Language Independence - The .NET Framework introduces a Common Type System, or CTS.
The CTS specification defines all possible data types and programming constructs supported by the CLR and
how they may or may not interact with each other. Because of this feature, the .NET Framework supports
development in multiple programming languages. This is discussed in more detail in the .NET languages
section below.
• Base Class Library - The Base Class Library (BCL), sometimes referred to as the Framework
Class Library (FCL), is a library of types available to all languages using the .NET Framework. The BCL
provides classes which encapsulate a number of common functions, including file reading and writing,
graphic rendering, database interaction and XML document manipulation.
• Simplified Deployment - Installation of computer software must be carefully managed to
ensure that it does not interfere with previously installed software, and that it conforms to increasingly
stringent security requirements. The .NET framework includes design features and tools that help address
these requirements.
• Security - .NET allows for code to be run with different trust levels without the use of a
separate sandbox.
A design goal of the .NET Framework was to support platform independence[citation needed]. That is,
a program written to use the framework should run without change on any type of computer for which the
framework is implemented. However, Microsoft has only implemented the full .NET framework on the
Windows operating system. Microsoft and others have implemented portions of the framework on non-
Windows systems, but to date these implementations are neither complete nor widely used, so full cross-
platform support has not been achieved.
3.4 INTRODUCTION TO SQL SERVER 2005
Microsoft SQL Server 2005 is comprehensive, integrated data management and analysis software that
enables organizations to reliably manage mission-critical information and confidently run today’s increasingly

23. complex business applications. SQL Server 2005 allows companies to gain greater insight from their business
information and achieve faster results for a competitive advantage.
SQL Server 2005 is the Data Platform leader:
• SQL Server is the fastest growing Database and Business Intelligence vendor.
• SQL Server ships more units than Oracle and IBM combined.
• SQL Server is the #1 OLAP Server on the market.
• SQL Server is more secure than Oracle. Since July 2003 more than 100 critical Oracle database
security vulnerabilities have been identified, compared to ZERO for SQL Server for that period.
• SQL Server is a benchmark leader, with the best price/performance for TPC-H 1TB & 3TB
(non-clustered) as well as best performance for TPC-H 1TB.
• Gartner 2006 worldwide RDBMS market share reports highest growth rate in market share for
Microsoft SQL Server. With 28% growth in market share, growth is almost twice the nearest competitor at
14.8% growth.
• SQL Server Manages the World's Largest Databases

24. CHAPTER 4
SYSTEM ANALYSIS
The primary goal of the system analyst is to improve the efficiency of the existing system. For that
the study of specification of the requirements is very essential. For the development of the new system, a
preliminary survey of the existing system will be conducted. Investigation done whether the upgradation of
the system into an application program could solve the problems and eradicate the inefficiency of the
existing system.
4.1 FEASIBILITY STUDY
The initial investigation points to the question whether the project is feasible. A feasibility is
conducted to identify the best system that meets the all the requirements. This includes an identification
description, an valuation of the proposed systems and selection of the best system for the job. The
requirements of the system are specified with a set of constraints such as system objectives and the
description of the out puts. It is then duty of the analyst to evaluate the feasibility of the proposed system to
generate the above results. Three key factors are to be considered during the feasibility study.
4.1.1 Operation Feasibility
An estimate should be made to determine how much effort and care will go into the developing of
the system including the training to be given to the user. Usually, people are reluctant to changes that come
in their progression. The computer initialization will certainly affected the turn over, transfer and employee
job status. Hence an additional effort is to be made to train and educate the users on the new way of the
system.
4.1.2 Technical Feasibility
The main consideration is to be given to the study of available resources of the organization where
the software is to be implemented. Here the system analyst evaluates the technical merits of the system
giving emphasis on the performance, Reliability, maintainability and productivity.

25. By taking the consideration before developing the proposed system, the resources availability of the
organization was studied. The organization was immense computer facilities equipped with sophisticated
machines and the software hence this technically feasible.
4.1.3 Economic Feasibility
Economic feasibility is the most important and frequently used method for evaluating the
effectiveness of the proposed system. It is very essential because the main goal of the proposed system is to
have economically better result along with increased efficiency. Cost benefit analysis is usually performed
for this purpose. It is the comparative study of the cost verses the benefit and savings that are expected from
the proposed system. Since the organization is well equipped with the required hard ware, the project was
found to be economically.

26. CHAPTER 5
SYSTEM SPECIFICATION
5.1 HARDWARE REQUIREMENTS
Processor : Pentium IV
Ram : 512 MB RAM
Hard Disk : 80 GB Hard disk
5.2 SOFTWARE REQUIREMENTS
Operating System : Microsoft XP/VISTA/2003 server
Platform : Visual Studio 2005
Database : Microsoft SQL Server 2005
Application Software : Microsoft Office 2003
5.3 SOFTWARE FEATUERS
5.3.1 LANGUAGES USED: C#
Visual C# .Net is designed to be a fast and easy way to create .NET applications, including Web services and
ASP.NET Web applications. Applications written in Visual C# are built on the services of the common language
runtime and take full advantage of the .NET Framework.
It is a simple, elegant, type-safe, object-oriented language recently developed by Microsoft for
building a wide range of applications. Anyone familiar with C and similar languages will find few problems
in adapting to C#. C# is designed to bring rapid development to the C++ programmer without sacrificing the
power and control that are a hallmark of C and C++. Because of this heritage, C# has a high degree of fidelity
with C and C++, and developers familiar with these languages can quickly become productive in C#. C#
provides intrinsic code trust mechanisms for a high level of security, garbage collection, and type safety. C#
supports single inheritance and creates Microsoft intermediate language (MSIL) as input to native code
compilers.
It is fully integrated with the .NET Framework and the common language runtime, which together
provide language interoperability, garbage collection, enhanced security, and improved versioning support.
C# simplifies and modernizes some of the more complex aspects of C and C++, notably namespaces, classes,

27. enumerations, overloading, and structured exception handling. C# also eliminates C and C++ features such as
macros, multiple inheritance, and virtual base classes. For current C++ developers, C# provides a powerful,
high-productivity language alternative.
Visual C# provides prototypes of some common project types, including:
• Windows Application.
• Class Library.
• Windows Control Library.
• ASP.NET Web Application.
• ASP.NET Web Service.
• Web Control Library.
• Console Application.
• Windows Service.

28. CHAPTER 6
SYSTEM DESIGN
System design is the solution to the creation of a new system. This phase is composed of several
systems. This phase focuses on the detailed implementation of the feasible system. It emphasis on
translating design specifications to performance specification. System design has two phases of
development logical and physical design.
During logical design phase the analyst describes inputs (sources), out puts (destinations),
databases (data sores) and procedures (data flows) all in a format that meats the uses requirements. The
analyst also specifies the user needs and at a level that virtually determines the information flow into and out
of the system and the data resources. Here the logical design is done through data flow diagrams and
database design.
The physical design is followed by physical design or coding. Physical design produces the working
system by defining the design specifications, which tell the programmers exactly what the candidate system
must do. The programmers write the necessary programs that accept input from the user, perform necessary
processing on accepted data through call and produce the required report on a hard copy or display it on the
screen.
6.1 LOGICAL DESIGN
Logical design of an information system shows the major features and also how they are related to one
another. The first step of the system design is to design logical design elements. This is the most creative and
challenging phase and important too. Design of proposed system produces the details of the state how the
system will meet the requirements identified during the system analysis that is, in the design phase we have to
find how to solve the difficulties faced by the existing system. The logical design of the proposed system
should include the details that contain how the solutions can be implemented. It also specifies how the
database is to be built for storing and retrieving data, what kind of reports are to be created and what are the
inputs to be given to the system. The logical design includes input design, output design, and database design
and physical design

29. 6.2 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 into a
usable form for processing data entry. The activity of putting data into the computer 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 errors, avoiding delay, avoiding extra steps and keeping the process
simple.
The system needs the data regarding the asset items, depreciation rates, asset transfer, physical
verification for various validation, checking, calculation and report generation.. The error raising method is
also included in the software, which helps to raise error message while wrong entry of input is done. So in
input design the following things are considered.
What data should be given as input?
• How the data should be arranged or coded?
• The dialogue to guide the operating personnel in providing input.
• Methods for preparing input validations and steps to follow when error occur
• The samples of screen layout are given in the appendix.
6.3 OUTPUT DESIGN
Computer output is the most important and direct information source to the user. Output design is
a process that involves designing necessary outputs in the form of reports that should be given to the users
according to the requirements. Efficient, intelligible output design should improve the system’s relationship
with the user and help in decision making. Since the reports are directing referred by the management for
taking decisions and to draw conclusions they must be designed with almost care and the details in the
reports must be simple, descriptive and clear to the user. So while designing output the following things are
to be considered.
• Determine what information to present

30. • Arrange the presentation of information in an acceptable format
• Decide how to distribute the output to intended receipts
Depending on the nature and future use of output required, they can be displayed on the monitor
for immediate need and for obtaining the hardcopy. The options for the output reports are given in the
appendix.
6.4 PHYSICAL DESIGN
The process of developing the program software
is referred to as physical design. We have to design
the process by identifying reports and the other
outputs the system will produce. Coding the program
for each module with its logic is performed in this
step. Proper software specification is also done in this
step.
6.5 MODULAR DESIGN
A software system is always divided into several sub systems that makes it easier for the
development. A software system that is structured into several subsystems makes it easy for the development
and testing. The different subsystems are known as the modules and the process of dividing an entire system
into subsystems is known as modularization or decomposition.
A system cannot be decomposed into several subsystems in any way. There must some logical barrier,
which facilitates the separation of each module. The separation must be simple but yet must be effective so
that the development is not affected.

31. The system under consideration has been divided into
several modules taking in consideration the above-
mentioned criteria. The different modules are
1.College and Department details
2. Login and subject
3. Student Details
4. Exam Details
6.6 DATABASE DESIGN
The overall objective in the development of database technology has been to treat data as an
organizational resource and as an integrated whole. DBMS allow data to be protected and organized
separately from other resources. Database is an integrated collection of data. The most significant form of
data as seen by the programmers is data as stored on the direct access storage devices. This is the difference
between logical and physical data.
Database files are the key source of information into the system. It is the process of designing
database files, which are the key source of information to the system. The files should be properly designed
and planned for collection, accumulation, editing and retrieving the required information.
The organization of data in database aims to achieve three major objectives: -
• Data integration.
• Data integrity.
• Data independence.

32. The proposed system stores the information relevant for processing in the MS SQL SERVER
database. This database contains tables, where each table corresponds to one particular type of information.
Each piece of information in table is called a field or column. A table also contains records, which is a set of
fields. All records in a table have the same set of fields with different information. There are primary key
fields that uniquely identify a record in a table. There are also fields that contain primary key from another
table called foreign keys.
6.6.1 NORMALIZATION
Normalization is a technique of separating redundant fields and braking up a large table in to a smaller
one. It is also used to avoid insertion, deletion and updating anomalies. All the tables have been normalized
up to the third normal form. In short the rules for each of the three normal forms are as below.
• First normal form
A relation is said to be in 1NF if all the under lying domain of attributes contain simple individual
values.
• Second normal form
The 2NF is based on the concept of full functional dependency. A relation said to be in 2NF if and
only if it is in 1NF and every non-key attribute is fully functionally dependent on candidate key of the table.
• Third normal form
The 3NF is based on the concept of transitive dependency. A relation in 2NF is said to be in 3NF if
every non-key attribute is non-transitively.

33. CHAPTER 7
CODING
The goal of the coding phase is to translate the design. The aim in this phase is to implement the
design in the best possible manner. Well known code can reduce the testing and maintenance effort. During
coding, the focus should on developing programs that are easy to read and understand and not simply on
developing the programs that are easy to write. Simplicity and clarity should be strived for during the code
phase. An important concept that help the understandability of the programs is structured programming. The
program that should be organized as a sequence of statements and during execution of the statements is
executed in the sequence given in the program. There are many different criteria for judging of the program,
execution time and required memory.

34. CHAPTER 8
SYSTEM TESTING AND IMPLEMENTATION
8.1 SYSTEM TESTING
System testing is a critical aspect of Software Quality Assurance and represents the ultimate review
of specification, design and coding. Testing is a process of executing a program with the intent of finding an
error. A good test is one that has a probability of finding an as yet undiscovered error. The purpose of testing
is to identify and correct bugs in the developed system. Nothing is complete without testing. Testing is the
vital to the success of the system.
In the code testing the logic of the developed system is tested. For this every module of the program
is executed to find an error. To perform specification test, the examination of the specifications stating what
the program should do and how it should perform under various conditions.
Unit testing focuses first on the modules in the proposed system to locate errors. This enables to
detect errors in the coding and logic that are contained within that module alone. Those resulting from the
interaction between modules are initially avoided. In unit testing step each module has to be checked
separately.
System testing does not test the software as a whole, but rather than integration of each module in the
system. The primary concern is the compatibility of individual modules. One has to find areas where modules
have been designed with different specifications of data lengths, type and data element name.
Testing and validation are the most important steps after the implementation of the developed system.
The system testing is performed to ensure that there are no errors in the implemented system. The software
must be executed several times in order to find out the errors in the different modules of the system.
Validation refers to the process of using the new software for the developed system in a live
environment i.e., new software inside the organization, in order to find out the errors. The validation phase
reveals the failures and the bugs in the developed system. It will be come to know about the practical
difficulties the system faces when operated in the true environment. By testing the code of the implemented
software, the logic of the program can be examined. A specification test is conducted to check whether the

35. specifications stating the program are performing under various conditions. Apart from these tests, there are
some special tests conducted which are given below:
Peak Load Tests: This determines whether the new system will handle the volume of activities when
the system is at the peak of its processing demand. The test has revealed that the new software for the
agency is capable of handling the demands at the peak time.
Storage Testing: This determines the capacity of the new system to store transaction data on a disk or
on other files. The proposed software has the required storage space available, because of the use of a
number of hard disks.
Performance Time Testing: This test determines the length of the time used by the system to process
transaction data.
In this phase the software developed Testing is exercising the software to uncover errors and ensure
the system meets defined requirements. Testing may be done at 4 levels
• Unit Level
• Module Level
• Integration & System
• Regression
8.1.1 UNIT TESTING
A Unit corresponds to a screen /form in the package. Unit testing focuses on verification of the
corresponding class or Screen. This testing includes testing of control paths, interfaces, local data structures,
logical decisions, boundary conditions, and error handling. Unit testing may use Test Drivers, which are
control programs to co-ordinate test case inputs and outputs, and Test stubs, which replace low-level
modules. A stub is a dummy subprogram.
8.1.2 MODULE LEVEL TESTING
Module Testing is done using the test cases prepared earlier. Module is defined during the time of
design.
8.1.3 INTEGRATION & SYSTEM TESTING

36. Integration testing is used to verify the combining of the software modules. Integration testing
addresses the issues associated with the dual problems of verification and program construction. System
testing is used to verify, whether the developed system meets the requirements.
8.1.4 REGRESSION TESTING
Each modification in software impacts unmodified areas, which results serious injuries to that
software. So the process of re-testing for rectification of errors due to modification is known as regression
testing.
Installation and Delivery:
Installation and Delivery is the process of delivering the developed and tested software to the
customer. Refer the support procedures.
Acceptance and Project Closure:
Acceptance is the part of the project by which the customer accepts the product. This will be done as
per the Project Closure, once the customer accepts the product, closure of the project is started. This
includes metrics collection, PCD, etc.
8.2 SYSTEM IMPLEMENTATION
Implementation includes all those activities that take place to convert from the old system to the
new. The old system consists of manual operations, which is operated in a very different manner from the
proposed new system. A proper implementation is essential to provide a reliable system to meet the
requirements of the organizations. An improper installation may affect the success of the computerized
system.
8.2.1 IMPLEMENTATION METHODS:
There are several methods for handling the implementation and the consequent conversion from the
old to the new computerized system.
The most secure method for conversion from the old system to the new system is to run the old and
new system in parallel. In this approach, a person may operate in the manual older processing system as well
as start operating the new computerized system. This method offers high security, because even if there is a
flaw in the computerized system, we can depend upon the manual system. However, the cost for
maintaining two systems in parallel is very high. This outweighs its benefits.

37. Another commonly method is a direct cut over from the existing manual system to the computerized
system. The change may be with in a week or with in a day. There are no parallel activities. However, there
is no remedy in case of a problem. This strategy requires careful planning.
A working version of the system can also be implemented in one part of the organization and the
personnel will be piloting the system and changes can be made as and when required. But this method is less
preferable due to the loss of entirety of the system.
8.2.2 IMPLEMENTATION PLAN:
The implementation plan includes a description of all the activities that must occur to implement
the new system and to put it into operation. It identifies the personnel responsible for the activities and
prepares a time chart for implementing the system. The implementation plan consists of the following steps.
o List all files required for implementation.
o Identify all data required to build new files during the implementation.
o List all new documents and procedures that go into the new system.
The implementation plan should anticipate possible problems and must be able to deal with them.
The usual problems may be missing documents; mixed data formats between current and files, errors in data
translation, missing data etc.

38. CHAPTER 9
FIGURES
The different modules, forms and tables in our system are displayed here.
9.1 DATA FLOW DIAGRAM
The following dataflow diagrams show the control flow in our system.
User
Student
information Service
request
Fig9.1 LEVEL 1 DFD

39. USER
SIGN UP LOGIN
REGISTERED
MEMBER
USER
ADMINISTRATOR
DATA BASE VIEW
ACCES DATABASE
SIGN OUT

40. Fig13.2 LEVEL 2 DFD
9.2 SCREEN SHOTS
9.2.1 College and Department details
It deals with the details of college and department.
Fig 1: College details
This form is used to enter the details of the college.

41. Fig 2: Department details
This form is used to enter the details about various courses.

42. 9.1.2 Login and subject
It contains the details of login process and subject details. Login process include sign in sign up ,sign
out, change password.
Fig3: Signup
This form is used for sign up process.

43. Fig4: Sign in form
This form is used to sign in to the system

44. Fig5: Change password form
This form is used to change the password of users.

45. Fig5 :Subject form
This form is used to enter the details about different subjects of different departments and semesters.

46. 9.1.3 Student Details
Fig6: Personnel details

47. Fig7:Parent details
Fig6 and Fig7 are used to enter the personnel details of student.

48. Fig8:Acdemic details
This form is used enter different types

49. 10.1.3 Exam Details
Fig9: Exam details
This form is used to enter marks got for various exams including its register number.

50. Fig 10: This form is used to select a particular student.

51. Fig11: Other details
This form is used to enter the achievements, disciplinary action taken and the month and year of under
going cour se.

52. Fig12: Final report
This form is used to enter technical knowledge, about the lab record, his/her character any remarks.

53. CHAPTER 10
CONCLUSION
The system has been developed with much care that it is free of errors and at the same time it is
efficient and less time consuming. The important thing is that the system is robust. Avoid malfunction from
outsiders .It goes through all phases of software development cycle. So product is accurate. Also provision is
provided for future developments in the system.

54. RESUME
The current application developed is in accordance with the request that has been provided by the
organization. On regarding the future enhancement, the application can further expanded in accordance with
changing scenario. Since the change in testing and user needs arises frequently in certain short intervals of
time, the application can be further upgraded to meet the requirements that may arise in the far or near future.
With regarding to the needs that arises, more and more features can be included by adding it as separate
modules and integrate it with the existing system.
The .NET today is based on OOPs concept, whose main advantage is modularity, which helps us in
adding the future needs as add-on modules to work with the main system which can be done effortlessly
instead of rewriting or modifying the entire application. So the scope of future enhancement is absolutely
clear with the concept that is incorporated in the today that was made used to build the application.

55. REFERENCES
www.msdn.microsoft..com
www.csharpcorner.com
www.getdotnet.com
www.google.com