{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:31:10Z","timestamp":1750307470894,"version":"3.41.0"},"reference-count":1,"publisher":"Association for Computing Machinery (ACM)","issue":"9","license":[{"start":{"date-parts":[[2010,9,1]],"date-time":"2010-09-01T00:00:00Z","timestamp":1283299200000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["Queue"],"published-print":{"date-parts":[[2010,9]]},"abstract":"<jats:p>\n            The ever-increasing might of modern computers has made it possible to solve problems once thought too difficult to tackle. Far too often, however, the systems for these functionally complex problem spaces have overly complicated architectures. In this article I use the term\n            <jats:italic>architecture<\/jats:italic>\n            to refer to the overall macro design of a system rather than the details of how the individual parts are implemented. The system architecture is what is behind the scenes of usable functionality, including internal and external communication mechanisms, component boundaries and coupling, and how the system will make use of any underlying infrastructure (databases, networks, etc.). The architecture is the \"right\" answer to the question: how does this system work?\n          <\/jats:p>","DOI":"10.1145\/1854039.1862187","type":"journal-article","created":{"date-parts":[[2020,8,31]],"date-time":"2020-08-31T13:23:23Z","timestamp":1598880203000},"page":"30-39","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":0,"title":["Tackling Architectural Complexity with Modeling"],"prefix":"10.1145","volume":"8","author":[{"given":"Kevin","family":"Montagne","sequence":"first","affiliation":[],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2010,9]]},"reference":[{"edition":"2","volume-title":"Object-oriented Analysis and Design with Applications","author":"Booch G.","key":"e_1_2_1_1_1"}],"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1854039.1862187","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1854039.1862187","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T12:08:42Z","timestamp":1750248522000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1854039.1862187"}},"subtitle":["Component models can help diagnose architectural problems in both new and existing systems."],"short-title":[],"issued":{"date-parts":[[2010,9]]},"references-count":1,"journal-issue":{"issue":"9","published-print":{"date-parts":[[2010,9]]}},"alternative-id":["10.1145\/1854039.1862187"],"URL":"https:\/\/doi.org\/10.1145\/1854039.1862187","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"type":"print","value":"1542-7730"},{"type":"electronic","value":"1542-7749"}],"subject":[],"published":{"date-parts":[[2010,9]]},"assertion":[{"value":"2010-09-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}