This article provides an introduction to component modeling beyond the UML notation. It describes how I typically do component modeling, combining the non-functional and functional aspects of software to be built.
Archive for the ‘Architecture Diagrams’ Category
Diagram: A Component Modeling Example
Posted in Software Architecture, Architectural Patterns, Architecture Diagrams, Developing Architectures, software engineering, software design, tagged software engineering, uml, non-functional requirements, architectural design, Architectural Patterns, best practice, Software Architecture, software design, software modeling on June 21, 2011 | 4 Comments »
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.
Diagram: A more complex Layer Diagram (example)
Posted in Software Architecture, Architectural Patterns, Architecture Diagrams, Developing Architectures, tagged software engineering, uml, architecture overview, architectural design, best practice, Software Architecture, how to, software design, j2ee, java, technology, technology development, software modeling on June 22, 2010 | Leave a Comment »
This article describes a best practice for a layer diagram, showing a typical architecture for a server-centric application as can commonly be found in J2EE- or .NET-based Web, Service-oriented or Rich-Client applications.
Architectural Pattern: Clustering for Single-Tier Network-Centric J2EE Software Applications
Posted in Software Architecture, Architectural Patterns, Deployment Architectures, Architecture Diagrams, tagged software, architecture, software engineering, deployment diagram, network diagram, architectural design, Architectural Patterns, best practice, Software Architecture, architecture overview diagram, how to, software design, j2ee, java, technology, technology development on May 4, 2010 | Leave a Comment »
Read this article if you want to learn about the principles of clustering for a single-tier J2EE application. I know that clustering is a commonly found pattern in today’s IT world. I nevertheless wanted to cover it for those with less experience in a short entry as it is an essential pattern to know.
I outlined the objective, variations and commonly found patterns. After reading this article you should be able to distinguish between clustering and availability, know the advantages and disadvantages of clustering and be able to recognize the infrastructure impact a clustered application has.
Knowledge Nugget: What is a Tier in Software Architecture?
Posted in Software Architecture, Knowledge Nuggets, Architecture Diagrams, tagged software engineering, architecture overview, architecture overview diagram, how to, software design, j2ee, java, technology, technology development on April 27, 2010 | 2 Comments »
Read this knowledge nugget if you want to learn what a Tier is in Software Architecture and why you would use it.
Knowledge Nugget: What is a Layer in Software Architecture?
Posted in Software Architecture, Knowledge Nuggets, Architecture Diagrams, tagged software engineering, architecture overview, architecture overview diagram, how to, software design, j2ee, java, technology, technology development on April 20, 2010 | 2 Comments »
Read this knowledge nugget if you want to learn what a layer is in Software Architecture, how you can use it, how the concept works and why you would want to use it.
Diagram: A more complex Network Diagram (example)
Posted in Software Architecture, Knowledge Nuggets, Architecture Diagrams, tagged deployment diagram, network diagram, operational model, architecture overview, architectural design, how to, software design, j2ee, technology on April 13, 2010 | Leave a Comment »
In a previous article I have described the notation I am using for network diagrams in Software Architecture. This article describes an extensive sample diagram showing a possible solution with a large variety of different aspects. Read this article if you want to learn more about network diagrams in Software Architecture.
Diagram: The Network Diagram
Posted in Software Architecture, Architecture Diagrams, tagged deployment diagram, network diagram, Software Architecture, architecture overview diagram, how to, software design, j2ee, technology, technology development on April 6, 2010 | 4 Comments »
Read this article if you want to learn how I construct network diagrams, the notation and how I put it together. While the notation itself can be put to a broader use, such as infrastructure architecture and others, it is specifically geared towards Software Architecture.
