Object-oriented design: a responsibility-driven approach
OOPSLA '89 Conference proceedings on Object-oriented programming systems, languages and applications
Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Object Design: Roles, Responsibilities, and Collaborations
Object Design: Roles, Responsibilities, and Collaborations
IEEE Software
Structured Analysis and System Specification
Structured Analysis and System Specification
Evaluating Quality in Model-Driven Engineering
MISE '07 Proceedings of the International Workshop on Modeling in Software Engineering
Modeling and Refining the Service-Oriented Requirement
TASE '08 Proceedings of the 2008 2nd IFIP/IEEE International Symposium on Theoretical Aspects of Software Engineering
On Extracting Tests from a Testable Model in the Context of Domain Engineering
ICECCS '08 Proceedings of the 13th IEEE International Conference on on Engineering of Complex Computer Systems
Technology Neutral Business Process Design using URDAD
Proceedings of the 2007 conference on New Trends in Software Methodologies, Tools and Techniques: Proceedings of the sixth SoMeT_07
Derivation and Refinement of Textual Syntax for Models
ECMDA-FA '09 Proceedings of the 5th European Conference on Model Driven Architecture - Foundations and Applications
RE '09 Proceedings of the 2009 17th IEEE International Requirements Engineering Conference, RE
Editorial: Using ontologies with UML class-based modeling: The TwoUse approach
Data & Knowledge Engineering
What is software architecture?
Proceedings of the South African Institute for Computer Scientists and Information Technologists Conference
A new tool for URDAD to Java EE EJB transformations
Proceedings of the South African Institute for Computer Scientists and Information Technologists Conference
Hi-index | 0.00 |
Use-Case Responsibility-Driven Analysis and Design (URDAD) is a service-oriented software analysis and design methodology. It is used by requirements engineers to develop technology-neutral, semi-formal platform-independent models (PIM) within the OMG's MDA. In the past, URDAD models were denoted in UML. However, that was tedious and error-prone. The resulting models were often of rather poor quality. In this paper we introduce and discuss a new Domain-Specific Language (DSL) for URDAD. Its meta model is consistent and satisfiable. We show that URDAD DSL specifications are simpler and allow for more complete service contract specifications than their corresponding UML expressions. They also enable traceability and test case generation.