Revision as of 22:53, 28 August 2008 edit SmackBot (talk \| contribs) 3,734,324 edits m Date the maintenance tags and general fixes ← Previous edit		Revision as of 09:10, 20 October 2008 edit undo Antonielly (talk \| contribs) 1,563 edits →Characteristics: fixing grammar + removing nonsense statement Next edit →
Line 22: Requirements languages, because ADLs are rooted in the solution space, whereas requirements describe problem spaces. Programming languages, because ADLs do not bind architectural abstractions to specific point solutions Modeling languages, because ADLs tend to focus on representation of components rather than the behavior of the whole. ~~Although~~However, there are ___domain specific modeling languages (DSMLs) that focus on representation of components. The following list is a minimal set of requirements for a language to be an ADL. The languages must : Line 52: There is not universal agreement on what ADLs should represent, particularly as regards the behavior of the architecture Representations currently in use are relatively difficult to parse and are not supported by commercial tools Most ADL work today has been undertaken with academic rather than commercial goals in mind *Most ADLs tend to be very vertically optimized toward a particular kind of analysis

Architecture description language: Difference between revisions