• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
(slides)
 

(slides)

on

  • 346 views

 

Statistics

Views

Total Views
346
Views on SlideShare
346
Embed Views
0

Actions

Likes
0
Downloads
8
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    (slides) (slides) Presentation Transcript

    • Symbiosis of Enterprise Architecture and ICT Architecture J.C. Wortmann¹, D.K. Hammer², J.B.M. Goossenaerts¹, A.T.M. Aerts²
    • Overview
      • Four architectural domains
      • Six phases in enterprise architectures
      • Six times the same point:
      • It takes two to tango
      • Domain Architectures Overview
      • Conclusion : it takes four to tango
      • All in 10 minutes !!
    • Four Architectural Domains
      • enterprise architecture,
      • model architecture,
      • software architecture and
      • ICT-platform architecture.
    • Enterprise Architecture
      • Enterprises (recursively),
      • their contracts,
      • their structure,
      • their processes
      • their positions
      • their controls
      • their exchange (G, S, H, I, M, E) with others
    • Model Architecture
      • Object models:
      • Resource Models
      • Workflow Models
      • Products Models
      • Document Models
      • Interaction Models
      • Users and Applications,
      • etcetera
    • Software Architecture
      • Logical view (end-user functionality)
      • Components view (development)
      • Process view (run-time behavior)
      • Physical view (installation)
      • Usage cases and scenarios
    • ICT platform Architecture
      • Structure
      • Interaction
      • Distribution
      • Concerns
      • Performance
      • Stakeholders
    • Six Phases
      • the functional hierarchy
      • the functional hierarchy with function oriented automation
      • the functional hierarchy with shared data base on mainframes
      • the process oriented enterprise
      • t he supply chain oriented enterprise
      • the web-enabled agile enterprise
    • 1. Functional hierarchy - no automation
      • Enterprise Architecture
        • functional hierarchy -- machine bureaucracy
        • focus on resources within functional silos
      • Model Architecture -- hierarchy
        • business processes carried by document flows
        • object models implemented in files
      • Software Architecture
        • humans perform calculations and access files
      • ICT Platform Architecture
        • paper, pencil, abacus, telegraph, telephone,mail
    • Point 1:
      • Model architecture (hierarchy, processes) enables:
      • predictability,
      • correctness,
      • repeatability, and
      • accountability.
    • 2. Functional hierarchy: silo automation
      • Enterprise Architecture (same)
        • Vertical communication well organized
        • Horizontal communication slow and error-prone
      • Model Architecture (same)
        • object models passive but explicit in functional datastructures
      • Software Architecture
        • monolithic applications per functional area
      • ICT Platform Architecture
        • mainframe with terminals
    • Point 2:
      • Silo-based automation enables
      • speed and
      • reliability
      • of all data-related activities
      • and calculations.
      • .. Automation enables improvement
    • 3. F-hierarchy: shared DB on mainframe
      • Enterprise Architecture : logistics
        • matrix organization to co-ordinate flows
      • Model Architecture
        • single conceptual data model for whole enterprise
        • explicit integration by “process diagrams”
      • Software Architecture
        • separation between data layer and application layer
      • ICT Platform Architecture
        • mainframes with minicomputers as “satelites”
    • Point 3:
      • Conceptual database and 3 schema architecture bridge gap between enterprise and ICT-domain
      • Automation problem of functional hierarchy is solved!
      • ICT-solution is cast in concrete while business requires change: business process re-engineering
    • 4. process-oriented enterprise
      • Enterprise Architecture
        • Business Units: value-adding processes become leading principle rather than functional units
      • Model Architecture
        • Workflow plays the dominant role in modeling
        • Object-orientation emerges
      • Software Architecture
        • Best-of-breed standard integration rather than ad hoc
        • separation of UI, business logic and data access
      • ICT Platform Architecture
        • 2 tier client-server; LAN; open platforms
    • Point 4:
      • Client-server enables internal integration
      • in a more flexible way than ad-hoc integration
      • ideal tool for BPR
      • But .. Enterprise needs are already moving towards external integration over the supply chain
    • 5. SC process oriented enterprise
      • Enterprise Architecture
        • cross-enterprise business processes
        • re-definition of roles in the supply chain
      • Model Architecture
        • federated models of heterogeneous origin
        • semantic mapping and explicit SC modeling
      • Software Architecture
        • asynchronous message-based integration
        • mapping and transaction services; rich UI
      • ICT Platform Architecture
        • WAN; 3-tier CS; Distributed data and processing
    • Point 5:
      • Enterprise application integration technology enables supply chain integration
      • Enterprises leverage these technologies to move forward towards more responsiveness and agility
    • 6. A gile process-oriented enterprise: the supply chain is the enterprise
      • Enterprise Architecture
        • differentiation; scope; globalization;
        • collaboration
      • Model Architecture
        • task-based UI; self-descriptive data; scope and roles;
        • executable models; distant users; differentiated
      • Software Architecture
        • thin client; mobile agents; alert and launch
      • ICT Platform Architecture
        • ubiquituous asynchronous, heterogeneous computing
    • Point 6:
      • ICT developments enable enterprises to make progress in directions where they would like to go: collaborativeness
      • Enterprises leverage ICT developments as soon as they occur -- when there is a market opportunity: e-business
    • Domain architecture - overview
    • Point 7:
      • Modularity occurs within a domain
      • Performance is defined within a domain
      • Integration covers several domains
      • Breakthrough occurs in several domains
      • Architecting requires several domains
    • Conclusion
      • Enterprise architectures and ICT architectures move forward in symbiosis
      • It takes four to tango