We use a few cookies

Essential cookies keep the library working. With your permission, we'd also like to use analytics to see what's useful and improve the experience. Read our Privacy Policy or Cookie Policy.

Skip to main content
Home/e-Resources/Mathematics/Identifikasi Kebutuhan Pengguna Untuk Aplikasi Permainan Edukasi Bagi Anak Usia 4 sampai 6 Tahun
PeriodicalsMathematics

Identifikasi Kebutuhan Pengguna Untuk Aplikasi Permainan Edukasi Bagi Anak Usia 4 sampai 6 Tahun

Checking your access to this record.

Abstract & Overview

User requirement identification is the most important initial phase in developing an eductional game application. At this stage will be formulated characteristics, abilities, and users interest to an application. Targeted users for the game application that will be developed are preschool chidren range from 4 to 6 years. User requirement identification process involves 52 respondents that consists of parents,teachers, and children. Interview, observation, and questionaire are used as a method for data collection. This research produce the characteristics definition of an educational application and basic capabilities for children from 4 to 6 years. Keywords: Educational Game for Children, User Requirement Identification, Children and Computer Game.

Cite this record

Rosa Delima, Nevi Kurnia Arianti, Brasmati Pramudyawardani (2015). Identifikasi Kebutuhan Pengguna Untuk Aplikasi Permainan Edukasi Bagi Anak Usia 4 sampai 6 Tahun. Jurnal Teknik Informatika dan Sistem Informasi, 1(1), 134391. https://doi.org/10.28932/jutisi.v1i1.360

Copy in another style

Delima, R., Arianti, N. K., & Pramudyawardani, B. (2015). Identifikasi Kebutuhan Pengguna Untuk Aplikasi Permainan Edukasi Bagi Anak Usia 4 sampai 6 Tahun. Jurnal Teknik Informatika dan Sistem Informasi, 1(1), 134391. https://doi.org/10.28932/jutisi.v1i1.360
Author names are used as deposited, so check their order before you submit.

Metadata is harvested from open-access indexes and can be incomplete. Check a citation against the published version before relying on it — see our open access & attribution policy.