Please enable JavaScript.
Coggle requires JavaScript to display documents.
Solution Related Architectures the fundamental organization of a system…
Solution Related Architectures the fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution
Modular Architecture The technical architecture was somewhat simpler - often a single physical node and much of the data processing was batch driven and managed by job control software, each executable program tended to be limited in functionality
Loosely Coupled Architecture these are components that can be updated or even replaced without significantly impacting on others. Dependency is typically one way or acyclic
Tightly coupled Modules changing one module requires that others need to be updated. Dependencies typically exist in both direction on any pair of modules otherwise known as cyclic or circular dependency
-
-
-
-
Communication and Interoperation Patterns an architecture composed of, or assembled from, discrete components or sub-systems need those components to communicate and interoperate. Some basic patterns are evident at both logical and physical views of business, application and infrastructure architectures
-
-
Service-oriented architecture is fundamentally about how components can be defined by the services they require as a service consumer or client and provided as a service provider - server. These components are typically as de-coupled as possible in all aspects.
- Service providers to register their services with a service registry held by the hub
- Service consumers to look up or discover service providers as required
- a temporary point to point connection may be setup between them, across which they communicate directly
- the interaction are conducted through the hub acting as a broker
Enterprise Architecture EA is typically the highest level and most holistic form of architecture developed and evolved about the organisation over a strategic time frame.
- a context or environment within which they exist
- a mission, the reason why they exist
- a set of products and or services that they provide to a customer base
- an organisational structure with individuals fulfilling roles
- a set of processes that they execute to conduct their operating model
-
Strategy versus tactics
A vision of what their future context or environment is likely to be and what they want to be in the future to remain relevant to that future
The need therefore to evolve through changes to meet the challenges presented by their constantly changing context or environment
-
-
EA processes, content models, organisation and frameworks
-
-
-
-
Architecture Principles fill the gap between high-level strategic intentions and concrete design. Principles can be defined that relate to any domain or aspect
- business units are autonomous
- routine tasks are automated - relates to business and application domains
- Primary business processes are not disturbed by implementation of changes - relates to all domains
- applications have a common look and feel - relates to application design
- only in response to business needs are changes to IT systems made, is actually an application and technology domain-focused principle
Software Architecture is fundamentally concerned with the purpose and structure of software application, including software components, that may be considered to deliver platform services within the infrastructure architecture.
-
Structural constraints presented by platform technologies chosen for the solutions that already exist or need to be procured
Identifying and employing appropriate logical and physical design patterns that encourage robust software design and implementation
-
-
-
-
-