reviewerEnterpise.pdf

Business Process Modeling Notation - Developed by the Business Process Management Initiative (BPMI) - Also known as Business Process Model and Notation - Has an easy-to-use flowchart-like notation Element types in a Business Process Diagrams Flow Objects Event - A trigger that...

Business Process Modeling Notation - Developed by the Business Process Management Initiative (BPMI) - Also known as Business Process Model and Notation - Has an easy-to-use flowchart-like notation Element types in a Business Process Diagrams Flow Objects Event - A trigger that starts, modifies, or completes a process - Include message, timer, error, compensation, signal, cancel, escalation, etc. - Either “throwing” or “catching” - Notation of different events: Activity - A particular task performed by a person or system - Includes subprocesses, loops, multiple loops, and compensations - Notation of different activities: Gateway - A decision point that can adjust the path based on conditions or events - Can be exclusive or inclusive, parallel, complex, or based on data or event. - Notation of different gateways: Connecting Objects Sequence flow - Shows the order of activities to be performed Message flow - Depicts messages that flow across pools - Should not connect events or activities within a pool Association - Associates an artifact or text to an event, activity, or a gateway Swimlanes Pool - Represents major participants in a process Lane - A subpart of a pool - Shows the activities and flow for a certain role or participant Notation of Swimlanes: Artifacts Data Object - Shows the necessary data for an activity Group - Shows a logical grouping of activities - Doesn't change the diagrams flow Annotation - Provides further explanation to a part of a diagram Notation of artifacts: Sub-models Within a BPMN Diagram Private BP - Involves internal processes to a specific organization - Do not cross pools or organizational boundaries Abstract BP - Occurs between a Private BP and an external participation or process - Does not show the Private BP itself Collaborative BP - Shows the interaction between two or more business entities Unified Modeling Language (UML) - created to establish a common, semantic, and syntactical visual modeling language - currently the most important industry-standard language for specifying, visualizing, constructing, and documenting software systems. - emerged from the combination of three (3) existing practices: → Booch Method → Object-Modeling Technique (OMT) → Objectory - commonly used by programmers, but not generally used by database developers Modeling Concepts Specified by UML  Functional – This concept involves use-case diagrams, which describe system functionality from the point of view of a user. Object – This concept involves class diagrams, which describe the structure of a system in terms of objects, attributes, associations, and operations. Dynamic – This concept involves interaction diagrams, state machine diagrams, and activity diagrams, which are used to describe the internal behavior of the system. Types of UML Diagrams Structural UML Diagrams Class diagram – It describes the static structure of a system. Package diagram – It is a subset of a class diagram used to organize elements of a system into related groups. Object diagram – It describes the static structure of a system at a particular time and can be used to test class diagrams for accuracy. Component diagram – This describes the organization of physical software components, including source codes, run-time code, and executables. Composite structure diagram – This diagram shows the internal parts of a class. Deployment diagram – This depicts the physical resources in a system, including nodes, components, and connections. Behavioral UML Diagrams Activity diagram – This illustrates the dynamic nature of a system by modeling the flow of control from activity to activity. Communication diagram – This describes the interactions among classes in terms of an exchange of messages over time. Use case diagram – This models the functionalities of a system using actors and use cases and can be considered as a simplified version of a collaboration diagram introduced in UML 2.0. State machine diagram – This describes the dynamic behavior of a system in response to external stimuli. Sequence diagram – It models the interactions between objects in sequence. Interaction overview diagram – It is a combination of an activity and a sequence diagram, which models a more complex interaction. Timing diagram – It is an interaction UML diagram that focuses on processes that take place during a specific period of time, wherein time is shown to increase from left to right. Architecture Description Language (ADL) - a general term referring to different formal languages Motivation Concepts - These are used to model the enthusiasm, including the reasons, that instigate the design or change of an enterprise architecture. - They influence, guide, and constrain the design process of an enterprise architecture. Terms Related to Motivation Concepts: Stakeholder: An individual, team, department, or organization representing their interest in the outcome of the architecture. Driver: An external or internal condition that motivates an organization to define its goals and implement necessary changes to achieve them. Assessment: The result of an analysis of a particular business issue within the enterprise with respect to some drivers. Goal: A high-level statement of intent, direction, or desired end state for an organization and its stakeholders. Requirement: A specific statement of need that architectural designers must meet. Constraint: A factor that averts or hinders the realization of goals. Principle: A qualitative statement of intent strongly related to the organization’s goals and requirements that should be met by the architecture. Outcome: A result that has been achieved. Value: The relative worth, usefulness, or importance of a core element or an outcome. Meaning: The knowledge or expertise present in a business object or its representation, given a particular context. Strategy Concepts Course of Action: Represents what an enterprise has decided to do to realize its goals. It is an approach or plan for configuring capabilities and resources of an enterprise to achieve a goal. Capabilities: Key building blocks of a business, unique and independent from each other, stable over time. They are aimed at achieving some goal or delivering value by realizing an outcome. These are abilities possessed by an active structure element, such as an organization, person, or system.  Resources: Assets owned and/or controlled by an individual or organization. They are structured elements assigned to capabilities. -Business Layer- Business Structure Concepts Business Actor: A business entity capable of performing behavior. Business Role: The responsibility for performing specific behavior, to which an actor can be assigned. Business Collaboration: An aggregate of two or more active internal business structure elements that work together to perform collective behavior. Business Interface: A point of access where a business service is made available to the environment. Business Object: Models an object type in which several instances may exist within an organization, representing important information or conceptual elements within a particular business domain. Representation: A perceptible form of the information carried by a business object. Business Behavior Concepts Business Service: An explicitly defined perceptible business behavior, used to manifest business functionality to the environment. Business Process: A sequence of business behaviors that achieve a specific outcome, such as a defined set of products and services. Business Function: A collection of business behaviors based on a chosen set of criteria closely aligned to an organization but not explicitly governed by the organization. Business Interaction: A unit of collective business behavior collaboratively performed by two or more business roles. Business Event: Denotes an organizational state change, which is instantaneous and does not have a specific duration. Higher-Level Business Concepts Product – It is a coherent collection of services and/or passive structure elements, accompanied by a contract or a set of agreements, which is offered as a whole to customers. Contract – It is a formal or informal specification of an agreement between a provider and a consumer -Application Layer- Application Structure Concepts Application Component – It is an encapsulation of an application’s functionality that is aligned to the implementation structure, which is modular and replaceable. Application Collaboration – It is an aggregate of two (2) or more application components working together to perform collective application behavior. Application Interface – It is a point of access where an application service is made available to users to another application component or a node. Data Object – It is a data that is structured for automated processing. Application Behavior Concepts Application Service - It is an explicitly defined and visible application behavior - It is used to specify services provided by the business. Application Function - It is an automated behavior that can be performed by an application component. Application Process - It is a sequence of application behaviors that realizes a specific outcome. Application Interaction - It is a unit of collective application behavior collaboratively performed by two (2) or more application components. Application Event - It refers to an application behavior that denotes a state of change. -Technology Layer- Technology Structure Concepts Node  - It is a computational or a physical resource that hosts, manipulates, or interacts with other computational or physical resources. Technology Collaboration - It is an aggregate of two (2) or more nodes that work together to perform collective behavior. Technology Interface - It is a point of access where technological services offered by a node can be accessed. Device - It is a physical information technology resource wherein system software and artifacts can be deployed for execution. System Software - It is a software that supports a business environment in storing, executing, and utilizing applications, including the data deployed within the environment. Path - It is a link between two (2) or more nodes through which the exchange of data or material happens. Communication Network - It is a set of structures that connects computer systems or other electronic devices for transmission, routing, and reception of data or information. Artefact - It is a piece of data that is used and/or produced in a software development process or a system deployment and operation. Technology Behavior Concepts Technology Service - It is an external visible unit of functionality, provided by one or more nodes accessible through well-defined interfaces. Technology Function - It is a behavior element that groups infrastructural behavior, which can be performed by a node.  Technology Process - It is a sequence of technological behavior that achieves a specific outcome. Technology Interaction - It is a unit of collective technology behavior collaboratively performed by two (2) or more nodes. Technology Event - It is a technology behavior element that denotes a state change Physical Concepts Equipment - It is a physical machine, tool, or instrument that can create, use, store, move, or transform materials. Facility - It is a physical structure or environment interconnected by distribution networks. Distribution Network - It is a physical network used to transport materials, data, or information. Material - It is a tangible matter or physical element that can be accessed by equipment. Implementation and Migration Concepts Implementation-Related Concepts Work Package - It is a series of actions identified and designed to achieve a specific goal or result within a clearly defined beginning and end date and resource constraints. Implementation Event - It is a behavior element that denotes a state of change related to implementation or migration that can encompass a time attribute. Deliverable - It is a precisely defined outcome of a work package. Migration Planning Concepts  Plateau - It is a relatively stable state of an enterprise architecture that exists during a specific period of time. Gap - It is a statement of difference between two (2) plateaus.