ScenIC: a strategy for inquiry-driven requirements determination

ScenIC is a requirements engineering method for evolving systems. Derived from the Inquiry Cycle model of requirements refinement, it uses goal refinement and scenario analysis as its primary methodological strategies. ScenIC rests on an analogy with human memory: semantic memory consists of generalizations about system properties; episodic memory consists of specific episodes and scenarios; and working memory consists of reminders about incomplete refinements. Method-specific reminders and resolution guidelines are activated by the state of episodic or semantic memory. The paper presents a summary of the ScenIC strategy and guidelines.

[1]  William B. Rouse.  Best Laid Plans , 1994 .

[2]  D. Rumelhart.  NOTES ON A SCHEMA FOR STORIES , 1975 .

[3]  Jonathan Grudin,et al.  Evaluating Opportunities for Design Capture , 1996 .

[4]  M. Waltre.  Scenario Analysis: An Approach t o Organisational Learning , 1996 .

[5]  Mary Beth Rosson,et al.  Getting around the task-artifact cycle: how to make claims and design by scenario , 1992, TOIS.

[6]  Ralph L. Keeney,et al.  Value-Focused Thinking: A Path to Creative Decisionmaking , 1992 .

[7]  Gill Ringland,et al.  Scenario Planning: Managing for the Future , 1998 .

[8]  Annie I. Antón,et al.  Goal Decomposition and Scenario Analysis in Business Process Reengineering , 1994, CAiSE.

[9]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[10]  Michael L. Begeman,et al.  gIBIS: A tool for all reasons , 1989, JASIS.

[11]  Charles Higgins Kepner,et al.  The Rational Manager: A Systematic Approach to Problem Solving and Decision-Making , 1965 .

[12]  Tom DeMarco,et al.  Structured Analysis and System Specification , 1978 .

[13]  Pelle Ehn.  The art and science of designing computet artifacts , 1991 .

[14]  Melody M. Moore,et al.  Rule-based detection for reverse engineering user interfaces , 1996 .

[15]  Karen Holtzblatt,et al.  Apprenticing with the customer , 1995, CACM.

[16]  Lutz E. Schlange.  Scenarios: The art of strategic conversation , 1997 .

[17]  Michael J. Muller,et al.  Bifocal tools for scenarios and representations in participatory activities with users , 1995 .

[18]  Jintae Lee,et al.  Extending the Potts and Bruns model for recording design rationale , 1991, [1991 Proceedings] 13th International Conference on Software Engineering.

[19]  Sue Holwell,et al.  Information, Systems and Information Systems: Making Sense of the Field , 1998 .

[20]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[21]  Colin Potts.  A generic model for representing design methods , 1989, ICSE '89.

[22]  Annie I. Antón,et al.  The use of goals to surface requirements for evolving systems , 1998, Proceedings of the 20th International Conference on Software Engineering.

[23]  Leonard J. Bass,et al.  Scenario-Based Analysis of Software Architecture , 1996, IEEE Softw..

[24]  Colin Potts,et al.  Using schematic scenarios to understand user needs , 1995, Symposium on Designing Interactive Systems.

[25]  Gregory D. Abowd,et al.  MORALE. Mission ORiented Architectural Legacy Evolution , 1997, 1997 Proceedings International Conference on Software Maintenance.

[26]  Douglas T. Ross,et al.  Structured Analysis (SA): A Language for Communicating Ideas , 1977, IEEE Transactions on Software Engineering.

[27]  Michael Jackson,et al.  Four dark corners of requirements engineering , 1997, TSEM.

[28]  Kenneth S. Rubin.  Object behavior analysis , 1992, CACM.

[29]  David G. Ullman,et al.  Design rationale: Concepts, techniques, and use , 1997 .

[30]  Ana I. Anton,et al.  Goal identification and refinement in the specification of software-based information systems , 1997 .

[31]  Neil R. Storey,et al.  Safety-critical computer systems , 1996 .

[32]  Francoise Brun-Cottan,et al.  Using video to re-present the user , 1995, CACM.

[33]  Annie I. Antón,et al.  Goal-based requirements analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[34]  Allen Newell,et al.  The psychology of human-computer interaction , 1983 .

[35]  K. C. Burgess Yakemovic,et al.  Report on a development project use of an issue-based information system , 1990, CSCW '90.

[36]  Roger C. Schank,et al.  Scripts, plans, goals and understanding: an inquiry into human knowledge structures , 1978 .

[37]  John S. Anderson,et al.  Using scenarios in deficiency-driven requirements engineering , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[38]  P. Thorndyke.  Cognitive structures in comprehension and memory of narrative discourse , 1977, Cognitive Psychology.

[39]  Jeffrey D. Smith,et al.  An evaluation of inquiry-based requirements analysis for an Internet service , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[40]  E. Tulving,et al.  Episodic and semantic memory , 1972 .

[41]  Jeffrey D. Smith,et al.  Hypermedia support for collaboration in requirements analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[42]  Colin Potts,et al.  Recording the reasons for design decisions , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.

[43]  J. Moubray.  Reliability-Centered Maintenance , 1991 .

[44]  J. J. Storey.  From memory to monitor-pixel display architectures , 1992 .

[45]  Victor R. Basili,et al.  Tailoring the software process to project goals and environments , 1987, ICSE '87.

[46]  Karen Holtzblatt,et al.  Making customer-centered design work for teams , 1993, CACM.

[47]  Douglas T. Ross,et al.  Structured Analysis for Requirements Definition , 1977, IEEE Transactions on Software Engineering.

[48]  Stewart Green,et al.  Goal-driven approaches to requirements engineering , 1993 .

[49]  Pelle Ehn,et al.  The Art and Science of Designing Computer Artifacts , 1991, Scand. J. Inf. Syst..

[50]  John A. McDermid,et al.  Requirements analysis: orthodoxy, fundamentalism and heresy , 1994 .

[51]  Colin Potts,et al.  Collaboration during conceptual design , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[52]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[53]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[54]  Roland Vonk.  Prototyping - the effective use of CASE technology , 1989 .

[55]  David Chenho Kung,et al.  Formal approach to scenario analysis , 1994, IEEE Software.