EXAMPLE OF REQUIREMENT MODELING

IPO (Input-Process-Output) Diagram this must be placed in your appendices

Input

Basically, the system requires the student’s personal information, a digital image of the
instructor’s modular instructions, students’ ratings and their corresponding user accounts. This inputs
are taken into consideration that the purpose and scope of the proposed system is focused on user
management, virtual classroom management, and record transcription.
Process

The process of managing user accounts comprises the registration of student and faculty. The
system should be able to register all faculties and students in order to participate in virtual classroom
sessions.

The virtual classroom management enables the faculty to systematically upload his/her lessons
and give home works and classroom activities. This is also a venue for students to take their quizzes and
term examinations via online. The faculty will no longer have to do traditional checking since the system
is designed to evaluate and give the student’s ratings.

The record transcription, however, is a process where student’s progress and ratings in the class
are consolidated. This process enables the school to automatically determine the student’s standings in
their class whether he/she is a dean’s list or an honor student. It also aids the enrolment committees in
advising and admitting students’ during enrolment.

Backing up the system is the process of creating a duplicate of records and transactions done in
a day. It is important to understand that the loss of data is inevitable event that may happen in an
organization. The system backup is capable of creating a shadow of upto 500MB of data. This process
replaces the backed up database with a new one and is expected to increase in size by 2-3% of the
backup file daily.

Output

With the key processes involved, the system is expected to generate a list of students’ user
accounts, database backup reports and statistics, students’ individual report ratings including their
transcript of records. All reports are not valid without the approval of the school administrators and/or
university dry seal.

The system won’t be able to generate the faculties’ user accounts due to security reasons. But
the system may generate a statistical transaction logs about user activities (which includes student
activity as well).

Control

It is important that system users are the players of the system. Each player have their different
role and access in the system. Every faculty members are responsible for collecting students’
information as well as the HRMO for consolidating faculty personal information to administrator, where
the administrator registers these information into the system.

All digital modular instructions and students’ ratings are being managed by the faculty member.
These inputs are essential to the virtual classroom management process.

The students’ record transcription process is being managed no other than the registrar. They
are given the authority to generate and release student’s individual report ratings and transcript of
records. These specific reports are the result of virtual classroom management and record transcription
management.
 In addition, the administrator is the only use who could perform system backup and generate a
list of students’ user accounts and database backup reports and statistics. He is responsible for
maintaining the system and sees to it that the system is running in good condition.

Performance

System performance could only be attained if there is a higher security level, provision on
speeding up transactions, and risk management.

Equipping faculty members with a unique user name, a strong 15-alphanumeric character
password, and a personalized token promotes a higher security level within the institution. It is
important that the faculty must remember his/her account and carry his/her token during school days in
order for him to access the virtual classroom management. The token as described is a personalized USB
flashdrive that enables him to used it as a key to access the system.

To speed up any transaction process, it is important that the system should be maintained
weekly every weekends. This is the only time that the system is operating with a very minimum number
of users and data traffic is not a problem. Faculty members are limited in uploading a 10MB PDF files
format of their modular instruction per upload session. This will enable the system to efficiently manage
file transmission to the server and ease the access of other operations within the system. It is also
recommended that generating the transcript of records (TOR) are to be done by batch due to
voluminous data that are being transmitted from server to client. It is best if the generation of the
report is limited to up to 50 files per batch. However, the student after requesting for his/her TOR is
expected to be released after 3-4 working days.

Backing up the system is scheduled daily every 5:00 in the afternoon where system users are
less likely accessing the system. This is the only perfect time to perform the backup operation in order
not to obstruct or slowdown the transactions during work hours. The system backup plays an important
role in the system as this addresses the risk of losing data in our database system. The System
Administrator should be aware of the schedule of when to perform this operation.