{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,10,16]],"date-time":"2025-10-16T03:49:16Z","timestamp":1760586556904,"version":"3.41.0"},"reference-count":6,"publisher":"Association for Computing Machinery (ACM)","issue":"2","license":[{"start":{"date-parts":[[2011,3,14]],"date-time":"2011-03-14T00:00:00Z","timestamp":1300060800000},"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":["SIGSOFT Softw. Eng. Notes"],"published-print":{"date-parts":[[2011,3,14]]},"abstract":"<jats:p>When the Agile software development became popular in software development communities, some engineers thought that software architecture would die out. But no matter what, a software project will have an architecture, whether documented intentionally or created on the fly. Software Architecture should enable Agile development methods by itself being Agile. But how? In this paper, I will discuss my experience of doing architecture in an Agile way and in a non-Agile way. Have an architecture that follows the Agile principles is key to obtaining success in an Agile development environment.<\/jats:p>","DOI":"10.1145\/1943371.1943388","type":"journal-article","created":{"date-parts":[[2011,3,15]],"date-time":"2011-03-15T16:38:06Z","timestamp":1300207086000},"page":"1-3","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":3,"title":["Agile software architecture"],"prefix":"10.1145","volume":"36","author":[{"given":"Christine","family":"Miyachi","sequence":"first","affiliation":[{"name":"Xerox Corporation"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2011,3,14]]},"reference":[{"key":"e_1_2_1_1_1","unstructured":"http:\/\/agilemanifesto.org\/  http:\/\/agilemanifesto.org\/"},{"key":"e_1_2_1_2_1","unstructured":"http:\/\/www.informit.com\/articles\/article.aspx?p=471929  http:\/\/www.informit.com\/articles\/article.aspx?p=471929"},{"key":"e_1_2_1_3_1","unstructured":"http:\/\/www.agilemodeling.com\/essays\/agileArchitecture.htm  http:\/\/www.agilemodeling.com\/essays\/agileArchitecture.htm"},{"key":"e_1_2_1_4_1","unstructured":"http:\/\/en.wikipedia.org\/wiki\/File:Interative_development_model_V2.jpg  http:\/\/en.wikipedia.org\/wiki\/File:Interative_development_model_V2.jpg"},{"key":"e_1_2_1_5_1","unstructured":"http:en.wikipedia.org\/wiki\/File:Waterfall_model.svg  http:en.wikipedia.org\/wiki\/File:Waterfall_model.svg"},{"key":"e_1_2_1_6_1","unstructured":"http:\/\/www.agilearchitect.org\/agile\/principles.htm  http:\/\/www.agilearchitect.org\/agile\/principles.htm"}],"container-title":["ACM SIGSOFT Software Engineering Notes"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1943371.1943388","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1943371.1943388","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T12:23:21Z","timestamp":1750249401000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1943371.1943388"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2011,3,14]]},"references-count":6,"journal-issue":{"issue":"2","published-print":{"date-parts":[[2011,3,14]]}},"alternative-id":["10.1145\/1943371.1943388"],"URL":"https:\/\/doi.org\/10.1145\/1943371.1943388","relation":{},"ISSN":["0163-5948"],"issn-type":[{"type":"print","value":"0163-5948"}],"subject":[],"published":{"date-parts":[[2011,3,14]]},"assertion":[{"value":"2011-03-14","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}