UNIVERSITY OF SOUTHERN PHILIPPINES FOUNDATION

COLLEGE OF COMPUTER STUDIES

IT 312 – SYSTEM INTEGRATION & ARCHITECTURE 1

EVENT ATTENDANCE
(A Hybrid Student Attendance iOS Application)

Prepared By:
Antipuesto, Niña Ruthchie B.
Pascua, Daliber

1
TABLE OF CONTENTS

Cover Page .......................................................................................... 1

I. Executive Summary ................................................................. 3
II. Work Plan ............................................................................... 4
III. Feasibility Analysis ................................................................... 5
IV. Requirement Definition ............................................................. 6
V. Use Case Model ....................................................................... 8
VI. Process Model .......................................................................... 9

2
 I. EXECUTIVE SUMMARY

We believe that attendance is playing a big role in every student in school.

Attendance is key, as they say. So this Event Attendance is a hybrid iOS

application which can truly help us manage our attendance status in every

event required for every department in school. Event Attendance is a helpful

tool to help our dear students and for the department manage every student’s

presence in each event. This application monitors the attendance of every

student in every event required by the department. This allows the

department admin or the in-charge to create an account and will be able to

see the list of students enrolled on that specific department. On the other

hand, the students should also have their own account and will receive a

notification regarding the said event together with a registration form. Instead

of using paper, this application will serve as the admin’s attendance checklist.

Some instructors or those who are in the teaching staff uses attendance as

additional points to their students’ grades. Indeed, attendance is one of the

important matter in school.

3
II. WORK PLAN

4
 III. FEASIBILITY ANALYSIS

The Event Attendance application is kind of simple and common yet really

helpful. Can we build it? It will be developed by a short span of time since this

only focus on checking the attendance of the students for those required and

important school events that is required by the department. Basically, this will

serve as a checklist of the one in-charge in checking the attendance. This

application is way better than using paper each time the department requires

the students to attend this specific event in school. It is either the students

will pass a paper written his or her name or the one in-charge will provide

copy of attendance sheet. In solution to this, an application like Event

Attendance is perfect for this kind of situation. We have been checking the

attendance in the most basic way by the using a paper and a pen, I think it is

time to level up and improve the process and since the university’s goal is to

promote high-tech way of learning to every student. This benefits both the

school and the students since this project has zero development cost. Less

hassle, less paper to use.

5
IV. REQUIREMENT DEFINITION

IV.1 Functional Requirement

1. Log In

a. The system needs to have options for the identification of

users. It is either Admin or Student.

2. User Interface

a. The system should allow both admin and student view the

events.

3. User Functions for Admin

a. The system should allow admin to add an event.

b. The Admin can add and check student’s name on a particular

event.

c. Once Admin added a new event, it should automatically send a

notification to the students.

4. User Functions for Students

a. The students can see their names in each event.

b. The students should receive a notification with a registration

form. An indication that there is a new event at school and

every student should register.

IV.2 Non-Functional Requirement

1. Performance

a. The system should be reliable.

6
2. Security

a. User logins are stored securely in a database.

b. Passwords are encrypted.

3. Accessibility

a. The system needs to be accessed only in iPhone for mobile

device and in any browser for laptop.

4. Availability

a. The system should be available at all times.

7
V. USE CASE

Below is a diagram representation of the interactions of the users to the

application.

8
VI. PROCESS MODEL

This model is a graphical representation of the application’s workflow.

9
VII. Data Model

10