2012-04-09

Architecting modern information systems

My course "Architecting modern information systems" (please, see its structure below) is available at slideshare.net.

The class in Tunisia:


 Module 1: Enterprise architecture (EA) http://www.slideshare.net/samarin/architecting-of-modern-information-systems-m1
  •  Architecture within an enterprise 

 Module 2: Business architecture http://www.slideshare.net/samarin/architecting-modern-informaiton-systems-m2a and http://www.slideshare.net/samarin/architecting-modern-informaiton-systems-m2a-business-architecture
  •  Management by processes 

 Module 3: Application architecture http://www.slideshare.net/samarin/architecting-modern-informaiton-systems-m2b-application-architecture
  • Link applications to the business 
  • Technologies: BPM, BRM, BEM, BAM 
  • SOA, Integration (ESB), Application systems (suites) 

 Module 4: Information architecture http://www.slideshare.net/samarin/architecting-modern-informaiton-systems-m4-information-architecture
  • Knowledge management 
  • Technologies: ECM, MDM, BI, risk management 

Module 5: Technology architecture
  • Flexibility systems 
  • Security considerations 
  • Virtualisation 

 Module 6: Modern disruptive technologies http://www.slideshare.net/samarin/architecting-modern-informaiton-systems-m6-modern-disruptive-technologies
  • Cloud computing 
  • Social computing 
  • Free and Open Source Software; Open standards 

 Module 7: Essential techniques http://www.slideshare.net/samarin/architecting-modern-informaiton-systems-m7-essential-techniques
  • Project management (PMBOK, HERMES)  
  • Governance (COBIT)
  • Writing the IT strategy
Thanks,
AS

Lettre de remerciement



2 comments:

Anatoly said...

The methodology of risk management can be built taking into account the application of the standards ISO 31000 and related. A separate issue is the architecture for embedding risk management into corporate business processes. How can you illustrate this?

Alexander Samarin said...

As an enterprise architect, I have to seamlessly integrate risk into enterprise "fabric". In general, risk is an intangible artefact which co-exists with other artefacts, e.g. assets, rules, roles, goals, KPIs, processes, data, documents, etc. In specific, risk requires a simulation model of enterprise and the EA is the right place to provide such a model. The blogpost http://improving-bpm-systems.blogspot.com/2011/10/ea-view-on-enterprise-risk-management.html shows where to put "placeholders" for risk-related functions. For example, any external or internal business event may trigger a risk-evaluation procedure. The latter may trigger a risk-mitigation processes. The latter may adjust some business rules which affect the execution of some business processes.

If those dependencies are anticipated in the architecture then the implementation of ERM is concentrated on the risk-centric issues.

Majority of ISO 31000 principles are guaranteed by the EA:
- Risk management creates and protects value
- Risk management is an integral part of organizational processes
- Risk management is part of decision making.
- Risk management explicitly addresses uncertainty.
- Risk management is systematic, structured and timely.
- Risk management is based on the best available information
- Risk management is tailored.
- Risk management is transparent and inclusive
- Risk management is dynamic, iterative and responsive to change.
- Risk management facilitates continual improvement and enhancement of the organization

Thanks,
AS