Advertisement

Designing Web-Based Systems in Social Context: A Goal and Scenario Based Approach

  • Lin Liu
  • Eric Yu
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2348)

Abstract

In order to design a better web-based 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 language GRL and a scenarios-oriented notation UCM for representing design knowledge of web-based systems and information systems in general. Goals are used to depict business objectives, functional and non-functional system requirements. Tasks are used in the exploration of alternative technologies and their operationalizations into system constructs. Actors are used to do role-based analysis on social relationships. Scenarios are used to describe elaborated business processes or workflow. The approach is illustrated with an example of designing a web-based training system.

Keywords

Requirement Engineering Goal Model Requirement Engineer Business Objective Task Node 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

References

  1. 1.
    Buhr, R. J. A. Use Case Maps as Architectural Entities for Complex Systems. In: Transactions on Software Engineering, IEEE, Vol. 24, No. 12, December 1998, pp. 1131–1155.CrossRefGoogle Scholar
  2. 2.
    Carroll, J. M. Introduction: The Scenario Perspective on System Development. In Scenario-Based Design: Envisioning Work and Technology in System Development, Ed Caroll, J. M. 1995. pp. 1–17.Google Scholar
  3. 3.
    Chung, L., Nixon, B. A., Yu, E.and Mylopoulos, J. Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers, 2000.Google Scholar
  4. 4.
    Fuxman, A., Pistore, M., Mylopoulos, J., and Traverso, P. Model Checking Early Requirements Specifications in Tropos. In Proceedings of the 5th IEEE International Symposium on Requirements Engineering. August 2001. Toronto, Canada. 174–181.Google Scholar
  5. 5.
  6. 6.
    Horton, W. Designing Web-Based Training, John Wiley & Sons, 2000.Google Scholar
  7. 7.
    Kazman, R., Bass, L., Abowd, G. and Webb, M. SAAM: A Method for Analyzing the Properties of Software Architectures. In Proceedings of the 16 th International Conference on Software Engineering. May 1994. Sorrento, Italy. 81–90.Google Scholar
  8. 8.
    Lamsweerde, A. V., Willemet, L. Inferring Declarative Requirements Specifications from Operational Scenarios. IEEE Transactions on Software Engineering, Special Issue on Scenario Management, December 1998.Google Scholar
  9. 9.
    Lamsweerde, A. V. Requirements Engineering in the Year 00: A Research Perspective. In the Proceedings of 22nd International Conference on Software Engineering. Limerick, June 2000, ACM press.Google Scholar
  10. 10.
    Liu, L., Yu, E. From Requirements to Architectural Design-Using Goals and Scenarios. ICSE-2001 Workshop: From Software Requirements to Architectures (STRAW 2001) May 2001, Toronto, Canada, pp. 22–30. Toronto, Canada, May 14,2001. On-line at: http://www.cs.toronto.edu/~liu/.
  11. 11.
    Rolland, C, Grosz, G. and Kla, R. Experience With Goal-Scenario Coupling In Requirements Engineering. In Proceedings of the IEEE International Symposium on Requirements Engineering 1998. June 1999. Limerick, Ireland.Google Scholar
  12. 12.
    Simon, A. H. The Sciences of the Artificial, Second Edition. Cambridge, MA: The MIT Press, 1981.Google Scholar
  13. 13.
  14. 14.
    Yu, E. and Mylopoulos, J. Why Goal-Oriented Requirements Engineering. In Proceedings of the 4th International Workshop on Requirements Engineering: Foundations of Software Quality. June 1998, Pisa, Italy. E. Dubois, A.L. Opdahl, K. Pohl, eds. Presses Universitaires de Namur, 1998. pp. 15–22.Google Scholar
  15. 15.
    Yu, E. 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.Google Scholar
  16. 16.
    Yu, E. Agent Orientation as a Modelling Paradigm. Wirtschaftsinformatik. 43(2) April 2001. pp. 123–132.CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2002

Authors and Affiliations

  • Lin Liu
    • 1
  • Eric Yu
    • 1
  1. 1.Faculty of Information StudiesUniversity of TorontoCanada

Personalised recommendations