ENTERPRISE H1 Flashcards
- This was originally developed by the Business Process Management Initiative (BPMI). In 2005, the Object Management Group took over the initiative (Lucid Software Inc., n.d.).
Business Processing Model Notation (BPMN)
its goal is to support business process modeling by providing
BPMN
A trigger that starts, modifies, or completes a process. Event types include message, timer, error, compensation, signal, cancel, escalation, link, etc. An event can be classified as either “throwing” or “catching,” depending on their function.
Event
A particular task performed by a person or system. It can include sub-processes, loops, multiple loops, and compensations.
Activity
A decision point that can adjust the path based on conditions or events. A gateway can be exclusive or inclusive, parallel, complex, or based on data or event.
Gateway
This shows the order of activities to be performed.
Sequence flow
This depicts messages that flow across pools, or organizational boundaries such as departments. It should not connect events or activities within a pool.
Message flow
This associates an artifact or text to an event, activity, or a gateway.
Association
It represents major participants in a process. A different pool may be in a different company or department but still involved in the process.
Pool
It is a sub-part of a pool. It shows the activities and flow for a certain role or participant, defining the accountability within the processes.
Lane
This shows the necessary data for an activity.
Data object
This shows a logical grouping of activities, but does not change the diagram’s flow.
Group
This provides further explanation to a part of the diagram.
Annotation
This involves internal processes to a specific organization and do not cross pools or organizational boundaries.
Private BP
This occurs between a private BP and an external participant or process. This does not show the private BP itself.
Abstract BP
This shows the interactions between two or more business entities.
Collaborative BP
- This was created to establish a common, semantic, and syntactical visual modeling language for the architecture, design, and implementation of complex software systems both structurally and behaviorally (Lucid Software Inc., n.d.).
Unified Modeling Language (UML)
- This is currently the most important industry-standard language for specifying, visualizing, constructing, and documenting software systems.
UML
- It emerged from the combination of three (3) existing practices namely, the Booch Method, Object-Modeling Technique (OMT), and Objectory (Lankhorst, 2017).
UML
- This is commonly used by programmers, but not generally used by database developers.
UML
- The Object Management Group (OMG) oversees the definition and maintenance of the UML specifications, which provides engineers and programmers the ability to use one language for different purposes during all phases of the software lifecycle, for all system sizes (Lucid Software Inc., n.d.).
UML
This concept involves use case diagrams, which describes system functionality from the point of view of a user.
Functional
This concept involves class diagrams, which describes the structure of a system in terms of objects, attributes, associations, and operations.
Object
This concept involves interaction diagrams, state machine diagrams, and activity diagrams, which are used to describe internal behavior of the system.
Dynamic
It is a subset of a class diagram used to organize elements of a system into related groups.
Package diagram
It describes the static structure of a system at a particular time, and can be used to test class diagrams for accuracy.
Object diagram
This describes the organization of physical software components, including source codes, run-time code, and executables.
Component diagram
This diagram shows the internal parts of a class.
Composite structure diagram
This depicts the physical resources in a system, including nodes, components, and connections.
Deployment diagram
This illustrates the dynamic nature of a system by modeling the flow of control from activity to activity.
Activity diagram
This describes the interactions among classes in terms of an exchange of messages over time.
Communication 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.
Use case diagram
This describes the dynamic behavior of a system in response to external stimuli.
State machine diagram
It models the interactions between objects in sequence.
Sequence diagram
It is a combination of an activity and a sequence diagram, which models a more complex interaction.
Interaction overview 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.
Timing diagram
- It is a general term referring to different formal languages used in enabling formalization, description, specification, modeling and reasoning of software architectures (Vac, 2017).
Architecture Description Language (ADL)
