SOFTWARE REQUIREMENT

SPECIFICATION DOCUMENT
ON
TITLE

Year (2010 2014)

Submitted By:
Name(Roll No)
Name(Roll No)

Under the Supervision of

Guide Name
(Designation)

Department of
Information Technology
Department of Information Technology

Mahant Bachittar Singh College of Engineering &

Technology
Babliana, Jeevan Nagar Road, PO Miran Sahib, Jammu-181101.

(University of Jammu)

CERTIFICATE
ABSTRACT [Times New Roman; 16; Bold]
[Times New Roman; 14]

INDEX

[Times New Roman; 16; Bold]

[Times New Roman; 14]

1. INTRODUCTION
Bold]

[Times New Roman; 16;

SUB-HEADINGS
[Times New Roman; 14; Bold]
[Times New Roman; 14]

2. LITERATURE SURVEYED
16; Bold]

[Times New Roman;

TITLE [Times New Roman; 14;Bold]

[Times New Roman; 14]

3. PROBLEM DEFINITION

SUB-HEADINGS

[Times New
Roman; 16;
Bold]

[Times New Roman; 14; Bold]

[Times New Roman; 14]

4. WORK METHODOLOGY AND DESIGN

[Times
New Roman;
16;Bold]
SUB-HEADINGS
[Times New Roman; 14; Bold]
[Times New Roman; 14]

5. IMPLEMENTATION CHALLENGES
Roman; 16; Bold]

[Times New

[Times New Roman; 14]

6. CONCLUSION [Times New Roman; 16; Bold]

[Times New Roman; 14]

7. FUTURE SCOPE
Bold]

[Times New Roman; 16;

[Times New Roman; 14]

REFERENCES
Bold]
[Times New Roman; 14]

[Times New Roman; 16;

Introduction
The aim of our project was to develop a online system for Internal
Assesment which will reduce the manual work to a greater extent.
The aim of our project was to build a dynamic web application that
will enable Different Department to input different internal
assesment marks of students through an online Interface. Previously
the faculty had to manually submit the records thus making the
process time consuming and error prone and the results also got
delayed due to this manual process.
It will provide a secured login
mechanism and the first and foremost feature of this application was
to make it secure as the application involves sensitive data, so high
level of security was needed to be added into the application so that
no unauthorized access to the application is possible and no
tampering of data is done.
The application provides a multi user system and hence will enable
the multiple departments and their faculty to access this application
and make entry of internal assessment. This module being the main
module, will enable users to have access to the student information
and according to the students rollno the faculties can input the
marks.
This system will enable college authorities as well as Controller
office to export data that has been updated by the colleges. The data
once updated from faculty side can be accessed by controller and
exported to merge the data with external marks to create final
result.
The Controller Office Admin will have access to create Streams,
Subjects and the Student data according to various departments.

LITERATURE SURVEYED

Web Based Student Information

Management System
http://www.ijarcce.com/upload/2013/june/4-shobha
%20bharamaoudar-WEB%20BASED%20STUDENT
%20INFORMATION.pdf
Student Information Management System (SIMS) provides a simple interface for maintenance of
student information. It can be used by educational institutes or colleges to maintain the records Of
students easily. The creation and management of accurate, up-to-date information regarding a
students academic career is critically important in the university as well as colleges. Student
information system deals with all kind of student details, academic related reports, college details,
course details, curriculum, batch details, placement details and other resource related details too.
It tracks all the details of a student from the day one to the end of the course which can be used
for all reporting purpose, tracking of attendance, progress in the course, completed semesters,
years, coming semester year curriculum details, exam details, project or any other assignment
details, final exam result and all these will be available through a secure, online interface
embedded in the colleges website. It will also have faculty details, batch execution details,
students details in all aspects, the various academic notifications to the staff and students
updated by the college administration. It also facilitate us explore all the activities happening in
the college, Different reports and Queries can be generated based on vast options related to
students, batch, course, faculty, exams, semesters, certification and even for the entire college.

Creating ASP.NET Web Applications

http://msdn.microsoft.com/en-us/library/ywdtth2f
%28v=vs.71%29.aspx

ASP.NET provides a unified Web development model that includes

the services necessary for you to build enterprise-class Web
applications. While ASP.NET is largely syntax compatible with Active
Server Pages (ASP), it provides a new programming model and
infrastructure that allow you to create a powerful new class of
applications. ASP.NET is part of the .NET Framework and allows you
to take full advantage of the features of the common language
runtime, such as type safety, inheritance, language interoperability,
and versioning.
This section provides you with conceptual information about how
ASP.NET works and procedural topics that show you how to write
code that takes full advantage of the power of this new technology.
In This Section
ASP.NET Platform Requirements
Details the hardware and software needed to work with ASP.NET.
Introduction to ASP.NET
Provides a brief overview of all the ASP.NET technologies.
ASP.NET Application Walkthrough
Provides a sample deployment of an ASP.NET application. The
application demonstrates a directory structure, including virtual roots
and the bin directory, where to store assemblies, and where the
application configuration file resides.
Security Considerations for ASP.NET Web Applications
Provides an introduction to security in Web applications and
explains basic strategies for protecting the application and your
system.
Securing ASP.NET Web Applications
Details how to work with authorization and authentication issues
in ASP.NET Web applications.
Web Forms Pages

Provides information about how to create forms-based Web pages

that are processed on the server.
ASP.NET Server Controls
Introduces the four types of server controls and details how to
create and program them in Web Forms pages.
Developing ASP.NET Server Controls
Provides information about events, implementing properties, state
management, rendering, templates, data binding, post-back data
processing, and so on. This topic also contains samples of complex
controls that perform validation and data binding.
Note
User controls are not described here, but they are
explained in Web Forms User Controls.
ASP.NET State Management
Provides details about how to use application state and session
state in your Web applications.
HTTP Runtime Support
Provides an overview of how to use IHttpModule and IHttpHandler
interfaces. Explains how you can implement and configure custom
HTTP handlers to synchronously or asynchronously process selected
HTTP Web requests. Also discusses how to create custom HTTP
modules that can participate in each request.
ASP.NET Caching Features
Details how the data and output caching mechanisms available
through ASP.NET work, as well as how you can use them to help
optimize the performance of your Web applications.
XML Web Services Created Using ASP.NET and XML Web
Service Clients
Details how to build XML Web services created using ASP.NET and
XML Web service clients. XML Web services are applications that
provide the ability to exchange messages in a loosely coupled
environment using standard protocols such as HTTP, XML, XSD,
SOAP, and WSDL. These communications are interoperable with a
broad variety of implementations, platforms and devices. The SOAPbased XML messages exchanged between an XML Web service and

its clients can have well defined (structured and typed) or loosely
defined parts (using arbitrary XML).
ASP.NET Trace
Describes how to troubleshoot your Web Forms pages and ASP.NET
applications using the built-in TraceContext class. This class provides
methods and properties that allow you to display information about a
Web request in an application-wide trace viewer, or in the requested
page itself.
ASP.NET Optimization
Provides information on how to create Web applications using
ASP.NET that meet your performance requirements.
Side-by-Side Support in ASP.NET
Describes side-by-side support in ASP.NET and explains how to
configure
ASP.NET
applications for
side-by-side
execution.
Applications are said to be running side by side when they are
installed on the same computer but use different versions of the
.NET Framework.
IIS 6.0 Application Isolation Modes
Describes the application isolation modes in IIS 6.0 and explains how
to translate ASP.NET process model settings to application pool
settings.
Related Sections
ASP.NET Syntax
Details the declarative syntax you can use to create ASP.NET files
without the aid of a rapid application development (RAD) designer.
Any ASP.NET feature can be created in text files with the proper file
name extension. These include ASP.NET configuration files
(Web.config), application files (Global.asax), ASP.NET pages (.aspx
files), user controls (.ascx files), and XML Web services (.asmx files).
In addition, this section details the declarative syntax for all the
ASP.NET server controls.
Accessing Data
Outlines how you can access data throughout the .NET
Framework. Included is conceptual information about ADO.NET, the

successor to ActiveX Data Objects (ADO), and details about how to

use it. It also contains information about how to access and use XML
and relational data.
Debugging and Profiling
Explains how to examine and improve the performance of .NETbased applications.
System.Web Namespace
the System.Web namespace, which supplies classes and interfaces
that enable communication between browsers and Web servers.
System.Web.Caching Namespace
the System.Web.Caching namespace, which provides classes for
caching frequently used resources on the server, independent of
page, XML Web service, session, or application.
System.Web.Configuration Namespace
the System.Web.Configuration namespace, which contains classes
that are used to configure ASP.NET.
System.Web.Security Namespace
the System.Web.Security namespace, which contains classes that
are used to implement ASP.NET security in Web server applications.
System.Web.Services Namespace
the System.Web.Services namespace, which consists of the classes
that enable you to create XML Web services using ASP.NET. XML Web
services are applications that provide the ability to exchange
interoperable messages in a loosely coupled environment using
standard protocols such as HTTP, XML, XSD, SOAP and WSDL.
System.Web.Services.Description Namespace
the System.Web.Services.Description namespace, which consists of
the classes that enable you to publicly describe an XML Web service
by using the Web Services Description Language (WSDL).
System.Web.Services.Discovery Namespace
the System.Web.Services.Discovery namespace, which consists of
the classes that allow XML Web service clients to locate the available
XML Web services on a Web server through a process called XML
Web service discovery.
System.Web.Services.Protocols Namespace
the System.Web.Services.Protocols namespace, which consists of the
classes that define the protocols used to transmit data during the
communication between XML Web services created using ASP.NET
and their clients.
System.Web.UI Namespace

the
System.Web.UI
namespace,
which
contains
classes,
enumerations, and interfaces that support visible UI for Web Forms.
System.Web.UI.HtmlControls Namespace
System.Web.UI.HtmlControls classes that allow you to create HTML
server controls on a Web page. HTML server controls run on the
server and map directly to standard HTML tags supported by all
browsers. These classes allow you to programmatically control the
HTML elements on the Web page.
System.Web.UI.WebControls Namespace
System.Web.UI.WebControls classes that allow you to create Web
server controls on a Web page. Web controls run on the server and
include form controls such as buttons and text boxes, as well as
special purpose controls, such as a Calendar. These classes allow you
to programmatically control these elements on a Web page. The Web
controls object model does not necessarily reflect HTML syntax.

Introduction to ASP.NET Web Applications in

Visual Studio
http://msdn.microsoft.com/enus/library/aa711425%28v=vs.71%29.aspx

Visual Studio .NET allows you to create applications that leverage the
power of the World Wide Web. This includes everything from a
traditional Web site that serves HTML pages, to fully featured
business applications that run on an intranet or the Internet, to
sophisticated business-to-business applications providing Web-based
components that can exchange data using XML.
This topic provides an overview of the types of Web applications you
can create in Visual Studio, how they relate to one another and to
other Visual Studio technologies, and suggestions about where to
learn more about the types of Web applications you want to create.
Note
For details about the relative advantages of Web
applications and Windows applications, see Windows Forms and Web
Forms Recommendations.

Visual Studio ASP.NET Web Applications

A Visual Studio Web application is built around ASP.NET. ASP.NET is a

platform including design-time objects and controls and a run-time
execution context for developing and running applications on a
Web server.
ASP.NET in turn is part of the .NET Framework, so that it provides
access to all of the features of that framework. For example, you can
create ASP.NET Web applications using any .NET programming
language (Visual Basic, C#, Managed Extensions for C++, and many
others) and .NET debugging facilities. You access data using
ADO.NET. Similarly, you can access operating system services
using .NET Framework classes, and so on.
ASP.NET Web applications run on a Web server configured with
Microsoft Internet Information Services (IIS). However, you do not
need to work directly with IIS. You can program IIS facilities using
ASP.NET classes, and Visual Studio handles file management tasks
such as creating IIS applications when needed and providing ways
for you to deploy your Web applications to IIS.
Where Does Visual Studio Fit In?
As with any .NET application, if you have the .NET Framework, you
can create ASP.NET applications using text editors, a command-line
compiler, and other simple tools. You can copy your files manually to
IIS to deploy the application.
Alternatively, you can use Visual Studio. When you use Visual Studio
to create Web applications, you are creating essentially the same
application that you could create by hand. That is, Visual Studio does
not create a different kind of Web application; the end result is still
an ASP.NET Web application.
The advantage of using Visual Studio is that it provides tools that
make application development much faster, easier, and more
reliable. These tools include:
Visual designers for Web pages with drag-and-drop controls and
code (HTML) views with syntax checking.

Code-aware editors that include statement completion, syntax

checking, and other IntelliSense features.
Integrated compilation and debugging.
Project management facilities for creating and managing
application files, including deployment to local or remote servers.
If you have used Visual Studio before, these kinds of features will
seem familiar, because they are similar to features that you get for
creating applications in previous versions of Visual Basic and Visual
C++. With Visual Studio .NET you can use these kind of features to
create ASP.NET Web applications.
Elements of ASP.NET Web Applications
Creating ASP.NET Web applications involves working with many of
the same elements you use in any desktop or client-server
application. These include:
Project management features When creating an ASP.NET Web
application, you need to keep track of the files you need, which ones
need to be compiled, and which need to be deployed.
User interface Your application typically presents information to
users; in an ASP.NET Web application, the user interface is presented
in Web Forms pages, which send output to a browser. Optionally, you
can create output tailored for mobile devices or other Web
appliances.
Components
Many applications include reusable elements
containing code to perform specific tasks. In Web applications, you
can create these components as XML Web services, which makes
them callable across the Web from a Web application, another XML
Web service, or a Windows Form, for example.
Data
Most applications require some form of data access. In
ASP.NET Web applications, you can use ADO.NET, the data services
that are part of the .NET Framework.
Security, performance, and other infrastructure features As in
any application, you must implement security to prevent
unauthorized use, test and debug the application, tune its
performance, and perform other tasks not directly related to the
application's primary function.

The following diagram provides an overview of how the pieces of

ASP.NET Web applications fit together and fit into the broader
context of the .NET Framework.
Aa711425.aspnet_frameworkbmp(en-us,VS.71).gif
The sections below outline the different elements of an ASP.NET Web
application and provide links to more information about how to work
with each element in Visual Studio.
Overview: ASP.NET
The information in this topic provides only an introduction to
ASP.NET. For details about what ASP.NET is and what components are
involved in an ASP.NET application, see Introduction to ASP.NET.
Project Management: ASP.NET Web Application Projects and
Deployment
To work with an ASP.NET Web application using Visual Basic or Visual
C#, you use the ASP.NET Web Application project template. As with
other Visual Studio projects, a Web application project is a central
repository for all the information required to design, run, and
manage the application.
When you create a Web application project, Visual Studio creates the
necessary files and folders on the server, sets the appropriate
security settings on them, and creates the IIS application. For details,
see ASP.NET Web Application Template.
Each Web application can maintain a Web.config file that follows the
format and conventions of .NET configuration files. In ASP.NET, the
configuration file allows you to establish project-specific settings for
security, compilation options, tracing, error handling, and more.
For details about how to create and manage ASP.NET Web
application projects in Visual Studio, see the following topics.
Working with Web Projects Provides links to topics that describe
Web application projects in Visual Studio.
Web Forms Pages and Projects in Visual Studio Provides details
about the types of files created in a Web Application project.

Deployment of a Web Setup Project Provides an introduction to

deploying Web applications.
ASP.NET Configuration Describes the configuration file system
and provides links to topics about the contents of the Web.config file.
User Interface: Web Forms and the ASP.NET Page Framework
You can create HTML pages and Web Forms pages as the user
interface for your application. HTML pages are generally used for
static content. In contrast, Web Forms pages give you a
programmable interface that works much like a Visual Basic form,
except that the user interface is rendered in a Web browser or other
Web device.
Note You can use a Windows Form as the user interface in an
application that calls XML Web services. For an example, see
Walkthrough: Creating a Distributed Application.
Web Forms pages are built on the ASP.NET Page framework. Each
Web Forms page is an object that derives from the ASP.NET Page
class, which acts as a container for controls. The page actually
consists of two files: an .aspx file that contains the UI elements
(static HTML text and control elements) and a class file that contains
the code that runs the page. For details, see Introduction to Web
Forms Pages.
When users request a Web Forms page, the Page framework runs the
Web Forms page object and all the individual controls on it. The
output of the Page class and of the controls is HTML. For details, see
Web Forms Page Processing.
Because the Web is inherently stateless by default, components in
a Web application are alive only long enough to process a single
request Web applications face challenges in preserving values as
the user works with the application. To help, the Page framework
includes facilities for managing state. These include page-based
"view state" (a method for preserving values in controls) and access
to non-page-based state facilities such as Session state (userspecific) and Application state (global to the application). For details,
see Web Forms State Management.

The Page framework supports a set of controls you can use to

program user interaction with your Web Forms pages. User actions in
the form are captured and processed by the Page framework in a
way that lets you treat them as standard events. You can choose
from a large selection of controls available in Visual Studio. In
addition, you can create your own custom controls. For details, see
Introduction to Web User Controls and Developing ASP.NET Server
Controls.
Note You can also create output for mobile devices. To do so, you
use the same ASP.NET page framework, but you create Mobile Web
Forms instead of Web Forms pages and use controls specifically
designed for mobile devices. For details, see Creating ASP.NET Mobile
Wep Applications.
For details about Web Forms pages and how to work with them in
Visual Studio, see the following topics:
Web Forms Pages Lists topics that provide an overview of Web
Forms, including background on ASP.NET and on the Web Forms code
model.
Creating and Managing Web Forms Pages Provides information on
how to create, add, and manage Web Forms pages.
Programming Web Forms Provides information on the specific
aspects of programming in a Web Forms environment.
Web-based Components: XML Web Services
An XML Web service is a component that can be called over a TCP/IP
network by other applications. It performs a specific function
anything from calculations and credit card validation to complex
order processing and returns values to the calling application.
What makes XML Web services unique is that they can be called
across the Web. XML Web services are invoked using HTTP or SOAP
requests and exchange data with other components using XML. As
such, they can form an integral part of ASP.NET Web applications,
providing services not only to your applications, but also to any

application that has Web access, making them ideal for business-tobusiness transactions.
For information about XML Web Services, how they work with
ASP.NET applications, and how you can create them in Visual Studio,
see Programming the Web with XML Web Services.
Web Application Data Access
Most ASP.NET Web applications involve at least some level of access
to data. ASP.NET does not directly include data access facilities.
Instead, Web applications use ADO.NET data services.
ADO.NET provides a complete framework for accessing and
managing data from a variety of sources, including databases and
XML files or streams. ADO.NET includes providers classes that
allow you to connect to data sources, execute commands, and read
results. You can optionally keep data in a dataset, which is a
disconnected, in-memory cache.
Data access in Web applications, whether in a Web Forms page or an
XML Web service, introduces special challenges:
Statelessness The components of Web applications usually do
not preserve state, which makes it impractical to maintain live
connections to a data source (or other resources).
Scalability Because Web applications can have user loads that
vary substantially over short periods of time, data access has to be
designed with scalability in mind.
Visual Studio provides a variety of tools for working with data,
including Toolbox support for data elements, various configuration
wizards, and so on. The following topics provide information on data
in general that is, ADO.NET as well as about using data in Web
applications.
Introduction to Data Access with ADO.NET
Provides general
information on the design of ADO.NET and some implications of the
ADO.NET model for application development.
Introduction to Data Access in Web Forms Pages
Provides an
overview of data access in Web applications, including information

about some of the common issues associated with Web application

data access.
Web Application Infrastructure: Security, Performance, and More
In addition to giving you the means to create user interface elements
and callable components, ASP.NET provides a context for those
elements to run in. For example, ASP.NET communicates with IIS to
handle requests for Web Forms pages and XML Web services, parse
the files, call related components, and so on.
Much of this work occurs beneath the surface, at a level where you
do not typically need to program when you are creating desktop
applications.
Note
Visual Studio provides limited support for working with
ASP.NET infrastructure features. For example, you can edit the Web
application configuration file (Web.config) using the Visual Studio
Code Editor. But the .NET Framework is both pluggable and
extensible, providing you with low-level access if necessary.
There are other aspects of Web applications that you must often
contend with that are part of the application's infrastructure. These
include:
Security You frequently have to authenticate and authorize users
of your Web application. There are special problems associated with
security in a Web application, because users are getting access to
server-based resources and because you have very little control over
the client side of the application (the browser or mobile device).
ASP.NET includes security features that you can configure and
program against in your Web application.
Performance and optimization You can tune your application's
performance by caching pages and data. ASP.NET maintains an
output cache that stores pages that have been requested before; by
specifying caching settings, you can control how long pages are
cached and under what circumstances they are refreshed.
Tracing Because Web applications run on the server often a
remote server they do not have output other than the application
output (a Web Forms page, for example). ASP.NET therefore gives

you the opportunity to include trace information directly in a Web

Forms page. For details about adding tracing to ASP.NET Web
applications, with links to topics that address specific trace
procedures

Problem Definition
Our Project aim is to develop an Internal Assessment System for our College. To
Develop such portal we need to choose a Platform which will enable us integrate all such
features into one platform for that very purpose we chose our Microsoft.Net as our
Development Platform. The application will use Microsoft ASP.NET as Front End and
Microsoft SQL Server as Back End.
Existing System
In the existing system, the colleges had to manually submit the assessment records thus making the
process time consuming and error prone and the results also got delayed due to this manual process.

Work Methodology
The Project will be developed in phased or modular manner and will have different modules which
can be defined below:

Secured Login Mechanism

Multi User System
Entry System
Reporting System
Master Creation

The project will be developed in two phases i.e. the development phase and deployment
phase.
Development phase
It consists of following phases:
1.
2.
3.
4.

Database design
Template design
Database Design
Logical Coding

Deployment phase
The portal will be uploaded and configured on the Web server so that it can be accessed
across the network.
The Project will be created as an web application, with following features:
Secured Login Mechanism: This first and foremost feature of this
application is to make it secure as the application involves sensitive
data, high level of security needs to be added into the application so
that no unauthorized access to the application is possible and no

tampering of data is done.

Multi User System: The application will have a multiuser system
which will enable it multiple colleges to access this application and

make entry of internal assessment.

Entry System: This module being the main module, will enable users
to have access to the student information and according to the students

rollno the college authorities can input the internal assessment marks.
Reporting System: This system will enable college authorities as well
Controller office to export data that has been updated by the colleges.
The data once updated from college side can be accessed by controller

and exported to merge the data with external marks to create final

result.
Master Creation: This will allow Controller Office to create Streams,
Subjects and the Student data according to various colleges.

Userwise Project Functionality

Our system will contain following Users :
Admin Module
College Admin Module
Faculty Module
The admin is able to perform following Functions:

Create/Manage Department Logins : Through this module the admin can

create as well as edit the login details of Department admin.

Create/Manage Courses : This Module enables the admin to add new courses.
The admin can also edit/delete the existing courses.

Create/Manage Subjects : The admin can upload new subject and can also edit
or delete the existing subjects using this module.

View Reports : The Admin can view different marks reports uploaded by faculty.

SMS/E-Mail : The Admin can send any kind of information alerts through SMS
or via E-Mail .

The Department admin is able to perform following Functions:

Create/Manage Faculty Profile : Through this module the college admin can
create as well as edit or delete the profile of their faculty Member.

Assign Subjects : The admin can assign subject to any of the existing Faculty and
can also remove the assigned Subject using this Module.

Add Student Records : The college admin can add student Details through this
module . the college admin can also edit/delete the student details if required.

View Reports : The college admin can view marks uploaded by the faculty.

The Faculty is able to perform following Functions:

Manage Marks : This module is used to upload/edit or delete marks of students.

1.2.4.1

Data Flow Diagrams

A Data Flow Diagram (DFD) is a graphical tool used to describe and analyze the
movement of data through a system manual or automated including the processes,
stores of data and delays in the system. They are central tools and the basis from which
other components are developed. It depicts the transformation of data from input to
output through processes and the interaction between processes.
Transformation of data from input to output through processes logically and independent
of physical components is called the DFD. The physical DFD shows the actual
implementation and movement of data between people, departments and workstation.
DFDs are an excellent mechanism of communicating with the customers during
requirement analysis and are widely used for representing external and top-level internal
design specification. In the Later situations, DFDs are quite valuable for establishing
naming conventions and names of system components such as subsystems, files and data
links.
In a DFD there are four components:
1. Sources or Destinations of data such as human, entities that interact with
system, outside the system boundary, who form the source and the recipient
of information are depicted in the form of a closed rectangle.
2. Data flow is a packet of data. It identifies data flow. It is a pipeline through
which information flows. It is depicted in DFD as an arrow with the pointer
pointing in the direction of flow. This connecting symbol connects an entity,
process and data stores. This arrow mark also specifies the sender and the
receiver.

3. Process depicts procedure, function or module that transform input data into
output data. It is represented as a circle or a bubble with the procedure name
and a unique number inside the circle.
4. Data stores are the physical areas in the computers hard disk where a group
of related data is stored in the form of files. They are depicted as an openended rectangle. The Data store is used either for storing data into the files or
for reference purpose.

Level-0 DFD

Level-1 DFD for College ADMIN

Level-1 DFD for Admin

Level-1 DFD for College Faculty

Implementation Challenges
The implementation challenge that are involved into this Project are:
1. Secure Login Authentication: To make this Web Application Secure
we need to make a highly secure login authentication, for that pupose
we plan to use encryption for passwords and getting user IP Address
on every login attempt.
2. Muti level Informational Flow: Using this mechanism we plan to
introduce multi level informational flow, so that information can
easily flow from one user to another and there should be no duplicacy
or disparency.
3. Network Support: Since we plan to use this application through out
the college, we need to implement it across the network using a client
server architecture.

Conclusion
All aspects of internal assement automation system were
studied and a detailed analysis was carried out on how the
application can shaped up and developed as per the
parameters.
The application with all modules will be developed in
Microsoft.net with ASP.net as front end and SQL Server as
the Back End.

Future Scope
1. The System can be integrated with the universities
information system so that the marks that are fed into
the system are directly exported to the university at one
button click and the entire process gets completely
automated.
2. The system can have Parent module which can send
alerts to the parents regarding their wards progress in
the internal assessment.
3. The
Internal
Marks
of
Attendance
can
be
automatically calculated based on no. of classes
attended by the student and can be integrated with a
biometric attendance system for more automation.