The classification of requirements engineering methods

Bickerton, M.J.; Siddiqi, Jawed I. A.

doi:10.1109/isre.1993.324819

Cited by 22 publications

(16 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In fact, using more RE techniques might even delay the software project and possibly even lead to project failure. Examples of project failures due to inappropriate use of RE techniques can be found in [25]. The key point is to use those techniques that satisfy the constraints of the project and contribute to the overall quality of the requirements at the same time.…”

Section: Observations and Discussionmentioning

confidence: 99%

“…An interesting discussion related to the misuse of RE techniques can be found in [25]. • The Fuzzy Clustering algorithm is limited in its capabilities as it is based on a mathematical model and therefore is in some respect inflexible and rigid.…”

Section: Techniques Clusteringmentioning

confidence: 99%

“…Hickey and Davis [23,24] proposed a finegrained selection model that helps understand the elicitation process and the selection of elicitation techniques. Bickerton and Siddiqi [25] proposed a framework for the classification of RE techniques built on the social assumptions made about organizations. Based on the identified needs for RE techniques that support the RE process, human communication, knowledge development, documentation and management, Macaulay [12] proposes a wish-list for RE techniques with the aim of identifying what kind of techniques are needed.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A methodology for the selection of requirements engineering techniques

et al. 2007

View full text Add to dashboard Cite

The complexity of software projects as well as the multidisciplinary nature of requirements engineering (RE) requires developers to carefully select RE techniques and practices during software development. Nevertheless, the selection of RE techniques is usually based on personal preference or existing company practice rather than on characteristics of the project at hand. Furthermore, there is a lack of guidance on which techniques are suitable for a certain project context. So far, only a limited amount of research has been done regarding the selection of RE techniques based on the attributes of the project under development. The few approaches that currently exist for the selection of RE techniques provide only little guidance for the actual selection process. We believe that the evaluation of RE techniques in the context of an application domain and a specific project is of great importance. This paper describes a Methodology for Requirements Engineering Techniques Selection (MRETS) as an approach that helps requirements engineers select suitable RE techniques for the project at hand. The Communicated by Professor Roel J. Wieringa. MRETS has three aspects: Firstly, it aids requirements engineers in establishing a link between the attributes of the project and the attributes of RE techniques. Secondly, based on the evaluation schema proposed in our research, MRETS provides an opportunity to analyze RE techniques in detail using clustering. Thirdly, the objective function used in our approach provides an effective decision support mechanism for the selection of RE techniques. This paper makes contributions to RE techniques analysis, the application of RE techniques in practice, RE research, and software engineering in general. The application of the proposed methodology to an industrial project provides preliminary information on the effectiveness of MRETS for the selection of RE techniques.

show abstract

Section: Observations and Discussionmentioning

confidence: 99%

Section: Techniques Clusteringmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A methodology for the selection of requirements engineering techniques

et al. 2007

View full text Add to dashboard Cite

show abstract

“…This has lead to problems in engineering research and practice, most notably in Requirements Engineering (Bickerton & Siddiqi (1993)), and resulted in new departures during the 1990"s in modelling domains and other social dimensions of advanced technology development (for example Goguen (1993), Goguen & Linde (1993)). …”

Section: Empirical Evidence For the Ontological Incompleteness Of Thementioning

confidence: 99%

“…Functional Rationalism is a term coined in the literature to describe positivist influences in much information systems engineering theory and practise (Bickerton & Siddiqi (1993)). Most systems methodologies are based upon functionally rationalist premises.…”

Section: Introductionmentioning

confidence: 99%

Examining Non-Representation in Engineering Notations Empirical Evidence for the Ontological Incompleteness of the Functionally-Rational Modelling Paradigm

Stapleton

Murphy

2002

IFAC Proceedings Volumes

View full text Add to dashboard Cite

The assumption that functionally rational notations can represent organisational spaces is central to engineering diagrammatical approaches in the delivery of advanced technology. This is reflected in a approach to notations which assumes objective, rationalistic ontologies. This paper opens the debate on research into notations and their relationship to sound method and socio-technical issues, suggesting that researchers need to rethink the ways in which the world is represented in engineering documentation, especially Requirements Engineering and Business Process Re-Engineering (BPRE). Empirical data from 9 companies and 48 people involved in manufacturing systems projects is presented which provides evidence for this position.

show abstract

Theories of meaning and different perspectives on information systems

Holm

Karlgren

1995

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

Even though automated information systems have been used in work life for almost three decades, the academic discipline of information systems development is still in a 'preparadigmatic phase'. There is no central corpus of a well understood and accepted theory of how these artifacts should be understood and designed. What we see is a set of scattered methods and theories, with influences from a wide variety of other disciplines, such as logic, linguistics, philosophy, cognitive psychology, organizational theory, ethnography, etc. There is a practical need for creating an overview and a deeper understanding of how different theories and methods are related to each other, what their relative strengths and weaknesses are and when they are applicable.In this paper we will present such an overview, based on a discussion about different theories of meaning. A framework is presented that divides the usage context of an information system into three areas of interest: referential aspects, individual aspects, and social aspects. Different theories elaborate on these aspects in different ways and to different degrees. There are strong analogies between these theories and philosophical theories of meaning that elaborate on corresponding aspects. To bring out these analogies we discuss the strengths and weaknesses of a set of approaches: (1) the traditional mainstream focus on referential aspects, (2) the adoption of cognitive theories in the information systems field, (3) structured theories about the social and communicative usage of information systems, e.g., theories based on the speech act theory, and (4) 'usage holism' and the criticisms of the role of abstract, theoretical modeling and analysis during information systems development. The paper does not present a final solution to the problems we address. Rather, it should be read as a contribution to what we believe must be an ongoing debate and a long term reflection on the theoretical foundation of information systems-research.

show abstract

The classification of requirements engineering methods

Cited by 22 publications

References 15 publications

A methodology for the selection of requirements engineering techniques

A methodology for the selection of requirements engineering techniques

Examining Non-Representation in Engineering Notations Empirical Evidence for the Ontological Incompleteness of the Functionally-Rational Modelling Paradigm

Theories of meaning and different perspectives on information systems

Contact Info

Product

Resources

About