Reconciling the needs of architectural description with object-modeling notations

摘要: Complex software systems require expressive notations for representing their architectures. Two competing paths have emerged. One is to use a specialized notation architecture, an architecture description language (ADL). The other adapt general-purpose modeling notation, such as UML. latter has number of benefits, including familiarity developers, close mapping implementations, and commercial tool support. However, it remains open question how best object-oriented architectural description, and, indeed, whether they are sufficiently expressive, currently defined. In this paper, we take systematic look at these questions, examining the space possible mappings from ADLs into Specifically, describe (a) principal strategies structure in UML; (b) benefits limitations each strategy; (c) aspects that intrinsically difficult model UML using strategies.