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 PETLON Algorithm to Plan Efficiently for Task-Level-Optimal Navigation