Modeling Information Systems Architectures
Transcript of Modeling Information Systems Architectures
![Page 2: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/2.jpg)
Purpose of this lecture
The purpose of this lecture is notto present pre-cooked solutions to architectural problems, but rather to clarify architectural issues and discuss a number of important topics in this context.
![Page 3: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/3.jpg)
Table of contents
■ What are IS architectures ?■ Aspects of IS architectures■ Types of IS Architectures■ Reference Architectures■ Designing IS architectures■ Architectural platforms■ Conclusions
![Page 4: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/4.jpg)
What are ISarchitectures ?
![Page 5: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/5.jpg)
General architecture
architectuur' (architektuur), v., 1. bouwkunst, de kunst en de leer van het ontwerpen en uitvoeren van bouwwerken; - toepassing daarvan: onder architectuur gebouwd , naar de plannen van een bekend architect; - 2. bouwstijl: Griekse architectuur; - 3. (fig.) bouw, constructie: de architectuur van de kaak (Vestdijk); - 4. (m eton.) bouwsel(s), bouwwerk(en): voorbeelden van moderne architectuur;
Van Dale
![Page 6: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/6.jpg)
Software architecture
The architecture of a software system defines that system in terms ofcomputational components and interactions among those components.
Software Architecture; Shaw & Garlan;Prentice Hall, 1996
![Page 7: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/7.jpg)
Example architecture
![Page 8: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/8.jpg)
Information system architecture
The architecture of an information system defines that system in terms of components and interactions among those components,from the viewpoint of specific aspectsof that system, and based on specific structuring principles.
![Page 9: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/9.jpg)
Interpreting IS architectures
■ Syntax:structure of the architecture
■ Semantics:meaning of components and interactions
■ Pragmatics:reasons behind structure & meaning
![Page 10: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/10.jpg)
Aspects of ISArchitectures
![Page 11: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/11.jpg)
Aspects architecture
data
system
configu-ration
commu-nication
organi-zation
Truyenset al.;1990
![Page 12: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/12.jpg)
Data aspect architecture
data
system
configu-ration
commu-nication
organi-sation
Architecture of data managed by systems, e.g. using (E)ER diagrams.
![Page 13: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/13.jpg)
System aspect architecture
data
system
configu-ration
commu-nication
organi-sation
Architecture of application software, e.g. using data flow diagrams ormodule diagrams.
trip data fin. data
booktrip
proc.ackn.
proc.inv.
proc.docs.
proc.paym.
1
2
3
4
5
a b
Req.
Pay.
![Page 14: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/14.jpg)
Configuration aspect architecture
data
system
configu-ration
commu-nication
organi-sation
Architecture of hardware and low-level software (e.g. OS, DBMS),e.g. using configuration diagrams.
SPARCSPARC
UNIXUNIX
OracleOracle FlowMarkFlowMark
![Page 15: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/15.jpg)
Communication aspect architecture (I)
data
system
configu-ration
commu-nication
organi-sation
Architecture of communication infrastructure(networks, communication software), using e.g. topology diagrams.
3174
3174
3745
ES/9000(HBS)
ES/9000(APL)
Token Ring
3174
3174
PDP11/74
3174PC
PCPC
OLD
LOS
SpecialistenSystemen
PMK
Commun.Controller
ClusterController
Haemo-dialyseSysteem
2 Mb/s
19,2 Kb/s
![Page 16: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/16.jpg)
Communication aspect architecture (II)
data
system
configu-ration
commu-nication
organi-sation
3174
3174
3745
ES/9000(HBS)
ES/9000(APL)
Token Ring
3174
3174
PDP11/74
3174PC
PC
PC
OLD
LOS
SpecialistenSystemen
PMK
Commun.Controller
ClusterController
Haemo-dialyseSysteem
2 Mb/s
19,2 Kb/s
![Page 17: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/17.jpg)
Organization aspect architecture
data
system
configu-ration
commu-nication
organi-sation
Architecture of organization structure and processes related to administration and maintenance of systems, using e.g. organigrams and procedure handbooks
![Page 18: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/18.jpg)
A design path with aspects
start arch.:major apectscombined
global arch.:major apects
combined
![Page 19: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/19.jpg)
Types of ISArchitectures
![Page 20: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/20.jpg)
Type of IS architectures
Based on structuring principles:■ Monolithic / Layered / Columned / OO■ Single-Level versus Multi-Level
Based on purpose:■ Conceptual versus Technical■ Application versus General System■ Reference versus Concrete
![Page 21: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/21.jpg)
Structuring principles (I)
Monolithic
Columned
Layered
Object-Oriented
and combinations
![Page 22: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/22.jpg)
Structuring principles (II)
Multi-level architectures:allow for multiple aggregationlevels of functionality
![Page 23: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/23.jpg)
Structuring principles (III)
Columned
Syntax: several system modules in the same layer.Semantics: multiple subsystems at the same abstraction level using each others functionality.Pragmatics: separation of concerns (system arch.) or distribution (conf. arch.).Pipe
![Page 24: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/24.jpg)
Purpose of architecture (I)
Conceptual architecture: describes structure of conceptual design of systemTechnical architecture: describes structure of implementation of system
conceptual technical
![Page 25: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/25.jpg)
Purpose of architecture (II)
Application: describes architecture for specific application and contextGeneral system: describes architecture for general application and context
Concrete: describes architecture of a specific system to be directly appliedReference: describes blue-print of abstract system to be “concretized” before application
![Page 26: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/26.jpg)
Reference Architectures
![Page 27: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/27.jpg)
Reference architecture
A reference architecture is a general, abstract architecture that can be instantiated for specific situations.
Instantiated =• filled in, detailed• parameterized, adapted• extended, selected
![Page 28: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/28.jpg)
ISO-OSI reference architecture
application
presentation
session
transport
network
data link
physical
Structure: layeredAspects: system configuration communicationPragmatics: standard interface levels for horizontal communication
![Page 29: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/29.jpg)
ANSI/SPARC reference architecture
externalmodel
conceptualmodel
internalmodel
Structure: layeredAspects: system data organizationPragmatics: separation between database levels for different purposes
![Page 30: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/30.jpg)
ANSI/SPARC in DDBS
Glob.Ext.Schema
Glob.Ext.Schema
Glob.Ext.Schema
Glob.Conc.Schema
Fragm.Schema
Alloc.Schema
Loc.Map.Schema
Loc.Map.Schema
Loc.Map.Schema
Loc.Conc.Schema
Loc.Conc.Schema
Loc.Conc.Schema
Loc.Int.Schema
Loc.Int.Schema
Loc.Int.Schema
DB DB DB
Structure: idemAspects: idem + communicat. Pragmatics: idem + distribution
Connolly, Begg &Strachnan, 1995
![Page 31: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/31.jpg)
WfMC reference architecture (I)
Workflow API & Interchange Formats
WorkflowEngine(s)
Workflow Enactment Service
Workflow ClientApplications
ProcessDefinition Tools
Adminstration &
Mngmnt Tools
InvokedApplications
IF1
IF2 IF3
IF4IF5 WorkflowEngine(s)
Other WF Enactment Service(s)
![Page 32: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/32.jpg)
WfMC reference architecture (II)
Workflow EngineWorkflow Engine
ProcessDefinitionProcess
DefinitionWorkflow
ClientsWorkflow
ClientsAdministr.& MngmntAdministr.& Mngmnt
ApplicationsApplications
Structure: first layered, then columned
![Page 33: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/33.jpg)
Designing ISArchitectures
![Page 34: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/34.jpg)
Example architecture design
■ Mercurius initiative (1995)■ Purpose:
specification of reference WFMS■ Focus:
detailed system architecture■ Participants:
2 universities, polytechnicconsultancy firm,financial institution
![Page 35: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/35.jpg)
Mercurius architecture design principles
Flexibility (detail, aspect)■ Top-down architecture design strategy■ WF design versus WF enactment■ Kernel versus additional functionalityPositioning in context■ Explicit interfaces to environment
![Page 36: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/36.jpg)
Mercurius overall WFMS architecture
datastores
UIS UIS
WFDesign
WFClients
WFServer
DBMS AS/OS
CS WFServer
AS/OS/DBMS
datastores
configuration
system
communication
organi-zation
data
![Page 37: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/37.jpg)
Mercurius design module architecture
ASInterface
WF DesignEngine
DBMSInterface
def.data
proc.data
appl.data
UISInterface
ExtensionModule
organ.data
software bus
![Page 38: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/38.jpg)
Mercurius design engine architecture
def.data
proc.data
Organisat.Design
organ.data
appl.data
ProductDesign
Global Design
DetailDesign Tuning
![Page 39: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/39.jpg)
Mercurius enactment module architecture
ASInterface
WFSEngine
OSInterface
DBMSInterface
CSInterface
ExtensionModule
proc.data
man.data
appl.data
WFCInterface
AS
software bus
def.data
organ.data
![Page 40: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/40.jpg)
Mercurius enactment engine architecture
ASInterface
EventA nalyzer
A ctionSynthesizer
def.data
proc.data
EventReceptor
ClockM odule
ActionExecutor
CSInterface
W FCInterface
appl.data
software bus
O SInterface
![Page 41: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/41.jpg)
Architectural Platforms
![Page 42: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/42.jpg)
Distributed Object Architectures
■ object model architecturevs. system model architecture
■ application object accessvs. server system access
■ fine grain computationvs. coarse grain computation
■ transparent distributionvs. no/explicit distribution
![Page 43: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/43.jpg)
Example architecture ‘traditional’
WorkflowEngine
TransactionManager
WorkflowClient
casedata
transdata
![Page 44: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/44.jpg)
Example architecture a la DOA
casecase
scheduler
client
transact.
transact.
client
![Page 45: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/45.jpg)
OMG-OMA
Application Objects Common Facilities
Object Services
Object Request Broker
![Page 46: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/46.jpg)
Example architecture: WIDE WFMS
WorkflowEngine
BAL
DBMS
LTM
Local Trans.Interface
GlobalTrans. Man.
GT LT
![Page 47: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/47.jpg)
Conclusions
![Page 48: Modeling Information Systems Architectures](https://reader030.fdocuments.net/reader030/viewer/2022020213/584ab51e1a28ab85738bcd17/html5/thumbnails/48.jpg)
Conclusions
✸ Modeling of architectures ofparamount importance CIS design
✸ Modeling of CIS architectures hasmany aspects
✸ Modeling of CIS architectures is adiscipline that is in its infancy