Index
A
- Actions
- actions / 2.7.2 Effects on the Business System Model
- Activities
- activity / 2.7.2 Effects on the Business System Model
- activity diagram
- about / 5.4.3 Activity Diagrams
- elements / 5.4.3 Activity Diagrams
- reading / Reading Activity Diagrams
- verifying, in process view / Verify the View—Is Everything Correct?
- activity diagram elements
- activity / 5.4.3 Activity Diagrams
- object flow (edge) / 5.4.3 Activity Diagrams
- accepting a signal action / 5.4.3 Activity Diagrams
- business object / 5.4.3 Activity Diagrams
- Activity diagrams / 3.3.2 The Elements of a View
- about / 3.3.5 Activity Diagrams, 3.4.6 Activity Diagram
- reading / Reading Activity Diagrams, Reading Activity Diagrams
- constructing / 3.3.6 Constructing Activity Diagrams, 3.4.7 Constructing Activity Diagrams, Find Activities and Actions—Which Activities Have to be Performed so that the Goods and Services Utilized by Actors can be Provided and Delivered?, Connect Actions—In Which Order are Actions Processed?, Verify the View—Is Everything Correct?
- Actors
- adopting, from business use cases / Adopt Actors from Business Use Cases—Who is Responsible for Each Action?
- actors / Actors
- Analysis patterns / Practical Tips
- Architecture of Integrated IT Systems (ARIS) / 3.1.4 Using UML to Model Business Processes and Business Systems
B
- behavioral view
- about / 4.3.1 The Life of an Object
- object life cycle / 4.3.1 The Life of an Object
- elements / 4.3.2. The Elements of the View
- statechart diagram / 4.3.3 Statechart Diagram
- statechart diagram, constructing / 4.3.4 Constructing Statechart Diagrams, Identify Mutation Events Relevant for the Object—What Affects the Object?, Group Relevant Events Chronologically—How Does a Normal Life Look?, Model States and Transitions—Which States are There?
- actions, adding to statechart diagram / Add Actions to the Statechart Diagram—What do Objects Do?
- statechart diagram, verifying / Verify Statechart Diagram—Is Everything Correct?
- boarding / 2.1 Introduction to the Case Study
- business events / 5.4.1 The Business System Model as Foundation
- business object / 5.2 Messages in UML
- modeling / 5.5 The Static View
- relevant information, collecting / Collect Information Relevant for the Business Objects—What Do We Want to Read?
- designing / Collect Information Relevant for the Business Objects—What Do We Want to Read?
- structure / Construct Class Diagram—What is the Structure of the Business Object?
- classes, defining / Define Classes and Relationships of the Business Object—Which Class Relationships do We Need?
- relationships, defining / Define Classes and Relationships of the Business Object—Which Class Relationships do We Need?
- business process
- about / 3.1.1 What is a Business Process?
- UML, using / 3.1.4 Using UML to Model Business Processes and Business Systems
- modeling, tips for / 3.1.5 Practical Tips for Modeling Business Processes
- business rules
- static business rules / 4.2.3 Static and Dynamic Business Rules
- dynamic business rules / 4.2.3 Static and Dynamic Business Rules
- business system
- about / 3.1.3 Business Systems
- UML, using / 3.1.4 Using UML to Model Business Processes and Business Systems
- external view / 3.2 One Model—Two Views
- internal view / 3.2 One Model—Two Views
- benefits / 3.3.1 What Benefit does a Business System Provide?
- business use cases / Business Use Cases
- actors / Actors
- designating / Designate Actors and Business System—Who is Taking Part?
- business system model
- changes / 2.7.2 Effects on the Business System Model
- using, as integration foundation / 5.4.1 The Business System Model as Foundation
- business system passenger services / 5.4.1 The Business System Model as Foundation
- business use cases
- about / Business Use Cases
- identifying / Identifying Potential Business Use Cases—Which Goods and Services can Actors Draw Upon?
- connecting / Connecting Business Use Cases—Who Can Make Use of What Goods and Services of the Business System?
- searching / Searching for More Business Use Cases—What else Needs to be Done?
- editing / Editing Business Use Cases—What actually has to be Included in a Business Use Case?
- documenting / Documenting Business Use Cases—What Happens in a Business Use Case?
- modeling, relationship between / Modeling Relationships between Business Use Cases—What Activities are Conducted Repeatedly?
- Actors, adopting from / Adopt Actors from Business Use Cases—Who is Responsible for Each Action?
C
- case study
- about / 2.1 Introduction to the Case Study
- passenger check-in / 2.1 Introduction to the Case Study
- passenger boarding / 2.1 Introduction to the Case Study
- passenger services / 2.1 Introduction to the Case Study
- creating, purpose / 2.1 Introduction to the Case Study
- case study models
- about / 2.4 The Models of our Case Study
- business system / 2.4 The Models of our Case Study
- IT system / 2.4 The Models of our Case Study
- system integration / 2.4 The Models of our Case Study
- CASE tools
- about / 2.2.5 Diagrams as Views
- check-in employee / 4.1.1 The User View or "I don't care how it works, as long as it works.", Reading Use Case Diagrams
- check-in options
- Normal check-in / 2.1 Introduction to the Case Study
- Express check-in / 2.1 Introduction to the Case Study
- Automated check-in / 2.1 Introduction to the Case Study
- check-in representative / Identifying Potential Actors—Which Partners and Customers Use the Goods and Services of the Business System?, 4.1.1 The User View or "I don't care how it works, as long as it works."
- class diagram
- about / 3.4.4 Class Diagram, 4.2.5 Class Diagram, 5.5.2 Class Diagram
- reading / Reading Class Diagrams, Reading Class Diagrams, Reading Class Diagrams
- constructing / 3.4.5 Constructing Class Diagrams, Create Associations Between Classes—Which Classes Deal with Each Other?, Substantiate Associations—What do these Relationships Mean?, Verify the View—Is Everything Correct?, 4.2.6 Constructing Class Diagrams, 5.5.3 Constructing Class Diagrams, Construct Class Diagram—What is the Structure of the Business Object?
- constructing, steps / 4.2.6 Constructing Class Diagrams
- model classes, identifying / Identify and Model Classes—Which Classes do We Need?
- model associations, identifying / Identify and Model Associations—How Are the Classes Connected?
- attributes, defining / Define Attributes—What do We Want to Know about the Objects?
- queries, identifying / List Required Queries and Inputs—What does the IT System Need to Deliver and Accept?
- inputs, identifying / List Required Queries and Inputs—What does the IT System Need to Deliver and Accept?
- inputs, formulating / Formulate Queries and Inputs—How Exactly Should the Display Look?
- queries, formulating / Formulate Queries and Inputs—How Exactly Should the Display Look?
- information analysis, conducting / Conduct Information Analysis—Which Classes, Associations, and Attributes Do We Need?
- consolidating / Consolidate Class Diagrams—How Does Everything Fit Together?
- verifying / Verify the Class Diagrams—Is Everything Correct?
- business object information, collecting / Collect Information Relevant for the Business Objects—What Do We Want to Read?
- contents / Adopt Classes and Attributes from the Class Diagram of the IT System—What is Present in the Class Diagram?
- data elements, deriving / Derive Remaining Data Elements—From Where Do I Get the Rest?
- class relationships, requiring / Define Classes and Relationships of the Business Object—Which Class Relationships do We Need?
- verifying, in static view / Verify the View—Is Everything Correct?
- classes
- about / 4.2.1 Objects and Classes
- communication diagrams
- elements / 4.4.3 Communication Diagram
- constructing / 4.4.5 Constructing Communication Diagrams
- constructing, steps / Draft Query Result—What do We Want?, Identify Involved Classes—Which Classes Do We Need?, Define Initial Object—Where Do We Start?, Design Event Path—Where Do We Go?, Amend Event Path—Exactly Which Objects do We Need?, Identify Necessary Attributes—What Exactly Do We Want to Know?, Verify the Communication Diagram—Is Everything Correct?
- communication diagrams
- reading / Reading Communication Diagrams
- communication diagrams construction steps
- query result, drafting / Draft Query Result—What do We Want?
- classes, identifying / Identify Involved Classes—Which Classes Do We Need?
- initial object, defining / Define Initial Object—Where Do We Start?
- event path, designing / Design Event Path—Where Do We Go?
- event path, amending / Amend Event Path—Exactly Which Objects do We Need?
- attributes, identifying / Identify Necessary Attributes—What Exactly Do We Want to Know?
- verification / Verify the Communication Diagram—Is Everything Correct?
- communication diagrams elements
- Actor / 4.4.3 Communication Diagram
- query event / 4.4.3 Communication Diagram
- parameter / 4.4.3 Communication Diagram
- iteration / 4.4.3 Communication Diagram
- object / 4.4.3 Communication Diagram
- entry object / 4.4.3 Communication Diagram
D
- database / 2.2.5 Diagrams as Views
- Degree of Hazardousness attribute / 4.2.2 Generalization, Specialization, and Inheritance
- diagram
- using, as view / 2.2.5 Diagrams as Views
- constructing, in process view / 5.4.5 Constructing Diagrams in the Process View
- diagram, constructing in process view
- interfaces, determining / Determine Interfaces—Between Which IT Systems Should Communication Take Place?
- involved systems, identifying / Identify Involved Systems—Which IT Systems Exchange Information?
- activities, identifying / Identify Activities and Control Flow—What has to be Done and Who is Responsible for It?
- control flow, identifying / Identify Activities and Control Flow—What has to be Done and Who is Responsible for It?
- messages, defining / Define Messages—Which Messages have to be Exchanged?
- rules, defining / Define Rules—What Influences Actions?
- verification / Verify the View—Is Everything Correct?
E
- EAI
- EDI
- about / Electronic Data Interchange
- emphasizing
- about / 2.2.1 What is a Model?
- engineering approach / 2.5 History of UML: Methods and Notations
- Enterprise Application Integration (EAI) / 2.7.4 Effects on the Systems Integration Model
- ETD
- external view / 3.2 One Model—Two Views, 5.4.1 The Business System Model as Foundation
- about / 3.2 One Model—Two Views, 4.1.1 The User View or "I don't care how it works, as long as it works."
- business system, benefits / 3.3.1 What Benefit does a Business System Provide?
- elements / 3.3.2 The Elements of a View
- Use case diagrams / 3.3.3 Use Case Diagrams
- Use Case Diagrams, constructing / 3.3.4 Constructing Use Case Diagrams
- Activity diagrams / 3.3.5 Activity Diagrams
- Activity diagrams, constructing / 3.3.6 Constructing Activity Diagrams
- sequence diagrams / 3.3.7 Sequence Diagrams
- sequence diagrams, constructing / 3.3.8 Constructing Sequence Diagrams
- high-level sequence diagrams / 3.3.9 High-Level Sequence Diagrams
- sequence diagrams, for scenarios of business use cases / 3.3.10 Sequence Diagrams for Scenarios of Business Use Cases
- elements, containing / 4.1.1 The User View or "I don't care how it works, as long as it works."
- constructing / 4.1.6 Constructing the External View, Identify Potential Actors—Who Works with the IT System?, Connect Actors and Use Cases—Who Can Do What with the IT System?, Search for More Use Cases—What Functionalities does the IT System have to Provide?, Edit Use Cases—What Actually Has to be Included in a Use Case?, Document Use Cases—What Happens in a Use Case?, Verify the View—Is Everything Correct?
- information sources, collecting / Collect Information Sources—How Am I Supposed to Know That?
- potential actors, identifying / Identify Potential Actors—Who Works with the IT System?
- actors, describing / Describe Actors—Who or What do the Actors Represent?
- use cases, searching for / Search for More Use Cases—What Functionalities does the IT System have to Provide?
- use cases, editing / Edit Use Cases—What Actually Has to be Included in a Use Case?
- use cases, documenting / Document Use Cases—What Happens in a Use Case?
- model relationships between use cases / Model Relationships between Use Cases—What can be Reused?
- verifying / Verify the View—Is Everything Correct?
- use case diagram, verifying / Verify the View—Is Everything Correct?
- use case sequence diagram, verifying / Verify the View—Is Everything Correct?
- external view elements
- user interface / 4.1.1 The User View or "I don't care how it works, as long as it works."
- use case diagrams / 4.1.2 The Elements of a View, 4.1.3 Use Case Diagram
- use case sequence diagrams / 4.1.2 The Elements of a View
- interface prototypes / 4.1.2 The Elements of a View
F
- flight / 2.1 Introduction to the Case Study
- flight number / 2.1 Introduction to the Case Study
- Freight class / 4.2.2 Generalization, Specialization, and Inheritance
G
- generalization
- graphs
- about / 2.2.5 Diagrams as Views
H
- Hierarchy Input Processing Output (HIPO) method / 2.5 History of UML: Methods and Notations
- high-level sequence diagrams / 3.3.9 High-Level Sequence Diagrams
I
- IATA
- information sources
- information systems
- history / 2.3 Information Systems and IT Systems
- implementing, as IT systems / 2.3 Information Systems and IT Systems
- inheritance
- initiator
- interaction view
- about / 4.4.1 Seeing What Happens Inside the IT System
- elements / 4.4.2 Elements of the View
- communication diagrams / 4.4.3 Communication Diagram
- communication diagrams, reading / Reading Communication Diagrams
- sequence diagrams / 4.4.4 Sequence Diagram
- sequence diagrams, reading / Reading Sequence Diagrams
- communication diagrams, constructing / 4.4.5 Constructing Communication Diagrams, Draft Query Result—What do We Want?, Identify Involved Classes—Which Classes Do We Need?, Define Initial Object—Where Do We Start?, Design Event Path—Where Do We Go?, Amend Event Path—Exactly Which Objects do We Need?, Identify Necessary Attributes—What Exactly Do We Want to Know?, Verify the Communication Diagram—Is Everything Correct?
- sequence diagrams, constructing / 4.4.6 Constructing Sequence Diagrams, Propagate Events—How is the Mutation Event Forwarded?, Specify Event Parameter—What do Objects have to Know?
- interaction view elements
- about / 4.4.2 Elements of the View
- communication diagrams / 4.4.2 Elements of the View
- sequence diagrams / 4.4.2 Elements of the View
- internal view / 3.2 One Model—Two Views, 5.4.1 The Business System Model as Foundation
- about / 3.2 One Model—Two Views
- elements / 3.4.1 The Elements of the View
- package diagram / 3.4.2 Package Diagram
- package diagram, constructing / 3.4.3 Constructing Package Diagrams
- class diagram / 3.4.4 Class Diagram
- class diagram, constructing / 3.4.5 Constructing Class Diagrams
- Activity diagrams / 3.4.6 Activity Diagram
- Activity diagrams, constructing / 3.4.7 Constructing Activity Diagrams
- invoice receipt event / Messages
- IT system
- IT system data
- tranforming, to message passenger list / 5.5.4 Transforming Data from the IT System to the Message "passenger list"
- flight data, transforming / Transformation of Flight Data
- passenger data, transforming / Transformation of Passenger Data
- IT system model
- changes / 2.7.3 Effects on the IT System Model
K
- knowledge carriers
- working with / 2.2.4 Process of Analysis
- finding / Practical Tips
M
- MDA
- Model
- about / 2.2.1 What is a Model?
- views / 2.2.1 What is a Model?
- tasks, performing / 2.2.2 Why do we Need Models?
- creating, purpose / 2.2.3 Purpose and Target Group of a Model
- target group, defining / 2.2.3 Purpose and Target Group of a Model
- analysis process / 2.2.4 Process of Analysis
- Model purpose
- business expertise, expecting / 2.2.3 Purpose and Target Group of a Model
- Model target group
- detail, requiring / 2.2.3 Purpose and Target Group of a Model
- time, requiring / 2.2.3 Purpose and Target Group of a Model
- language / 2.2.3 Purpose and Target Group of a Model
- abstraction level / 2.2.3 Purpose and Target Group of a Model
- Model tasks
- communication / 2.2.2 Why do we Need Models?
- visualization / 2.2.2 Why do we Need Models?
- verification / 2.2.2 Why do we Need Models?
- mutation events / 4.4.2 Elements of the View
N
- no boarding procedure / 5.4.1 The Business System Model as Foundation
O
- objects
- about / 4.2.1 Objects and Classes
- modelling / 4.2.1 Objects and Classes
- life cycle / 4.3.1 The Life of an Object
- OCL
- about / 2.7.1 Overview of UML 2.0
- omitting
- about / 2.2.1 What is a Model?
- OMT
- OOSE
- operators / 2.7.2 Effects on the Business System Model
P
- package diagram
- about / 3.4.2 Package Diagram
- reading / Reading Package Diagrams
- constructing / 3.4.3 Constructing Package Diagrams
- checklist, in internal view / 3.4.3 Constructing Package Diagrams, Find Additional Organization Units—Who Else is There?, Verify the View—Is Everything Correct?
- passenger / 4.1.1 The User View or "I don't care how it works, as long as it works."
- passenger check-in / 2.1 Introduction to the Case Study
- passenger class / 4.4.3 Communication Diagram
- passenger list to customs procedure / 5.4.1 The Business System Model as Foundation
- Passenger Services
- about / 3.1.3 Business Systems
- Piece of Luggage attribute / 4.2.2 Generalization, Specialization, and Inheritance
- potential actors
- process view
- about / 5.4 Process View
- business system model, using as integration foundation / 5.4.1 The Business System Model as Foundation
- elements / 5.4.2 Elements of the View
- activity diagram / 5.4.3 Activity Diagrams
- activity diagram, reading / Reading Activity Diagrams
- sequence diagram / 5.4.4 Sequence Diagram
- sequence diagram, reading / Reading Sequence Diagrams
- diagrams, constructing / 5.4.5 Constructing Diagrams in the Process View, Determine Interfaces—Between Which IT Systems Should Communication Take Place?, Identify Involved Systems—Which IT Systems Exchange Information?, Identify Activities and Control Flow—What has to be Done and Who is Responsible for It?, Define Messages—Which Messages have to be Exchanged?, Define Rules—What Influences Actions?, Verify the View—Is Everything Correct?
Q
- queries / 4.4.2 Elements of the View
R
- reference data / Messages
- requirement specification
- about / 2.6 Requirement Specification
- decision, making / 2.6.1 Guidance for Decision Making
- verifying / 2.6.2 Verification
S
- scenario
- sequence diagram elements
- object / 5.4.4 Sequence Diagram
- message / 5.4.4 Sequence Diagram
- message flow / 5.4.4 Sequence Diagram
- argument / 5.4.4 Sequence Diagram
- sequence diagrams / 3.3.2 The Elements of a View
- about / 3.3.7 Sequence Diagrams, 5.4.4 Sequence Diagram
- reading / Reading Sequence Diagrams, Reading Sequence Diagrams, Reading Sequence Diagrams
- constructing / 3.3.8 Constructing Sequence Diagrams, 4.4.6 Constructing Sequence Diagrams
- elements / 4.4.4 Sequence Diagram, 5.4.4 Sequence Diagram
- constructing, steps / Identify Involved Classes—What is Affected by Mutation Events?, Determine Initial Object—Where does the Mutation Event go First?, Specify Event Parameter—What do Objects have to Know?
- verifying, in process view / Verify the View—Is Everything Correct?
- sequence diagrams construction steps
- classes, identifying / Identify Involved Classes—What is Affected by Mutation Events?
- initial object, determining / Determine Initial Object—Where does the Mutation Event go First?
- events, propogating / Propagate Events—How is the Mutation Event Forwarded?
- event parameter, specifying / Specify Event Parameter—What do Objects have to Know?
- verification / Verify the Sequence Diagram—Is Everything Correct?
- sequence diagrams elements
- comment / 4.4.4 Sequence Diagram
- actor / 4.4.4 Sequence Diagram
- mutation event / 4.4.4 Sequence Diagram
- object / 4.4.4 Sequence Diagram
- iteration / 4.4.4 Sequence Diagram
- lifeline / 4.4.4 Sequence Diagram
- software crisis / 2.5 History of UML: Methods and Notations
- specialization
- statechart diagram
- elements / 4.3.3 Statechart Diagram
- reading / Reading Statechart Diagrams
- constructing / 4.3.4 Constructing Statechart Diagrams
- statechart diagram construction steps
- object relevant mutation events, identifying / Identify Mutation Events Relevant for the Object—What Affects the Object?
- relevant mutation events, chronologically grouping / Group Relevant Events Chronologically—How Does a Normal Life Look?
- model states / Model States and Transitions—Which States are There?
- transitions / Model States and Transitions—Which States are There?
- actions, adding / Add Actions to the Statechart Diagram—What do Objects Do?
- verifying / Verify Statechart Diagram—Is Everything Correct?
- statechart diagram elements
- initial state / 4.3.3 Statechart Diagram
- state / 4.3.3 Statechart Diagram
- transition / 4.3.3 Statechart Diagram
- internal transition / 4.3.3 Statechart Diagram
- mutation event / 4.3.3 Statechart Diagram
- action / 4.3.3 Statechart Diagram
- guard condition / 4.3.3 Statechart Diagram
- final state / 4.3.3 Statechart Diagram
- static view
- about / 5.5 The Static View
- business objects, modeling / 5.5 The Static View
- elements / 5.5.1 Elements of the View
- class diagram / 5.5.2 Class Diagram
- class diagram, reading / Reading Class Diagrams
- class diagram, constructing / 5.5.3 Constructing Class Diagrams, Collect Information Relevant for the Business Objects—What Do We Want to Read?, Adopt Classes and Attributes from the Class Diagram of the IT System—What is Present in the Class Diagram?, Derive Remaining Data Elements—From Where Do I Get the Rest?, Define Classes and Relationships of the Business Object—Which Class Relationships do We Need?
- class diagram, verifying / Verify the View—Is Everything Correct?
- data, transforming / 5.5.4 Transforming Data from the IT System to the Message "passenger list", Transformation of Flight Data, Transformation of Passenger Data
- UML messages, transforming into standard formats / 5.5.5 Transformation of UML Messages into Various Standard Formats
- static view element
- class / 5.5.2 Class Diagram
- structural view
- about / 4.2.1 Objects and Classes
- objects / 4.2.1 Objects and Classes
- classes / 4.2.1 Objects and Classes
- generalization / 4.2.2 Generalization, Specialization, and Inheritance
- specialization / 4.2.2 Generalization, Specialization, and Inheritance
- inheritance / 4.2.2 Generalization, Specialization, and Inheritance
- business rules / 4.2.3 Static and Dynamic Business Rules
- elements / 4.2.4 Elements of the View
- class diagram / 4.2.5 Class Diagram
- class diagrams, verifying / Verify the Class Diagrams—Is Everything Correct?
- structural view elements
- class / 4.2.5 Class Diagram
- attribute / 4.2.5 Class Diagram
- generalization / 4.2.5 Class Diagram
- association / 4.2.5 Class Diagram
- multiplicity / 4.2.5 Class Diagram
- aggregation / 4.2.5 Class Diagram
- subordinate business process / 5.4.1 The Business System Model as Foundation
- SWIFT
- about / Electronic Data Interchange
- system integration model
- process view / 5.3 One Model—Two Views
- static view / 5.3 One Model—Two Views
- system integration terminology
- interfaces / Interfaces
- messages / Messages
- EAI / Enterprise Application Integration
- EDI / Electronic Data Interchange
- UN/EDIFACT / UN/EDIFACT
- XML / XML
- systems integration model
T
- ticket / 2.1 Introduction to the Case Study
U
- UML
- history / 2.5 History of UML: Methods and Notations
- used, to model business process / 3.1.4 Using UML to Model Business Processes and Business Systems
- used, to model business system / 3.1.4 Using UML to Model Business Processes and Business Systems
- events / 4.1.4 Query Events and Mutation Events
- messages / 5.2 Messages in UML
- UML 2.0
- about / 2.7.1 Overview of UML 2.0
- infrastructure / 2.7.1 Overview of UML 2.0
- superstructure / 2.7.1 Overview of UML 2.0
- advantages / 2.7.1 Overview of UML 2.0
- Business system model changes / 2.7.2 Effects on the Business System Model
- IT system model changes / 2.7.3 Effects on the IT System Model
- Systems integration model changes / 2.7.4 Effects on the Systems Integration Model
- UML diagrams
- Use case diagrams / 3.3.2 The Elements of a View
- Activity diagrams / 3.3.2 The Elements of a View
- sequence diagrams / 3.3.2 The Elements of a View
- UML events
- about / 4.1.4 Query Events and Mutation Events
- query events / 4.1.4 Query Events and Mutation Events
- mutation events / 4.1.4 Query Events and Mutation Events
- UML history
- about / 2.5 History of UML: Methods and Notations
- methods / 2.5 History of UML: Methods and Notations
- notions / 2.5 History of UML: Methods and Notations
- Booch Method / 2.5 History of UML: Methods and Notations
- OMT / 2.5 History of UML: Methods and Notations
- OOSE / 2.5 History of UML: Methods and Notations
- UML message
- about / 5.2 Messages in UML
- categorically dividing / 5.2 Messages in UML
- transforming, into standard formats / 5.5.5 Transformation of UML Messages into Various Standard Formats
- UN/ECE
- about / UN/EDIFACT
- UN/EDIFACT
- about / UN/EDIFACT
- URL / UN/EDIFACT
- Use case diagrams / 3.3.2 The Elements of a View
- about / 3.3.3 Use Case Diagrams
- reading / Reading Use Case Diagrams
- constructing / 3.3.4 Constructing Use Case Diagrams
- information sources, collecting / Collecting Information Sources—How am I Supposed to Know That?
- potential actors, identifying / Identifying Potential Actors—Which Partners and Customers Use the Goods and Services of the Business System?
- potential business use cases, identifying / Identifying Potential Business Use Cases—Which Goods and Services can Actors Draw Upon?
- business use cases, connecting / Connecting Business Use Cases—Who Can Make Use of What Goods and Services of the Business System?
- actors, describing / Describing Actors—Who or What do the Actors Represent?
- business use cases, searching / Searching for More Business Use Cases—What else Needs to be Done?
- business use cases, editing / Editing Business Use Cases—What actually has to be Included in a Business Use Case?
- business use cases, documenting / Documenting Business Use Cases—What Happens in a Business Use Case?
- business use cases, relationships modeling between / Modeling Relationships between Business Use Cases—What Activities are Conducted Repeatedly?
- View, verifying / Verifying the View—Is Everything Correct?
- use case diagrams
- about / 4.1.3 Use Case Diagram
- elements / 4.1.3 Use Case Diagram
- reading / Reading Use Case Diagrams
- use case diagrams elements
- actor / 4.1.3 Use Case Diagram
- use cases / 4.1.3 Use Case Diagram
- association / 4.1.3 Use Case Diagram
- include relationship / 4.1.3 Use Case Diagram
- use cases
- use case sequence diagram
- about / 4.1.5 Use Case Sequence Diagram
- elements / 4.1.5 Use Case Sequence Diagram
- reading / Reading Use Case Sequence Diagrams
- use case sequence diagram elements
- comment / 4.1.5 Use Case Sequence Diagram
- references / 4.1.5 Use Case Sequence Diagram
- actor / 4.1.5 Use Case Sequence Diagram
- query event / 4.1.5 Use Case Sequence Diagram
- mutation event / 4.1.5 Use Case Sequence Diagram
- interaction reference / 4.1.5 Use Case Sequence Diagram
- IT system / 4.1.5 Use Case Sequence Diagram
V
- View
- views
- about / 2.2.1 What is a Model?, 2.2.5 Diagrams as Views
- diagram, using as / 2.2.5 Diagrams as Views
W
- W3C
- URL / XML
- Weight attribute / 4.2.2 Generalization, Specialization, and Inheritance
- Workflow Management Coalition