CHAPTER 1 3
INTRODUCTION 3
1.1 PROJECT OVERVIEW 3
1.2 PURPOSE 4
1.3 OBJECTIVE 4
1.4 SCOPE 4
CHAPTER 2 6
CHAPTER 3 9
CHAPTER 4 14
INTRODUCTION
1.1 PROJECT OVERVIEW
The purpose of this AMS for SDM IMD is to automate the process of
attendance recording and report generation in
order to consolidate the attendance for any
particular student, subject, or term. It would
also help the faculties to know the attendance
of a particular student for his/her course with
just a few clicks rather than going through various sheets to find out
the attendance records manually.
1.3 OBJECTIVE
1.4 SCOPE:
SYSTEM REQUIREMENTS
SPECIFICATIONS
2.1 INTRODUCTION
The System Requirements Study is documented
with an aim to know the users of the system and
the basic activities to be performed by the user. It
tells more about certain constraints, which are to
be implemented in the project, as well as the rules,
which it should follow, in order to merge with the
current processes at SDM IMD so that the whole
system does not have to change.
This chapter explains the functional and non-
functional requirements of the system as well as
the hardware and software requirements. The use-
case diagrams and scenarios have also been
included in this chapter along with the various
other UML diagrams for the AMS.
2.2 PURPOSE:
• Communicates an understanding of users and their interference
with the system.
Helps understanding the limitations, assumptions
and dependencies of the system.
2.3 PROBLEM STATEMENT
At SDM IMD, currently the attendance is taken manually on a sheet.
In that sheet, the students who are present would sign against their
names, which show that they attended the class. Then these
attendance sheets are filed and kept for further usage like knowing
the total leaves of the student for a course or any such thing. Now the
problem with this process is that to know the attendance results of a
particular student or course, the office needs to look through each
and every sheet and then only they can find out the information that
they want. This is very tedious, time consuming and may not be
accurate also.
• The new system to be designed should allow the PGDM office to
enter the data about the attendance of a particular course on a
specific date for the students who have opted for the course.The
PGDM office can only do entering the attendance details.
• If a particular student has not opted for a course, his name should
not be there in the attendance list when that course is selected for
entering the attendance.
• The date for entering the attendance cannot be more than 7 days
before the current date.
• Once the attendance for a particular course on a given date and a
particular session is entered, it should not allow the user to choose
the same combination again, as the attendance for that
combination is already entered.
• At any particular point of time, if a student has been absent for 2 or
more number of classes till the current date, a message should be
displayed telling that.
• Attendance for students of first and second years would differ
slightly because in the first year, it is assumed that all the students
are supposed to undergo all the courses offered where as in the
second year, they are allowed to choose specific courses according
to their specialization.
2.4 ASSUMPTIONS:
• One roll number can only be assigned to one student. And the
length of the roll number would not be more or less than 4 digits.
• Students, who are newly added to the
system, would only be of the 1st year so
there is no need to choose any subjects
or specializations for them.
• For second year students, it is assumed
that each and every one has to choose
some specific subjects. No limit for how many credits and subjects
they can choose are implemented in this system, as its main task is
attendance management.
• It is assumed that all the students for a particular course are
present. So only those who are absent for that particular class have
to be unchecked in the system.
4.3.1 LOGIN
The PGDM member or faculty navigates to the
login page, enters his or her username and
Summary
password and selects the option to login to the
system.
Importance Essential
Priority Expected
Use Always
Frequency
Direct PGDM member, Faculty, Admin
Actor(s)
Pre- The direct actors must have their account in the
requisite(s) system
Minimal System sends an error message when the direct
guarantee actor fails to login to the system
Display the home page to the respective actor who
Success
has logged in successfully.
guarantee
1.) Visit login page
Main
2.) Enter username and password
Success
3.) Select the option to login to the system
Scenario
4.) See personalized home page.
User enters incorrect username and password
Alternative
1.) The “login” page with empty fields and error
2a Scenario
message is displayed.
Extensions
2.) Perform UC-Login: Login to AMS steps 2-4.
1.) The username and password fields are
Business mandatory.
Rules/ 2.) The password should be alphanumeric and the
Constraints minimum length of password should be 6
characters.
4.3.2 ADD NEW STUDENTS
COURSE
The course class contains various methods related to course like
adding new courses, modifying the
existing ones or deleting some
courses from the system. It also has
the method, which displays all the
courses on the page.
The methods for adding, updating or deleting the course have the
return type of Boolean because they would return whether the
corresponding methods have done the work they were allotted to do
or were unsuccessful.
The method ‘View Courses by Faculty (FacId)’ would help us in
showing the courses taken by a given faculty. It takes the ‘FacId’ as
the parameter and the return type would be an object of the type
‘Course’.
There are no sub classes or super classes for Course.All the methods
are declared as ‘Public’ methods.
STUDENT
The student class contains the details about the students and the
courses they have opted for (for 2nd year students). It contains
methods, which allow showing the list of all the students. It also
contains methods, which allow adding, modifying or deleting the
details about the students.
The method ‘View Students by Course ()’ allows getting the list of
students who have taken a particular course, which helps to generate
the list of students during the attendance entries.
There are no sub classes or super classes for Course. All the methods
are declared as ‘Public’ methods.
ATTENDANCE
The attendance class is the core of the system and does the most
important task of marking the attendance of the students and is also
responsible for major part of the report generation.
The main method of this class is ‘Enter Attendance ()’. It allows
adding the attendance details to the database. This class has to fetch
details from all the other classes and then add these details to the
database. It also contains methods to ‘view attendance details’ as
well as to modify them.
For the report generation, this class will contain methods like, ‘Get
Attendance by Course (CourseId)’ or ‘Get Attendance term wise (term
No)’, etc. which helps the retrieval of the data in a more efficient and
faster manner.
There are no sub classes or super classes for Course. All the methods
are declared as ‘Public’ methods.
FACULTY
This class is just to get and set the details about the faculties by
using methods like ‘Add Faculty Details()’ or ‘Modify Faculty Details
()’. It also helps in displaying the list of faculties in the system by
using the ‘View Faculties ()’ method.
For special purposes like viewing some specific faculties based on the
course, it has the function ‘View Faculties by Course (CourseId)’ which
will give the faculties that take a particular course. It also has ‘View
Faculties by Area (AreaOfSpec)’ which will give a list of all the
faculties belonging to a particular area of specialization.
CHAPTER 6
IMPLEMENTATION
ENVIRONMENT
Da
ta
La
yer
Bu
s
La
yer
Printer
CHAPTER 7
TESTING
7.1 INTRODUCTION
7.2 SCOPE
Various such test cases would be prepared to check the quality of the
system.
7.6 A PROTOTYPE