CPIS-352: Enterprise Architecture Introduction, Ch. 1

• The lecture is about CPIS-352 IS Applications Design & Development.
• The textbook for the lecture is "Enterprise Architecture at Work" by Marc Lankhorst.
• The learning modules include:

Learning Modules

• What is Enterprise Architecture
• State of the Art
• Dimensions of Architectural Modeling
• Viewpoints and Visualization

Grade Distribution

• Quiz 1 accounts for 5% of the grade and is in week 4.
• Graded Lab Work 1 accounts for 2.5% in week 4.
• Graded Lab Work 2 accounts for 2.5% in week 5.
• Graded Lab Work 3 accounts for 2.5% in week 6.
• The Midterm accounts for 30% of the grade and is in week 6.
• Graded Lab Work 4 accounts for 2.5% in week 7.
• Quiz 2 accounts for 5% in week 8.
• The Group Project accounts for 20% of the grade and is in week 11.
• The Final Exam accounts for 30% of the grade and is in week 12.

Introduction to Enterprise Architecture

• The lecture is about Introduction to EA, specifically Chapter 1.
• The lecture contents include architecture, enterprise architecture, the architecture process, and the drivers for enterprise architectures.
• The drivers for Enterprise Architectures are internal drivers and external drivers

Enterprise Architecture

• Enterprise is any collection of orgs that has a common set of goals and/or a single bottom line.
• Architecture is a representation of the structure or form of a system embodied by its components.
• Architecture gives physical from to the functions needed by the system

Architecture Forms

• The collection of elements in the system
• The Configuration those elements
• The arrangement of the elements and how they are related to each other
• With regard to an enterprise the architecture represents conceptual components, conceptual relationships, and enterprise-wide principles.
• To create an overview of the structure of an organization, its business processes, their application support, and the technical infrastructure, different aspects, domains, and their relations need to be expressed.
• To deal with the complexity of designing an enterprise, many organizations use enterprise architecture.

Architect & Stakeholders

• Stakeholder is an individual, team, or organization with interests in, or concerns relative to, a system.

Enterprise Architecture Definition

• Enterprise architecture comprises of a coherent whole of principles, methods, and models that are used in the design and realization of an enterprise's organizational structure, business processes, information systems, and infrastructure.
• Enterprise Architecture, or EA, conceptually blueprints the structure and operation of organizations in order to determine how an organization can effectively achieve current and future objectives.
• Enterprise Architecture establishes the organization-wide roadmap to achieve the mission through optimal performance of its core business functions within an efficient information technology (IT) environment.
• Enterprise Architecture defines the organization's current baseline and desired target settings and specifies transformation mechanisms to achieve target outcomes systematically.

The Architecture Process

• Architecture is a process as well as a product.
• The product should guide managers in designing business processes and system developers in building applications in line with business objectives and policies.
• Stakeholders awareness with respect to business objectives and information flow will be raised
• Once the architecture is created, it needs to be maintained and changed by the people in power see an opportunity to strengthen business objectives
• The architecture process consists of usual steps involving taking an initial idea through design and implementation phases to an operational system, and finally changing or replacing this system.
• For all of the phases of the architecture process, clear communication with and between stakeholders is indispensable.
• The architecture descriptions undergo a life cycle that corresponds to this design process.
• Architecture products are discussed with stakeholders, approved, revised, and play a central role in establishing a common frame of reference for all those involved.

Drivers for Enterprise Architecture

• Organizations benefit from having a clear understanding of its structure, products, operations, technology, and the web of relations tying these together and connecting the organization to its surroundings.
• External pressures from customers, suppliers, other business partners, and regulatory bodies should be taken into account.
• Good architectural practice becomes indispensable, especially if a company becomes larger and more complicated.

Internal Drivers for Enterprise Architecture

• Business-IT alignment is commonly recognized as an important instrument to realize organizational effectiveness.
• Effectiveness is not obtained by local optimizations but realized by the well-orchestrated interaction of organizational components.
• Henderson and Venkatraman distinguish aspects of business strategy and organizational infrastructure on the one hand, and IT strategy and IT infrastructure on the other hand.
• An enterprise's mission is its purpose of existence, and the vision describes the future and values while the strategy states the route to achieve the mission and vision.
• Daily concrete operational changes require the application of enterprise architecture.

External Drivers for Enterprise Architecture

• External pressures push organizations towards adopting enterprise architecture practice.
• Regulatory frameworks are increasingly demanding that organizations and governmental institutions prove insight into operations and compliance with applicable laws.

The Value of Archetecture

• The primary reason to have an enterprise architecture is to provide an overall, high-level design of the enterprise
• Since enterprises are not designed in one step, the enterprise architecture provides the structure for all types of enterprise projects to conform to
• It expresses architectural principles of a long-term visión.
• It communicates the system design vision and enterprise strategy to all stakeholders.
• It helps management to plan, manage, and effectively utilize the enterprise's resources.
• It can also help to ensure legal and regulatory compliance.
• The primary reason to have an enterprise architecture is to provide an overall, high-level design.
• It must Address stakeholder needs and show how those needs will be satisfied
• Explains the required trade-offs to meet those needs

Other key points

• Architecture expresses the principles of a long-term vision for the system.
• It is done to support growth and change because many systems have long-expected life-times.
• Architecture communicates the system design vision to all stakeholders.

Developing an Enterprise Architecture

• Uses of a Reference Architecture.
• It describes a structured set of models that collectively represent the building blocks of the system in a specific domain.

Knowledge Reuse - Reference Architectures.

• Reference Architectures embodies the knowledge gathered, on a large scale, from a multitude of enterprise engineering projects.

Reference Architecture: Frameworks

• Zachman's Framework was originally developed at IBM for help with IT Frameworks.
• The Framework is a logical structure for classifying and organizing the descriptive representations of an Enterprise that are significant to Enterprise management.
• Federal Enterpise Architecture was created by the CIO Council that was then used to develope the Federal Enterprise Architecture Framework (FEAF1999) for the US federal government
• TOGAF Architecture framework is an industry standard architecture freely used by any enterprise.
• TOGAF Version 8.1 Enterprise Edition is an industry standard architecture framework
• CIMOSA was created by European research consortium for manufacturing systems.
• ARIS was created in Germany and principles adopted by SAP.
• The DoD Reference Architecture defines viewpoints and what to include, defines net-centric architecture and DoD-wide requirements.
• TOGAF frameworks are industry standards to developing enterprise architectures.

Zachman's Framework

• The Framework helps to classify and organize the descriptive representations of a company or enterprise that are significant to the management of the enterprise.
• The framework borrows from Architecture/Construction and Engineering/Manufacturing principles to classify and organize artifacts created over the process of designing products.
• It includes Provides a good classification of the stakeholder views and the enterprise views
• It also shows how cells are related horizontally and vertically (between views).
• It should be remembered It Has 36 cells that need to be filled with artifacts such as models
• Lack of methodology or guidance on how to fill cell artifacts

Enterprise Architecture common traits

• Information, Process, and Orginization are common
• Decisions that are enterprise-wide
• Terminology and Architecural Principles for decision making

Good Architecutal Practices

• Enterprise Architecture values have a high impact and not low impact.
• In order to have good, architecture must:
• Resilient
• Simple
• Scalable and extendable
• Have Clear Separation of Concerns
• Have a Balanced Distribution of Responsibilities
• Balances economic and technology constraints

Key Enterprise archicture takeaways.

• Able to Define enterpirse archtecture
• Explain business and technical reasons why an enterprise would want to develope an architecture.
• Able to describe and compare the different reference architectures and how they are used to derive enterprise architectures
• Describe what an enterprise architecture should contain

Lecture on CPIS-352 IS Applications Design & Development, focusing on Chapter 1 from 'Enterprise Architecture at Work' by Marc Lankhorst. The lecture will cover what is Enterprise Architecture. It also covers State of the Art, Dimensions of Architectural Modeling, Viewpoints and Visualization.