Designing information systems in social context: a goal and scenario modelling approach (original) (raw)

Abstract

In order to design a better information system, a designer would like to have notations to visualize how design experts' know-how can be applied according to one's specific social and technology situation. We propose the combined use of a goal-oriented requirements language (GRL) and a scenario-oriented notation Use Case Maps (UCM) for representing design knowledge of information systems. Goal-oriented modelling is used throughout the requirements and design process. In GRL, goals are used to depict business objectives and system requirements, both functional and non-functional. Tasks are used to represent different ways for achieving goals. Means-ends reasoning is used to explore alternative solutions and their operationalizations into implementable system constructs. Social context is modelled in terms of dependency relationships among agents and roles. Scenarios expressed in UCM are used to describe elaborated business processes or workflow. The complementary use of goal-oriented modelling with GRL and scenario modelling with UCM is illustrated with an example of designing a web-based training system.

Loading...

Loading Preview

Sorry, preview is currently unavailable. You can download the paper by clicking the button above.

References (24)

  1. A.V. Lamsweerde, Requirements engineering in the year 00: a research perspective, in: The Proceedings of the 22nd International Conference on Software Engineering, Limerick, June 2000, ACM press, New York.
  2. E. Yu, J. Mylopoulos, Why goal-oriented requirements engineering, in: E. Dubois, A.L. Opdahl, K. Pohl (Eds.), Proceedings of the Fourth International Workshop on Requirements Engineering: Foundations of Software Quality, Pisa, Italy, Presses Universitaires de Namur, Paris, June 1998, pp. 15-22.
  3. J.G. Leite, J. Doorn Hadad, G. Kaplan, A scenario construction process, Requirements Eng. 5 (1) (2000) 38-61.
  4. A. Sutcliffe, N. Maiden, S. Minocha, D. Manual, Supporting scenario-based requirements engineering, IEEE Trans. Software Eng. 24 (12) (1998) 1072-1088.
  5. K. Weidenhaupt, K. Pohl, M. Jarke, P. Haumer, Scenario management in software development: current practice, IEEE Software (15) (1998) 34-45.
  6. J.M. Carroll, Introduction: the scenario perspective on system development, in: J.M. Caroll (Ed.), Scenario-Based Design: Envisioning Work and Technology in System Development, Wiley, 1995, pp. 1-17.
  7. M. Jarke, X.T. Bui, J. MC arroll, Scenario management- an interdisciplinary approach, Requirements Eng. J. 3 (3-4) (1998) 155-173.
  8. GRL web site. http://www.cs.toronto.edu/km/GRL/
  9. E. Yu, Towards modelling and reasoning support for early phase requirements engineering, in: Proceedings of the Third IEEE International Symposium on Requirements Engineering (RE '97), Washington, DC, USA, January 6-8, 1997, pp. 226-235.
  10. R.J.A. Buhr, Use case maps as architectural entities for complex systems, in: Transactions on Software Engineer- ing, Vol. 24, No. 12, IEEE Press, New York, December 1998, pp. 1131-1155.
  11. L. Chung, B.A. Nixon, E. Yu, J. Mylopoulos, Non- Functional Requirements in Software Engineering, Kluwer Academic Publishers, Dordrecht, 2000.
  12. A H. Simon, The Sciences of the Artificial, 2nd Edition, The MIT Press, Cambridge, MA, 1981.
  13. E. Yu, Agent orientation as a modelling paradigm, Wirtschaftsinformatik 43 (2) (2001) 123-132.
  14. Z.150: Users requirements notation, Recommendation to ITU-T Study Group 17, Available at URN web site. http://www.usecasemaps.org/urn/
  15. D. Amyot, G. Mussbacher, N. Mansurov, Understanding existing software with use case map scenarios, in: Third SDL and MSC Workshop (SAM '02), Aberystwyth, UK, June 2002.
  16. W. Horton, Designing Web-Based Training, Wiley, New York, 1990.
  17. E. Yu, Agent-oriented modelling: software versus the world, in: The Proceedings Agent-Oriented Software Engineering AOSE-2001 Workshop, LNCS 2222, On-line at: http://www.fis.utoronto.ca/faculty/yu
  18. A.V. Lamsweerde, L. Willemet, Inferring declarative requirements specifications from operational scenarios, in: IEEE Transactions on Software Engineering, Special Issue on Scenario Management, December 1998.
  19. C. Rolland, G. Grosz, R. Kla, Experience with goal- scenario coupling in requirements engineering, in: Proceed- ings of the IEEE International Symposium on Require- ments Engineering, 1998, Limerick, Ireland, June 1999.
  20. P. Haumer, K. Pohl, K. Weidenhaupt, Requirements elicitation and validation with real world scenes, IEEE Trans. Software Eng. 24 (12) (1998) 1036-1054.
  21. R. Kazman, L. Bass, G. Abowd, M. Webb, SAAM: a method for analyzing the properties of software architectures, in: Proceedings of the 16th International Conference on Software Engineering, Sorrento, Italy, 1994, pp. 81-90.
  22. L. Liu, E. Yu, From requirements to architectural design-using goals and scenarios, in: ICSE-2001 Work- shop: From Software Requirements to Architectures (STRAW 2001), May 2001, Toronto, Canada, pp.22-30.
  23. Toronto, Canada, May 14, 2001, On-line at: http:// www.cs.toronto.edu/Bliu/
  24. A. Fuxman, M. Pistore, J. Mylopoulos, P. Traverso, Model checking early requirements specifications in Tropos, in: Proceedings of the Fifth IEEE International Symposium on Requirements Engineering, Toronto, Canada, August 2001, pp. 174-181.