Requirement

Model of School Attendance Monitoring In Secondary Schools

System (SAMS)

..

ROSZANA MOHD AMIN

Universiti Utara Malaysia

2010

..
•
-~-----

Requirement

Model of School Attendance Monitoring System (SAMS) In Secondary Schools

A thesis submitted to the college Art and Sciences in partial fulfillment of the requirements Master of Science (Information for the degree Technology)

..

Universiti Utara Malaysia by Roszana Mohd Amin

..
...

© Roszana Mohd Amin, 2010. All rights reserved

KOLEJ SASTERA DAN SAINS (College of Arts and Sciences) Universiti Utara Malaysia

PERAKUAN KERJA KERTAS PROJEK

(Certificate of Project Paper)

Saya, yang bertandatangan, memperakukan (I, the undersigned, certify that) bahawa

ROSZANA MOHD AMIN

(804850)

calon un tuk Ijazah (candidate for the degree of)

MSc. (Information Technology)

telah mengemukakan kertas projek yang bertajuk (has presented his/ her project paper of the following title) REQUIREMENT MODEL OF STUDENTS ATTENDANCE MONITORING SYSTEMS (SAMS) IN SECONDARY SCHOOL seperti yang tercatat di muka surat tajuk dan kulit kertas projek (as it appears on the title page and front cover of project paper) bahawa kertas projek tersebut boleh diterima dari segi bentuk serta kandungan dan meliputi bidang ilmu dengan memuaskan. (that the project paper acceptable in form. and content, and that a satisfactory knowledge of the field is covered by the project paper) . Nama Penyelia Utama (Name of Main Supervisor):

..
..
•

MRolD

SAMSU SAJAT

Tandatangan (Signature) Tarikh (Date)

III

PERMISSION

TO USE

In presenting this thesis in partial fulfillment of the requirements for a postgraduate

degree from Universiti Utara Malaysia, I agree that the University library may make it freely available for inspection. I further agree that permission for copying of this thesis in any manner, in whole or in part, for scholarly purposes may be granted by my supervisor(s) or, in their absence, by the Dean of the Graduate School. It is understood that any copying or publication or use of this thesis or parts thereof for financial gain shall not be allowed without my written permission. It is also understood that due

recognition shall be given to me and to Universiti Utara Malaysia for any scholarly use which may be made of any material from my thesis .

..
..

Requests for permission to copy or to make other use of materials in this thesis, in whole or in part, should be addressed to:

Dean of Academic Affairs Universiti Utara Malaysia 06010 UUM Sintok Kedah Darul Aman

..

ABSTRACT

The focus of this study is to get a good requirement model for Student Attendance Monitoring Systems (SAMS) in secondary school. It is aimed at system designer who want to know how to design an efficient SAMS. Methodology was used for this study requirement requirements modelling elicitation, process. The methodology analysis, comprises requirements four main phases: management and

requirements

requirements verification. At the end of this study, a SAMS prototype were designed based on the requirement model. User acceptance testing was conducted to examine user's satisfaction.

III

..

ii

.. .. ..

ACKNOWLEDGEMENT

A lhamdu I illah, praise

to Allah

S.W.T.

for grving me strength

physically

and

psychologically to complete my thesis. It is my pleasure acknowledges to everyone who helped me explicitly and implicitly. First of all, I would like to thanks and give my warmest appreciation to my beloved parents, Tuan Haji Mohd Amin Mohd Jali and Puan Hajah Puteh Zawiyah Mohd Alias and my siblings who always encourage me complete duty on time. Special thanks to Universiti Utara Malaysia and its staff for giving me knowledge and opportunity to make my study meaningful. To my supervisor Mr. Samsu Sajat that has gave me guidance and supports in completing this thesis. To all people from S.M.K. Malim Nawar, S.M.K. Kampar, S.M.K. Sri Kampar and S.M. ACS Kampar, thanks for your cooperation. And not forgetting to all my friends that have been helping and supporting me throughout the entire duration of this semester, thanks for your kindness.

iii

T ABLE OF CONTENT

Page
ill

PERMISSION ABSTRACT

OF USE

i ii iii viii ix
x

ACKNOWLEDGEMENT LIST OF TABLES LIST OF FIGURES LIST OF ABBREVIATIONS

CHAPTER 1: PROJECT 1.1 1.2 1.3 1.4 Introduction

OVERVIEW 1 2 4 4 5 5 5 6 6 6 7 7

Background of Problem Statement of Problem Project Objectives Project Scope 1.5.1 1.5.2 1.5.3 1.5.4 1.5.5 Functionalities Data SoftwarelHardware Features Users

..
II.

..

.. ..

1.5

1.6 1.7

Project Importance Chapter Summary

iv

-..---------------

CHAPTER 2: LITERATURE REVIEW

2.1 2.2 2.3 2.4 2.5 Introduction Literature Review of Requirement Literature Review of Visual Modeling Literature Review of Attendance System Literature Review of Software Development Process Literature Review of Tools 2.6.1 2.6.2 2.6.3 2.7 Rational Rose 2000 Macromedia Dreamweaver MX 2004 EasyPHP 5.3.2 8 8 10 11 12 15 15 16 17 17 18 18 20

..

2.6

Literature Review of Web-based Analysis 2.7.1 2.7.2 Web Site Web Portal

.. ..
III

2.8

Chapter Summary

CHAPTER 3: METHODOLOGY
3.1 3.2 III Introduction Methodology 3.2.1 3.2.2 3.2.3
III

21 21 22 24 25 25 26

..

Requirements Elicitation Requirements Analysis Requirements Management Requirements Verification

..

3.2.4 3.3

Chapter Summary

..
.. .. ..
.. .. ..
..

..

CHAPTER 4: FINDING 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 Chapter introduction List of Requirement Use Case Diagram Use Case Description Activity Diagram Sequence Diagram Collaboration Diagram Prototype of SAMS 4.8.1 4.8.2 4.8.3 4.8.4 4.8.5 4.8.6 Prototype: Login Prototype: Register Account Prototype: Manage Personal Information Prototype: Search Prototype: Register Class Prototype: Get Notification and Send Memo Prototype: Register Student Prototype: Manage Student Information Prototype: View Attendance 27 28 31 33 33 34 34 35 35 38 39 40 41 42 42 43 43 44 45 45 46

-..
lilt

4.8.7 4.8.8 4.8.9

4.8.10 Prototype: Manage Attendance 4.8.11 Prototype: Logout 4.8.12 Prototype: Forum

4.9

User Acceptance Testing

vi

..

..
.. .. .. .. .. .. ..
..
II

.. ..

..

CHAPTER 5: CONCLUSION

47 47 49 49 49

5.1 5.2 5.3 5.4

Project Summary Problem and Limitation Recommendation for Future Project Chapter Summary

REFERRENCES

50

APPENDIX Appendix A: Interview Questions AppendixB: Use Case Description

54 56 80 85 106

Appendix C: Activity Diagram Appendix D: Sequence Diagram Appendix E: Collaboration Diagram

..

vii

..

-----

---------~.~~~----

.-~---.-~-~-~--

__

.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
",_~ "~

LIST OF FIGURES

Figure 1: Parallel Model of tbe Requirements

Process .

Figure 2: Conceptual model of software development process Figure 3: Model for Integrated Functional Requirement Figure 4: Requirement modeling process

Figure 5: Details of Elicitation Activities. Figure 6: Model of SAMS Figure 7: Use Case Diagram: SAMS Figure 8: Prototype: Login Figure 9: Prototype: Register Account Figure 10: Prototype: Figure 11: Prototype: Manage Personal Information Search

Figure 12: Prototype: Register Class Figure 13: Prototype: Get Notification and Send Memo

Figure 14: Prototype: Register Student Figure 15: Prototype: Figure 16: Prototype: Figure 17: Prototype: Figure 18: Prototype: Figure 19: Prototype: Manage Student Information View Attendance Manage Attendance Logout Forum

viii

,.

.__

._.

w_~

.. _

••

,_

.. __•

__

___"...,.---_.

--',-,-

--

-,--------------.--,--~

__

.,~--.--

•. '--

.. .. .. .. .. .. .. .. .. ..
...
.

LIST OF TABLES

Table 1: Functional Requirements Table 2: Non-Functlonal Requirements Result

Table 3: User Acceptance Understanding

...

..
.. ..
ix

..

..
•
lit

.. .. .. ..

..
LIST OF ABBREVIATIONS

ASP BSD CFML DDL HTML

Active Server Pages Berkeley Software Distribution ColdFusion Markup Language Data Definition Language Hypertext Markup Language Interactive Data Language JavaServer Pages Hypertext Preprocessor Unified Modeling Language

.. .. .. .. .. ..

..

IDL JSP PHP

UML

..

..

.. .. ..
CHAPTER 1
PROJECT OVERVIEW 1.1 Introduction

In schools, attendance is important and mandatory. Nowadays, due to large number of students, it is efficient to use School Attendance Monitoring System (SAMS) to manage attendance in secondary schools. In recent years, system developers and designers have expands many ways and characteristics in design a good system.

A requirement characteristic

model helps system developers must have. Techniques

or designers

to understand include

what

for requirement

modeling

process

modeling, dataflow diagramming, entity relationship modeling and others .

•
1

..

1.2

Background of Problem

A generation ago, either in principle or in practice, attendance was not optional. Today, often in principle and almost in practice, it is optional (Romer, 1993). According to Lim,

..

Sim and Mansor (2009), most educational institutions'

administrators are concerned

about student irregular attendance. Shendell et al. (2004) defines it can affect student in overall academic performance.

Romer (1993) found that attendance did contribute

significantly

to the academic

performance of students. There is a slightly stronger relationship between attendance and

..

performance. Also, Durden & Ellis (1995) conclude that attendance does matter for academic achievement. Thus, it makes student attendance mandatory in schools (Romer, 1993), (Woltz, 1955).

Yet, almost everyone noticed that attendance in schools is far from perfect (Romer,

..
..
..

1993). There is a lack of school attendance data and a lack of consistency in the defmition and measurement of non-attendance (Bourke, Rigby & Burden, 2000). Large schools are more likely to have problems with student attendance than small ones (Epstein & Sheldon, 2002). Everyday, school staff spends much time to handle student's attendance .

..

There are many problems when recording data manually (Richard, 2005). Sometimes, the

..

attendance's record books were missing. In real situation, it is hard for school staff to search student's record by looking at attendance's record books one by one. School staff usually spend much time to find the student's record especially when there are many classes in the school.

Furthermore, parents may miss to get any information or letter from schools when their children didn't attend to school. According to Epstein & Sheldon (2002), high school staff's communications with parents about attendance can increased student attendance and reduced chronic absenteeism.

Hence, by creating school attendance system is one of the best solutions to address this problem. The system should help school staff to take attendance for student especially in secondary schools. It must make the process of taking the attendance easier, faster and secure as compared to conventional method. The conventional method of taking

attendance by calling names or signing on paper is very time consuming, inefficient, and insecure (Ervasti, Isomursu, & Kinnula, 2009), (Lim, Sim & Mansor, 2009).

III

It is a one way that helps teachers or school staff reducing the taken time to carry out routine processes and enable them connected with parents by sending real-time

information on their children's attendance immediately if students are not-attended to school more than the limit. Thus, teachers has more time for teaching. (Ervasti, Isomursu, & Kinnula, 2009).
3

lilt

1.3

Statement of Problem

Based on background of problem, several problems have been identified.

l.

To set up the first requirement models of student attendance monitoring systems in secondary school. The requirement model must meet the user needs, goals and constraints.

III

11.

The conventional method of taking attendance is very time consuming, inefficient and insecure. So, attendance system can assist to solve the problem of

conventional method. It is important to identify characteristics, features, relations and design implications to design a good SAMS. iii. User acceptance testing is important to validate user's understanding and

satisfaction to the developed system. User acceptance can be test by showing prototype to user under study. Hence, a prototype should be design and develop.

1.4

Project Objectives

The project objectives are:

i. ii.
lll.

To study and analyze the existing attendance system in secondary schools. To create a good requirement model of SAMS for secondary school. To design and build a prototype of SAMS.

1.5

Project Scope

The project scopes used to define the boundary of the project consist of system functionalities, data, softwarelhardware, features and users.
ill

1.5.1

Functionalities

The main functionalities of SAMS are register account, login, manage personal info, search, register class, send memo, register student, manage student info, view attendance, manage attendance, and logout.
III

1.5.2 Data

.. ..
til

The study was conducted within the Kampar district, Perak. All schools chosen for survey were secondary schools only. Similarly, there were nine secondary schools in Kampar district (sample size). Parents and people who manage secondary school organizations were the only respondents of the study. The population was between 3 to 5 persons. The particular focus areas of the study have included attendance system which already used in secondary schools. The collected data were used as a guideline.

..

..

..
1.5.3 SoftwarelHardware
Several type of software has been used in order to create a requirement model of SAMS for secondary school. Typically, Microsoft Office 2003 has been used for documentation, Rational Rose 2000 to create diagram, Macromedia Dreamweaver MX 2004 to design coding and easyPHP as a web development tool. Then, personal computer (PC) or notebook has been used as a hardware component.

1.5.4 Features

.. ..
..

One of the features of this SAMS is web based application which operates for several type of user. Admin, staff, teachers and parents can login into the Student Attendance Monitoring System (SAMS) with an authorized access .

1.5.5 Users

The proposed requirement model of SAMS will be used by system designer or developer . However, the SAMS will be used by admin, staff, teachers, parents and students .

.. .. ..
..

..

1.6

Project Importance

At the end of this study, the requirement model can help any system designers to design

.. .. .. ..
..

good SAMS for secondary schools. They will know how to design useful, usable and desirable SAMS such as in the system should contain the right functions, secure and must be user friendly. SAMS should contain all the basic needs of attendance system such as records student's attendance, checks either student is present or absent, process the attendance data, save it and send an email to the parents if student was absent more than limit .

The aimed of requirement model for Student Attendance Monitoring System (SAMS) is to help system designer in designing a good attendance system and also conduct them to develop the attendance system in the future. Attendance system are important because can gives many benefit to schools such as security on attendance, reduce work time on taking attendance and create connection or link between school staff and parents .

1.7

Chapter Summary

..

With the proposed requirement model of SAMS, it is hoped that this requirement model will help the system developers or designers to create a good and effective student

.. ..

attendance monitoring system for secondary school and replace the conventional method of taking student's attendance.
7

..

..

.. ..
III

-..
CHAPTER 2 LITERATURE REVIEW

2.1

Introduction

..

A literature review is an analysis of published information that researchers have written on a certain topic. It is expressed according to issues or problems that the researchers wish to address.

2.2

Literature

Review of Requirement

..

A requirement described as a statement of what the system must do or what characteristic it must have. It is a function or characteristic of a system that is necessary, the quantifiable and verifiable behaviors that a system must possess and constraints that a system must work within to satisfy an organization's problems.
8

objectives and solve a set of

..
Similarly, requirement also defined as a condition or capability needed by a user to solve

.. .. ..

a problem or achieve an objective or must be met or possessed by a system to satisfy a contract, standard, specification, or other formally imposed documents (Christel & Kang, 1992). Requirement is divided into two categories which are the functional requirement and non-functional requirement (Sommerville, 2001) .

In the requirements model, the system is considered as a black box (Gomaa, 2001). The use case model is developed. The requirements process is often described as a series of activities such as:

..
:E
ti -t ~ e ~ E
:l)

III

100%

'"
75%

50%

·S

L..

.. ..

._

e ti'"

:::r ~ ,..,

25%
0%

time -->

Figure 1: Parallel Model of the Requirements Process .

The majority of existing models of the requirements process show it as an ordered sequence of activities. In reality, requirements activities are not performed sequentially, but iteratively and in parallel, as shown conceptually in Fig. 1 (Hickey & Davis, 2004).

.. ..

..
2.3 Literature Review of Visual Modeling
Visual modeling can be defined as the mapping of real world processes of a system to some graphical representation (Bennet, Skelton & Lunn, 2001). Visual models give the

.. ..

software developer a graphical representation

of the structure and interrelationships

within a system. In addition, it helps software developers organize, visualize, understand and create complex system aspects. The blueprint makes explicit the requirements of the project, ensuring that the final product meets the needs of the end users.

.. ..

The standard language for visual modeling is the Unified Modeling Language (UML). The Object Management Group (OMG) adopted UML in 1997 as a standard modeling language for object-oriented applications. As with any language, UML has its own notation and syntax. UML notation comprises a set of specialized shapes for constructing

..

different kinds of models. Each shape has a particular meaning .

The UML syntax dictates how the shapes can be combined. UML has become the software industry's standard notation for representing software architecture and design models. By using the common language of visual modeling, communication is improved, development time is shortened, and complex systems are easily understood and therefore easily constructed, while designs are made cleaner and more maintainable (Shumba, 2005) .

.. .. .. ..

10

..
III

2.4

Literature Review of Attendance System

According

to Epstein & Sheldon (2002), reducing

the rates of student chronic

absenteeism has been and continues to be a goal of many schools and school systems. In 1999, a student tracking system involving a database is being trialed in government and non-government schools Western Australia (Bourke, Rigby & Burden, 2000). The

student tracking system involved a set of processes, procedures and systems which can identify and monitor the location of students.

In the Torres Strait schools, they used a system called Student Information Management System (SIMS). The SIMS provides a good quality data regarding student attendance. This computer-based system collates individual class attendance records on a weekly basis (Bourke, Rigby & Burden, 2000).

The relationship between staff and parents was seen as vitally important by parents and principals. The student survey results indicated that attendance levels were significantly

higher among students when teachers got in touch with their parents to talk about how they were going at school (Bourke, Rigby & Burden, 2000).

Therefore, in schools where students have attendance problems, school staff may need to go beyond the school building to involve parents in reducing absenteeism (Epstein & Sheldon, 2002) .

•
11

..

..

..

2.5

Literature Review of Software Development Process

Software Development is an activity of creating a software system that when used, solves some users' problems, leverages their opportunities, or satisfies their needs. Classic software development follows a well-defined series of phases, traditionally called a waterfall model. More recently, software development is performed iteratively where development activities are repeated multiple times, resulting in a time series of

successively more sophisticated products (Hickey & Davis, 2004).

..

There are many views of software's development or development process though that has evolved over the years. What follows is a brief discussion of the theories of the software development process that recently used today. The first formal description of the software development process model is published in 1970 by Winston W. Royce. Refer Fig. 2.

.. ..
.. .. .. ..

According to Royce (1970), firstly, developer must analyze user requirements. After that, make requirement specifications by clearly set out necessary features of system based on user requirement. Then, developer can design a suitable solution and do implementation by develop the proposed solution. In addition, developer must test the system to ensure that the solution solves the original problem and works in context. Lastly, developer must maintain the system .

12

Below is one of the software development process's models:

.. ..

Figure 2: Conceptual model of software development process

Implementation of an application system can present many unforeseen challenges. The first step toward implementing a student data analysis system should be to thoroughly assess the data, needs, and resources available to a school or district. The successful implementation is important for the long-term development of a data based decisionmaking climate (Wayman, et. al,2004) .

.. ..

13

.. ..
..

There are varieties of opportunities for implementing IT in management education . Technology can be used to facilitate the display of information, to increase access to external explicit information, and to increase the sharing and construction of knowledge (Leidner & Jarvenpaa, 1995) but some of the use of this technology is not yet

widespread, efficient and practical for implementation of data management (Wayman, et. al., 2004).

Fig. 3 shows the model for integrated functional requirement which has been explained by Malet et al. (2007)

Process

)\

.. .. .. ..

... ~

..---;--• • • , • •
...

........_
•

_- _-

.._ Initial Li1k Result

Figure 3: Model for Integrated Functional Requirement

In Fig. 3, functions can be linked with specific processes. The technical realization of functions takes place in these processes. Functions can also be related to specific positions in the product structure. As a result of linking the requirements with functions, functions to processes and the product structure, an indirect relation between

..
...

..

requirements, processes and the product structure has been established (Malet et al., 2007). 14

.. .. .. .. .. ..

2.6

Literature Reviewof Tools

I have decided to choose Rational Rose 2000, Macromedia Dreamweaver MX 2004, and easyPHP 5.3.2 as tools in this study. The description of these tools is as follows:

2.6.1 Rational Rose 2000

The Rational Rose is designed to provide the software developer with a complete set of visual modeling tools for development of robust, efficient solutions to real business needs in the client/server, distributed enterprise, and real-time systems environments.

Rational Rose products share a common universal standard, making modeling accessible to nonprogrammers wanting to model business processes as well as to programmers

modeling applications logic.

..

Rational Rose is suitable for business requirements analysis or business scenario analysis with sequence and collaboration diagrams, state modeling, and additional code generation capabilities for DDL and IDL, along with the inclusion of a scripting language to provide

..

access to the Rose domain (Quatrani, 1999).

15

..

2.6.2

Macromedia Dreamweaver MX 2004

Dreamweaver MX is poised to bring dynamic application development to the masses. Dreamweaver MX offers easy-to-use tools that can very quickly connect to databases and Web pages in a logical and visual manner. Dreamweaver can design interactive sites on Windows and Macintosh computers, but deploy the appropriate code to run the sites on UNIX, Linux, BSD, Windows, Macintosh, and dozens of other operating systems.

It combining the power of the full HTML language and an interface that made publishers and designers feel at home, it brought cross platform HTML development to the world.

.. ..
..

With HTML in the hands of the masses, Web page design is available to anyone. This has pushed the elite HTML programmers to move onward and upward to the next big thing . This big thing is creating sites that interact with the users .

Dreamweaver ASP.NET)

MX supports five server technologies (JSP, CFML, ASP, PHP, and through plug-ins .

with the capability to expand to new technologies

Dreamweaver MX offers the designer the ability to preview data in real-time within a document design. It makes life even easier by allowing the person designing the application logic to work on the database side while designers work on the page layout (Ray, 2002) .

..
lilt

16

.. ..

2.6.3 EasyPHP 5.3.2

Easy PHP is a software application written in dynamic PHP language that combines an Apache web server and MySQL database to create flexible web development tools. Apache is an open source web server. Web servers use hypertext transfer protocol (http) to enable a computer user to connect to the Internet. MySQL is an open source database that organizes information through tables and enables interactions between the user and the web through the creation of dynamic web pages.

2.7

Literature Review of Web-based Analysis

Most oftoday's web based solutions are focused on the design and manufacturing part of the equation. As such, they are very focused on data security, sharing, and visualization. The processing of the data is still seen as mainly a desktop/client function. Analysis provides an opportunity to expand the role of the Web from a role of data sharing to one of distributed data processing. For analysis, data visualization is not a static function. Analysis runs can produce enormous results files that will burden even the fastest Web connections. Servers need to process this data into useable form for client requests (Carroll & Hawkins, 2002).

17

..

2.7.1 Web Site

Web site provides the key interface for consumer use of the internet. Web site is a primary user interface for business, information provision and promotional activities. Developing sites that are responsive to user needs is critical for all site designers and managers. For web page owners to be successful and for users to be satisfied, Web sites

..

need to consider usability and other design criteria. User interactions with sites that exhibit higher than normal usability have been significantly associated with performance improvement. Poor interface design has been a key element in a number of high profile site failures. Web site design can benefit from the application of usability principles, media richness theory and marketing concepts (palmer, 2002).

2.7.2 Web Portal

According to Elmagarmid and McIver (2001), digital government (hereafter called egovernment) can be defined as the use of adequate information and telecommunication

technologies to support political conduct of government and enhance its services to citizens and various constituent communities. The core function of current e-government practices is to provide a wide range of government services through Web portals, namely e-services. Critical to e-govemment development is how to deliver an array of e-services to citizens and constituent communities through Web portals effectively.

18

Customizability is generally considered a desirable feature of web portals. However, if left uncontrolled, customizability may come at the price of lack of uniformity or lack of maintainability. assumptions Indeed, as the portal content and services evolve, they can break in the definition of customized views. Also, uncontrolled

made

customization may lead to certain content considered important by the web portal owners to not be displayed to end users. Thus, web portal customization is hindered by the need to enforce customization policies and guidelines with minimal overhead (Weske, Hacid,
& Godart, 2007).

2.8

Chapter Summary

From the literature review, there have been lots of facts gathered to help in developing SAMS. From the study, there some features can be adapted to promote usability of attendance system in the future. Besides that, it gives reasonableness that this SAMS is very important and useful to be developed. This requirement model of SAMS supposes to give benefits and importance to developer and designer of attendance system.

III

20

..
Continuing advances in web technology combined with trends such as Web 2.0 are generating higher expectations for user participation and customized user experiences on the Web. These heightened expectations entail additional maintenance costs for

..

..

community-oriented web sites, such as web portals. A natural way for web portal owners to balance higher expectations with the imperative of keeping a manageable cost base is to open up the box by allowing the community to contribute content, services and presentation components into the portal.

This way, the portal owner can focus on developing and maintaining the core of the portal instead of doing so for every service and presentation component offered by the portal. Also, increased openness and community participation has the potential of

promoting fidelity, by motivating end users and partner sites to continue relying on the portal once they have invested efforts into customizing it or contributing to it.

On the other hand, this increased openness needs to be accompanied

by a sound

governance framework as well as tool support to apply this framework in a scalable manner. Indeed, a manual approach to reviewing and correcting user-contributed

components would easily offset the benefits of accepting such contributions in the first place.

19

..

CHAPTER 3

METHODOLOGY

3.1

Introduction

Methodology

defined as the physical implementation

of the logical life cycle that

includes roles, sequential activities, and system deliverable (Whitten & Bentley, 1998). It is a body of methods, rules and set of procedures of inquiry in particular field. It also defines as the philosophy of process that integrates various values and assumptions as a standard for interpreting and getting a conc1usion (Nunamaker, et.al., 1990).

3.2

Methodology

The methodology comprises four main phases: requirements elicitation, requirements analysis, requirements management and requirements verification. Fig. 4 shows the requirement modeling process which has been explained by Malet et al. (2007). 21

III

Requirements Elicitation

Requirements Analysis

Requirements
Management

Requirements

Veti~tion

III

Figure 4: Requirement modeling process

III

Requirement's

modeling takes place in all phases of product development.

More

..

emphasis needs to be put on later development phases such as usage, recycling and maintenance. The knowledge gained in these phases, once included in the development process, can accelerate the development of new products (Malet et al., 2007).

3.2.1 Requirements Elicitation

The first step was elicitation of requirements. According to Hickey and Davis (2004),
III

elicitation is all about determining needs of stakeholders. Most models of requirements elicitation focus on specific methodologies or techniques. Requirements elicitation is recognized as one of the most critical activities of software development. Poor execution of elicitation will almost guarantee that the final project is a complete failure.

22

III

..
Below are details of elicitation activities by Hicker and Davis (2004):
III

-.~---~ · .. ~ C
s.ers.. Customers, ' j & Other Stakeholders __ ..._-- ! -,
.

In~ulH'd I'rohIt' ms

.--_.-~.-------

( 'andtdare R eq ui re rtwn ts

.....

Problem

Known
Problem .\ Prlljl'd Requirements

()omaill

Domain
Sitmll
\

Kno\\ll'dl!("

" Situalion

Problem &

Dommns

Solution

Project DOmain

Figure 5: Details of Elicitation Activities.

The requirements were based on collected data. The sites were the secondary school managing departments. The sampling frame was based on the list of the secondary
III

schools within area of Kampar district, Perak. The sample sizes were nine secondary schools. The population was between 3 to 5 or more employees including principal, clerks, teachers and parents. The method of data collection was by interviewing.
III

Interview is a method of collecting data in order to get information on the issues of interest (Sekaran, 2003). 23

During interview session, the informants were selected individuals within the sample employees who had an experience of using any school attendance system. An interview is a directed conversation with a specific purpose in question and answer format (Kendall, 1992). According to Satzinger, Jackson and Burd (2005), a list of questions should be prepared and discussed until all the requirement process were understood and

documented.

II

The purpose

of the interview was to get employee's

personal

details, personal

experiences of using any school attendance system, problem with existing attendance system and an opinion or suggestion for the future system's developer. Opinion or suggestion from each employees or parents within the sample can helps system designer or developer to understand the actual problem. In this situation, interviewer gets more background information about the employees or parents and the school environment to perform well interview session.

III

3.2.2 Requirements Analysis

•
The second step was analyzing the requirements. According to Christel and Kang (1992), requirements analysis is a process in which what is to be done is elicited and modeled. This process has to deal with difference viewpoints, and it uses a combination of methods, tools, and actors. The product of this process is a model, from which a
III

document, called requirements, is produced.

24

III

..
All user requirements were investigated. The data were analyzed and checked for

..

consistency, validity, verifiability, realism and completeness. It has been interpreted and translated into a form that suitable for other developer (sequence diagram, activity diagram, class diagram & etc.). A requirement specifications model were defined by clearly set out necessary features of SAMS.

3.2.3

Requirements Management

..

...

The third step was managing the requirements. In this step, a prototype of SAMS was design and built based on user requirement model by using several types of tool such as Dreamweaver MX and easyPHP. During this system development lifecycle, requirements always changing and evolving. These changes had been tracked and traced (Malet et al., 2007).

3.2.4

Requirements Verification

Lastly, the fulfillment of requirements was validated with virtual or physical tests. A product was deemed successful (by means of satisfying the customer) if all requirements are fulfilled (Malet et al., 2007). SAMS was tested to ensure that the solution solves the

..

original problem and integrate the system to make sure that the solution will working in circumstance .

25

The user acceptance testing had been done by choosing user randomly within the sample. It was conducted to test the system usability and performance by giving a questionnaire to the respondents. The results such as feedbacks and recommendations were gained in order to get an effective and comprehensive Student Attendance Monitoring System (SAMS).
III

3.3

Chapter Summary

Methodology contains with several techniques, procedures and tools that utilized by system designer or developer. It is usually written down as a method statement relating to a particular enquiry.

III

..

26

CBAPTER4

FINDING

4.1

Introduction

This chapter will discuss UML diagram. The UML will elaborate in detail about Student Attendance Monitoring System (SAMS). Fig. 6 shows model of SAMS.

Figure 6: Model of SAMS 27

4.2

List of Requirement

III

Listed below are the functional requirements and non-functional system. In the priority column, the following short hands are used: • • M - mandatory requirements (something the system must do)

requirement of the

D - desirable requirements (something the system preferably should do) 0- optional requirements (something the system may do)

III

Table 1: Functional Requirements No. Requirement ID SAMS -01-01 SAMS 01 02 SAMS 01 03 Requirement Description Priority

SAMS 01

1. 2. 3.
lit

LOf,dn Admin, staff, teachers or parents shall key in user ID and password. System shall verify user Id and password. System shall detect invalid user Id and password. Register Account Admin shall register admin, staff, teachers or parents in the database. Admin can save an account registration. Admin can reset the registration if she/he wants to clear an account registration form. Mao32e Personal Info Admin, staff, teachers or parents can insert new personal information. Admin, staff, teachers or parents can update personal information . Admin, staff, teachers or parents can delete personal information. Admin, staff, teachers or parents can save personal information. Admin, staff, teachers or parents can reset the information if she/he wants to clear the personal information form.
28

M D D

4. 5.

SAMS - 02- 01 SAMS 02 02 SAMS -02 -03

SAMS 02

M 0 0

6.

7.

SAMS -03- 01 SAMS 03 02 SAMS -03-03 SAMS - 03- 04 SAMS - 03- 05

SAMS 03

0 0 0 0 0

..

8.
,

9.

10. 11.

III

..
III

III

12.

SAMS 04 SAMS - 04- 01 SAMS 04 02 SAMS - 04 - 03 SAMS 05 SAMS 05 01 SAMS 05 02 SAMS 05 03 SAMS -05-04 SAMS 06 SAMS 06 01 SAMS -06-02 SAMS - 06-03 SAMS 07 SAMS 07 01 SAMS 07 02 SAMS -07 -03 SAMS 08 SAMS - 08- 01 SAMS -08- 02 SAMS -08-03 SAMS 08 04 SAMS -08-05 SAMS 9 SAMS 9 01 SAMS -9-02

..
..

13.
14.

Search Admin can search admin, staff, teachers, parents and student account/information. Staff can search class and teachers information. Teachers can search student and parent's information . Register Class Staff shall register class in the database. Staff shall assign class to teachers. Staff can save the class registration. Staff can reset the registration if she/he wants to clear the class registration form. Get Notification and Send Memo. Staff shall get notification. Staff shall send memo to parents after get the notification. System shall send notification to staff if student was absent directly three days. Register Student Teachers shall register student in the database. Teachers can save student's r~stration. Teachers can reset the registration if she/he wants to clear student's registration form. Manage Student Info Teachers and parents can insert new student's information . Teachers and parents can update student's information. Teachers and parents can delete student's information. Teachers and l'_arentscan save student's information. Teachers or parents can reset the information if she/he wants to clear the student's information form. View Attendance Teachers, parents and student can view daily attendance. Teachers, parents and student can view monthly attendance. 29

0 0 0

15. 16. 17. 18.

M M 0 0

17. 18. 19.

M M D

20. 21. 22.

M 0 0

..

23. 24. 25. 26. 27.

0 0 0 0 0

28.
III

0 0

29.

..

III

28. 29. 30.

III

SAMS 10 SAMS 10 01 SAMS -10-02 SAMS - 10- 03 SAMS 11 SAMS - 11-01 SAMS 11 02 SAMS 12 SAMS -12-01 SAMS 12 02 SAMS 12 03 SAMS 12 04 SAMS - 12-05 SAMS 12 06 SAMS 12 07 SAMS 12 08

Manage Attendance Teachers shall record daily attendance. Parents can list down reason why student absent to school. Teachers can manage reason why student absent to school. Logout Admin, staff, teachers or parents shall exit from the system. System shall stop running. Forum Admin, staff, teachers, parents or student can register into forum. Admin, staff, teachers, parents or student can login into forum. System shall verify user Id and___gassword. System shall detect invalid user Id and password. Admin, staff, teachers, parents or student can post topic. Admin, staff, teachers, parents or student can reply to any t~ic. Admin, staff, teachers, parents or student can logout from forum. System shall stop the system from runnin_g.

M 0 0

31. 32.

M D

..

33. 34. 35. 36. 37. 38. 39. 40.

0 0 D D 0 0 0 D

Table 2: Non-Functional

Requirements Description Priority

No •

41. 42.

Requirement ID SAMS 13 SAMS 13 01 SAMS 13 02

Requirement

Reliability issues The system shall categories the user by refer the user Id. If the systems crash, it should behave perfectly normal when reloaded again. Usability issues Only the admin can register an account for admin, staff, teachers and _parents. Only the teachers can register student. The system should be available for use 24 hours per day, 365 days per year
30

M M

43. 44. 45.

SAMS 14 SAMS 14 01 SAMS 14 02 SAMS 14 03

M M M

III

4.3

Use Case Diagram

There are 17 use case that have been identified that involved in this requirement model; login, verifying, register account, manage personal info, insert info, search, register class,

..

get notification, send memo,

register student, manage student info, view attendance,

manage attendance, manage absent reason, update info, logout, and forum.

Below is use case diagram for SAMS:

31

II

«include»

verifying

..

Admin

Parents

Student

..
..
32

Forum

Figure 7: Use Case Diagram: SAMS

4.4

Use Case Description

Use case description is a detailed specification of a use case. Use case specification is used to textually describe the sequence of steps of each interaction between the actor and the use case (Whitten et.al., 2001). Use case description contains eight fields; use case brief description, actor, pre-conditions, characteristic of activation, flow of events (basic flow, alternative flow, exception flow), post-conditions, rules and constraints (Dennis,

2005). There are 17 use case description for this requirement model; login, verifying, register account, manage personal info, insert info, search, register class, get notification, send memo, register student, manage student info, view attendance, manage attendance, manage absent reason, update info, logout, and forum. Use Refer to appendix B for full detailed of use case description .

..

4.5

Activity Diagram

Activity diagrams describe the workflow behavior of a system. There are nine activity diagram which explain the workflow of SAMS; login, manage personal information and logout, register account, search, register class, get notification and send memo, register student, manage personal information, view attendance, and also manage attendance and manage absent reason. Refer to appendix C for previewed of activity diagram .

.. ..

33

4.6

Sequence Diagram

.. ..

Sequence diagram defines as interaction diagram that shows different processes. A sequence diagram shows as parallel vertical lines (lifelines), different processes or objects that live simultaneously and as horizontal arrows, the messages exchanged between them . This allows the specification of simple runtime scenarios in a graphical manner. There are 17 sequence diagram for this requirement model; login, verifying, register account, manage personal info, insert info, search, register class, get notification, send memo, register student, manage student info, view attendance, manage attendance, manage

III

absent reason, update info, logout, and forum. Sequence diagram are categorized into three flow; normal flow, alternative flow and exceptional flow. Refer to appendix D for full representation of sequence diagram.

...

..

4.7

Collaboration Diagram

Collaboration diagram is sometimes called communication diagram. It holds the same information as sequence diagrams. It show link between objects that participate in the collaboration. There are 17 collaboration diagram for this requirement model; login, verifying, register account, manage personal info, insert info, search, register class, get notification, send memo, register student, manage student info, view attendance, manage attendance, manage absent reason, update info, logout, and forum. Collaboration diagram

.. ..

34

emphasizes the flow of messages through a set of objects. Refer to appendix E for detailed of collaboration diagram.

4.8
III

Prototype of SAMS

III

Below is prototype of SAMS. It is one of the website which is most reliable, scalable, and easy to use.

4.9.1

Prototype:

Login

User must entered their user Id and password before can access the system.

..

Login for Admin

..

Welcome to Student System (SAMS)

Sb.ld.nt
AtQndalta ~m

Attendances

Monitoring

MO"nltvrl"'1il b. •• d
0"

'5ymm

(~}

h •• '-rtrv .. ThitI .....'" rowtfnoe. Itvd.nt

• bru:l.nc.

_b b•••

d .l;Ipiiaatio"_

aDofiQtIoft giYII"f\iI •••• ta t..c!M~ 11'1 ttt.Ir e~.J' .tt..,<1 • ...,.. S.I.MS OOI"Iboh" I Stud:tlrtt I"fonftatioft -, Stud.". ..... un

0'IId._
_

Student

Ab ..

Usl

-c

~nA.R.po!'t: Fofum,

.. ..
III

:..: SAMS

r-unc ticnafitv

or uerformancc
Monthty Atteno:bil1'Ce ~

UPng' StudeI'II: ..... floCf.:a_ ~"SII end I'nIoOdI fa.t:er ~" t.disonaI .~, .. nd .. cb.-It • ..,...,._. ......

_".. I..cI

(SAMSj Is ~ a.H'd __ b balled

till'

........ aIId

5AMSf"oru:m

~\
:MMt ~

b:t:Iv
to

M;JIW'.""""'_"

jua _.,.

.'R... ~ ~

..

User name: admin, Password: admin

35

..
Login for Staff
ISch
0

a I S A !'vIS

(,
~

.: , '
.. b-Jut ooortultHN L.,..,Lo~"t

..
..

Vielo:<rl(:_' ttl StlF:kn~ j\ftend:".,-,

.~').'Sf,~:l' Stu-=! ..t •

<".0.

~~fpni-J':-J;>inq

!:sr;MS~
.... ::. "'ol\oito ..... ~

;I...th.:-.':!

5:,.C •. '"

:S~M::::+

ill'

.I'~"'I:
t

-'

.U."d • .,ee ."st.." t;.s.d 0" .... !::. bl •• d 'I::~;::'tio". Thill " ••• .::::Ik.tjo" Ij;Ni~ •••• tQ t..c"t.'"1I In t .... ., ....... ;,c.·.. !"Outl_, atr."d... Itte'1dl"r3, SA"'!
to"b.ln I

Stud."t I.,~tio" .
Shlc.~ Sh"c.,*

J ••••• Urt

.r.u..'td,!'\ao
.c..bl~'

un

J.J;:a."'OI.
!A~S

R.c.ort

Fo"",",,

Uri""Ol Shld.!"It .Att.!'td.nt.

and r'UJCo a;>pficatkl",

NlO<1itori",=~h·n.m
to b ....""

,:S.AMS! II much .....

'I'OI~

f,rte<- ti't .. " lIIdllo".1 -V" •• c, ::>.nlO" do ..... ·t nelod

e••• ~ 0"

balled

;:IaPlr

.end

It .. ,,"{""I'I.......

.t.It ....... ort: .ltOlJld jlln

'''.1'')'

.",m. ..... arot:!

•
.Ii."I,

tQ

view 'I

dkk_

.. ..
,

User name: staff, Password: staff

Login for Teacher

School SA.i'IS :

.. 1;><,,,'

pnctufol •.,

,r,nl .. ,t

wetcou-e to Student Attenc\;]nces Monitoring System (SAMS}

Sb.;<I."t .att.rtdanC41 Mo,",Ito<i"'= S)'rtern (SA.fI.1S) I••• .tt.rtd.~
.pQbtio" .u..,,,d • ._,

1.dTo"k TiVs ,"-1'1"

f'O'Ai,"-.

lyJt.m
SAMS

b •• ed 0,",.... b ba •• d .otlbtion. to t:..~ tc.,t:.i" I '" thoaJf

.Teryd.y

gfvlrtfil ••••

Jb.I<! ....

Sb.ld.rttlcrformatkm " S"b.ld.!'\otlottllrtd.1IW Ult )-; Stu-C.rtt Aobnl'lot tist ,,_ AobI.1IW R,4IQOrt:

..

Function alitv or perfo

UII.". Sb"c!...-,t .c.u.~.I'IC4I

rrn

ancc s.,lt4IrTI

D.ify

Attlffid",,,ce

Mot1itorl"'1l

.'1'd ,.....c, ~~ 1.'tCIIte-n~

tart.<"

th." bclllolta1
....

_,I.

,,--.:I

(SAMS}

a" _b

Is rnud\ billed

.........

...

ch ~

~QOI't~"'"

doout\"t.....:l to boi.". .,..,... • .".....,. ...... ~

••• .,to

.... ·".p,.;hodk:lt.

User name: teacher, Password: teacher

36

..

..
Login for Parent
,School SAMS (;
~

./
dbQut IX)rtofoJoo r out.ect

..

\N\~:(c-rnt~~ t(,,_ Studcu: Sv-c;tr~!''1j'S;"\MS;

Stu'::.nt .. tt.'1'd.~. IoIOl"lito"f"'W

~\it,

nd.:;oe'"2_'"

Monit[';;I,q

S.,..:rtem
....

(s.:-MS,

be II .h!d!"Onk

.ttend.".:.

.ystlm ~':I'.d (I"I

••••

b b'.ld
j'l

.c::c::liatkl .... Tkis '-'" .. ,·.-,-t:lly

'"OL.'ti"",

.;:p4i,. .... Ho"l ;Iyl"",

tt: tel~""

~r-

rtl.:dl'lt

iE_arenC
P.uworc;!

__j

,t:t."dl"tQl. SAA~S conQ.j" e

Stud.nt
Stuc! •

l!'lfQnn.. \io."
Lbt

...t Att1IrtC!~ -se. -

stue.nt

.b-... l\ctI Wit

r-unr.tionality
UII.,.. Stu!! I,.,d
,"1.10,

(_lr-pcrforrn;,.nuc AIh.,od.... ,.. ,""o.,Itvr!I"I'i5ylw", (SAM's)

r..
....

m"o,

........

F
••• ".,

th.11l b.:'ho".1 ....y•. Sallllci em v.. b b •• .d

~I"JO"

.;)C;II~ttol"l

cae.,'"t

l1_d

to

brtr"IQ ;:;I1I~r

, • .,c!

it

._.,yv.h.".

I:.Il .... ;lort lhoo..~

l.... t .. II·!

ee

..,1 ...... I •••

,-.-.tte"" and ,...... .. dick. !

User name: parent, Password: parent

..
.. .. ..

If the user entered invalid user Id or password, the system will display error message .

Error Message

Login Inccorect, Please Try Again Back to Main PaRe

So, the user needs to key in a correct user id and password when trying to log in into the system .

37

III

III

III

4.9.2

Prototype: Register Account

Admin can register admin, staff, teachers or parents.

.. .. ..

Admin and Staff Registration

'SM1S

HonK'-

,>t.1f

1.......,.....

.'..........

l()Q""t

~ .......... I

Sb"'

... tlT •• ".....

~n.<;J",St.eH

Teacher RC2istration

T[J\CHER R[G~~'! RAT10~'

T~

rc , :-

-----11

SEARCH

I ~fI.r.d.T..cher

.. ..

'-"'

.. ..

38

.. ..
lSAI'1S

Parent Registration

..........

;'t ... tI

I .. ~tw.-r

I-J •

..-,t

l<>'9O"'~

.. ..
4.9.3 Prototype: Manage Personal Information

...I

..

Admin, staff, teachers or parents can manage their personal information such as insert new data in blank text box or edit the existing data by click "CHANGE" button, reset data by click "NEW REGISTRATION" and delete data by click by click "DELETE" button.
Manage Personal Information

.. ..
.. .. .. ..

..

EDIT

OWN

INI-ORMAfJON

A.!""'n/n.ffl.,fo~
... .,... PIa tc U.... T~ Ronan. HI

..
Mohd AmI"

~..... I~"~ ~
S~ff.I'tdT •• ~r

I .. tonn.tioft

.....
U~m

••

., • ............-.1

Admin dmln Mrntn

__ .~:T __

·co...

~~

I JEW REGlSTRA TlON I

.. ..

39

..
4.9.4 Prototype: Search

..

Admin can search admin, staff, teacher and parent. Staff can search teacher and student. Teacher and parent can search student.

.. .. .. .. .. .. .. .. ..
..

Search Admin/Staff

IAdm;n

j Staff

No IC , '--

---'1 [ SEARCH

II

Search Teacher
rc .]'---' S_EAR C_H__ __

Tea"'.,

Search Parent

SEARCH

II

Search Student

IStudent

IC j MyKIO '---

-'1 [

SEARCH

40

..

..
4.9.5 Prototype: Register Class
Staff can register class.

,SAHS

.. "'.-

.....,-.. "~ "

' ......... ,

"tu.J.!,,'

~<>9'O"t

..
..

Wf'i~~Llllh' \0 S\udcnl_ SYSIC{]l (Sr..MS)

A\'_l<cn~\<,nr_C5 Mr'l"illr:r:!,\l

.a ..

'~.r.tt.~._ "'0'*'""'" ">d._ ....-.... No_ ..,.,

.~t6o<>"""''Y,I'''''to
yltl.c

h~ b

,)I.I.IotI) Is • .a..v.,l'Iic ..! .D~tIo ... N~_..__ . 1Fbo~..t

.tt... d.._.SIUo!SClI
• ..tl~

,·~.r.tt_d.._Urt Job ... _

-_
... poot

_~

_b

'reecne-

... I..",*,._ryc!.T

..... ,.,,'

I-''''''_''_
Student Attendance

Class

....

...

logout

u.l"9Rud.",.,

III_~$y

...... _Y:l. a._d ",It ...

(s; .... s;!br: ..... d'o_ ..... on _iI b4qd ...

II

....t.....c.

u..." t.lcbtoro"
pOtt

.. ~t6o<>F.-.ctI~

.. d_'-.:I'ta

brI~IM_.~
y

<>d

..

..
uset

_...:I

it. • ..,. ................

.'-'1eI

to .........

.Ito;k

dick-

During registration, staff must key in class name .

._p
---~I
S€AACH

CLASS REGISTRATION

..

d."

1111.",.Ij~.

.....

"'.1'1.9'"

n~

p,",~~o".:"~~t.o" I

T •• r;t, ... S~.rch"'e.dl'c.Il'1fonTIiJt;O'l'!

0...
Regirle<'iUpdBllI! a.u

5tu<d.I'Il~I'Id._
"~ ... ",,,trfKiJti..,....

.. .. ..

41

4.9.6 Prototype: Get Notification and Send Memo

..
lit

Staff can get notification and can send memo if any notification appeared.

..
lit

~\HSrN t NOTlnCA DON

Personal

Teacher

ciass Student 1.u.....c. ..Attendance

tiRcation

logout

..

..

4.9.7 Prototype: Register Student

Teacher can register their students.

..
Q.AlS

Student RC2istration

uset

I•

"'h

__

w."",

",-ho

!!;.....chl!

..

STUDENT ... -e rc ,

R[GJSTRATJON
1If)«ICL__

--',1

SEARCH

..
III

42

lit

4.9.8 Prototype: Manage Student Information

..
..
•

Teachers or parents can manage student's information such as insert new data in blank text box or edit the existing data by click "CHANGE" button, reset data by click "NEW REGISTRA nON" and delete data by click by click "DELETE" button .

Mana2e Student Information

~,,,o.

\Y.~

~._~

.. i

~!I.""_"""
STUDfN

R[G]STR.ATION

tJpd.t.d

duO' .... I"'~"

........ '....,..._/~~
Shld • ..t .... ...,.,.... TO'bol'-"P1':--.d .. n",.

Nome

Adl Amad

III

~:~~t

~CykrD 122 Class 4 Amonoh Amad Abu Ind.h

Address No.4. Lorong Phone 012-1234567

lOll""ut

~,:~tamad_abu#lImall.oom

.iIIIII

4.9.9 Prototype: ViewAttendance

Teacher, parent and student can view attendance.

..

43

..
..
USER : Acko Wahyu ClASS : 4 Amanah Ramadhani

CLASS 5 PJl)J:NT LIS-! C€,'29,'2!;lC

---=::= I

PdtDalo

II SHOW I

""..... ITad.y

RCc"",.-t"~i

Up-d;>h;

5t>..:d .. "t

Q",d.~,I,Ii

....:!."w

Att...t~ Att",..,d.,,,,,C'

I"o;><.thl"

4.9.10 Prototype: Manage Attendance

.. ..
III III

Teacher can manage attendance by select no if student is absent.

Mana2e Attendance
ISAM S
QAss :
tL.~S5
USER :

",.,.
..... adhani

"OM"'"

,,_,.,'

.""

.. '-' ,

''"''' ..

Ade w....yu 4 Amanah

STUOTNT LIST

.,.,.., ...
SHOW

LD6_,_'29_,'2Ill0____]

I Pdto.oe II

H.a""9~

p~.,.,".1

InfontHlb<:>r'

.ltud.~
R..!iI~~/Upd.t~ 5rua-ntLnt Shood."t

stud • ...t~1\d.1'IW
Today Attendanct'

..
44

4.9.11 Prototype: Logout

User is able to leave the system by clicking on the Logout button.

V!!'t:~':":"WIt"""'~._ci\.a."" cuss " -.'\,.~!<:-S':,;", to Student Sy_"tc'~': (S(\MS}

sts.;d ..... A,*,,-.d._ .l:bofOC • ._ .~IIati U_Itoo1-.; .. 1M • ..:
~,

...... ::h-:nd:Jnu's

t),,=,.ni~;Jr;_n(l

_..c.~.
~ 'St\.le.

S,I'tII." ... 11 b .. ~

\S,",VS'i il •
'~<:I"',

.,....
~A __

Mc.tro.-n.;. _...

Student
stud.rot

.... gt..6nq .....

tg"".cto."""'~C_~'T

~"".

Student

Attendillnce

stu.jntl ............ licr.o ..... .......-...~Urt .. ~~Lht

TodilvAtt"nd"""e

Func!ionalit), ~
'IJI:I~'" ... "I!I .... ~

OJ

;-tF::rl('\'I,\<'ln,_Io:

,-Logout
{!"AIO!SJ Is ......:!'I_"",c
....

~"&Ib..e.,_
.......

IIIIO-«O~

s...-....
•••
tg or.I

."'Il......:!'lhl.ta~b.a

.. laod" .... I_r._ ~ ..... --.k

"C.~"C",,,l:_eQ!

Irrho;

Ju.t ...... to .... "" It

IJ'~'''''''''''_
•~

_bt.....:I

InC dkk.

..

4.9.12 Prototype: Forum

User can join into forum by register and login into the system. They can post any topic, reply to any post and communicate with each other.

on-.. __

......... -·-.--1rw.......,·

..._.- ...... _·..--,..,_ ·

tv ...........

..

I._~- _ ..,..."..• ..=.,

• ....

__

••

__

0 ........

• .....

, .. 11-_ ......

O __

I~

.-;r

...

...-

"'"'''''_ .......

•.... \I~.:._'

"" -. .. ~- '1.'"•• rltl.

1_._ ...... -_..

1\a....,.-'-.!..~".,-."'n.~-''1..
.. .,."4.0'_''''_'''''.:Io ~

<.<" ..._' ..,... \.~-...:.. .....

.. ~

"

45

III

..

4.9

User Acceptance Testing

After the prototype of SAMS was completely developed, it has been tested by users such as staff, teachers, parents and students. Majority of the users were less knowledge in information technology and rarely using any systems. The user was tested their feedback and understanding about the system and system's performance.

Based on testing, about 84.37% were satisfied with this system. As a conclusion, the ratio shows positive values for this test.

Table 1: User Acceptance Understanding

Result

User Yes No Total

Staff 8 0 8

Teacher 8 0 8

Parent 6 2 8

Student 5 3 8 frequency 27 5 32 Percent (%) 84.37 15.63 100.0

..
46

..

CHAPTERS

CONCLUSION

5.1

Project Summary

Requirement model is used to model out the user's requirement. The requirement model in this study can easily be understood and referred by other system developers or designers. It can be a guideline to create a real Student Attendance Monitoring System (SAMS) in secondary schools or in any related area. It is consisted of use case diagram, use case description, activity diagram, sequence diagram, collaboration diagram, and class diagram. In order to validate the requirement model, a prototype for the system has been build.

In order to define a good requirement model for Student Attendance Monitoring System for secondary school, several tasks has been followed:

47

1.

Review some theories or principles regarding software development and attendance system.

2.

Make data col1ection to get user requirements. Conduct interview with several users (staff, teachers and parents).

3.

Analyzed user requirement and demonstrate it through models. Build a prototype based on requirement model. Construct user acceptance testing to get feedback from them.

4.
5.

In this study, each chapter describes and demonstrates several tasks detailed:

Chapter one describes about background of the problem, problem statements, objectives, scopes and project importance.

Chapter two describes about literature review of software development phase, methods, tools and etc.

Chapter three describes about methodology. There are four steps to accomplish this study which is requirement elicitation, requirement analysis, requirement management and requirement verification.

Chapter four describes about finding. In this chapter, SAMS were demonstrates detailed through list of requirements, use case diagram, use case description, activity diagram, sequence diagram, collaboration diagram, class diagram and prototype.
48

a.

Problem and Limitation

During this study, the mam problem and limitation occur is Student Attendance Monitoring System (SAMS) contains many users; admin, staff, teachers, parents, and students. Therefore, there are a little bit complicated to develop and design the system.

5.3

Recommendation for Future Project

In the future, it is good to design and develop requirement model of web application which can manage whole part in schools include staff and teachers attendance, examination results, co-curriculum activity and so on.

5.4

Chapter Summary

Overall, the objective of this study has been achieved which is to study and analyze the existing attendance system in secondary schools, create a requirement model of SAMS for secondary school and design and build a prototype of SAMS.

49

REFERRENCES

Bennett, S., Skelton, J., & Lunn, K. (2001). UML: Schaums Outlines.

Bourke, C. J., Rigby, K., & Burden J. (2000). Better Practice in School Attendance: Improving the School Attendance of Indigenous Students. Commonwealth of Australia, 1-62.

Carroll, M.P., & Hawkins, C.M. (2002). Web Based Analysis. SM'02, 220-225. ACM 158113-506-8/02/0006

Christel, M.G., & Kang, K.C. (1992). Issues in Requirements Elicitation. Technical Report CMU/SEI-92-TR-012 ESC-TR-92-012.

Dennis, A., Wixom, B.H., Tegarden, D. (2005). System Analysis and design with UML Version 2.0. (2nd ed). New York: John Wiley & Sons.

Durden, G. C. & Ellis, L. V. (1995). The Effects of Attendance on Student Learning in Principles of Economics, The American Economic Review, Papers and Proceedings of the Hicker, A.M., & Davis, A.M. (2004). A Unified Model of Requirements Elicitation. Journal of Management Information Systems, 20(4), 65-84.

Hundredth and Seventh Annual Meeting of the American Economic Association Washington, 85(2), 343-346. Elmagarmid, A.K., & Mclver.W.L, Jr. (2001). The Ongoing March Toward Digital Government. IEEE Computer, 34(2), 32-38.

Epstein, J. L., & Sheldon, S. B. (2002). Present and Accounted for: Improving Student Attendance Through Family and Community Involvement. Educational Research
50

and Improvement. 95(5). 308-318.

Ervasti, M., Isomursu, M., & Kinnula, M. (2009). Bringing Technology into SchoolNFC-enabled School Attendance Supervision. ACM 978-1-60558-846-9 09

Gomaa, H. (2001). Designing Concurrent, Distributed, and Real-Time Applications with UML. Proceedings of the 23rd International Conference on Software Engineering (ICSE'OJ).

Kendall, K.E. (1992). System Analysis and Design Inc.

(zui ed). New Jersey:

Prentice-Hall,

Leidner, D. E. & Jarvenpaa S. L. (1995). The Use oflnformation

Technology to Enhance

Management School Education: A Theoretical View. MIS Quarterly: Special Issue on IS Curricula and Pedagogy, 19(3),265-291.

..

Lim, T. S., Sim, S. C. & Mansor, M. M. (2009). RFID Based Attendance System, Symposium on Industrial Electronics and Applications (ISIEA 2009), 2, 778-782.

Maletz, M., Blouin, J. G., Schnedl, H., Brisson, D., & Zamazal, K. (2007). A Holistic Approach for Integrated Requirements Modeling in the Product Development Process. The Virtual Vehicle-Research Center, Graz, Austria, 1-10.

Nunamaker, Jr., J.L., Chen, M., & Purdin, Titus, D.M. (1990). Systems Development in Information Systems Research. Journal of Management Information System, 7(3), 89106. Palmer, J. W. (2002). Web Site Usability, Design, and Performance Metrics, Information System Research, 13(2), 151-167.

51

Quatrani, T. (1999). Visual Modeling with Rational Rose 2000 and UML Addison Wesley Longman, Inc. ISBN: 0-201-69961-3.

(2"" ed.).

US:

Ray, J. (2002). Sams Teach Yourself Macromedia Dreamweaver MX Application Development in 21 Days. Pearson Education.

Richard, L. (2005). Handling Qualitative Data: A Practical Guide. Thousand Oaks, California: Sage. Romer, D. (1993). Do Students Go to Class? Should They? Journal of Economics Perspectives, 7(3), 167-174.

.. .. ..

Royce, W. W. (1970). Managing the Development of Large Software Systems. Proceedings IEEE WESCON, 1-9.

Satzinger D.W., Jackson, R.B., & Burd, S.D. (2005). Object-Oriented Analysis and Design, Thomson Course Technology.

Sekaran (2003). Research Method/or Business a Skill Building approach (4th ed). Singapore: John Wiley & Sons (Asia) Pte.Ltd.

..

Shackel, B. (984). Information Technology: A challenge to ergonomics and design . Behaviour and Information Technology, 3, 263-275.

Shendell, D. G., Prill, R., Fisk, W. J., Apte, M. G., Blake, D. & Faulkner, D. (2004). Associations between Classroom C02 Concentrations and Student Attendance in Washington and Idaho. Lawrence Berkeley National Laboratory: LBNL Paper LBNL-544 I3. Retrieved from: http://www.escholarship.orgluc/iteml88r0924r

Shumba, R. (2005). Usability of Rational Rose and Visio in a Software Engineering Course. The SIGCSE Bulletin, 37(2), 107-110. 52

lilt

..
Wayman, J. C., Stringfield, S., & Yakimowski, M. (2004). Software Enabling School Improvement Through Analysis Of Student Data. Research on the Education of Students, 67. Weske, M., Hacid, M.S., & Godart, C. (2007). Enforcing Policies and Guidelines in Web Portals: A Case Study. WISE 2007 Workshops, LNCS 4832, 154-165. Whitten, J.L., & Bentley, L.D. (1998). System Analysis and Design Methods (4th ed). USA: Irwin/McGraw Hill.

Whitten, J.L., Bentley, L.D., & Dittman, K.C. (2001). System Analysis and Design Methods (5th ed). Boston: McGraw Hill.

..
..

Woltz, C. K. (1955). Compulsary Attendance at School. Law and Comtemporary Problems, 20(1),3-22 .

53

APPENDIX A INTERVIEW QUESTIONS

Interview Question for School Management

1. How school management monitor student's attendance? 2. What are the problems faced in monitoring student attendance? 3. Is there any system used to monitor student's attendance? If yes, what kind of the system? 4. What do you think about the current system? 5. Is there any problem when using the system?
fill

6. How school management informs parents regarding their children's attendance? 7. Any suggestion?

Interview Question for Class Teachers

1. Can you explain how you handle student's attendance of your class? 2. What do you think when handling student's attendance manually? 3. Do you face any problem while handling student's attendance? 4. Do you think web based student attendance monitoring system (SAMS) is appropriate in handling student's attendance? 5. Any suggestion?
54

Interview Question for Parents

..
III

1. Do you observe your children's attendance in school? 2. How you observe your children's attendance? 3. How you inform the reason when your children absent to school? 4. What is your suggestion to overcome this problem? 5. Based on your point of view, do you think web based student attendance monitoring system (SAMS) is appropriate to ease you to view your students attendance? 6. Any suggestion?

..

ss

APPENDIXB USE CASE DESCRIPTION

1.0

USE CASE: LOGIN (SAMS_Ol)

-¥ ~ .:
/

(\
-,
"-

-,

« include »
Login Verifying

Admin, Staff, Teachers, Parents

1.1

BRIEF DESCRIPTION

This use case is initiated by admin, staff, teachers or parents. User must entered user Id and password before can access the system.

1.2

PRE-CONDITIONS

This application is opened only to all registered user who have an account only.

1.3

CHARACTERISTIC

OF ACTIVATION

Event driven (admin, staff, teachers or parents demand)

1.4 1.4.1

FLOW OF EVENTS Basic Flow (SAMS_Ol_Ol)

This use case begins when admin, staff, teachers or parents key in user Id and password. After key in, user shall click 'Submit' button. Then, the system shall verify user Id and password (E-l: Verifying). The system shall display the Student Attendance Monitoring System (SAMS) after verifying. The system shall categories the user by refer the user Id. 56

If the user entered invalid user Id or password, the system shall display error message (E-

..

2: Invalid user Id and password) .

1.4.2

Alternative Flow

Not applicable.

1.4.3

Exceptional Flow

E-1: Verifying. (SAMS_Ol_02) The system will verify user Id and password with the data in the database. E-2: Invalid user ID and password. (SAMS_Ol_03) The system will display message "Login Incorrect, Please Try Again" and login process will be unprocessed. User must entered correct user Id and password.

1.5

POST -CONDITIONS

User can access the system based on their category.

1.6

RULE(S)

User must key in valid user Id and password before can access the system.

1.7

CONSTRAINT(S)

Only users who already login can moderate their own account.

57

2.0

USE CASE: REGISTER ACCOUNT (SAMS_02)

Admin

Register Account

2.1

BRIEF DESCRIPTION

This use case is initiated only by admin. This use case will enable admin to register

account, save the registration process or clear an account registration form .

2.2

PRE-CONDITIONS

This application is opened only for admin who already sign in. Admin will register an account for admin, staff, teachers and parents.

2.3

CHARACTERISTIC

OF ACTIVATION

Event driven (admin demand)

2.4

FLOW OF EVENTS

2.4.1

Basic Flow (SAMS_02_01)

This use case begins when admin login into system to activate the user Id and password. Admin start with key in identification number of user. Once admin have filled in the form, the data can be saved in the database by clicking 'Save' registration). registration ). button (A-I: Save Admin shall clear all data when he/she click reset button (A-2: Reset

2.4.2

Alternative Flow (SAMS_02_02)

58

A-I: Save registration.

3.0

USE CASE: MANAGE PERSONAL INFORMATION

(SAMS_03)

\."-._.-)

----t/)",

evt/nd (.r=:">: ''I « 7~"~

'~'

Insert Info

<,

Admin, Staff, Teachers, Parents

~anage Personal Info

~ «in

de »l,/"-~-~,\, ;'. Update Info

3.1

BRIEF DESCRIPTION

This use case is initiated by admin, staff, teachers or parents. They can manage personal information such as insert new personal information, update, delete, save and reset.

3.2

PRE-CONDITIONS

This application is limited to registered users who already login.

3.3

CHARACTERISTIC

OF ACTIVATION

Event driven (admin, staff, teachers or parents demand)

3.4

FLOW OF EVENTS

3.4.1

Basic Flow (SAMS_03_01)

This use case begins when the admin, staff, teachers or parents click on 'Edit Information' button. The system shall display Edit Information Panel on the screen.

Then, admin, staff, teachers or parents can insert personal information (A-I: Insert personal info). Admin, staff, teachers or parents able to update personal information by click on 'Update' button (A-2: Update personal info), delete personal information by click on 'Delete' button (A-3: Delete personal info), save personal information by click on 'Save' button (A-4: Save personal info) and reset personal information by click on 'Reset' (A-5: Reset personal info).
60

III

Admin can save an account registration in the database by click on the 'Save' button.

A-2: Reset registration.

(SAMS _02_03)

Admin can reset all the information's if she/he wants to clear an account registration form.

2.4.3

Exceptional Flow

Not Applicable.

2.5

POST -CONDITIONS

An account will be created. User Id and password automatically can be used. Register user shall update their personal information.

2.6

RULE(S)

Admin can register one account for each user only.

2.7

CONSTRAINT(S)

Not applicable.

59

III

..
II

3.4.2

Alternative Flow

A-I: Insert persona) info. (SAMS_03_OI) After click on 'Edit Information' button, alumni can insert personal information such as name, user Id, password and emaiL A-2: Update personal info. (SAMS_03_02) Admin, staff, teachers or parents can update personal information when he/she have new information. A-3: Delete personal info. (SAMS_03_03) Admin, staff, teachers or parents can delete personal information when he/she needed. A-4: Save personal info. (SAMS_03_04) Admin, staff, teachers or parents can save personal information information. A-5: Reset personal info. (SAMS_03_05) after update the

..

Admin, staff, teachers or parents can reset the information if she/he wants to clear the personal information form .

3.4.3

Exceptional Flow

Not Applicable.

3.5

POST -CONDITIONS

The personal information will be updated.

3.6

RULE(S)

Not applicable.

3.7

CONSTRAINT(S)

Not applicable.

61

.. ..

4.0

USE CASE: SEARCH (SAMS _04)

Admin, staff, teachers

Search

4.1

BRIEF DESCRIPTION

This use case is initiated by admin, staff, and teachers. They can search any personal information or account.

4.2

PRE-CONDITIONS

This application is limited to admin, staff, and teachers who already login.

4.3

CHARACTERISTIC

OF ACTIVATION

Event driven (admin, staff, and teachers demand)

4.4

FLOW OF EVENTS

4.4.1

Basic Flow

Admin, staff, and teachers can search any personal information or account by click 'Search' button. Admin can search admin, staff, teachers, parents and students account or information (A-I: Admin search). Staff can search class and teachers information (A-2: Staff search). Teachers can search student and parent's information (A-3: Teachers search).

4.4.2

Alternative Flow

A-I: Admin search. (SAMS_04_02) Admin can search admin, staff, teachers, parents and student account or information, 62

A-2: Staff search. (SAMS_04_03) Staff can search class and teachers information. A-3: Teachers search. (SAMS_04_03) Teachers can search student and parent's information

4.4.3

Exceptional Flow

Not applicable.

4.5'

POST -CONDITIONS

After searching, admin, staff, and teachers can manage the personal information or account.

4.6

RULE(S)

Not applicable.

4.7

CONSTRAINT(S)

Not applicable .

..

..
63

5.0

USE CASE: REGISTER CLASS (SAMS_05)

..
Staff Register 5.1 BRIEF DESCRIPTION This use case is initiated by staff. This use case will enable them to register class.

•
•

5.2

PRE-CONDITIONS

This application is limited to staff who already sign in.

5.3

CHARACTERISTIC

OF ACTIVATION

Event driven (staff demand)

..
..

5.4

FLOW OF EVENTS

5.4.1 Basic Flow (SAMS_05_01) (SAMS_05_02) This use case begins when staff register class in the database. Then, staff should assign class to teacher, save (A-I: Save registration) registration). or reset the class registration (A-2: Reset

5.4.2

Alternative Flow (SAMS_05_03)

A-I: Save registration.

Staff can save the class registration.

..

A-2: Reset registration.

(SAMS_05_04)

Staff can reset the registration if she/he wants to clear the class registration form .
64

5.4.3

Exceptional Flow

Not applicable.

5.5

POST-CONDITIONS

Teachers can manage their personal class.

5.6

RULE(S)

Not applicable.

5.7

CONSTRAINT(S)

Not applicable .

65

III

6.0

USE CASE: GET NOTIFICATION and SEND MEMO (SAMS_06)

III

•
Staff

(~

<, ______________ __.-//

0
Send Memo

() './
/

-,

iIIIII

Get Notification

-,

Parents

6.1

BRIEF DESCRIPTION

This use case is initiated only by staff. This use case will enable to get notification and then send memo to parents.

6.2

PRE-CONDITIONS

This application is opened only for staffthat already login.

6.3

CHARACTERISTIC OF ACTIVATION

Event driven (staff demand)

..

6.4

FLOW OF EVENTS

6.4.1 Basic Flow (SAMS_06_01)

This use case begins when staff get notification. System shall send notification to staff (E-l: Notification). Then, staff can send memo to parents (A-I: Send Memo).

6.4.2 Alternative Flow A-I: Send Memo. (SAMS_06_02)

Staff ca~ send memo to parents after get the notification .

•
66

..

6.4.3 Exceptional Flow E-l: Notification. (SAMS_06_03)

System shall send notification to staff if student was absent directly three days.

6.5

POST -CONDITIONS

Parents will get memo about their children's attendance.

ill

6.6

RDLE(S)

Not applicable.

6.7

CONSTRAINT(S)

Not applicable.

67

7.0

USE CASE: REGISTER

STUDENT (SAMS_07)

(~
Teachers Register Student

7.1

BRIEF DESCRIPTION

This use case is initiated by teachers. This use case will enable teachers to register student, save student's registration process or clear student's registration form.

7.2

PRE-CONDITIONS

This application is opened only for teachers who already login.

7.3

CHARACTERISTIC

OF ACTIVATION

Event driven (teachers demand)

7.4

FLOW OF EVENTS

7.4.1

Basic Flow (SAMS_07_01)

This use case begins when teacher login into system to register student. Teacher starts the process with key in identification number of student. Once teacher have filled in the form, the data can be saved in the database by clicking 'Save' registration). registration). button (A-I: Save

Teacher shall clear all data when he/she click reset button (A-2: Reset

7.4.2

Alternative Flow (SAMS_07_02)

A-I: Save registration.

Teacher can save student's registration in the database by click on the 'Save' button.
68

..

A-2: Reset registration.

(SAMS _07_03)

Teacher can reset all the information's if she/he wants to clear an student's registration form,

7.4.3

Exceptional Flow

Not Applicable.

7.5

POST -CONDITIONS

Student's profile will be created.

7.6

RULE(S)

Teacher can register one profile for each student only.

7.7

CONSTRAlNT(S)

Not applicable.

69

..
8.0 USE CASE: MANAGE STUDENTINFORMATION (SAMS_08)
Manage Student Info «include » Update Info

Teachers and Parents

8.1

BRIEF DESCRIPTION

This use case is initiated by teachers and parents. They can manage student's information such as insert new student's information, update, delete, save and reset.

8.2

PRE-CONDITIONS

This application is limited to teachers or parents who already login.

8.3

CHARACTERISTIC OF ACTIVATION

Event driven (teachers or parents demand)

8.4

FLOW OF EVENTS

..

8.4.1 Basic Flow (SAMS_08_01)

This use case begins when teachers or parents click on 'Edit Student Information' button. The system shall display Edit Student Information Panel on the screen. Then, teachers or parents can insert student information (A-I: Insert student info). Teachers or parents able to update student information by click on 'Update' button (A-2: Update student

info), delete student information by click on 'Delete' button (A-3: Delet~student info),
save student information by click on 'Save' button (A-4: Save student info) and reset student information by click on 'Reset' (A-5: Reset student info).

70

III

8.4.2

Alternative Flow

A-I: Insert student info. (SAMS_08_01) After click on 'Edit Information' button, alumni can insert student information such as name, user Id, password and email. A-2: Update student info. (SAMS_08_02) Teachers or parents can update student information when he/she have new student information. A-3: Delete student info. (SAMS _08_03) Teachers or parents can delete student information when he/she needed. A-4: Save student info. (SAMS_08_04) Teachers or parents can save student information after update the information. A-S: Reset student info. (SAMS_08_OS) Teachers or parents can reset the information if she/he wants to clear the student information form. 8.4.3 Exceptional Flow

Not Applicable.

III

8.S

POST-CONDITIONS

The student's information will be updated.

8.6

RULE(S)

Not applicable.

8.7

CONSTRAINT(S)

Not applicable.

71

9.0

USE CASE: VIEW ATTENDANCE (SAMS_09)

,//

" T -.
,/

()
',,-

Teachers, Parents, students

View Attendance

9.1

BRIEF DESCRIPTION

This use case is initiated by teachers, parents and students. They were able to view attendance.

..
..

III

9.2

PRE-CONDITIONS

This application is limited to teachers, parents or students .

9.3

CHARACTERISTIC OF ACTIVATION

Event driven (teachers, parents or students demand)

9.4

FLOW OF EVENTS

9.4.1 Basic Flow (SAMS_09_01&02)

This use case begins when teachers, parents or student wants to view attendance. They can view daily attendance or monthly attendance.

9.4.2 Alternative Flow

Not Applicable.

9.4.3 Exceptional Flow

Not Applicable.

72

..

9.5

POST -CONDITIONS

Teachers can manage attendance and parents can monitor their children's attendance.

9.6

RULE(S)

Not applicable.

9.7

CONSTRAlNT(S)

Not applicable.

73

III

..
,

10.0

USE CASE: MANAGE ATTENDANCE (SAMS_10)

'~--""",
~.

,'----_.-/)

~~)
I

Manage Absent

-:

_/'

-. -,

Teachers or Parents Update Info

10.1

BRIEF DESCRIPTION

This use case is initiated by teachers or parents. They can manage student's attendance such as record daily attendance, list down reason and manage reason.

10.2

PRE-CONDITIONS

This application is limited to teachers or parents who already login.

10.3

CHARACTERISTIC OF ACTIVATION

Event driven (teachers or parents demand)

10.4

FLOW OF EVENTS

10.4.1 Basic Flow (SAMS_10_Ol)

This use case begins when the teachers click on 'Manage Attendance' and teacher can manage reason (A-2: Manage Reason). button. Then, teachers shall records daily attendance. Parents can list down reason (A-I: List Reason)

10.4.2 Alternative Flow A-I: List Reason. (SAMS_10_02)

Parents can list down reason why student absent to school.

A-2: Manage Reason. (SAMS_lO_03)

74

Teachers can manage reason why student absent to school.

10.4.3 Exceptional Flow Not Applicable.

10.5

POST-CONDITIONS

Student's attendance and absent reason will be updated.

10.6

RULE(S)

Not applicable.

10.7

CONSTRAINT(S)

Not applicable.

..

7S

..
11.0 USE CASE: LOGOUT (SAMS_l1)
(~~)

III

-I .: >. Admin, Staff, Teachers, Parents

,/""

"rr-"

~, (~/

Logout

11.1

BRIEF DESCRIPTION

This use case is initiated by admin, staff, teachers or parents. This use case will enable them to leave the system.

11.2

PRE-CONDITIONS

This application is limited to users who already sign in.

lilt

11.3

CHARACTERISTIC OF ACTIVATION

...

Event driven (admin, staff, teachers or parents demand)

11.4

FLOW OF EVENTS

11.4.1 Basic Flow (AS_Ol1_OI)

This use case begins when alumni or admin click on sign out button. User was able to leave the system ifhe/she wants and the system shall stop from running (E-l: Stop Run).

11.4.2 Alternative Flow

Not applicable.

11.4.3 Exceptional Flow E-l: Stop Run. (SAMS_1l_02)

System shall stop running.
76

..
11.5 POST -CONDITIONS Not applicable.

11.6

RULE(S)

Not applicable.

11.7

CONSTRAINT(S)

Not applicable.

77

12.0

USE CASE: FORUM (SAMS_12)

Admin, Staff, Teachers, Parents,

III

Forum

Students

12.1

BRIEF DESCRIPTION

This use case is initiated by admin, staff, teachers, parents or students. They can joined forum to discuss any topic.

12.2

PRE-CONDITIONS

This application is limited to registered users who already login.

12.3

CHARACTERISTIC OF ACTIVATION

Event driven (admin, staff, teachers, parents or students demand)

12.4

FLOW OF EVENTS

12.4.1 Basic Flow (SAMS_12_OI,02,05,06&07)

This use case begins when the admin, staff, teachers, parents or students register and login into forum. Then, system shall verify (E-l: Verifying) and detect invalid user Id and password (E-2: Invalid user Id and password). Admin, staff, teachers, parents or student can post topic, reply to any topic and logout from the forum. System shall stop running when users select to logout (E-3: Stop Run).

12.4.2 Alternative Flow

..

Not Applicable.
78

ill

12.4.3 Exceptional Flow E-1: Verifying. (SAMS_12_03) The system will verify user Id and password with the data in the database. E-2: Invalid user ID and password. (SAMS_12_04) The system will display message "Login Incorrect, Please Try Again" and login process will be unprocessed. User must entered correct user Id and password. E-3: Stop Run. (SAMS _12_08) System shall stop running.

1M

III

12.5

POST -CONDITIONS

Not applicable.

12.6

RULE(S)

Not applicable.

12.7

CONSTRAINT(S)

Not applicable.

79

APPENDIXC ACTIVITY DIAGRAM

ACTIVITY DIAGRAM: LOGIN, MANAGE PERSONAL INFORMATION, LOGOUT

Adrrin Stairs, Teachers, Parents

display Error

update

personal infi:J

click "delete" button

80

ACTIVITY DIAGRAM: REGISTER ACCOUNT

..

..

Yes

..
81

ACTIVITY DIAGRAM: SEARCH

Admin. Stafs. Teachers

No

82

..

ACTIVITY DIAGRAM: REGISTER CLASS

83

ACTIVITY DIAGRAM: GET NOTIFICATION AND SEND MEMO

III

II.

84

ACTIVITY DIAGRAM: REGISTER STUDENT

Teachers

Yes

..

85

ACTIVITY DIAGRAM: MANAGE STUDENT INFORMATION

Teadlers. Parents

update stude nt ilfo

delete student info

ctick "delete" button

..

ACTIVITY DIAGRAM: VIEW ATTENDANCE

Teachers. Parents. Students

86

ACTIVITY DIAGRAM: MANAGE ATTENDANCE,

MANAGE ABSENT REASON

Teach!H's

Parents

list absent reason

87

lilt