Software architecture central concern, key decisions
Shankar Nayak Bhukya, Suresh Pabboju
Abstract
Shankar Nayak Bhukya, Suresh Pabboju
Abstract
If the applications software supporting your services and essential business systems or the software in your products, is becoming bigger and messier, it is time to consider whether software architecture ought to tbe a core competency of your business. So, it is fair to ask - what is software architecture?” This paper seeks to answer that question, not in terms of a simple definition, but by helping us understand the full nature of software architecture. First, we explore the concerns that are uniquely, or most appropriately, addressed by software architecture. Next, we consider the decisions and descriptions that characterize and formulate architecture. We present our layered mode of software architecture, which both organizes architectural decision. Finally, we consider how to communicate the architecture. With this fundamental understanding of what software architecture is, architects can turn to the question of how to create architectures that are good, right and successful, and managers can consider how to hire and develop great architects.
A significance statement is not available in the OpenAlex record.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
If the applications software supporting your services and essential business systems or the software in your products, is becoming bigger and messier, it is time to consider whether software architecture ought to tbe a core competency of your business. So, it is fair to ask - what is software architecture?” This paper seeks to answer that question, not in terms of a simple definition, but by helping us understand the full nature of software architecture. First, we explore the concerns that are uniquely, or most appropriately, addressed by software architecture. Next, we consider the decisions and descriptions that characterize and formulate architecture. We present our layered mode of software architecture, which both organizes architectural decision. Finally, we consider how to communicate the architecture. With this fundamental understanding of what software architecture is, architects can turn to the question of how to create architectures that are good, right and successful, and managers can consider how to hire and develop great architects.
Key concepts: Resource-oriented architecture, Software architecture description, Computer science, Reference architecture, Software architecture, Architecture, Software engineering, Architecture tradeoff analysis method