OMG Updated OMG-OCUP2-FOUND100 Exam Questions and Answers by gloria

In UML, a Class is a template that defines the structure and behavior of objects, whereas a DataType is a type of classifier which specifies a domain of values without identity. Operations (such as money transfers and withdrawals) are behaviors that change the state of an object and, therefore, are defined in Classes rather than DataTypes. This suggests that accounts, which require operations to transfer and withdraw money, should be modeled as Classes.

References:

• UML 2.x Superstructure Specification: Provides definitions for Classes and DataTypes, and details the circumstances under which each should be used. It specifically states that Classes can have operations while DataTypes cannot.
• UML 2.x Infrastructure Specification: This foundational document provides an in-depth explanation of UML modeling constructs, supporting the use of Classes when operations are needed to manage an object's state.

In a UML system, the state machine associated with an object becomes active and ready to process events as soon as the object's initialization process is complete. Here's why:

• Object Creation and State Machines: When an object is created, its associated state machine is instantiated along with it. This means the state machine's structural elements (states, transitions, etc.) are established.
• Initialization and the Initial State: During the object's initialization phase, essential attributes and relationships might be set up, and the state machine enters its designated initial state.
• Event Readiness: Once initialization is complete, the object and its state machine are considered "operational" and can respond to events as defined by the state machine's logic.

Why Other Options are Incorrect:

• A. by the time the last state ends: State machines often don't have a designated "last" state. Their execution is based on events and can continue indefinitely. Additionally, a state machine can be ready to handle events long before ending.
• B. immediately after the sequence diagrams start: Sequence diagrams illustrate interactions between objects, but they don't dictate the exact timing of object creation or state machine readiness in the overall system.
• D. when all objects in the system are ready to receive events: While system-wide coordination might be necessary, an individual object's state machine readiness is dependent on its own initialization, not on the state of every other object.

References:

• UML Specification (Superstructure) Version 2.5.1: Specifically, sections covering state machines (https://www.omg.org/spec/UML/2.5.1).
• Practical guides to UML and object-oriented modeling often discuss object creation and state machine lifecycles.

In UML 2, a class diagram is used to depict the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among the classes. The constraint{age >= 18}in thePersonclass diagram indicates a condition that must hold true for the instances of thePersonclass whenever they are used in the context of aBankAccount. This constraint is an invariant of thePersonclass that specifies the rule for the attributeage.

Now, let's consider the provided options and explain why option B is correct:

A. The preferred age to open a bank account is 18 years old or older – This statement is incorrect because the diagram does not indicate a preference; it indicates a constraint or a rule.

B. Only customers who are 18 years old or older can open a bank account – This is the correct statement. The{age >= 18}constraint next to theageattribute of thePersonclass signifies that any instance ofPersonassociated with aBankAccountmust be at least 18 years old. SincePersonis connected toBankAccountwith the role namecustomer, this implies that only persons who are at least 18 can be customers of a bank account.

C. The age condition should only hold when the setAge(Integer) function is called – This statement is incorrect because the constraint{age >= 18}is not a condition that applies only when thesetAgeoperation is invoked. Instead, it is a class invariant that must always hold true for any instance ofPerson.

D. An object of Customer with age set to 18 or greater will raise an exception – This is incorrect because the UML diagram specifies a constraint, not an exception condition. The constraint ensures validity, not the raising of an exception.

The answer is verified according to the UML 2 Foundation documents, such as the UML 2.5 specification, where class diagrams and constraints are defined. The specification states that constraints are semantic conditions or restrictions expressed in natural language text or in a machine-readable language that must hold true for the system being modeled (UML 2.5 specification, section 7.9).

An execution occurrence specification in UML sequence diagrams is represented by a thin rectangle on a lifeline. It shows that an instance is performing an action over a period of time.

In the provided sequence diagram, we can see three such thin rectangles on lifeline 'b', which indicates that there are three execution occurrence specifications.

• One for the message that comes from 'a' to 'b'.
• Another one for the message that 'b' sends to 'c'.
• And the last one for the return message from 'c' to 'b'.

There are no execution occurrence specifications on lifelines 'a' and 'c'.

Therefore, the correct answer is:

D. 3