Software requirements engineering produces several different artifacts. In order to cope with all requirements contained in these artifacts, they must be kept in a single place. Today, usually this place is a document or a simple list of requirement statements. A modelling infrastructure for the integration of requirements in models is a new way of keeping and managing requirements in a model-c...

Requirements elicitation is the most critical phase in software development as it captures the required functionality of a software system. The elicitation process is indeed resource intensive. It involves a number of dedicated stakeholders who are deliberately gathered to confer and stipulate software requirements. The effectiveness of the process is greatly influenced by the credibility and s...

Preliminary communication Effective requirements management that embraces both explicit and implicit aspects is a prerequisite for successful software development. Although different researchers and practitioners have identified the importance of implicit requirements (IMR) for overall successful outcome of software development, there is a need to correlate these theoretical assumptions about i...

Requirements elicitation is a complex process that requires stakeholders in teams to collaborate, go through decision-making processes to arrive at consensus. During the requirements elicitation processes, stakeholders who have different backgrounds, view points and understandings, need to clarify, capture and uncover user/client requirements in an efficient and effective manner. However, there...

Requirements elicitation is a critical phase in information systems development (ISD), having significant impacts on software quality and costs. Prior research suggests that it is a collaborative activity, where system requirements-related knowledge is extensively shared between users and analysts. This knowledge sharing can get extremely tenuous given the different knowledge perspectives of th...

A method for scenario based requirements engineering is described. The method uses two types of scenario, structure models of the system context and scripts of system usage. A modelling language is reported for describing scenarios, and heuristics are given to cross check dependencies between scenario models and the requirements specification. Heuristics are grouped into several analytic treatm...

Requirements engineering is the critical phase of the software engineering process, where complex, heterogeneous human needs, together with environmental constraints have to be captured and translated into system requirements. In this paper we recall the concept of normative environment, discuss the problems and challenges related to the requirements analysis in this kind of environments and pr...

This paper describes our experience in capturing, using a formal specification language, a model of the knowledge-intensive domain of oceanic air traffic control. This model is intended to form part of the requirements specification for a decision support system for air traffic controllers. We give an overview of the methods we used in analysing the scope of the domain, choosing an appropriate ...

Context: Learning can be regarded as knowledge construction in which prior knowledge and experience serve as basis for the learners to expand their knowledge base. Such a process of knowledge construction has to take place continuously in order to enhance the learners’ competence in a competitive working environment. As the information consumers, the individual users demand personalised informa...

Requirements elicitation is a complex process that requires stakeholders in teams to collaborate, go through decision-making processes to arrive at consensus. During the requirements elicitation processes, stakeholders who have different backgrounds, view points and understandings, need to clarify, capture and uncover user/client requirements in an efficient and effective manner. However, there...