Pohl, K. (1994), "Three dimensions of requirements engineering: A framework and its application", Information Systems, vol. 19(3):pp. 243--258.  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... this result conflicts with the academic literature in RE, for example see the major textbooks [42, 43, 24] Not only does the textbook literature describe the RE process as smoothly evolutionary in a cumulative manner, but the research literature (even, for example the often cited work by Pohl [37] which forms the foundation for the RE process) also focuses on a generally incremental model. It is important to note that there are a number of studies into the opportunism in design including general design and RE (for example, 48, 49, 8, 16, 17, 23, 4] These studies cast considerable doubt ....

Pohl, K. (1994) Three Dimensions of Requirements Engineering: framework and its application, Information Systems 19(3):243-258.

....also influenced by the different knowledge background, and the different interests of the modelers. In other words, viewpoint resolution must happen in all three dimensions of requirements engineering: representation (notations) specification (domain understanding) and agreement (negotiation) [Pohl, 1994]. To indicate how this can be supported by a repository, the left of the figure relates the picture to the levels of the ISO Information Resource Dictionary Standard [ISO IEC, 1990] In IRDS, the concepts on level n l (the defining level) constitute a type system for level n (the defined level) ....

K. Pohl. The Three Dimensions of Requirements Engineering: a Framework and its applications. Information Systems 19, 3 (1994), pp. 243 - 258.

....such as those used in electronic markets. What does our work add to previous related efforts Commitment Identification: Existing MAS coordination approaches [37] 38] 39] agent software engineering methodologies [40] 41] 42] 43] and software requirements capture methodologies in general [44] [45] all discuss the notions of roles and commitments. Our work differs in that it requires a superset of the inter agent requirements typically considered by these approaches, to enable greater completeness in commitment identification. Our approach considers, for example, idealized commitments ....

Pohl, K., The Three Dimensions of Requirements Engineering: A Framework and its Applications. Information Systems, 1994. 19(4): p. 234-248.

....frameworks of requirements and requirement engineering have been proposed, with the intention of capturing the basic products, agents, and relationships that are involved in the requirement engineering process. In this research area, we point out the proposals of Lindland et al. 16] and of Pohl [23], that have been further merged and refined by Krogstie et al. 14] On the other hand, several specific natural language processing (NLP) techniques have been tailored to the purpose of analyzing and controlling software requirements [3, 9, 17, 18, 21, 24] Techniques of different kinds have ....

....for being applied to classify a number of techniques, tools, and practices proposed in the literature. 4 The top down way Until recently, no systematic approach has been proposed for the analysis of quality properties of requirements specifications. The proposals of Lindland et al. 16] and Pohl [23], further merged and refined by Krogstie et al. 14] are recent attempts towards a systematic analysis of the quality issues. It is worth noting that a distinguishing feature of the framework by Krogstie et al. is that it can be closely linked to linguistic concepts. This is the main motivation ....

K. Pohl. The three dimensions of requirements engineering: a framework and its applications. Information Systems, 19(3):243--258, 1994.

....frameworks of requirements and requirements engineering have been proposed, with the intention of capturing the basic products, agents, and relationships that are involved in the requirements engineering process. In this research area, we point out the proposals of Lindland et al. 6] and of Pohl [11], that have been further merged and refined by Krogstie et al. 5] It is worth noting that a distinguishing feature of the last framework is that it can be closely linked to linguistic concepts. Knowledge Participant Domain appropriateness Req. Doc. syntactic quality semantic quality ....

K. Pohl. The three dimensions of requirements engineering: a framework and its applications. Information Systems, 19(3):243--258, 1994.

....a model: Mathematics, logic . Programming languages . Physical materials (e.g. for wind tunnel models) Graphical symbology . Human language Languages can be informal (e.g. human language) semi formal (e.g. graphical languages such as flow charts) or formal (e.g. mathematics) [5]. Real life phenomena are or occur within systems. Nadler [3] states that everything is a system and defines a system as: A system processes inputs into outputs that achieve and satisfy a purpose or purposes through the use of human, physical, and information resources in a sociological and ....

....in the language L. Participant knowledge appropriateness: all statements in the meta model of the language are part of the explicit knowledge of the actor. Krogstie, Lindland, Sindre [24] The second work of Krogstie, et al. combines and extends the work of Lindland et al. 17] and Pohl [5]. Purpose Understanding quality of conceptual models used in requirements engineering Type Framework Focus Theory Measures Metrics Symbolic metrics; goals and means Foundation Social construction theory Pohl examines the requirements engineering process and does not address either data ....

Pohl, K., The Three Dimensions of Requirements Engineering: A Framework and Its Applications. Information Systems, 19, 3, (1994), pp. 243-258.

....conceptual modelling, quality, process heuristics 1 Introduction Previously propositions of quality goals for requirements specifications or conceptual models have included many useful aspects, but unfortunately in an unsystematic form. Two recent frameworks by Lindland et al. and Pohl [18, 20] have attempted to take a more structured approach to understanding this area. Still, both these need more development before they can result in concrete guidelines for requirements specification. Comparisons between the Lindland framework and the work of Pohl and of the FRISCO task group [17] on ....

K. Pohl. The three dimensions of requirements engineering: A framework and its applications. Information Systems, 19(3):243--258, April 1994.

....in order to validate the scenarios and refine the specifications. 3. 1 Classification of Scenarios in Requirements Engineering The requirements engineering process involves aspects of concern along three dimensions, namely the representation, cognitive or semantic and social or pragmatic [23]. According to the focus and starting point of a scenario, it could be classified along these three dimensions. Scenarios used in requirements engineering exhibit different properties along each dimension, as summarised in figure 4. Pragmatic Dimension Semantic Dimension Explanatory Domain ....

Pohl K., The three dimensions of requirements engineering: A Framework and its applications, Information systems Vol. 19, No. 3, pp. 243-258, 1994

....frameworks of requirements and requirement engineering have been proposed, with the intention of capturing the basic products, agents, and relationships that are involved in the requirement engineering process. In this research area, we point out the proposals of Lindland et al. 16] and of Pohl [23], that have been further merged and re ned by Krogstie et al. 14] On the other hand, several speci c natural language processing (NLP) techniques have been tailored to the purpose of analyzing and controlling software requirements [3, 9, 17, 18, 21, 24] Techniques of di erent kinds have been ....

....for being applied to classify a number of techniques, tools, and practices proposed in the literature. 4 The top down way Until recently, no systematic approach has been proposed for the analysis of quality properties of requirements speci cations. The proposals of Lindland et al. 16] and Pohl [23], further merged and re ned by Krogstie et al. 14] are recent attempts towards a systematic analysis of the quality issues. It is worth noting that a distinguishing feature of the framework by Krogstie et al. is that it can be closely linked to linguistic concepts. This is the main motivation ....

K. Pohl. The three dimensions of requirements engineering: a framework and its applications. Information Systems, 19(3):243-258, 1994.

....of [Ramesh93b] and [Gotel94] indicate that requirements pre traceability is at least as important as requirements post traceability ; especially for systems which are embedded in a constantly changing environment. An interesting framework for requirements pre traceability was provided by Pohl [Pohl94a] which described the requirements engineering process in a three dimensional space (see Figure 7) The framework assumes that there are three major facets of the RE process, namely modelling the requirements in a more complete manner, modelling with more formality, and more consensus among ....

: Pohl, K., "The Three Dimensions of Requirements Engineering: a framework and its application", Information Systems Vol 19, N 3, pp 243-258, 1994.

....services are expressed as restrictions on how to update the database. This simple formalization thus was a prerequisite of the re integation of syntactical, graphical, and semantic aspects of meta modeling, as discussed in section 2. below. 1. 2 Three Basic Modeling Methodologies As observed in [Poh94] modeling processes proceed along three dimensions: representational transformation, domain knowledge acquisition, and stake 1 ConceptBase has been developed since 1988 and been applied in numerous modeling projects around the world. The current version of the system can be obtained from the ....

K. Pohl. The three dimensions of requirements engineering: A framework and its application. Information Systems, 19(3), 1994.

....position used by an individual when examining a universe of discourse. Similar to us, they advocate a viewpoint resolution approach but do not consider explicitly the case of a very high number of viewpoints. The work by [Maiden95] does elaborate viewpoints along the three dimensions proposed by [Pohl94], together with some proposals for computational mechanisms supporting resolution. But the implicit assumption of that work is a small number of viewpoints to be reconciled, and no design guidelines for what views to choose are given. ViewPoints [Nuseibeh94] start from the premise that complex ....

Pohl K.: The three dimensions of requirements engineering: a framework and its application; Information Systems, 19(3), 1994.

No context found.

Pohl, K.: "The Three Dimensions of Requirements Engineering: A Framework and its Applications", Information Systems, June 1994

....used the imperative language C for defining such contexts since C offers more suitable constructs. Step 2 Definition of Method Guidance in the Process Model: The product model underlying the PRIME CREWS environment is structured according to the three dimensions of requirements engineering [77]. It adds a conceptual goal model, and a model for structuring multi media artifacts such as real world scenes to the product models provided by its pre cursor environment PRO ART (ER model, data flow model, hypertext model, glBIS like decision model, the RSM model; see [4] 78] for details) ....

K. Pohl, The Three Dimensions of Requirements Engineering: A Framework and its Application, Information Systems, Vol. 19, No. 3, 1994, pp. 243-258

....background and different roles, e.g. sales persons, managers, customers, developers are involved in the initial phase of the system (product) development. To enable the people to cooperate and communicate about the specification, traceability has been recognized as an important issue (cf. [46, 1, 14, 50, 19, 58, 49, 54]) As in concurrent engineering processes, the people involved in the requirements engineering task have their own preferences for representations and products. For example, the customer uses natural language to express his needs, whereas the system specialist uses entity relationship and data ....

Klaus Pohl. The Three Dimension of Requirements Engineering: A Framework and Its Application. Information Systems, 3(19):243--258, June 1994.

....against some standard, guideline, or domain model. This dimension has traditionally come from practice, emphasized by large procurement agencies, but has recently seen substantial progress in terms of more formal and detailed guidelines and reference models for various application domains. 1 In [Pohl 1994], they have been called the three dimensions of requirements engineering and were independently derived from a survey of the RE literature and practice. The observation how they can be related to the four worlds was made in collaboration with our Swedish colleague Peter Holm. 10 . The social ....

Pohl, K.: The three dimensions of requirements engineering: a framework and its application. Information Systems 19, 3 (1994).

....Ramesh and Edwards 1993) As a consequence, much of our approach is more qualitative and the basic process models are much more open, following a paradigm of situated decision making. The approach has been implemented as part of the NATURE requirements engineering environment (Jarke et al. 1993, Pohl et al. 1994), and is being validated with a number of specific methods and tools. Throughout the paper, we shall use simple running examples from the NATURE prototype for illustration. In section 2, we present the concept of process repositories used in our approach. It is designed to be compatible with the ....

....complete AAAA AAAA AAAA AAAA AAAA AAAA AAAA AAAA personal views common view semi formal trace of the process inital input desired result Figure 7. The three dimensions of requirements engineering. Within the NATURE project, we have developed a framework for requirements engineering processes (Pohl 1994). This framework derives three dimensions of interest from the major sources of problems in requirements engineering (cf. figure 7) As a basis for formal system development, requirements engineering moves along a representational axis typically from informal to more formal representations, ....

[Article contains additional citation context not shown here]

Pohl, K.: The Three Dimensions of Requirements Engineering: A Framework and its Applications, Information Systems, 19(2), 1994.

.... trace repository on a product and process repository approach developed for the precursor environment PROART [30] The repository adopts the four level architecture of the IRDS standard [18] and structures the product models according to the dimensions representation, specification, and agreement [29] (for a detailed discussion of the repository see [31] Orthogonal to these dimensions, dependency models are defined which provide dependency types for capturing trace relationships between arbitrary product parts. For the PRIME CREWS environment we have extended the repository by additional ....

K. Pohl, "The Three Dimensions of Requirements Engineering: A Framework and its Application. Information Systems, Vol. 3, No. 19, Jun. 1994, pp. 243-258.

.... engineering itself can be understood as a process of establishing a overall system vision in context [12] Thus, RE is not an indirect analysis process, but a mutual learning process in which the various stakeholder involved have to reach an agreement about the requirements for the future system [17]. Scenario based approaches have proven useful to support the various stakeholders in reaching such an agreement. Due to the grounding of the indirect or direct expressed requirement on concrete examples, e.g. a concrete application (use) case, scenarios help in bridging the gap between the ....

K. Pohl. The three dimensions of requirements engineering: A framework and its application. Information Systems, 3(19):243--258, 6 1994.

No context found.

Pohl, K. (1994), "Three dimensions of requirements engineering: A framework and its application", Information Systems, vol. 19(3):pp. 243--258.

No context found.

Pohl, K.: Three dimensions of requirements engineering: a framework and its applications. Information Systems 19 (1994) 243--258

No context found.

K. Pohl. The three dimensions of requirements engineering: a framework and its applications. Information systems, 19(3):243--258, April 1994.

No context found.

Pohl K. The three dimensions of requirements engineering: a framework and its applications. Information Syst 1994;19(3): 243--258

No context found.

Pohl, K. (1994) Three Dimensions of Requirements Engineering: framework and its application, Information Systems 19(3):243-258.

No context found.

Pohl, K. 1994. The three dimensions of requirements engineering: a framework and its applications. Information Systems 19, 3, 243-258.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC