DEPARMENT Of COMPUTER SCIENCE AND ENGINEERING

(Accredited by NBA 2021-2024)

A CASE STUDY ON

HOD OFFICE AUTOMATION SYSTEM

Subject: Software Engineering

Code: 18CS35

Date of announcement: 07/02/2022

Date of submission: 28/02/2022

Instructor:
Dr. Manu A P
Prof., Dept. of CSE

Submitted by
GURUKIRAN B [4PM20CS038]
HARSH MISHRA [4PM20CS039]
HARSHA M S [4PM20CS040]
HARSHITHA R [4PM20CS041]

PES INSTITUTE OF TECHNOLOGY AND MANAGEMENT

(Approved by AICTE, New Delhi, Affiliated to VTU, Belagavi, Accredited by NAAC. ISO 9001 Certified)
NH 204, Sagar Road, Shivamogga - 577 204
 DECLARATION

We Gurukiran B (4PM20CS038), Harsh Mishra(4PM20CS039), Harsha M S

(4PM20CS040), Harshita R(4PM20CS041) students of 3rd semester B.E. in Computer Sci-
ence and Engineering, PESITM, Shivamogga hereby declare that the case study report en-
titled “HOD Office Automation System” which is being submitted to the PESITM, Shiva-
mogga is a record of an original work done by us under the supervision of Dr Manu AP.
Prof., Dept. of CSE, PESITM, Shivamogga.

Gurukiran B, Harsh Mishra, Harsha M S, Harshita R

(4PM20CS038) (4PM20CS039) (4PM20CS040) (4PM20CS041)

Place: PESITM, Shivamogga.

Date: February 28, 2022
Chapter no. Content Page no.

1 INTRODUCTION 4
2 SOFTWARE PROCESSES 5-8
3 MODELLING 9-
3.1 USE CASE DIAGRAM 9-10
STATE DIAGRAM 11
SEQUENCE DIAGRAM 12-13
CLASS DIAGRAM 13-15
ARCHITECTURE DIAGRAM 16-17
4 IMPLEMENTATION SRS 18-19
5 TEST CASES 20-22
6 COCOMO 2 MODEL 23-26
7 REFRENCES 27

Table Of Content
 HOD OFFICE AUTOMATION SYSTEM

INTRODUCTION

Office automation is the process of watching data flow around on its own
without any human intervention, inaccuracies, and errors. It is the process of
using an automation tool to create, collect, store, analyse, and share confidential
office data that is required to accomplish basis day-to-day routine tasks and
processes effectively.
An office automation system is the tool that enables data to move from one
system to another on its own without human intervention and inaccuracies.
These tools help organizations collect, manage, and analyse securely to
accomplish everyday tasks and processes. It optimizes and automates existing
business processes and procedures
HOD office automation system is a type of automation system in which the
Head Of The Department is able to keep track of all the activities in the
department for example can keep track of students performance, regularity, can
set time table for students, can see the details of students

It helps to control or maintain the department of the college by sitting in one

place. Students can also use some part of automation system like they can also
see their progress, about their mentors, they can also give feedback about the
department teaching and their mentors.
 SOFTWARE PROCESSES
1) Water fall model
The waterfall model is the earliest software development life cycle
approach that was used for software development. The waterfall model illustrates the
software development process in a linear sequential flow. This means that any phase
in the development process only begins only if the previous phase is completed.

The phases are

1) Requirement Analysis and definition:
In this phase we asked the constraints, services and goals which
should be achieved by the system from the users and the requirements
are addressed in detail.
The requirements we obtained were:
1) Attendance: The automation system should keep track of the at-
tendance of students and staffs of the department.
2) Timetable: The timetable should be set like that all the subjects
are given required amount of time.
3) Student data: The automation system should hold all the data of
the student and keep track of all the progress of students
4) Fee details: The automation should hold the details of fee pay-
ment of students of the department if it is pending or paid com-
pletely.
5) Progress report: It should hold the progress report of all students
in all tests.
2) System Design: The requirements are allocated to either to hardware
based on the architecture of the system. It involves identifying and de-
scribing the fundamental software system abstractions and their rela-
tionships.

3) Implementation and unit testing: During this stage the requirements

are divided into separate units and programs are developed for certain
units like attendance tracking, progress report, fee details etc. Then the
program of each unit is tested if it meets the customer requirements
and works according to its specification.

4) Integration and system testing: During this stage the programs for each
unit like attendance tracking, student details, fee details etc. are inte-
grated and formed as a system. Then the system is tested to see if it
meets the specification and expectations.

5) Operation and maintenance: The system is installed and put into practi-
cal use. If any fault is found repairs are done and further the system is
updated as per the requirement.
Phase-1: Requirement engineering
Functional requirements:
 Attendance: The automation system should keep track of the atten-
dance of students and staffs of the department.

 Timetable: The timetable should be set like that all the subjects are
given required amount of time.

 Student data: The automation system should hold all the data of the stu-
dent and keep track of all the progress of students

 Fee details: The automation should hold the details of fee payment of
students of the department if it is pending or paid completely.
 Progress report: It should hold the progress report of all students in all
tests.

 Mentoring: The system should contain all the mentors and students un-
der those mentors and how those students fared under those mentors.

 Feedback: the system should take feedback from students about teach-
ing and store it in the database.

Non-Functional requirements:
 Performance: The system should minimize errors. The performance of
the function should be well.

 Correctness: The results provided by the system should be accurate by

validating and testing the system.

 Reliability: The system should be reliable and should not give major er-
rors.

 Reusability: The data in the system should be reusable and it should be

stored in the backup.
  Security: Security is the very important requirement in this system in-
cluding privacy. The developer should provide high security interface
and protect the details in system.
The external security should be provided by giving the login
authentication. There should be proper security regarding to the accessing
of data by unauthorized user.

Domain requirements: The list of students should appear when a

letter is typed in search of students of same letter.
 MODELLING

USE CASE DAIGRAM:

This use case diagram is a graphic depiction of the interactions
among the elements of college management system. It represents the
methodology used in system analysis to identify
Clarify and organize system requirements of college management system. The
main actors of college manage system in this use case diagram are super admin,
system user, faculties, student, who perform the different type of use cases such
as manage college, manage students, manage classes, manage faculties, manage
courses, manage registrations, manage users and full college management
system operations. Major elements of the UML case diagram of college
management system are shown on the picture below
The relationships between and among the actors and the use cases of college
management system;
 Super Admin Entity: Use cases of super Admin are manage college, man-
age students, manage classes, manage faculties, manage courses, man-
age registrations, manage users and full college management system op-
erations
 System User Entity: Use cases of system user are manage college, man-
age students, manage classes, manage faculties, manage courses, man-
age registrations
 Faculties Entity: Use cases of faculties and create timetable, add exams,
add results
 Student Entity: Use cases of student are view timetable, view results
STATE DAIGRAM:

State diagrams are used to show how objects respond to different service
requests and the state transitions triggered by these requests. State diagrams
are useful high-level models of a system or an object’s run-time behaviour.
You don’t usually need a state diagram for all of the objects in the system.
Many of the objects in a system are relatively simple and a state model adds
unnecessary detail to the design
SEQUENCE DIAGRAM :

Sequence diagrams show the interaction between participating

objects in a given use case they are helpful to identify the missing
objects that are not identified in the analysis object model. To see the
interaction between objects, the following describe the sequence
diagram of
each identified use cases.
CLASS DIAGRAM:

Class Diagram is the way to represent the relationship between the

classes. In this article, we will see about the class diagram for the
College Management system.
Classes:
 College Management – This class is the overall main class
of the whole system.
 Department – This class contains the details of various de-
partments in the college.
 Student – This class is for students and it is the base class
for two child classes – UG Student and PG Student. Since UG
Student is a Student and PG Student is a student
 UG Student – This class is the child class of Student and it
contains the details of UG Student.
 PG Student – This class is the child class of Student and it
contains the details of PG Student.
 Staff – There are two types of staff in the college so this
class is the base class of two child classes – Teaching Staff
and Non Teaching Staff
 Teaching Staff – This class is the child class of Staff. Since
Teaching Staff is a Staff.
 Non Teaching Staff – This class is the child class of Staff.
Since Non Teaching Staff is a Staff.
Attributes:
 College Management – College Name, City, Contact Num-
ber
 Department – Department Id, Department Name, HOD
Name, Total Staffs, Total Students
 Student – Student Id, Student Name, Gender, Year, Class Id
 Staff – Staff Id, Staff Name, Department Id, Salary
 Classroom – Class Id, Section, Department Id
Methods:
1. College Management:
 Open () – This method tells whether the college is open or
not.
 College Details () – This method contains the college de-
tails like name, its location and contact number.
2. Department:
 Department Details () – This method contains the depart-
ment name and its corresponding Head of the department
name, the total students count of each department.
 Show Events () – This method is to show any events in a
particular department.
3. Student:
 Student Details () – This method contains all the informa-
tion about each and every student in the college.
 Pay Fees () – This method contains the payment status of
each student.
 Is Present () – This method shows whether the student is
present to the college on a particular date.
4. Staff:
 Staff Details () – This method contains the details of both
teaching as well as non-teaching staff along with their salary
details.
5. Classroom:
 Classroom Details () – This method shows the details of
each classroom and to which department the classroom be-
longs.
 Is Occupied () – This method tells whether the classroom is
occupied or not
ARCHITECTURE DIAGRAM:

An architecture diagram is a visual representation of all the elements that

make up part or all of the system. It helps the engineers, designers,
stakeholders and anyone else involved in project understand a system or
applications layout.

An architecture diagram is a diagram of the system that is used to abstract

the overall outline of the software system and the relationships,
constraints, and boundaries between components. It is an important tool as
it provides an overall view of physical deployment of software system and
its evolution roadmap.

These diagrams help with comprehension and improve the communication

and collaboration.
 IMPLEMENTATION
The implementation phase is where we actually do the project work to produce
the deliverables. The word “deliverable” means anything that our project deliv-
ers. The deliverables for our project include all of the products or services that
we are performing for the client, customer, or sponsor, including all the project
management documents that we put together.

The software implementation stage involves the transformation of software

technical data package into one or more fabricated, integrated, and tested soft-
ware configuration items that are ready for software acceptance testing.

Software implementation refers to the process of adopting and integrating the

software applications into a business workflow as a part of a digital transforma-
tion strategy.

Implementation of a new tool and software into an enterprise can be complex,

depending on the size of organization and the software.

The important parts of the software requirements specification (SRS) document

are:

1. Functional requirements of the system,

2. Non-Functional requirements of the system.

3.Goals of implementation

By the functional and the non functional this software, the automation system
should keep track of the attendance of students and the staff and the required
specific attendance should be maintained by it. It used to be maintain the
timetable and all the subjects are given required amount of time. Also the auto-
mation system is used to collect and preserve the data of the students and also
faculties also it should look after their performance and keep track all the pro-
gress of them.

The automation system should also maintain and hold the progress report of all
the students in all the internals (tests).

It also take the feedback from the students about the teaching and store it in the
database.

The automation system should be reliable and should not give major errors and
data in the system be reusable and stored in the backup. Security is also very
important requirement in this system including the privacy. The developer
should provide the good and high security interface and protect the details in the
system.
 TEST CASES
Project Testing is an investigation conducted to
determine the quality of the project and the services
provided by the project. Testing is the process of
analysing a project to detect the differences between
existing and required conditions (i.e.
defects/errors/bugs) and to evaluate the features of the
project.

After complete development of the project it is

mandatory to test the project. The main motive of the
project testing is to identify whether project is able to
meet user requirements or not. To know the better
performance of project we have to develop various test
cases.

Now, designing good test cases is a complex art. The

complexity comes from three sources: Test cases help
us discover information. Different types of tests are
more effective for different classes of information.

Testing Objectives:
The main objective of testing is to uncover a host of
errors, systematically and with minimum effort and
time. Stating formally, we can say, Testing is a process
of executing a program with the intent of finding an
error.

A successful test is one that uncovers an as yet

undiscovered error. The tests are inadequate to detect
possibly present errors. The software more or less
confirms to the quality and reliable standards.

TYPES OF TESTING:

1)Unit Testing:
During this phase, each module is unit tested to de-
termine the correct working of all the individual
 modules. It involves testing each module in isola-
tion as this is the most efficient way to debug the
errors identified at this stage. Another reason be-
hind testing a module in isolation is that the other
modules, with which this module has to be inter-
faced, may not be ready.

2)Integration and System Testing:

During the integration and system testing phase,
the modules are integrated in a planned manner.
The different modules making up a software prod-
uct are almost never integrated in one shot. Inte-
gration is normally carried out incrementally over a
number of steps.

During each integration step, the partially inte-

grated system is tested and a set of previously
planned modules are added to it. Finally, when all
the modules have been successfully integrated and
tested, system testing is carried out. The goal of
system testing is to ensure that the developed sys-
tem conforms to its requirements laid out in the
SRS document.

Our project is integrated and tested by using an ac-

tivity by name - testing. - testing is the system
testing performed by the development team

3)Acceptance Testing:
Acceptance testing is often done by the customer
to ensure that the delivered product meets the re-
quirements and works as the customer expected.

It falls under the class of black box testing.

4)Regression Testing:
 Regression testing is the testing after modification
of a system, component, or a group of related units
to ensure that the modification is working correctly.

It should not damaging or imposing other modules

to produce unexpected results. It falls under the
class of black box testing

5)Beta Testing:
Beta testing is the testing which is done by end
users, a team outside development, or publicly re-
leasing full pre-version of the product which is
known as beta version.

The aim of beta testing is to cover unexpected er-

rors. It falls under the class of black box testing

(FOR OUR DOMAIN THE BETA TESTER IS GEMS APP

OR WEBSITE)

COCOMO-2 MODEL

COCOMO stands for Constructive Cost Model . It is one of the most famous
model which is used to estimate the cost of the software. COCOMO model was
proposed by Boehm in the year 1981. Using this model we can estimate time
(month) and number of people needed to develop a software.

The three stages are :

• Basic
• Intermediate
• Complete
Basic:
It gives an approximate estimation of the project parameters, it predict the
effort and cost of the project.
Effort =a1*(KLOC)a2 PM
Time= b1*(effort)b2months

Intermediate :
It is the extention of basic stage. It uses 15 additional predictors ,consisting
it’s environment to estimate a value or cost.

Complete :
This model is phase sensitive. Used to calculate amount of effort required
to complete each phase.
Sub models in COCOMO are
• Application composite model.
• Early design model.
• Reuse model
SCREEN 1 2 3 • Post
REPORT 2 5 8 archi-
tecture Model

Objects points is computed using counts of number

• Screen
• Report
• Components likely to be required to build the application

Here for semi-detached type:

a1 = 5 ,a2= 1.3 , b1= 2.8 ,b2= 0.48

E= 5(10)1.3( KLOC= 10000) =99 PM

Time= 2.8(99)0.48 = 25 months

Person estimation= Effort/Time

= 99/25
= 3 members

OBJECT TYPE COMPLEXITY WEIGHT

 SIMPLE MEDIUM DIFFICULT

TABLE-2

Developer ex- Productivity

perience capab-
ility

Very low (vl) 4

Low (l) 7
Nominal(n) 13
High (h) 25
Very high (vh) 50

To our project we used 10000 lines of code, 20% reusability and Nominal pro-
ductivity ( i.e. 13)

Object points = screen: 7*2=14

Record: 3*5=15
So, total object points = 29
NOP= ( object points)*((100-%reuse)/100)
NOP = 29*((100-20)/100)
= 29*(80/100) = 23.2
Effort= NOP/PROD
= 23.2/13
 = 1.784

Based on a standard formula for algorithmic models .

PM = A SizeB M
M= RUSE*RCPX*PERS*PDIF
A= 2.9 in initial calibration
Size = Kilo lines of code (KLOC)
B= varies from 1.1 to 1.24 depending on novelty of the project, flexibility,risk
management.
Hence , PM = 2.94(10)1.17*1 PM
= 43.485
Salary of a person per month =20,000
Effort =PM*per person cost
43.485*20,000
8,69,700

REFRENCES

1. CSE Department’S HOD

2. Mr. Devraj F V
3. SOFTWARE ENGINEERING BY Sommerville(8th edition)
4. www.GeeksforGeeks.com
5. Ecampus_lncs