Designing Web-Based Systems in Social Context: A Goal and Scenario Based Approach
- 844 Downloads
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.
KeywordsRequirement Engineering Goal Model Requirement Engineer Business Objective Task Node
- 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.Chung, L., Nixon, B. A., Yu, E.and Mylopoulos, J. Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers, 2000.Google Scholar
- 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.GRL web site. http://www.cs.toronto.edu/km/GRL/.
- 6.Horton, W. Designing Web-Based Training, John Wiley & Sons, 2000.Google Scholar
- 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.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.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.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.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.Simon, A. H. The Sciences of the Artificial, Second Edition. Cambridge, MA: The MIT Press, 1981.Google Scholar
- 13.URN web site. http://www.usecasemaps.org/urn/.
- 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