SOFTWARE REQUIREMENTS

SPECIFICATIONS
For
Student Monitoring and Advising System

Prepared By:
Angelo D.Olaivar
Nurman M. Amil
Mary Rose Andico
Shanen Fae Turco

July 23, 2018

 Table of Contents
1.0 Introduction….…………….…………………………………………………………………..1
1.1 Purpose…………………………………………………..…………………………… 1
1.2 Document Conventions…………………………………………………..……………1
1.3 Intended Audience and Reading Suggestions………….……………………………...1
1.4 Product Scope……………………………………………………..…………………..1
1.5 References………………..……………………………………………..……………..1
2.0 Overall Description…………………………….…………………………..………………….2
2.1 System Environment ……………………………………………..…………………...2
2.2 Functional Requirements Specification……………………………….………………2
2.2.1 Student Use Case.…………………………...………….…………………2
Use case Input Info:.…...…………………………….......…………….2
2.2.2 Adviser Use case…………………………………………………………..3
Use case: Check Grade……………...…………………………...…….3
Use case: Assign/Add Subjects………………………………………..4
Use case: Remove Subject…………………………………………….5
Use case: Change Subject………………………………………..……5
Use case: Print Subjects………………………………………….……6
Use case: Update ROS…………………………………….………….7
2.3 User Characteristics………………………...…………………………………………7
2.4 Non-Functional Requirements………………………………………………………...8
1.0 Introduction

1.1 Purpose

The purpose of this document is to provide a system about Student monitoring

and advising system. It gives the necessary subjects for the students, monitor students
grade and track the records of students. The system will help both the adviser and
student.

1.2 Document Conventions

WMSU - Western Mindanao State University
- University which vision is to educate student and guide them with knowledge.
ICS - Institute of Computer Studies
-An institute that tackles about computer science and information technology.

1.3 Intended Audience and Reading Suggestions

The student should approach the adviser first, in order to know the available
subjects that can be taken. So, the adviser coheres the grades of the student if they are
allowed to take the subject accordingly.

1.4 Product Scope

The Student Monitoring and Advising System is intended for student and adviser.
The system is designed to assist the process of monitoring students grades, advising and
tracking the rendering services of the student, which would otherwise have to be per-
formed manually, by improving the adviser’s work and time efficiency.

1.5 References
Student Guidance Information and Monitoring Website with SMS Notification,
Rochelle C. Candido, Jessa Faye V. Narvassa, Cristalyn A. Ramonez, and Czarina Y.
Usup, 2018

1
2.0 Overall Description

2.1 System Environment

STUDENT
PAGE

ADMIN
ADVISER PAGE

Teacher STUDENTS MONITORING AND

Student
ADVISING

Figure 1 – System Environment

The Student Monitoring and Advising System has one active actor and cooperating
system. The Teacher access the system and inputs data. The adviser provides and access the
system directly.

2.2 Functional Requirements Specifications

2.2.1 Student Use Case

Use Case: Inputs Information

Diagram:

Input Info

Student

Brief Description
The student inputs information and the adviser gives necessary subjects to the students.
2
Initial Step-by-step Description
Before this use case can be initiated, the student has already accessed the Student
Monitoring and Advising System.
1. The student inputs information.
2. The system will display the choices grades, subjects , or the return of service
(ROS).
3. The Students selects desired link to present to the adviser.
4. The System / Adviser will provide recommended subjects.

2.2.2 Adviser Use Case

The adviser has following sets of use case:

Check Student Info

Update Student Subjects

Adviser
Update ROS

Check Student Info Use Case

Use Case: Check Grade
Diagram:

Check Grade

Adviser
3
Brief Description
The adviser inputs student name or student ID and checks students grades.
Initial Step-by-step Description
Before this use case can be initiated, the adviser has already accessed the Admin form.
1. The adviser inputs the student name/ID#.
2. The system presents the course, year, and grades.
3. The adviser select student grade.
4. The system display the student grades.
5. The system verifies the student grades and return the adviser to the admin main
page.

Update Student Subjects

Use Case: Assign / Add Subject
Diagram:

Add Subject

subjectAdviser Student

Brief Description
The Adviser assign subjects to the student.
Initial Step-by-step Description
Before this use case can be initiated, the adviser has already accessed the update student
subject use case.
1. The adviser selects assign subject.
2. The system present a list of subjects with the units.
3. The adviser select subjects to add to the students subjects.
4. The system verifies the subjects assign to the student subjects.
5. The system returns the adviser to the update student use case.
4
Use Case: Remove Subject
Diagram:

Remove Subject

Adviser Student

Brief Description
The Adviser removes subject, if the current subject was failed to pass the pre-
requisite subject.
Initial Step-by-step Description
Before this use case can be initiated, the adviser has already accessed the update
student subjects use case.
1. The adviser select verified student subjects.
2. The system presents the students subjects.
3. The adviser selects subject to remove to the student subjects.
4. The system verifies the removed subject to the student subjects.
5. The system returns the adviser to the update student use case.

Use Case: Change Subject

Diagram:

Change Subject

Adviser Student
Brief Description
5
Brief Description
The Adviser Changes subject, if the current subject was failed to pass the pre-requisite subject.
Initial Step-by-step Description
Before this use case can be initiated, the adviser has already accessed the update
student subjects use case.
1. The adviser selects alter subject as an exchange for the removed subject.
2. The system present a list of subjects with the units.
3. The adviser select subjects to add to the students subjects.
4. The system verifies the changed subjects to the student subjects.
5. The system returns the adviser to the update student use case.

Use Case: Prints Subject

Diagram:

Prints Subject

Adviser

Brief Description
The adviser prints the verified subjects of the students.
Initial Step-by-step Description
Before this use case can be initiated, the adviser has already accessed the update student
subjects use case.
1. The adviser select the verified student subjects.
2. The system presents the student assign subjects with their units and total no. of
units.
3. The adviser selects print subjects.
4. The system will automatically print the subjects.
5. The system returns the adviser to the update student subjects use case.
6
 Update Rendering of Service
Use Case: Update Rendering of Service
Diagram:

Update ROS

Adviser

Brief Description
The adviser input student name and update the record of rendering service of a
student.

Initial Step-by-step Description

Before this use case can be initiated, the adviser has already accessed the admin
form.
1. The adviser select to Add/Update ROS.
2. The system presents a choice of adding or updating ROS.
3. The adviser chooses to add/or to update.
4. The system links to the ROS History database.
5. If the adviser is updating the ROS, the system presents the current status of ROS,
else the system adds no. of hours to ROS.
6. The system verifies the student ROS and returns the adviser to the Update ROS
use case.

2.3 User Characteristics

The teacher is expected to be computer literate and knows how to use a computer to
use the system. The system has a help section for the user to read on how to use the system. The
teacher can use all the functionalities of the system, like add, edit, update and delete.
The student is expected to have a knowledge about computers to be able to use the
system. The student has limited access to the system, like they can only view information for
security reasons.
7
 2.4 Non-Functional Requirements
The Student Monitoring and Advising System is a computer base application. The
installation of the software will depend on the compatibility of the user’s computer hardware.
Help tabs will appear on the first run to guide the user.

2.4.1 Performance Requirement

The user must have a Pentium processor or higher like i3, i5, or i7 processors. The
system runs smoothly on higher processors. It’s works on Windows 7, Windows 8,
Windows 8.1, and Windows 10.

2.4.2 Safety Requirement

The Student may save their records in their flash drive before exiting the program.
The Adviser must always have a backup of the record so that even if there is sudden loss
of record.
2.4.2 Security Requirement
The System is encrypted for the security of student information. The Student has
only limited access to the system.