Architecture description language: Difference between revisions

Revision as of 06:40, 20 November 2021

Revision as of 23:12, 24 January 2022

Line 28:

As a way to overcome some of those limitations, [[Unified Modeling Language|UML]] has been indicated as a possible successor of existing ADLs. Many proposals have been presented to use or extend the UML to more properly model software architectures.<ref>{{cite web|title= Garlan_TR |url= http://www.sei.cmu.edu/library/abstracts/reports/04tr008.cfm}}</ref><ref>{{Cite book | last1 = Pérez-Martínez | first1 = J. E. | last2 = Sierra-Alonso | first2 = A. | chapter = UML 1.4 versus UML 2.0 as Languages to Describe Software Architectures | doi = 10.1007/978-3-540-24769-2_7 | title = Software Architecture | series = Lecture Notes in Computer Science | volume = 3047 | pages = 88 | year = 2004 | isbn = 978-3-540-22000-8 }}</ref>

InA fact, as highlighted in a recent2013 study conducted with practitioners,<ref name="IndustrySurvey">{{cite journal| first1 = Ivano| last1 = Malavolta| first2 = Patricia| last2 = Lago| first3 = Henry| last3 = Muccini| first4 = Patrizio| last4 = Pelliccione| first5 = Antony| last5 = Tang | year = 2013 | title = What Industry Needs from Architectural Languages: A Survey | journal = IEEE Transactions on Software Engineering | volume = 39 | issue = 6 | pages = 869–891| doi = 10.1109/TSE.2012.74| s2cid = 6383726}}</ref> whilstfound that practitioners arewere generally satisfied with the design capabilities provided byof the languagesADLS they useused, theybut arehad dissatisfiedseveral major concerns with thethem: architecturalthey languagelacked analysis features and theirthe abilitiesability to define extra-functional properties; architectural languagesthose used in practice mostly originateoriginated from industrial development insteadrather of fromthan academic research; they needed more formality and better usability are required of an architectural language.

==Characteristics==