Academic

Information
System For
University
Department

Abstract
Academic Information System(AIS) deals with the
maintenance of Teacher, Office, Seminar, Students
and so on. AIS are an automation system, which is
used to store the faculty, student, courses and
information of any institute. Starting from
registration of a new student in the faculty. It
maintains all the details regarding the attendance
and marks of the student. The project deals with
retrieval of information through an INTERNET based
campus wide portal. It collects related information
from all the departments of an organization and
maintains files, which are used to generate reports
in various forms to measure individual and overall
performance of the students.
Development process of the system starts with
2
System analysis. System analysis involves creating

Introduction
Academic Information system is software which
is helpful for students as well as the Dept.
authorities. In the current system all the
activities are done manually. It is very time
consuming and costly. Academic information
deals with the various activities related to the
students and teacher.
There are mainly 5 modules in this software:

Admin Modules
Teacher Module
Student Module
Seminar Library Module

In the software we can register as a user and

user has of two types, student and teacher.
Administrator has the power to add new teacher
profile and can edit and delete a profile. Teacher
has the power to create the attendance sheet
and also view all the student attendance.
Student can view the marks or his attendance
and also view any teachers message. The
teacher can add, edit and delete marks for the
students. All the users can see the marks.

PURPOSE OF THE SYSTEM

ACADEMIC INFORMATION SYSTEM [AIS] deals with
the maintenance of university, student
information, teacher information with in the
university. This project of AIS involved the
automation that can be implemented in different
faculty managements
The project deals with retrieval of information
through an INTERNET based campus wide portal.
It collects related information from all the
departments of an organization and maintains
files, which are used to generate reports in
various forms to measure individual and overall
performance of the student.
5

System Requirements & Planning

This system based on Linear Sequential

model (Water fall model)

Water Fall Model

Diagram

Requirements
Requirements
defi nition
defi nition

System and
System and
software design
software design
Implementa
tion
Implementa
tion
and unit testing
and unit testing
Integration and
Integration and
system testing
system testing
Operation and
Operation and
maintenance
maintenance

 Requirements consists of some stages:

Inception
Elicitation
Elaboration
Negotiation
Specification
Validation
Management

Questions we had asked to

the teacher and office staff:
Questions asked to teacher:
1.Who will use this system?
2.What functionality we can add for
teachers?

Questions asked to office staff

1.What the most important work done by
office?
2.How they manage students information?
3.About Result publishing
4.What other works they do for department?

Planning
Team Structure
Discussion among team
members
Decisions on problems

Final decision

10

Planning on Academic
Information System
1.Data collection on teachers and
students
2.Creating profile of Teachers and
Students
3.Genrate seminar id
4.Arrangement of meeting by
office
5.Admission ,Form fill-up
6.Cost efficient
11

System analysis

12

EXISTING SYSTEM
Section
officer

Collects
document
s

Write down
information
s

Store in
excel
sheet

This process is time consuming and

also risky

13

The system starts with registration of new staff

and students. When the subjects are to be
allocated to the faculty, the Head Of the
Department should enter everything in the Excel
sheets. Then the stuff enters corresponding
subjects attendance and marks of a student
then those must also entered in the Excel sheets
and validation are to be done by the user itself.
So there will be a lot of work to be done and
must be more conscious during the entrance of
details. So, more risk is involved.

14

Problems in the existing

system
Section
Officer

Storing data
into Excel
sheet and
account
books

Accessing data
from excel sheet
and account
books

Tedious work

15

Sorting and accessing the data in the form of

Excel sheets and account books is a tedious
work. It requires a lot of laborious work. It may be
often yield undesired results. Maintaining these
records as files may turn out to be a costlier task
than any other of the colleges and institutions.

16

Risk Involved in existing

system

Present system is time consuming and also results

in lack of getting inefficient results. Some of the
risk involved in the present system are:
During the entrance of marks and attendance , if
any mistake is done at a point, then this becomes
cumulative and leads to adverse consequences.
If there is any need to retrieve results it may seem
to be difficult to search.

17

Proposed System
Academic Information
System
This system has following
divisions:
Admin
Teacher
Student
Office
Seminar Library

18

19

Teacher has the right of creating attendance

sheet, mark sheet, and class schedule. Any
tutorial, text, or ppt file send for student.
Student of this faculty has the facility of
entering the marks and attendance of the
student. Students can be check their marks and
attendance but there is no chance of
modification. Student also search the library
books.
Seminar library has the right to include the
book name, counting, and position for library.
Office has the right to arrange meeting, form
fill-up, result publishing and also update notice

20

FEASIBILITY ANALYSIS:
Whatever we think need not be
feasible. It is wise to think about the feasibility
of any problem we undertake. Feasibility is the
study of impact, Which happens in the
organization by the development of a system.
The impact can be either positive or negative.
When the positive nominate the negative, then
the system is considered feasible. Here the
feasibility study can be performed in two ways
such as technical feasibility and Economical
Feasibility.
21

Technical Feasibility:
We can strongly says that it is technically
feasible, since there will not be much difficultly
in getting required resources for the
development and maintaining the system as
well. All the resources needed for the
development of the software as well as
maintenance of the same is available in the
organization here we are utilizing the resources
which are available already.

22

Economical Feasibility:
Development of this application is highly
economically feasible. The organization needed
not spend much money for the development of
the system already available. The only thing is to
be done is making an environment for the
development with an effective supervision. If we
are doing so, we can attain the maximum
usability of the corresponding resources. Even
after the development, the organization will not
be condition to invest more in the organization.
Therefore, the system is economically feasible.
23

24

UML Diagrams
Introduction
Design is the first step in the
development phase for an engineered product or
system .Design is the place where quality is
fostered in software development .Design is the
only way that we can accurately translate a user
requirements into a finished software product or
system .Software design serves as the foundation
for all software engineers and software
maintenance steps that follow .Without design we
risk building an unstable design-one that will fail
when small changes are made .One that may be
difficult to test, and one whose quantity cannot
be accessed until late in the software engineering

25

Taking software requirements specification document

of analysis phase as input to the design phase we
have drown Unified Modeling Language(UML)
diagrams .UML depends on the visual modeling of the
system .Visual modeling is the process of taking the
information from the model and displaying it
graphically using some sort of standards set of
graphical
elements.
UML Diagrams
are drawn using the pace star UML
Diagrammed Software. We seem to able to
understand complexity better when it is displayed to
us visually as opposed to written textually .By
producing visual models of a system, we can show
how system works on several levels .We can model
and the interactions between the users and the
26
system

Types of UML Diagrams

Each UML diagram is designed to let developers
and customers view a software system from a
different perspective and in varying degrees of
abstraction .UML diagrams commonly created in
Visual modeling tools include.
Use Case Diagram displays the relationship
among actors and use cases.

27

Unified Modeling Language

(UML) Diagram

28

Use case diagram for Admin:

Login

ADMIN

Students
Profile
Teachers
Profile
Employee list

Notice Board

29

Logout

Use case diagram for Teacher:

TEACHER

Login

Profile
Create
Attendance
sheet
Create Mark
sheet
Create Class
Schedule
Notice Board

30

Logout

Use case diagram for Student:

Login

STUDENT

View
Attendance
sheet
View Mark
sheet
View Class
Schedule
View Notice
Board
Logout

31

Use case diagram for Office:

OFFICE

Login
Meeting
Arrangement
Admission
Class
Percentage
Form
Fill-up
Admit Card
Result
Notice Board

32

Logout

Use case diagram for Library Stuff:

Login

Library Stuff

Book List

Given Books
Seminar
ID
Take Book

33

Logout

34

35

36

37

38

39

40

In UML class diagram it

has Admin, Teacher,
Student, Seminar Library,
Office class diagram.
There are shown in next
page.
41

42

43

44

45

46

47

48

49

50

51

52

53

Testing Methods
There are two major type of testing
1) White Box Testing
2) Black Box Testing

White Box Testing

White box some time called Glass Box
Testing is a test case design uses the control
structures of the procedural design to drive test case.
Using white box testing methods, the following test
were made on the system
a)
All independent path will be a module have been
exercise once. In our system ensuring that cases was
selected and executed checked all case structures
.The bugs that were prevailing in some part of the
code where fixed.
54

b) All logical decision were checked for the truth and

falsity of the values.

Black Box Testing

Black box testing

focuses on the functional
requirement of the software. This is black box testing
enable the software engineering to drive a set of input
condition that will fully exercise all functional
requirement for a program .Black box testing is not an
alternative to white box testing
rather it is
complementary approach that is likely to uncover a
different class of errors that white box methods like..
1)
Interface errors
2)
Performance in data structures
3)
Performance errors

55

Unit Testing
Unit testing is a software verification and validation
method in which programmer tests if individual of
source code are fit for use.
A unit is smallest testable part of an application. In
procedural programming a unit may be an individual
function or procedure.
Ideally ,each test case is independent from the
others: Substitutes like method stubs, objects, fake
and test harnesses can be used to assist testing a
module in isolation.

56

Integration Testing
This testing is some time called Integration
and Testing .Integration testing is the phase in
software testing in which individual software modules
are combined and tested as a group .It occurs after
unit testing and before system testing .Integration
testing takes as it input modules that have been unit
tested, groups them in larger aggregates, applies tests
defined in an integration test plan to those aggregates
and delivers as its output the integrated system ready
for system testing.

57

Validation Testing
Validation testing can be defined in many
ways, but a simple definition is that validation
succeeds when the software function is a manner that
can be reasonably expected by a customer. After
validation test has been conducted, one of the
following two possible condition exists .The function
or
performance
characteristics
confirm
to
specification and are accepted.
. In the administrator and modules, all the fields
must be filled.
. In the student registration, mobile number should
contain exactly 10 numbers.
58

User Acceptance Testing

User acceptance of a system is a key factor of
any system .The system under consideration is tested
for the acceptance by constantly keeping in touch
with the prospective system users at the same time of
developing and marketing changes whenever
required .This is done in regard to the following
points:
. Input screen design
. Output screen design

59

60

CONCLUTION
Our project is only a humble venture to
satisfy the need in an Institutions .Several user
friendly coding have also adopted .This package
shall prove to be powerful package in satisfying all
the requirements of the organization.

61

Thank You

62