Uploaded byDakiry
Діма Зубець ” The Zachman Framework for Enterprise Architecture”
The document discusses architecture and defines it as "the set of descriptive representations relevant for describing a complex object such that the instance of the object can be created and such that the descriptive representations serve as the baseline for changing an object instance." It introduces the Zachman Framework, which provides a schema for organizing architectural representations based on fundamental interrogatives and perspectives. The framework establishes an ontology and methodology for developing architectures. Developing architectures with an ontology and methodology produces reusable assets and allows engineering complex systems, while an ad hoc methodology treats architecture as an alchemical practice.
More Related Content
Similar to Діма Зубець ” The Zachman Framework for Enterprise Architecture”
Діма Зубець ” The Zachman Framework for Enterprise Architecture”
- 2.
- 3. This is theRESULT of architecture. In the RESULT you can see the Architect’s “architecture”. The RESULT is an implementation, an instance.
- 4. Complexity & Change Complexity:it is something you can’t describe, you can’t create, you can’t see it in its entirely at one time (whatever “it” is) Change: if it is likely to change considerably over time (whatever “it” is)
- 5. The key tocomplexity and change is ARCHITECTURE
- 6. Architecture - ISthe set of descriptive representations relevant for describing a complex object such that the instance of the object can be created and such that the descriptive representations serve as the baseline for changing an object instance
- 7. Are there anyproblems with Architecture definition? “Architecture is Architecture is Architecture”
- 9. Zachman Framework -is a schema!
- 10. Columns: the fundamentalsof communication found in the primitive interrogatives: What, How, Where, Who, When, and Why Identification Definition Representation Configuration Instantiation Rows: the transformation of an abstract idea into an instantiation that was initially postulated by ancient Greek philosophers: Identification, Definition, Representation, Specification, Configuration, Instantiation Specification
- 11.
- 12. Scope (Boundaries –Strategist’s) Requirement’s (Concepts – Owner’s) Design (Logic, Schematics – Designer’s) Plan (Physics, Blueprints– Builder’s) Part(Configurations – Implementer’s) THE PRODUCT INSTANTION Audience Perspectives Models Perspectives Identification Definition Representation Specification Instantiation Configuration
- 13. Scope (Boundaries –Strategist’s) Requirement’s (Concepts – Owner’s) Design (Logic, Schematics – Designer’s) Plan (Physics, Blueprints– Builder’s) Part(Configurations – Implementer’s) THE PRODUCT INSTANTION What?BillsofMaterial How?Functionalspecs Where?DistributionDiagrams Who?OperatingInstructions When?TimingDiagrams How?DesignObjectives
- 15. It is notjust a schema. It is Normalized Matrix.
- 16. Ontology An Ontology isthe classification of the total set of “PRIMITIVE” (elemental) components that exist and that are relevant to the existence of an object PRIMITIVES are timeless
- 17. Methodology (process) Methodology –a process of transformation. A methodology produces “COMPOSITE”(compound) implementation of “PRIMITIVES” COPMPOSITES are temporal
- 18. This is aMethodology WITHOUT the Ontology A Process with no ontological structure is ad hoc, fixed and dependent on practical skills. This is NOT A SCIENCE. This is ALCHEMY, a PRACTICE
- 19. This is aMethodology WITH the Ontology
- 20. Alchemist can ignorePeriodic Table and define a process (a methodology) that will produce results, point-in-time solutions, based on their own skills and experience (heuristics). The process (methodology) will be fixed (not changeable) but the alchemist will forever remain ALCHEMIST
- 21. Methodologies WITH Ontologyproduce ARCHITECTURE
- 22. This is NOTa methodology (process) This is Ontological Normalized Matrix
- 23. Primitives and Compositemodels Primitives Composite
- 24.
- 25.
- 26. Primitives Place Composite The Key 1. Single-variable,precisely unique, relevant (not arbitrary), ontologically-based components 2. Binary Relationships (only two components at time) Customer Order
- 28. The Zachman Framework for Enterprise Architecture What? Inventory How? Processes Where? Distributions Who? Responsibiliti es When? TimeCycles Why? Motivations Executive Perspective (Scope) Business Mgmt Perspective (Business Models) LocationLocation
- 29.
- 31.
- 33.
- 35.
- 36. Manufacturing vs Engineering EngineeringView One VERIABLE – Total Product Manufacturing View One PART – Multiple Variables
- 37. ENTERPRISE ARCHITECTURE Business Strategy BusinessNeeds System Design Physical Configuration Solution
- 38. 1. Make-to-Order Strategy.If IT is in the business of building and running systems and the objective is to build systems faster and cheaper, then break them down into smaller pieces and start writing the code. Result is more of the same … LEGACY. (NOT reusable, NOT interoperable, etc., etc.,…BUT running). Reducing Time-to-Market Strategies
- 39. Reducing Time-to-Market Strategies 2. Provide-from-StockStrategy. If the IT strategy is to buy rather than build then implement “as is”, change the Enterprise to fit the package. Build and maintain “interfaces” with any replicated concerns in the existing legacy or in future system implementations.
- 40. Reducing Time-to-Market Strategies 3. Assemble-to-OrderStrategy. If IT is in the business of engineering and manufacturing Enterprises, then start build an inventory of Enterprise Architecture assets, engineering them to be reused in any implementation. The “asset paradigm”.
- 41.