Object-oriented metrics: measures of complexity
Object-oriented metrics: measures of complexity
UML for Agent-Oriented Software Development: The Tropos Proposal
«UML» '01 Proceedings of the 4th International Conference on The Unified Modeling Language, Modeling Languages, Concepts, and Tools
The Object Constraint Language: Getting Your Models Ready for MDA
The Object Constraint Language: Getting Your Models Ready for MDA
Requirements Engineering
Use Case Driven Object Modeling with UML: Theory and Practice
Use Case Driven Object Modeling with UML: Theory and Practice
A deidealisation semantics for KAOS
Proceedings of the 2010 ACM Symposium on Applied Computing
A Model Transformation Method in Service-Oriented Domain Modeling
ASWEC '10 Proceedings of the 2010 21st Australian Software Engineering Conference
Analyzing goal models: different approaches and how to choose among them
Proceedings of the 2011 ACM Symposium on Applied Computing
Stream: a strategy for transition between requirements models and architectural models
Proceedings of the 2011 ACM Symposium on Applied Computing
A scenario- and observation-based requirement analysis for delivery of remote mining services
Proceedings of the 24th Australian Computer-Human Interaction Conference
Hi-index | 0.00 |
Consistency between various phases of the software development process is an important aspect in software engineering. Without this aspect, software products may not satisfy users' needs. The cause of the inconsistency is that users' requirements may not be sufficiently reflected in software products. We consider this situation as a gap between the requirements and the products. We focus on the early phases of the software development, because we need to deal with the problem before the inconsistency in the early phases affects the later phases. KAOS has been attracting attentions and UML has been widely adopted, in the early phases, for requirements analysis and design respectively. However, the requirements analysis phase and the design phase are often practiced separately which may cause a gap between them. In this paper, we propose a systematic approach, to reduce the gap between the requirement analysis phase and the design phase, by generating UML class diagram and OCL constraints from the KAOS model. We propose transformation rules between operation models and class diagrams and rules for producing OCL constraints from the KAOS model. In addition, we carried out a case study to confirm the validity of this approach.