Please enable JavaScript.
Coggle requires JavaScript to display documents.
solution related architecture - Coggle Diagram
solution related architecture
architecture
ISO 42010:2011 - organisation of a system embodied in its components, their relationship to each other and to the environment and the principles guiding its design and evolution
modular architecture
monolithic - where data input/output / processing, UI not separated
tech architecture simpler
data processing - batch driven / job control software
change in business rule might require multiple changesc
config & version management key
tightly coupled
loosely coupled architecture
coupling= level of dependency between 2 software components
interface abstractly defined separately from implementation code
allows implementation of the module to be updated, replaced or dynamically interchanged - providing interface supported
cohesion = how closely modular elements need to operate / changed together
coarse grained components = application programming interface = API
interoperation
point to point
most direct / simplest pattern
tightly coupled
components linked logical / physically
prob - multiple point to point
hub & spoke
significant no components
set of P2P plus hub component
service-oriented
how components defined by services required (service consumer/client) and provided (SP/server)
how BUs organised - allows for outsource
broker hub - service bus - SP registry
can be temp P2P / hub as broker
Enterprise
long term strategic focus but delivers short term tactical changes
tactical changes = people structures / business processes / IT systems
typically uses 4 domains
business architecture
data and/or information architecture
application architecture
infrastructure / technology architecture
each contain subset / are independent + have overlaps
determines
org
process
content
frameworks
The Open Group Architecture Framework (TOGAF)
Zachmann Framework for EA
US gov - Federated EA framework (FEAF)
US Defense - DODAF
UK MOD - MODAF
gov
principles & policies that constrain change = ensure strategic obj met
principles
general rules & guidelines, intended to be enduring but seldom amended that inform and support the way in which an organisation sets about fulfilling its mission - TOGAF 9.1)
policies
more actionable implementation of principles
EA function (or other?) ensure compliance through governance
Solution
shorter term - tactical
holistic solution - building blocks & how interface / interoperate to meet reqs
address business issues
scope
focus
breadth
depth
software
purpose &structure of software apps considered to deliver platform services within infrastructure architecture
breaks down solution architecture to be more granular
N-tiered software architecture
further sub division of three tier architecture
system interface, boundary / presentation layer
web-server layer
client
business logic layer
process logic / controller layer
business entity
data layer
data services layer
data management layer
component based software architecture
assemblies of components
more maintainable
more flexible in deployment in distributed architectures
more consistent