A 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.     

KMoS-RE: knowledge management on a strategy to requirements engineering

This paper introduces the KMoS-RE Strategy, a novel requirements engineering strategy to Informal Structured Domains. Requirements engineering aims to elicit, analyze, evaluate, consolidate, and manage the requirements of a software system. The complexity of this process depends on the application domain. In Informal Structured Domains, not all concepts and their relations are formally defined, most of the problems do not have algorithms to obtain solutions, and the domain specialists use large amounts of tacit knowledge to solve problems. These characteristics generate ambiguous, inappropriate, and incomplete requirements. It could generate an inadequate software solution, or it could be the cause of increasing the project development time. Therefore, it is important to use an appropriate requirements engineering strategy to minimize these problems. The objective of this study is to present the Knowledge Management on a Strategy to Requirements Engineering (KMoS-RE Strategy): a novel requirements engineering strategy oriented to the transformation and transference of knowledge, and with the aim to minimize the percentage of ambiguous, incomplete, and inappropriate requirements. The functionality and utility of the strategy is explained through its application to a real case study. The case study shows that using the KMoS-RE Strategy helps to internalize the domain knowledge, to clarify the solution idea, to reduce the ignorance of symmetry, to structure the domain knowledge, and to detect and correct wrong beliefs about the domain. All of these are performed in the early stage of the project development.     

A framework to integrate design knowledge reuse and requirements management in engineering design

This paper presents a framework to integrate requirements management and design knowledge reuse. The research approach begins with a literature review in design reuse and requirements management to identify appropriate methods within each domain. A framework is proposed based on the identified requirements. The framework is then demonstrated using a case study example: vacuum pump design. Requirements are presented as a component of the integrated design knowledge framework. The proposed framework enables the application of requirements management as a dynamic process, including capture, analysis and recording of requirements. It takes account of the evolving requirements and the dynamic nature of the interaction between requirements and product structure through the various stages of product development.     

Reusable knowledge in security requirements engineering: a systematic mapping study

Security is a concern that must be taken into consideration starting from the early stages of system development. Over the last two decades, researchers and engineers have developed a considerable number of methods for security requirements engineering. Some of them rely on the (re)use of security knowledge. Despite some existing surveys about security requirements engineering, there is not yet any reference for researchers and practitioners that presents in a systematic way the existing proposals, techniques, and tools related to security knowledge reuse in security requirements engineering. The aim of this paper is to fill this gap by looking into drawing a picture of the literature on knowledge and reuse in security requirements engineering. The questions we address are related to methods, techniques, modeling frameworks, and tools for and by reuse in security requirements engineering. We address these questions through a systematic mapping study. The mapping study was a literature review conducted with the goal of identifying, analyzing, and categorizing state-of-the-art research on our topic. This mapping study analyzes more than thirty approaches, covering 20 years of research in security requirements engineering. The contributions can be summarized as follows: (1) A framework was defined for analyzing and comparing the different proposals as well as categorizing future contributions related to knowledge reuse and security requirements engineering; (2) the different forms of knowledge representation and reuse were identified; and (3) previous surveys were updated. We conclude that most methods should introduce more reusable knowledge to manage security requirements.     

Giving voice to requirements engineering

Developers have plenty of reasons to avoid investing in requirements engineering: It is next to impossible to capture user needs completely, and needs are constantly evolving. The gap between software research and practice is no more evident than in the field of requirements engineering. Requirement engineering has a fairly narrow goal - determine a need and define the external behaviour of a solution - but the range of research into requirements is enormous     

A knowledge engineering approach to knowledge management

Knowledge management facilitates the capture, storage, and dissemination of knowledge using information technology. Methods for managing knowledge have become an important issue in the past few decades, and the KM community has developed a wide range of technologies and applications for both academic research and practical applications. In this paper, we propose a knowledge engineering approach (KMKE) to knowledge management. First, a knowledge modeling approach is used to organize and express various types of knowledge in a unified knowledge representation. Second, a verification mechanism is used to verify knowledge models based on the formal semantics of the knowledge representation. Third, knowledge models are classified and stored in a hierarchical ontology system. Fourth, a knowledge query language is designed to enhance the dissemination of knowledge. Finally, a knowledge update process is applied to modify the knowledge storage with respect to users’ needs. A knowledge management system for computer repair is used as an illustrative example.     

Investigating knowledge creation technology in an engineering course

The aim of the present study was to examine the technological affordances of a web-based collaborative learning technology, Knowledge Practices Environment (KPE), for supporting different dimensions of knowledge creation processes. KPE was used by engineering students in a practically oriented undergraduate engineering course. The study concentrated on students’ usage and selfreported experiences of the tool, and student-adopted strategies for spatially arranging items in KPE’s main knowledge space. According to the results, students used KPE mainly to share and organize project documentation. KPE appears to offer an advantage over traditional folder-based learning environments by providing a structured visual overview of the process and materials in the content view, thus facilitating pragmatic and epistemic dimensions of knowledge creation at the same time.     

From conceptual modelling to requirements engineering

Conceptual modelling is situated in the broader view of information systems requirements engineering. Requirements Engineering (RE) explores the objectives of different stakeholders and the activities carried out by them to meet these objectives in order to derive purposeful system requirements and therefore lead to better quality systems, i.e., systems that meet the requirements of their users. Thus RE product models use concepts for modelling these instead of concepts like data, process, events, etc., used in conceptual models. Since the former are more stable than the latter, requirements engineering manages change better. The paper gives the rationale for extending traditional conceptual models and introduces some RE product models. Furthermore, in contrast to conceptual modelling, requirements engineering lays great stress on the engineering process employed. The paper introduces some RE process models and considers their effect on tool support. This revised version was published online in June 2006 with corrections to the Cover Date.     

Polarized visible light as an aid to vegetation classification

Radiation, when reflected from the surface of the earth, can be described in terms of both its radiance and its polarization and yet remote sensing has concerned itself with the measurement of radiance and has paid little attention to the measurement of polarization. However, the use of polarization measurements in remote sensing may increase as NASA have included polarizing filters on the satellite-borne Multispectral Resource Sampler (MRS), which may be launched in the mid-1980s. Photographic measurements of percent reflected visible light (percent RVL) and percent polarised visible light (percent PVL) were taken from a light aircraft on two summer days and two winter days. The study area was a heathland with seven land cover classes. In the summer, percent RVL, percent PVL, and percent RVL plus percent PVL could discriminate four land-cover classes. In the winter percent RVL plus percent PVL could discriminate five land-cover classes, percent PVL could discriminate four land-cover classes and percent RVL could discriminate only three land-cover classes. It was concluded that measurements of percent PVL when combined with measurements of percent RVL improved vegetation discrimination in winter months.     

The transportation algorithm as an aid to chromosome classification

An algorithm is presented which obtains a constrained maximum likelihood classification of homogeneously stained chromosomes. Significantly improved results over a both context-free and a plausible context-driven classification are obtained. Extension to banded chromosomes and abnormal cells are discussed.     

Applying knowledge to reverse engineering problems

This paper summarizes a series of recent research results made at Edinburgh University based on projects that apply domain knowledge of standard shapes and relation ships to solve or improve reverse engineering problems. The problems considered are how to enforce known relationships when data fitting, how to extract features even in very noisy data, how to get better shape parameter estimates and how to infer data about unseen features.     

An MDA approach to knowledge engineering

This paper proposes an MDA approach to knowledge engineering, centered on the CommonKADS knowledge model. The latter corresponds to the CIM level of MDA whereas PRR, which represents production rules and rulesets, corresponds to the PIM level. The paper explores the mapping between CommonKADS knowledge models and production rules and rulesets based on PRR. Mapping CommonKADS knowledge models into PRR is very useful, due to the fact that the CIM level remains relatively unexplored, despite its key role in MDA. This motivates our choice to focus on the CIM and PIM levels. Furthermore, the mapping between PIM and PSM (i.e. the implementation of production rules in specific rule-based systems) constitutes less of an issue. To map CommonKADS knowledge models into PRR production rules and rulesets, we propose and illustrate a set of transformations. To ease these transformations, we start by grouping elements of the CommonKADS knowledge models into so-called “inference groups”. We propose and illustrate an algorithm that defines these inference groups automatically. The definition of transformations between models (CIM to PIM levels) requires a specific metamodel for CommonKADS as well as a dedicated metamodel for PRR. Unlike PRR, there is no published CommonKADS metamodel. This paper proposes a comprehensive CommonKADS knowledge metamodel. We describe and discuss an example, applying the whole approach.     

Relationship analysis in requirements engineering

This research addresses a major shortcoming in todays requirements analysis techniques—the lack of a rigorous and comprehensive process to explicitly capture the relationship structure of the problem domain. Whereas other analysis techniques lightly address the relationship discovery process, relationship analysis (RA) is a systematic, domain-independent analysis technique focusing exclusively on a domains relationship structure. This paper describes RAs taxonomy of relationship types and corresponding brainstorming questions for eliciting the relationship structure from a domain expert. A preliminary case study analysis of online bookstores using RA as well as a formal experiment have both confirmed RAs effectiveness in helping the analyst produce significantly higher quality requirements. RA should become an invaluable tool for analysts, irrespective of the software engineering approach taken during systems analysis.     

Triangulation as a basis for knowledge discovery in software engineering

Everyone agrees that reliable empirical “facts” must be derived from a series of investigations. However, the question of what is an appropriate framework for this series is an unresolved issue. Other articles in this issue present replication as the basis for this framework (Shull FJ, Carver JC, Vegas S, Juristo N (2008) The role of replications in Empirical Software Engineering, J Empir Softw Eng (in press)); however, alternatives exist! This brief note argues triangulation should be considered as the basis for this knowledge discovery (from empirical evaluation) strategy.