ELICA: An Automated Tool for Dynamic Extraction of Requirements Relevant Information

Requirements elicitation requires extensive knowledge and deep understanding of the problem domain where the final system will be situated. However, in many software development projects, analysts are required to elicit the requirements from an unfamiliar domain, which often causes communication barriers between analysts and stakeholders. In this paper, we propose a requirements ELICitation Aid tool (ELICA) to help analysts better understand the target application domain by dynamic extraction and labeling of requirements-relevant knowledge. To extract the relevant terms, we leverage the flexibility and power of Weighted Finite State Transducers (WFSTs) in dynamic modeling of natural language processing tasks. In addition to the information conveyed through text, ELICA captures and processes non-linguistic information about the intention of speakers such as their confidence level, analytical tone, and emotions. The extracted information is made available to the analysts as a set of labeled snippets with highlighted relevant terms which can also be exported as an artifact of the Requirements Engineering (RE) process. The application and usefulness of ELICA are demonstrated through a case study. This study shows how pre-existing relevant information about the application domain and the information captured during an elicitation meeting, such as the conversation and stakeholders' intentions, can be captured and used to support analysts achieving their tasks.Comment: 2018 IEEE 26th International Requirements Engineering Conference Workshop

Embedding Requirements within the Model Driven Architecture

The Model Driven Architecture (MDA) brings benefits to software development, among them the potential for connecting software models with the business domain. This paper focuses on the upstream or Computation Independent Model (CIM) phase of the MDA. Our contention is that, whilst there are many models and notations available within the CIM Phase, those that are currently popular and supported by the Object Management Group (OMG), may not be the most useful notations for business analysts nor sufficient to fully support software requirements and specification. Therefore, with specific emphasis on the value of the Business Process Modelling Notation (BPMN) for business analysts, this paper provides an example of a typical CIM approach before describing an approach which incorporates specific requirements techniques. A framework extension to the MDA is then introduced; which embeds requirements and specification within the CIM, thus further enhancing the utility of MDA by providing a more complete method for business analysis

Effective communication in requirements elicitation: A comparison of methodologies

The elicitation or communication of user requirements comprises an early and critical but highly error-prone stage in system development. Socially oriented methodologies provide more support for user involvement in design than the rigidity of more traditional methods, facilitating the degree of user-designer communication and the 'capture' of requirements. A more emergent and collaborative view of requirements elicitation and communication is required to encompass the user, contextual and organisational factors. From this accompanying literature in communication issues in requirements elicitation, a four-dimensional framework is outlined and used to appraise comparatively four different methodologies seeking to promote a closer working relationship between users and designers. The facilitation of communication between users and designers is subject to discussion of the ways in which communicative activities can be 'optimised' for successful requirements gathering, by making recommendations based on the four dimensions to provide fruitful considerations for system designers

The Influence of Analyst Communication in IS Projects

Information system (IS) researchers have long noted that IS analysts need to understand users’ needs if they are to design better systems and improve project outcomes. While researchers agree that analyst communication activities are an important prerequisite for such an understanding, little is known about the nature of different communication behaviors IS analysts can undertake to learn about users’ system needs and the impact of such behaviors on IS projects. To address this gap, this paper draws from the learning literature to articulate the information transmission activities IS analysts can undertake and the content of the information they can transmit when learning about users’ organizational tasks and information needs. The influence of analyst communication activities on the generation of valid information regarding user needs, analyst learning, and IS project outcomes are then investigated via a case study of two IS projects. The analysis of the two cases suggests that analysts who encourage the use of concrete examples, testing, and validation, and who solicit feedback about users’ business processes are likely to better understand users’ tasks, and in turn design systems that better meet users’ task needs than analysts who do not

Using protocol analysis to explore the creative requirements engineering process

Protocol analysis is an empirical method applied by researchers in cognitive psychology and behavioural analysis. Protocol analysis can be used to collect, document and analyse thought processes by an individual problem solver. In general, research subjects are asked to think aloud when performing a given task. Their verbal reports are transcribed and represent a sequence of their thoughts and cognitive activities. These verbal reports are analysed to identify relevant segments of cognitive behaviours by the research subjects. The analysis results may be cross-examined (or validated through retrospective interviews with the research subjects). This paper offers a critical analysis of this research method, its approaches to data collection and analysis, strengths and limitations, and discusses its use in information systems research. The aim is to explore the use of protocol analysis in studying the creative requirements engineering process.<br /

From Rich User Requirements to System Requirements

In recent years the usage of information systems has changed dramatically. Today many information systems are developed for non-organizational users. These wide-area end-users are often socially, as well as geographically very widely dispersed, which makes it for organizations that develop information systems extremely difficult to know who their users are, or what they expect. Previous research has claimed that rich user requirements information is necessary, in order to understand how to serve this audience right. However, at the same time current requirements engineering methods, capable of providing this rich information, do not serve the needs of designers and developers, who actually implement the services and who need precise knowledge of system requirements. It appears that there is a severe gap in the communication of requirements between end-user, analyst, and designer. We have the design science research agenda to develop a method for extending one advanced requirements engineering method, WARE, to provide support for the full spectrum of communication. Our study presents results of ongoing research program, studying the innovation possibilities of Mobile Presence technology. Our method enables analysts to make the transition from rich user requirements to system requirements, which designers and developers can use in their implementation work

APPLICATION OF ACTIVITY THEORY TO ELICITATION OF USER REQUIREMENTS FOR A COMPUTERIZED CLINICAL PRACTICE GUIDELINE: THE ACTCPG CONCEPTUAL FRAMEWORK

Clinical practice guidelines are knowledge uptake instrument that support decision making by the physicians. They are often implemented as computer-interpreted guidelines that are embedded in a hospital information system. We argue that computer-interpreted guidelines should be considered as regular information system, thus their development should follow all the steps of system analysis and design, starting with exploration and definition of user requirements. In this paper we propose the ActCPG conceptual framework to establish basic user requirements for implementing computer-interpreted guidelines. This framework relies on the Activity Theory to structure and decompose information coming from a clinical practice guideline and associated narrative so UML use cases can be developed. We illustrate operation of the ActCPG framework with an example of a practice guideline for a management of clinically obese children enrolled in some obesity program

Design, implementation, and evaluation of an ICT-supported collaboration methodology for distributed requirements determination

As information systems development becomes more distributed, information and communication technology (ICT) has become crucial to overcome distance and to enable collaboration between system users and analysts. This study presents the design, implementation, and experimental evaluation of a new technology-supported collaborative methodology for requirements determination. The new ICT-supported methodology enables the elicitation, analysis, specification, and validation of requirements in a distributed environment. Its design follows the theoretical principles of Te’eni’s (2001) cognitiveaffective model of organizational communication for IT design and combines established methods as well as techniques for requirements identification, formulation, dependency determination, prioritization, and selection in a coherent and innovative way. The resulting prototype is professionally implemented and evaluated in an experiment. The experiment is the first to compare the performance of traditional ways of communication via interviews and document exchange with that of communication via an Internet-based collaboration platform for requirements determination. The results show that, both, the efficiency of the overall requirements determination process as well as the overall quality of the resulting requirements, are higher when using the new collaborative methodology. In terms of quality, efficiency, the user and analyst perspectives need to be distinguished. While the effort for requirements elicitation increases for the analysts, this up-front investment pays off in terms of significantly lower effort for the later specification and validation of requirements. In contrast, the users benefit in particular from lower effort during requirements elicitation and analysis