This Article 
 Bibliographic References 
 Add to: 
Requirements Elicitation and Validation with Real World Scenes
December 1998 (vol. 24 no. 12)
pp. 1036-1054

Abstract—A requirements specification defines the requirements for the future system at a conceptual level (i.e., class or type level). In contrast, a scenario represents a concrete example of current or future system usage. In early RE phases, scenarios are used to support the definition of high level requirements (goals) to be achieved by the new system. In many cases, those goals can to a large degree be elicited by observing, documenting and analyzing scenarios about current system usage, i.e., the new system must often fulfill many of the functional and nonfunctional goals of the existing system. To support the elicitation and validation of the goals achieved by the existing system and to illustrate problems of the old system, we propose to capture current system usage using rich media (e.g., video, speech, pictures, etc.) and to interrelate those observations with the goal definitions. Thus, we particularly aim at making the abstraction process which leads to the definition of the conceptual models more transparent and traceable.

More precisely, we relate the parts of the observations which have caused the definition of a goal or against which a goal was validated with the corresponding goal. These interrelations provide the basis for: 1) explaining and illustrating a goal model to, e.g., untrained stakeholders and/or new team members, and thereby improving a common understanding of the goal model; 2) detecting, analyzing, and resolving a different interpretation of the observations; 3) comparing different observations using computed goal annotations; and 4) refining or detailing a goal model during later process phases. Using the PRIME implementation framework, we have implemented the PRIME-CREWS environment, which supports the interrelation of conceptual models and captured system usage observations. We report on our experiences with PRIME-CREWS gained in a first experimental case study.

[1] A.I. Anton, W.M. McCracken, and C. Potts, "Goal Decomposition and Scenario Analysis in Business Process Reengineering," Proc. CAISE'94, Sixth Conf. Advanced Information Systems Eng., pp. 94-104, Lecture Notes in Computer Science 811, Springer-Verlag, 1994.
[2] A.I. Anton, "Goal-based Requirements Analysis," Proc. 2nd IEEE Int'l Conf. Requirements Engineering, CS Press, Los Alamitos, Calif., Apr. 1996, pp. 136-144.
[3] H. Beyer and K. Holtzblatt, Contextual Design: Defining Customer-Centered Systems, Academic Press, San Diego, 1998.
[4] G. Booch, Object-Oriented Analysis and Design with Applications, Addison-Wesley, Reading, Mass., 1994.
[5] F. Brun-Cottan and P. Wall, "Using Video to Re-present the User," Comm. ACM, vol. 38, no. 5, pp. 61-71, May 1995.
[6] P.P. Chen, “The Entity‐Relationship Model: Toward a Unified View of Data,” ACM Trans. Database Systems, Vol. 1, No. 1, Jan. 1976, pp. 9–36.
[7] K.L. Chung, "Representing and Using Non-Functional Requirements for Information System Development: A Process-Oriented Approach," PhD thesis, also Technical Report DKBS-TR-93-1, Dept. of Computer Science, Univ. of Toronto, June 1993.
[8] A. Cockburn, "Structuring Use Cases with Goals," J. Object-Oriented Programming, vol. 10, no. 7, pp. 35-40, Nov. 1997.
[9] J.M. Carroll et al., "Raison d'Etre: Capturing Design History and Rationale in Multimedia Narratives," Proc. ACM CHI '94 Conf., pp. 192-197,Boston, Apr. 1996.
[10] M.G. Christel, D.P. Wood, and S.P. Stevens, "AMORE: The Advanced Multimedia Organizer for Requirements Elicitation," Technical Report CMU/SEI-93-TR-12, ESC-TR-93-189, SE Information Modeling Project, SE Inst., Carnegie Mellon Univ., Pittsburgh, Pa., June 1993.
[11] A. Dardenne, A. van Lamsweerde, and S. Fickas, "Goal-Directed Requirements Acquisition," Science of Computer Programming, pp. 3-50, vol. 20, Apr. 1993.
[12] T. DeMarco, Structured Analysis and System Specification.New York: Yourdon Press, 1978.
[13] R. Dömges, K. Pohl, and K. Schreck, "A Filter-Mechanism for Method-Driven Trace Capture," Proc. 10th Int'l. Conf. Advanced Information Systems Engineering (CAiSE '98), pp. 237-250,Pisa, Italy, June 1998.
[14] M. Dowson, "Consistency Maintenance in Process Sensitive Environments," Proc. Process Sensitive Software Eng. Environments Architectures Workshop,Boulder, Colo., Sept. 1992.
[15] A. Finkelstein et al., "Inconsistency Handling in Multi-Perspective Specifications," IEEE Trans. Software Eng., vol. 20, no. 8, Aug. 1994, pp. 569-578.
[16] M. Fowler, Analysis Patterns: Reusable Object Models. Addison-Wesley, 1997.
[17] D. Harel, “Statecharts: A Visual Approach to Complex Systems,” Science of Computer Programming, Vol. 8, No. 3, pp. 231–274, 1987.
[18] ISO/IEC, Information Technology—Information Resource Dictionary System (IRDS) Framework. Int'l Standard ISO/IEC 10027, first ed. 1990-06-15, 1990.
[19] M. Jackson, Software Requirements and Specifications, Addison-Wesley, Reading, Mass., 1995.
[20] S. Jacobs and R. Holten, "Goal-Driven Business Modeling—Supporting Decision Making within Information Systems Development," Proc. Conf. Organizational Computing Systems, pp. 96-105,Milpitas, Calif., 1995.
[21] I. Jacobson et al., Object-Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley, 1992.
[22] M. Jarke and K. Pohl, "Establishing Visions in Context: Towards a Model of Requirements Processes," Proc. 14th Int'l. Conf. Information Systems, pp. 23-34,Orlando, Fla., Dec. 1993.
[23] M. Jarke and K. Pohl, "Requirements Engineering in 2001: (Virtually) Managing a Changing Reality," Software Engineering, Nov. 1994, pp. 257-266.
[24] A. van Lamsweerde, R. Darimont, and P. Massonet, "Goal-Directed Elaboration of Requirements for a Meeting Scheduler: Problems and Lessons Learned," Proc. RE'95—Second Int'l Symp. on Requirements Eng.,York, IEEE, 1995.
[25] M. Lundeberg, G. Goldkuhl, and A. Nilsson, "A Systematic Approach to Information Systems Development (I+II)," Information Systems, vol. 4, nos. 2-3, pp. 1-12, 93-118, 1979.
[26] K.L. McGraw and K. Harbison, User-Centered Requirements, Lawrence Erlbaum, Mahwah, N.J., 1997.
[27] S.M. McMenamin and J. Palmer, Essential Systems Analysis, Prentice Hall, Englewood Cliffs, N.J., 1984.
[28] B. Nuseibeh, J. Kramer, and A. Finkelstein, "A Framework for Expressing the Relationships Between Multiple Views in Requirements Specification," IEEE Trans. Software Eng., vol. 20, no. 10, pp. 760-773, Oct. 1994.
[29] K. Pohl, "The Three Dimensions of Requirements Engineering," Information Systems, Vol. 19, No. 2, 1994.
[30] K. Pohl, "PRO-ART: Enabling Requirements Pre-Traceability", Proc. Second Int'l Conf. Requirements Eng. (ICRE '96), pp. 76-84,Colorado Springs, Colo., Apr. 1996.
[31] K. Pohl, Process Centered Requirements Engineering. John Wiley and Sons Ltd., 1996.
[32] K. Pohl, R. Dömges, and M. Jarke, "Towards Method-Driven Trace Capture," Proc. Ninth Int'l Conf. Advanced Information Systems Engineering (CaiSE '97), pp. 103-116,Barcelona, Spain, June 1997.
[33] K. Pohl and P. Haumer, "Modeling Contextual Information about Scenarios," Proc. Third Int'l Workshop Requirements Eng.: Foundation for Software Quality (RESFQ '97), pp. 187-204,Barcelona, Spain, June 1997.
[34] K. Pohl and K. Weidenhaupt, A Contextual Approach for Process-Integrated Tools Proc. Sixth European Software Eng. Conf. (ESEC/FSE '97), M. Jazayeri and H. Schauer, eds., 1997.
[35] C. Potts, K. Takahashi, and A. Anton, "Inquiry-Based Requirements Analysis," IEEE Software, Mar. 1994, pp. 21-32.
[36] C. Potts, "Determining Requirements for Evolving Systems," Tutorial Notes and Slides, CAiSE '97,Barcelona, Spain, June 1997.
[37] Rational Software Corporation, Unified Modeling Language. Available on the World Wide Web:http:/, Jan. 1997.
[38] B. Regnell, K. Kimbler, and A. Wesslen, "Improving the Use Case Driven Approach to Requirements Engineering," Proc. RE'95—Second Int'l Symp. Requirements Eng., pp. 40-47,York, IEEE, 1995.
[39] B. Regnell, M. Andersson, and J. Bergstrand, "A Hierarchical Use Case Model with Graphical Representation," Proc. ECBS'96, IEEE Second Int'l Symp. and Workshop Eng. of Computer Based Systems, Mar. 1996.
[40] C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyte, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, E. Dubois, and P. Heymans, "A Proposal for a Scenario Classification Framework," Requirements Engineering J., vol. 3, no.1, 1998.
[41] C.L. Chang, R.A. Stachowitz, and J.B. Combs, “Validation of Nonmonotonic Knowledge-Based Systems,” Proc. IEEE Int'l Conf. Tools for Artificial Intelligence, Nov. 1990.
[42] A.W. Scheer, Architektur Integrierter Infomationssysteme [Architecture of Integrated Information Systems]. Springer, 1990 (in German).
[43] L.A. Suchman and R.H. Trigg, "Understanding Practice: Video as a Medium for Reflection and Design," Design at Work: Cooperative Design of Computer Systems, J. Greenbaum and M. Kyng, eds., pp. 65-89.New Jersey: Lawrence Erlbaum Assoc., 1991.
[44] K. Weidenhaupt, K. Pohl, M. Jarke, and P. Haumer, "Scenarios in System Development: Current Practice," IEEE Software, pp. 34-45, Mar./Apr. 1998.
[45] D.P. Wood, M.G. Christel, and S.M. Stevens, "A Multimedia Approach to Requirements Capture And Modeling," Proc. First Int'l Conf. Requirements Eng. (ICRE '94), pp. 53-56,Colorado Springs, Colo., Apr. 1994.
[46] E. Yourdon, Modern Structured Analysis, Prentice Hall, Englewood Cliffs, N.J., 1989.
[47] E. Yu, "Modeling Strategic Relationships for Process Reengineering," PhD thesis, Technical Report on Research in Data and Knowledge Eng., DKBS-TR-94-6, Dept. of Computer Science, Univ. of Toronto, 1994.
[48] E. Yu, "Why Goal-Oriented Requirements Engineering," Proc. Fourth Int'l Workshop Requirements Eng.: Foundation for Software Quality (RESFQ '98),Pisa, Italy, June 1998.

Index Terms:
Requirements management, scenario, scenario-based requirements engineering, requirements traceability, requirements elicitation, requirements validation, goal modeling, rich media, process-integrated environments, software development.
Peter Haumer, Klaus Pohl, Klaus Weidenhaupt, "Requirements Elicitation and Validation with Real World Scenes," IEEE Transactions on Software Engineering, vol. 24, no. 12, pp. 1036-1054, Dec. 1998, doi:10.1109/32.738338
Usage of this product signifies your acceptance of the Terms of Use.