Curriculum Manage System Chapter i i i

Student Information System

Chapter III

3.1 Software Requirements Specification

3.1.1 Introduction

Curriculum Management System requires the specific role of a user onto system. This

chapter represents on how the requirements describe as will to easy comprehend, to

illustrate on how the flow and portrait different diagram like relationship, activity diagram,

state chart diagram, and use case diagram to be clearly understand what system is.

From this chapter, it will help the end-users to know the usage and those scenarios, the

acknowledgement, the intention, the purpose and admission to the system.

3.1.1.1 Goal and Objectives

The purpose of this document is to describe the requirement of the school that

will include the revision of their existing system to become accelerate with accurate

reports. It is important that the project must meet or reached the expectation and

achieve the good transaction to be attaining the satisfactory of client. This document

uses written descriptions as well as various types of different diagrams to illustrate

the high level structure of the application. Although some of the diagrams may seem

ti convey similar information they typically do so from an alternate perspective. This

give different stakeholder a view of the requirements that is better suited to their area

of responsibility.

3.1.1.1.2 General Objective

3.1.1.1.2.1 To develop an existing curriculum management system in

managing school year in accurate.

The Curriculum Management System helps Grace Montessori School

of Novaliches to input/transfer immediately data and information

process or transactions on that day to be done soon as possible.

Grace Montessori School of Novaliches (Curriculum Management System) Page 3- 1


3.1.1.2 Statement of Scope

To explain the user requirement and are those needed things to consider in

creating a system and considered as necessary because it guides how the system will

make and to consider the needs of the users. Illustrate the various types of different

diagram show the different function and explanation how the system for. Those

diagrams help the users to understand the function and to help the user to manipulate

the system by them.

A complete and descriptive detail of system requirement and a complete scenario of

the system process with the use of different diagram to illustrate the structures of the

application. Thus, the management of the data and transaction will be all

computerized.

Before gaining access to the Curriculum management system, user will be required to

enter their user name and password. A user access privileges within the system are

determined by their job classification. The Administrator will have unlimited access

whereas registrar and student will have fewer privileges below.

The following table groups are user requirements and segregate this into various

categories. The requirement is assigned priority requirements to indicate whether it

must be implemented (high) or (medium) and (low). High priority requirements are

essential requirement of the system. Medium priority requirements are not essential or

didn’t totally focus just fulfilling to become or called a whole system. And low

priority is requirements may be eliminated if it helps meet the scheduled delivery

date.



Req. No. Priority Reference DescriptionAccess Privileges

R1 High Program There have been three character or access

designations: one for administrator, the

second user is registrar and the last can

access the system those students have

account.

R2 High Administrator The administrator capable to edit all

account information, system data and

implement new update in system.

R3 Medium Administrator

and

Registrar

Administrator and Registrar are allowed to

print those request reports.

R4 High Student Viewing and updating an account

information and daily reminder of school or

system

R5 High Administrator The administrator has authorizations to

change the registrar setting privileges.

R6 High Administrator The administrator is allowed to add new

account, subject, event calendar and those

memorandums of DepEd.



Security

R5 High Program All users have a unique User ID

and password required to log

onto system.

R6 Medium Code Access Access granted if account is valid

when after third attempt the user

account will be locked.

R7 High Administrator An account shall be assigned by

administrator to each user.

R8 High User The account user shall contain

10-12 alphanumeric characters.

R9 High Administrator After five unsuccessful attempts

to enter, the account shall be

locked out until 12hr’s retrieve.

R10 High Administrator A new password shall be

assigned by administrator if

users forget his/her password.

R11 Low User If there is no activity or idle for

15 minutes the user automatically

shall be logged off onto the

system.

R12 High Program Log-in form of we’ve made system have user Designation before gain to access the system.

Account Information



R13 High Program Store, keeping and update record

like, subject information, student

information, and curricular

information. As well for; new

curricular implemented, subjects,

grade level, time, room, section,

assign teacher, schedule and

other detail.

R14 High User The user’s account record shall

contain the following

information:

• User ID

• User Password

• Email address

• Access level

R15 High Student The student account record shall


information:

• Name

• Photo

• Gender

• Age

• Date of birth

• Address

• Email address

• Phone number



R16 High Database The table subject record shall


information:

• Subject ID

• Subject Name

• Subject time implemented

• Subject date implemented

• Subject Description

R17 High Database The table grade level record shall


information:

• Grade level ID

• Grade level name

R18 High Database The table grade level record shall


information:

Set subject ID

Set subject name

Set subject description

R19 High Database The table schedule record shall


information:

•Grade level ID

•Section ID

•Room ID

•Set subject ID

•Day ID

•Time ID



• Teacher ID

• Description ID

R20 High Database The table curricular activities

record shall contain the following

information:

Activities ID

Activities name

Date

Time

Event place

Event Description

R21 High Database The table section record shall


information:

Section ID

School year

Section name

Number of student

R22 High Database The table time and date record

when login shall contain the

following information:

TimeID

DateID

Status

R23 High Program User log notes shall store the date

and time.



R24 High Database The table section record shall


information:

• Teacher ID• Teacher name

R25 High Program Student reports shall be print all

of the information of the student

including the name, age, birth

date, contact information and

their scheduled.

R26 High Program Master list report shall alphabetically list the name of the student categorized by male and female.

Reminders



R27 High Administrator Administrator shall only allow

setting the daily reminders in

system.

R28 Medium Administrator The administrator limit enters 60

character messages only for the

reminders.

R29 Medium Code Access The time/date of reminder or

event shall be show and we

selected from calendar.

R30 Low User When user log onto the system,

the first that can saw in

displaying in screen are those

reminders.

R31 Low User The user can view the current and

recently event by selected or

click date at calendar.

R32 Medium Administrator

And

Registrar

Administrator and registrar are

allowed to print those reminders

and event description.

3.1.1.3 Software context



However, the functionalities of Curriculum Management Information Systems

(CMS), have lagged significantly behind the capacities of current hardware and

software technologies, while the complexity of the information produced by school

has been increasing over time and will soon undergo rapid expansion with the use of

new, high-throughput and high-dimensionality language. In the broadest sense, CMS

are essential to manage the flow of information between the curricular provide by

DepEd, should be designed to optimize not only school managing but also

personalized student welfare when it comes curricular.

In order to cope the project the proponents will be using different types of software

O.S Windows 7 Professional Service pack 1 32 bit 1Gb(RAM) for document

purposes & O.S Windows 7 ultimate 64Bit Processor AMD ATHLON 1.60 GH,3.6

GB(RAM) & Eclipse Indigo 3.7, MySQL Version 5.6 11MySQLyog Ultimate

XAMPP win32version 1.8.3 XCII MSWord 2010 this are the software were going to

use in able to perform the project.

3.1.1.4 Major Constraints

All new code shall be original constraints place upon documented at BCP to be

documented by BCPian’s journey to project study documentation system.

• The Student information system, language will be use java eclipse 3.7 environment

which requires a database like MySQL supporting this technology.

3.1.2 Usage Scenario



3.1.2.1 User profiles

There have (3) three characters can access the system; one for the registrar and

their assistant then for student and one for administrator. The following definition

describes the actor in the system.

Administrator or Principal

The one capable or allowed to edit all data like account/user information and those

old/new subject’s that have availability to add a new user and curriculum

implemented by DepEd.and etc.

Creating and Updating with setting and activating a current school year activities

and subject’s with the use of the computerized system the user can easily filter and

print all the student request

When DepEd has contract a new subject or change it their subject name, the

administrator shall be allowed to create or add subjects at subject list, that will

create an new description for new subject. So, the old subjects become now fix but

can edit by administrator and can gathered data or subject report of those alumni

that can browse and printable. The present subject lists will process continuously

keeping stored a data.

Registrar or Assistant

The registrar is the one is accountable for keeping the good maintenance of the

previous and current data and files of each student. The system provides the

registrar to update those student account information and reminder’s to can

generate a print report’s.

Viewing, updating, browser, editing data those not fix like subject description,

subject list and etc.

The things that can’t act are didn’t allowed to edit those old subjects taken by the

alumni and no access to create other new user’s or account.

Student



Only viewing and updating his/her old/current info.

System

The system refers to the computer hardware and software that control the application.

The system can also generates reports, provide user access, store data into the

database and have the features of add information, editing, saving and printing.

Web-Based

The Web server is a remote computer system that maintains the database and serves

Web pages to the System.

WEB based with all students to update easily will communicate with Web server on

the internet through a high speed network connection WEB based is designed for

those clients who are busy and doesn’t have time to go to school?

Lan-Based

Is a computer network that interconnects computers in a limited area such as a home, school, computer laboratory, office building, for walk in transaction.

3.1.2.2 Use-cases



The following use-cases are interaction between the external environment and the internal

software system. Each use-case are all described in 3.2.2.1

Student log onto system

Administrator or Registrar log onto system

View and Update account information

Subject implemented onto system

Print/view reports

Subject teacher assign

Grade level/ Set subject scheduled

Set a calendar

New / Set User

Display Notification massager

Search engine

Sign out onto system

3.2.2.1 Use-Case Diagram



The use-case diagram, shows 3 (three) actors with different job description maybe they’re a

little bit comparison but each of them have limited can’t do in system; every use-cases will

typically involve an interaction with the system wave made. The principal can be

administrator.

3.2.2.2 Use-Case Descriptions



Use-case: Log on to System

Primary actor: Student

Goal in context: To gain access to the System.

Preconditions: The student has a valid user name and password.

The account of student can’t be use or log by the other user.

Trigger: A student needs to access to the system to update his/her current

scheduled and subject information.

Scenario:

1. The Student logs onto the web server System.

2. The Student selects user designation.

3. The Student enters the Login ID and Password.

4. The system verifies the Login ID and password

5. If Student enters (3) three times attempt incorrect the

account has been locked.

6. Only administrator can retrieve student account.

7. Access granted invalid account enter.

8. Message box will show saying “ACCESS GRANTED”

9. The Student is given access to view/update.

10. The Student views the daily reminders.

11. The Student click Update button.

12. Viewing student information.

13. Viewing student scheduled.

14. Viewing Curricular Activity.

15. Viewing Calendar event Activity.

16. The System will displayed the suggest info.

17. The Student is given access to view/update.

Exceptions: The user name and password cannot be verified.

Use-case: Log on to System



Primary actor: Administrator or Registrar

Goal in context: To gain access to the System.

Preconditions: The Administrator or Registrar has a valid user name and password.

Trigger: Administrator or Registrar needs to access to the system to update the

scheduled and current subject information.

Scenario:

1. Logs onto the System.

2. Select user designation.

3. Enters the Login ID and Password.

4. Verify the account.

5. System will displayed message prompt.

6. If administrator enters (3) three times attempt incorrect the

account has been locked out on 12hr’s.


8. Message box will show saying “ACCESS GRANTED”

9. Record the time and date logged.

10. Given access to manage system base in their job description.

Display Notification massager

Exceptions: The user name and password cannot be verified.

Use-case: Update account Information



Primary actor: Administrator/Registrar

Goal in context: The administrator updates the account information.

Preconditions: Administrator is only allowed to update all account information while

Registrar is only allowed to update all Student account information

onto system.

Trigger: Administrator needs to access to the system to edit and update the

changes of account information.

Scenario:

1. Administrator logs onto the System.

2. Administrator enters the Login ID and Password.

3. Verify the administrator/Registrar account.


5. Administrator/Registrar time and date logged.

6. Click the button of account information.

7. Administrator/Registrar views the old and current account.

8. Administrator can view all account information while Registrar

only allowed to all student account.

9. Select Account information.

10. Enter student/registrar ID number.

11. Edit and update the student account.

12. Click the save button to be changes.


14. Successfully update the account information.

15. Logged out to the system.

Exceptions: Only student can update by registrar account information while

administrator can edit all user account setting.

Use-case: Implementing Subject



Primary actor: Administrator

Goal in context: The Administrator implements a new subject onto system.

Preconditions: Administrator is only allowed to add new subject onto system.

Trigger: Administrator needs to access to the system to add new subject

implemented by DepEd going implement to the system.

Scenario: 1. Administrator logs onto the System.

2. Administrator enters the Login ID and Password.

3. Verify the administrator account.


5. If administrator enters (5) five times attempt incorrect the

account has been locked out on 24hr’s.


7. Administrator time and date logged.

8. Administrator Access to add and edit.

9. Administrator updates the subject list.

10.Administrator add new subject to the system.

11.Administrator enter subject name.

12.System will displayed message prompt.

13.When have same subject name, re-enter again.

14.Administrator set a subject description <100character.

15.When >100character subject description the system will

display prompt message that “the description is too long.”

16.Administrator click save button to implement.

17.New subject display and stored in system.

18.System, record the time and date subject implemented.

19.Successfully implemented new subject.

20.Administrator time and date log out.

Exceptions: Other users cannot access to implement except administrator.



Use-case: Set a calendar activities


Goal in context: The Administrator/Registrar set events on the calendar of activities.

Preconditions: The Administrator/Registrar is the only allowed setting the upcoming

events and activities for the students.

Trigger: The Administrator/Registrar needs to access to the system set the

upcoming events and activities for the students.

Scenario:

1. Logs onto the System.

2. Administrator/Registrar enters the Login ID and Password


4. Select Calendar date to view.

5. Shows categories, View required number of days, view make-

up classes, view suspension of class.

6. System will determine user authorization.

7. Student has limited to access to be print.

8. Administrator and Registrar are allowed to view the

information with categories

9. Administrator and Registrar will set the events or activities in a

specific date.

10. Save changes made by the Admin/Registrar.

11. Post and display.

12. Admin/Registrar successfully set events or activities on

calendar of activities.

Exceptions: Students are not allowed to set upcoming events on the calendar of

activities.



Use-case: Subject teacher assign


Goal in context: The Administrator/Registrar set Subject Teacher Assign.

Preconditions: Administrator/Registrar is only allowed to assign the subject teacher.

Trigger: Administrator/Registrar needs to access to the system to assign the

subject teacher.

Scenario: 1. Administrator/Registrar logs onto the System.

2. Administrator/Registrar enters the Login ID and Password.


4. Select teacher’s information and achievements.

5. Select another teacher if teacher is not qualified for the subject.

6. The selected teacher is suitable for the subject

7. Waiting for the date of seminar about the subject to be taught.

8. Teacher attended the seminar.

9. Administrator/Registrar successfully assigns the subject

teacher.

Exceptions: Other users cannot access to implement except

Administrator/Registrar.



Use-case: View/Print


Goal in context: The Administrator/Registrar prints those student requests.

Preconditions: The Administrator/Registrar allowed printing those reports, reminders,

scheduled, event calendar activities and curricular activities.

Trigger: The Administrator/Registrar needs to access to the system to print

those student request.

Scenario:

1. Administrator/Registrar logs onto the System.





6. Select categories information of student request to be print.

7. View the reports, reminders, subjects, curricular activities,

calendar event activities and their scheduled.

8. User does want to print the choosing information.



11. Administrator and Registrar are allowed to print those student

requests.

12. Administrator and Registrar view the student request to be

print.

13. Prompt to be print and not to print.

14. Enter the number to be print.

15. Student request has been successfully print.

Exceptions: Students are not allowed to print that report.



Use-case: View Set Calendar


Goal in context: The Administrator/Registrar prints those student requests.

Preconditions: The Administrator/Registrar allowed printing those reports, reminders,

scheduled, event calendar activities and curricular activities.

Trigger: The Administrator/Registrar needs to access to the system to print

those student request.

Scenario:

1. Administrator/Registrar logs onto the System.





6. Select categories information of student request to be print.

7. View the reports, reminders, subjects, curricular activities,

calendar event activities and their scheduled.

8. User does want to print the choosing information.



11. Administrator and Registrar are allowed to print those student

requests.

12. Administrator and Registrar view the student request to be

print.

13. Prompt to be print and not to print.

14. Enter the number to be print.

15. Student request has been successfully print.

Exceptions: Students are not allowed to print those reports.



Use-case: New / Setting User


Goal in context: To create new user and their user setting

Preconditions: The administrator has valid user name and password.

Trigger: Create new user and to set a user setting.

Scenario:

1. The Administrator logs onto the System.

2. The Administrator clicks the system set-up User

setting button and edits setting or add new user.

3. The administrator create new user.

4. The administrator encodes the set user information.

5. Set the setting access to the system.

6. Tha administrator saves the changes.

7. The Administrator Edit the setting user.

8. The Administrator view the setting information.

9. The Administrator set changes in user setting.

10.The administrator saves the changes.

11.The administrator has been done in task.

Exceptions: If the user does not log in as an administrator.



Use-case: Searching

Primary actor: User's

Goal in context: To be accelerate the search information.

Preconditions: All users are allowed to use search bar to be search.

Trigger: User needs to access or use the search bar on system.

Scenario:

1. The Users logs onto System.

2. The Users selects user designation.

3. The Users enters the Login ID and Password.


5. The Users click the search bar.

6. The Users enter to be search in search bar.

7. Press enter or click magnifying glass to be search.

8. System Data search loading.

9. System found show on screen.

10. The Users logged out.

Exceptions:



Use-case: Display Notification messenger


Goal in context: To Logged out in system.

Preconditions: The Admin are allowed to log out.

When users idle more 15 minute the account auto logged out.

Trigger: User needs to log out to the system.

Scenario:

1. Admin logs onto System.

2. Admin selects user designation.

3. Admin enters the Login ID and Password.


5. Admin click the pop-up notification.

6. Admin view the message from DepEd.

7. Notification message is ready printable for approval.

8. System Data save time/date prints.

9. The Users logged out.

Exceptions:



Use-case: Log out onto system

Primary actor: Users

Goal in context: To Logged out in system.

Preconditions: The users are allowed to log out.

When users idle more 15 minute the account auto logged out.

Trigger: User needs to log out to the system.

Scenario:

1. The Users onto System.

2. If the Users idle more 15 minute the account auto logged out.

3. The Users idle less 15 minute are still in system.

4. The Users click the main menu.

5. The Users choose to click Sign out.

6. System message prompt "are you sure to sign out"

7. System message prompt " continue, cancel"

8. The Users has been Logged out.

Exceptions:



3.1.2.3 Special usage considerations

3.1.2.4 Activity diagrams

The following activity diagrams show the actions that occur during a particular use-case.

Figure 1 shows the steps taken as a student to log on to the web server system. Access

granted if account has correctly entered given by administrator to student when the

combination is entered within the first three attempts their must will be locked out and an

administrator will need to issue a massage warning or notification to student.

Figure 1 – Activity diagram for Student logging on the system.



In figure (2) two, show the steps taken as a administrator to log on to the computer

system. An admin has capable main person can access the whole system. The

administrator will first check the security to maintain the good transaction of a system.

Figure 2 – Activity diagram for Admin logging on the system.



In figure (3) three, show the steps how to implement a subject in system by an

administrator to log on to the computer system.

Figure 3 – Activity diagram for Implementing Subject on the system.



In Figure 4 (four), shows the activity of updating account and viewing as in the diagram

all users will be able to view their account information or report’s displayed but only

administrators is capable allowed to edit for updating all account while registrar only

allowed to all student account information.

Figure 4 – Activity diagram for Updating Account on the system.



In Figure 5 (Five) show all user can access to view a report that displayed by

administrator. Administrator and staff the only allowed to printing some report as need to

print just inform or noted them.

Figure 5 – Activity diagram for View with Print on the system.



In figure (6) six, steps to show the set subject per grade level to the computer system.

Figure 6 – Activity diagram for Grade level/set subject to the system.



In figure (7) seven, show the steps to set a teacher Assign to per subject on the system.

Figure 7 – Activity diagram for Teacher assign to the system.



In figure (8) eight, show the steps how to view the calendar of activities and how to

create new description per date calendar on the system.

Figure 8 – Activity diagram for View Set Calendar to the system.



In figure (9) nine, show the steps how to change the setting user and how to create new

user on the system.

Figure 9 – Activity diagram for New Set User to the system.



In figure (10) ten, show the steps to view the Notification massager on the system.

Figure 10 – Activity diagram for Notification messenger to the system.



In figure (11) eleven, show the steps taken as User to be search in computer system.

Figure 11 – Activity diagram for searching to the system.



In figure (12) twelve, show the steps to view the setting of sections on the system.



Figure 12 – Activity diagram for sectioning to the system.

In figure (13) thirteen, show the steps taken as user to log out to the computer system.

Figure 12 – Activity diagram for log out to the system.



3.1.3 Data Model Description

3.1.3.1 Data Object

Subject Data Object

Subject ID, An identifier assigned to the subject.

Name, The subject name.

Date Implement, The subject implemented date.

Description, A description of the subject.

Student Data Object

Student ID, A code number assigned to the student.

Password, An account password of a student.

Name, The Student full name.

Address, The Address of the student.

Phone, The guardian and student phone number.

Email, The email address of a student.

Classification, The job description of the student are limited can viewing and updating his/her

old and current info.

Grade level subject Data

Grade level ID, A code identifier assigned to the grade level subeject.

Set subject, The subject list that set per grade level.

Description, The set schedule list of subject.



Administrator Data Object

Admin ID, The account name of the Administrator.

Password, The account password of the Administrator.

Description, Has the authorization in all transactions of system.

Registrar Data Object

Username, The account ID name of the registrar.

Password, The account password of the registrar.

Description, The assistant of administrator in system.

Change Data Object

Change Data ID, The number of the changing record onto system.

Time, The time of chance.

Date, The date of chance.

Description, The Data record chance.

User Data Object

Access level, The role of the user to be access the system.

Name, The name of the User.

Password, The password to secure the un-authorized alternation.

Schedule Data Object

Day, Pertaining to the daily assigned day schedule.

Time, Pertaining to the indicated to the daily schedule time.

Room, Pertaining to the room indicated where the schedule shall be taken.



Reminder Data Object

ReminderID , A unique identifier for the reminder

StudentID, The ID numbers of a student give an reminder.

Date, The date of the reminder we’ve post

Time, The exact time of the reminder we’ve post

Message, The reminder message to be displayed

Login/Logout history Data Object

Login ID, A unique number of log history.

Logged Date, Date of logged.

Logged Time, Exact time of logged.

Logged Out, Exact time and date to be logged out to the system.



3.1.3.2 Relationships

In order for a student to access the system, the students must go first to the administrator to

create their account. Since admin is the only one that capable of creating new account for

many students, one-to-many relationship exists.

Registrar manages the information of every student so one-to-many relationship exists. At

the same time, the registrar makes schedule of every section so one-to-many relationship

exists.

Every students has many schedules so one-to-many relationship exists. These schedules are

not just the everyday subjects that they are taking but the curricular activities and events are

also included on the schedules.

Administrator is the only one that capable of implementing new curriculum so one-to-one

relationship exists. Only one curriculum is followed by every school and it is given by the

memorandum of Dep-Ed.

Administrator has also a power to tamper the schedule made by the registrar for the students

so one-to-many relationship exists. Administrator has also capable of making the schedule of

every student that’s why this relationship exists.

Reminder depends on the upcoming events of every student. Every student will receive a

reminder if there are events or activity is near on the date. So zero-to-one relationship exists.



3.1.3.3 Complete data model

The relationships between the data objects describe in 3.1.3.2 Relationships are shown in this

figure (13) thirteen.



Figure 13 – Relationship diagram for the Curriculum Management System.

3.1.4.1 Class Diagram

The association between the diffent classes are shown in figure 14. The access functions to

get and set private data attributes.

Figure 14 – Curriculum Management System Class Diagram.



3.1.4.2 Data Dictionary of class diagrams

Data Dictionary of Student

Field Length Type Description

Username 12 Varchar Unique username of the student that

can be a combination of letters and

numbers only.

Password 15 Varchar Password of the user with variable

length that may consist of letters and

numbers.

Field Type Description

STUD_ID Int Unique ID of the student

STUD_ FNAME Text Given name of the student

STUD_ LNAME Text Family name of student

STUD_MINITIAL Text Mother’s surname of the student

STUD_GENDER Text Student sex

STUD_AGE Int How old is the student

STUD_ADDRESS Varchar Location where student currently lives

STUD_CONTACTNO Int Contact no. of the student

STUD_EMAIL Varchar Student email address

STUD_DOB Date/Time Date of birth of student

STUD_POB Text Birth place of the student

STUD_PHOTO Image 1x1 photo of student

STUD_STATUS Text The Student state

STUD_RELIGION Text Religion of the student



Data Dictionary of Administrator


Username 12 Varchar Unique username of the Administrator

that can be a combination of letters and

numbers only.



numbers.


ADMIN_ID Int Unique ID of the Administrator

ADMIN_FNAME Text Given name of the Administrator

ADMIN_LNAME Text Family name of Administrator

ADMIN_MINITIAL Text Mother’s surname of the Administrator

ADMIN_GENDER Text The Administrator sex

ADMIN_AGE Int How old is the Administrator

ADMIN_ADDRESS Varchar Location where Administrator

currently lives

ADMIN_CONTACTNO Int Contact no. of the Administrator

ADMIN_DOB Date/Time Date of birth of Administrator

ADMIN_POB Text Birth place of the Administrator

ADMIN_PHOTO Image 1x1 photo of Administrator

ADMIN_STATUS Text The Administrator state

ADMIN_RELIGION Text Religion of the Administrator



Data Dictionary of Registrar


Username 12 Varchar Unique username of the Registrar that

can be a combination of letters and

numbers only.



numbers.


REG_ID Int Unique ID of the Registrar

REG_FNAME Text Given name of the Registrar

REG_LNAME Text Family name of Registrar

REG_MINITIAL Text Mother’s surname of the Registrar

REG_GENDER Text The Registrar sex

REG_AGE Int How old is the Registrar

REG_ADDRESS Varchar Location where Registrar currently

lives

REG_CONTACTNO Int Contact no. of the Registrar

REG_DOB Date/Time Date of birth of Registrar

REG_POB Text Birth place of the Registrar

REG_PHOTO Image 1x1 photo of Registrar

REG_STATUS Text The Registrar state

REG_RELIGION Text Religion of the Registrar



Data Dictionary of ScheduledField Type Description

SCHED_CURRACTIVITIES Varchar Set schedule for curricular activities

SCHED_CALENDAR Varchar Event schedule in calendar

SCHED_GRADELEVEL Int Unique ID of Grade Level

SCHED_SECTION Int Unique ID for sectioning

SCHED_ROOM Text Unique number for room name

SCHED_DAY Date The exact day of schedule

SCHED_TIME Time The exact time of schedule

SCHED_SUBJECT Date/Time The set subject of schedule

SCHED_TEACHER Date/Time The teacher schedule assigned

Data Dictionary of Implement CurricularField Type Description

IMPLE_SETSUBJECT Int Unique ID for set subject

IMPLE _SUBNAME Text The subject name

IMPLE _DATEIMPLE Date Exact date implemented subject

IMPLE _TIMEIMPLE Time Exact Time implemented subject

IMPLE _SUBDES Text The subject description

Data Dictionary of ReminderField Type Description

REM_CURRENTDATE Varchar Current Reminder message

REM _RECENTDATE Varchar Recent Reminder message

REM _DATE/TIME Date/Time Exact Date and Time reminders

REM _MESSAGE Text The create reminder messages

3.1.4.2 Software interface Description



A computer language whereby computer programs can communicate with each

other and one language can call upon another for assistance.

3.1.4.2.1 External machine interfaces

The software will be capable to print those scheduled, curricular activities, Event

calendar activities, student information and reports.

3.1.4.2.2 External system interfaces

The researcher will design and develop an automated system which is LAN based at the

same time, WEB based with all students to update easily will communicate with Web server

on the internet through a high speed network connection WEB based is designed for those

clients who are busy and doesn’t have time to go to school? By using an automated system, it

can lessen the exertion of effort at the same time; the process will be fast while LAN based is

designed for the walk-in clients who decided to go at school for their question and other

personal issues.

3.1.4.2.3 Human interface

The actual system will only navigate by keyboard alone, in addition to use mouse and

keyboard combination.

3.1.4.3 Reports



3.1.4.3.1 Inventory of reports

Curricular Implemented reports

-Memorandum of DepEd

-K12 program

-New subject

Calendar activities reports

-Required days of classes

-Make-up class

-Suspension of classes

-Holiday

-Extracurricular activities

-School Event calendar

Information date/time changes reports

Login/Logout history reports

3.1.4.3.2 Layout of Reports

3.1.4.3.3 Data Dictionary of reports.

3.1.5 Behavioral Moral Description



3.1.5.1 Description for software behavior

3.1.5.1.1 Events

Admin Class Events

Admin logs on to system

Admin updates school year

Admin logs off the system

Registrar Class Events

Registrar logs onto system

Registrar keeps and maintains records

Students Class Events

Student logs onto system

Student view his/her information

Schedule Class Events

Admin updates schedules

Registrar posts schedules

Student view schedules



Classroom/Sectioning Class Events

Student added to section

Student removed from section

Student added to new section

Subject Implement Class Events

Admin Adds new Subject

Admin posts implemented Subject

Edit/Update Class Events

View File List

Choose file to be change

Edit selected file

Information Changed

3.1.5.1.1 States



Administrator State Description

Memorandum of DepEd

Onto system The administrator has been log into system.

Access The administrators have access to update school year.

Log-in/out History the history of user log-in/log-out onto system

User setting The administrator have access of setting of users.

Create account The administrator one capable to create user.

Subject The administrators have access of setting of subject.

Curricular activity The administrator have access of setting of curricular activity.

Calendar activity Administrator set a schedule of upcoming events of the school.

Teacher assign Principal chosen person who is teaching every subjects of a student.

Reports The administrator has access to post and distribute those reports.

Book Required References that is suitable per grade level set subjects

Maintenance The administrator must do to maintain the security.

Registrar State Description

Onto system The Registrar has been log into system.

Waiting The Registrar has been waiting to be want to access.

Student info The Registrar have access to update all student info.

Subject info The Registrar maintained the good description of each subject.

Curricular activity The Registrar have access of setting of curricular activity.



Schedule The Registrar has to set a student schedule.

Book required The Registrar have access to give a reminder to all student.

Report The Registrar has access to post and distribute those reports.

Event The Registrar must do to set Event at calendar.

Student State Description

Onto system The Student has been log into system.

Waiting The Student has been waiting to be want to access.

Reminder The message is being displayed for the student to acknowledge.

Report Request The student has to set a message for report request.

Curricular activity The student view the Curricular activity to be updated.

Event The student must do to view the Event at calendar.

Student schedule The set schedule for a student.

Subject View the description of subject to be acknowledge.

Student info. The Student data.

Print The report suggest to administrator and registrar to be print.

Calendar State Description



Onto system The user has been log into system.

Access The administrators have access to update school year.

Setting The setting of calendar selected categories of calendar activities per date.

Extracurricular Administrator set the upcoming curricular activities for the students.

Required class The recommended number of days of the school.

Make-up class Set a arranged class to cope up the previous past classes.

Suspension classes The postponement of the classes due to specific reasons and events.

Event The principal create an additional activities for curricular managing

Holiday The day set aside by custom or by law in which normal activities.

Waiting The administrator select want to change.

Changes Set a changes.

Save Save the changes

Post/display Post to the system what changes is, to update all user.

Subject implemented onto System State Description

Encode Subject To input new subject implemented

Subject Description Description of the new subject implemented.

Description Length is too long Exceed to the assigned maximum characters > 100 character.

New Subject has been implemented The subject successful implemented and post onto system.

Edit/Update Class States Description



Select file User will choose what file he/she wants to change.

Edit Selected File User will now edit the file he/she has chosen

Save Save changes made by the user.

Time/date Change this will track the exact date and time when the

changes made.

Success data store The information that administrator changes has been

success.

Current Information changes Shows the current changes made by authorize user.

Classroom States Description

Under Capacity Less Than 25 students are enrolled in the classroom.

Waiting list Waiting to become 25 student in one classroom

New Section/Room If the classroom has greater than 25 students.

Verify Section/Room If the classroom has exact number of students.

3.1.5.1 Statechart Diagram



A statechart diagram for the entire system is shown in figure 13.

Figure 13 – Overall System State Chart Diagram

Administrator Class State chart Diagram.



Registrar Class State chart Diagram.

Student Class State chart Diagram.



Calendar Activity State Chart Diagram.

Subject Implement onto system Class State Chart Diagram.



Edit/Update Class State Chart Diagram.

Classroom/Sectioning Class State Chart Diagram.



1.1.6 Restriction, Limitation and constraints.



This are those can’t tackled or our knowledge limitation at system we’ve made.

• Can’t change the name of those past year curriculums subject taken with an alumni

graduate if already taken or change it in present if want to retrieve some data, just fix.

• We didn’t allow changing the other related module that entering or connecting in our

system.

1.1.7 Validation Criteria

Software validation will ensure that the system responds according to the users

expectations; therefore it is important that the end users be involved in some phases of

the test procedure. All test will be traced back to the requirements in section 3.1.1.2.

1.1.7.1 Classes of test

Unit testing will be conducted on all of software subsystems including.

1. Logging on to the system

2. Viewing and editing Information

3. Viewing Curricular Activity

4. Viewing Event Calendar

5. Viewing and setting Student schedule

6. Implemented curriculum

7. Viewing and posting with printing of report

8. Notification messenger from DepEd

Acceptance testing will be conducted at the Lan and Web server.

1.1.7.2 Expected software response



The software should display an suitable error message when a value outside the

accepted limits is entered.

The software should not be capable of deleting an implemented subject inside and

those account information at system we’ve made.

1.1.7.3 Performance bounds

The system will provide good and accurate performance for the accelerate transaction to the process of implement curricular and schedule managing.

The system will provide access to the database system in immediate response.


Date post:	08-Feb-2016
Category:	Documents
Upload:	jeric-delrosario-ue
View:	43 times
Download:	0 times

Curriculum Manage System Chapter i i i

Documents