I have come to realize that successful (typical) Solution Architectures rely on only a handful of areas (let’s call them corner-stones) that need to be defined. Examples are: Non-Functional Requirements, Architectural Decisions, etc. Naturally, those areas need to be defined and thought about that much more carefully…
Archive for the ‘Documenting Architectures’ Category
The seven most important corner-stones of successful Solution Architectures
Posted in Architectural Patterns, Developing Architectures, Documenting Architectures, j2ee, jee, Software Architecture, software design, software engineering, Technical Leadership, tagged architectural design, architectural design decisions, Architectural Patterns, architecture, architecture overview, architecture overview diagram, best practice, deployment diagram, j2ee, non-functional requirements, operational model, Software Architecture, software design, software engineering, system context, technical leadership, technology on May 31, 2011 | Leave a Comment »
Diagram: Layering Software-Centric Systems (an example for a Layer Diagram)
Posted in Software Architecture, Architectural Patterns, Architecture Diagrams, Documenting Architectures, Developing Architectures, tagged software, architecture, software engineering, documentation, architectural design decisions, architecture overview, architectural design, Architectural Patterns, best practice, Software Architecture, architecture overview diagram, how to, software design, j2ee, java, technology, technology development on June 29, 2010 | 3 Comments »
Read this article if you want to learn how to layer software centric server-based system. This article is not geared towards a specific technology and the concepts presented can be applied to any type of server-centric architectures, such as J2EE or .NET It does – however – have a focus on server-side processing such as web-based, rich-client or service-oriented architectures.
Knowledge Nugget: What is Vertical Scalability (Scale Up)?
Posted in Architectural Patterns, Developing Architectures, Documenting Architectures, Knowledge Nuggets, Software Architecture, tagged architectural design, Architectural Patterns, architecture, architecture overview, best practice, deployment diagram, how to, j2ee, non-functional requirements, software, Software Architecture, software design, software engineering, technology, technology development on June 8, 2010 | Leave a Comment »
Read this knowledge nugget if you want to learn more about vertical scalability. It is a term that is more or less clear. From time to time you can – however – find different interpretations of it…
How much documentation does a Software Development project really need?
Posted in Developing Architectures, Documenting Architectures, Software Architecture, tagged architecture overview, best practice, documentation, j2ee, Software Architecture, software design, software engineering, technical leadership, technology on June 1, 2010 | Leave a Comment »
There is one thought I have been carrying around for while and wanted to share. Read this if you are interested in how much documentation a software development project really needs. I am not religiously demanding it nor am I denying the need for documentation. There is a third answer…
Network Diagrams are a very good starting point for developing a System’s Architecture
Posted in Developing Architectures, Documenting Architectures, Software Architecture, tagged architectural design, architecture, architecture overview, how to, it, j2ee, network diagram, non-functional requirements, operational model, software, software design, software engineering, technology, technology development on February 16, 2010 | Leave a Comment »
This article presents the outline of a method for developing Software Architectures. Even though developing Architectures seems to be – and to some extent is – a creative process it is important to approach it in a structured way. This ensures that all important aspects of the architecture – and therefore the client’s non-functional requirements – are covered.
On documenting Software Architectures (for Business Applications)
Posted in Developing Architectures, Documenting Architectures, Software Architecture, tagged architectural design, architectural design decisions, architecture, architecture overview, component diagram, deployment diagram, documentation, functional requirements, how to, network diagram, non-functional requirements, operational model, service model, software design, software engineering, system context, uml, user interface on February 4, 2010 | 3 Comments »
This article presents the outline of a method for developing Software Architectures. Even though developing Architectures seems to be – and to some extent is – a creative process it is important to approach it in a structured way. This ensures that all important aspects of the architecture – and therefore the client’s non-functional requirements – are covered.
Introduction to the process of developing Software Architectures
Posted in Developing Architectures, Documenting Architectures, Software Architecture, tagged architecture, how to, it, software, software design, software engineering on January 19, 2010 | 2 Comments »
This article presents the outline of a method for developing Software Architectures. Even though developing Architectures seems to be – and to some extent is – a creative process it is important to approach it in a structured way. This ensures that all important aspects of the architecture – and therefore the client’s non-functional requirements – are covered.
