Relevant bibliographies by topics / Software architecture

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Software architecture'

Author: Grafiati
Published: 4 June 2021
Last updated: 25 July 2025

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software architecture.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Software architecture"

1

WOODSIDE, C. M. "SOFTWARE RESOURCE ARCHITECTURE." International Journal of Software Engineering and Knowledge Engineering 11, no. 04 (2001): 407–29. http://dx.doi.org/10.1142/s0218194001000608.

Full text
Abstract:
Performance is determined by a system's resources and its workload. Some of the resources are software resources which are an aspect of the software architecture; some of them are even created by the software behaviour. This paper describes software resources and resource architecture, and shows how resource architecture can be determined from software architecture and behaviour. The resource architecture is distinct from views of software architecture which describe software components, but it is related to the so-called "execution view" of architecture. The paper considers how resource archi
APA, Harvard, Vancouver, ISO, and other styles
2

Abuseta, Yousef. "Towards a Generic Software Architecture for IoT Systems." International Journal of Software Engineering & Applications 15, no. 6 (2024): 01–16. https://doi.org/10.5121/ijsea.2024.15601.

Full text
Abstract:
The complexity of IoT, owing to the inherent distributed and dynamic nature of such systems, brings more challenges to the software development process. A vast number of devices with different communication protocols and data formats is involved and needs to be connected and exchange data with each other in a seamless manner. Traditional software architectures fall short of addressing the requirements of IoT systems and, therefore, a new approach to software architecture is required. This paper presents an attempt to lay out the foundation for a quality attribute driven software architecture f
APA, Harvard, Vancouver, ISO, and other styles
3

Medvidovic, Nenad, Eric M. Dashofy, and Richard N. Taylor. "The Role of Middleware in Architecture-Based Software Development." International Journal of Software Engineering and Knowledge Engineering 13, no. 04 (2003): 367–93. http://dx.doi.org/10.1142/s0218194003001330.

Full text
Abstract:
Software architectures promote development focused on modular functional building blocks (components), their interconnections (configurations), and their interactions (connectors). Since architecture-level components often contain complex functionality, it is reasonable to expect that their interactions will be complex as well. Middleware technologies such as CORBA, COM, and RMI provide a set of predefined services for enabling component composition and interaction. However, the potential role of such services in the implementations of software architectures is not well understood. In practice
APA, Harvard, Vancouver, ISO, and other styles
4

Siedashev, Oleh. "DETERMINATION OF SOFTWARE ARCHITECTURE (SOA) AND MICROSERVICE ARCHITECTURE (MSA) USAGE CRITERIA." Computer Science and Cybersecurity, no. 2 (December 30, 2024): 41–50. https://doi.org/10.26565/2519-2310-2024-2-04.

Full text
Abstract:
In modern software development, one of the key tasks is to choose the appropriate architecture for the system in the early stages of its design. This article examines two popular software architecture approaches: service-oriented architecture (SOA) and microservice architecture (MSA). Based on the analysis of architectural features, advantages and disadvantages of these approaches, the criteria that influence the choice of an architectural model depending on the specifics of the system are investigated. Microservice architecture, due to its independence and the possibility of rapid scaling, is
APA, Harvard, Vancouver, ISO, and other styles
5

Ulichev, Oleksandr, Oleksandr Dorenskyi, and Victor Kulahin. "Innovative Solutions and Benefits of Microservice Architecture for Software Products." Central Ukrainian Scientific Bulletin. Technical Sciences 1, no. 10(41) (2024): 16–29. https://doi.org/10.32515/2664-262x.2024.10(41).16-29.

Full text
Abstract:
The rapid advancement of technology and increasing market competition compel businesses to adapt swiftly by implementing new features and services to meet user demands. Traditional monolithic software architectures often hinder this agility due to challenges in scalability and maintenance. This article aims to analyze microservice architecture to solve these challenges, exploring its historical development, current trends, practical implementation aspects, and comparison with alternative architectural styles such as modulith architecture. The study examines the limitations of monolithic archit
APA, Harvard, Vancouver, ISO, and other styles
6

McGregor, John D. "Software Architecture." Journal of Object Technology 3, no. 5 (2004): 65. http://dx.doi.org/10.5381/jot.2004.3.5.c7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Anderson, Bruce, Mary Shaw, Larry Best, and Kent Beck. "Software architecture." ACM SIGPLAN Notices 28, no. 10 (1993): 356–59. http://dx.doi.org/10.1145/167962.165922.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Ponnala Gangadhar Adepu, Ramesh. "Modeling Software Architecture with UML." International Journal of Science and Research (IJSR) 1, no. 3 (2012): 21–26. http://dx.doi.org/10.21275/ijsr12120316.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Roško, Zdravko. "Business Applications Architecture Model Based on Software Product Line Approach." Research Papers Faculty of Materials Science and Technology Slovak University of Technology 21, Special-Issue (2013): 90–97. http://dx.doi.org/10.2478/rput-2013-0015.

Full text
Abstract:
Abstract Software product line architecture is one of the most important artifacts defined at the early stage of a product line development process. Since the rest of the products are developed based on the initial product line architecture, it is of high importance to ensure the architecture stability by enabling the software’s evolution possibilities. Industrial evidence shows that companies spend more resources on maintaining and evolving their architecture and products than on the initial development of them. Hence, there is a need for flexible software architecture that stays stable as th
APA, Harvard, Vancouver, ISO, and other styles
10

Sarma, U. V. R., Neelakantam Pavani Pavani, and P. Premchand. "Building Software Architecture using Architectural Design Patterns." International Journal of Science and Engineering Applications 2, no. 4 (2013): 71–77. http://dx.doi.org/10.7753/ijsea0204.1004.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Software architecture"

1

Bahtiyar, Muhammed Yasin. "Software Architecture Checker." Thesis, Växjö University, School of Mathematics and Systems Engineering, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:vxu:diva-2294.

Full text
Abstract:
<p>By the increasing needs of software industry, software systems became more complex constructions than ever before. As a result of increasing complexity in software systems, functional decomposition of these systems gains the status of the most important aspect in the software development process. Dividing problems to sub-problems and producing specific solutions for divided parts makes it easier to solve the main problem.</p><p>Component Based Software Engineering is a way of developing software systems that consists of logically or functionally decomposed components which integrated to eac
APA, Harvard, Vancouver, ISO, and other styles
2

Mårtensson, Frans, and Per Jönsson. "Software Architecture Simulation." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4087.

Full text
Abstract:
A software architecture is one of the first steps towards a software system. A software architecture can be designed in different ways. During the design phase, it is important to select the most suitable design of the architecture, in order to create a good foundation for the system. The selection process is performed by evaluating architecture alternatives against each other. We investigate the use of continuous simulation of a software architecture as a support tool for architecture evaluation. For this purpose, we study a software architecture of an existing software system in an experimen
APA, Harvard, Vancouver, ISO, and other styles
3

Barnes, Jeffrey M. "Software Architecture Evolution." Research Showcase @ CMU, 2013. http://repository.cmu.edu/dissertations/291.

Full text
Abstract:
Many software systems eventually undergo changes to their basic architectural structure. Such changes may be prompted by new feature requests, new quality attribute requirements, changing technology, or other reasons. Whatever the causes, architecture evolution is commonplace in real-world software projects. Today’s software architects, however, have few techniques to help them plan such evolution. In particular, they have little assistance in planning alternatives, making trade-offs among these different alternatives, or applying best practices for particular domains. To address this, we have
APA, Harvard, Vancouver, ISO, and other styles
4

Hatch, Andrew. "Software architecture visualisation." Thesis, Durham University, 2004. http://etheses.dur.ac.uk/3040/.

Full text
Abstract:
Tracing the history of software engineering reveals a series of abstractions. In early days, software engineers would construct software using machine code. As time progressed, software engineers and computer scientists developed higher levels of abstraction in order to provide tools to assist in building larger software systems. This has resulted in high-level languages, modelling languages, design patterns, and software architecture. Software architecture has been recognised as an important tool for designing and building software. Some research takes the view that the success or failure of
APA, Harvard, Vancouver, ISO, and other styles
5

Pei, Breivold Hongyu. "Software Architecture Evolution and Software Evolvability." Licentiate thesis, Mälardalen University, School of Innovation, Design and Engineering, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-4540.

Full text
Abstract:
<p>Software is characterized by inevitable changes and increasing complexity, which in turn may lead to huge costs unless rigorously taking into account change accommodations. This is in particular true for long-lived systems. For such systems, there is a need to address evolvability explicitly during the entire lifecycle, carry out software evolution efficiently and reliably, and prolong the productive lifetime of the software systems.</p><p>In this thesis, we study evolution of software architecture and investigate ways to support this evolution.           The central theme of the thesis is
APA, Harvard, Vancouver, ISO, and other styles
6

Svahnberg, Mikael. "Supporting Software Architecture Evolution." Doctoral thesis, Ronneby : Blekinge Institute of Technology, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00232.

Full text
Abstract:
Today it is more a rule than an exception that software systems have a lifecycle of more than several years. Hence, software evolution is inevitable. During the life span of a software system the domain in which the system is working evolves and changes. This causes changes to the software system, and the software system may also be evolved to satisfy new markets. The ability to evolve gracefully, and thus the long-term success of a software system, is to a large extent governed by its software architecture and the ability of the software architecture to fulfil requirements on quality attribut
APA, Harvard, Vancouver, ISO, and other styles
7

Ström, David. "Purposes of Software Architecture Design." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2830.

Full text
Abstract:
Software architecture design as an engineering field has evolved greatly during the last 15 years, which is evident by the number of methods, styles, patterns, and guidelines available for its practitioners in industry. This paper takes a closer look at the purposes behind this field to reveal the level of discrepancy in pursued purposes between industrial practitioners and published methods for software architecture design. In our research surveys of architecture design methods and of purposes at a number of industrial practitioners resulted in two sets of purposes which were eventually compa
APA, Harvard, Vancouver, ISO, and other styles
8

Cunningham, Hamish. "Software architecture for language engineering." Thesis, University of Sheffield, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.324440.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Wermelinger, Miguel Alexandre. "Specification of software architecture reconfiguration." Doctoral thesis, FCT - UNL, 1999. http://hdl.handle.net/10362/1137.

Full text
Abstract:
In the past years, Software Architecture has attracted increased attention by academia and industry as the unifying concept to structure the design of complex systems. One particular research area deals with the possibility of reconfiguring architectures to adapt the systems they describe to new requirements. Reconfiguration amounts to adding and removing components and connections, and may have to occur without stopping the execution of the system being reconfigured. This work contributes to the formal description of such a process. Taking as a premise that a single formalism hardly ever sati
APA, Harvard, Vancouver, ISO, and other styles
10

Väisänen, T. (Toni). "Applied software architecture on Graphingwiki." Bachelor's thesis, University of Oulu, 2017. http://urn.fi/URN:NBN:fi:oulu-201710042937.

Full text
Abstract:
Graphingwiki extends the wikiengine MoinMoin by providing tools for visualizing the interconnections between the wiki pages. The extension has been used for collaborative dependency mapping. Graphingwiki can be considered a legacy system, because there is no documentation available. This thesis focuses on applied software archeology to gain understanding on the implementation in order to support decision-making as regards to its further development. An overview of the system was mapped by using code execution tracing and by reading the code manually. Performance of the Graphingwiki graph gener
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software architecture"

1

Biffl, Stefan, Elena Navarro, Welf Löwe, Marjan Sirjani, Raffaela Mirandola, and Danny Weyns, eds. Software Architecture. Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-86044-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Scandurra, Patrizia, Matthias Galster, Raffaela Mirandola, and Danny Weyns, eds. Software Architecture. Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-031-15116-3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Gerostathopoulos, Ilias, Grace Lewis, Thais Batista, and Tomáš Bureš, eds. Software Architecture. Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-031-16697-6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Drira, Khalil, ed. Software Architecture. Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-39031-9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Cuesta, Carlos E., David Garlan, and Jennifer Pérez, eds. Software Architecture. Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-030-00761-4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Weyns, Danny, Raffaela Mirandola, and Ivica Crnkovic, eds. Software Architecture. Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-23727-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Lopes, Antónia, and Rogério de Lemos, eds. Software Architecture. Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-65831-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Crnkovic, Ivica, Volker Gruhn, and Matthias Book, eds. Software Architecture. Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-23798-0.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Tekinerdogan, Bedir, Uwe Zdun, and Ali Babar, eds. Software Architecture. Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-48992-6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Bures, Tomas, Laurence Duchien, and Paola Inverardi, eds. Software Architecture. Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-29983-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software architecture"

1

Vogel, Oliver, Ingo Arnold, Arif Chughtai, and Timo Kehrer. "Architectures and Architecture Disciplines (WHAT)." In Software Architecture. Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-19736-9_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Gebhardt, Friedrich, Angi Voß, Wolfgang Gräther, and Barbara Schmidt-Belz. "Software Architecture." In Reasoning with Complex Cases. Springer US, 1997. http://dx.doi.org/10.1007/978-1-4615-6233-7_18.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Doornbos, Richard, and Sjir van Loo. "Software Architecture." In From scientific instrument to industrial machine. Springer Netherlands, 2012. http://dx.doi.org/10.1007/978-94-007-4147-8_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Dooley, John F. "Software Architecture." In Software Development, Design and Coding. Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-3153-1_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Budgen, David. "Software Architecture." In Software Design. Chapman and Hall/CRC, 2020. http://dx.doi.org/10.1201/b21883-9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Jalote, Pankaj. "Software Architecture." In A Concise Introduction to Software Engineering. Springer London, 2008. http://dx.doi.org/10.1007/978-1-84800-302-6_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Dooley, John F., and Vera A. Kazakova. "Software Architecture." In Software Development, Design, and Coding. Apress, 2024. http://dx.doi.org/10.1007/979-8-8688-0285-0_7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Streekmann, Niels. "Software Architecture." In Clustering-Based Support for Software Architecture Restructuring. Vieweg+Teubner Verlag, 2012. http://dx.doi.org/10.1007/978-3-8348-8675-0_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Dooley, John. "Software Architecture." In Software Development and Professional Practice. Apress, 2011. http://dx.doi.org/10.1007/978-1-4302-3802-7_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Laplante, Phillip A., and Mohamad Kassab. "Software Architecture." In What Every Engineer Should Know about Software Engineering, 2nd ed. CRC Press, 2022. http://dx.doi.org/10.1201/9781003218647-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software architecture"

1

Homay, Aydin, and Mario de Sousa. "Axiomatic Software Architecture." In 2025 IEEE 22nd International Conference on Software Architecture Companion (ICSA-C). IEEE, 2025. https://doi.org/10.1109/icsa-c65153.2025.00008.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Cavalcante, Everton, and Thais Batista. "Using Software Architecture Descriptions to Detect Architectural Smells at Design Time." In Congresso Ibero-Americano em Engenharia de Software. Sociedade Brasileira de Computação, 2023. http://dx.doi.org/10.5753/cibse.2023.24697.

Full text
Abstract:
Architectural smells are decisions made at the software architecture level, whether intentional or not, that may negatively impact the quality of a software system. In the literature, architectural smells are identified mainly by relying on the source code or other implementation artifacts. However, architectural smells could be detected at design time, even before employing implementation efforts and preventing them from being reflected at the system implementation. This research investigates how software architecture descriptions realized through architecture description languages (ADLs) can
APA, Harvard, Vancouver, ISO, and other styles
3

E. U. Silva, Douglas, Roberto A. Bittencourt, and Rodrigo T. Calumby. "Clustering Similarity Measures for Architecture Recovery of Evolving Software." In VII Workshop on Software Visualization. Sociedade Brasileira de Computação - SBC, 2019. http://dx.doi.org/10.5753/vem.2019.7583.

Full text
Abstract:
Automated software architecture recovery of module views from source code is a challenging research issue. Different similarity measures are used to evaluate clustering algorithms in the software architecture recovery of module views. However, few studies seek to evaluate whether such measures accurately capture the similarities between two clusterings. This work presents an evaluation of six clustering similarity measures through the use of intrinsic quality and stability measures and the use of ground truth architectures proposed by developers. The results suggest that the MeCl metric is the
APA, Harvard, Vancouver, ISO, and other styles
4

Garlan, David, and Mary Shaw. "Software architecture." In the 19th ACM SIGSOFT symposium and the 13th European conference. ACM Press, 2011. http://dx.doi.org/10.1145/2025113.2025116.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Taylor, Richard N. "Software architecture." In the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering. ACM Press, 2009. http://dx.doi.org/10.1145/1595696.1595754.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Garlan, David. "Software architecture." In the conference. ACM Press, 2000. http://dx.doi.org/10.1145/336512.336537.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Anderson, Bruce, Mary Shaw, Larry Best, and Kent Beck. "Software architecture." In the eighth annual conference. ACM Press, 1993. http://dx.doi.org/10.1145/165854.165922.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Medvidovic, Nenad, and Richard N. Taylor. "Software architecture." In the 32nd ACM/IEEE International Conference. ACM Press, 2010. http://dx.doi.org/10.1145/1810295.1810435.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Sosa, Manuel E., Tyson Browning, and Ju¨rgen Mihm. "Studying the Dynamics of the Architecture of Software Products." In ASME 2007 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference. ASMEDC, 2007. http://dx.doi.org/10.1115/detc2007-34761.

Full text
Abstract:
This paper reports on an exploratory study of how the architecture of a software product evolves over time. Because software is embedded in many of today’s complex products, and it is prone to relatively rapid change, it is instructive to study software architecture evolution for general insights into product design. We use metrics to capture the intrinsic complexity of software architectures as they evolve through successive generations (version releases). We introduce a set of product representations and metrics that take into account two important features used to manage the complexity in s
APA, Harvard, Vancouver, ISO, and other styles
10

Masuda, Satoshi, Jon Hagar, Yasuharu Nishi, and Kazuhiro Suzuki. "Software Test Architecture Definition by Analogy with Software Architecture." In 2022 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW). IEEE, 2022. http://dx.doi.org/10.1109/icstw55395.2022.00050.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software architecture"

1

Khare, Rohit. Decentralized Software Architecture. Defense Technical Information Center, 2002. http://dx.doi.org/10.21236/ada441133.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Bachmann, Felix, Len Bass, Jeromy Carriere, et al. Software Architecture Documentation in Practice: Documenting Architectural Layers. Defense Technical Information Center, 2000. http://dx.doi.org/10.21236/ada377988.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Wood, William G., Mario Barbacci, Paul Clements, Steve Palmquist, and Huei-Wan Ang. DoD Architecture Framework and Software Architecture Workshop Report. Defense Technical Information Center, 2003. http://dx.doi.org/10.21236/ada416453.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Bachmann, Felix, Len Bass, Paul Clements, David Garlan, and James Ivers. Documenting Software Architecture: Documenting Behavior. Defense Technical Information Center, 2002. http://dx.doi.org/10.21236/ada399792.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Bachmann, Felix, Len Bass, Paul Clements, David Garlan, and James Ivers. Documenting Software Architecture: Documenting Interfaces. Defense Technical Information Center, 2002. http://dx.doi.org/10.21236/ada403788.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Hamilton, Jr, Murtagh John A., and Jeanne L. Enabling Interoperability Via Software Architecture. Defense Technical Information Center, 2000. http://dx.doi.org/10.21236/ada458021.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Clements, Paul C., and Linda M. Northrop. Software Architecture: An Executive Overview. Defense Technical Information Center, 1996. http://dx.doi.org/10.21236/ada305470.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Clements, Paul C. Coming Attractions in Software Architecture. Defense Technical Information Center, 1996. http://dx.doi.org/10.21236/ada309156.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Bass, Len, Bonnie E. John, and Jesse Kates. Achieving Usability Through Software Architecture. Defense Technical Information Center, 2001. http://dx.doi.org/10.21236/ada387874.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Auguston, Mikhail. Software Architecture Built from Behavior Models. Defense Technical Information Center, 2009. http://dx.doi.org/10.21236/ada502640.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software architecture' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography