Você está na página 1de 81

1.

INTRODUCTION

1.1 GENERAL INTRODUCTION

“Information system is a generic reference to a technology-based system that does two things:
providing information processing capabilities and providing information people need to make
better, more informed decisions”. “Management Information system is a computer-based system
that optimizes the collection, transfer and presentation of information throughout an organization by
using an integrated structure of databases and information flow”.

Management Information Systems are information systems, typically computer based that are
used within an organization comprising of all the components that collect, manipulate, and
disseminate data or information. It usually includes hardware, software, people, communications
systems and the data itself. Management Information Systems defined a system as “A set of
interacting components that operate together to accomplish a purpose”.

Advantages of MIS:

• MIS Facilitates planning.


• Minimizes information overload.
• Encourages Decentralization.
• MIS brings Co ordination.
• MIS assembles, process, stores, retrieves, evaluates and disseminates the
information.

1.2 MIS FOR AEC

The idea of developing an Information System for the college came to light when the
management of the college started experiencing some major difficulties in record-keeping,
searching for records, querying, sorting of data, performing calculations and manipulations of data,
insufficient spaces for filing cabinets, irregularities in collection and keeping records of tuition fees,
difficulties in keeping records of present and past students, is management/embezzlement of fees
and funds, etc. This gave rise to the development of an automated Information Systems for the
college. All organizations require information for planning, controlling, recording transactions,
A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM
performance measurement and decision-making. Management Information Systems convert data
from internal and external sources into information, and communicates that information in an
appropriate form to managers at all levels. This enables them to make timely and effective
decisions. It is an web based application .This is developed to be user friendly. It has various
advantages like, it is easy to add the student fee details, to update the fee details, to communicate
with students of the college, and important details can be maintained in an easier way. Here the
student can interact with Principal and accountant in a similar manner as when they meet face-to-
face.

The Accountant & Principal registers students when they are studying in the college in order to
maintain the record of their fee details. All the details of the students are maintained in the
repository..Accountant prepares fee receipts, payment voucher and balance sheet in order to
maintain details of money inflow and outflow of college.

The Principal, accountant and student can interact with one another without meeting by posting
remainders and request. The Principal and accountant can update the fee related details of student in
the repository such as their bus fee, tuition fee etc. The principal and accountant task in tracking the
list of defaulters becomes easy by using this system. The system provides flexibility in obtaining the
summary report of fee branch wise as well as year wise.
The student can interact with the Principal and the accountant of the college. The student can
post their request regarding the delay in fee payment due to some reason and ask for the permission
in this regard from the Principal and also impose query related to fee to both principal and
accountant. Hence in this manner they can interact with one another online without the necessity of
meeting face-to-face. This has various advantages like user friendly, less time consuming and easy
maintenance. Hence in this manner MIS is very useful for the college management which helps
them in making timely and effective decisions.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


2. LITERATURE SERVY

These literatures are dealt with the environment in which the project is executed and the
technology required to perform the complete operations.

2.1 ADVANTAGES OF .NET OVER OTHER LANGUAGES:


1) It is a user friendly one have to only click and drag the controls on the form events is
automatically generated. .
2) It is faster development environment to create application easily.
3).Net 2005 reduces the code up to 70% because of its build in controls.
4) One can easily developed the application with less effort compare to java.
5) .Net is Language independent, so if the team has multiple skill expertise C#, VB.NET, C++ ,
developers can still work on the same project with different skill set. .
6) Deployment is very easy and simple.

2.2 DOT NET FRAMEWORK

The .NET Framework is a new computing platform that simplifies application development
in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the
following objectives:

• To provide a consistent object-oriented programming environment whether object code is


stored and executed locally, executed locally but Internet-distributed, or executed remotely.
• To provide a code-execution environment that minimizes software deployment and
versioning conflicts.
• To provide a code-execution environment that guarantees safe execution of code, including
code created by an unknown or semi-trusted third party.
• To provide a code-execution environment that eliminates the performance problems of
scripted or interpreted environments.
• To make the developer experience consistent across widely varying types of applications,
such as Windows-based applications and Web-based applications.
• To build all communication on industry standards to ensure that code based on the .NET
Framework can integrate with any other code.

2.2.1 DOT NET ARCHITECTURE

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Microsoft .NET consists of four major components:

• Common Language Specification (CLS)


• Framework Class Library (FCL)
• Common Language Runtime (CLR)
• .NET Tools

At the base of the diagram in gray is the operating system, which technically can be any platform
but typically is Microsoft Windows 2000 or greater, accessed through the Win32 API (Application
Programming Interface).

2.2.1.1Common Language Specification (CLS)

The CLS is a common platform that integrates code and components from multiple .NET
programming languages. In other words, a .NET application can be written in multiple
programming languages with no extra work by the developer (though converting code between
languages can be tricky).

.NET includes new object-oriented programming languages such as C#,Visual basic.net,J# (a Java
clone) and Managed C++. These languages, plus other experimental languages like F#, all compile
to the Common Language Specification and can work together in the same application.

2.2.1.2 Framework Class Library (FCL)

The FCL is a collection of over 7000 classes and data types that enable .NET applications to read
and write files, access databases, process XML, display a graphical user interface, draw graphics,

2.2.2 FEATURES OF .NET FRAMEWORKS

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


• Easier and quicker programming
• Reduced amount of code
• Declarative programming model
• Richer server control hierarchy with events
• Larger class library
• Better support for development tools

2.3 DOT NET DATABASE CONNECTIVITY (ADO.NET)

ADO.NET uses a multilayered architecture that revolves around a few key concepts, such as
Connection, Command, and Dataset objects. However, the ADO.NET architecture is quite a bit
different from classic ADO.

One of the key differences between ADO and ADO.NET is how they deal with the challenge
of different data sources. In ADO, programmers always use a generic set of objects, no matter what
the underlying data source is. For example, if you want to retrieve a record from an Oracle database,
you use the same Connection class you would use to tackle the same task with SQL Server. This
isn’t the case in ADO.NET, which uses a data provider model.

ADO.NET Data Providers

A data provider is a set of ADO.NET classes that allows you to access a specific database,
execute SQL commands, and retrieve data. Essentially, a data provider is a bridge between your
application and a data source.

The classes that make up a data provider include the following:

o Connection: You use this object to establish a connection to a data source.


o Command: You use this object to execute SQL commands and stored procedures.
o Data Reader: This object provides fast read-only, forward-only access to the data
retrieved from a query.
o Data Adapter: This object performs two tasks. First, you can use it to fill a Dataset
(a disconnected collection of tables and relationships) with information extracted
from a data source. Second, you can use it to apply changes to a data source,
according to the modifications you’ve made in a Dataset.
o ADO.NET doesn’t include generic data provider objects. Instead, it includes
different data providers specifically designed for different types of data sources.
Each data provider has a specific implementation of the Connection, Command,
DataReader and DataAdapter classes that’s optimized for a specific RDBMS
(Relational database management system). For example, if you need to create a
connection to a SQL Server database, you’ll use a connection class named SQL
Connection.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


One of the key underlying ideas of the ADO.NET provider model is that it’s extensible. In
other words, developers can create their own provider for proprietary data sources. In fact,
numerous proof-of-concepts examples are available that show how you can easily create custom
ADO.NET providers to wrap no relational data stores, such as the file system or a directory service.
Some third-party vendors also sell custom providers for .NET.

The .NET Framework is bundled with a small set of four providers:

o SQL Server Provider: Provides optimized access to a SQL Server database


(version 7.0 or later).
o OLEDB Provider: Provides access to any data source that has an OLEDB driver.
This includes SQL Server databases prior to version 7.0.
o Oracle Provider: Provides optimized access to an Oracle database (version 8i or
later).
o ODBC Provider: Provides access to any data source that has an ODBC driver.

2.4 ASSEMBLIES OVERVIEW:

Assemblies are a fundamental part of programming with the .NET Framework. An


assembly performs the following functions:

• It contains code that the common language runtime executes. Microsoft intermediate
language (MSIL) code in a portable executable (PE) file will not be executed if it does not
have an associated assembly manifest. Note that each assembly can have only one entry
point
• It forms a security boundary. An assembly is the unit at which permissions are requested and
granted. For more information about security boundaries as they apply to assemblies, see
Assembly Security Considerations
• It forms a type boundary. Every type's identity includes the name of the assembly in which it
resides. A type called MyType loaded in the scope of one assembly is not the same as a type
called MyType loaded in the scope of another assembly.

It forms a reference scope boundary. The assembly's manifest contains assembly metadata that is
used for resolving types and satisfying resource requests. It specifies the types and resources that
are exposed outside the assembly. The manifest also enumerates other assemblies on which it
depends.

2.5 THE TECHNOLOGY USED -ASP.NET

ASP.NET is a server side scripting technology that enables scripts (embedded in web pages) to be
executed by an Internet server.

• ASP.NET is a Microsoft Technology


• ASP stands for Active Server Pages
A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM
• ASP.NET is a program that runs inside IIS
• IIS (Internet Information Services) is Microsoft's Internet server
• IIS comes as a free component with Windows servers
• IIS is also a part of Windows 2000 and XP Professional

2.5.1 What is an ASP.NET File?

• An ASP.NET file is just the same as an HTML file


• An ASP.NET file can contain HTML, XML, and scripts
• Scripts in an ASP.NET file are executed on the server
• An ASP.NET file has the file extension ".aspx"

2.5.2 How Does ASP.NET Work?

• When a browser requests an HTML file, the server returns the file
• When a browser requests an ASP.NET file, IIS passes the request to the ASP.NET engine
on the server
• The ASP.NET engine reads the file, line by line, and executes the scripts in the file.
• Finally, the ASP.NET file is returned to the browser as plain HTML.

2.5.3 Advantages of ASP.NET

• Better language support


• Programmable controls
• Event-driven programming
• XML-based components
• User authentication, with accounts and roles
• Higher scalability
• Increased performance - Compiled code
• Easier configuration and deployment
• Not fully ASP compatible

i)Language Support

ASP.NET uses ADO.NET.

ASP.NET supports full Visual Basic, not VBScript.

ASP.NET supports C# (C sharp) and C++.

ASP.NET supports JScript.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


ii) ASP.NET Controls

ASP.NET contains a large set of HTML controls. Almost all HTML elements on a page can be
defined as ASP.NET control objects that can be controlled by scripts.

ASP.NET also contains a new set of object-oriented input controls, like programmable list-boxes
and validation controls.

A new data grid control supports sorting, data paging, and everything you can expect from a dataset
control.

iii) Event Aware Controls

All ASP.NET objects on a Web page can expose events that can be processed by ASP.NET
code.Load, Click and Change events handled by code makes coding much simpler and much better
organized.

iv) ASP.NET Components

ASP.NET components are heavily based on XML. Like the new AD Rotator, that uses XML to
store advertisement information and configuration.

v) User Authentication

ASP.NET supports form-based user authentication, cookie management, and automatic redirecting
of unauthorized logins.

vi) User Accounts and Roles

ASP.NET allows user accounts and roles, to give each user (with a given role) access to different
server code and executables.

vii) High Scalability

Much has been done with ASP.NET to provide greater scalability.Server-to-server communication
has been greatly enhanced, making it possible to scale an application over several servers. One
example of this is the ability to run XML parsers, XSL transformations and even resource hungry
session objects on other servers.

viii) Compiled Code

The first request for an ASP.NET page on the server will compile the ASP.NET code and keep a
cached copy in memory. The result of this is greatly increased performance.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


ix)) Easy Configuration

Configuration of ASP.NET is done with plain text files.Configuration files can be uploaded or
changed while the application is running. No need to restart the server. No more metabase or
registry puzzle.

x) Easy Deployment

No more server-restart to deploy or replace compiled code. ASP.NET simply redirects all new
requests to the new code.

xi) Compatibility

ASP.NET is not fully compatible with earlier versions of ASP, so most of the old ASP code will
need some changes to run under ASP.NET.To overcome this problem, ASP.NET uses a new file
extension ".aspx". This will make ASP.NET applications able to run side by side with standard ASP
applications on the same server.

2. 6 THE PROGRAMMING LANGUAGES USED

2.6.1 VB.NET:
Visual Basic .NET (VB.NET) is an object-oriented computer programming language that can be
viewed as an evolution of Microsoft’s Visual Basic (VB) which is generally implemented on the
Microsoft .NET Framework.

Visual Basic.net Is Object Oriented


Visual Basic Programs Are Event Driven

2.6.2 JAVASCRIPT:

2.6.2.1 What is JavaScript?

• JavaScript was designed to add interactivity to HTML pages


• JavaScript is a scripting language
• A scripting language is a lightweight programming language
• JavaScript is usually embedded directly into HTML pages
• JavaScript is an interpreted language (means that scripts execute without preliminary
compilation)
• Everyone can use JavaScript without purchasing a license.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


2.6.2.2 What can a JavaScript do?

• JavaScript gives HTML designers a programming tool - HTML authors are normally not
programmers, but JavaScript is a scripting language with a very simple syntax! Almost
anyone can put small "snippets" of code into their HTML pages
• JavaScript can put dynamic text into an HTML page - A JavaScript statement like this:
document.write("<h1>" + name + "</h1>") can write a variable text into an HTML page
• JavaScript can react to events - A JavaScript can be set to execute when something happens,
like when a page has finished loading or when a user clicks on an HTML element
• JavaScript can read and write HTML elements - A JavaScript can read and change the
content of an HTML element
• JavaScript can be used to validate data - A JavaScript can be used to validate form data
before it is submitted to a server. This saves the server from extra processing
• JavaScript can be used to detect the visitor's browser - A JavaScript can be used to detect the
visitor's browser, and - depending on the browser - load another page specifically designed
for that browser
• JavaScript can be used to create cookies - A JavaScript can be used to store and retrieve
information on the visitor's computer.

2.6.3 HTML:
HTML, short for Hyper Text Markup Language, to publish information for global distribution,
one needs a universally understood language, a kind of publishing mother tongue that all
computers may potentially understand. The publishing language used by the World Wide Web
is HTML (from Hypertext Markup Language).

HTML gives authors the means to:


1) Publish online documents with headings, text, tables, lists, photos, etc.
2) Retrieve online information via hypertext links, at the click of a button.
3) Design forms for conducting transactions with remote services, for use in searching for
information, making reservations, ordering products, etc.
4) Include spread-sheets, video clips, sound clips, and other applications directly in their
documents.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


2.7 CRYSTAL REPORTS:

Crystal Reports for Visual Basic .NET is the standard reporting tool for Visual Basic.NET; it
brings the ability to create interactive, presentation-quality content — which has been the strength
of Crystal Reports for years — to the .NET platform.

With Crystal Reports for Visual Basic.NET, you can host reports on Web and Windows
platforms and publish Crystal reports as Report Web Services on a Web server.

To present data to users, you could write code to loop through recordsets and print them inside
your Windows or Web application. However, any work beyond basic formatting can be
complicated: consolidations, multiple level totals, charting, and conditional formatting are difficult
to program.

With Crystal Reports for Visual Studio .NET, you can quickly create complex and professional-
looking reports. Instead of coding, you use the Crystal Report Designer interface to create and
format the report you need. The powerful Report Engine processes the formatting, grouping, and
charting criteria you specify.

Report Experts

Using the Crystal Report Experts, you can quickly create reports based on your development
needs:

• Choose from report layout options ranging from standard reports to form letters, or build
your own report from scratch.
• Display charts that users can drill down on to view detailed report data.
• Calculate summaries, subtotals, and percentages on grouped data.
• Show TopN or BottomN results of data.
• Conditionally format text and rotate text objects.

2.8 DEVELOPMENT ENIVORNMENT-VISUAL STUDIO .NET

Visual Studio .NET is a complete set of development tools for building ASP Web applications,
XML Web services, desktop applications, and mobile applications In addition to building high-
performing desktop applications, user can use Visual Studio's powerful component-based

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


development tools and other technologies to simplify team-based design, development, and
deployment of Enterprise solutions.

Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same integrated development
environment (IDE), which allows
to share tools and facilitates in the creation of mixed-language solutions. In addition, these
languages leverage the functionality of the .NET Framework and simplify the development of ASP
Web applications and XML Web services.

Visual Studio supports the .NET Framework, which provides a common language runtime and
unified programming classes; ASP.NET uses these components to create ASP Web applications and
XML Web services. Also it includes MSDN Library, which contains all the documentation for these
development tools.

2.9 BACKEND-SQLSERVER :

Microsoft SQL Server is a Structured Query Language (SQL) based, client/server relational
database. Each of these terms describes a fundamental part of the architecture of SQL Server.

Database is similar to a data file in that it is a storage place for data. Like a data file, a database
does not present information directly to a user; the user runs an application that accesses data from
the database and presents it to the user in an understandable format.

A database typically has two components: the files holding the physical database and the
database management system (DBMS) software that applications use to access data. The DBMS is
responsible for enforcing the database structure, including:
• Maintaining the relationships between data in the database.
• Ensuring that data is stored correctly, and that the rules defining data relationships are not
violated.
• Recovering all data to a point of known consistency in case of system failures.

Relational Database
There are different ways to organize data in a database but relational databases are one of the
most effective. Relational database systems are an application of mathematical set theory to the
problem of effectively organizing data. In a relational database, data is collected into tables (called
relations in relational theory).
When organizing data into tables, you can usually find many different ways to define
tables. Relational database theory defines a process, normalization, which ensures that the set of
tables you define will organize your data effectively.
Client/Server

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


In a client/server system, the server is a relatively large computer in a central location that manages
a resource used by many people. When individuals need to use the resource, they connect over the
network from their computers, or clients, to the server.

Examples of servers are: In a client/server database architecture, the database files and DBMS
software reside on a server. A communications component is provided so applications can run on
separate clients and communicate to the database server over a network. The SQL Server
communication component also allows communication between an application running on the
server and SQL Server.

Server applications are usually capable of working with several clients at the same time. SQL
Server can work with thousands of client applications simultaneously. The server has features to
prevent the logical problems that occur if a user tries to read or modify data currently being used by
others. While SQL Server is designed to work as a server in a client/server network, it is also
capable of working as a stand-alone database directly on the client. The scalability and ease-of-use
features of SQL Server allow it to work efficiently on a client without consuming too many
resources.

Structured Query Language (SQL)


To work with data in a database, you must use a set of commands and statements (language)
defined by the DBMS software. There are several different languages that can be used with
relational databases; the most common is SQL. Both the American National Standards Institute
(ANSI) and the International Standards Organization (ISO) have defined standards for SQL. Most
modern DBMS products support the Entry Level of SQL-92, the latest SQL standard (published in
1992).

2.9.1 SQL Server Features


Microsoft SQL Server supports a set of features that result in the following benefits:

Ease of installation, deployment, and use


SQL Server includes a set of administrative and development tools that improve your ability to
install, deploy, manage, and use SQL Server across several sites.

Scalability
The same database engine can be used across platforms ranging from laptop computers running
Microsoft Windows® 95/98 to large, multiprocessor servers running Microsoft Windows NT®,
Enterprise Edition.

Data warehousing
SQL Server includes tools for extracting and analyzing summary data for online analytical
processing (OLAP). SQL Server also includes tools for visually designing databases and analyzing
data using English-based questions.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


System integration with other server software
SQL Server integrates with e-mail, the Internet, and Windows.

Databases
A database in Microsoft SQL Server consists of a collection of tables that contain data, and
other objects, such as views, indexes, stored procedures, and triggers, defined to support activities
performed with the data. The data stored in a database is usually related to a particular subject or
process, such as inventory information for a manufacturing warehouse.

SQL Server can support many databases, and each database can store either interrelated data or
data unrelated to that in the other databases. For example, a server can have one database that stores
personnel data and another that stores product-related data. Alternatively, one database can store
current customer order data, and another; related database can store historical customer orders that
are used for yearly reporting. Before you create a database, it is important to understand the parts of
a database and how to design these parts to ensure that the database performs well after it is
implemented.
2.9.2 SQL Server Tables
SQL Server stores records relating to each other in a table. Different tables are created for
the various groups of information. Related tables are grouped together to form a database.

Primary Key
Every table in SQL Server has a field or a combination of fields that uniquely identifies each
record in the table. The Unique identifier is called the Primary Key, or simply the Key. The
primary key provides the means to distinguish one record from all other in a table. It allows the
user and the database system to identify, locate and refer to one particular record in the database.

Foreign Key
When a field is one table matches the primary key of another field is referred to as a foreign
key. A foreign key is a field or a group of fields in one table whose values match those of the
primary key of another table.

2.10 ARCHITECTURE USED-2-TIER


In 2 tier architecture the application is splitted in to two parts which is located in two machines
called as client and server that is why it is also known as client server architecture..in this
architecture the business logic resides either with the client or with the server where database
resides, so if client machine contains the business logic then is termed as Fat client coz it has to
look after the client related as well as business related issues where as if business logic resides with
the database server then it is termed as Fat Server since it has to manage the database related as well
as business related issues so some how either the client or the server performance hampers.

In this system client application interracts directly with server(means Database server)by means of
connection string. This architecture is used in windows applications. So if any changes is happend

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


in business rules then we should make changes in every clients that were installed in different
locations. This system is used for small business system.

Two type of 2tier architecture:


1.Fat Client
In fat client the application or business layer is associated with user or presentation layer and
data storage layer is reside separately.
Ex.- by submitting user name and password before login into home page

2.Fat Server
In Fat server the application or business layer is associated with data storage layer and user or
presentation layer is reside separately.here all function is carried out on the server.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


3. ANALYSIS

3.1 EXISTING SYSTEM:

In the existing system the details of student’s fee are maintained in registers. Hence the process
is not automated. All the activities done for maintaining the details are performed manually. This is
a time consuming process and also there may be redundancy of data.

3.1.1 Disadvantages of Existing System:

• Managing fee related information manually is a tedious and error prone task.
• Selection of a student who have not paid fee is done manually by the accountant by
Selection of a student who have not paid fee is done manually by the accountant refering the fee
receipt and matching with the student database which it not only tedious work to do but
alsSelection of a student who have not paid fee is done manually by the accountant by Selection of
a studeno time consuming .
• Due to mismanagement the work is delayed to later date than the due date.
• Students need to directly interact with the principal in order to get permission for the delay
in the payment of fee.
• There is no system through which student can view his fee details directly without assistance
of any higher authority.
• There is no clear system to analyse the benefits of early payment and effects of late
payment of the fee.

3.2 PROPOSED SYSTEM:


In the proposed system the process of maintaining repository is automated. The system to be
developed is intended to be user friendly. Redundancy of data is reduced, time consumed is less.
Interaction among students, accountant and Principal is more.

3.3Advantages of Proposed System:

• The processing of the entire application is faster when compared to existing system
by one fourth.
• There is no loss or damage on the documents exchanged.
• Acknowledgement or Confirmation that the fee has been paid is received.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


• No Third party involvement Student can directly see their fee details without help of
accountant once they have registered..
• The system provides the tool with the help of which the user can analysis the fine as well
concession in case of late fee payment or advance fee payment respectively.
• The fee related information of the all the student will be maintained at a centralized data
base which can be assessed by authorized users of the system to get details.
• The information is available when needed.
• Information is clearly presented, not excessively long, and sent using the right medium and
communication channel (eg:reports)

3.4 OVERALL DESCRIPTION

The application is completely web based, It encompasses various files from the MIS Database
which are accessed by users through internet.

HTML
Client
(student)

HTML
Client
(principal) HTTP/
INTERNET
HTTPS INFORMATION SQL
SERVER (IIS) Database
HTML
Client
(accountant)

Client end Application Server &Database server

• The web pages are present to provide user interface on the client side. Communication is
provided through HTTP/HTTPS protocol.
• On the server side Internet Information Server is used and the Database server is used to
store information

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


4.FESABILITY ANALYSIS

FEASIBILITY REPORT
The main objective of the feasibility study is to test the Technical, Operational and Economical
feasibility for adding new modules and debugging old running system. All system is feasible if they
are unlimited resources and infinite time. There are aspects in the feasibility study portion of the
preliminary investigation:
• Technical Feasibility
• Operation Feasibility
• Attendance Feasibility

4.1. Technical Feasibility

The technical issue usually raised during the feasibility stage of the investigation includes the
following:
• Does the necessary technology exist to do what is suggested?
• Do the proposed equipments have the technical capacity to hold the data required to
use the new system?
• Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?
• Can the system be upgraded if developed?
• Are there technical guarantees of accuracy, reliability, ease of access and data
security?

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Earlier no system existed to cater to the needs of the college management regarding the fee
management and tracking of the defaulter list . The current system developed is technically
feasible. It is a web based user interface. Thus it provides an easy access to the users. The
database’s purpose is to create, establish and maintain a workflow among various entities in order to
facilitate all concerned users in their various capacities or roles. Permission to the users would be
granted based on the roles specified. Therefore, it provides the technical guarantee of accuracy,
reliability and security. The software and hardware requirements for the development of this project
are not many and are already available or are available as free as open source. The work for the
project is done with the current equipment and existing software technology. Necessary bandwidth
exists for providing a fast feedback to the users irrespective of the number of users using the
system.

4.2. Operational feasibility:

Proposed projects are beneficial only if they can be turned out into information system. That
will meet the organization’s operating requirements. Operational feasibility aspects of the project
are to be taken as an important part of the project implementation. Some of the important issues
raised are to test the operational feasibility of a project includes the following: -
• Is there sufficient support for the management from the users?
• Will the system be used and work properly if it is being developed and
implemented?
• Will there be any resistance from the user that will undermine the possible
application benefits?
This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the
management issues and user requirements have been taken into consideration. So there is no
question of resistance from the users that can undermine the possible application benefits.
The well-planned design would ensure the optimal utilization of the computer resources and
would help in the improvement of performance status.

4.3. Economic Feasibility

A system can be developed technically and that will be used if installed must still be a good
investment for the organization. In the economical feasibility, the development cost in creating the
system is evaluated against the ultimate benefit derived from the new systems. Financial benefits
must equal or exceed the costs.
The system is economically feasible. It does not require any addition hardware or software.
Since the interface for this system is developed using the existing resources and technologies. There
is nominal expenditure and economical feasibility for certain.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


5. ESTIMATION OF PROJECT

5.1 FUNCTIONAL POINT MODEL:


This model is used to estimate the cost & schedule of the project using requirements. you
can divide the system in scenarios and identifies the items given below with their weight in the
system.

ATTRIBUTE COUNT SIMPLE AVERAGE


No of user inputs 12 3
Outputs 13 4
Inquires 19 2
No Of files 1 7
No of external interface 0 5

Functional point(fc)=(itemcount * avg weight)


UFC=12*3+13*4+19*2+1*7+0*5
UFC=32+52+38+7+0
UFC=100
FP=UFC* TCF
TCF is 0.65 to 1.35
FP=100*0.1=100
FP=100

5.2 COCOMO MODEL:


The basic formula of the cocomo model is based exclusive program size expressed in kdloc.
The underlying formula assumes the form
Effort=a* kdlocb

Embedded system a=3.6 b=1.20

Orgaranic system a=2.4 b=1.05

Semidetached a=3.0 b=1.12

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Where a,b are the basic term of the cocomo model uses the following expression for
embedded system.

Effort= 3.6 * kdloc1.20

Where a=3.6 b=1.20

Kdloc=26

Effort =3.6*26 1.20

Effort=179.58

Where a,b are the basic term of the cocomo model uses the following expression for
Orgarinic system.

Effort= 2.4 * kdloc1.05

Where a=2.4 b=1.05

Kdloc=26

Effort =2.4*26 1.05

Effort=73.44

Where a,b are the basic term of the cocomo model uses the following expression for
semidetached system.

Effort= 3.0 * kdloc1.12

Where a=3.0 b=1.12

Kdloc=26

Effort =3.0*26 1.12

Effort=115.31

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


6. SOFTWARE REQUIREMENT SPECIFICATION

6.1 INTRODUCTION

6.1.1PURPOSE:
The main purpose of the project is to develop an MIS of the college and to maintain a repository
for maintaining the fee related details of the student. To develop MIS for college there is a need to
maintain a repository for the students of the college. Here the details of all the students of the
college can be maintained in a simpler and better manner. The project is aimed at automating the
entire process of maintaining the fee details ,tracking the defaulters list and maintaining the details
regarding the money inflow and money outflow of the college. The redundancy of data is reduced
and the time consumed for performing any action or task is less. This also facilitates online
communication among the principal of the college and also between the accountant and the
students of the college.

6.1.2 SCOPE:

This project is designed to be built on web based application. It has various advantages like,
the principal and accountant can add the fee related details of student in a simpler and easier way,
only they have the privilege to add new student to the repository, efficient and secure user
management, a personalized page for each logged in MIS , the students can communicate with
principal of the college or the accountant of the college, the students can post their query regarding
the fee and any other updation in their details to both the super users. The principal and accountant
task in tracking the list of defaulters becomes easy by using this system . The system provides
flexibility in obtaining the summary report of fee branch wise as well as year wise.

6.1.3 TECHNOLOGIES USED

1. Operating System : Microsoft® Windows® XP Professional SP2


2. Microsoft® Visual Studio 2005 Professional Edition :
Microsoft .NET compact Framework 1.0 SP3
Developer, Version: 1.0.4292
Microsoft .NET compact Framework 1.0, Version: 2.0.5238

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Crystal report
3. Web server : Internet Information Server 5.0 (IIS)
4. Web Browser : Microsoft® Internet Explorer 7 or greater

6.1.4 REFERENCE

• INTERNET

• FOR .NET INSTALLATION

www.support.mircosoft.com

• FOR DEPLOYMENT AND PACKING ON SERVER

www.developer.com

www.15seconds.com

• FOR SQL

www.msdn.microsoft.com

• FOR ASP.NET

www.msdn.microsoft.com/net/quickstart/aspplus/default.com

www.asp.net

www.fmexpense.com/quickstart/aspplus/default.com

www.asptoday.com

www.aspfree.com

www.4guysfromrolla.com/index.aspx

• BOOKS REFERRED

1)Visual Studio 2005 programmers,Gead Mead


2)Microsoft SQL Server 2005 Reporting Services-Das praxisbuch

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


6.1.5 OVERVIEW

The application is completely web based, It encompasses various files from the MIS Database
which are accessed by users through internet.

6.2 OVERALL DESCRIPTION:

6.2.1 Product Perspective:

After understanding the existing system and understanding the need for developing a new
system different people involved in the related activities have been consulted. The data needed for
the study has been collected from company records.
The computerization of this system would avoid the wrong interpretation and bad
calculation of data .The system help the user to see any documents, source code, tasks, activities,
team information with details at the click of a button. The record data is maintained and backed up
such a way that data is not loss. The speed of the system could also increased.

6.2.2 Product Functions:

The major functionality of this product is divided into four categories.

1. student Functions
The student can view the messages in the the inbox and post messages either to the
Accountant or the Principal and view sent messages.
2. Principal Functions
Principal can view ,update and delete the details of particular student based on the rollno.
3. Accountant Functions
Accountant can view the summary report branch wise and even defaulters list can be
viewed by principal which will help to short list the student how don’t pay fee .

6.2.3 User Classes and Characteristics:

Identify the various user classes that you anticipate will use this product. User classes may
be differentiated based on frequency of use, subset of product functions used, technical expertise,

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


security or privilege levels, educational level, or experience. Describe the pertinent characteristics
of each user class.
Certain requirements may pertain only to certain user classes. Distinguish the favored user
classes from those who are less important to satisfy.

6.2.4 Constraints:

• Only authorized users should be able to access the system.


• Only Project Manager should be able to view the client details.
• The entire user interfaces need to be in HTML format.
• Details of the project are restricted only to some users.

6.2.5 Assumptions and Dependencies Specific Requirement :

Only the valid users can login in to the page. As per the details given in the database,
whether an project manager, project leader, teamleader or else programmer.
Different users have different functions to view and to add the details as per the
dependencies of the respective user.

6.3 Specific Requirement

6.3.1 FUNCTIONAL REQUIREMENT:

Functional requirement defines a function of a software system or its component. A function is


described as a set of inputs, the behavior, and outputs. Functional requirements specify particular
results of a system. This should be contrasted with non-functional requirements which specify
overall characteristics such as cost and reliability. Functional requirements drive the application
architecture of a system. The Functional Requirements of this system are:

• Principal can view ,update and delete the details of particular student based on the rollno.
• Principal can check the inbox for received messages, can compose new messages in
response to the message recevied and can view sent messages .
• Principal can view the summary report branch wise and even defaulters list can be viewed
by principal which will help to short list the student who dn’t pay fee .
• Accountant can view ,update and delete the details of particular student based on the rollno.
• Accountant can check the inbox for receveid messages, can compose new messages in
response to the message received and can view sent messages .
• Accountant can view the summary report branch wise and even defaulters list can be
viewed by principal which wil help to short list the student how don’t pay fee .

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


• Accountant can register new student .
• Accountant prepare payment voucher ,fee reciepts and balance sheet to maintain the money
inflow and outflow details
• The student can view the messages in the the inbox and compose messages either to the
Accountant or the Principal and view sent messages
• This modules help student to have knowledge about their fee details without assistance of
any higher authority.
• The student can anlayse the fine as well as concession to be obtained in case of late and
advance fee payment respectively.

6.3.2. NON-FUNCTIONAL REQUIREMENT:

Non-functional requirement is a requirement that specify criteria that can be used to judge the
operation of a system, rather than specific behaviors. Non-functional requirements are often called
qualities of a system. Non-functional requirements drive the technical architecture of a system. The
following are the Non-Functional requirements of the present system.
EFFICIENCY
It must be the key requirement that will deal with the reduction of response time and caching of
the frequently visited web pages.
FLEXIBILITY
Flexibility is the ability of a system to respond to the requests made by the clients and respond
to potential internal or external changes affecting its value delivery, in a timely and cost-effective
manner. Thus, flexibility for a system is the ease with which the system can respond to uncertainty
in a manner to sustain or increase its value delivery.
SCALABILITY
Irrespective of the number of clients or users requesting a same page, the delivery of that page
should be independent. In other words, we expect the system to be as efficient to one system or
number of systems.
MANAGEABILITY
How easy it is to manage a computer system or collection of systems. It includes such diverse
tasks as administration, backup, security, filtering, performance tuning, granting privileges, and
fault recovery.

6.3.3 PERFORMANCE REQUIREMENTS


Performance is measured in terms of the output provided by the application. Requirement
specification plays an important part in the analysis of a system. Only when the requirement
specifications are properly given, it is possible to design a system, which will fit into required
environment. It rests largely in the part of the users of the existing system to give the requirement
specifications because they are the people who finally use the system. This is because the
requirements have to be known during the initial stages so that the system can be designed
according to those requirements. It is very difficult to change the system once it has been designed

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


and on the other hand designing a system, which does not cater to the requirements of the user, is of
no use.
The requirement specification for any system can be broadly stated as given below:
• The system should be able to interface with the existing system
• The system should be accurate
• The system should be better than the existing system.
The existing system is completely dependent on the user to perform all the duties.

6.3.4. Logical Database Requirements:

Logical requirements connected with the database include:


• Most of the values are string types.
• Accessing rights are limited to authenticated users only.

6.3.5. Hardware Constraints:


PROCESSOR : Pentium II with 1GHz or Higher
HARD DISK : 2GB
RAM : 512 GB or Higher

6.3.6 Software Constraints:

DOCUMENTATION TOOL : MS – WORD 2000


OPERATING PLATFORM : Microsoft® Windows® XP Professional
Web server : Internet Information Server 5.0
SOFTWARE :
Microsoft® Visual Studio 2005 Professional Edition
Microsoft .NET compact Framework 1.0 SP3
Developer, Version: 1.0.4292
Microsoft .NET compact Framework 1.0, Version: 2.0.5238
Crystal report
BROWSER : Microsoft® Internet Explorer 7

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


7. DESIGN
7.1DATABASE DESIGN

TABLES

1 Login Table :

This tables stores login details of all users

Attribute Datatype constraint


Sno Int Not null
Id Varchar(50)
Userid Varchar(50)
Username Varchar(50)
Password Varchar(50)
Usertype Varchar(50)

2 Sentmsg Table:

This table stores the details of the sender and receiver of the messages .

attribute Datatype Constraint


Sno Int Primary Key
Rmsg Varchar(50)
Sender Varchar(50)
Subject Varchar(50)
Msg Varchar(50)

3 Remainders Table:

This table is used to store sender and and receivers details .

Attribute Datatype Constraint


Sno Int Primary key
Rno Varchar(50)
subject Varchar(50)
Message Varchar(50)
Date Smalldatetime

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Sender Varchar(50

4 Asstdfee table:

This table is used to store the fee related details of students.

Attribute Datatype Constraint


Rollno Varchar(50) Primary key
Sname Varchar(50)
Branch Varchar(50)
Section Varchar(50)
Year Varchar(50)
Caste Varchar(50)
Tfee Int
Tfeebal Int
Sefee Int
Sefeebal Int

5 Fee receipt table:

This table is used to store the fee related details of students so as to generate fee receipt prints .

Attribute Datatype Constraint


Year Varchar(50)
Vchno Int Primary key
Rollno Varchar(50)
Date Smalldatetime
Sname Varchar(50)
Branch Varchar(50)
Section Varchar(50)
Sem Varchar(50)
Cashtype Varchar(50)
Chqno. Int
Feetype Varchar(50)
Amt Int
rupeestoword Varchar(max)

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


6 Reg Table :

This table is used to store the details of student at the time of registration.

Attribute Datatype constraint


Name Varhchar(50)
Sof Varchar(50)
Rno Varchar(50) Primary key
Address Varchar(50)
Contactno Int
Course Varchar(50)
Branch Varchar(50)
Year Varchar(50)
Admby Varchar(50)
Caste Varchar(50)
Tfee Int
Sefee Int
Busfee Int
Ldtopay Smalldatetime

7. 2 E-R DIAGRAMS:

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


It is useful to develop a blue print before you create your database. Entity-Relationship (E-R)
diagram is such a blue print. Entity-Relationship (E-R) diagrams are commonly used to show how
data are organized.
Entity Relationship (ER) modelling
• is a design tool
• is a graphical representation of the database system
• provides a high-level conceptual data model
• supports the user’s perception of the data

Entity-Relationship Diagrams are used:


• As a database design tool formalizing the information requirements of the end users
• As a documentation tool for databases (to help programmers, especially those that have to
update the database)
• As a tool of system analysis
Basic constructs of the E-R model:
– Entities
– Attributes
– Relationships

Entities: A person, place, object, event or concept in the user environment about which the
organization wishes to maintain data.
Attributes: A named property or characteristic of an entity that is of interest to an organization
Relationship: An association between the instances of one or more entity types that is of interest to
the organization. Association indicates that an event has occurred or that there is a natural link
between entity types.
The primary purpose of the ERD is to represent data objects and their relationships.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


E-R DIAGRAM

7.3 DATA FLOW DIAGRAMS

Data flow diagram is a pictorial representation of the system in which Flow of data from
one process to another process is described. A Data Flow is composed of Data movement shown
by arrows.
Data Flow Diagrams are of two types:
• Physical Data Flow Diagrams: These are implementation-dependent i.e., they show the
actual devices, departments, people, etc., involved in the system.
• Logical Data Flow Diagrams: These diagrams describe the system independently of how it
is actually implemented, they show what takes places, rather than how an activity is
accomplished.

The DFD is intended to represent information Flow but it is not a flow chart and is not
intended decision-making, flow of control, loops and other procedural aspects of the system. DFD
is a useful Graphical tool and is applied at the earlier stages of requirements analysis. It may be

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


further refined at preliminary design stage and is used as mechanism for top-level structural design
for software.
The DFD drawn first at a preliminary level is further expanded into greater details:
• The context diagram is decomposed and represented with multiple rectangles.
• Each of these rectangles may be decomposed further and given as more detailed DFD.

Context-level DFD’S:

Login Checking login-Info


Fee Management
Authorized Login Valid data
System
proces
s Authorized
Authorized
Project Manager Employee

Principal
Accontant Student

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Level-I DFD’s:

Login-info
Check inbox

Principal Valid Checking


Login Update
FeeDet
Authorized
Administrator
Login
Proc Compose
ess mess

Change
password

Fig for level-1 PrincipalDFD

Login-info

Valid Checking
Login View fee details
Accountant
Login
Proces Authorized
s Employee Update
feedetails

View
balancesheet

Fig for Level-I DFD Accountant

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Login-info

Valid Checking
Login View fee details
Student
Login
Proces Authorized
s Employee
Check inbox

Compose
messages

Fig for Level-I DFD Student

Level-II DFD‘s

Login Login Authorized Assign


Principal process Principal Proces
s

Fig for level-2 DFD Principal

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Accountant
Login information
Accountant process
process

Account
ant Add
details Acc-info

View
Fig for level-2 DFD accountant

Login Login Authorized Assign


Student process Principal Proces
s

Fig for level-2 DFD Student

7.4 FLOWCHART

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


User

Fee Mgmt
system

Student
Principal Accountant
no no no

val Va Val
id lid id

yes yes yes

Student
Principal Accountant
option
option option

stop

Fig for process logic

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


7.5 UML DIAGRAM:

UML is the international standard notation for object-oriented analysis and design. The Object
Management Group defines it. The heart of object-oriented problem solving is the construction of a
model. The model abstracts the essential details of the underlying problem from its usually
complicated real world. Several modeling tools are wrapped under the heading of the Unified
Modeling Language.
The UML is a language for
• Visualizing
• Specifying
• Constructing
• Documenting
These are the artifacts of a software-intensive system. The major elements of UML are
• The UML basic building blocks
• The rules that dictate how those building blocks may be put together.
• Some common mechanisms that apply throughout the UML.

BASIC BUILDING BLOCKS OF THE UML:


The vocabulary of UML encompasses three kinds of building blocks:
• Things:
• Relationships
• Diagram

Things in the UML


They are the abstractions that are first-class citizens in a model. There are four kinds of things in
the UML
• Structural things
• Behavioral things.
• Grouping things.
• Annotational things.
These things are the basic object oriented building blocks of the UML. They are used to write
well-formed models.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Relationships in the UML
There are four kinds of relationships in the UML:
• Dependency
• Association
• Generalization
• Realization
Diagrams in the UML
Diagrams play a very important role in the UML. There are nine kind of modeling diagrams as
follows:
• Use Case Diagram
• Class Diagram
• Object Diagram
• Sequence Diagram
• Collaboration Diagram
• State Chart Diagram
• Activity Diagram
• Component Diagram
• Deployment Diagram

CLASS DIAGRAM:-
Class diagrams are the most common diagram found in modeling object-oriented
systems. A class diagram shows a set of classes, interfaces, and collaborations and their
relationships.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


member voluntaries
id : varchar(50) id : varchar(50)
password : varchar(5;0) password : varchar(50)
adminl
login() id : varchar(50) login()
View donations() password : varchar(50) viewvillages()
check_inbox() View activities()
compose_messagesto voluntaries() login()
compose_messagetoadmin() view_memberdetails() check_inbox()
view_sentreminders() update_memberdetails() compose_messages()
View_inbox) Delete_memberdetails() check_sentreminders()
changepassword() check_inbox() view_defaulterslist()
logout() compose_messages()
check_sentreminders()
1 1 1 view_defaulterslist()
view_summaryreports()

1 1

1 1
logout()
1 1 1 1
1

0..* 0..*

Remainders
sno : int 0..*
rno : varchar(50) login
subject : varchar(50)
sno : int 1..* 1..*
date : smalldateime
id : varchar(50)
sender : varchar(50) Asstdfee
userid : varchar(50)
message : varchar(50)
username : varchar(50) rollno : varchar(50)
password : varchar(50) sname : varchar(50)
usertype : varchar(50) branch : varchar(50)
section : varchar(50)
year : varchar(50)
caste : varchar(50)
1 tfee : varchar(50)
0..* 0..*
1..* tfee : int
sentrem tfeebal : int
reg
sefee : int
name : varchar(50) sno : int
sefeebal : int
sof : varchar(50) rmsg : varchar(50)
rno : varchar(50) sender : varchar(50) 0..*
address : varchar(50) subject : varchar(50)
1..* 1..*
contactno : varchar(50) message : varchar(50)
course : varchar(50) date : smalldatetime
feereceipts
branch : varchar(50)
year : varchar(50) year : varchar(50)
admby : varchar(50) Vchno : int
caste : varchar(50) rollno : varchar(50)
tfee : varchar(50) date : smalldatetime
sefee : varchar(50) sname : varchar(50)
busfee : 'varchar(50) branch : varchar(50)
ldtopay : smalldatetime section : varchar(50)
sem : varchar(50)
cashtype : varchar(50)
chqno : varchar(50)
feetype : varchar(50)
amt : varchar(50)
rupeestoword : varchar(MAX)

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


(Class Diagram)

USECASE DIAGRAM:.

Student usecase diagram:

<<include>>

login authentication

view_feedetails

check_inbox

composemessagetoaccountant

composemessagetoprincipal

student

view_sentreminders

view_fine/concessionstructure

change_password

logout

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Accountant usecase diagram:

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


<<in
clu
de>>

lo
gin a
uth
entica
tio
n

vie
w _fe
ede
tailsb
ase
d_o
nro
lln
o.

u
pda
te_
fee
deta
ilsb
ase
d_o
nro
lln
o.

d
ele
te_
fee
deta
ils_
onro
lln
o.

ch
eck_in
box

co
m p
ose
_me
ssa
ge

vie
w _
sen
tre
m in
ders

p
rep
are
_fe
ere
ceip
ts

g
ene
rate
_fe
ere
ceip
ts

p
rep
are
_pa
yme
ntvo
uch
er

a
cco
unta
nt
g
ene
rate
_pa
yme
ntvo
uch
er

vie
w _
summa
ryre
port

vie
w _
defa
ulte
rlist

re
giste
r_n
ewstu
den
ts

vie
wba
lan
cesh
eet

vie
w _
fin
e/co
nce
ssio
nstru
ctu
re

ch
ang
epa
ssw
ord

lo
gou
t

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


<<include>>

login authentication

view_ feedetailsbased_onrollno.

update_feedetailsbased_onrollno.

delete_feedetails_onrollno.

check_ inbox

compose_message

view_sentreminders

prepare_feereceipts

principal
generate_feereceipts

view_defaulterlist

view_summaryreport

register_newstudents

changepassword

logout

Principal

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


SEQUENCE DIAGRAM:

A sequence diagram is an interaction diagram that emphasizes the time ordering of


messages.

Student sequence diagram:

student System

1: login

2: authentication
3: login successfully

4: view_feedetails

5: viewmessages in inbox

6: compose messages to principal/accountant

7: viewsent reminders

8: viewfine /concession on fee payment

9: change password

10: logout

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Accountant sequence diagram:

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Accountant system

1: login

3: loginsuccessfully 2: authentication

4: view_feedetailsof students basedonrollno.

5: update_feedetailsof students

6: delete_feedetails of students

7: viewmesssages ininbox

8: composemessages

9: viewsent reminders

10: preparefeereceipts
11: generatecrystal report for feereceipts
12: edit /deletefeereceipts

13: preparepayment voucher


14: generatecrystel report for payment voucher

15: viewdefaulterslist

16: viewsummaryreport

17: viewbalancesheet
18: register newstudents

19: changepassword

20: logout

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Principal sequence diagram

Principal system

1: login

2: authentication
3: login successfully

4: view_student feedetails basedon rollno.

5: updatefeedetails
6: delete the student feedetails
7: viewthemessages in inbox

8: composenewmessages
9: viewthe sent reminders

10: prepare feereceipts

11: generate crystal reports for the feereceipts

12: viewdefaulters list

13: viewsummary reports


14: change password

15: logout

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


ACTIVITY DIAGRAM:

Activity diagrams are for modeling the dynamic aspects of systems. An activity diagram is
essentially a flowchart, showing flow of control from activity to activity.

1 Student Activity Diagram :

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


2 Principal Activity Diagram

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


3 Accountant Activity Diagram:

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


8.CODING
8.1 CODING

Login page:

Imports system.data
Imports system.data.sqlclient
Partial Class login
Inherits System.Web.UI.Page

Protected Sub Login1_Authenticate(ByVal sender As Object, ByVal e As


System.Web.UI.WebControls.AuthenticateEventArgs) Handles Login1.Authenticate

Dim con As New SqlConnection("Data Source=.\SQLEXPRESS;AttachDbFilename=|


DataDirectory|\Database.mdf;Integrated Security=True;User Instance=True")

Dim user_login As String = " "


Dim pwd_login As String = ""
Dim user_name As String = ""
Dim user_id As String = ""

Dim user As String = Login1.UserName


Dim pwd As String = Login1.Password

Dim cmd As New SqlCommand("select id,userid,username,password,usertype from login


where userid='" & user & "'and password='" & pwd & "'", con)
Dim dr As SqlDataReader
con.Open()
dr = cmd.ExecuteReader()
Dim usd As String = ""
While dr.Read()
user_login = dr.GetValue(0)
pwd_login = dr.GetValue(1)
usd = dr.GetValue(2)
user_name = dr.GetValue(4).ToString
user_id = dr.GetValue(3).ToString

End While

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


con.Close()
If user_login <> "" Then
Session("userid") = user_login
Session("pwd") = pwd_login
Session("id") = user_id
Session("name") = usd
Session("usertype") = user_name
If user_name = "student" Then
Response.Redirect("stdhomepage.aspx")
ElseIf user_name = "acc" Then
Response.Redirect("acchomepage.aspx")
ElseIf user_name = "principal" Then
Response.Redirect("principalhome.aspx")
End If
End If

End Sub
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles
Me.Load
End Sub
End Class

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


9. TESTING

One definition of testing is “the process of questioning a product in order to evaluate it”, where the
“questions” are operations the tester attempts to execute with the product, and the product answers
with its behavior in reaction to the probing of the tester. A good test is sometimes described as one
which reveals an error; however, more recent thinking suggests that a good test is one which reveals
information of interest to someone who matters within the project community.

9.1 Testing Objectives


There are several rules that state the intention of testing, collectively known as testing
objectives.
They are:
• Testing is a process of executing a program with the intent of finding an error.

• A good test case is one that has a high probability of finding an as-yet undiscovered error.

• A successful test case is one that uncovers an as-yet undiscovered error.

From these objectives we can understand that a successful test is not the one that passed without
any error. Thus our objective is to design test that systematically uncovers different classes of errors
by consuming a minimum amount of time and effort.

9.2 Testing Principles

There is basic software testing principles suggested by Davis that guide a software engineer in
design of effective test cases.
• All tests should be traceable to user requirements.

• Tests should be planned long before testing begins.

• The Pareto principle (80 percent of all errors uncovered during testing will likely be
traceable to 20 percent of all program components) applies to software testing.

• Testing should begin ‘in the small’ and progress towards testing ‘in the large’.

• Exhaustive testing (testing each and every combination of paths in program logic) is not
possible.

• To be most effective, an independent third party should conduct testing.

9.3 Testing phases:

1 System testing:

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


After finishing the development of any computer based system the next complicated time
consuming process is system testing. During the time of testing only the development
company can know that, how far the user requirements have been met out, and so on.

2 Unit Testing

Unit testing focuses on verifying the effort on the smallest unit of software-module. The
local data structure is examined to ensure that the date stored temporarily maintains its integrity
during all steps in the algorithm’s execution. Boundary conditions are tested to ensure that the
module operates properly at boundaries established to limit or restrict processing.

3 Source Code Testing:

This examines the logic of the system. If the output is desired ouput i.e required by the
user, then that the logic is perfect.

4 Specification Testing:

We can set with, what program should do and how it should perform under various
condition. This testing is a comparative study of evolution of system performance and system
requirements.

5 Module Level Testing:

In this the error will be found at each individual module, it encourages the programmer
to find and rectify the errors without affecting the other modules.

6 Validation Testing:

It begins after the integration testing is successfully assembled. Validation succeeds when
the software functions in a manner that can be reasonably accepted by the client. In this the majority
of the validation is done during the data entry operation where there is a maximum possibility of
entering wrong data. Other validation will be performed in all process where correct details and data
should be entered to get the required results.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


9.4 TEST CASES:

9.4.1) Login Test Case:

Test Inputs Actual Output Observed Output Description


Valid user User id & success success Test passed
password Navigates to
next page.
Invalid user User id & Failed Failed Test passed
password Displays the
error message.

9.4.2)Principal Module:

9.4.2.1) View Student Details:

Test Input Output Observed Output Description


Valid Student roll no. success success Test passed
Transaction Displays details
of the student.
Invalid Student roll no. Failed Failed Test passed
Transaction Displays error
message this roll
no. Doesn’t exist.

9.4.2.2) Update/Delete Student Details:

Test Input Output Observed Output Description

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Valid Student roll no. success success Test passed
Transaction Updated
successfully.
Invalid Student roll no. Failed Failed Test passed
Transaction Displays
appropriate
message.

9.4.2.3) Compose message:

Test Input Output Observed Output Description


Valid year , branch and success success Test passed
Transaction message Sent message
successfully.
Invalid year ,branch and Failed Failed Test passed
Transaction message Displays
appropriate
message.

9.4.2.4) Fee Receipt:

Test Input Output Observed Description


Output

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Valid Year,vchno,rollno,date,sname,branch,section,sem,casht success success Test Passed
Transaction ype,cheque no, fee type, amount. Values
inserted
Successfully
Invalid Year,vchno,rollno,date,sname,branch,section,sem,casht Failed Failed Test Passed
Transaction ype,cheque no, fee type, amount. Displays
appropriate
message.

9..4.2.5 ) Summary Report:

Test Input Output Observed Output Description


Valid Year and Branch success success Test passed
Transaction Displays all the
details of the
student.
Invalid Year and Branch Failed Failed Test passed
Transaction Displays error
message if
doesn’t exist.

9.4.2.6) Defaulters List:

Test Input Output Observed Output Description


Valid Year and Branch success success Test passed
Transaction Displays all the
details of the

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


student.
Invalid Year and Branch Failed Failed Test passed
Transaction Displays error
message if
doesn’t exist.

9.4.3) Student Module:

9.4.3.1) Student View Details:

Test Input Output Observed Output Description


Valid Student roll no. success success Test passed
Transaction Displays details
of the student.
Invalid Student roll no. Failed Failed Test passed
Transaction Displays error
message this roll
no. Doesn’t exist.

9.4.3.2) Compose message:

Test Input Output Observed Output Description


Valid Receiver and success success Test passed
Transaction message Sent message
successfully.
Invalid Receiver and Failed Failed Test passed
Transaction message Displays
appropriate
message.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


9.4.4) Accountant Module:

9.4.4.1) View Student Details:


Test Input Output Observed Output Description
Valid Student roll no. success success Test passed
Transaction Displays details
of the student.
Invalid Student roll no. Failed Failed Test passed
Transaction Displays error
message this roll
no. Doesn’t exist.

9.4.4.2)Update/Delete Student Details:

Test Input Output Observed Output Description


Valid Student roll no. success success Test passed
Transaction Updated
successfully.
Invalid Student roll no. Failed Failed Test passed
Transaction Displays
appropriate
message.

9.4.4.3) Compose message:

Test Input Output Observed Output Description

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Valid year , branch and success success Test passed
Transaction message Sent message
successfully.
Invalid year ,branch and Failed Failed Test passed
Transaction message Displays
appropriate
message.

9.4.4.4) Fee Receipt:

Test Input Output Observed Description


Output
Valid Year,vchno,rollno,date,sname,branch,section,sem,casht success success Test Passed
Transaction ype,cheque no, fee type, amount. Values
inserted
Successfully
Invalid Year,vchno,rollno,date,sname,branch,section,sem,casht Failed Failed Test Passed
Transaction ype,cheque no, fee type, amount. Displays
appropriate
message.

9.4.4.5) Summary Report:

Test Input Output Observed Output Description


Valid Year and Branch success success Test passed
Transaction Displays all the
details of the
student.
Invalid Year and Branch Failed Failed Test passed

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Transaction Displays error
message if
doesn’t exist.

9.4 .4.6) Defaulters List:

Test Input Output Observed Output Description


Valid Year and Branch success success Test passed
Transaction Displays all the
details of the
student.
Invalid Year and Branch Failed Failed Test passed
Transaction Displays error
message if
doesn’t exist.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Test Input Output Observed Description
Output
Valid Date, paid success success Test passed
Transaction to,vchno,cheque/dd,amount,towards,cheque Navigates to
no. next page
which
generates a
crystal
report for
the given
input.
Invalid Date, paid Failed Failed Test passed
Transaction to,vchno,cheque/dd,amount,towards,cheque Displays
no. appropriate
message.

9.4.5) Change Password Test Case:

Test Input Output Observed Output Description


Valid Old password, success success Test passed
Transaction new password, Displays
conform message
password successfully
password
changed.
Invalid Old password, Failed Failed Test passed
Transaction new password, Displays error
conform message that
password passwords don’t
match.

9.4.6) Fee Structure Test Case:

Test Input Output Observed Output Description

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Valid Roll no., actual success success Test passed
Transaction amount, date of Displays fine or
payment, last concession and
date to pay total amount.
Invalid Roll no., actual Failed Failed Test passed
Transaction amount, date of Displays error
payment, last message.
date to pay

9.5 NAVIGATION TESTING:


The job of navigation Testing is
 To ensure that the mechanisms that allow the WebApp user to travel through the WebApp
are all functional and
 To validate that each navigation semantic unit can be achieved by the appropriate user
category.

9.5.1 Testing Navigation Syntax:


Navigation links: Internal links within the WebApp, external links to other WebApps and
anchors within a specific Web page should be tested to ensure that proper content or functionality is
reached when the link is chosen.
Redirects: these links come into play when a user requests a nonexistent URL or selects a link
whose destination has been changed. We have tested this by accessing the incorrect internal links
and the test is completed successfully.

9.6 SECURITY TESTING:

Security testing attempts to verify that protection mechanism built into system will in fact
protect it from improper penetration. The tester may attempt to acquire password through external
clerical means, may attack the system with custom software design to break down any defenses to
others, and may purposely cause errors.

9.7 PERFORMANCE TESTING:

Performance Testing is used to test runtime performance of software within the context of an
integrated system. Performance test are often coupled with stress testing and require both software
instrumentation.

9.8 BLACKBOX TESTING:

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Black- box testing focuses on functional requirement of software. It enables to derive etc. of
input conditions that will fully exercise all functional requirements for a program. Black box testing
attempts to find error in the following category:

· Incorrect or missing function

· Interface errors

· Errors in data structures or external database access and performance errors

.9.9 OUTPUT TESTING:

After performing the validation testing, the next step is output testing of the proposed system
since no system would be termed as useful until it does produce the required output in the specified
format. Output format is considered in two ways, the format

10.SCREENS

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Fig 1 for Login page Accountant

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Fig 2 for Accountant HomePage

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Fig 3 for Accountant Inbox

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Fig 4 forAccountant send messages

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Fig 5 Registration Form

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Fig 6 Output for Fee structure(concession case)

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Fig 7 Principal Login

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Fig 8 Student View Details

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Fig 9Principal Compose message

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Fig 10 Output screen for summary reports

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Fig 11 Output screen for Defaulters List

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Fig 12 Students Home Page

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


Fig 13 Student Sent Messages

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


11 FUTURE SCOPES

The current application developed is in accordance with the requirement that has been
provided by the agency . On regarding the future enhancement, the application can further expanded
in accordance with changing scenario. Since the change in testing and user needs arises frequently
in certain short intervals of time, the application can be further upgraded to meet the requirements
that may arise in the far or near future. With regarding to the needs that arises, more and more
features can be included by adding it as separate modules and integrate it with the existing system.

• The MIS for AUCP can be extened to automate complete accounting work .Such as the
entire work of account can be embedded in the MIS to provided full fledge automation to
accounting work.
• The accounting software Telly can be imported to MIS for AUCP to ease the work of
accountant.

This improvement will further enhance the efficiency of work done by the college management.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


12. CONCLUSION

It has been a great pleasure for me to work on this exciting and challenging project. This project
proved good for me as it provided practical knowledge of not only programming in ASP.NET and
VB.NET web based application and no some extent Windows Application and SQL Server, but also
about all handling procedure related with “Quality Management System”.

BENEFITS:
The merits of this project are as follows: -
• This project offers user to enter the data through simple and interactive forms. This is very
helpful for the client to enter the desired information through so much simplicity.
• User is provided the option of monitoring the records he entered earlier.
• From every part of the project the user is provided with the links through framing so that he
can go from one option of the project to other as per the requirement. This is bound to be simple
and very friendly as per the user is concerned. That is, we can say that the project is user friendly
which is one of the primary concerns of any good project.
• Data storage and retrieval will become faster and easier to maintain because data is stored in
a systematic manner and in a single database.
• Decision making process would be greatly enhanced because of faster processing of
information since data collection from information available on computer takes much less time then
manual system.

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM


13. BIBLIOGRAPHY
INTERNET

• FOR .NET INSTALLATION

www.support.mircosoft.com

• FOR DEPLOYMENT AND PACKING ON SERVER

www.developer.com

www.15seconds.com

• FOR SQL

www.msdn.microsoft.com

• FOR ASP.NET

www.msdn.microsoft.com/net/quickstart/aspplus/default.com

www.asp.net

www.fmexpense.com/quickstart/aspplus/default.com

www.asptoday.com

www.aspfree.com

www.4guysfromrolla.com/index.aspx

• BOOKS REFERRED

1)Visual Studio 2005 programmers,Gead Mead


2)MicrosoftSQLServer2005 Reporting Services-Daspraxisbuchs

A.E.C, C.S.E 70 FEE MANAGEMENT SYSTEM

Você também pode gostar