P. Darke and G. Shanks, "Stakeholder viewpoints in requirements definition: A framework for understanding viewpoint development approaches," Requirements Engineering, vol. 1, pp. 88--105, 1996. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Documenting And Analyzing A Context-Sensitive Design Space - de Bruin, van Vliet, Baida (2002) (5 citations) (Correct)
....resembles the F part of the FS graph. Usually though, features of a product line are units of functionality rather than quality concerns. In requirements engineering, viewpoints are used to express different perspectives of stakeholders, agents that may have different responsibilities or roles [7]. Some requirements engineering methods, and the associated tool environments, treat viewpoints as first class objects that may be used and manipulated by the users of that method. At an early stage, each viewpoint is represented. Later on, viewpoints are compared and conflicts and inconsistencies ....
Peta Darke and Graeme Shanks. Stakeholder Viewpoints in Requirements Definition: A Framework for Understanding Viewpoint Development Approaches. Requirements Engineering Journal, 1:88--105, 1996.
Practical Experience with Viewpoint-Oriented.. - Gerald Kotonya.. (1997) (Correct)
....proposes a set of 10 comparators that other researchers can use to compare their approaches and techniques. Keywords Requirements, specification, experience, viewpoints, interactive, system 1 Introduction The notion of viewpoints as a means of formulating software requirements is well known [1,2,3,4,5]. The proposed approaches range from those based on extensions to structured analysis, such as CORE [6] to those that use viewpoints as means for integrating multiple perspectives in system development [7] through to those that use viewpoints as means of eliciting and structuring requirements ....
Darke, P., and Shanks, G. Stakeholder viewpoints in requirements definition: A framework for understanding viewpoint development approaches. Requirements Engineering 1996; 1(2): 88-104.
Using Decision Tools in Deciding System Product Requirements.. - Hurri (2000) (Correct)
....view of SATIRE naturally avoids conversion to common unit. operational formalism for impact: In SATIRE the decision maker(s) have a complete freedom in deciding how , and are defined. Using the terms of requirements engineering, SATIRE resembles a viewpoint development approach [22], but with very little methodological support for comparing viewpoints or managing conflicts or inconsistencies. The devotion to the behavioural decision approach has kept the method very simple. In fact it is a good question why one would want to use tools to support the behavioural decision ....
Darke, P., and Shanks, G. Stakeholder viewpoints in requirements definition: A framework for understanding viewpoint development approaches. Requirements Engineering 1 (1996), 88--105.
An Empirical Investigation of Multiple Viewpoint.. - Menzies.. (1999) (Correct)
....modified. In viewpoint based requirements engineering, an emphasis is placed on capturing separate descriptions of the viewpoints of different stakeholders, and on identifying and resolving conflicts between them (e.g. 7, 11, 22] In their survey of viewpoints based approaches, Darke Shanks [3] note that If different perceptions of the same problem domain can exist, then it may not always be possible, or desirable, to develop a single integrated viewpoint [that] attempts to satisfy the needs of all stakeholders . In this paper we set out to test the extent to which it is necessary to ....
P. Darke and G. Shanks. Stakeholder viewpoints in requirements definition: A framework for understanding viewpoint development approaches. Requirements Engineering, 1(2):88--105, 1996.
Translating Descriptions of a Viewpoint among Different.. - Stanger (2000) (Correct)
No context found.
P. Darke and G. Shanks, "Stakeholder viewpoints in requirements definition: A framework for understanding viewpoint development approaches," Requirements Engineering, vol. 1, pp. 88--105, 1996.
Guidelines of Business Process Modeling - Becker, Rosemann, von Uthmann (2000) (1 citation) (Correct)
No context found.
Darke, P., Shanks, G.: Stakeholder Viewpoints in Requirements Definition: A Framework for Understanding Viewpoint Development Approaches. Requirements Engineering 1 (1996), 85-105
A Viewpoint-Based Framework for Discussing the Use of Multiple.. - Stanger (2000) (Correct)
No context found.
Peta Darke and Graeme Shanks. Stakeholder viewpoints in requirements definition: A framework for understanding viewpoint development approaches. Requirements Engineering, 1:88--105, 1996.
Requirements Engineering: A Roadmap - Nuseibeh, Easterbrook (2000) (28 citations) (Correct)
No context found.
Darke, P. & Shanks, G. (1996). Stakeholder Viewpoints in Requirements Definition: A Framework for Understanding Viewpoint Development Approaches. Requirements Engineering, 1(2): 88-105.
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