Carroll, J.M., Rosson, M.B., Chin, G. & Koenemann, J. (1998) Requirements Develop-ment in scenario-based design. IEEE Transactions on Software Engineering, 24(12), 1156-1170. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
The Requirements Engineer as Architect? - Johnston (Correct)
....of the spectrum, where user input is considered most effective [6] Prototyping and walkthroughs are common tools to help establish the requirements. ffl Task artifact cycle The user centred design approach, in turn, has been given more substance in the work of Carroll and co workers (see e.g. [7]) who consider requirements should be sufficiently articulated to provide technical guidance for systems specification . Their work is based on the co evolution of tasks and artefacts, and looks at the emergent tasks of the users once they have access to the new system. The use of scenarios ....
....they may not otherwise conceive of. 8] Similarly with software, one would hope that the architect would be able to see a bigger picture, and apply a solution more fitting to the total needs in the larger work environment. Techniques such as those proposed by Carroll et al. and Dzida and Freitag [7, 9] allow the context to be considered. It then becomes possible to look more carefully at the work practices, and to extend the boundaries of the proposed solution, thereby arriving at a better solution in the larger environment. The optimal solution comes not from purely technical issues, but from ....
[Article contains additional citation context not shown here]
John M. Carroll, Mary Beth Rosson, George Chin Jr., and Jurgen Koenemann. Requirements development in scenario-based design. IEEE Transactions on Software Engineering, pages 1156--1170, December 1998.
User's Manual as a Requirements Specification - Berry, Daudjee, Dong, Nelson.. (2001) (Correct)
....the CBS is supposed to do, clear enough that the manual author can visualize user scenarios for each kind of user and describe both 1. what the user should say to the CBS and 2. what the CBS will respond to the user. Note that this information amounts to scenarios describing uses of the CBS [14, 8]. If scenarios with steps in common are collected into abstractions focused on user tasks, one gets use cases Even in the case of the specific user s manual, there is a question about which detailed information should be in it. The information in the manual depends both on the CBS whose ....
Carroll, J., Rosson, M.B., Chin, G., and Koenemann, J., "Requirements Development in Scenario-Based Design," IEEE Transactions on Software Engineering SE-24(12), p.1156--1170 (December 1998).
Explaining Scenarios for Information Personalization - Ramakrishnan, Rosson, Carroll (2001) Self-citation (Carroll Rosson) (Correct)
....of information spaces needed in PIPE. In this sense, we are extending the PIPE methodology upstream in the personalization system design life cycle, to include requirements analysis and specification. While even a very general notion of requirements gathering applies in our situation [11, 34, 36, 58], personalization offers the unique viewpoint of interpreting a general, existing information resource in a specialized manner (and thus, indirectly improving it) Studies in traditional IR contexts (e.g. see [5, 64] have shown that one way to achieve such specialized interpretation is to ....
....in a given scenario. By comparing these effects to those deduced before the change, we can reason about the orthogonality of scenarios. 4. 4 Related Research As narrative descriptions of use, scenario based methods have become prevalent in various applications, including requirements analysis [11, 29, 62] and user interface design [9] The design of software systems from scenarios (as opposed to purely functional, solution first specifications) is the cornerstone of our approach. Most relevant to our presentation is Potts s distinction between inducing scenarios (from interaction) and deducing ....
J.M. Carroll, M.B. Rosson, G. Chin Jr., and J. Koenemann. Requirements Development in Scenario-Based Design. IEEE Transactions on Software Engineering, Vol. 24(12):pages 1156--1170, December 1998.
The Development of Cooperation: Five Years of.. - Carroll, Chin.. (2000) (2 citations) Self-citation (Rosson Chin) (Correct)
No context found.
) Carroll, J.M., Rosson, M.B., Chin, G. & Koenemann, J. 1998. Requirements development in scenario-based design. IEEE Transactions on Software Engineering,
The Human Interface in Mobile Applications - Lynne Baillie And (Correct)
No context found.
Carroll, J.M., Rosson, M.B., Chin, G. & Koenemann, J. (1998) Requirements Develop-ment in scenario-based design. IEEE Transactions on Software Engineering, 24(12), 1156-1170.
Original Article - Berry Daudjee Dong (Correct)
No context found.
Carroll J, Rosson MB, Chin G, Koenemann J (1998) Requirements development in scenario-based design. IEEE Trans Software Eng SE-24:1156--1170
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