0% found this document useful (0 votes)
43 views3 pages

Architecture - Q and A

Common architecture Q and A for senior software engineer interview

Uploaded by

Benny Susanto
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
43 views3 pages

Architecture - Q and A

Common architecture Q and A for senior software engineer interview

Uploaded by

Benny Susanto
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Table of Contents

Software Architecture......................................................................................................................2
Software Architecture

Q: What is a software architecture?


A: Some definitions of software architecture

References:

“Fundamental concepts or properties of a system in its environment embodied in its elements,


relationships, and in the principles of its design and evolution” (IEEE 42010).

“Software architecture is the collection of fundamental decisions about a software product or


solution designed to meet the project’s quality attributes (the architectural requirements). The
architecture includes the main components, their main attributes, and their collaborations
(their interactions and behavior) to meet the quality attributes. Architecture can, and usually
should, be expressed in several levels of abstraction, where the number of levels depends on
the project’s size and complexity.

Looking at this definition, we can draw some conclusions about software architecture:

 Architecture occurs early. It should represent the set of earliest design decisions
 that are both hardest to change and most critical to get right.
 Architecture is an attribute of every system. Whether or not its design was intentional,
every system has an architecture.
 Architecture breaks a system into components and sets boundaries. It doesn’t need to
describe all the components, but the architecture usually deals with the major
components of the solution and their interfaces. Architecture is about relationships and
component interactions. We’re interested in the behaviors of the individual components
as they can be discerned from other components interacting with them. The
architecture doesn’t have to describe the complete characteristics of the components; it
mainly deals with their interfaces and other interactions.
 Architecture explains the rationale behind the choices. It’s important to understandthe
reasoning as well as the implications of the decisions made in the architecture because
their impact on the project is large. Also, it can be beneficial to understand what
alternatives were weighed and abandoned. This may be important for future reference,
if and when things need to be reconsidered, and for anyone new to the project who
needs to understand the situation.
 There isn’t a single structure that is the architecture. We need to look at the archtecture
from different directions or viewpoints to fully understand it. One diagram, or even a
handful, isn’t enough to be considered an architecture.”
(SOA Patterns)
An architecture is the set of significant decisions about the organization of a software system,
the selection of the structural elements and their interfaces by which the system is composed,
together with their behavior as specified in the collaborations among those elements, the
composition of these structural and behavioral elements into progressively larger subsystems,
and the architectural style that guides this organization, these elements and their interfaces,
their collaborations, and their composition (Applying UML and Patterns)
The word “architecture” is often used in the context of something at a high level that is
divorced from the lower-level details, whereas “design” more often seems to imply structures
and decisions at a lower level. But this usage is nonsensical when you look at what a real
architect does. (Clean Architecture)

You might also like