Professional Documents
Culture Documents
Aclc Online Enrollment System Srs Pre or
Aclc Online Enrollment System Srs Pre or
1 Introduction
Almost everything can be done with technology. Technology for the users
provide good consolation and comfort in everyday life. The technology today plays an
important role in our society because it lessen error of work by using machines. It makes
work easier and faster and reduces cost to an organization from paper work up to
automated working system. Many manual transactions can be computerized by using
software applications or computer system to make work easier. Nowadays, computer
based system is commonly used by every company and institution and one of these is
an Online Enrollment System. Online Enrollment System serves as a vital part of a
school for easy and convenient way of enrolling a student.
I.1. PURPOSE
I.2. SCOPE
This software system will be an Online Enrollment System for ACLC College of
Mabalacat. This system will be designed to maximize the deficiency and ineffective in
performing job on daily basis in terms of enrolment, grading, payment and record
keeping process, which would otherwise have to be performed manually. By maximizing
the school official’s work efficiency and meet their needs in the system in terms of
usage.
Computerization has its benefits, it may also have disadvantage. The proposed
system is not capable of transactions that involves online payment such as enrollment
fees, uniform fees and contributions.
School Officials. The system will help the school administrators assigned in
different offices by inputting and viewing data records of students in efficient and
convenient ways. It will also help by giving them accurate and on time information for
decision making purposes.
Faculty. The system will help the school faculty in managing the grades easily
by viewing and inputting student’s grades online.
Students. The students will benefit the Online Enrollment System to make
request fast and reliable and eliminate complaints regarding on delayed and inaccurate
system used. It will also serve as a medium to educate the students at ACLC College of
Mabalacat with use of new technology.
Term Definition
Authentication It is a process of verification involving username and
password needed to grant certain access level in the
website. It is a process of confirming if a user is an
existing and registered user in the system.
Authorization It is the process of determining which privileges a user
can have in the website. Permission is granted to
registered users to view certain features in the system
and able to edit his or her account.
Enrollment It simply refers to the body of people (such as student
in ACLC College of Mabalacat) who register or enrol at
the same time.
Online It simply refers to an uploaded website.
Online Enrollment System It simply refers to the system developed by the
researcher to be deployed online used for ACLC
College of Mabalacat.
System A set of detailed method, procedures and routines
created to carry out a specific activity perform a duty or
solve a problem.
1. Gary B. Shelly and Harry J. Rosenblatt (2012). Systems Analysis and Design 9 th
Edition, Cengage Learning Pte. Ltd. First Philippine reprint.
2. Jeffrey A. Hopper, Mary B. Prescoll and Heikko Topi (2010). Modern Database
Management. Peason Education Sout Asia Pte. Ltd. (Philippine Representation
Office).
3. Kathy Schwalbe (2010). Management of Information Systems Technology
Projects. Cengage Learning Pte. Ltd. First Philippine reprint.
4. McGraw-Hill Irwin (2012). Business Driven Information Systems. McGraw-Hill
Companies, Inc., New York, NY, 10020.
5. Roger S. Pressman (2010). Software Engineering 7 th Edition. McGraw-Hill
Companies, Inc., New York, NY, 10020.
2 Overall Description
This section will give an overview of the whole system. The system will be
explained in its context to show how the system interacts with other systems and
introduce the basic functionality of it. It will also describe what type of stakeholders that
will use the system and what functionality is available for each type. At last, the
constraints and assumptions for the system will be presented.
2.1. PERSPECTIVE
This system will show the enrollment, payment, grading and record keeping
process of ACLC College of Mabalacat. Context Diagram is provided to illustrate how
the entities interact with each other. (See Appendix E for the Context Diagram)
2.2. FUNCTIONALITY
DFD is designed based on the needs of the clients; each process would
represent entity that actually performs the transaction of business based on the given
scenario found during interviews and data gathering. The data flow diagram is part of the
data analysis which encompasses different process involved in the system, the
proponent have made it clear for the readers to understand better the processes
involved through the data flow diagram. (See Appendix F for the Data Flow Diagram)
There are four types of users that interact with the system: Administrator, school
officials (registrar, dean, accounting and admission), faculty members and students.
Each of these four types of users has different use, so each of them has their own
requirements.
The administrator only interact with the web portal and manage school official’s
account for security purpose. The administrator manage the overall system so there is
no incorrect information within it.
Next, the school officials: registrar is the one who manage the grades of students
such as copy of grades, transcript of records, terminal reports, trimester report,
enrollment report; dean is the one who manage the schedule of the curriculum offered,
manage faculty schedule, enrollment report and student copy of grades; accounting is
the one who manage different types of payment and admission is the one who manage
the admitted new student with their admission requirements.
And finally, the faculty members who interact with the grading system and the
students serve as client that can view their personal account in terms of grades, history
of payments and enrollment registration.
In order to use the proposed system to be developed at the client side, the
following system requirement:
Specification Description
Web Browser Microsoft Internet Explorer v11.0 or, higher
Mozilla Fire-Fox v12.0 or, higher
Google Chrome v27.0.1453.116m or, higher.
Internet Connection 3 Mbps
In order for the proposed system to be developed and implemented the following
hardware specifications are needed:
The following are used to develop the Online Enrolment System for ACLC College of
Mabalacat campus:
Since, the proposed Online Enrollment System for ACLC College of Mabalacat to
be developed, therefore following are the limitations:
o The system cannot perform an online payment;
o The system cannot perform an automated scheduling;
o The Internet connection is also a constraint for the application. Since the
application fetches data from the database over the Internet, it is crucial that
there is an Internet connection for the application to function.
One assumption about the product is that it will always be used on Personal
Computers, Laptop and even mobile phones that have enough performance. If these
devices does not have enough hardware resources available for the application, there
may be scenarios where the application does not work as intended.
3 Specific Requirements
This section contains all of the functional and quality requirements of the system.
It gives a detailed description of the system and all its features.
This section provides a detailed description of all inputs into and outputs from the
system. It also gives a description of the hardware, software and communication
interfaces and provides basic prototypes of the user interface.
This part of the study will present the features of each modules of the system,
which were identified based from the requirements of the users.
The school website provides the corporate information of the school. Specifically it
contains Home Page and Login Page.
Administrator Portal
Registrar Portal
Dean’s Portal
Admission Portal
Accounting Portal
Faculty Portal
Student Portal
This part of the study will present the features of each modules of the system,
which were identified based from the requirements of the users.
Email
verification
Login
<<extend>>
Change
Password
<<include>>
Account Management
for Registrar, Dean,
Change or
Edit Profile
ADMINISTRATOR Accounting, Admission
and Faculty
Enlistment
Report
Brief Description
The Administrator accesses the Online Enrollment System Website, can manage users
in the system and can access for different types reports from entities.
Before this use case can be initiated, the Administrator has already accessed the Online
Enrollment System Website.
Schedule
Login
Change
Password
<<include>>
Class List
Change or FACULTY
Edit Profile
Grade Book
Brief Description
The Faculty accesses the Online Enrollment System Website, can manage class list and
grade book for grading system.
Before this use case can be initiated, the Faculty has already accessed the Online
Enrollment System Website.
Admission
Login
Change
Password
<<include>>
Change or
Edit Profile
ADMISSION
Reports
Brief Description
The Admission accesses the Online Enrollment System Website, can manage admitted
students per semester, course and year.
Before this use case can be initiated, the Admission has already accessed the Online
Enrollment System Website.
Change Faculty
Password Schedule
<<include>>
Change or
Edit Profile
DEAN
Student
Schedule
Grades
Brief Description
The Admission accesses the Online Enrollment System Website, can manage admitted
students per semester, course and year.
Before this use case can be initiated, the Admission has already accessed the Online
Enrollment System Website.
Change Student
Password Records
<<include>>
Change or
Edit Profile
REGISTRAR Student
Grades
Brief Description
The Registrar accesses the Online Enrollment System Website, can manage students
grades.
Before this use case can be initiated, the Registrar has already accessed the Online
Enrollment System Website.
Fee Settings
Login
Change
Password Payments
<<include>>
Change or
Edit Profile
ACCOUNTING
Receipt
Brief Description
The Accounting accesses the Online Enrollment System Website, can manage students
payments.
Before this use case can be initiated, the Registrar has already accessed the Online
Enrollment System Website.
Schedule
Login
Change Curriculum/
Password Grades
<<include>>
Change or
Edit Profile
STUDENT Financial
Account
Clearance
Registration
Brief Description
The Student accesses the Online Enrollment System Website, can view grades,
financial account, schedule, registration.
Before this use case can be initiated, the Student has already accessed the Online
Enrollment System Website.
The school website provides the corporate information of the school. Specifically it
contains the following:
Home Page. A home page which will serve as the welcome page of the school
website and provides links to all other pages of the system.
Login page. This will be used to log in the portal and modules of the users of the
system (administrator, registrar, dean, accounting, admission, student and
instructor).
Administrator Portal
Dashboard. The dashboard will serve as the home page of the school director. It
contains a welcome message and task of the portal.
Accounts Management. This page will let the administrator add the users such
as registrar, dean, accounting, admission and faculty depending on assigned
privileges.
Enlistment Report. This page will show Enlistment report from assigned
branches after enrolment. It will display the number of students in different
programs.
Registrar Portal
Dashboard. The dashboard will serve as the home page of the registrar. It
contains a welcome message and task of the portal.
Academic Settings. The academic settings will be used for adding a new school
year, courses, curriculum, subjects, year level and semester/trimester.
Student Records. This page will display the enrolled students. The student
profile, curriculum and grades will be viewed here.
Dean’s Portal
Dashboard. The dashboard will serve as the home page of the dean. It contains
a welcome message and task of the portal.
Faculty. This part will allow the Dean to view the profile of his/her faculties and
view if the instructor is active or not for the semester.
Students. This part will display the enrolled students. The student profile,
curriculum and grades will be viewed here. Same with the registrar but the Dean
is for viewing purposes only.
Grades. This will display grades of students per year level, course, subject and
section.
Admission Portal
Dashboard. The dashboard will serve as the home page of the admission
officer. It contains a welcome message and task of the portal.
Admission. This part will let the admission officer register a student applicant,
view existing applicants, and update the requirements submitted by the student.
It will have a search feature to view student applicant records easily.
Reports. The reports to be generated in the admission portal will be the Admitted
students, Probationary Status, Pending Students Disapproved Students Number
of student applicants per courses
Accounting Portal
Dashboard. The dashboard will serve as the home page of the accounting
officer. It contains a welcome message and task of the portal.
Fee Setup. This page allows the accounting officer set the tuition fees every
semester and trimester.
Reports. Reports that will be printed here will be the receipt for payments,
temporary permit, exam permit, registration form and summary of payments.
Faculty Portal
Dashboard. The dashboard will serve as the home page of the instructor. It
contains a welcome message and task of the portal.
Schedule. This will display schedule of the teacher for the current semester.
Classes and Grade Book. This will display the teaching loads of the teacher for
the current semester and encode the grade of the students every term.
Student Portal
Dashboard. The dashboard will serve as the home page of the student. It will
contain a welcome message, the picture of the student and a brief description as
to what the portal can do.
Schedule. This portion will display the schedule of the student for the current
semester once officially enrolled.
Curriculum This portion will display the curriculum of the student within the four-
years of his/her degree. This will serve as the student’s guide throughout the four
years as to what subjects he/she needs to complete and enrol. The student can
view his/her grades here also.
Financial Account. The accounts will display pending balance and payment
history of the student.
Clearance. Clearance will be another basis for the registrar office if the student
grades can be viewed on his/her account.
Grades. This will display the grades of the students for the semester provided
that the student has been cleared to all departments.
This subsection specifies both the static and the dynamic numerical requirements
placed on the software or, on human interaction with the software, as a whole. Static
numerical requirements may include:
A use case is a tactic used in system analysis to identify, clarify, and categorize
system requirements. The use case is made up of a set of possible sequences of
interactions between systems and users within an environment and related to a
particular goal. The use case should contain all system activities that have significance
to the users within a given system.
The proponent uses the User Case Diagram during the analysis phase of the
project to identify system functionality. They separate the system into actors and use
cases. Actors represent roles that are played by users of the system. (See Appendix G
for the Use Case Diagram)
The software is to be designed in ASP.NET MVC 5, both the front End, i.e. the
forms and the back End, the database, so that performance level is not affected
while trying to connect front end and back end together as it would be in 2
different software.
The software must be designed in a way such that response time is minimal and
the software reacts quickly to its environment.
Safety is another key factor in the design and development of the system.
The product must be safe to use without resulting in any injury of any kind to the
user.
The software must provide safety measures so as to recover any data loss.
Loss of data of any kind should not result in the use of the software.
The software must meet the safety requirements specified in the IEEE standards.
Software must provide means for verification and authorization of users, for e.g
use of IDs and passwords.
4.3.1. Functionality. Is the essential purpose of any product or service? It has the
following sub-characteristics:
4.3.2. Reliability. A set of attributes that bear on the capability of software to maintain
its level of performance under stated conditions for a stated period of time.
Fault tolerance - The ability of software to withstand (and recover) from
component, or environmental, failure.
Maturity - This sub-characteristic concerns frequency of failure of the
software.
Recoverability - Ability to bring back a failed system to full operation,
including data and network connections.
4.3.3. Usability. A set of attributes that bear on the effort needed for use, and on the
individual assessment of such use, by a stated or implied set of users.
Learnability - Learning effort for different users, i.e. novice, expert, casual
etc.
Understandability - Determines the ease of which the systems functions
can be understood, relates to user mental models in Human Computer
Interaction methods.
Operability - Ability of the software to be easily operated by a given user
in a given environment.
4.3.4. Efficiency. A set of attributes that bear on the relationship between the level of
performance of the software and the amount of resources used, under stated
conditions.
Resource behaviour - Characterizes resources used, i.e. memory, cpu,
disk and network usage.
Time behaviour - Characterizes response times for a given thru put, i.e.
transaction rate.
4.3.5. Maintainability. A set of attributes that bear on the effort needed to make
specified modifications.
Changeability - Characterizes the amount of effort to change a system.
Testability - Characterizes the effort needed to verify (test) a system
change.
Analyzability - Characterizes the ability to identify the root cause of a
failure within the software.
Stability - Characterizes the sensitivity to change of a given system that is
the negative impact that may be caused by system changes.