Institute Management System Report

PROJECT
On
ONLINE INSTITUTE
MANAGEMENT SYSTEM
In Partial Fulfillment of the Requirement for the
Award of the Degree of Master of Business
Administration (IS)
Submitted to
SIKKIM MANIPAL UNIVERSITY
SUBMITTED BY:
NAME
CHOWDHURY
ROLL NO
STUDY CENTER CODE
MAYUKH ROY
520855065
:
02017
ONLINE
INSTITUTE MANAGEMENT
SYSTEM
Submitted By:
Name
Chowdhury
Programme
Mayukh Roy
:
Roll No.
520855065
MBA (IS)
:
Study Centre Code
02017
ACKNOWLEDGEMENT
With Candor and Pleasure I take opportunity to express my sincere thanks. It is because
of his able and mature guidance and co-operation without which it would not have been
possible for me to complete my project.
It is my pleasant duty to thank all the staff member of the computer center who never
hesitated me from time during the project.
Finally, I gratefully acknowledge the support, encouragement & patience of my family,
And as always, nothing in my life would be possible without God, Thank You!
Mayukh Roy Chowdhary
DECLARATION
I hereby declare that this project work titled ONLINE INSTITUTE MANAGEMENT
SYSTEM is my original work and no part of it has been submitted for any other degree
purpose or published in any other from till date.
Mayukh Roy Chowdhary
TABLE OF CONTENT
1.
2.
3.
4.
Introduction and objectives... 8

1.1.
Introduction8
1.2.
Proposed System...12
1.3.
Software & Hardware Requirements13
System Study 22
2.1.
Preliminary Investigation. 24
2.2.
System Development Life Cycle..... 24
2.3.
Feasibility Study. 29
System Analysis. 32
3.1.
Importance of computerized.. 33
3.2.
Functional Requirements. 36
3.3.
Data Description. 41
System Design45
4.1.
Physical Design... 52
4.1.1. Design
Methodology 52
4.1.2. Design
Overview. 52
4.1.3.
Process modeling. 53
4.2.
ER Diagram..54
4.3.
Process Logic For Each modules. 64

5
5.
6.
4.4.
Data Modeling. 66
4.5.
Scheduling.69
Source Code
5.1.
Code Efficiency 72
5.2.
Code Efficiency. 162
5.3.
Optimization of Code 162
Testing
6.1.
Testing Phases.164
6.2.
Verification & Validation170
6.3.
System Implementation Maintenance and Review 171
6.4. Security Measures174

7.
Cost Implementation Of The Project. 175
8.
Conclusion.178
9.
Bibliography. 178
10.
Glossary 179
1.
INTRODUCTION & OBJECTIVES OF THE PROJECT
The product INSTITUTE MANAGEMENT SYSTEM offers records of students,

teachers etc. in an institute. To the users of this project are administrator, teachers,
students, visitors and parents. User is a person of administrative staff at an institute.
Therefore INSTITUTE MANAGEMENT SYSTEM has been designed in such a way
that it will automate the manual work of administrative department by maintaining
records such as fee records, payroll records etc. The user can even manipulate the data
such as by editing the records to update them from time to time or can delete records
which are no more required.
PURPOSE OF REQUIRED DOCUMENTATION:
The software requirement specification is produced at the culmination of the analysis
task. The function and performance allocated to software as a part of system engineering
are refined by establishing a complete information description, a representation of system
behavior, an indication of performance requirements and design constraints, appropriate
validation criteria and other information pertinent to requirements.
SCOPE OF PRODUCT:
The deliverable product is named as INSTITUTE MANAGEMENT SYSTEM. The
scope of automation of INSTITUTE MANAGEMENT SYSTEM is to provide record of
all students, teachers, books in library, courses, fees, payrolls etc. At an institute about
their training or courses at the click of a button rather than maintaining files of papers.
ONLINE INSTITUTE MANAGEMENT SYSTEM will automate the work of
administrative staff which before this software was made was done manually. With the
help of ONLINE INSTITUTE MANAGEMENT SYSTEM administrative people like
receptionist or center manager can get record of students at the click of a button. Record
of students contains their fee status, exam result status (optional) etc. parents can check
the status of their wards, there fee status, feedbacks by the teachers, exam result without
visiting the institute. New visitors can create there accounts, can get course details, fee
details etc.
I have designed the given proposed Website in the ASP.Net to automate the manual work
of administrative department by maintaining records.
The complete set of rules & procedures related to educational administrative department
day to day activities and generating report is called Online Institute Management
System. My project gives a brief idea regarding automated educational department
activities.
I have tried my best to make the complicated process of Online Institute Management
System as simple as possible using Structured & Modular technique & Menu oriented
interface. I have tried to design the software in such a way that user WHO ARE ONLINE
may not have any difficulty in using this package & further expansion is possible without
much effort. Even though I cannot claim that this work to be entirely exhaustive, the
main purpose of my exercise is perform each ADMINISTRATIVE DEPARTMENT
activity in computerized way rather than manually which is time consuming.
I am confident that this software package can be readily used by non-programming
personal (online users as well as management of the educational department) avoiding
human handled chance of error. This project can be successfully uploaded for educational
and training operations .
FEATURES OF INSTITUTE MANAGEMENT SYSTEM
The system is secure in terms that other than authorized user, it cannot be
accessed by any other person.
User friendly interface of the software enables user to use this easily and
conveniently, proper messages and guidelines have been provided as the user
navigates through the forms.
Automatically roll number,admission number is generated for the student being

registered.
Cases where one student can opt for more than one subject like in educational
courses category, new and existing students case has been handle so that existing
student need not register itself again else he/she registers to specific course only,
also subject choice of the student is checked for whether that specific student is
already enrolled to that course or not.
Data retrieval has been done through search forms that is user has full authority
to search records based on any of the prime fields that was entered as a part of
insertion module.
Parents,Teachers,Students and Administrator can login,general visitor can also

become the autorised user.
User can delete and update records along with insertion and searching the
records.
All validations and checks have been deployed in the software to prevent
entering wrong data by user by mistake. Also user can enter records by clicking
the button or by pressing enter key of keyboard; similarly, esc key is used to exit
from one page besides button.
Authentications
ADMIN
1.
2.
3.
4.
5.
6.
7.
8.
9.
Student Entry / ID assignment

Teacher Entry / ID assignment
Course Entry
Show all teacher
Show all student by Course
Fee Report
Payroll Entry
Holiday Approval
Login
9
10.Change Password
STUDENT
1. Login
2. Upload Resume
3. Download Notes
4. Online Examination
5. Show Result
6. Holiday
7. Fee Payment Details
8. Change Password
9. Teacher feed back
TEACHER
1.
2.
3.
4.
5.
6.
7.
8.
Login
Upload Notes
Course Details
Question Answer Entry for online test
Show Result
Student feed back
Holiday Report
Change Password
PARENT
Ward Details
2. Fee Details
3. Exam Result
4. Login
1.
VISITOR
1.
2.
3.
4.
5.
All Login
About Us
Course Details
Contact Us
Fee Details
10
DRAWBACKS OF CURRENT MANUAL- SYSTEM
1.
The current manual system has a lot of paper work and it does not deal
with old and new car purchase and sale.
2. To maintain the records such as fee records, attendance records etc.

manually, is a time-consuming job.
3. With the increase in database, it will become a massive job to maintain the
database.
4. Requires large quantities of file cabinets, which are huge and
require quite a bit of space in the office, which can be used for storing records
of previously registered student.
5. The retrieval of records of previously registered student will be a tedious job.
6. Lack of security for the records, anyone disarrange the records of your system.
7. If someone want to check the details of the available records for his satisfaction ,the
previous system does not provide any necessary detail of this type.
Establish the need of new system
1. Problem of Reliability: Current system is not reliable. It seems to

vary in quality from one month to the, next. Some times it gives
good output, but some times the output is worst.
2. Problem of Accuracy: There are too many mistakes in reports.
3. Problem of timeliness: In the current system the reports and
output produced is mostly late and in most of the cases it is useless
because it is not on time.
11
4. Problem of Validity: The output and reports mostly contains misleading information.
The customer's information is sometimes not valid.
5. Problem of Economy: The current system is very costly. We have to spend lots of
money to keep the system up and going, but still not get the desired results.
6. Problem of Capacity: The current system is suffering from problem of capacity also.
The staff for organization is very less and the workload is too much. Few peoples cannot
handle all the work.
1.2 Proposed System

l. Students Details: The new proposed system stores and maintains all the employees
details.
2. Calculations: The new proposed system calculates service tax ,vat etc automatically
and it is very fast and accurate.
3. Registers: There is no need of keeping and maintaining records register manually. It
remembers each and every record and we can get any report related to students at any
time.
4. Speed: The new proposed system is very fast with 100% accuracy and saves time.
5. Manpower: The new proposed system needs less manpower. Less people can do the
large work.
6. Efficiency: The new proposed systems complete the work of many sales person in
less time.
8. Reduces redundancy: The most important benefit of this system is that it reduces the
redundancy of data within the data.
9. Work load: Reduces the work load of the data store by helping in easy updates of the
products and providing them with the necessary details together with financial
transactions management.
10. Easy statements: Month-end and day-end statement easily taken out without getting
headaches on browsing through the day end statements.
11. Security : Security has been provided to prevent unauthorized access.
12
1.3 SOFTWARE & HARDWARE REQUIREMENTS

The need of todays software development is competence in a GUI based front-end tool,
which can connect to Relational Database engines. This gives the programmer the
opportunity to develop client server based commercial applications.
FRONT END
.NET programming tools are complete programming environments. It allows
programmers to build a GUI program using the various on-screen controls such as
buttons, text, menus, boxes etc. These controls are placed on a form and then the
processing details related with each control are filled in.
In the business world, competitive strategies have become the order of the day to improve
quality, cut costs and provide a high response customer service base. Most organizations
today need to be market driven and do a lot of value addition to their products and
services. This naturally calls for rational decision making, which requires information.
Information Technology or IT provides that effective channel to support and implement
this strategy. Client/Server is the technology that empowers the desktop, thus setting a
trend for the way successful organizations will use technology in the next decade.
13
Introduction to .NET
What is .NET?
A vision of how information technology will evolve

A platform that supports the vision
A business model of software as a service
1. A Vision.
Web sites will be joined by Web services

New smart devices will join the PC
User interfaces will become more adaptable and customizable
Enabled by Web standards
2. A Platform.
The .NET Framework

ASP.NET
.NET Enterprise Servers
o Database, Messaging, Integration, Commerce, Proxy, Security, Mobility,
Content Management
.NET Building Block Services
o Passport
o .NET My Services (Appin)
Goal: make it incredibility easy to build powerful Web applications and Web
services
3. A business model.
Software as a service
Subscription-based services
Application hosting, e.g. bCentral
Interoperability: Web languages and protocols must be compatible with one another
independent of hardware and software.
Evolution: The Web must be able to accommodate future technologies. Encourages
simplicity, modularity and extensibility.
Decentralization: Facilitates Scalability and Robustness.
14
Web Services
A programmable application component accessible via standard Web protocols

The center of the .NET architecture
Exposes functionality over the Web
Built on existing and emerging standards are HTTP, XML, SOAP, UDDI,
WSDL,
The .NET Framework
What is the .NET Framework?
A set of technologies for developing and using components to create:

o Web Forms
o Web Services
o Windows Applications
Supports the software lifecycle
o Development
o Debugging
o Deployment
o Maintenance
Application Architectures
The Different types of Applications may vary from single-tier desktop
applications (applications that follow the single-tier architecture) to multi-tier
applications (applications that follow the two-, three, or n-tier architecture)
Single-tier architecture
o A single executable file handles all functions relating to the user, business,
and data service layers.
Two-tier architecture
15
o Divides an application into the following two components:

Client
Server
Three-tier architecture
o All the three service layers reside separately, either on the same machine
or on different machines.
n-tier architecture
o Uses business objects for handling business rules and data access.
o Has multiple servers handling business services.
The .NET Initiative
The introduction of the Internet and its rapid growth in the recent past has led to
the development of a number of new Technologies.
One of the most important requirements of such applications is the ability to

interchange information across platforms and to benefit from the functionality
provided by other applications.
In the current scenario, although applications serve organization-specific

requirements, they are not interoperable. Microsoft has introduced the .NET
initiative with the intention of bridging the gap in interoperability between
applications.
The .NET initiative offers a complete suite for developing and deploying
applications, which consists of the following:
o NET products: Microsoft has already introduced Visual Studio .NET,
which is a tool for developing NET applications by using programming
languages such as Visual Basic, C#, and Visual C++.
o NET services: Microsoft is coming up with its own set of Web services,
known as My Services. These services are based on the Microsoft Passport
Authentication service, the same service that is used in Hotmail.
16
Explanation of the .NET Framework
Is a collection of services and classes?

Exists as a layer between .NET applications and the underlying operating system.
Encapsulates much of the functionality, such as debugging and security services.
The following figure depicts the components of the .NET Framework:
The .NET Framework Base Classes or the .NET Class Framework
Consists of a class library that works with any .NET language, such as Visual
Basic .NET and C#.
Provides classes that can be used in the code to accomplish a range of common
programming tasks.
Comprises
o Namespaces: Namespaces help you to create logical groups of related
classes and interfaces that can be used by any language targeting the .NET
Framework.
o Assembly: An assembly is a single deployable unit that contains all the
information about the implementation of classes, structures, and
interfaces.
The Common Language Runtime
o Provides functionality such as exception handling, security, debugging,
and versioning support to any language that targets it.
o Can host a variety of languages and offer a common set of tools across
these languages, ensuring interoperability between the codes.
The following diagram depicts the process of compilation and execution of a

.NET application:
Provides the following features:

o Automatic memory management
o Standard type system
o Language interoperability
o Platform independence
o Security management
o Type safety
Advantages of the .NET Framework
Some advantages of the .NET Framework are:

o Consistent programming model
o Multi-platform applications
o Multi-language integration
o Automatic resource management
o Ease of deployment
17
ADO.NET
Is a model used by Visual Basic .NET applications to communicate with a

database for retrieving, accessing, and updating data?
Uses a structured process flow to interact with a database.
ADO .NET Data Access

Most applications need data access at one point of time making it a crucial component
when working with applications. Data access is making the application interact with a
database, where all the data is stored. Different applications have different requirements
for database access. ASP.NET uses ADO.NET (Active X Data Object) as it's data access
and manipulation protocol, which also enables us to work with data on the Internet. Let's
take a look why ADO.NET came into picture replacing ADO.
18
Evolution of ADO.NET
The first data access model, DAO (data access model) was created for local databases
with the built-in Jet engine which had performance and functionality issues. Next came
RDO (Remote Data Object) and ADO (Active Data Object) which were designed for
Client Server architectures but soon ADO took over RDO. ADO was a good architecture
but as the language changes so is the technology within it. With ADO, all the data is
contained in a record set object which had problems when implemented on the network
(Internet) and penetrating firewalls. ADO was a connected data access which means that
when a connection to the database is established the connection remains open until the
application is closed, which raises concerns about database security and network traffic.
And also as databases are becoming increasingly important and as they are serving more
people a connected data access model makes us think about its use. For example, an
application with connected data access may do well when connected to two clients, the
same may do poorly when connected to 10 and might be unusable when connected to 100
or more. Also, open database connections use system resources to a maximum extent
making the system performance less effective.
Why ADO.NET?
To cope up with some of the problems mentioned above, ADO.NET came into existence.
ADO.NET addresses the above mentioned problems by maintaining a disconnected
database access model which means that when an application interacts with the database
the connection is opened to serve the request of the application and is closed as soon as
the request is completed. Likewise if a database is updated, the connection is opened long
enough to complete the Update operation and is closed. By keeping connections open for
only a minimum period of time ADO.NET conserves system resources and provides
maximum security for databases and also has less impact on system performance. Also,
ADO.NET when interacting with database uses XML by converting all the data into
19
XML and using it for database related operations making them more efficient.
Features of ADO.NET
Disconnected data architecture Applications connect to the database only while

retrieving and updating data.
Data cached in datasets ADO.NET is based on a disconnected data structure.

Therefore, the data is retrieved and stored in datasets.
Data transfer in XML format ADO.NET uses XML for transferring

information from a database into a dataset and from the dataset to another
component.
Interaction with the database is done through data commands.
ADO.NET Object Model

Key Components of the ADO.NET Model
Data Provider
o Is used for connecting to a database, retrieving data, and storing the data.
Is of two types:
o OLE DB data provider
o SQL Server data provider
Components of a Data Provider
Connection
o Used to establish a connection with a data source
o Some commonly used properties and methods:
ConnectionString property
Open()method
Close()method
State property
20
Data adapter
o Creates a dataset and updates the database.
o Handles data transfer between the database and the dataset through its
properties and methods.
o Displays the data through the process of table mapping.
o Are of two types:
SqlDataAdapter
OleDbDataAdapter
Data command
o Is a SQL statement or a stored procedure that is used to retrieve, insert,
delete, or modify data from a data source.
o Is an object of the OleDbCommand or SQLCommand class.
Data reader
o Is used to retrieve data from a data source in a
read-only and forward-
only mode.
o Stores a single row at a time in the memory.
o Commonly used methods:
Read()
Close()
NextResult()
Dataset
o Is a disconnected, cached set of records that are retrieved from a database?
o Is present as a DataSet class in the System.Data namespace.
o Has its own object model.
21
22
2.1 Preliminary Investigation

System development, a proccess consisting of two major steps of system analysis and
design, start when management or sometimes system development personnel feel that a
new system or an improvement in the existing system is required. The sustem
development life cycle is classically thought of as the set of activities that analysts,
desiners and users carry out to develop and implement an information system. The
system development life cycle consists of the following activities:
Preliminary investigation
Determination of system requirements
Design of system
Development of software
System testing
Implementation, evaluation, and maintenance
A request to take assistance from information system can be made for many reasons,
but in each case someone in the organisation initiates the request is made, the first
system activity the preliminary investigation begins. This activity has three parts:
1) Request clarification
2) Feasibility study
3) Request approval
Request clarification: Many requests from employees and users in the

organisations are not clearly defined, Therefore it becomes necessary that project
request must be examined and clarified properly before considering systems
investigation.
23
2.2 SYSTEM DEVELOPMENT LIFE CYCLE

Systems are created to solve problems. One can think of the systems approach as an
organized way of dealing with a problem. In this dynamic world, The subject System
Analysis and Design (SAD), mainly deals with the software development activities.
DEFINING A SYSTEM
A collection of components that work together to realize some objective forms a
system. Basically there are three major components in every system, namely input,
processing and output.
In a system the different components are connected with each other and they are
interdependent. For example, human body represents a complete natural system. We are
also bound by many national systems such as political system, economic system,
educational system and so forth. The objective of the system demand that some output
is produced as a result of processing the suitable inputs.
SYSTEM LIFE CYCLE

System life cycle is an organizational process of developing and maintaining systems. It
helps in establishing a system project plan, because it gives overall list of processes
and sub-processes required for developing a system.
System development life cycle means combination of various activities. In other words
we can say that various activities put together are referred as system development life
cycle. In the System Analysis and Design terminology, the system development life cycle
means software development life cycle.
Following are the different phases of software development cycle:
System study
Feasibility study
24
System analysis
System design
Coding
Testing
Implementation
Maintenance
The different phases of software development life cycle is shown

below.
25
PRELIMINARY
INVESTIGATION
DETERMINATION OF
REQUIREMENTS
REVIEW RUNNING
SYSTEM AND SYSTEM
MAINTENANCE
DEVELOPMENT OF
PROTOTYPE SYSTEM
SYSTEM
IMPLEMENTATION
DESIGN OF SYSTEM
DEVELOPMENT OF
SOFTWARE AND CODING
SYSTEM
SYSTEM TESTING
TESTING
SYSTEM
ANALYSIS
50%
DESIGN
OF
SYSTEM
30%
CODING
20%
FIG: SHOWING GENERAL LIFE CYCLE PROCESS AND PERCENTAGE OF TIME

DEVOTED
26
A system analysis is a separation of a substance into parts for study and their
implementation and detailed examination.
Before designing any system it is important that the nature of the business and
the way it currently operates are clearly understood. The detailed examination provides
the specific data required during designing in order to ensure that all the client's
requirements are fulfilled. The investigation or the study conducted during the analysis
phase is largely based on the feasibility study. Rather it would not be wrong to say that
the analysis and feasibility phases overlap. High-level analysis begins during the
feasibility study. Though analysis is represented as one phase of the system
development life cycle (SDLC), this is not true. Analysis begins with system
initialization and continues until its maintenance. Even after successful implementation
of the system, analysis may play its role for periodic maintenance and up gradation of
the system.
One of the main causes of project failures is inadequate understanding, and one
of the main causes of inadequate understanding of the requirements is the poor planning
of system analysis.
Analysis requires us to recall the objectives of the project and consider
following three questions:
What type of information is required?
What are the constraints on the investigation?
What are the potential problems that may make the task
more difficult?
Keeping the above questions in mind and considering the survey conducted to
determine the need of the system, the total system was deigned and can be described as
under:
27
The three major parts of the system are:
Providing Information:
The system is effectively used to provide large variety of information to the interested
customer. The major purpose of the site is to easily provide access to records of various
automobile such as car with quick update to latest modifications in the records. This
thing is not at all possible in printed material, which are updated only once a few
weeks. It also gives information about the general usage of the system for first time
visitors. The system itself works as a information provider for automobile organization.
28
2.3 FEASIBILITY STUDY
The feasibility study proposes one or more conceptual solution to the problem set of the
project. In fact, it is an evaluation of whether it is worthwhile to proceed with project or
not.
Feasibility analysis usually considers a number of project alternatives, one that is chosen
as the most satisfactory solution. These alternatives also need to be evaluated in a broad
way without committing too many resources. Various steps involved in feasibility
analysis are:
1. To propose a set of solution that can realize the project goal. These solutions are
usually descriptions of what the new system should look like.
2. Evaluation of feasibility of such solutions. Such evaluation often indicates
shortcomings in the initial goals. This step is repeated as the goals are adjusted and
the alternative solutions are evaluated.
COST AND BENEFIT ANALYSIS

Developing an IT application is an investment. Since after developing that application it
provides the organization with profits. Profits can be monetary or in the form of an
improved working environment. However, it carries risks, because in some cases an
estimate can be wrong. And the project might not actually turn out to be beneficial.
Cost benefit analysis helps to give management a picture of the cost, benefits and risks. It
usually involves comparing alternate investments.
Cost benefit determines the benefits and savings that are expected from the system and
compares them with the expected costs.
29
In performing cost and benefit analysis it is important to identify cost and benefits
factors. Cost and benefits can be categorized into the following categories:
1.
Development Costs Development costs is the costs that are incurred during the
development of the system. It is one time investment.
2.
Operating Costs Operating Costs are the expenses required for the day to day
running of the system. Examples of Operating Costs are Wages, Supplies and
Overheads.
3.
Hardware/Software Costs It includes the cost of purchasing or leasing of

computers and its peripherals. Software costs involves required S/W costs.
4.
Personnel Costs It is the money spent on the people involved in the

development of the system.
5.
Facility Costs Expenses that are incurred during the preparation of the physical
site where the system will be operational. These can be wiring, flooring, acoustics,
lightning, and air-conditioning.
6.
Supply Costs These are variable costs that are very proportionately with the
amount of use of paper, ribbons, disks, and the like.
BENEFITS
We can define benefits as

Profit or Benefit = Income Costs
Benefits can be accrued by:
Increasing income, or
Decreasing costs, or
Both
SYSTEM OVERVIEW
30
The limited time and resources have restricted us to incorporate, in this project, only a
main activities that are performed in an Online Institute Management System, but utmost
care has been taken to make the system efficient and user friendly. Institute
Management System has been designed to computerized the following functions that are
performed by the system:
1. New records are entered.
2. Present record can be updated.
3. Record not needed can be deleted.
4. Existing record can be searched.
5. Prevents unauthorized access.
31
32
3.1 IMPORTANCE OF COMPUTERIZED

There are several attributes in which the computer based information works. Broadly
the working of computer system is divided into two main groups:
Transaction System
Decision Support System
Transaction System:
A transaction is a record of some well-defined single and usually small occurrence in
a system. Transactions are input into the computer to update the database files. It
checks the entering data for its accuracy. This means that numeric data appears in
numeric field and character data in character field. Once all the checks are made,
transaction is used to update the database. Transaction can be inputted in on-line
mode or batch mode. In on-line mode, transactions are entered and updated into the
database almost instantaneously. In batch mode, transactions are collected into
batches, which may be held for a while and inputted later.
Decision Support System:

It assists the user to make analytical decision. It shows the various data in organized
way called analysis. This analysis can be made to syrdy preferences and help in
making decisions.
Computer system works out best with record maintenance. It will tell you which
customer would get how much pending/reports statements. It will also help to search
the information about a particular person by simply entering his telephone number.
User can store information as per requirement, which can be used for comparison
with other reports.
33
DEFINETION, ACRONYMS & ABBREVIATIONS:

Log-In-Id: When user logs in to the Online Institute Management System then user is
requested to fill in the login provided to him by he administrator. It acts as a security
mechanism to prevent unauthorized access.
Password: When a user will try to login in to the site to access record, the user will be
requested to fill in the password. This check the validity of the user.
USER CHARACTERISTICS:
Software uses graphical interface and also at every step user is guided well to
avoid confusion if any.
User authentication is tested through login and password facility
It is the responsibility of the user to enter the records genuinely and correctly and
with utmost accuracy as far as possible to avoid discrepancies.
ASSUMPTIONS & DEPENDENCIS:
The software uses vb.Net therefore the terminal it is to be run trust support
Visual.Net studio 2003.
It is assumed that the user is intelligent enough that he/she will not repeat
information again & again.
34
SPECIFIC REQURIMENTS:
New records are entered through the graphical user interface i.e the forms and at the click
of a button they are entered into the database, so that they can be retrieved for future use
or any enquiry.
EXTERNAL INTERFACE REQUIREMENTS:

User Interface : Online Institute Management System provides complete graphical
user interface which will make software more interactive & convenient to use.
Hardware Interface: Online Institute Management System will interact with almost
all types of hardware available at an institute.
Software Interface: Software uses ASP.Net for forms designing and to provide good
graphical user interface. SQL Server is used at the backend to store data.
NON FUNCTIONAL REQUIREMENT:
Performance Requirement: Using ASP.Net with SQL Server 2000 enhances the
performances of project as both are Microsoft products therefore front and backend have
been chosen such that the performance increases.
Software Quality Attributes: Online Institute Management System with stands
following quality attributes: correctness in terms of number of computational errors,
Robustness.
35
3.2 FUNCTIONAL REQIREMENTS:

Functional Module 1: To login and password facility has been provided to authenticate
the user.
Input: password provided by administrator.
Process: designing the login form.
Functional Module 2: User enters the data through forms the database.
Purpose: Data is required for later use by the institute also to keep records of students
performance.
Input: student that come for courses or training in the institute register themselves.
Process: designing the forms and entering data into database.
Functional Module3: To enter and maintain projects being made t an institute.
Input: Input for these forms is provided to user by the group leader and guide of the
project.
Process: Designing the project record entry form.
Functional Module4: To enable user to edit data
Purpose: Data or information changes with time therefore records need to be updated.
Input: monthly assessment of each student
Process: Updating database with new records
Functional Module5: To delete records that is no more required
Purpose: Saving space and memory requirements and thus increasing accessibility and
retrieval of data faster.
Input: Roll no of student or primary key of the table.
Process: updating database.
36
Functional Module6: Retrieval of data

Purpose: user needs for future planning or for studying a students performance graph.
Input: primary key of tables from which we want to extract data.
Process: generating reports.
Functional Module7: Fee Details
Purpose: Student,Parents needs to get their updated students Fee Details.Administrator
add these details.
Input: primary key of tables from which we want to extract data.
Functional Module8: Holiday Details
Purpose: Student,Parents,Teachers needs to get updated holidays approval
list.Administrator add these details.
Functional Module9: Uploading
Purpose: This module is for Students and Teachers.Teachers can upload notes and
assignments that students can download,Students can upload there resumes that teachers
can download.
Functional Module10: Online Examination
Purpose: Students can check their skills through online examination.Teachers can add
new questions.
37
Functional Module11: Examination Result

Purpose: Students and Parents can check the results online by just giving their
enrollment number.Teachers can add mark details.
Functional Module12: Feedback
Purpose: Students ,Teachers and Parents can give their feedbacks.
38
DETAILED DECOMPOSITION
MODULE DESCRIPTION
MODULE 1: User Authentication Module
This module verifies whether the user is valid or not. Basically, purpose of this module is
to distinguish between two types of users one i.e. those who can view and manipulate
records that is the administrative staff members & the other who have no right to view
this information.
Module 2: A New Records Being Entered
Purpose of this module is to edit/ update the records previously entered for example the
monthly attendance record of the student needs to be updated, similarly fee record
updation after the due fees has been deposited.
MODULE 3: Deleting the Records
Students who have completed there Industrial Training or course or employees who have
done their training submit their ID back to the institute before leaving and
correspondingly certificate is issued to them for their successful completion of course etc,
these students records needs to be deleted as they are no more part of the organization.
39
MODULE 4 Retrieving Records

The user of the software is the administrative person of the organization therefore he/she
needs to access the records as when required like enquiring the fee status, attendance
status of a student, or it may be generating a notice for notice board enlisting students
who are short of attendance etc.
PROCESS DECOMPOSITION
Validation: This login and password facility has been provided to authenticate the user.
The process is designing the login form.
Record Entry: Entering the records via forms designed for user convenience an finally
records are stored into the database.
Editing the records: The process is to enable user to edit. Data or information changes
with time therefore records need to be updated like monthly assessment of each student
etc.
Deleting the Records: The process is to delete records that are no more required.
Purpose is to save space and memory requirement and thus increasing accessibility and
40
3.3. DATA DESCRIPTION

Data entity 1:
First thing is the login and the password facility, it has been provided to authenticate the
user that is other than administrative staff like students etc should not have access to the
records as they may try to change the records like fee and attendance status.
Data entity 2:
Second important information is registration form, fee record form, attendance form and
lastly the accessories form. These forms appear again for different category of students at
an institute that allows i.e. one, who come for industrial training/ project in their final
semesters, secondly those who join an institute with purpose of doing the courses offered
by it, in this case one student can opt for more than one course thus he has been
categorized as new and existing student, finally those customers who are or were
employees of some organization and have joined an institute under some scheme like one
for VRS employees.
Data Entity 3:
Third important entity is the data retrieval forms that take input as user parameters for the
search and generate report for the same.
41
DEPENDENCY DESCRIPTION
Module Dependency:
All the modules are interrelated as editing; deletion and retrieval can be performed only
after successful execution of the data entry module, same way unless and until login and
password form is executed user cannot enter the options page.
Process Dependency:
Interdependence of validation process, entering records process, edit, delete and retrieval
process & all its sub processes. All the processes are dependent upon the validation
process as in if a user does not surpasses this process the user will not be able to move
onto other processes.
Data Dependency:
String of characters entered as password, allows user to move to other page, & options
are displayed. Thus, validation module, basically deals with data i.e. password.
Registration form entries act as input to databases that keep record of new & existing
students. Information like name of student, data of birth etc entered by user is entered in
database all this data is the part of edit, delete & retrieve module of Institute Management
System.
42
Test Data:
The user at the time of login, if enters wrong password then appropriate message will be
flashed & user stays on the same form.
E.g. Say password is Institute Management System & if user enters some other string
then error will be displayed as invalid password.
If wrong data is entered in text boxes during the filling of Registration form then as the
user clicks OK button valid types will appear & invalid fields will be made to fill
again.
43
44
45
System Design
The design document that we will develop during this phase is the blueprint of the
software. It describes how the solution to the customer problem is to be built. Since
solution to complex problems isnt usually found in the first try, iterations are most likely
required. This is true for software design as well. For this reason, any design strategy,
design method, or design language must be flexible and must easily accommodate
changes due to iterations in the design . Any technique or design needs to support and
guide the partitioning process in such a way that the resulting sub-problems are as
independent as possible from each other and can be combined easily for the solution to
the overall problem. Sub-problem independence and easy combination of their solutions
reduces the complexity of the problem. This is the objective of the partitioning process.
Partitioning or decomposition during design involves three types of decisions: Define the boundaries along which to break;
Determine into how money pieces to break; and
Identify the proper level of detail when design should stop and implementation should
start.
Basic design principles that enable the software engineer to navigate the design process
suggest a set of principles for software design, which have been adapted and extended in
the following list:
Free from the suffer from "tunnel vision." A good designer should consider alternative
approaches, judging each based on the requirements of the problem, the resources
available to do the job.
The design should be traceable to the analysis model. Because a single element of the
design model often traces to multiple requirements, it is necessary to have a means for
tracking how requirements have been satisfied by the design model.
The design should not repeat the same thing. Systems are constructed using a set of
design patterns, many of which have likely been encountered before. These patterns
should always be chosen as an alternative to reinvention. Time is short and resources are
46
limited! Design time should be invested in representing truly new ideas and integrating
those patterns that already exist.
The design should "minimize the intellectual distance" between the software and the
problem as it exists in the real world. That is, the structure of the software design should
(whenever possible) mimic the structure of the problem domain.
The design should exhibit uniformity and integration. A design is uniform if it appears
that one person developed the entire thing. Rules of style and format should be defined
for a design team before design work begins. A design is integrated if care is taken in
defining interfaces between design components.
The design activity begins when the requirements document for the software to be
developed is available. This may be the SRS for the complete system, as is the case if the
waterfall model is being followed or the requirements for the next "iteration" if the
iterative enhancement is being followed or the requirements for the prototype if the
prototyping is being followed. While the requirements specification activity is entirely in
the problem domain, design is the first step in moving from the problem domain toward
the solution domain. Design is essentially the bridge between requirements specification
and the final solution for satisfying the requirements.
The design of a system is essentially a blueprint or a plan for a solution for the system.
We consider a system to be a set of components with clearly defined behavior that
interacts with each other in a fixed defined manner to produce some behavior or services
for its environment. A component of a system can be considered a system, with its own
components. In a software system, a component is a software module.
The design process for software systems, often, has two levels. At the first level, the
focus is on deciding which modules are needed for the system, the specifications of these
modules, and how the modules should be interconnected. This is what is called the
system design or top-level design. In the second level, the internal design of the modules,
or how the specifications of the module can be satisfied, is decided. This design level is
often called detailed design or logic design. Detailed design essentially expands the
system design to contain a more detailed description of the processing logic and data
structures so that the design is sufficiently complete for coding.
47
Because the detailed design is an extension of system design, the system design controls
the major structural characteristics of the system. The system design has a major impact
on the testability and modifiability of a system, and it impacts its efficiency. Much of the
design effort for designing software is spent creating the system design.
The input to the design phase is the specifications for the system to be designed. Hence,
reasonable entry criteria can be that the specifications are stable and have been approved,
hoping that the approval mechanism will ensure that the specifications are complete,
consistent, unambiguous, etc. The output of the top-level design phase is the architectural
design or the system design for the software system to be built. This can be produced
with or without using a design methodology. A reasonable exit criteria for the phase
could be that the design has been verified against the input specifications and has been
evaluated and approved for quality.
A design can be object-oriented or function-oriented. In function-oriented design, the
design consists of module definitions, with each module supporting a functional
abstraction. In object-oriented design, the modules in the design represent data
abstraction (these abstractions are discussed in more detail later). In the function-oriented
methods for design and describe one particular methodology the structured design
methodology in some detail. In a function- oriented design approach, a system is viewed
as a transformation function, transforming the inputs to the desired outputs. The purpose
of the design phase is to specify the components for this transformation function, so that
each component is also a transformation function. Hence, the basic output of the system
design phase, when a function oriented design approach is being followed, is the
definition of all the major data structures in the system, all the major modules of the
system, and how the modules interact with each other.
Once the designer is satisfied with the design he has produced, the design is to be
precisely specified in the form of a document. To specify the design, specification
languages are used. Producing the design specification is the ultimate objective of the
design phase. The purpose of this design document is quite different from that of the
design notation. Whereas a design represented using the design notation is largely to be
used by the designer, a design specification has to be so precise and complete that it can
48
be used as a basis of further development by other programmers. Generally, design

specification uses textual structures, with design notation helping in understanding.
49
The final deliverable from system analysis is a document containing an unambiguous

statement of the client's requirements from the new system and what the development
project will have to deliver in order to be considered a success.
The functional specification is the starting point for designing, which depends to a large
extent on the accuracy and thoroughness with which the analysis has been carried out.
Understanding of the business, appreciation of the client's problems and documentation
of requirements provide the foundation on which the designing is based.
A key factor in this approach is the use of the structured techniques.
Analysis ends with a description of what the new system must do to fulfill the
requirements of the organization, while design specifies how this will be done by
selecting one of the many ways of doing it.
DESIGN
ANALYSIS
Describing WHAT the
System will do?
The
gap
Describing HOW
the system will do
it
The structured techniques used during the analysis which provide this logical view are:
Data flow diagrams - representing the process, which manipulate the data as it passes
through the system.
50
Entity model - showing the relationship within the data items held within the system.
A data dictionary - providing an overall consistent definition of the data used during the
system development. This definition includes the content of the data stores, data flows
and the process shown on the data flow diagrams, and the entities that make up the entity
model.
DESIGN OBJECTIVES AND CONSTRAINTS:

Flexible
The design would enable future requirements of the organization to be incorporated
without much difficulty. Often the organizational needs and objectives change over time
and hence such a design enables the system to reflect these changes.
Maintainable A good design is easy to maintain and this reduces the client's maintenance cost, which
usually represents a proportion of the lifetime of the system.
Portable A client for whom the software was developed may wish to change the hardware on
which the system run. A good design is portable - in other words it is capable of being
transferred from one machine environment to another with minimum amount of effort.
Easy to use With increasing number of general users having exposure to computers and access to web
sites, expectations of computer applications in term of their ease of use are also
increasing. A good design will result in a system which is `user - friendly' - easy to
understand, not difficult to learn how to use and straightforward to operate.
51
Reliable The system designed must be secure against human error, deliberate misuse or machine
failure, and which the data will be stored without corruption.
4.1 PHYSICAL DESIGN

The design phase focuses on the detailed implementation of the system recommended in
the feasibility. Emphasis is on translating performance specifications into design
specifications. The design phase is a transition from user-oriented document to a
programmer-oriented document.
a.
Design Methodology:
Design Methodology is a way to transform the "art" of system analysis and design into an
"engineering - type" discipline. It explains the relationship amongst various modules and
programs with in the system. It standardizes the approach to analysis and design,
simplifies design by segmentation, improves documentation and subsequent maintenance
and enhancements.
The following structured diagram can appropriately represent the relationship between
various modules .
b. Design Overview:
In analyzing the present system a great deal of information was collected during the
investigation and feasibility phases through list of problems and requirements, interview
reports, questionnaires, onsite observations, manuals and determining potential solutions.
It is important to record this information in an unambiguous, concise manner
which will be clear and accessible to others, and which can be used by other analysts
52
and designers involved in developing the system. Structured techniques help us to record
the information in this way, using diagrams and minimum amount of the text.
Structured analysis is a set of techniques and graphical tools that allow the
analyst to develop a new kind of system specification that are easily understandable
to the user. The traditional approach of organizing data through flowcharts support
future developments and simplify communication with the user but focus on the
cost/benefit and feasibility analysis, project
management,
hardware and software
selection, and personal considerations. In contrast, structured analysis considers new

goals and structured tools for
analysis, which provide the basis for design and implementation.
c. Process Modeling:
System design goes through two phases of development: logical and physical. Logical
implementation represented by Data Flow Diagram shows the logical flow of a
system and defines the boundaries of the system it describes the input (source),
outputs (destinations), data bases (data stores), and procedures (data flows) - all in
the format that meets the user's requirements. The logical implementation of the
whole project can be represented as under through Data Flow Diagrams (DFD).
53
ER diagrams
54
Online Institute Management System

Holidays,
Feedback
Report
Status
Library
Student
Acknowledgement
Admission
Issue Book
Book
Request /Return
Online
Institute
Managemen
t System
Downloads
Receipt
Online
Exam
Exam Result
Fees
Exams
Fee
Management Reports
Institute Management
System
55
Exam
Result
1st LEVEL DFD

Admission
Submit
Request/Exam form
Student
Receipts/ Result
Mark sheet
Status
Receive &
Transform
Student
Admission
Form/fees
Submit
Subject wise form
Book Request
Academic
D1: Student
registered
Library
Submit System
Book Issue
Receiv fees
Receipts
Fee details
Fee Details
D4: Fee
Library
Management
System
Library
Management
system
D3: Library
56
2.0 update
Accounts
Detail
Accounts
Manager
D2: Fee record
DFD for ACADEMIC
for admission
Student
Receipt
Acknowledgement
Generate
Acknowledgement
Slip
Academic
Update Student
Admission Data
D1: Registration
57
DFD for ACCOUNTS

Submit Fees
Student
Receipts
Generate
Acknowledgement
Slip
Academic
Update payment
made
D2: ACCOUNT
58
DFD for Fee

Give Student Details
Fee Details
Academic
Receipts
Generate
Acknowledgement
Slip
Check payment
details
D2: Fee
59
DFD for Library
Book request
Student
Book Issue
LIBRARY
Receipt
Late Fine
Accounts
D2: Accounts
Update Book
Record
Print
Report
D3: Library
60
DFD for Notes,Resumes

Resume
Resumes
and Projects
Student
Notes
Update Notes
Generate
Status
Report
D4: Notes
61
DFD For Online Examination System
Student
Student
Request
Request
Administrator
1.2
Administrator
1.1 Book
Exam
D1
admin
Book Exam
D2 Exam
1.4 Result
Processor
1.3 Online
Examinatio
n System
marks
1.5 Paper
Setter
Evaluate
Papers
D3
D5 Surveyor
`
62
Papers
DFD for Exam Booking

Request
Student
2.1 Request
Booking
Take time
Book Exam
2.2
Administrator
2.3 Online
Examination
System
2.3 Online
Examination
System
D1 Administrator
63
4.3 Process Logic for Each Module:

Validation: This login and password facility has been provided to authenticate the user.
The process is designing the login form.
Record Entry: Entering the records via forms designed for user convenience and finally
records are stored into the database.
Editing the records: The process is to enable user to edit. Data or information changes
with time therefore records need to be updated like monthly assessment of each student
etc.
Deleting the Records: The process is to delete records that are no more required.
Purpose is to save space and memory requirement and thus increasing accessibility and
Data Structure Requirements according to the modules:

Identify The Various Tables Required.
Fields for These Tables.
The Various Key Fields (for example Primary key and foreign key).
Identify The Various Constraints like Not Null, Unique etc.
Describing Data Elements:

Each entry in the data dictionary consists of a set of details describing the data used or
produced in the system. Each item is identified by a data name, description, alias, and
length and has specific values that are permissible for it in the system being
studied.
64
List of Tables:
1. Login
2.
Students
3. Courses
4.
Fee
5. Teachers
6. Resume
7. Notes
8. Result
9. Payroll
10.Notes
11.Feedback
12.Holidays
13.Teachers Feedback
14.Students Feedback
65
4.4 Data Modeling

Teacher Feedback
Field Name
stid
comment
Data Type
Char
Char
Constraint
Not Null
Not Null
Data Type
Char
Char
Char
Char
Char
Char
Constraint
Primary Key
Not Null
Not Null
Not Null
Not Null
Not Null
Data Type
Char
Char
Char
Constraint
Not Null
Not Null
Not Null
Data Type
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Constraint
Primary Key
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Teacher
Field Name
Teacher_Id
Name
Qualification
Course
Email
Department
Student Feedback
Field Name
stid
tname
comment
Student
Field Name
Name
Name
Address
City
Phone
Email
Fathers_name
Occupation
Admission_no
Course
Sessions
66
Resume
Field Name
Resume
Name
Data Type
Char
Char
Constraint
Not Null
Not Null
Data Type
Char
Char
Char
Char
Char
Char
Char
Constraint
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Data Type
Char
Char
Char
Char
Char
Char
Char
Constraint
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Data Type
Char
Char
Constraint
Not Null
Not Null
Data Type
Char
Char
Char
Char
Char
Constraint
Not Null
Not Null
Not Null
Not Null
Not Null
Result
Field Name
Name
Rollno
Addno
Course
Marks
Maxmarks
sem
Payroll
Field Name
id
name
email
department
basic
da
pf
Notes
Field Name
Filename
title
Login
Field Name
Id
usern
passw
authen
email
67
Library
Field Name
Name
Auther
publisher
copies
Category
Data Type
Char
Char
Char
Char
Char
Constraint
Not Null
Not Null
Not Null
Not Null
Not Null
Holiday
Field Name
Year
month
Day
course
Date
holiday
Data Type
Char
Char
Char
Char
Char
Char
Constraint
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Feedback
Field Name
Name
Email
Comment
Data Type
Char
Char
Char
Constraint
Not Null
Not Null
Not Null
Fee
Field Name
Name
Email
Admission_no
Course
Session
Semester
Amount
Mode
Description
Data Type
Char
Char
Char
Char
Char
Char
Char
Char
Char
Constraint
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
68
4.5 SCHEDULING
Scheduling of a software project does not differ greatly from scheduling of any multitask engineering effort. Therefore, generalized project scheduling tools and techniques
can be applied with little modification to software projects.
Program evaluation and review technique (PERT) and critical path method (CPM) are
two project scheduling methods that can be applied to software development. Both
techniques are driven by information already developed in earlier project planning
activities.
Estimates of Effort
A decomposition of the product function.
The selection of the appropriate process model and task set.
Decomposition of tasks.
Interdependencies among tasks may be defined using a task network. Tasks, sometimes
called the project Work Breakdown Structure (WBS) are defined for the product as a
whole or for individual functions.
Both PERT and CPM provide quantitative tools that allow the software planner to (1)
determine the critical path-the chain of tasks that determines the duration of the project;
(2) establish "most likely" time estimates for individual tasks by applying statistical
models; and (3) calculate "boundary times" that define a time window" for a particular
task.
Boundary time calculations can be very useful in software project scheduling. Slippage in
the design of one function, for example, can retard further development of other
functions. It describes important boundary times that may be discerned from a PERT or
CPM network: (I) the earliest time that a task can begin when preceding tasks are
completed in the shortest possible time, (2) the latest time for task initiation before the
minimum project completion time is delayed, (3) the earliest finish-the sum of the earliest
start and the task duration, (4) the latest finish- the latest start time added to task duration,
69
and (5) the total float-the amount of surplus time or leeway allowed in scheduling tasks
so that the network critical path maintained on schedule. Boundary time calculations lead
to a determination of critical path and provide the manager with a quantitative method for
evaluating progress as tasks are completed.
Both PERT and CPM have been implemented in a wide variety of automated tools that
are available for the personal computer. Such tools are easy to use and take the
scheduling methods described previously available to every software project manager.
70
71
Home.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Home.aspx.cs" Inherits="Home" %>

<%@ Register Src="webparent.ascx" TagName="webparent" TagPrefix="uc1" %>
<%@ Register Src="visitor.ascx" TagName="visitor" TagPrefix="uc2" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>Institute Management System</title>
<link href="styleSheetp.css" rel="Stylesheet" type="text/css" />
</head>
<body>
<form id="form1" runat="server">
<div id="header">
<uc1:webparent ID="Webparent1" runat="server" />
</div>
<div id="sidebar">
<uc2:visitor ID="Visitor1" runat="server" />
72
</div>
<br />
<strong> HOME</strong>
<br />
<br />
<p class="MsoNormal" style="margin: 0in 0in 0pt; line-height: 150%">
<span style="font-size: 12pt; line-height: 150%; font-family: Verdana; mso-bidi-font-size: 10.0pt">
The product Institute Management System offers records of student,teachers,fee
details,payroll details,holidays approved etc.all the details about an institute.
To<span style="mso-spacerun: yes"> </span>the general
usres,parents,students,administrator,teachers
of the institute. Therefore this website has been designed in such a
way that it will automate the manual work of administrative department by maintaining
records such as fee records, payroll records etc. The administrator can even manipulate
the data such as by editing the records to update them from time to time or can
delete records which are no more required.</span></p>
</p>
<span style="font-size: 12pt; line-height: 150%; font-family: Verdana; mso-bidi-font-size: 10.0pt">
<asp:Image ID="Image1" runat="server" ImageUrl="~/IMAGES/i_corporates[1].jpg" /><?xml
namespace="" ns="urn:schemas-microsoft-com:office:office"
prefix="o" ?><o:p></o:p></span> </p>
</form>
</body>
</html>
73
Administrator Pannel
Login.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default"

%>
<title>Add Fee Details</title>
<link href="styleSheet2.css" rel="Stylesheet" type="text/css" />
</head>
<body>
<div id="header">
<br />
</div>
<div>
<table style="width: 535px; left: 106px; position: relative; top: 87px; background-color: #ccffcc;">
<tr>
74
<td style="width: 92px">

</td>
</td>
</td>
</tr>
<tr>
Username</td>
<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox></td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server"
ControlToValidate="TextBox1"
ErrorMessage="Should not be blank"></asp:RequiredFieldValidator></td>
</tr>
<tr>
Password</td>
</tr>
<tr>
Authentication</td>
<asp:DropDownList ID="DropDownList1" runat="server" Width="138px">
<asp:ListItem>Parent</asp:ListItem>
<asp:ListItem>Teacher</asp:ListItem>
<asp:ListItem>Student</asp:ListItem>
<asp:ListItem>Admin</asp:ListItem>
</asp:DropDownList></td>
</td>
</tr>
<tr>
<td style="width: 92px; height: 26px">
</td>
<asp:Button ID="Button1" runat="server" Text="Login" Width="123px"
OnClick="Button1_Click" /></td>
<asp:HyperLink ID="HyperLink1" runat="server" NavigateUrl="~/Newuser.aspx"
Width="168px">New User Sign Up</asp:HyperLink></td>
</tr>
</table>
</div>
</form>
75
</body>
</html>
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
public partial class _Default : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
string connectionString = "trusted_connection=true;database=institute";
SqlConnection con = new SqlConnection(connectionString);
SqlCommand com = new SqlCommand();
string query = "select * from login where usern=@membername and passw=@password and
authen=@aut";
com.CommandText = query;
com.Connection = con;
SqlParameter obj1 = new SqlParameter("@membername", DbType.StringFixedLength);
obj1.Value = TextBox1.Text;
Session["name"] = TextBox1.Text;
com.Parameters.Add(obj1);
SqlParameter obj2 = new SqlParameter("@password", DbType.StringFixedLength);
Session["pass"] = TextBox2.Text;
SqlParameter obj3 = new SqlParameter("@aut", DbType.StringFixedLength);
obj3.Value = DropDownList1.SelectedItem.Text;
SqlDataAdapter da = new SqlDataAdapter();
da.SelectCommand = com;
DataTable ds = new DataTable();
da.Fill(ds);
if (ds.Rows.Count == 0)
{
TextBox1.Text = "";
TextBox2.Text = "";
Response.Write("Invalid user:try again:");
}
else
{
Session["log"] = "Sign In";
76
if(DropDownList1.SelectedItem.Text=="Parent")
Response.Redirect("Parent menu.aspx");
else if (DropDownList1.SelectedItem.Text == "Teacher")
Response.Redirect("teacher menu.aspx");
else if (DropDownList1.SelectedItem.Text == "Student")
Response.Redirect("student menu.aspx");
else if (DropDownList1.SelectedItem.Text == "Admin")
Response.Redirect("admin menu.aspx");
}
}
}
Changepassword.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Changepassword.aspx.cs"

Inherits="Changepassword" %>
77

</head>
<body>
<div id="header">
<br />
</div>
<div>
<strong>
<br />

<span style="color: #000066">Change Password
Form</span></strong><table style="width: 535px; left: 58px; position: relative; top: 34px; backgroundcolor: #ffff99;">
<tr>
</td>
</td>
</td>
</tr>
<tr>
Username</td>
</tr>
<tr style="color: #000000">
Old Password</td>
<asp:TextBox ID="TextBox2" runat="server" TextMode="Password"
Width="148px"></asp:TextBox></td>
ErrorMessage="Should not be blank" Width="134px"></asp:RequiredFieldValidator></td>
</tr>
New Password</td>
<asp:TextBox ID="TextBox3" runat="server" TextMode="Password"></asp:TextBox></td>
78

</tr>
<tr>
Confirm Password</td>
<asp:CompareValidator ID="CompareValidator1" runat="server"
ControlToCompare="TextBox3"
ControlToValidate="TextBox4" ErrorMessage="Password Sholud be
same"></asp:CompareValidator></td>
</tr>
<tr>
Authentication</td>
<asp:ListItem>Parent</asp:ListItem>
<asp:ListItem>Teacher</asp:ListItem>
<asp:ListItem>Student</asp:ListItem>
<asp:ListItem>Admin</asp:ListItem>
</td>
</tr>
<tr>
Email</td>
<asp:RegularExpressionValidator ID="RegularExpressionValidator1" runat="server"
ErrorMessage="Invalid Email Id" ValidationExpression="\w+([-+.']\w+)*@\w+
([-.]\w+)*\.\w+([-.]\w+)*"></asp:RegularExpressionValidator></td>
</tr>
<tr>
</td>
<asp:Button ID="Button1" runat="server" Text="Submit" Width="123px"
OnClick="Button1_Click1" /></td>
<asp:Label ID="Label1" runat="server" Text="Label"></asp:Label></td>
</tr>
</table>
</div>
</form>
</body>
79
</html>
using System;
using System.Data;
using System.Collections;
using System.Web;
public partial class Changepassword : System.Web.UI.Page
{
protected void Button1_Click1(object sender, EventArgs e)
{
string query = "select * from login where usern=@membername and passw=@password and
authen=@aut and email=@email";
com.CommandText = query;
Session["name"] = TextBox1.Text;
SqlParameter obj4 = new SqlParameter("@email", DbType.StringFixedLength);
SqlDataAdapter da = new SqlDataAdapter();
da.SelectCommand = com;
da.Fill(ds);
if (ds.Rows.Count == 0)
{
TextBox1.Text = "";
TextBox2.Text = "";
TextBox3.Text = "";
TextBox4.Text = "";
TextBox5.Text = "";
Label1.Text="Invalid user:try again:";
80
}
else
{
string queryString = "update login set passw=@newpass where usern=@membername and
passw=@password and authen=@aut and email=@email";
SqlCommand com1 = new SqlCommand();
com1.CommandText = queryString;
com1.Connection = con;
SqlParameter obj5 = new SqlParameter("@newpass", DbType.StringFixedLength);
com1.Parameters.Add(obj5);
SqlParameter obj9 = new SqlParameter("@email", DbType.StringFixedLength);
con.Open();
com1.ExecuteNonQuery();
con.Close();
Label1.Text = "Password Changed";
}
}
}
81
Reports
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="reports.aspx.cs" Inherits="reports" %>

<%@ Register Src="admin.ascx" TagName="admin" TagPrefix="uc1" %>
<link href="styleSheeta.css" rel="Stylesheet" type="text/css" />
</head>
<body>
<div id="header">
</div>
<div id="sidebar">
<uc1:admin ID="Admin1" runat="server" />
</div>
<br />
82
<table style="width: 302px; height: 84px">

<tr>
<td>
</td>
<td>
<strong>View Reports</strong></td>
<td>
</td>
</tr>
<tr>
<td>
</td>
<td>
<asp:HyperLink ID="HyperLink1" runat="server" NavigateUrl="~/repostudent.aspx">Student
Details</asp:HyperLink></td>
<td>
</td>
</tr>
<tr>
<td>
</td>
<td>
<asp:HyperLink ID="HyperLink2" runat="server"
NavigateUrl="~/repoteacher.aspx">Teacher Details</asp:HyperLink></td>
<td>
</td>
</tr>
<tr>
<td>
</td>
<td>
<asp:HyperLink ID="HyperLink3" runat="server" NavigateUrl="~/repopayroll.aspx">Payroll
<td>
</td>
</tr>
<tr>
<td>
</td>
<td>
<asp:HyperLink ID="HyperLink4" runat="server" NavigateUrl="~/repofee.aspx">Fee
<td>
</td>
</tr>
<tr>
<td>
</td>
<td>
NavigateUrl="~/repofeedback.aspx">Visitors/Parents Feedback</asp:HyperLink></td>
<td>
</td>
</tr>
83
<tr>
<td style="height: 25px">
</td>
<asp:HyperLink ID="HyperLink6" runat="server" NavigateUrl="~/repobooks.aspx">Books
</td>
</tr>
<tr>
<td>
</td>
<td>
NavigateUrl="~/repoholiday.aspx">Holidays Approved</asp:HyperLink></td>
<td>
</td>
</tr>
<tr>
<td>
</td>
<td>
NavigateUrl="~/repostufeed.aspx">Students Feedbacks</asp:HyperLink></td>
<td>
</td>
</tr>
</table>
</form>
</body>
</html>
84
Repostudent.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="repostudent.aspx.cs"

Inherits="repostudent" %>
<%@ Register Assembly="CrystalDecisions.Web, Version=10.2.3600.0, Culture=neutral,
PublicKeyToken=692fbea5521e1304"
Namespace="CrystalDecisions.Web" TagPrefix="CR" %>
<link href="/aspnet_client/System_Web/2_0_50727/CrystalReportWebFormViewer3/css/default.css"
rel="stylesheet" type="text/css" />
</head>
<body>
<div>
<CR:CrystalReportViewer ID="CrystalReportViewer1" runat="server" AutoDataBind="true" />
<CR:CrystalReportSource ID="CrystalReportSource1" runat="server">
85
<Report FileName="stu.rpt"></Report>
</CR:CrystalReportSource>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class repostudent : System.Web.UI.Page
{
{
String scon = "Trusted_Connection=True;DataBase=institute";
SqlConnection con = new SqlConnection(scon);
SqlDataAdapter da1 = new SqlDataAdapter("select * from student", con);
DataTable dt = new DataTable();
da1.Fill(dt);
CrystalReportSource1.ReportDocument.SetDataSource(dt);
CrystalReportViewer1.ReportSource = CrystalReportSource1;
CrystalReportViewer1.DataBind();
}
}
86
Repoteacher.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="repoteacher.aspx.cs"

Inherits="repoteacher" %>
</head>
<body>
<div>
87
<Report FileName="teacher.rpt"></Report>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class repoteacher : System.Web.UI.Page
{
{
SqlDataAdapter da1 = new SqlDataAdapter("select * from teacher", con);
da1.Fill(dt);
}
}
88
Repopayroll.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="repopayroll.aspx.cs"

Inherits="repopayroll" %>
</head>
<body>
<div>
89
<Report FileName="payroll.rpt"></Report>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class repopayroll : System.Web.UI.Page
{
{
SqlDataAdapter da1 = new SqlDataAdapter("select * from payroll", con);
da1.Fill(dt);
}
}
90
Visitor/Parents Feedbacks Report
using System;
using System.Data;
using System.Web;
public partial class repofeedback : System.Web.UI.Page
{
{
SqlDataAdapter da1 = new SqlDataAdapter("select * from feedback", con);
da1.Fill(dt);
91
}
}
Repofee.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="repofee.aspx.cs" Inherits="repofee" %>

92

</head>
<body>
<div>
<Report FileName="fee.rpt"></Report>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class repofee : System.Web.UI.Page
{
{
SqlDataAdapter da1 = new SqlDataAdapter("select * from fee", con);
da1.Fill(dt);
}
}
93
Books Details Report
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="repobooks.aspx.cs"

Inherits="repobooks" %>
</head>
<body>
<div>
<cr:crystalreportviewer id="CrystalReportViewer1" runat="server"
autodatabind="true"></cr:crystalreportviewer>
94
<cr:crystalreportsource id="CrystalReportSource1" runat="server">

<Report FileName="BOOKS.RPT"></Report></cr:crystalreportsource>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class repobooks : System.Web.UI.Page
{
{
SqlDataAdapter da1 = new SqlDataAdapter("select * from library", con);
da1.Fill(dt);
}
}
95
Holidays Approved
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="repoholiday.aspx.cs"

Inherits="repoholiday" %>
</head>
<body>
96

<div>
<Report FileName="holiday.rpt"></Report>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class repoholiday : System.Web.UI.Page
{
{
SqlDataAdapter da1 = new SqlDataAdapter("select * from holiday", con);
da1.Fill(dt);
}
}
97
Student Feedback Report
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="repostufeed.aspx.cs"

Inherits="repostufeed" %>
</head>
<body>
98

<div>
<Report FileName="STUFEED.RPT"></Report>

</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class repostufeed : System.Web.UI.Page
{
{
SqlDataAdapter da1 = new SqlDataAdapter("select * from teacherfeed", con);
da1.Fill(dt);
}
}
99
Addstudent.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="addstudent.aspx.cs"

Inherits="addstudent" %>
</head>
<body>
<div id="header">
</div>
<div id="sidebar">
</div>
100
<div>
<br />
<br />
<tr>
Name</td>
</tr>
<tr>
Enrollment No.</td>
</td>
</tr>
<tr>
Address</td>
</tr>
<tr>
City</td>
</tr>
<tr>
Phone</td>
</tr>
<tr>
101
Email</td>
ErrorMessage="Invalid email id" ValidationExpression="\w+([-+.']\w+)*@\w+
([-.]\w+)*\.\w+([-.]\w+)*"></asp:RegularExpressionValidator></td>
</tr>
<tr>
Father's Name</td>
</tr>
<tr>
Occupation</td>
</tr>
<tr>
AddmissionNo.

</td>
</tr>
<tr>
Course</td>
<asp:ListItem>BCA</asp:ListItem>
<asp:ListItem>MCA</asp:ListItem>
<asp:ListItem>B.Tech.</asp:ListItem>
<asp:ListItem>M.Tech.</asp:ListItem>
<asp:ListItem>PGDCA</asp:ListItem>
<asp:ListItem>MBA</asp:ListItem>
102
</td>
</tr>
<tr>
Session</td>
</tr>
<tr>
</td>
<asp:Button ID="Button1" runat="server" OnClick="Button1_Click" Text="Submit"
Width="114px" /></td>
<asp:Label ID="Label1" runat="server"></asp:Label></td>
</tr>
</table>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class addstudent : System.Web.UI.Page
{
{
int code;
string que = "select *from student";
SqlDataAdapter da = new SqlDataAdapter(que, connectionString);
DataTable dataset = new DataTable();
da.Fill(dataset);
int n = dataset.Rows.Count;
if (n == 0)
code = 1;
else
103
code = n + 1;
TextBox2.Text = "D0/2009/" + code;
TextBox9.Text = "10" + code;
}
{
string queryString = "insert into student
values(@name,@roll,@add,@city,@phone,@email,@fname,@occu,@addno,@course,@sess)";
com.CommandText = queryString;
try
{
com.Parameters.Add(new SqlParameter("@name", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@add", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@city", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@phone", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@email", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@addno", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@roll", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@fname", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@occu", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@sess", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@course", SqlDbType.Char, 50));
com.Parameters["@name"].Value = TextBox1.Text;
com.Parameters["@roll"].Value = TextBox2.Text;
com.Parameters["@add"].Value = TextBox3.Text;
com.Parameters["@city"].Value = TextBox4.Text;
com.Parameters["@phone"].Value = TextBox5.Text;
com.Parameters["@email"].Value = TextBox6.Text;
com.Parameters["@fname"].Value = TextBox7.Text;
com.Parameters["@occu"].Value = TextBox8.Text;
com.Parameters["@addno"].Value = TextBox9.Text;
com.Parameters["@course"].Value = DropDownList1.SelectedItem.Text;
com.Parameters["@sess"].Value = TextBox10.Text;
con.Open();
com.ExecuteNonQuery();
con.Close();
Label1.Visible = true;
Label1.Text = "Details added";
TextBox1.Text = "";
TextBox2.Text = "";
TextBox3.Text = "";
104
TextBox4.Text = "";
TextBox5.Text = "";
TextBox6.Text = "";
TextBox7.Text = "";
TextBox8.Text = "";
TextBox9.Text = "";
TextBox10.Text = "";
}
catch (SqlException ed)
{
Label1.Text = ed.Message;
}
}
}
uploadresumes.aspx
105
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="upload resumes.aspx.cs"

Inherits="upload_resumes" %>
<%@ Register Src="teacher.ascx" TagName="teacher" TagPrefix="uc2" %>
<%@ Register Src="Students.ascx" TagName="Students" TagPrefix="uc3" %>
<link href="styleSheet.css" rel="Stylesheet" type="text/css" />
</head>
<body>
<div id="header">
</div>
<div id="sidebar">
<uc3:Students ID="Students1" runat="server" />
</div>
<div>
<strong>
<br />
   Resume Upload<br />
<br />
</strong>
<table style="font-weight: bold; width: 467px; background-color: #ffffcc;">
<tr>
Title</td>
<asp:TextBox ID="TextBox1" runat="server" Width="230px"></asp:TextBox></td>
</tr>
<tr>
<td>
Filename</td>
<asp:FileUpload ID="FileUpload1" runat="server" /></td>
</td>
</tr>
<tr>
</td>
<td style="width: 28px; height: 49px;">
<asp:Button ID="Button1" runat="server" OnClick="Button1_Click" Text="Upload" />
106

</td>
</tr>
</table>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class upload_resumes : System.Web.UI.Page
{
{
}
{
if (FileUpload1.HasFile)
{
string str = Server.MapPath("~//Resume//");
str = str + FileUpload1.FileName;
FileUpload1.SaveAs(str);
Label1.Text = "File Uploaded";
string queryString = "insert into resume values(@name,@title)";
try
{
com.Parameters.Add(new SqlParameter("@title", SqlDbType.Char, 50));
com.Parameters["@title"].Value = "resume/" + FileUpload1.FileName; ;
con.Open();
107
con.Close();
TextBox1.Text = "";
}
{
}
}
}
}
Adminholiday.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="adminholiday.aspx.cs"

Inherits="adminholiday" %>
108

</head>
<body>
<div id="header">
</div>
<div id="sidebar">
</div>
<div>
<asp:TextBox ID="txtadholi" runat="server" BorderStyle="Groove" Height="26px" Style="z-index:
100;
left: 407px; position: absolute; top: 395px" TabIndex="2" TextMode="MultiLine"
Width="156px"></asp:TextBox>

<asp:Label ID="Label5" runat="server" BackColor="Transparent" Font-Names="Verdana"
Font-Size="11pt" Height="16px" Style="z-index: 111; left: 265px; position: absolute;
top: 215px" Width="112px">Enter the year</asp:Label>
top: 305px" Width="41px">Date</asp:Label>
<asp:DropDownList ID="dddate" runat="server" Font-Names="Verdana" Font-Size="10pt"
Height="24px" Style="z-index: 109; left: 411px; position: absolute; top: 306px"
TabIndex="3" Width="56px">
<asp:ListItem Value="Date">Date</asp:ListItem>
<asp:ListItem Value="01">01</asp:ListItem>
109
</asp:DropDownList>
<asp:DropDownList ID="ddyear" runat="server" Font-Names="Verdana" Font-Size="10pt"
Height="24px" Style="z-index: 108; left: 408px; position: absolute; top: 217px"
TabIndex="5" Width="56px">
<asp:ListItem Value="Year">Year</asp:ListItem>
</asp:DropDownList>
top: 345px" Width="111px"> Enter the Day</asp:Label>
top: 255px" Width="112px">Select a Month</asp:Label>
<asp:Button ID="adholibutton" runat="server" OnClick="adholibutton_Click" Style="z-index: 104;
left: 358px; position: absolute; top: 452px" TabIndex="3" Text="Submit" />
110
top: 395px" Width="104px">Holidays</asp:Label>

<asp:DropDownList ID="ddmonth" runat="server" Height="26px" Style="z-index: 102;
left: 407px; position: absolute; top: 255px" TabIndex="1" Width="79px">
<asp:ListItem Value="January">January</asp:ListItem>
<asp:ListItem Value="February">February</asp:ListItem>
<asp:ListItem Value="March">March</asp:ListItem>
<asp:ListItem Value="April">April</asp:ListItem>
<asp:ListItem Value="May">May</asp:ListItem>
<asp:ListItem Value="June">June</asp:ListItem>
<asp:ListItem Value="July">July</asp:ListItem>
<asp:ListItem Value="August">August</asp:ListItem>
<asp:ListItem Value="September">September</asp:ListItem>
<asp:ListItem Value="October">October</asp:ListItem>
<asp:ListItem Value="November">November</asp:ListItem>
<asp:ListItem Value="December">December</asp:ListItem>
</asp:DropDownList>
<asp:Label ID="Label1" runat="server" BackColor="#FFE0C0" Font-Bold="True" FontNames="Arial"
Font-Size="20pt" Font-Underline="True" ForeColor="Magenta" Height="24px" Style="z-index:
101;
left: 214px; position: absolute; top: 71px" Width="554px">List of Holidays form for
Adiminstration</asp:Label>
<asp:DropDownList ID="ddday" runat="server" Style="z-index: 106; left: 409px; position: absolute;
top: 346px">
<asp:ListItem Value="Sunday">Sunday</asp:ListItem>
<asp:ListItem Value="Monday">Monday</asp:ListItem>
<asp:ListItem Value="Tuesday">Tuesday</asp:ListItem>
<asp:ListItem Value="Wednesday">Wednesday</asp:ListItem>
<asp:ListItem Value="Thursday">Thursday</asp:ListItem>
<asp:ListItem Value="Friday">Friday</asp:ListItem>
<asp:ListItem Value="Saturday">Saturday</asp:ListItem>
</asp:DropDownList>

<br />
<br />
<br />
<br />
<br />
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
111
public partial class adminholiday : System.Web.UI.Page
{
{
}
protected void adholibutton_Click(object sender, EventArgs e)
{
string queryString = "insert into holiday values(@year,@month,@day,@date,@holiday)";
try
{
com.Parameters.Add(new SqlParameter("@year", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@month", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@day", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@holiday", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@date", SqlDbType.Char, 50));
com.Parameters["@year"].Value = ddyear.SelectedItem.Text;
com.Parameters["@month"].Value = ddmonth.SelectedItem.Text;
com.Parameters["@day"].Value = ddday.SelectedItem.Text;
com.Parameters["@date"].Value = dddate.SelectedItem.Text;
com.Parameters["@holiday"].Value = txtadholi.Text;
con.Open();
con.Close();
Label1.Text = "Holiday added";
txtadholi.Text = "";
}
{
}
}
}
112
Teacherfeedback.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Teacher feedback.aspx.cs"

Inherits="Teacher_feedback" %>
</head>
<body>
<div id="header">
<br />
<br />
</div>
<div id="sidebar">
113
</div>
<div>
<strong>Feedbacks given by the students<br />
</strong>
<br />
<br />
<table style="width: 434px">
<tr>
<br />
</td>
</td>
</td>
</tr>
<tr>
Student ID</td>
</td>
</tr>
<tr>
<td style="height: 144px; width: 72px;">
Comment</td>
<asp:TextBox ID="TextBox2" runat="server" Height="117px"
TextMode="MultiLine"></asp:TextBox></td>
</tr>
<tr>
</td>
</tr>
</table>
</div>
</form>
</body>
</html>
using System;
114
using System.Data;
using System.Web;
public partial class Teacher_feedback : System.Web.UI.Page
{
{
if (!IsPostBack)
{
string que1 = "select *from student";
SqlDataAdapter da1 = new SqlDataAdapter(que1, connectionString);
DataTable dataset1 = new DataTable();
da1.Fill(dataset1);
DropDownList2.DataSource = dataset1;
DropDownList2.DataTextField = "rollno";
DropDownList2.DataBind();
}
}
{
string queryString = "insert into teacherfeed values(@stid,@comment)";
try
{
// com.Parameters.Add(new SqlParameter("@name", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@stid", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@comment", SqlDbType.Char, 50));
// com.Parameters["@name"].Value = DropDownList1.SelectedItem.Text;
com.Parameters["@stid"].Value = DropDownList2.SelectedItem.Text;
com.Parameters["@comment"].Value = TextBox2.Text;
con.Open();
con.Close();
115
Label1.Text = "Feedback added";
TextBox2.Text = "";
}
{
}
}
}
Addfeedetails.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Add fee details.aspx.cs"

Inherits="Add_fee_details" %>
116

</head>
<body>
<div id="header">
</div>
<div id="sidebar">
</div>
<div>
<strong><span style="color: #660000">Add Fee Details</span></strong><br />
<br />
<br />
<tr>
Id</td>
<asp:DropDownList ID="DropDownList4" runat="server" AutoPostBack="True"
OnSelectedIndexChanged="DropDownList4_SelectedIndexChanged"
Width="152px">
</td>
</tr>
<tr>
Name</td>
<asp:TextBox ID="TextBox1" runat="server" ReadOnly="True"></asp:TextBox></td>
</td>
</tr>
<tr>
Email</td>
</td>
</tr>
<tr>
Address</td>
117

</td>
</tr>
<tr>
Course</td>
</td>
</tr>
<tr>
Session</td>
</td>
</tr>
<tr>
Semister</td>
<asp:ListItem>Sem-I</asp:ListItem>
<asp:ListItem>Sem-II</asp:ListItem>
<asp:ListItem>Sem-III</asp:ListItem>
<asp:ListItem>Sem-IV</asp:ListItem>
<asp:ListItem>Sem-V</asp:ListItem>
<asp:ListItem>Sem-VI</asp:ListItem>
<asp:ListItem></asp:ListItem>
</td>
</tr>
<tr>
Amount</td>
</tr>
<tr>
Mode of payment</td>
118
</tr>
<tr>
Description</td>
<asp:TextBox ID="TextBox8" runat="server" TextMode="MultiLine"></asp:TextBox></td>
</tr>
<tr>
</td>
<asp:Button ID="Button1" runat="server" OnClick="Button1_Click1" Text="Submit" /></td>
</tr>
</table>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class Add_fee_details : System.Web.UI.Page
{
{
if (!IsPostBack)
{
string que = "select * from student";
da.Fill(dataset);
DropDownList4.DataSource = dataset;
}
}
119
protected void DropDownList4_SelectedIndexChanged(object sender, EventArgs e)

{
string que = "select * from student where rollno='" + DropDownList4.Text + "'";
da.Fill(dataset);
//Response.Write(dataset.Rows.Count);
TextBox1.Text = dataset.Rows[0][0].ToString();
}
{
string queryString = "insert into fee
values(@id,@name,@email,@adno,@course,@sess,@sem,@amount,@mode,@other)";
try
{
com.Parameters.Add(new SqlParameter("@id", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@adno", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@sess", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@sem", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@amount", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@mode", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@other", SqlDbType.Char, 50));
com.Parameters["@id"].Value = DropDownList4.SelectedItem.Text;
com.Parameters["@adno"].Value = TextBox6.Text;
com.Parameters["@course"].Value = TextBox3.Text;
com.Parameters["@sess"].Value = TextBox4.Text;
com.Parameters["@sem"].Value = DropDownList1.SelectedItem.Text;
com.Parameters["@amount"].Value = TextBox5.Text;
com.Parameters["@mode"].Value = TextBox6.Text;
com.Parameters["@other"].Value = TextBox7.Text;
120
con.Open();
con.Close();
Label1.Text = "Record added";
TextBox1.Text = "";
TextBox2.Text = "";
TextBox3.Text = "";
TextBox4.Text = "";
TextBox5.Text = "";
TextBox6.Text = "";
TextBox7.Text = "";
TextBox8.Text = "";
}
catch
{
Label1.Text = "Record Exist";
}
}
}
DownloadResume.aspx
121
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Download Resume.aspx.cs"

Inherits="Download_Resume" %>
</head>
<body>
<div id="header">
</div>
<div id="sidebar">
</div>
<div>
<br />
122
<br />
<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox><asp:Button ID="Button1"
runat="server" OnClick="Button1_Click" Text="Download" /><br />
<br />
<asp:DataList ID="DataList1" runat="server" RepeatColumns="1" RepeatDirection="Horizontal">
<ItemTemplate>
<%#Eval("name")%>
<br />
<asp:HyperLink ID="HyperLink1" runat="server" NavigateUrl='<%#Eval("resume") %>'
Text='<%#Eval("resume") %>'>Download</asp:HyperLink>
<br />
<br />
</ItemTemplate>
</asp:DataList><br />
<br />
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class Download_Resume : System.Web.UI.Page
{
{
SqlDataAdapter da = new SqlDataAdapter("Select * from resume", con);
DataSet ds = new DataSet();
da.Fill(ds);
DataList1.DataSource = ds;
DataList1.DataBind();
}
{
Response.Redirect("Resume/"+TextBox1.Text);
}
}
Addbooks.aspx
123
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="addbooks.aspx.cs"

Inherits="IMAGES_addbooks" %>
</head>
<body>
<div id="header">
</div>
<div id="sidebar">
</div>
<div>
<br />
124
<strong>Add Bookd Details available in library</strong><br />

<br />
<br />
<br />
<tr>
Title</td>
</tr>
<tr>
Author</td>
</tr>
<tr>
Publisher</td>
</tr>
<tr>
No of copies</td>
</tr>
<tr>
Category</td>
<asp:ListItem>Computers</asp:ListItem>
<asp:ListItem>Maths</asp:ListItem>
<asp:ListItem>Electronics</asp:ListItem>
<asp:ListItem>Othes</asp:ListItem>
125
</td>
</tr>
<tr>
</td>
</tr>
</table>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class IMAGES_addbooks : System.Web.UI.Page
{
{
}
{
string queryString = "insert into library values(@name,@aut,@pub,@copy,@cate)";
try
{
com.Parameters.Add(new SqlParameter("@aut", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@pub", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@copy", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@cate", SqlDbType.Char, 50));
126
com.Parameters["@aut"].Value = TextBox2.Text;
com.Parameters["@pub"].Value = TextBox3.Text;
com.Parameters["@copy"].Value = TextBox4.Text;
com.Parameters["@cate"].Value =DropDownList1.SelectedItem.Text;
con.Open();
con.Close();
Label1.Text = "Book added";
TextBox1.Text = "";
TextBox2.Text = "";
TextBox3.Text = "";
TextBox4.Text = "";
}
{
}
}
}
127
Marks.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="marks.aspx.cs" Inherits="marks" %>

</head>
<body>
<div id="header">
<br />
<br />
<br />
</div>
128
<div id="sidebar">
<uc2:teacher ID="Teacher1" runat="server" />
</div>
<div>
<br />
<span style="color: #990066"><strong>Add Marks Details<br />
</strong></span>
<br />
<table style="width: 485px; height: 76px; background-color: #ffffcc;">
<tr>
Name Of the Student</td>
</tr>
<tr>
Enrollment No.</td>
</tr>
<tr>
Course</td>
<asp:ListItem>BCA</asp:ListItem>
<asp:ListItem>MCA</asp:ListItem>
<asp:ListItem>B.Tech.</asp:ListItem>
<asp:ListItem>M.Tech.</asp:ListItem>
<asp:ListItem>PGDCA</asp:ListItem>
<asp:ListItem>MBA</asp:ListItem>
</td>
</tr>
<tr>
Admission No.</td>
</tr>
129
<tr>
Max. Marks</td>
</tr>
<tr>
Marks obtained</td>
</td>
</tr>
<tr>
Semister</td>
<asp:DropDownList ID="DropDownList2" runat="server">
<asp:ListItem>Sem-1</asp:ListItem>
<asp:ListItem></asp:ListItem>
</td>
</tr>
<tr>
</td>
</tr>
</table>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
130
public partial class marks : System.Web.UI.Page
{
{
}
{
string queryString = "insert into result values(@name,@roll,@addno,@course,@max,@min,@sem)";
try
{
com.Parameters.Add(new SqlParameter("@roll", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@addno", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@max", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@min", SqlDbType.Char, 50));
com.Parameters.Add(new SqlParameter("@sem", SqlDbType.Char, 50));
com.Parameters["@roll"].Value = TextBox7.Text;
com.Parameters["@course"].Value = DropDownList1.SelectedItem.Text;
com.Parameters["@addno"].Value = TextBox3.Text;
com.Parameters["@max"].Value = TextBox4.Text;
com.Parameters["@min"].Value = TextBox5.Text;
com.Parameters["@sem"].Value = DropDownList2.SelectedItem.Text;
con.Open();
con.Close();
TextBox1.Text = "";
TextBox3.Text = "";
TextBox4.Text = "";
TextBox5.Text = "";
131
TextBox7.Text = "";
}
{
}
}
}
132
Teacher Panel
Teachermenu.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Teacher menu.aspx.cs"

Inherits="Teacher_menu" %>
</head>
<body>
<div id="header">
<br />
<br />
133
<br />
</div>
<div id="sidebar">
</div>
<br />
<span style="font-size: 14pt"><strong>Teacher's
Control Panel<br />
<br />
</strong><span style="font-size: 10pt"> <strong>Login</strong>- Must login if you
are existed user and you can <strong>change your password </strong>if you are existed
user.<br />
<br />
<strong>Online Examination-</strong>Add new question for online examintation
papers.<br />
<em><strong> </strong></em><span style="font-size: 11pt; font-family: Times New
Roman"><em><span
style="color: #000000"><span style="font-size: 10pt"><span style="font-family:
Arial"></span></span><em><span
style="font-family: Arial"><strong> <br />
Holidays</strong> - Approved holidays list is given.<br />
<br />
<strong><span style="font-size: 10pt">Students Feedback </span></strong>- Give
your
feedbacks for the student .<br />
<br />
<strong>Upload Notes- </strong>uploaded the notes and assignments.<br />
<br />
<strong>Library Facility- </strong>Check the availability of books in the
library.<br />
<br />
</span></em> <em><span style="font-size: 10pt; font-family: Verdana"> <strong>Exam
Result</strong>- Give the enrollment no. and check the results.</span></em><br />
<br />
<strong>Add Marks Details - </strong>Add marks details of the students.<br />
</span></em></span></span></span>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class Teacher_menu : System.Web.UI.Page
{
134
{
}
}
Searchpayroll.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="searchpayroll.aspx.cs"

Inherits="searchpayroll" %>
</head>
<body>
<div id="header">
135
<br />
<br />
<br />
</div>
<div id="sidebar">
</div>
<div>
<br />
<br />
<br />
<strong>Find your Payroll Details</strong><br />
<br />
<br />
<tr>
<strong>
Enter your
Id </strong>   <br />
<td style="width: 275953px" rowspan="2">
<asp:GridView ID="GridView1" runat="server">
</asp:GridView>
</td>
</tr>
<tr>
<asp:Button ID="Button1" runat="server" OnClick="Button1_Click1" Text="Submit" /></td>
</tr>
</table>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class searchpayroll : System.Web.UI.Page
{
{
136
}
{
string que = "select * from payroll where id='" + TextBox1.Text + "'";
da.Fill(dataset);
GridView1.DataSource=dataset;
GridView1.DataBind();
//Response.Write(dataset.Rows.Count);
}
}
Studentfeedback.aspx
137

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Student feedback.aspx.cs"
Inherits="Student_feedback" %>
</head>
<body>
<div id="header">
<br />
<br />
</div>
<div id="sidebar">
</div>
<div>
<strong>
<br />
<br />
Students Feedback given by the Teacher<br />
<br />
<br />
</strong>
<table style="font-weight: bold; width: 434px; background-color: #ffcc99;">
<tr>
<br />
Student ID</td>
</td>
</tr>
<tr>
Teacher Name</td>
</td>
</tr>
138
<tr>
Comment</td>
</tr>
<tr>
</td>
</tr>
</table>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class Student_feedback : System.Web.UI.Page
{
{
if (!IsPostBack)
{
string que = "select *from teacher";
da.Fill(dataset);
DropDownList1.DataTextField = "name";
139
string que1 = "select *from student";

da1.Fill(dataset1);
DropDownList2.DataSource = dataset1;
}
}
{
string queryString = "insert into stufeedback values(@stid,@name,@comment)";
try
{
com.Parameters.Add(new SqlParameter("@stid", SqlDbType.Char, 50));
com.Parameters["@name"].Value = DropDownList1.SelectedItem.Text;
com.Parameters["@stid"].Value = DropDownList2.SelectedItem.Text;
con.Open();
con.Close();
Label1.Text = "Feedback added";
TextBox2.Text = "";
}
{
}
}
}
140
Holidays.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Holidays.aspx.cs" Inherits="Holidays"

%>
</head>
<body>
<div>
<br />
<strong><span style="color: #cc0066">LIST OF HOLIDAYS</span></strong><br />
<br />
<asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="False">
<Columns>
<asp:BoundField DataField="HOLIDAY" HeaderText="HOLIDAY" />
<asp:BoundField DataField="DAT" HeaderText="DATE" />
<asp:BoundField DataField="DAYS" HeaderText="DAY" />
<asp:BoundField DataField="MONTHS" HeaderText="MONTH" />
<asp:BoundField DataField="YEARS" HeaderText="YEAR" />
141
</Columns>
</asp:GridView>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class Holidays : System.Web.UI.Page
{
{
SqlDataAdapter da = new SqlDataAdapter("Select * from holiday ", con);
da.Fill(ds);
GridView1.DataSource = ds;
}
}
142
Result.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="result.aspx.cs" Inherits="result" %>

</head>
<body>
<div id="header">
<br />
</div>
<div>

<br />

143

Enter Rollno.
<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox>
<asp:Button ID="Button1" runat="server" OnClick="Button1_Click" Text="Search" Width="125px"
/><br />
<br />
<br />
<br />
<asp:GridView ID="GridView1" runat="server" style="left: 210px; position: relative; top: -7px"
Width="260px">
</asp:GridView>
<br />
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class result : System.Web.UI.Page
{
{
}
{
SqlDataAdapter da = new SqlDataAdapter("Select * from result where rollno='" + TextBox1.Text +
"'", con);
da.Fill(ds);
}
}
144
145
Bookdetails.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="bookdetails.aspx.cs"

Inherits="IMAGES_bookdetails" %>
</head>
<body>
<div>
<br />
<br />
Total no. of books available :
<asp:Label ID="Label1" runat="server" Text="Label" Width="50px"></asp:Label><br />
<br />
News Papers Available in Hindi,English and Telgu.<br />
<br />
<asp:Button ID="Button1" runat="server" OnClick="Button1_Click" Text="Search for books"
Width="168px" /><br />
<br />
146
<strong>BOOKS AVAILABLE<br />

</strong>
<br />
<br />
<br />
</asp:GridView>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class IMAGES_bookdetails : System.Web.UI.Page
{
{
SqlConnection
con = new SqlConnection(scon);
SqlDataAdapter da = new SqlDataAdapter("Select * from library", con);
da.Fill(ds);
Label1.Text = ds.Rows.Count.ToString();
}
{
Response.Redirect("booksearch.aspx");
}
}
147
Students Panel
Studentmenu.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="student menu.aspx.cs"

Inherits="student_menu" %>
</head>
<body>
<div id="header">
<br />
<br />
148
</div>
<div id="sidebar">
</div>
<br />
   <span style="font-size: 14pt"><strong>Student's Control
Panel<br />
<br />
</strong><span style="font-size: 10pt"> <strong>Login</strong>- Must login if you
are existed user and you can <strong>change your password </strong>if you are existed
user.<br />
<br />
<strong>Exam Result</strong>- Give your enrollment no. and check your result.<br />
<br />
<strong>Online Examination<br />
<em> Rules For Online Examination<br />
<br />
</em></strong><span style="font-size: 11pt; font-family: Times New Roman"><span
style="color: #000000">
<em>. Become a member of online Examination System.(<asp:HyperLink ID="HyperLink10"
runat="server" Font-Size="Small" NavigateUrl="~/user login form.aspx">Click
Here</asp:HyperLink>)<br />
</em></span><span style="color: #000000"><em>. Register your self.(<asp:HyperLink
ID="HyperLink9" runat="server" Font-Size="Small"
NavigateUrl="~/exam_regist_form.aspx">Click Here</asp:HyperLink>)<br />
</em></span><em><span style="color: #000000">. Select payment mode.(<asp:HyperLink
ID="HyperLink8" runat="server" Font-Size="Small"
NavigateUrl="~/PAYMENT.aspx">Click Here</asp:HyperLink>)<br />
</span><span style="color: #000000">. Now you are valid for online Examination.<br />
<em><span style="font-family: Arial"><span style="font-size: 10pt"><strong> <br
/>
Holidays</strong> <strong>- </strong>Approved holidays list is given.<br />
</span>
<br />
<strong>Students Feedback </strong><span style="font-size: 10pt">- Give your
feedbacks
as a student .<br />
<br />
<strong>Upload Resume- </strong>Upload your Resumes.<br />
<br />
<strong>Download Notes- </strong>Download notes uploaded by the
teachers.<br />
<br />
<strong>Library Facility- </strong>Check the availability of books in the
library.</span><br />
<br />
</span></em>
<br />
<br />
<br />
</span></em>
<br />
</span>
149
<br />
<br />
</span></span>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class student_menu : System.Web.UI.Page
{
{
}
}
150
Parents Panel
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Parent menu.aspx.cs"

Inherits="Parent_menu" %>
<%@ Register Src="Parent.ascx" TagName="Parent" TagPrefix="uc2" %>
<title>Institute Management</title>
</head>
<body>
<br />
<br />
<div id="header">
</div>
<div id="sidebar">
151
<uc2:Parent ID="Parent1" runat="server" />

</div>
<br />
   <strong><span style="font-size: 14pt; color: #336600">
Parent's Control Panel</span></strong><br />
<span style="font-size: 12pt"> <br />
<strong>Login</strong>- If you are existed user must login.<br />
<br />
<strong>Exam Results </strong>- To see the result,give enrollment no. of the
student.<br />
<br />
<strong> Fee Details</strong> - Check Fee Details of your ward.<br />
<br />
<strong>Ward Details</strong>- Give enrollment no. and check ward details
of the student.<br />
<br />
<strong>Feedback </strong>- Give your feedbacks.</span>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class Parent_menu : System.Web.UI.Page
{
{
}
}
152
CheckFeeDetails.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Check Fee Details.aspx.cs"

Inherits="Check_Fee_Details" %>
</head>
<body>
<div>
Enter Your Enrollment No.<asp:DropDownList ID="DropDownList4" runat="server">
</asp:DropDownList><br />
<br />
<asp:Button ID="Button1" runat="server" OnClick="Button1_Click" Text="View Details"
Width="192px" /><br />
<br />
<HeaderStyle BackColor="#FFFFC0" />
</asp:GridView>
153
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class Check_Fee_Details : System.Web.UI.Page
{
{
if (!IsPostBack)
{
string que = "select * from fee";
da.Fill(dataset);
DropDownList4.DataTextField = "roll_no";
}
}
{
string que = "select * from fee where roll_no='"+DropDownList4.SelectedItem.Text+"'";
da.Fill(dataset);
GridView1.DataSource = dataset;
}
}
154
Wardddetails.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Ward details.aspx.cs"

Inherits="Ward_details" %>
</head>
<body>
<div id="header">
<br />
<br />
</div>
155
<div id="sidebar">
</div>
<div>
<br />
   Enter Enrollmentl No.
<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox><br />
<br />

<asp:Button ID="Button1" runat="server" OnClick="Button1_Click" Text="Search" Width="119px"
/><br />
<br />

<asp:DetailsView ID="DetailsView1" runat="server" Height="50px" Width="125px">
</asp:DetailsView>
<br />
<strong>Teachers Feedback if any<br />
<br />
</strong>Teacher
<asp:TextBox ID="TextBox2" runat="server" Width="171px"></asp:TextBox><br />
<br />
Comment<asp:TextBox ID="TextBox3" runat="server" Height="113px" TextMode="MultiLine"
Width="235px"></asp:TextBox></div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class Ward_details : System.Web.UI.Page
{
{
}
{
try
{
string que = "select * from student where rollno='" + TextBox1.Text + "'";
da.Fill(dataset);
156
DetailsView1.DataSource = dataset;
DetailsView1.DataBind();
string que1 = "select *from stufeedback where stid='" + TextBox1.Text + "'";
da1.Fill(dataset1);
TextBox2.Text = dataset1.Rows[0][1].ToString();
TextBox2.DataBind();
TextBox3.Text = dataset1.Rows[0][2].ToString();
TextBox3.DataBind();
}
catch { }
}
}
157
Feedback.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="feedback.aspx.cs" Inherits="feedback"

%>
</head>
<body>
<div id="header">
<br />
158
</div>
<div id="sidebar">
</div>
<div>
<table style="width: 535px; background-color: #ccffff;">
<tr>
</td>
<strong>FEEDBACK FORM</strong></td>
</td>
</tr>
<tr>
Name</td>
<asp:TextBox ID="TextBox1" runat="server" Width="171px"></asp:TextBox></td>
</tr>
Email</td>
ErrorMessage="Invalid Email ID"
ValidationExpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*" Width="148px"
ControlToValidate="TextBox2"></asp:RegularExpressionValidator></td>
</tr>
Comment</td>
</tr>
<tr>
</td>
</td>
159
</td>
</tr>
<tr>
</td>
<asp:Label ID="Label1" runat="server" Text="Label" Width="82px"></asp:Label></td>
</tr>
<tr>
</td>
</td>
</td>
</tr>
<tr>
</td>
</td>
</td>
</tr>
</table>
</div>
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class feedback : System.Web.UI.Page
{
{
}
{
160

string queryString = "insert into feedback values(@name,@email,@comment)";
try
{
con.Open();
con.Close();
TextBox1.Text = "";
TextBox2.Text = "";
TextBox5.Text = "";
}
{
}
}
}
161
VISITORS
Contactus.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="contact us.aspx.cs" Inherits="parent" %>

<%@ Register Src="visitor.ascx" TagName="visitor" TagPrefix="uc2" %>
<title>Institute Management System</title>
</head>
<body>
<div id="header">
</div>
162
<div id="sidebar">
<br />
<uc2:visitor ID="Visitor1" runat="server" />
</div>
<br />
<strong>Contact Us<br />
</strong>
<asp:Image ID="Image1" runat="server" ImageUrl="~/IMAGES/i_franchises[1].jpg" /><br />
For your Suggetions contact us at<br />
Email:contactus@yahoo.com<br />
Phone : 985643458,98543354646<br />
<br />
<asp:Image ID="Image2" runat="server" ImageUrl="~/images/images1.jpg" /><br />
</form>
</body>
</html>
using System;
using System.Data;
using System.Web;
public partial class parent : System.Web.UI.Page
{
{
}
}
163
5.2 Code Efficiency

Reviewing of Code efficiency for a module is carried out after the module is successfully
compiled and all the syntax errors eliminated. Code efficiency review is extremely costeffective strategies for reduction in coding errors in order to produce high quality code.
Normally, two types of efficiency are carried out on the code of a module - code
optimization and code inspection. The procedure and final objective of these two
efficiency techniques are very different as discussed below.
5.3 Optimization of Code

Code optimization is an informal code analysis technique. In this technique, after a
module has been coded, it is successfully compiled and all syntax errors are eliminated.
Some members of the development team are given the code a few days before the
optimization meeting to read and understand the code. Each member selects some test
cases and simulates execution of the code by hand (i.e. trace execution through each
statement and function execution). The main objectives of the optimization are to
discover the algorithmic and logical errors in the code. The members note down their
findings to discuss these in a optimization meeting where the coder of the module is also
present.
Even though a code optimization is an informal analysis technique, several guidelines
have evolved over the years for making this nave technique more effective and useful.
Of course, these guidelines are based on personal experience, common sense, and several
subjective factors. Therefore are based on personal experience, common sense, and
several subjective factors. Therefore, guidelines should be considered as examples rather
than as rules to be applied dogmatically. Some of these guidelines are the following:
164
The team performing the code optimization should not be either too big or too small.
Ideally, it should consist of three to seven members.
165
6.1 Testing Phase

One of the purposes of the testing is to validate and verify the system. Verification means
checking the system to ensure that it is doing what the function is supposed to do and
Validation means checking to ensure that system is doing what the user wants it to do.
No program or system design is perfect; communication between the user and the
designer is not always complete or clear, and time is usually short. The result is errors
and more errors. Theoretically, a newly designed system should have all the pieces in
working order, but in reality, each piece works independently. Now is the time to put all
the pieces into one system and test it to determine whether it meets the user's
requirements. This is the best chance to detect and correct errors before the system is
implemented. The purpose of system testing is to consider all the likely variations to
which it will be subjected and then push the system to its limits. If we implement the
system without proper testing then it might cause the problems.
1. Communication between the user and the designer.
2. The programmer's ability to generate a code that reflects
exactly the system specification.
3. The time frame for the design.
Theoretically, a new designed system should have all the pieces in working order, but in
reality, each piece works independently. Now is the time to put all the pieces into one
system and test it to determine whether it meets the requirements of the user.
The process of system testing and the steps taken to validate and
prepare a system for final implementation are:
166
LEVELS OF TESTING:
The different types of testing are as follows:
UNIT TESTING
VALIDATION
INTREGRATION
N
SYSTEM
1. Unit Testing:
This is the smallest testable unit of a computer system and is
normally tested using the white box testing. The author of the programs usually
carries out unit tests.
2. Integration Testing:
In integration testing, the different units of the system are
integrated together to form the complete system and this type of testing checks the system
as whole to ensure that it is doing what is supposed to do. The testing of an integrated
system can be carried out top-down, bottom-up, or big-bang. In this type of testing, some
parts will be tested with white box testing and some with black box testing techniques.
This type of testing plays very important role in increasing the systems productivity. We
have checked our system by using the integration testing techniques.
167
3. System Testing:
A part from testing the system to validate the functionality of
software against the requirements, it is also necessary to test the non-functional aspect of
the system. Some examples of non-functional tools include tests to check performance,
data security, usability/user friendliness, volume, load/stress that we have used in our
project to test the various modules.
System testing consists of the following steps:
1. Program(s) testing.
2. String testing.
3. System testing.
4. System documentation.
5. User acceptance testing.
4. Field Testing:
This is a special type of testing that may be very important in some
projects. Here the system is tested in the actual operational surroundings. The interfaces
with other systems and
the real world are checked. This type of testing is very rarely used. So far our project is
concerned, we haven't tested our project using the field testing.
5. Acceptance Testing:
After the developer has completed all rounds of testing and he is
satisfied with the system, then the user takes over and re-tests the system from his point
of view to judge whether it is acceptable according to some previously identified criteria.
This is almost always a tricky situation in the project because of the inherent conflict
between the developer and the user. In this project, it is the job of the bookstores to check
the system that whether the made system fulfills the goals or not.
168
Why System Testing?

Testing is vital to the success of the system. System testing makes a logical assumption
that if all the parts of the system are correct , the goal will be successfully achieved.
Inadequate testing results in two type of problems:
1. The time lag between the cause and the appearance of the
problem.
2. The effect of system errors on the files and records within
the system.
Activity Network for System Testing
The test plan entails the following activities:
1. Prepare test plan.
2. Specify conditions for user acceptance testing.
3. Prepare test data for program testing.
4. Prepare test data for transaction path testing.
5. Plan user training.
6. Compile/assemble programs.
7. Prepare job performance aids.
8. Prepare operational documents.
Prepare Test
A workable test plan must be prepared in accordance with established
design specifications. It includes the following items:
Outputs expected from the system.
Criteria for evaluating outputs.
A volume of test data.
169
Procedure for using test data.

Personnel and training requirements.
Specify Conditions for User Acceptance Testing
Planning for user acceptance testing calls for the analyst and the user to agree on
conditions for the test.
Prepare Test Data for Program Testing
As each program is coded, test data are prepared and documented to ensure that all
aspects of the program are properly tested.
Prepare Test Data for Transaction Path Testing

This activity develops the data required for testing every condition and transactions to be
introduced into the system. The path of each transaction from origin to destination is
carefully tested reliable results.
Compile / Assemble Programs

All programs have to be compiled / assembled for testing.
Systems testing
The computer department to ensure that the system functions as specified does this testing. This
testing is important to ensure that a working system is handed over to the user for acceptance
testing.
Acceptance testing.
The user to ensure that the system functions, as the user actually wanted performs this testing.
With prototyping techniques, this stage becomes very much a formality to check the
accuracy and completeness of processing. The screen layouts and output should already
have been tested during the prototyping phase.
170
An error in the program code can remain undetected indefinitely. To prevent this
from happening the code was tested at various levels. To successfully test a system,
each condition, and combinations of conditions had to be tested. Each program was
tested and linked to other programs. This unit of program is tested and linked to other
units and so on until the complete system has been tested.
The purpose of testing is to ensure that each program is fully tested. To do so a
test plan had to be created. The test plan consists of a number of test runs such as the
valid paths through the code, and the exception and error handling paths. For each
test run there is a list of conditions tested, the test data used and the result expected.
The test plan was then reviewed to check that each path through the code is tested
correctly. It is the responsibility of the programmer to collect the data that will
produce the required test condition.
171
6.2 Verification and Validation (V&V)

The objectives of verification, validity activities are to assess and improve the quality of
the work products generated during development and modification of the software.
Quality depends upon the various attributes like correctness, completeness, consistency,
reliability, usefulness, usability, efficiency and conformance to standards.
Verification activities include proving, testing, and reviews. Validation is the process of
evaluating software at the end of the software development to ensure compliance with the
software requirements. Testing is a common method of validation. Clearly, for high
reliability we need to perform both activities. Together, they are often called V&V
activities.
The major V&V activities for software development are inspection, reviews, and testing
(both static and dynamic). The V&V plan identifies the different V&V tasks for the
different phases and specifies how these tasks contribute to the project V&V goals. The
methods to be used for performing these V&V activities, the responsibilities and
milestones for each of these activities, inputs and outputs for each V&V task, and criteria
for evaluating the outputs are also specified.
The two major V&V approaches are testing and inspections. Testing is an activity that
can be generally performed only on code. It is an important activity and is discussed in
detail in a later chapter. Inspection is a more general activity that can be applied to any
work product, including code. Many of the V&V tasks are such that for them, an
inspection type of activity is the only possible way to perform the tasks (e.g. trace ability
and document evaluation). Due to this, inspections play a significant role in verification.
172
SYSTEM
IMPLEMENTATION
173
6.3 System Implementation Maintenance and Review

As we know, creating software is one thing and the implementation of the created
software is another. The process of implementing software is much difficult as compared
to the task of creating the project. First we have to implement the software on a small
scale for removing the bugs and other errors in the project and after removing them we
can implement the software on a large scale.
Before we think in terms of implementing the Software on a large basis, we must

consider the Hardware requirements.
Whenever we develop a software or project a certain hardware and software is
being used by the programmer for developing the project. The hardware and software to
be used by the programmer for developing the project should be such that it would result
in the development of a project, which would satisfy all the basic needs for which the
project has been created by the programmer. The Hardware should be such that cost
constraints of the Client should also be taken into account without affecting the
performance.
HARDWARE EVALUATION FACTORS
When we evaluate computer hardware, we should first investigate specific physical and
performance characteristics for each hardware component to be acquired. These specific
questions must be answered concerning many important factors. These hardware evaluation
factors questions are summarized in the below figure.
Notice that there is much more to evaluating hardware than determining the fastest and
cheapest computing device. For e.g. the question of possible obsolescence must be addressed
by making a technology evaluation. The factor of ergonomics is also very important.
174
Ergonomics is the science and technology that tries to ensure that computers and other
technologies are "user-friendly", that is safe, comfortable and easy to use. Connectivity is
another important evaluation factor, since so many computer systems are now interconnected
within wide area or local area telecommunications networks.
HARDWARE EVALUATION FACTORS

1) Performance
2) Cost
3) Reliability
4) Availability
5) Compatibility
6) Modularity
7) Technology
8) Ergonomics
9) Connectivity
10) Environmental requirements
11) Software
12) Support
175
SOFTWARE EVALUATION FACTORS

Software can be evaluated according to many factors similar to the hardware
evaluation. Thus the factors of performance, cost, reliability, compatibility, modularity,
technology, ergonomics, and support should be used to evaluate proposed software
acquisitions. In addition, however, the software evaluation factors are summarized in
below figure. For e.g. some software packages require too much memory capacity and
are notoriously slow, hard to use, or poorly documented. They are not a good selection
for most end users, even if offered at attractive prices.
SOFTWARE EVALUATION FACTORS:

1) Efficiency: is the software a well-written system of computer instructions that does
not use much memory capacity or CPU time?
2) Flexibility: can it handle its processing assignments easily without major
modifications?
3) Security: does it provide control procedures for errors, malfunctions and improper use?
4) Language: do our computer programmers and users write it in a programming
language that is used?
5) Documentation: is the s/w well documented? Does it include helpful user instructions?
6) Hardware: does existing hardware have the features required to best use this software?
7) Other characteristics of hardware such as its performance, what about the cost, how
much is reliable and etc.
6.4 SECURITY MEASURES

User Name & Password security implemented so that nounauthorised person can
handle any operation without username and Password.
Only authorized person can log-on the system.
176
Only authorized person can update the records.

Only authorized person can handle the reservation.
Only authorized person can print the report.
It has two kinds of users:

1. Administrator
2. User1
Administrator: He has complete authority (Read, Add, Modify) of operating the

software. The User Name and Password provided to the Administrator in this project is:
User Id:
Password:
Admin
admin123
User1: When this user logs onto the system, he can only view information and other
reports. He can generate different reports.
User Id:
Password:
User1
user123
7. COST ESTIMATION OF THE PROJECT

Cost in a project is due to the requirements for software, hardware, and human resources.
Hardware resources are computer time, terminal time and memory required for the
project. Software resources include the tools and compilers needed during development.
The bulk of cost of software development is due to human resources needed. Cost
estimates are determined in terms of person-months (PM).
Total No. Of Persons Involved In This Project:
1 Administrator
2 Senior Programmer
3 Junior Programmers
4..On line Users.
Since this Project will complete in 4 months
177
Cost Estimate: (Salary of Project Manager + Salary of Senior Programmer + 2 * Salary of

Junior Programmer) * 2
Further Scope of the Application

1. Though maximum efforts have been put in to make this report authentic in all aspects
and to take all necessary presentation to ensure that the information gathered is true,
some uncomfortable factors may have crept in.
2. Some of the respondents were reluctant to part with certain information on the pretext
of the sensitivity of the information. Also some facts of figures were not divulged as the
company policy came in the way for free revelation of the desired input.
3. An element of bias might have crept in from the side of the official interviewed. This
could also have resulted in some kind of modification of the information divulged.
4. Through
an
attempt
was
make to
collect information from the
best possible source in the company, it was difficult to meet the top officials due to their
busy schedules.
5. Most of the analysis and interpretations, made for this report, are based on secondary
data obtained. This data could have some inherent mistakes and errors.
6. Finally, although due care has been taken those can be typing and compilation errors in
the report itself.
The tasks specified were not well defined because nothing was
mentioned regarding validations in the project. Though gave maximum effort to check
the software with different validation tests, a few of them might be present in this version
Though all possible checks have been placed but still there
are some
controls where checks have not been deployed, therefore user has to be
careful while entering data through these controls. For e.g.: data entry
has to be in (mm/dd/yyyy) format.
178
Screen resolution has to be 1024 x 768 otherwise forms

will not be visible
Due to limited time available survey could not be undertaken for intended
20 consumers and thus had to be limited to 10
Communication gaps exist between employees and management, as

seniors don't share problem with subordinates resulting in violation of psychological
contract.
Poor rewarding system(slow)
Poor working conditions

The limitations may be many and the magnitude of the influence of these limiting factors
may have a bearing on the report, but it in no way alters the ultimate aim of the project
and because it's highly USER FRIENDLY, it would be the choice of all kinds of
personnel.
179
8. CONCLUSIONS
This project has been a rewarding experience in more than one way. The entire project
work has enlightened us in the following areas.
We have gained an insight into the working of the Hospital. This

represents a typical real world situation
Our understanding of database design has been strengthened this is because in

order to generate the final reports of database
designing has to be properly followed.
Scheduling a project and adhering to that schedule creates a strong sense of time
management.
Sense of teamwork has developed and confidence of handling real life project has
increased to a great extent.
Initially, there were problem with the validation but with discussions , we were to
implement validations.
9. Bibliography
ASP.NET 2003
ASP.NET Projects
ASP.Net Professional Projects
ORACLE 9 The Complete Reference
180
Jamew Foxall
Tony Martin,Dominic Selly
Kuljit Kaur,Pooja Bembey
George Koch Kevin Loney
10.GLOSSARY
Text Box
A text Box control, sometimes called an edit field or edit control, displays information
entered at design time, entered by the user, or assigned to the control in code at run time.
Button
Use a Command Button control to begin, interrupt, or end a process. When chosen, a
Command Button appears pushed in and so is sometimes called a push button.
List Box
A List Box control displays a list of items from which the user can select one or more. If
the number of items exceeds the number that can be displayed, a scroll bar is
automatically added to the List Box control.
Label
A Label control is a graphical control you can use to display text that a user cant change
directly.
GROUPBOX
A GROUPBOX control provides an identifiable grouping for controls. You can also use a
Frame to subdivide a form functionally for example, to separate groups of Option
Button controls.
Combo Box
A Combo Box control combines the features of a text box and a list box. This control
allows the user to select an item either by typing text into the combo box, or by selecting
it from the list.
181
Timer
A Timer control can execute code at regular intervals by causing a Timer event to occur.
The Timer control, invisible to the user, is useful for background processing.
Picture Box
The primary use for the Picture Box control is to display a picture to the user. The actual
picture that is displayed is determined by the picture property. The picture property
contains the file name (and optional path ) for the picture file that you wish to display.
DATA Grid Control

The DATAGrid
control displays and operates on tabular data. It allows complete
flexibility to sort, merge, and format tables containing strings and pictures. When bound
to a Data control, MSFlexGrid displays read-only data.
Date and Time Picker Control

A Date And Time Picker (DTP) Control provides a simple and intuitive interface through
which to exchange data and time information with a user. For example, with a DTP
control you can ask the user to enter a data and then retrieve his or her selection with
ease.
Option Button
An Option Button control displays an option that can be turned on or off.
Image Control
Use the Image control to display a graphic. An Image control can display a graphic from
an icon, bitmap or metafile, as well as enhanced metafile, JPEG, or GIF files.
182
Check Box Control

A Check Box indicates whether a particular condition is on or off. We use check boxes in
an application to give users true/false or yes/no options. Because check boxes work
independently of each other, a user can select any number of check boxes at the same
time.
183

Institute Management System Report

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Institute Management System Report

Uploaded by

Copyright:

Available Formats

PROJECT

Study Centre Code

Mayukh Roy Chowdhary

Mayukh Roy Chowdhary

Introduction and objectives... 8

Software & Hardware Requirements13

System Development Life Cycle..... 24

Process Logic For Each modules. 64

Code Efficiency. 162

Optimization of Code 162

Verification & Validation170

System Implementation Maintenance and Review 171

6.4. Security Measures174

Cost Implementation Of The Project. 175

INTRODUCTION & OBJECTIVES OF THE PROJECT

The product INSTITUTE MANAGEMENT SYSTEM offers records of students,

Automatically roll number,admission number is generated for the student being

Parents,Teachers,Students and Administrator can login,general visitor can also

Student Entry / ID assignment

DRAWBACKS OF CURRENT MANUAL- SYSTEM

2. To maintain the records such as fee records, attendance records etc.

Establish the need of new system

1. Problem of Reliability: Current system is not reliable. It seems to

1.2 Proposed System

1.3 SOFTWARE & HARDWARE REQUIREMENTS

A vision of how information technology will evolve

Web sites will be joined by Web services

The .NET Framework

A programmable application component accessible via standard Web protocols

The .NET Framework

What is the .NET Framework?

A set of technologies for developing and using components to create:

o Divides an application into the following two components:

The .NET Initiative

One of the most important requirements of such applications is the ability to

In the current scenario, although applications serve organization-specific

Explanation of the .NET Framework

Is a collection of services and classes?

The .NET Framework Base Classes or the .NET Class Framework

The following diagram depicts the process of compilation and execution of a

Provides the following features:

Advantages of the .NET Framework

Some advantages of the .NET Framework are:

Is a model used by Visual Basic .NET applications to communicate with a

ADO .NET Data Access

Disconnected data architecture Applications connect to the database only while

Data cached in datasets ADO.NET is based on a disconnected data structure.

Data transfer in XML format ADO.NET uses XML for transferring

Interaction with the database is done through data commands.

ADO.NET Object Model

Components of a Data Provider

read-only and forward-

2.1 Preliminary Investigation

Request clarification: Many requests from employees and users in the

2.2 SYSTEM DEVELOPMENT LIFE CYCLE

SYSTEM LIFE CYCLE

The different phases of software development life cycle is shown

FIG: SHOWING GENERAL LIFE CYCLE PROCESS AND PERCENTAGE OF TIME

The three major parts of the system are:

2.3 FEASIBILITY STUDY

COST AND BENEFIT ANALYSIS

Hardware/Software Costs It includes the cost of purchasing or leasing of

Personnel Costs It is the money spent on the people involved in the