Software Architecture: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 68: Line 68:
* Next Architecture: https://www.oreilly.com/ideas/3-emerging-trends-tech-leaders-should-watch#next-architecture
* Next Architecture: https://www.oreilly.com/ideas/3-emerging-trends-tech-leaders-should-watch#next-architecture
* Banking startup that uses Java, deploys on AWS, and builds "microliths" https://www.infoq.com/podcasts/cloud-based-banking-startup-java
* Banking startup that uses Java, deploys on AWS, and builds "microliths" https://www.infoq.com/podcasts/cloud-based-banking-startup-java
* [[Architectural Decision Records]]
=TODO=
=TODO=
* Clean Architecture https://www.amazon.com/Clean-Architecture-Craftsmans-Software-Structure/dp/0134494164/
* Clean Architecture https://www.amazon.com/Clean-Architecture-Craftsmans-Software-Structure/dp/0134494164/

Revision as of 21:01, 3 July 2023

External

Internal

Overview

The art of software architecture belongs under the larger domain of software engineering, alongside software development.

Subjects

Concepts

Software Architecture

Evolutionary Software Architecture

Evolutionary software architecture is the sum of software engineering practices and techniques, as well as structural architectural patterns that allow incremental guided change across multiple dimensions of a software system. The dimensions in question include first and foremost the domain, but also multiple other architectural characteristics the system designers deem as important.

Requirements

Functional requirements (related to domain) and non-functional requirements, associated to architectural characteristics.

Domain

Architectural Characteristics

Framework

Platform

Architectural Governance

Definition. TO DO.

Architectural governance includes code reviews, architecture review boards (manual, bureaucracy).

Change

Incremental change.

Architectural Patterns

Coupling and Cohesion

Referred by:

Organizatorium

TODO