Abstract

Children’s educational applications are designed to help children in the learning process; thus, direct child involvement in elicitation process helps to achieve learning objectives. Failure in the requirements elicitation stage may lead to undefined user requirements for the application affecting the quality and usability of the developed software. Failure in requirements elicitation occurs because the user is not directly involved in the application. It is also caused by the lack of the elicitation team’s knowledge in selecting elicitation techniques that match the characteristics of users, where children have different characteristics with adults and parents. Communication in exploring the needs of users is closely related to elicitation techniques selection. Selection of elicitation techniques that are inconsistent with children’s characteristics can lead to failure in exploring the children’s needs for children educational application. The results of questionnaires and interview with the application developers show that the prototype and interview techniques are the techniques most suitable in the elicitation process involving children as respondents because these methods are suitable for the child characteristics and the short elicitation time required in the application development.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.