A. H. Dutoit and B. Paech. Rationale-based use case specification. Requirements Engineering Journal, 2002. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Building Awareness in Global Software Engineering: .. - Kobylinski.. (2002) (1 citation) Self-citation (Dutoit) (Correct)
....participants to find their counter parts and to initiate conversations about impending crises. We are researching comprehensive solutions for supporting collaboration in distributed software engineering projects, including supporting informal meetings [1] capturing and maintaining rationale [10], and the travel of small groups of developers [9] In this paper, we focus on group awareness. We propose to adapt and generalize the results from the awareness and design rationale communities to global software engineering. We see three critical issues when defining an awareness system: 1. ....
....that the value of these cross model links is high for providing context information in an awareness system and, in general, for ensuring consistency among models manipulated by di#erent tools. Our approach so far has been to make it easier to create these types of links. For examples, REQuest [10], a tool for writing specifications in terms of use cases, enables users to create and attach issues to specific use cases. The issues and the links are stored in the issue repository, however, users view the issue models in the context of the specification. Following the same principle, we are ....
A. H. Dutoit and B. Paech. Rationale-based use case specification. Requirements Engineering Journal, 2002.
Supporting an Explicit Organizational Model in Global.. - Creighton, Dutoit.. (2003) Self-citation (Dutoit) (Correct)
....sharing environments, shared slides, and the web. The infrastructure also included asynchronous tools such as Lotus Notes bulletin boards, CVS for version control, a UML modeling tool, and an integrated development environment. More recently, we have also introduced a requirements management tool [4], an awareness infrastructure [6] and a workflow tool for process enactment. As most tools do not share the same user information, developers need a user name and password for each tool. Moreover, while the infrastructure available to students includes the same set of tools in both sites, these ....
A. H. Dutoit and B. Paech. Rationale-based use case specification. Requirements Engineering Journal, 2002.
Functional requirements, non-functional.. - Paech, Dutoit.. (2002) Self-citation (Dutoit Paech) (Correct)
....element) As illustrated in the example, with NFRs, FRs, and ADs, the relationships can be much more complex. How to ensure completeness and consistency of the considered option This can be supported e.g. by a knowledge base that should also include rationale to support trade off decisions (e.g. [DP02]) How to inspect or testNFR Different communities have investigated specific quality assurance techniques for specific NFRs (e.g. security, safety) Integrated quality assurance requires integration of these techniques to mirror the (de)composition of NFRs into more reftned NFRs and additional ....
A.H. Dutoit, B. Paech. "Rationale-based Use Case Specification", Requirements Engineering Journal, Special Issue on REFSQ'2001, 2002.
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