A methodology for specifying and analyzing consistency of object-oriented behavioral models
Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering
Towards consistency-preserving model evolution
Proceedings of the International Workshop on Principles of Software Evolution
Consistency-Preserving Model Evolution through Transformations
UML '02 Proceedings of the 5th International Conference on The Unified Modeling Language
LfP: A Specification Language for Rapid Prototyping of Concurrent Systems
RSP '01 Proceedings of the 12th International Workshop on Rapid System Prototyping
Towards a Context-Driven Development Framework for Ambient Intelligence
ICDCSW '04 Proceedings of the 24th International Conference on Distributed Computing Systems Workshops - W7: EC (ICDCSW'04) - Volume 7
Systematic Transformation of Functional Analysis Model into OO Design and Implementation
IEEE Transactions on Software Engineering
A Component Coordination Model Based on Mobile Channels
Fundamenta Informaticae
Consistent Interaction Of Software Components
Journal of Integrated Design & Process Science - Component-Based System Development
Issues with representing software architectures in the unified modeling language
AMCOS'05 Proceedings of the 4th WSEAS International Conference on Applied Mathematics and Computer Science
A factory to design and build tailorable and verifiable middleware
Proceedings of the 12th Monterey conference on Reliable systems on unreliable networked platforms
A Component Coordination Model Based on Mobile Channels
Fundamenta Informaticae
| Hi-index | 0.00 |
Designing a software system's architecture properly is one of the most important tasks of any software engineering project. Nevertheless there exists no common definition of the term \software architecture" and no standard software architecture description language (ADL). This paper discusses whether the standard OO modeling language UML is a standard ADL, explains some deficiencies if used for this purpose, and makes a proposal of how to eliminate these deficiencies.The proposal is based on the widely accepted idea that elements of the component-based OO modeling language ROOM should be integrated with UML. It explains why the idea of merging static structure diagrams of ROOM with behavior describing collaboration diagrams of UML is not sufficient and presents an additional approach for the integration problem.