A design process based on a model combining scenarios with goals and functions

IEEE Transactions on Systems, Man, and Cybernetics Part A:Systems and Humans.

Volumn 30, Issue 5, 2000, Pages 537-551

  Kaindl, Hermann ^a,b  

^a IEEE   (Austria)

^b SIEMENS AG ÖSTERREICH   (Austria)

Author keywords

Design methodology; Modeling; Software requirements and specifications; System analysis and design; User centered design

Indexed keywords

FUNCTIONS; INTELLIGENT CONTROL; REAL TIME SYSTEMS; REDUNDANCY; SPECIFICATIONS;

CONCRETE DESIGN PROCESS; REAL WORLD PROJECT; SCENARIO BASED DESIGN; USER CENTERED DESIGN;

SYSTEMS ANALYSIS;

EID: 0034269939     PISSN: 10834427     EISSN: None     Source Type: Journal    
DOI: 10.1109/3468.867861     Document Type: Article

References (39)

1. D. Allemang, "Using functional models in automatic debugging," IEEE Expert, vol. 6, pp. 13-18, Dec. 1991.
2. A. I Antón, "Goal-based requirements analysis," in Proc. 2nd Int. Conf. Requirements Engineering (ICRE'96), Colorado Springs, CO, April 1996, pp. 136-144.
3. S. K. Card, T. P. Moran, and A. Newell, The Psychology of Human-Computer Interaction. Hillsdale, NJ: Lawrence Erlbaum, 1983.
4. J. M. Carroll, Ed., Scenario-Based Design: Envisioning Work and Technology in System Development. New York: Wiley, 1995.
5. J. M. Carroll, R. L. Mack, S. P. Robertson, and M. B. Rosson, "Binding objects to scenarios of use," Int. J. Human-Comput. Stud., vol. 41, no. 1/2, pp. 243-276, July/Aug. 1994.
6. B. Chandrasekaran, "Functional representation and causal processes," in Advances in Computers, M. C. Yovits, Ed. New York: Academic, 1994, pp. 73-143.
7. B. Chandrasekaran, A. K. Goel, and Y. Iwasaki, "Functional representation as design rationale," IEEE Computer, vol. 26, no. 1, pp. 48-56, 1993.
8. B. Chandrasekaran and H. Kaindl, "Representing functional requirements and user-system interactions," in Proc. AAAI-96 Workshop on Modeling and Reasoning about Function. Portland, OR: AAAI, Aug. 1996.
9. L. Constantine, "Essential modeling: Use cases for user interfaces," ACM Interactions, vol. II.2, pp. 34-46, April 1995.
10. A. Dardenne, A. van Lamsweerde, and S. Fickas, "Goal-directed requirements acquisition," Sci. Comput. Program., vol. 20, pp. 3-50, 1993.
11. D. Diaper, Ed., Task Analysis for Human-Computer Interaction. Chichester, U.K.: Ellis Horwood, 1989.
12. P. Haumer, K. Pohl, and K. Weidenhaupt, "Requirements elicitation and validation with real world scenes," IEEE Trans. Software Eng., vol. 24, pp. 1036-1054, Dec. 1998.
13. P. Hsia, J. Samuel, J. Gao, D. Kung, Y. Toyoshima, and C. Chen, "Formal approach to scenario analysis," IEEE Softw., vol. 11, no. 2, pp. 33-41, 1994.
14. I. Jacobson, M. Christerson, P. Jonsson, and G. Övergaard, Object-Oriented Software Engineering: A Use Case Driven Approach. Reading, MA: Addison-Wesley, 1992.
15. P. Johnson, Human-Computer Interaction: Psychology, Task Analysis and Software Engineering. London, U.K.: McGraw-Hill, 1992.
16. P. Johnson, H. Johnson, and S. Wilson, "Rapid prototyping of user interfaces driven by task models," in Scenario-Based Design: Envisioning Work and Technology in System Development, J. M. Carroll, Ed. New York: Wiley, 1995, pp. 209-246.
17. H. Kaindl, "An integration of scenarios with their purposes in task modeling," in Proc. Symp. Designing Interactive Systems: Processes, Practices, Methods, and Techniques (DIS '95). Ann Arbor, MI: ACM, August 1995, pp. 227-235.
18. _, "How to identify binary relations for domain models," in Proc. 18th Int. Conf. Software Eng. (ICSE-18). Berlin, Germany: IEEE, March 1996, pp. 28-36.
19. _, "Using hypertext for semiformal representation in requirements engineering practice," The New Rev. Hypermedia Multimedia, vol. 2, pp. 149-173, 1996.
20. _, "A practical approach to combining requirements definition and object-oriented analysis," Ann. Softw. Eng., vol. 3, pp. 319-343, 1997.
21. _, "Combining goals and functional requirements in a scenario-based design process," in People and Computers XIII, Proc. Human Computer Interaction '98 (HCI '98). Sheffield, U.K.: Springer, Sept. 1998, pp. 101-121.
22. H. Kaindl, S. Kramer, and R. Kacsich, "A case study of decomposing functional requirements using scenarios," in Proc. 3rd Int. Conf. Requirements Engineering (ICRE'98), Colorado Springs, CO, April 1998.
23. D. Kieras, "Towards a practical GOMS model methodology for user interface design," in Handbook of Human-Computer Interaction, M. Helander, Ed. Amsterdam, The Netherlands: North-Holland, 1988, pp. 135-158.
24. B. Kirwan and L. K. Ainsworth, A Guide to Task Analysis. London, U.K.: Taylor and Francis, 1992.
25. N. G. Leveson, "Intent specifications: An approach to building human-centered specifications," IEEE Trans. Softw. Eng. , vol. 26, pp. 15-35, Jan. 2000.
26. P. Loucopoulos and V. Karakostas, System Requirements Engineering. New York: McGraw-Hill, 1995.
27. R. L. Mack, "Discussion: Scenarios as engines of design," in Scenario-Based Design: Envisioning Work and Technology in System Development, J. M. Carroll, Ed. New York: Wiley, 1995, pp. 361-386.
28. A. MacLean and D. McKerlie, "Design space analysis and use representations," in Scenario-Based Design: Envisioning Work and Technology in System Development, J. M. Carroll, Ed. New York: Wiley, 1995, pp. 183-207.
29. J. Mylopoulos, L. Chung, and B. Nixon, "Representing and using nonfunctional requirements: A process-oriented approach," IEEE Trans. Softw. Eng., vol. 18, no. 6, pp. 483-497, 1992.
30. N. Nilsson, Principles of Artif. Intell. Palo Alto, CA: Tioga, 1980.
31. C. Potts, "Using schematic scenarios to understand user needs," in Proc. Symp. Designing Interactive Systems: Processes, Practices, Methods, and Techniques (DIS '95). Ann Arbor, MI: ACM, August 1995, pp. 247-256.
32. C. Potts, K. Takahashi, and A. I. Antón, "Inquiry-based requirements analysis," IEEE Softw., vol. 11, no. 2, pp. 21-32, 1994.
33. C. Rolland, C. Souveyet, and C. Ben Achour, "Guiding goal modeling using scenarios," IEEE Trans. Software Eng., vol. 24, pp. 1055-1071, Dec. 1998.
34. J. Rumbaugh, M. Blaha, W. Premerlani, F. Eddy, and W. Lorensen, Object-Oriented Modeling and Design. Englewood Cliffs, NJ: Prentice-Hall, 1991.
35. J. Rumbaugh, I. Jacobson, and G. Booch, The Unified Modeling Language Reference Manual. Reading, MA: Addison-Wesley, 1999.
36. R. Schank and R. Abelson, Scripts, Plans, Goals, and Understanding. Hillsdale, NJ: Lawrence Erlbaum, 1977.
37. A. Sutcliffe, "Requirements rationales: Integrating approaches to requirements analysis," in Proc. Symp. Designing Interactive Systems: Processes, Practices, Methods, and Techniques (DIS '95). Ann Arbor, MI: ACM, Aug. 1995, pp. 33-42.
38. W. Wang, S. Hufnagel, P. Hsia, and S. M. Yang, "Scenario driven requirements analysis method," in Proc. 2nd Int. Conf. Systems Integration, Morristown, NJ, June 1992, pp. 127-136.
39. K. Weidenhaupt, K. Pohl, M. Jarke, and P. Haumer, "Scenarios in system development: Current practice," IEEE Software, pp. 33-45, March/April 1998.