Requirement elicitation techniques for an improved case based lesson planning system

Abstract

Purpose This paper presents a recommendation on how one requirement elicitation technique supports the other techniques in defining system requirement for a case-based system. A case-based lesson planning system aims to assist teachers in constructing quality lesson plans through its cycle which begins with case retrieval. To retrieve relevant lesson plans, appropriate inputs should be used and the intended output needs to be identified via suitable requirement elicitation techniques. The use of a single technique might result in inadequate requirement specification, thus affecting the quality of the output requirements as well as quality of the final information system. Design/methodology/approach Requirement elicitation was carried out in three phases: phase I involved document review, phase II was an interview and phase III used a survey. Respondents of the study comprised experienced teachers as well as new teachers. This research used both qualitative and quantitative approaches to answer the research questions, which involved semi-structured interviews, document review and survey to collect the relevant data. Documents were reviewed by analysing lesson plans from three different countries. In addition, a review of lesson plans prepared by teachers and the standard syllabus were carried out. Findings from the document review were used in structured interviews using a teach-back technique, sorting and matrix of attribute-values. A questionnaire was then constructed based on the interviews and document review. Findings The findings of this initial study, as part of a larger research investigation, would help in knowledge modelling and representation. This will contribute to effective case retrieval via good design of the system input and output. The study identifies important elements of a lesson plan according to their ranking. Keywords that were used by teachers as input for retrieval were identified together with the expected output. Research limitations/implications The main goal of requirement elicitation is to specify complete and detailed requirements of the proposed system. There are two main types of requirement: functional and non-functional requirements. This paper only focuses on functional requirements – specifically case retrieval with appropriate input and output. Practical implications Various requirement engineering (RE) techniques can be applied in different phases of requirement elicitation. Suitable technique should be chosen at different phases of RE, as it is important for triangulation purposes. Incomplete RE will affect the modelling part of system development, and, thus, affect the design and implementation of an information system. Social implications Software engineer or anybody involved in system development should plan accordingly for the RE process. They should be creative and reasonable in selecting suitable RE techniques to be applied. Originality/value This study aims to gain understanding of the various aspects of lesson planning. Crucial knowledge in lesson planning that was gathered from the elicitation phase is modelled to have a good understanding of the problems and constraints among teachers. The findings of this initial study, as part of a larger research investigation, would help in knowledge modelling and representation. This will contribute to effective case retrieval via a good design of the system input and output.

The Performance of Teachers in the Digital Era in Improving Learning Quality

“…As a matter of fact, the lesson plan was still very conventional where it does not use online media for learning materials and learning tools so it can be easily accessible by learners. Teachers need to spend a lot of time in preparing the lesson plan because lesson plans need to be adjusted with the teacher's situation, for example the students profile and the facilities owned by the teachers (Saad & Dawson, 2018). Lesson planning includes role play of characters to understand more learning approaches (Bestwick, 2017), therefore lesson planning must be discussed together in a group discussion of the subject teachers (Chichibu, 2016).…”

Strategic Information System for Decision Making in Railway Supply Chain Management

“…The industry needs four (4) strategic shifts in their organization for reliable IS that deliver a consistent and predictable IS experience. IS function needs to provide an actionable guide to helping strategy turn into successful execution [21]. Moreover, it needs to enhance industry processes and upgrade the industry value chain that creates a good decision-making process.…”

Selection of Requirement Elicitation Techniques: A Neural Network based Approach

“…; requirements elicitation [1] [2]. Requirement elicitation provides a base for a RE, has a strong impact on the software project success and quality [3]. The first stage in requirement engineering is requirement elicitation that uses various techniques to elicit requirements related to software project from various stakeholders.…”

“…Requirement Elicitation can be considered as a prerequisite for all other software development activities. It signifies that the developed software product is of good quality and will work properly according to the expectation [3]. The success and failure of the project is dependent on the quality of requirements that are gathered.…”