Software architectural model: Difference between revisions

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Revision as of 10:43, 26 February 2025 edit Citation bot (talk \| contribs) Bots 5,866,541 edits Add: isbn, doi, authors 1-1. Removed parameters. Some additions/deletions were parameter name changes. Upgrade ISBN10 to 13. \| Use this bot. Report bugs. \| Suggested by Headbomb \| Linked from Wikipedia:WikiProject_Academic_Journals/Journals_cited_by_Wikipedia/Sandbox2 \| #UCB_webform_linked 1053/1244 ← Previous edit		Latest revision as of 01:13, 28 May 2025 edit undo OAbot (talk \| contribs) Bots 643,717 edits m Open access bot: url-access updated in citation with #oabot.
(2 intermediate revisions by 2 users not shown)
Line 6: }} An '''architectural model''' (in [[software]]) contains several diagrams representing static properties or dynamic (behavioral) properties of the software under design.<ref>{{Citation \|last=Hasselbring \|first=Wilhelm \|title=Software Architecture: Past, Present, Future \|date=2018 \|work=The Essence of Software Engineering \|pages=169–184 \|url=https://doi.org/10.1007/978-3-319-73897-0_10 \|access-date=2025-02-10 \|place=Cham \|publisher=Springer International Publishing \|doi=10.1007/978-3-319-73897-0_10 \|isbn=978-3-319-73896-3\|url-access=subscription }}</ref><ref>{{Cite web \|title=About the Unified Modeling Language Specification Version 2.5.1 \|url=https://www.omg.org/spec/UML/2.5.1/About-UML \|access-date=2025-02-10 \|website=www.omg.org}}</ref><ref>{{Cite ~~journal~~book \|last1=Hilliard \|first1=Rich \|last2=Malavolta \|first2=Ivano \|last3=Muccini \|first3=Henry \|last4=Pelliccione \|first4=Patrizio \|~~date=August 2012 \|title~~chapter=On the Composition and Reuse of Viewpoints across Architecture Frameworks \|~~url~~date=~~https://doi.org/10.1109/wicsa-ecsa.212.21~~August 2012 \|~~journal~~title=2012 Joint Working IEEE/IFIP Conference on Software Architecture and European Conference on Software Architecture \|chapter-url=https://doi.org/10.1109/wicsa-ecsa.212.21 \|publisher=IEEE \|pages=131–140 \|doi=10.1109/wicsa-ecsa.212.21\|isbn=978-1-4673-2809-8 }}</ref> The diagrams represent different [[4+1 architectural view model\|viewpoints]] of the system ~~and~~at the appropriate scope of analysis. The diagrams are created by using available standards in which the primary aim is to illustrate a specific set of tradeoffs inherent in the structure and design of a system or ecosystem. [[Software architect]]s utilize architectural models to facilitate communication and obtain peer feedback. Some key elements in a software architectural model include: