Domain-driven design (DDD)
Every software is based on a specific domain. Only by eliciting requirements, you can understand it. If well designed, the architecture reflects the domain.
Every software is based on a specific domain. Only by eliciting requirements, you can understand it. If well designed, the architecture reflects the domain.
Knowing the business domain is crucial for being a great Software Architect!
Every project has its share of risks that can impact its success or its failure.
Software Architect is a generic role.
Every system has its own architecture. But not always there is someone with the official role of Software Architect.
We all know that software architecture is something somewhat important for every software, even the simples one.
«Ouch, that website is terrible! Better find an alternative»
Maintainability is the architectural attribute that describes how easy it is to maintain a software system.
To make sure that we have designed the correct Software Architecture, we need to validate our choices against measurable properties: «it works» is not enough.