Punjabi University patiala

DEPARTMENT OF COMPUTER SCIENCE

SESSION-2021-2023

MINOR PROJECT OF ASP.NET

ON
College Management System

(MCA 3RD SEM)

SUBMITTED TO:-Mr. AMARVIR SINGH

SUBMITTED BY:-
YADWINDER KAUR(60701)
KOMAL(60737)
RAMANDEEP KAUR(60714)

TABLE OF CONTENTS
 Project Profile

 Project Definition
 Objective & Scope
 Tools & Technology
 Overview of Tools

 Project Management

 Project Management Techniques

 Activity Chart

 System Analysis

 Feasibility Analysis
 Requirement Analysis

 System Design

 Structured Analysis & Design

 DFD
 Data Dictionary

 Input & Output Screen

PROJECT DEFINITION:

Good management helps organization to lead among competitor. Management made our
work silky, made our work trouble-free and speedy. Today’s life is so busy and organizations
have less time for maintaining their important work. So, to make life easy for organizations
we make a small web service for College Management System. It gives facility to do
personal & professional work online easily and speedy.
OBJECTIVE:

College Management System is a full-featured application designed specifically for planning,

managing, and scheduling College’s important dates and times. It runs in the background, sits in
the system tray, and makes it nearly impossible to forget record, entry, scheduling, meetings, and
other important events.

Using this web based application organisation can explain rationale, roles, responsibility for
reviews, performance management cycle, managing weak performance, confidentiality. The
main objective is user convenience College Management System.com provides easy user
interface, simple processing, and easy to use application.

SCOPE OF PROJECT:

College Management System is web applications from which any organization

can manage important work i.e. personal/professional. Organisation work would be
managed by registered user. Administrator can enter record, edit record, and manage
student as well as faculty information. Also user can make group for intercommunication
and can send his/her mail to the selected members of group.
TOOLS & TECHNOLOGY:

FrontEnd Contains:
-- Asp.Net 2.0
BackEnd Contains:
-- Microsoft SQL Server 2005

Overview of Tools:

Front-End
ASP.NET:
ASP.NET provides a unified Web development model that includes the services necessary for
you to build enterprise-class Web applications. ASP.NET is part of the .NET Framework and
enables you to take full advantage of the features of the common language runtime, such as type
safety, inheritance, language interoperability, and versioning.

The topics in this section provide you with conceptual information about how ASP.NET works
and procedural topics that show you how to write code that take advantage of the power of
ASP.NET to create dynamic Web applications.

The following sections describe changes made in different areas of ASP.NET:

1. Web Site Management

2. Page Design
3. Controls
4. Data
5. Security

1. Web Site Management:

Web site configuration is improved to include many more settings. You can easily manage
application settings using the Web Site Administration Tool, which provides a wizard-like
interface for setting up and maintaining your applications. The Web Site Administration Tool is
particularly useful for managing remote sites (for example, sites that are hosted by an ASP.NET-
compatible ISP).

If you host sites for others, you can use a new ASP.NET Microsoft Management Console
(MMC) plug-in or an administrative API to manage sites and monitor their health. You can add
value to your hosting site by offering controls or services that you can selectively enable or
disable.

2. Page Design

New features of ASP.NET help you easily create pages that are more consistent and can offer a
richer experience to users.
 2.1 Consistent Layout using Master Pages

You can use master pages to create a consistent page layout for your Web site or for a group of
related pages. On the master page, you define a common look; you can then create individual
content pages that provide the dynamic content that is displayed using the master page as a
template

2.2 Themes for Consistent Appearance

Themes allow you to create a consistent look for your site. A theme contains a collection of
control skins that define property settings (such as background color and font), CSS style
settings, and images to specify the appearance of a control.

2.3 New Code-Behind Model for Pages

ASP.NET continues to support the single-file model from the previous version of ASP.NET and
now includes a new code-behind model. The new model allows you to use a new .NET
Framework feature, partial classes, to create a code file with just the code in it that you need,
such as event handlers. The end result is a clean separation of the markup from the code in a
page, and a robust model for managing a page’s code.

2.4 Users-Customizable Web Pages

With Web parts, you can create modularized Web pages that users can customize extensively. A
Web part incorporates a discrete piece of functionality, such as a weather report, a stock ticker,
or a window for reading news. ASP.NET allows you to create your own Web parts. You can then
create Web pages that include a selection of Web parts. Using the Web parts architecture, you
can allow users to customize individual Web parts (for example, by typing in a ZIP code to
display local information) and change the layout of Web parts. You can also allow users to add
and remove Web parts, thereby giving users the ultimate flexibility in using your site

3. Control

ASP.NET features many improvements to Web server controls, including both enhancements to
existing controls and a selection of new controls.
 3.1 General Control Improvements

A major area of enhancement in ASP.NET 2.0 is in the controls you use to create ASP.NET Web
pages. General improvements to controls include:

 By default, controls now generate markup that is compatible with the XHMTL 1.1.
Standard.

 All controls support adaptive rendering, and can emit markup that is appropriate for the
requesting browser.

 All data controls can use either the new data-binding model with data source controls, or
can continue to use the model used in earlier versions of ASP.NET.

 All controls support themes and skins so that you can customize their appearance using
an ASP.NET theme

 You can use device filtering with many control properties, specifying different property
values for different devices. When the control is rendered, the appropriate property value
is set based on the requesting browser.

 Validation controls can now be grouped, which allows you to selectively enable
validation for some controls.

 Improvements to individual controls such as the Label control, List Box control, and
others to add functionality often requested by developers

3.2 New Controls

ASP.NET offers a greater selection of controls to help you create fully featured Web pages much
more quickly. You can now take advantage of the following controls:

 Navigation. You can add navigation paths (also known as breadcrumbs) to pages with
the SiteMapPath control and display a site map using the TreeView control.

 Security. You can authenticate users with a suite of login controls that allow you to get
and validate user credentials, display custom output for logged-in users, and more.

 Web Parts. A new set of Web Part controls allow you to create portal pages that users
can personalize at run time. For example, you can create a Web Part that allows a user to
enter a custom value such as a postal code and get localized weather reports.

 Client behavior. New controls provide ASP.NET server control functionality for tasks
that previously was handled only by HTML elements. These include the FileUpload
control, ImageMap control, and the HiddenField control.
 The new Wizard controls allow you to create a page with multiple panels that step the
user through multi-part forms.

In addition, existing ASP.NET controls have been enhanced with new features. All
controls now support the new data-binding model, themes, and personalization.

You can also use all controls to create pages for devices; controls now automatically support
adaptive rendering and device filtering.

4. Data

ASP.NET includes substantially improved support for working with data in your Web
applications.
 4.1 Data Source Controls

For binding data to controls on Web pages, you can now use data source controls, which
encapsulate connections, query commands, and parameters into a single control. ASP.NET
includes data source controls that work with a variety of back-end data sources, including
Microsoft SQL Server, Microsoft Access, XML files, Web services, FrontPage site maps, and
business objects that return data sets. All data source controls support the same basic object
model, giving you a consistent way to work with data regardless of its source.

Data source controls can automatically fetch data and manage it when the page runs. You no
longer need to write code to execute commands and manage datasets for common data scenarios.
However, if your application requires it, you still have access to the lower-level data functions
exposed by ADO.NET.

To pass parameters to data source controls, you can configure the controls to draw parameters
values from other controls, Session state, query strings, or cookies; in addition, you can set
parameter values programmatically.

4.2 Middle-Tier Data Access

By using the new Object Data Source control, you can easily add data access to a page that is
based on a middle-tier business object. The Object Data Source exposes the same binding
interface to controls on the page, but instead of performing direct database access, it invokes
methods on a component that you specify.

4.3 Data Display Controls

ASP.NET also includes enhanced support for displaying and updating data with controls on Web
pages. All controls can now use data source controls as data source instead of working directly
against a dataset or other store. You can also take advantage of the following new controls that
are specifically built to make data access easier:

 The GridView, DetailsView, FormView controls to display and edit data. (The
GridView control supersedes the DataGrid control from previous versions of ASP.NET.)

 The TreeView control to display hierarchical information from XML files, sitemap files,
and relational data sources.

 The SiteMapPath and Menu controls to provide data-bound support for navigation.

4.4 XML Support

You can use XML data in a variety of ways in ASP.NET. An XML data source control exposes
XML data to be used either as hierarchical or tabular data. You can bind a TreeView control to
XML data to provide a hierarchical view for users, or you can bind a list control such as the
GridView control to display XML in a traditional way.

4.5 Connection String Storage

To enhance Web site security, you can store connection strings in a dedicated section of the
configuration file.

5. SECURITY
New ASP.NET features provide built-in support for authenticating and authorizing users.
ASP.NET membership manages authentication, providing facilities for validating user
credentials and helping users manage their passwords.

The membership service provides APIs that you can call programmatically to create new users,
validate credentials, and get user information. To simplify authentication even more, you can use
the new login controls, which work with the ASP.NET membership to perform a variety of tasks,
often with no extra code required. The Login control prompts users for credentials and validates
them. The PasswordRecovery control provides various options for helping users either change or
remember their password. You can display user information with the LoginName control, and
present a Login or Logout button using the LoginStatus control. The LoginView control allows
you to mark content in a page that is visible only to authenticated users.

ASP.NET role management helps you manage authorization, providing high-level ways for you
to define and check roles for users.

Both the membership and role management systems use the new ASP.NET provider model,
which separates the functionality of the systems from the data store that supports them. For
example, membership allows you to store user information in Microsoft SQL Server or
Microsoft Access. If these default options are not suitable for your requirements, you can create
your own provider that accepts calls from membership and then fulfills them using your custom
data logic.

Database Architecture:

Microsoft SQL Server 2005 data is stored in databases. The data in a database is
organized into the logical components visible to users. A database is also physically
implemented as two or more files on disk.

When using a database, you work primarily with the logical components such as tables,
views, procedures, and users. The physical implementation of files is largely transparent.
Typically, only the database administrator needs to work with the physical
implementations
PROJECT MANAGEMENT TECHNIQUES

Project management techniques are used for maintenance of the project, meet the project dead
lines, and minimum effort required from the company employee.

Project Planning

The purpose of Project Planning is to identify the scope of the project, estimate the work
involved, and create a project schedule. Project planning begins with requirements that define the
software to be developed. The project plan is then developed to describe the tasks that will lead
to completion.
Project Monitoring and Control
The purpose of Project Monitoring and Control is to keep the team and management up
to date on the project's progress. If the project deviates from the plan, then the project manager
can take action to correct the problem. Project monitoring and control involves status meetings to
gather status from the team. When changes need to be made, Change control is used to keep the
products up to date.

Software Requirements
Requirements analysis is a term used to describe all the tasks that go into the instigation, scoping
and definition of a new or altered computer system. Requirements analysis is an important part
of the software engineering process; whereby business analysts or software developer identify
the needs or requirements of a client.
ACTIVITY CHART

1 1 1 1 1 1 1
Week 1 2 3 4 5 6 7 8 9
0 1 2 3 4 5 6
1 2 2 1 1 2 1 2 2 1 1 2
Date 3 1 8 5
3 0 7 0 7 4 5 2 9 2 9 6
Month
July August September Octomber
Activity

Analysis
Learning
Process
Design

Coding

Documentation

System Analysis
Feasibility study
Feasibility study is the likelihood the system will be useful to organization. After studying the
requirements, whether the proposed project is feasible or not, is determined by checking the
various feasibilities. The three aspects in the feasibility study portion of preliminary investigation
are:

Technical Feasibility
Technical feasibility corresponds to determination of whether it is technically feasible to
develop the software.
 Necessary technology exists to do what is suggested and required by the
organization.
 The proposed equipments have the technical capacity to hold the data required to
use the new system.
 The software guarantees accuracy, reliability and ease of access and data security.

Economic Feasibility
A system that can be developed and that will be used if installed must still be a good investment
for the organization. Financial benefits must equal or exceed the costs.
The financial and economical issues raised are as under:
 No extra cost is incurred for developing the system. As required software are already
used by the department.
 No extra cost for the modification or addition of software and hardware will require in
case of future expansion of the current system.
Operational Feasibility
Operational feasibility focuses on whether the system will work when it is developed and
installed. Operationally the system is feasible because:
 There is sufficient support for the project from management and user. The system is well
liked and used to the extent that persons will not be able to see reasons for change.
 The current business methods are not acceptable because the manual system is time
consuming. The users though initially repressive worked along with the development
team once the initial doubts were cleared.
 The users have been involved in the planning and development of the project. This
reduces the chances of resistance to the system.
 The proposed system will not cost any harm to the existing system and its users.
 No special training required for the user as it has a self explanatory interface. Validation
of data input is taken care of by the system and not by the user.
Time Schedule Feasibility
Time is the most affecting factor while making a project or a system like this one. The project
should be finished within the assigned time. Otherwise the whole project will be delayed and that
is disastrous for a project developer and project leader also.
Implementation Feasibility
Implementation feasibility is also a very effecting factor while for a new system. The project
manager will check whether the developer can make the project in time with the specified
requirements and best performance. The project leader will also check that the given tools and
technologies to the developer will make the system a success or not.

Requirement Analysis

Software requirement analysis is the activity of eliciting, analyzing and recording requirement
for software system. It shares much in common with requirement analysis for more general kinds
of systems. But has its own specific approaches.

Eliciting Requirement:
Requirement elicitation is the task of communicating with customers and users to determine
what their requirements are.

Analyzing Requirement:
The true analysis part of requirement analysis locates palaces where requirements are unclear,
incomplete or ambiguous. Requirements analysts work with customer representatives to resolve
these issues, sometimes preparing tradeoff studies to compare alternatives. The purpose of
analysis activity is to transform candidate technical requirements into formal requirements by
ensuring that they express the needs of the customer.

Analysis is an iterative activity. The process steps will likely to be repeated several times, with
consultation between customers, end users and developers during each iteration and
communication through the steps.

REQUIREMENTS SPECIFICATION
A software requirements specification (SRS) is a complete description of the behavior of the
system to be developed. It includes a set of use cases that describe all of the interactions that the
users will have with the software. In addition to use cases, the SRS contains functional
requirements and nonfunctional requirements. Functional requirements define the internal
workings of the software: that is, the calculations, technical details, data manipulation and
processing, and other specific functionality that shows how the use cases are to be satisfied.
Nonfunctional requirements impose constraints on the design or implementation (such as
performance requirements, quality standards, or design constraints).

STRUCTURED ANALYSIS AND DESIGN TECHNIQUE

Analysis Methodology

The structured analysis concept employed in the development involved the presentation of
system requirements in an easily derived and documented context. The Data Flow Diagram
(DFD) represents logical decomposition of system requirements they are valuable in providing a
succinct. Readily understood requirements representation, one which is directly communicated to
non programmer system users and one which provides an invaluable pre design analysis tool. E
R diagrams and data dictionaries have been used as system requirement specification devices.

Design methodology

The developments life cycle has effective used powerful software engineering management and
development plans. System design methodology input/process/output charts have been used for
top-down hierarchy charts. Structured design techniques and pseudo code have been used for
system design. Implementations and test phases to ensure adherence to specifications and
completeness of the system. Rigorous configuration control has been employed during the
software enhancement and the maintenance phase. The current production versions are archived
and backed up. Then, the software enhancements are produced and tested independent of the
existing operational system. The updated version implemented after thorough parallel testing and
approval. Documentation for the system has also been maintained under the configuration
management. The changes are tightly controlled to ensure the impact in all areas. The technical
approach followed the parallel chain of each of the approaches through the business planning,
requirement analysis, general design, database design and detailed design.

Data Flow Diagram

Context Diagram

Level 1 Diagram

Process 1.1
 Process 2.1

Process 3.1

DATA DICTIONARY

Admin_Login
Login
Name Type Constaint Description
ID Int P.K. Auto generated ID
Username Varchar(50) User Name
Password Varchar(50) Password of User

This table is used to maintain the information of the user’s login.

Dept
 Department
Name Type Constraint Description
ID Int P.K. Auto generated Dept
ID
ImgUrl varchar(50) Show Path to Choose
Image
Name varchar(50) Department Name
Designation Varchar(50)
Degree Varchar(50)

This table is used to maintain the information of the various Departments.

Faculty_Detail
Faculty
Name Type Constraint Description
ID Int P.K. Auto generated ID of
Faculty
RegNo Varchar(50) Faculty Registration
Number
Name Varchar(50) Name of Faculty/User
LastName Varchar(50) Last Name of
Faculty/User
Password Varchar(50) Require Password to
Login as Faculty
Joining Date Varchar(50) Joining Date Of
Faculty
Birth Date Varchar(50) Birth Date Of Faculty
Department Varchar(50) Department In Which
Faculty Recruited
Post Varchar(50) Post On Which
Faculty Recruited
Contact No Varchar(50) Mobile Number Of
Faculty
Email ID Varchar(50) E-Mail ID Of Faculty
Photo Varchar(50) Photo Link Of Faculty

This table is used to maintain the information of the groups Member of Faculty.

Gallary
 Gallary
Name Type Constraint Description
ID Int P.K. Auto generated ID for
Photo
ImgUrl Varchar(50) Display Path to
Choose Image
Category Varcahr(50) Name of Category for
which this Photo
belongs to

This table is used to maintain the detailed information of various category photo.

Mail
Mail
Name Type Constraint Description
ID Int P.K. Auto generated ID
SuserName varchar(50) Source
DuserName varchar(50) Destination
Message varchar(50) Contain Send To
Member

This table is used to maintain the detailed information of mail facility.

News
Gallary
Name Type Constraint Description
ID Int P.K. Auto generated ID for
Photo
Image Varchar(50) Display Path to
Choose Image
Sdesc Varcahr(50) Small Description
Fdesc Varcahr(50) Full Description

This table is used to maintain the detailed information of desplay events & news.
Registration

Registration
Name Type Constraint Description
ID Int P.K. Auto generated ID of
Faculty
RegNo Varchar(50) Faculty Registration
Number
Name Varchar(50) Name of Faculty/User
LastName Varchar(50) Last Name of
Faculty/User
UserName Varchar(50)
Password varchar(50) Require Password to
Login as Faculty
Category Varchar(50)
Class Varchar(50)
Joining Date Varchar(50) Joining Date Of
Faculty
Birth Date Varchar(50) Birth Date Of Faculty
Department Varchar(50) Department In Which
Faculty Recruited
Post Varchar(50) Post On Which
Faculty Recruited
Contact No Varchar(50) Mobile Number Of
Faculty
Email ID Varchar(50) E-Mail ID Of Faculty
Photo Varchar(50) Photo Link Of Faculty
Status Varchar(50)

This table is used to maintain the detailed information of about the user registration.

Input/Output Screen Design

 Home.aspx

About.aspx
Login.aspx

Gallery.aspx
 Library.aspx

News & Events.aspx

Department.aspx

Mail.aspx
LogOut.aspx