Understanding Quality in Conceptual Modeling
IEEE Software
Why looking isn't always seeing: readership skills and graphical programming
Communications of the ACM
Visual language theory: towards a human computer interaction perspective
Visual language theory
UML: An Evaluation of the Visual Syntax of the Language
HICSS '01 Proceedings of the 34th Annual Hawaii International Conference on System Sciences ( HICSS-34)-Volume 3 - Volume 3
Towards Modeling and Reasoning Support for Early-Phase Requirements Engineering
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
Goal-Based Requirements Analysis
ICRE '96 Proceedings of the 2nd International Conference on Requirements Engineering (ICRE '96)
Tropos: An Agent-Oriented Software Development Methodology
Autonomous Agents and Multi-Agent Systems
Where do Goals Come from: the Underlying Principles of Goal-Oriented Requirements Engineering
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Evaluating the Effectiveness of a Goal-Oriented Requirements Engineering Method
CERE '06 Proceedings of the Fourth Internationa Workshop on Comparative Evaluation in Requirements Engineering
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
On the quantitative analysis of agent-oriented models
CAiSE'06 Proceedings of the 18th international conference on Advanced Information Systems Engineering
Hi-index | 0.00 |
Goal modelling languages are visual modelling languages. To communicate ideas effectively with a visual modelling language, one should follow some basic principles. One is modularity, i.e. organising diagrams in manageable modules to avoid confusing the reader with overly complex diagrams. Another is emphasis, i.e. visually drawing the attention to the most important pieces of information. In this paper, we evaluate how the goal modelling language KAOS and its supporting tool, Objectiver, help modellers respect nine visual modelling principles. From our observations, we formulate recommendations for modellers, language designers and tool developers.