Framework for understanding creativity in requirements engineering

Creativity is important in the discovery and analysis of user and business requirements to achieve innovative uses of information and communication technologies. This paper builds a theoretical framework for understanding creativity in requirements engineering. The framework provides a systematic means of understanding creativity in requirements engineering and comprises five elements (product, process, domain, people and socio-organisational context). The framework provides researchers with a sound basis for exploring how the five elements of creativity can be incorporated within RE methods and techniques to support creative requirements engineering. It provides practitioners with a systematic means of creating environments that nurture and develop creative people, cognitive and collaborative processes and products.

Exploring the influences on requirements engineering during global software development

Through an interpretive study of global virtual teams, this research has explored the influences on the requirements engineering processes during global software development. Complex layers of explicit and implicit elements in the project environment, including systems methodology, project steering, management commitment and cultural differences, were found to influence these processes.

Critical success factors for the requirements engineering process, with reference to quality management of information systems development

Preliminary research into the critical factors associated with software development/implementation identified three dimensions for successful implementation based on alignment of the requirements engineering process with business needs, change management process and quality of the implementation process. Research results demonstrate the link between the conceptual model for process quality and the process management attributes determined during the research.

A framework for understanding collaborative creativity in requirements engineering: Empirical validation

Requirements engineering (RE) often needs creativity in a form where interactions among stakeholders are particularly important: collaborative creativity. However, few studies have explicitly concentrated on understanding collaborative creativity in RE, resulting in a lack of well-founded advice for practitioners on how to support this aspect of RE. Through an online survey, this paper seeks empirical validation for a framework of factors characterising collaborative creative processes in RE. Within the limits of the validity of the study, the results show support for the utility of the framework: collaborative creativity seems to be a linear function of the mean score to all factors in the framework. Factors can be grouped, and the specific impact of each group on collaboration, value and novelty can be assessed.

Collaborative creativity in requirements engineering: analysis and practical advice

Requirements engineering (RE) often entails interdisciplinary groups of people working together to find novel and valuable solutions to a complex design problem. In such situations RE requires creativity in a form where interactions among stakeholders are particularly important: collaborative creativity. However, few studies have explicitly concentrated on understanding collaborative creativity in RE, resulting in limited advice for practitioners on how to support this aspect of RE. This paper provides a framework of factors characterising collaborative creative processes in RE. These factors enable a systematic investigation of the collaboratively creative nature of RE. They can potentially guide practitioners when facilitating RE efforts, and also provide researchers with ideas on where to focus when developing methods and tools for RE. © 2013 IEEE.

KBRE: a framework for knowledge-based requirements engineering

Detecting inconsistencies is a critical part of requirements engineering (RE) and has been a topic of interest for several decades. Domain knowledge and semantics of requirements not only play important roles in elaborating requirements but are also a crucial way to detect conflicts among them. In this paper, we present a novel knowledge-based RE framework (KBRE) in which domain knowledge and semantics of requirements are central to elaboration, structuring, and management of captured requirements. Moreover, we also show how they facilitate the identification of requirements inconsistencies and other-related problems. In our KBRE model, description logic (DL) is used as the fundamental logical system for requirements analysis and reasoning. In addition, the application of DL in the form of Manchester OWL Syntax brings simplicity to the formalization of requirements while preserving sufficient expressive power. A tool has been developed and applied to an industrial use case to validate our approach.

A pair-oriented requirements engineering approach for analysing multi-lingual requirements

Requirements written in multiple languages can lead to error-proneness, inconsistency and incorrectness. In a Malaysian setting, software engineers are exposed to both Malay and English requirements. This can be a challenging task for them especially when capturing and analyzing requirements. Further, they face difficulties to model requirements using semi-formal or formal models. This paper introduces a new approach, Pair-Oriented Requirements Engineering (PORE) that uses an Essential Use Case (EUC) model to capture and analyze multi-lingual requirements. This approach is intended to assist practitioners in developing correct and consistent requirements as well as developing teamwork skills. Two quasi-experiment studies involving 80 participants in the first study and 38 participants in a subsequent study were conducted to evaluate the effectiveness of this approach with respect to correctness and time spent in capturing multi-lingual requirements. It was found that PORE improves accuracy and hence helps users perform better in developing high quality requirements models.

Integrating goal-oriented and use case-based requirements engineering: the missing link

Combining goal-oriented and use case modeling has been shown as an effective method of requirements engineering. To ensure the quality of such modeled artifacts, a conceptual foundation is needed to govern the process of determining what types of artifacts to be modeled, and how they should be specified and analyzed for 3Cs problems (completeness, consistency and correctness). However, such a foundation is missing in current goal-use case integration approaches. In this paper, we present GUIMeta, a meta-model, to address this problem. GUIMeta consists of three layers. The artifact layer defines the semantics and classification of artifacts and their relationships. The specification layer offers specification rules for each artifact class. The ontology layer allows semantics to be integrated into the entire model. Our promising evaluation shows the suitability of GUIMeta in modeling goals and use cases.

An automated collaborative requirements engineering tool for better validation of requirements

This demo introduces an automated collaborative requirements engineering tool, called TestMEReq, which is used to promote effective communication and collaboration between client-stakeholders and requirements engineers for better requirements validation. Our tool is augmented with real time communication and collaboration support to allow multiple stakeholders to collaboratively validate the same set of requirements. We have conducted a user study focusing on validating requirements using TestMEReq with a few groups of requirements engineers and client stakeholders. The study shows that our automated tool support is able to assist requirements engineers to effectively communicate with client-stakeholders to better validate the requirements virtually in real time. (Demo video: https://www.youtube.com/watch?v=7sWLOx-N4Jo).

Conceptualising the requirements of CRM from an organisational perspective : a review of the literature

For an organisation to undertake a Customer Relationship Management (CRM) implementation program it needs to consider a multitude of requirements. Some authors have hinted at viewing CRM within a wider perspective than just  customer centric perspectives. The aim of this paper is to discuss the domain and conceptualise some of the requirements of CRM from an organisation’s point of view. However, CRM needs to be identified as the whole organisation, including its internal and external environments. Undertaking CRM in any organisation needs to be preceded by a sequence of stages. An organization needs to develop a roadmap outlining the path to become CRM centric. Therefore an organisation should address, or at least consider, a list of those factors at every stage of a CRM implementation program, for an implementation program to be effective. The main focus of literature in CRM has been customer centric. This paper, being the first stage of much wider research, will focus on the organisation and the internal environment. This paper will identify three information systems (IS) and information technology (IT) requirements in organisations that are integral parts of CRM. These need to achieve a level of synergy for successful CRM. To understand these three requirements (front-end systems, back-end systems, and datahandling technologies) in a CRM project is too great in magnitude at this early stage of the research. This paper begins to draw together the tenuous links between the three requirements of information systems (IS) and information technology (IT) systems. Writing this paper and shifting its focus towards requirements engineering, the author has realised that a whole area of literature has to be explored, because CRM is another IS implementation.