Scenario-based design: envisioning work and technology in system development
Scenario-based design: envisioning work and technology in system development
SAAM: a method for analyzing the properties of software architectures
ICSE '94 Proceedings of the 16th international conference on Software engineering
Inferring Declarative Requirements Specifications from Operational Scenarios
IEEE Transactions on Software Engineering
Use Case Maps as Architectural Entities for Complex Systems
IEEE Transactions on Software Engineering
Requirements engineering in the year 00: a research perspective
Proceedings of the 22nd international conference on Software engineering
Experience with Goal-Scenario Coupling in Requirements Engineering
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
Agent-Oriented Modelling: Software versus the World
AOSE '01 Revised Papers and Invited Contributions from the Second International Workshop on Agent-Oriented Software Engineering II
Model Checking Early Requirements Specifications in Tropos
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
A context-based enterprise ontology
BIS'07 Proceedings of the 10th international conference on Business information systems
URN: towards a new standard for the visual description of requirements
SAM'02 Proceedings of the 3rd international conference on Telecommunications and beyond: the broader applicability of SDL and MSC
CAiSE'05 Proceedings of the 17th international conference on Advanced Information Systems Engineering
Extending tropos for a prolog implementation: a case study using the food collecting agent problem
CLIMA'05 Proceedings of the 6th international conference on Computational Logic in Multi-Agent Systems
| Hi-index | 0.00 |
In order to design a better web-based system, a designer would like to have notations to visualize how design experts' knowhow 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 nonfunctional 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.