Men have become the tools of their tools.
-- Henry David Thoreau
No description available... Please help other visitors by providing one!
Example publications from this periodical
The following articles are from "Requirements Engineering":
Rolland, C., Achour, C. Ben, Cauvet, C., Ralyté, J., Sutcliffe, Alistair G., Maiden, N., Jarke, M., Haumer, P., Pohl, Klaus, Dubois, E. and Heymans, P. (1998): A proposal for a scenario classification framework. In Requirements Engineering, 3 (1) pp. 23-47.
The requirements engineering, information systems and software engineering communities recently advocated scenario-based approaches which emphasise the user/system interaction perspective in developing computer systems. Use of examples, scenes, narrative descriptions of contexts, mock-ups and prototypes-all these ideas can be called scenario-based approaches, although exact definitions are not easy beyond stating that these approaches emphasise some description of the real world. Experience seems to tell us that people react to real things and that this helps in clarifying requirements. Indeed, the widespread acceptance of prototyping in system development points to the effectiveness of scenario-based approaches. However, we have little understanding about how scenarios should be constructed, little hard evidence about their effectiveness and even less idea about why they work. The paper is an attempt to explore some of the issues underlying scenario-based approaches in requirements engineering and to propose a framework for their classification. The framework is a four-dimensional framework which advocates that a scenario-based approach can be well defined by itsform, content, purpose andlife cycle. Every dimension is itself multifaceted and a metric is associated with each facet. Motivations for developing the framework are threefold: (a) to help in understanding and clarifying existing scenario-based approaches; (b) to situate the industrial practice of scenarios; and (c) to assist researchers develop more innovative scenario-based approaches.
© All rights reserved Rolland et al. and/or their publisher
Siau, Keng and Lee, L. (2004): Are Use Case and Class Diagrams Complementary in Requirements Analysis? - An Experimental Study on Use Case and Class Diagrams in UML. In Requirements Engineering, 9 (4) pp. 229-237.
Siau, Keng (2007): The Future of Information Systems Engineering. In Requirements Engineering, 12 (4) pp. 199-202.
Siau, Keng and Tian, Y. (2009): A Semiotics Analysis of UML Graphical Notations. In Requirements Engineering, 14 (1) pp. 15-26.
Join our community and advance:
Give us your opinion! Do you have any comments/additions
that you would like other visitors to see?
Jul 23rd, 2014
Changes to this page (periodical)31 Oct 2011: Modified20 Feb 2009: Added
20 Feb 2009: Added
20 Feb 2009: Added
Page maintainer: The Editorial TeamHow to cite/reference this page