International Journal of Information System Modeling and Design · 2014 · 57 citations · 27 references
ManagementInformation SystemsManagement Information SystemsDecision MakingEnterprise ArchitectureOrganizational LearningBusiness ArchitectureDecision Making In OrganizationsOrganizational ArchitectureOrganizational Decision-makingSoftware ArchitectureEnterprise Architecture ArtifactsEnterprise Architecture Decision-makingOrganizational Learning LoopsOrganizational Learning Strategy
Enterprise Architecture modeling languages depict the business‑to‑IT stack but omit the rationale behind designs; EA Anamnesis supplements them by revealing design alternatives, selection criteria, and the decision‑making strategy used. This study extends EA Anamnesis to support organizational learning. The authors integrate ex‑ante and ex‑post decision‑making viewpoints—capturing anticipated and unanticipated consequences—and demonstrate the approach with a realistic case study.
Enterprise Architecture (EA) modeling languages can express the business-to-IT-stack for an organization, showing how changes in the IT landscape impact business aspects and vice versa. Yet EA languages provide only the final architectural design, not the rationale behind this design. In earlier work, the authors presented the EA Anamnesis approach for EA rationalization. The authors discussed how EA Anamnesis forms a complement to current EA modeling languages, showing for example design alternatives, EA artifact selection criteria and the decision making strategy that was used. In this paper, the authors extend EA Anamnesis with a capability for organizational learning. In particular, the authors present an integration of two viewpoints presented in earlier work: (1) an ex-ante decision making viewpoint for rationalizing EA during decision making, which for example captures a decision and its anticipated consequences, and (2) an ex-post decision making viewpoint, which for example captures the unanticipated decision consequences, and possible adjustments in criteria. The authors use a fictitious, yet realistic, case study to illustrate our approach.
27
Charles Leave, John W. Payne, James R. Bettman et al. · Journal of the Operational Research Society · 1994 · 3.4K citations
Software Architecture as a Set of Architectural Design Decisions