Question #1
Which modeling relationship allows instances of one class to substitute for instances of another?
- A . auxiliary
- B . association
- C . dependency
- D . replacement
- E . generalization
Correct Answer: E
E
Explanation:
Generalization in UML is a modeling relationship that connects a general classifier (like a class) to a more specific classifier. It is akin to an "is a" relationship where the specialized element (subclass) inherits features from the general element (superclass), thus allowing instances of the subclass to substitute for instances of the superclass. For example, if "Bird" is a superclass and "Eagle" is a subclass, an instance of "Eagle" can substitute for an instance of "Bird". This relationship is fundamental in object-oriented modeling for representing inheritance. According to the UML 2.5
specification, generalization allows a subclass to inherit part or all of the structure and behavior of a superclass.
E
Explanation:
Generalization in UML is a modeling relationship that connects a general classifier (like a class) to a more specific classifier. It is akin to an "is a" relationship where the specialized element (subclass) inherits features from the general element (superclass), thus allowing instances of the subclass to substitute for instances of the superclass. For example, if "Bird" is a superclass and "Eagle" is a subclass, an instance of "Eagle" can substitute for an instance of "Bird". This relationship is fundamental in object-oriented modeling for representing inheritance. According to the UML 2.5
specification, generalization allows a subclass to inherit part or all of the structure and behavior of a superclass.
Question #2
How is the abstract syntax of UML specified?
- A . using a MOF metamodel
- B . using the Backus-Naur Form (BNF)
- C . using natural language (e.g.. English)
- D . using UML structure and behavior diagrams
Correct Answer: A
A
Explanation:
The abstract syntax of UML is specified using the Meta-Object Facility (MOF) metamodel. MOF is a modeling language that provides a meta-meta-model at the top layer of the four-layer metadata architecture, which is used to define the metamodels, like the UML. The MOF specification defines the structure and semantics for constructing metamodels, including the UML. By using MOF, UML ensures that its structure is well-defined and can be processed by tools that understand MOF-based metamodels. The use of MOF to specify UML abstract syntax ensures a clear, structured, and standardized method of describing the semantics of UML components, enabling consistent interpretation and implementation across different modeling tools and environments.
A
Explanation:
The abstract syntax of UML is specified using the Meta-Object Facility (MOF) metamodel. MOF is a modeling language that provides a meta-meta-model at the top layer of the four-layer metadata architecture, which is used to define the metamodels, like the UML. The MOF specification defines the structure and semantics for constructing metamodels, including the UML. By using MOF, UML ensures that its structure is well-defined and can be processed by tools that understand MOF-based metamodels. The use of MOF to specify UML abstract syntax ensures a clear, structured, and standardized method of describing the semantics of UML components, enabling consistent interpretation and implementation across different modeling tools and environments.
Question #3
What represents the most appropriate use of UML during software development?
- A . forcing management decisions
- B . describing a planned or existing system to non-technical stakeholders
- C . capturing and clarifying the business-level concerns of a planned or existing system
- D . capturing the essential characteristics and design decisions of a planned or existing system
Correct Answer: D
D
Explanation:
The most appropriate use of UML during software development is to capture the essential characteristics and design decisions of a planned or existing system. UML (Unified Modeling Language) is primarily utilized to visually represent the architecture, design, and behavior of a system, which includes detailing the components, relationships, and interactions within the system. This makes it a critical tool for understanding complex systems and making informed design decisions that align with project requirements and constraints. UML facilitates clear communication among development team members and stakeholders, ensuring that design decisions are well-understood and accurately implemented.
D
Explanation:
The most appropriate use of UML during software development is to capture the essential characteristics and design decisions of a planned or existing system. UML (Unified Modeling Language) is primarily utilized to visually represent the architecture, design, and behavior of a system, which includes detailing the components, relationships, and interactions within the system. This makes it a critical tool for understanding complex systems and making informed design decisions that align with project requirements and constraints. UML facilitates clear communication among development team members and stakeholders, ensuring that design decisions are well-understood and accurately implemented.
Question #4
For projects involving complex and strategic systems, what is a key advantage of developing models before starting implementation?
- A . Developing models ensures that all requirements will be addressed.
- B . Models are useful to provide proof of progress to project management.
- C . Models help to establish a consensus among all the project stakeholders.
- D . Modeling helps to convince developers that models are necessary for good design.
Correct Answer: C
C
Explanation:
For projects involving complex and strategic systems, a key advantage of developing models before starting implementation is that models help to establish a consensus among all the project stakeholders. Creating UML models in the early stages of a project provides a visual and conceptual representation of the system that can be easily understood by various stakeholders, including developers, managers, and clients. This facilitates discussions and negotiations about the system’s design and functionality, helping to ensure that all parties have a shared understanding and agreement on the project’s objectives and solutions before significant resources are invested in implementation.
C
Explanation:
For projects involving complex and strategic systems, a key advantage of developing models before starting implementation is that models help to establish a consensus among all the project stakeholders. Creating UML models in the early stages of a project provides a visual and conceptual representation of the system that can be easily understood by various stakeholders, including developers, managers, and clients. This facilitates discussions and negotiations about the system’s design and functionality, helping to ensure that all parties have a shared understanding and agreement on the project’s objectives and solutions before significant resources are invested in implementation.
Question #5
Why are abstractions in a model helpful?
- A . Abstractions add the full detail to the model.
- B . Abstractions can express or suppress detail as needed.
- C . Abstractions can be taken out and the model still makes sense.
- D . Abstractions are not helpful, but rather a distraction in models.
Correct Answer: B
B
Explanation:
Abstractions in a model are helpful because they can express or suppress detail as needed. This capability is essential in managing complexity in a model by focusing on the high-level, essential aspects of the system while omitting or simplifying the less critical details. This selective detail management aids in understanding and analyzing the system’s core functionality without getting overwhelmed by its intricacies. Abstractions facilitate clearer communication, more focused analysis, and more efficient system design by highlighting the most relevant aspects of the system in various contexts.
B
Explanation:
Abstractions in a model are helpful because they can express or suppress detail as needed. This capability is essential in managing complexity in a model by focusing on the high-level, essential aspects of the system while omitting or simplifying the less critical details. This selective detail management aids in understanding and analyzing the system’s core functionality without getting overwhelmed by its intricacies. Abstractions facilitate clearer communication, more focused analysis, and more efficient system design by highlighting the most relevant aspects of the system in various contexts.
Question #6
Which technique does Abstraction incorporate?
- A . agile modeling
- B . information hiding
- C . complexity coupling
- D . context-driven decision making
Correct Answer: B
B
Explanation:
Abstraction in UML and software modeling often incorporates the technique of information hiding. Information hiding is a principle that supports abstraction by ensuring that unnecessary details about software components are not exposed to other parts of the system. This encapsulation strengthens modularity and keeps various parts of the program independent of one another, which simplifies complexity in large systems. Abstraction and information hiding are closely related; abstraction focuses on the high-level structure of the system, while information hiding protects the internal states and functionality of components, allowing changes without extensive impact on other system parts.
B
Explanation:
Abstraction in UML and software modeling often incorporates the technique of information hiding. Information hiding is a principle that supports abstraction by ensuring that unnecessary details about software components are not exposed to other parts of the system. This encapsulation strengthens modularity and keeps various parts of the program independent of one another, which simplifies complexity in large systems. Abstraction and information hiding are closely related; abstraction focuses on the high-level structure of the system, while information hiding protects the internal states and functionality of components, allowing changes without extensive impact on other system parts.
Question #7
What is the defining characteristic of a domain model?
- A . It is a model that is specified using UML diagrams.
- B . It is a model that focuses on the domain requirements of the system
- C . It is a model that captures the main domain concepts and their relationships.
- D . It is a model that represents the domain architecture of the implementation of the system.
Correct Answer: C
C
Explanation:
A domain model’s defining characteristic is that it captures the main domain concepts and their relationships. This model focuses on representing the key elements within the problem domain, outlining how these elements interact with each other without detailing the specific implementations. The domain model is an essential tool in software development for understanding and communicating the fundamental structure of the system from a problem domain perspective, helping teams to design solutions that are well-aligned with actual domain needs. UML is often used to represent domain models due to its capability to visually and clearly model complex relationships and structures.
C
Explanation:
A domain model’s defining characteristic is that it captures the main domain concepts and their relationships. This model focuses on representing the key elements within the problem domain, outlining how these elements interact with each other without detailing the specific implementations. The domain model is an essential tool in software development for understanding and communicating the fundamental structure of the system from a problem domain perspective, helping teams to design solutions that are well-aligned with actual domain needs. UML is often used to represent domain models due to its capability to visually and clearly model complex relationships and structures.
Question #8
Which characteristic should apply to any useful model?
- A . It is specified in UML.
- B . It is platform independent.
- C . It abstracts away irrelevant detail.
- D . It is specified using a visual notation.
Correct Answer: C
C
Explanation:
A key characteristic that should apply to any useful model, including those created with UML, is that it abstracts away irrelevant details. This abstraction is crucial for managing complexity by focusing on the essential aspects of the system that are relevant to the current perspective or analysis task. By removing unnecessary information, the model remains understandable and manageable, even as the underlying system grows in complexity. This principle helps maintain a clear and concise representation of the system, enabling stakeholders to focus on strategic decisions without being overwhelmed by details.
C
Explanation:
A key characteristic that should apply to any useful model, including those created with UML, is that it abstracts away irrelevant details. This abstraction is crucial for managing complexity by focusing on the essential aspects of the system that are relevant to the current perspective or analysis task. By removing unnecessary information, the model remains understandable and manageable, even as the underlying system grows in complexity. This principle helps maintain a clear and concise representation of the system, enabling stakeholders to focus on strategic decisions without being overwhelmed by details.
Question #9
Which category of stakeholders should have prime responsibility for making decisions on the contents of a domain model, and why?
- A . The customers, as they will own the system when it is delivered
- B . The users, as they will be using the system when it is operational.
- C . All involved stakeholders, as they are knowledgeable and concerned.
- D . The development team, as they are responsible for the final implementation.
- E . Project managers, as they are responsible for delivering the right product to the customer
- F . The testing team, as test-driven design is proven to be an effective approach to development
- G . The system architects, as they are responsible for the design of the system and its proper functioning.
Correct Answer: B
B
Explanation:
In the development of a domain model, the prime responsibility for decision-making should ideally rest with the users, as they are the ones who will be using the system operationally. Users have the most direct and frequent interactions with the system, making them best positioned to provide relevant insights into what the system should do and how it should behave to meet their needs effectively. While other stakeholders such as customers, project managers, and developers play significant roles, the users’ intimate knowledge of the domain processes and their requirements make them key contributors to ensuring that the domain model aligns closely with real-world application and utility.
B
Explanation:
In the development of a domain model, the prime responsibility for decision-making should ideally rest with the users, as they are the ones who will be using the system operationally. Users have the most direct and frequent interactions with the system, making them best positioned to provide relevant insights into what the system should do and how it should behave to meet their needs effectively. While other stakeholders such as customers, project managers, and developers play significant roles, the users’ intimate knowledge of the domain processes and their requirements make them key contributors to ensuring that the domain model aligns closely with real-world application and utility.
Question #10
Which UML term pair captures complementary ways of looking at a relationship?
- A . include / extend
- B . use / implement
- C . dependency / trace
- D . aggregation / composition
- E . generalization / specialization
Correct Answer: D
D
Explanation:
The UML term pair that captures complementary ways of looking at a relationship is "aggregation / composition". Both terms describe types of associations between classes but differ in the degree of ownership and lifecycle dependency between the involved objects. Aggregation implies a weaker relationship where the parent class contains or is linked to other classes but does not strictly control their lifecycle (e.g., a university and its students). Composition, on the other hand, implies a stronger relationship where the parent class has full responsibility for the lifecycle of the associated classes (e.g., a house and its rooms). Understanding these relationships helps model systems more accurately in terms of object ownership and lifecycle management.
D
Explanation:
The UML term pair that captures complementary ways of looking at a relationship is "aggregation / composition". Both terms describe types of associations between classes but differ in the degree of ownership and lifecycle dependency between the involved objects. Aggregation implies a weaker relationship where the parent class contains or is linked to other classes but does not strictly control their lifecycle (e.g., a university and its students). Composition, on the other hand, implies a stronger relationship where the parent class has full responsibility for the lifecycle of the associated classes (e.g., a house and its rooms). Understanding these relationships helps model systems more accurately in terms of object ownership and lifecycle management.
Question #11
What is a reason to have all the UML diagrams of a model have the same amount of detail?
- A . This is typically required by management for planning purposes
- B . This is typically required by the implementers for coding purposes
- C . This is typically required by the system engineers to write requirements.
- D . This is typically required by tools that automatically transform the model.
Correct Answer: D
D
Explanation:
Having all the UML diagrams of a model maintain the same level of detail is typically required by tools that automatically transform the model into other forms, such as code or other types of models. Consistency in the level of detail across different diagrams ensures that automated tools can reliably interpret and convert the UML diagrams without encountering discrepancies that could lead to errors or misrepresentations in the generated outputs. This consistency is crucial for maintaining the integrity of the transformations and for ensuring that the resultant products accurately reflect the intended design and specifications.
D
Explanation:
Having all the UML diagrams of a model maintain the same level of detail is typically required by tools that automatically transform the model into other forms, such as code or other types of models. Consistency in the level of detail across different diagrams ensures that automated tools can reliably interpret and convert the UML diagrams without encountering discrepancies that could lead to errors or misrepresentations in the generated outputs. This consistency is crucial for maintaining the integrity of the transformations and for ensuring that the resultant products accurately reflect the intended design and specifications.
Question #12
Which statement characterizes a valuable model?
- A . A simple model that is useful has value.
- B . The value of a model is directly related to its complexity.
- C . A model must be "right" in an engineering sense to have value.
- D . The value of a model is always based on its ability to predict system behavior.
Correct Answer: A
A
Explanation:
A valuable model in UML and systems design is characterized by its usefulness rather than its complexity or how "correct" it is in an engineering sense. A model’s primary objective is to effectively communicate the key aspects of a system or process, and simplicity often enhances this communication by making the model easier to understand and use. The value of a model thus comes from its ability to facilitate decision-making, problem-solving, and understanding among stakeholders. This perspective aligns with the principle of Occam’s Razor in modeling, which suggests that simpler solutions are preferable when all other factors are equal. In UML, a model that provides clear insights with minimal complexity is considered more valuable because it is accessible to a wider audience and can be more readily applied to solve real-world problems.
A
Explanation:
A valuable model in UML and systems design is characterized by its usefulness rather than its complexity or how "correct" it is in an engineering sense. A model’s primary objective is to effectively communicate the key aspects of a system or process, and simplicity often enhances this communication by making the model easier to understand and use. The value of a model thus comes from its ability to facilitate decision-making, problem-solving, and understanding among stakeholders. This perspective aligns with the principle of Occam’s Razor in modeling, which suggests that simpler solutions are preferable when all other factors are equal. In UML, a model that provides clear insights with minimal complexity is considered more valuable because it is accessible to a wider audience and can be more readily applied to solve real-world problems.
Question #13
What is an advantage of modeling as a part of the software analysis and design process?
- A . It reduces the risk of inconsistent or improper implementations.
- B . It reduces the risk of incorporating technology constraints into a design.
- C . It reduces the risk of using an incorrect or improper programming language.
- D . It reduces the risk of the solution being strongly related to business practices.
Correct Answer: A
A
Explanation:
Modeling as part of the software analysis and design process offers several advantages, one of the primary being the reduction in the risk of inconsistent or improper implementations. By using models, developers can visualize the structure and behavior of the system before actual coding begins, allowing for the identification and correction of potential issues in the early stages of development. This practice helps ensure that all components of the software work together as intended, reducing the likelihood of bugs and inconsistencies that could arise if parts of the system were developed in isolation. UML, as a standardized modeling language, provides a coherent and universally understood set of diagrams and symbols, which facilitates clear communication among team members and stakeholders, further mitigating the risk of misunderstandings that could lead to improper implementations.
A
Explanation:
Modeling as part of the software analysis and design process offers several advantages, one of the primary being the reduction in the risk of inconsistent or improper implementations. By using models, developers can visualize the structure and behavior of the system before actual coding begins, allowing for the identification and correction of potential issues in the early stages of development. This practice helps ensure that all components of the software work together as intended, reducing the likelihood of bugs and inconsistencies that could arise if parts of the system were developed in isolation. UML, as a standardized modeling language, provides a coherent and universally understood set of diagrams and symbols, which facilitates clear communication among team members and stakeholders, further mitigating the risk of misunderstandings that could lead to improper implementations.
Question #14
Consider the following class diagram:
Which statement is true about the class diagram?
- A . The preferred age to open a bank account is 18 years old or older
- B . Only customers who are 18 years old or older can open a bank account.
- C . The age condition should only hold when the setAge(Integer) function is called
- D . An object of Customer with age set to 18 or greater will raise an exception.
Correct Answer: B
B
Explanation:
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 the Person class diagram indicates a condition that must hold true for the instances of the Person class whenever they are used in the context of a BankAccount. This constraint is an invariant of the Person class that specifies the rule for the attribute age.
Now, let’s consider the provided options and explain why option B is correct:
B
Explanation:
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 the Person class diagram indicates a condition that must hold true for the instances of the Person class whenever they are used in the context of a BankAccount. This constraint is an invariant of the Person class that specifies the rule for the attribute age.
Now, let’s consider the provided options and explain why option B is correct:
Question #15
Consider the following diagram:
Which statement is correct according to the diagram?
- A . responsiblePerson inherits from Person.
- B . Client and Manager have nothing in common.
- C . responsiblePerson can not refer to an object of class Client.
- D . The object referred to as responsiblePerson can be a Manager.
Correct Answer: D
D
Explanation:
In UML class diagrams, relationships between classes are represented in a number of different ways, including generalization, association, and composition.
Looking at the provided options, let’s analyze each one:
D
Explanation:
In UML class diagrams, relationships between classes are represented in a number of different ways, including generalization, association, and composition.
Looking at the provided options, let’s analyze each one:
Question #16
In the context of a UML model designed to capture the elements of a real-world business enterprise, the class Employee appears in the fragment of a class diagram as shown below:
Which actual entity does this element represent?
- A . An employee of the company
- B . The set of all employees of the company
- C . An anonymous employee of the company
- D . A diagram of an employee of the company
Correct Answer: B
B
Explanation:
In the context of a UML (Unified Modeling Language) model, the class named ‘Employee’ represents a template for all entities that are classified as employees within the business enterprise model.
Therefore, the correct answer is:
B. The set of all employees of the company
The term ‘Employee’ in the class diagram is a UML Class, which is defined as a description of a set of objects that share the same attributes, operations, relationships, and semantics (UML 2.5 specification, section 9.2). A class in UML is a blueprint from which individual objects (instances of the class) are created. It is not a representation of any single employee, an anonymous employee, or a diagram of an employee, but rather the conceptual model that defines the properties and behaviors of all employee instances in the domain being modeled.
B
Explanation:
In the context of a UML (Unified Modeling Language) model, the class named ‘Employee’ represents a template for all entities that are classified as employees within the business enterprise model.
Therefore, the correct answer is:
B. The set of all employees of the company
The term ‘Employee’ in the class diagram is a UML Class, which is defined as a description of a set of objects that share the same attributes, operations, relationships, and semantics (UML 2.5 specification, section 9.2). A class in UML is a blueprint from which individual objects (instances of the class) are created. It is not a representation of any single employee, an anonymous employee, or a diagram of an employee, but rather the conceptual model that defines the properties and behaviors of all employee instances in the domain being modeled.
Question #17
In UML modeling, what is a Constraint?
- A . a condition that must be satisfied when it is evaluated
- B . a condition that should be met depending on system operation
- C . a condition that causes the state of the objects to change over time
- D . a condition that constrains what can or cannot be put in a class diagram
Correct Answer: A
A
Explanation:
In UML modeling, a constraint is defined as:
A
Explanation:
In UML modeling, a constraint is defined as:
Question #18
Suppose you are using a programming language that knows the following basic types: byte, short, and long.
Which diagram defines them:
A)
B)
C)
D)
- A . Option A
- B . Option B
- C . Option C
- D . Option D
Correct Answer: A
A
Explanation:
In UML, basic types like byte, short, and long are represented as DataType elements. These are typically used to specify the types of attributes, parameters, or return values of operations in a model. Option A shows three separate classes named Byte, Short, and Long, which would represent these as distinct data types within the UML model.
Option B incorrectly uses stereotypes on objects, which is not the correct UML representation for data types.
Option C shows a class with attributes of different types, but it does not define these types as basic types.
Option D is incorrect because it uses stereotypes on DataType elements, which is not the standard way to represent basic types in UML.
According to the UML 2.5 specification, DataTypes are a kind of classifier that specifies a domain of values without identity (section 10.5.8). DataTypes are not classes; they do not have operations and cannot have instances that maintain an identity.
A
Explanation:
In UML, basic types like byte, short, and long are represented as DataType elements. These are typically used to specify the types of attributes, parameters, or return values of operations in a model. Option A shows three separate classes named Byte, Short, and Long, which would represent these as distinct data types within the UML model.
Option B incorrectly uses stereotypes on objects, which is not the correct UML representation for data types.
Option C shows a class with attributes of different types, but it does not define these types as basic types.
Option D is incorrect because it uses stereotypes on DataType elements, which is not the standard way to represent basic types in UML.
According to the UML 2.5 specification, DataTypes are a kind of classifier that specifies a domain of values without identity (section 10.5.8). DataTypes are not classes; they do not have operations and cannot have instances that maintain an identity.
Question #19
Consider the following model
Where is v visible?
- A . Only inside S
- B . Only inside T
- C . Only inside S and T
- D . Inside the whole P
Correct Answer: C
C
Explanation:
In UML, visibility of an attribute is determined by the scope of the classifier it belongs to and its visibility markers. The attribute ‘v’ is marked with a ‘-‘ sign, indicating it is private. Being private, it would normally be visible only within the class it is defined in, which is ‘S’ in this case. However, since ‘T’ is a subclass of ‘S’ (as indicated by the generalization relationship, a line with a closed, unfilled arrowhead), it inherits the attribute ‘v’. Therefore, ‘v’ is visible in both ‘S’ and ‘T’.
Option A is incorrect because it does not consider inheritance. Option B is incorrect for the same reason. Option D is incorrect because a private attribute in a class is not visible to the entire package, only to the class itself and its subclasses.
The UML 2.5 specification states that a private member is only accessible within the namespace it is defined (section 7.5.3). Since ‘T’ is within the namespace of ‘S’ due to inheritance, ‘v’ is visible in both.
C
Explanation:
In UML, visibility of an attribute is determined by the scope of the classifier it belongs to and its visibility markers. The attribute ‘v’ is marked with a ‘-‘ sign, indicating it is private. Being private, it would normally be visible only within the class it is defined in, which is ‘S’ in this case. However, since ‘T’ is a subclass of ‘S’ (as indicated by the generalization relationship, a line with a closed, unfilled arrowhead), it inherits the attribute ‘v’. Therefore, ‘v’ is visible in both ‘S’ and ‘T’.
Option A is incorrect because it does not consider inheritance. Option B is incorrect for the same reason. Option D is incorrect because a private attribute in a class is not visible to the entire package, only to the class itself and its subclasses.
The UML 2.5 specification states that a private member is only accessible within the namespace it is defined (section 7.5.3). Since ‘T’ is within the namespace of ‘S’ due to inheritance, ‘v’ is visible in both.
Question #20
What is the key difference between DataTypes and Classes?
- A . Classes can have operations that show that a class reacts to invocations sent by other classes DataTypes do not have this feature.
- B . DataTypes can only be very simple structures with attributes that are Datatypes as well, whereas Classes can be of arbitrary complexity.
- C . Two instances of a Datatype are considered to be equal when all their attributes have the same values, unlike instances of classes.
- D . Classes can inherit attributes, operations and other features of their super classes. DataTypes can only get instantiated.
Correct Answer: C
C
Explanation:
DataTypes in UML are a type of classifier that represents a set of values that do not have identity, which means that two instances of a DataType are indistinguishable if all their attributes are equal. This is in contrast to instances of Classes, which are distinguishable by their identity – each instance is considered unique even if their attributes have the same values.
Option A is incorrect because DataTypes can indeed have operations in UML.
Option B is also incorrect; DataTypes can have attributes of any complexity.
Option D is incorrect because DataTypes can also have features inherited from their super DataTypes; it is not solely about instantiation.
The UML 2.5 specification discusses DataTypes in section 10.5.8, stating that DataTypes do not have an identity and are often used to type attributes and operation parameters. The equality of DataType instances is based on the equality of their attribute values. Classes, however, are described in section 9.2 of the UML 2.5 specification as elements that can have identity, and instances of a Class are distinguished based on that identity.
C
Explanation:
DataTypes in UML are a type of classifier that represents a set of values that do not have identity, which means that two instances of a DataType are indistinguishable if all their attributes are equal. This is in contrast to instances of Classes, which are distinguishable by their identity – each instance is considered unique even if their attributes have the same values.
Option A is incorrect because DataTypes can indeed have operations in UML.
Option B is also incorrect; DataTypes can have attributes of any complexity.
Option D is incorrect because DataTypes can also have features inherited from their super DataTypes; it is not solely about instantiation.
The UML 2.5 specification discusses DataTypes in section 10.5.8, stating that DataTypes do not have an identity and are often used to type attributes and operation parameters. The equality of DataType instances is based on the equality of their attribute values. Classes, however, are described in section 9.2 of the UML 2.5 specification as elements that can have identity, and instances of a Class are distinguished based on that identity.
Question #21
What is the meaning of the relationship shown in the diagram below?
- A . class B is the creator of class A
- B . class A is dependent on class B
- C . class B is dependent on class A
- D . class A can be reached (torn class B
Correct Answer: B
B
Explanation:
In UML 2, the dashed arrow with an open arrowhead represents a dependency relationship. In the context of class diagrams, a dependency relationship indicates that changes to one class (the independent class) may cause changes in the other class (the dependent class). The direction of the arrow specifies which class is dependent on which. In the given diagram, the arrow points from class A to class B, which means that class A is dependent on class B. This could manifest as class A using some services or functions of class B, for example.
Reference: UML 2.5 Specification Document: The official document by the Object Management Group (OMG), which defines the syntax and semantics of UML.
UML Distilled: A Brief Guide to the Standard Object Modeling Language, Third Edition by Martin
Fowler: This book provides a clear guide to UML and includes examples of dependency relationships.
B
Explanation:
In UML 2, the dashed arrow with an open arrowhead represents a dependency relationship. In the context of class diagrams, a dependency relationship indicates that changes to one class (the independent class) may cause changes in the other class (the dependent class). The direction of the arrow specifies which class is dependent on which. In the given diagram, the arrow points from class A to class B, which means that class A is dependent on class B. This could manifest as class A using some services or functions of class B, for example.
Reference: UML 2.5 Specification Document: The official document by the Object Management Group (OMG), which defines the syntax and semantics of UML.
UML Distilled: A Brief Guide to the Standard Object Modeling Language, Third Edition by Martin
Fowler: This book provides a clear guide to UML and includes examples of dependency relationships.
Question #22
A structured class called System has two parts called Subsystem 1 and Subsystem2 respectively, as shown in the class diagram fragment below:
Which of the following diagrams contains an equivalent definition of System?
A)
B)
C)
D)
- A . Option
- B . Option
- C . Option
- D . Option
Correct Answer: C
C
Explanation:
In UML 2, a structured class can have internal parts, which are depicted using ‘parts’ or ‘roles’ within the class diagram. These internal parts are used to show the composition of the class in terms of contained classes or components. In the context of the question, the structured class named ‘System’ contains two parts named ‘Subsystem1’ and ‘Subsystem2’.
Option C is the equivalent definition of ‘System’ in terms of UML 2 notation for several reasons:
It represents the structured class ‘System’ with internal parts correctly labeled as ‘s1:Subsystem1’ and ‘s2:Subsystem2-[ ]’, which indicates the role names ‘s1’ and ‘s2’ followed by the class type ‘Subsystem1’ and ‘Subsystem2’ respectively. The notation ‘1..*’ after ‘s2:Subsystem2-[ ]’ suggests a multiplicity, meaning that there can be one or many instances of ‘Subsystem2’ associated with
‘System’.
The compartmentalization within the structured class is indicative of the composition of the ‘System’, showing that ‘Subsystem1’ and ‘Subsystem2’ are integral parts of the ‘System’.
The notation conforms to the standard UML 2 representation for composite structures, as described in the UML 2 Superstructure Specification, where a class can be broken down into its constituent parts within the class rectangle.
This information is verified against the UML 2 Superstructure Specification, which is the authoritative source for UML notation and semantics. Particularly, this aligns with section 9.3.5 on Composite Structures Diagrams, which details the graphical notation for parts and roles within a structured class.
C
Explanation:
In UML 2, a structured class can have internal parts, which are depicted using ‘parts’ or ‘roles’ within the class diagram. These internal parts are used to show the composition of the class in terms of contained classes or components. In the context of the question, the structured class named ‘System’ contains two parts named ‘Subsystem1’ and ‘Subsystem2’.
Option C is the equivalent definition of ‘System’ in terms of UML 2 notation for several reasons:
It represents the structured class ‘System’ with internal parts correctly labeled as ‘s1:Subsystem1’ and ‘s2:Subsystem2-[ ]’, which indicates the role names ‘s1’ and ‘s2’ followed by the class type ‘Subsystem1’ and ‘Subsystem2’ respectively. The notation ‘1..*’ after ‘s2:Subsystem2-[ ]’ suggests a multiplicity, meaning that there can be one or many instances of ‘Subsystem2’ associated with
‘System’.
The compartmentalization within the structured class is indicative of the composition of the ‘System’, showing that ‘Subsystem1’ and ‘Subsystem2’ are integral parts of the ‘System’.
The notation conforms to the standard UML 2 representation for composite structures, as described in the UML 2 Superstructure Specification, where a class can be broken down into its constituent parts within the class rectangle.
This information is verified against the UML 2 Superstructure Specification, which is the authoritative source for UML notation and semantics. Particularly, this aligns with section 9.3.5 on Composite Structures Diagrams, which details the graphical notation for parts and roles within a structured class.
Question #23
OpaqueExpression can use which languages?
- A . onlyOCL
- B . only programming languages
- C . only Mathematical Expressions
- D . any language
Correct Answer: D
D
Explanation:
An OpaqueExpression in UML 2 is used to specify behavior in a textual form when it is not necessary to specify which language is used, or when it is not possible to use graphical notation. According to the UML 2 specification, an OpaqueExpression is not limited to any particular language; it can represent expressions written in any language.
The key characteristics of an OpaqueExpression are as follows:
The ‘body’ of an OpaqueExpression is a sequence of strings, where each string could be written in a different language. This means it has the capacity to include multiple languages simultaneously.
The ‘language’ attribute is optional and is used to indicate the languages of the respective ‘body’ parts.
The allowance for any language is clearly stated in the UML 2 Infrastructure Specification. OpaqueExpression is designed to be a flexible way to capture expressions that are not readily expressible in UML or when using a language outside the scope of UML (e.g., mathematical expressions, programming languages, or other domain-specific languages).
D
Explanation:
An OpaqueExpression in UML 2 is used to specify behavior in a textual form when it is not necessary to specify which language is used, or when it is not possible to use graphical notation. According to the UML 2 specification, an OpaqueExpression is not limited to any particular language; it can represent expressions written in any language.
The key characteristics of an OpaqueExpression are as follows:
The ‘body’ of an OpaqueExpression is a sequence of strings, where each string could be written in a different language. This means it has the capacity to include multiple languages simultaneously.
The ‘language’ attribute is optional and is used to indicate the languages of the respective ‘body’ parts.
The allowance for any language is clearly stated in the UML 2 Infrastructure Specification. OpaqueExpression is designed to be a flexible way to capture expressions that are not readily expressible in UML or when using a language outside the scope of UML (e.g., mathematical expressions, programming languages, or other domain-specific languages).
Question #24
In UML modeling, what is the (unction of Comments?
- A . to provide additional semantics to the model elements
- B . to provide useful information to the reader of the model
- C . to enable automatic generation of comments in the code
- D . to add UML constraints to one or more model elements of the diagrams
Correct Answer: B
B
Explanation:
In UML, Comments are annotations that can be attached to most elements within UML diagrams. Their primary function is not to affect the semantics of the model directly but to provide useful information to anyone reading the model. Comments can help explain or clarify design decisions, make notes about specific parts of the model, or provide any other context necessary for understanding the model better.
The role of Comments in UML is not to enable automatic generation of code comments or to add constraints or semantics to model elements, although they can be associated with model elements to highlight or explain specific attributes or relationships.
Reference: UML 2.x Superstructure Specification: This document describes Comments as a way to provide human-readable descriptions and notes that do not impact the execution or structure of the model but are crucial for documentation and understanding.
UML 2.x Infrastructure Specification: Further delineates the role of comments in providing clarifications and additional information useful for model interpretation.
B
Explanation:
In UML, Comments are annotations that can be attached to most elements within UML diagrams. Their primary function is not to affect the semantics of the model directly but to provide useful information to anyone reading the model. Comments can help explain or clarify design decisions, make notes about specific parts of the model, or provide any other context necessary for understanding the model better.
The role of Comments in UML is not to enable automatic generation of code comments or to add constraints or semantics to model elements, although they can be associated with model elements to highlight or explain specific attributes or relationships.
Reference: UML 2.x Superstructure Specification: This document describes Comments as a way to provide human-readable descriptions and notes that do not impact the execution or structure of the model but are crucial for documentation and understanding.
UML 2.x Infrastructure Specification: Further delineates the role of comments in providing clarifications and additional information useful for model interpretation.
Question #25
Consider the following diagram:
Which statement is true about the diagram?
- A . Within G you may refer to v:K by gh.H::v. .
- B . From within H it is impossible to reach the v within G.
- C . The package Pckg cannot have two definitions of v as shown in the diagram.
- D . v will indicate different elements depending on where you refer to v within Pckg
Correct Answer: D
D
Explanation:
The diagram you provided shows two classes, G and H, which are within a package named Pckg. Each class has an attribute named ‘v’ with different visibility and type indicators. The attribute ‘v’ in class G has visibility ‘private’ (denoted by ‘-‘), and in class H, it is ‘protected’ (denoted by ‘#’). This suggests that the scope of each ‘v’ is limited to its respective class. Therefore, when you refer to ‘v’ within the package, its meaning depends on the context or the namespace from which it’s accessed.
Reference: UML 2.x Superstructure Specification: This defines the rules for scopes and namespaces in UML. It clarifies how elements with the same name can coexist in different namespaces and how their references would differ based on the context.
UML 2.x Infrastructure Specification: Provides the foundational concepts for UML, including the semantics of structured classifiers and namespaces which pertain to the interpretation of the ‘v’ attribute in different classes.
D
Explanation:
The diagram you provided shows two classes, G and H, which are within a package named Pckg. Each class has an attribute named ‘v’ with different visibility and type indicators. The attribute ‘v’ in class G has visibility ‘private’ (denoted by ‘-‘), and in class H, it is ‘protected’ (denoted by ‘#’). This suggests that the scope of each ‘v’ is limited to its respective class. Therefore, when you refer to ‘v’ within the package, its meaning depends on the context or the namespace from which it’s accessed.
Reference: UML 2.x Superstructure Specification: This defines the rules for scopes and namespaces in UML. It clarifies how elements with the same name can coexist in different namespaces and how their references would differ based on the context.
UML 2.x Infrastructure Specification: Provides the foundational concepts for UML, including the semantics of structured classifiers and namespaces which pertain to the interpretation of the ‘v’ attribute in different classes.
Question #26
Given the diagram fragment below:
What are the possible values for the attribute response in the class Query?
- A . Maybe
- B . Yes. No, Maybe
- C . There is insufficient information to determine the answer.
- D . The diagram is not legal UML
Correct Answer: B
B
Explanation:
The second diagram fragment you provided includes two enumeration types, YesNo and Answer, where YesNo is a generalization of Answer. The class Query has an attribute ‘response’ of type Answer. Given that YesNo is a generalization of Answer, the possible values for ‘response’ include the literals of Answer plus those inherited from YesNo. Since Answer includes ‘Maybe’, and YesNo includes ‘Yes’ and ‘No’, all three are valid values for ‘response’.
Reference: UML 2.x Superstructure Specification: Discusses attributes and their types, the concept of generalization, and how attributes of a generalized type can take on values from their own literals as well as those from their parent in the hierarchy.
UML 2.x Infrastructure Specification: Explains the foundational modeling constructs related to enumeration, classes, and attributes, which provides the basis for determining the legal values of an attribute based on its type’s enumeration literals.
B
Explanation:
The second diagram fragment you provided includes two enumeration types, YesNo and Answer, where YesNo is a generalization of Answer. The class Query has an attribute ‘response’ of type Answer. Given that YesNo is a generalization of Answer, the possible values for ‘response’ include the literals of Answer plus those inherited from YesNo. Since Answer includes ‘Maybe’, and YesNo includes ‘Yes’ and ‘No’, all three are valid values for ‘response’.
Reference: UML 2.x Superstructure Specification: Discusses attributes and their types, the concept of generalization, and how attributes of a generalized type can take on values from their own literals as well as those from their parent in the hierarchy.
UML 2.x Infrastructure Specification: Explains the foundational modeling constructs related to enumeration, classes, and attributes, which provides the basis for determining the legal values of an attribute based on its type’s enumeration literals.
Question #27
Consider the following diagram:
Is this diagram valid?
- A . No, because a DataType cannot have Associations to a Class.
- B . No, because a DataType cannot have Operations.
- C . No, because a DataType cannot have Attributes.
- D . Yes, it is formally correct.
Correct Answer: A
A
Explanation:
The provided diagram depicts a DataType named Route with operations, attributes, and associations to a Class named City. In UML, a DataType is a type of classifier that specifies the values that do not have identity (i.e., are not distinguishable from other objects). DataTypes may contain Attributes and Operations, so options B and C are incorrect.
However, DataTypes should not have associations to Classes because DataTypes are meant to be value types without identity, and associations typically imply a relationship between instances (which have identity). Thus, the presence of associations from Route to City is not consistent with the definition of a DataType.
Reference: UML 2.x Superstructure Specification: Sections on Classifiers and DataTypes provide definitions of what constitutes a DataType and what features they can have. They specifically mention that DataTypes are kinds of classifiers that do not have identity and are often used to type attributes.
UML 2.x Infrastructure Specification: This foundational document gives additional context on the semantics of different types of classifiers, including DataTypes, and how they relate to other elements in a UML model.
A
Explanation:
The provided diagram depicts a DataType named Route with operations, attributes, and associations to a Class named City. In UML, a DataType is a type of classifier that specifies the values that do not have identity (i.e., are not distinguishable from other objects). DataTypes may contain Attributes and Operations, so options B and C are incorrect.
However, DataTypes should not have associations to Classes because DataTypes are meant to be value types without identity, and associations typically imply a relationship between instances (which have identity). Thus, the presence of associations from Route to City is not consistent with the definition of a DataType.
Reference: UML 2.x Superstructure Specification: Sections on Classifiers and DataTypes provide definitions of what constitutes a DataType and what features they can have. They specifically mention that DataTypes are kinds of classifiers that do not have identity and are often used to type attributes.
UML 2.x Infrastructure Specification: This foundational document gives additional context on the semantics of different types of classifiers, including DataTypes, and how they relate to other elements in a UML model.
Question #28
Consider the following class diagram:
Which object diagram corresponds to it?
A)
B)
C)
D)
- A . Option A
- B . Option B
- C . Option C
- D . Option D
Correct Answer: D
D
Explanation:
The question asks to identify which object diagram corresponds to the provided class diagram. In order to verify which object diagram is correct, we must look at the class diagram to understand the relationships and multiplicities between the classes, and then match these with the objects and links in the object diagrams.
The class diagram (not visible in your query but implied to be the reference for the object diagrams provided) must contain three classes, A, B, and C, with specific multiplicity relationships among them. Here’s how we deduce the correct object diagram:
Multiplicity between A and C is "1..2", which means that for each instance of A there must be one or two links to instances of C.
Multiplicity between B and C is "0..2", which means that for each instance of B there are zero, one, or two links to instances of C.
Multiplicity between A and B is "0..1", which indicates that for each instance of A there can be zero or one link to an instance of B.
With these rules, we analyze the object diagrams:
Option A has one instance of A linked to two instances of C, which is correct according to the "1..2" multiplicity. However, there are two instances of B (b1 and b2) each linked to a single instance of C (c1), which violates the "0..2" multiplicity rule because it implies there should be two links from c1 to the B instances (b1 and b2) but instead, there are two separate links to the same instance of C (c1), which is not allowed.
Option B has similar issues where two instances of A (a2 and a1) are linked to a single instance of C, which violates the "1..2" multiplicity rule.
Option C shows each instance of A and B linked to their own separate instances of C. This violates the "1..2" multiplicity between A and C since there is only one link from A to C and does not show the possibility of two links which the multiplicity "1..2" would allow.
Option D shows a single instance of A linked to two instances of C (c1 and c2), which satisfies the "1..2" multiplicity. Additionally, there is a single instance of B linked to one of the instances of C (c1), satisfying the "0..2" multiplicity. The A instance has no direct link to the B instance, which is allowed because the "0..1" multiplicity permits zero links between instances of A and B.
Based on this analysis, the only object diagram that satisfies all the multiplicity constraints of the class diagram is Option D.
The verification of the answer can be cross-checked with the UML 2 Foundation documentation, specifically in the section dealing with object diagrams and their correlation with class diagrams, which will confirm that object diagrams represent instances of classes and must comply with the multiplicities defined in the class diagram they are derived from. Multiplicity notation and interpretation are fundamental concepts in UML and are well documented in the UML specification by the Object Management Group (OMG).
D
Explanation:
The question asks to identify which object diagram corresponds to the provided class diagram. In order to verify which object diagram is correct, we must look at the class diagram to understand the relationships and multiplicities between the classes, and then match these with the objects and links in the object diagrams.
The class diagram (not visible in your query but implied to be the reference for the object diagrams provided) must contain three classes, A, B, and C, with specific multiplicity relationships among them. Here’s how we deduce the correct object diagram:
Multiplicity between A and C is "1..2", which means that for each instance of A there must be one or two links to instances of C.
Multiplicity between B and C is "0..2", which means that for each instance of B there are zero, one, or two links to instances of C.
Multiplicity between A and B is "0..1", which indicates that for each instance of A there can be zero or one link to an instance of B.
With these rules, we analyze the object diagrams:
Option A has one instance of A linked to two instances of C, which is correct according to the "1..2" multiplicity. However, there are two instances of B (b1 and b2) each linked to a single instance of C (c1), which violates the "0..2" multiplicity rule because it implies there should be two links from c1 to the B instances (b1 and b2) but instead, there are two separate links to the same instance of C (c1), which is not allowed.
Option B has similar issues where two instances of A (a2 and a1) are linked to a single instance of C, which violates the "1..2" multiplicity rule.
Option C shows each instance of A and B linked to their own separate instances of C. This violates the "1..2" multiplicity between A and C since there is only one link from A to C and does not show the possibility of two links which the multiplicity "1..2" would allow.
Option D shows a single instance of A linked to two instances of C (c1 and c2), which satisfies the "1..2" multiplicity. Additionally, there is a single instance of B linked to one of the instances of C (c1), satisfying the "0..2" multiplicity. The A instance has no direct link to the B instance, which is allowed because the "0..1" multiplicity permits zero links between instances of A and B.
Based on this analysis, the only object diagram that satisfies all the multiplicity constraints of the class diagram is Option D.
The verification of the answer can be cross-checked with the UML 2 Foundation documentation, specifically in the section dealing with object diagrams and their correlation with class diagrams, which will confirm that object diagrams represent instances of classes and must comply with the multiplicities defined in the class diagram they are derived from. Multiplicity notation and interpretation are fundamental concepts in UML and are well documented in the UML specification by the Object Management Group (OMG).
Question #29
Consider the following diagram:
Which statement is always true about this diagram?
- A . There are infinitely many H objects inside Pckg.
- B . There are between 1 and 5 G objects inside Pckg
- C . For every H object, there are fewer than 5 G objects associated with it.
- D . There may be an G object which has no H object associated with it through gh.
Correct Answer: D
D
Explanation:
The diagram shows a package Pckg that includes two classes G and H with a one-to-many association
between them. The multiplicity ‘1..5’ near class G on the ‘gh’ association end suggests that for each H object, there should be between 1 to 5 associated G objects. However, the ‘*’ (multiplicity many) near class H on the ‘gh’ association end indicates that a G object can be associated with zero or more H objects. This implies that it’s possible to have a G object that is not associated with any H object.
Reference: UML 2.x Superstructure Specification: Multiplicity notations and association rules are clearly defined in the UML specifications, which detail the semantics of multiplicities and their implications for object association.
UML 2.x Infrastructure Specification: Further explains the basic constructs of the UML metamodel, which underpin the interpretation of multiplicities in associations.
D
Explanation:
The diagram shows a package Pckg that includes two classes G and H with a one-to-many association
between them. The multiplicity ‘1..5’ near class G on the ‘gh’ association end suggests that for each H object, there should be between 1 to 5 associated G objects. However, the ‘*’ (multiplicity many) near class H on the ‘gh’ association end indicates that a G object can be associated with zero or more H objects. This implies that it’s possible to have a G object that is not associated with any H object.
Reference: UML 2.x Superstructure Specification: Multiplicity notations and association rules are clearly defined in the UML specifications, which detail the semantics of multiplicities and their implications for object association.
UML 2.x Infrastructure Specification: Further explains the basic constructs of the UML metamodel, which underpin the interpretation of multiplicities in associations.
Question #30
In your model, you need to represent accounts.
Which statement supports using a Class, rather than a DataType. lor this purpose”
- A . The account is uniquely identified by its account number.
- B . The account number can change, but it would still be the same account.
- C . The account needs operations to transfer money into it or to withdraw money
- D . The account has attributes typed by Classes like account_holder; Person or bank_in_Charge Company
Correct Answer: C
C
Explanation:
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.
Reference: 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.
C
Explanation:
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.
Reference: 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.
Question #31
Which statement describes the semantics of a Property that has the aggregation kind composite?
- A . The aggregation kind composite is semantically equivalent to namespace containment
- B . Instances of the composed object’s type can exist only in the context of the composite object.
- C . When the Property’s composite object ceases to exist, all of its composed objects also cease to exist.
- D . The Property’s composed objects are part of a subset and the composite object is a union of the defined subsets.
Correct Answer: C
C
Explanation:
In UML, the aggregation kind ‘composite’ is one of the two types of aggregation, shared and composite. Composite aggregation, also known as composition, implies that the composed objects do not have a separate lifecycle from the owner object and are parts of the whole. This is in contrast to shared aggregation (aggregation), where the parts can be shared with different owners and have their own lifecycle.
Let’s look at the options:
C
Explanation:
In UML, the aggregation kind ‘composite’ is one of the two types of aggregation, shared and composite. Composite aggregation, also known as composition, implies that the composed objects do not have a separate lifecycle from the owner object and are parts of the whole. This is in contrast to shared aggregation (aggregation), where the parts can be shared with different owners and have their own lifecycle.
Let’s look at the options:
Question #32
Consider the following diagram:
According to the diagram, which statement describes the property db?
- A . The property db is a primary key
- B . The property db is a static property.
- C . The property db is inherited from a superclass.
- D . The property db is important and is emphasized by the modeler with an underline.
Correct Answer: B
B
Explanation:
In UML, a static property is one that belongs to the class itself rather than any instance of the class. In UML diagrams, static properties are denoted by underlining the property name.
Now, let’s review the options:
B
Explanation:
In UML, a static property is one that belongs to the class itself rather than any instance of the class. In UML diagrams, static properties are denoted by underlining the property name.
Now, let’s review the options:
Question #33
Which diagram shows inherited properties?
A)
B)
C)
D) Inherited properties cannot be shown In a specialized class.
- A . Option A
- B . Option B
- C . Option C
- D . Option D
Correct Answer: B
B
Explanation:
In UML, inherited properties are those attributes that are defined in a superclass and inherited by a subclass. According to UML notation, when a subclass inherits from a superclass, it inherits all the attributes and operations of the superclass unless they are redefined.
Let’s examine each option:
B
Explanation:
In UML, inherited properties are those attributes that are defined in a superclass and inherited by a subclass. According to UML notation, when a subclass inherits from a superclass, it inherits all the attributes and operations of the superclass unless they are redefined.
Let’s examine each option:
Question #34
Which elements in the diagram are Features of the Car class?
- A . drive(), Car
- B . stop(). driver
- C . name. stop()
- D . driveO, stop(). Person
Correct Answer: D
D
Explanation:
In UML, the features of a class are the combined set of attributes (properties) and operations (methods) that are defined for that class. A feature is a characteristic that classifiers (like classes) can possess. In the context of UML, operations are considered behavioral features, while attributes are considered structural features.
Let’s analyze the given options in the context of the Car class:
D
Explanation:
In UML, the features of a class are the combined set of attributes (properties) and operations (methods) that are defined for that class. A feature is a characteristic that classifiers (like classes) can possess. In the context of UML, operations are considered behavioral features, while attributes are considered structural features.
Let’s analyze the given options in the context of the Car class:
Question #35
Which statement is correct regarding Enumeration Literals?
- A . EnumerationLiterals are immutable
- B . EnumerationLiterals may be anonymous.
- C . EnumerationLiterals may not be compared for equality.
- D . Enumeration Literal names may appear more than once within an Enumeration.
Correct Answer: A
A
Explanation:
Enumeration literals in UML are used within an enumeration to define a set of named constants.
According to the UML specification:
A
Explanation:
Enumeration literals in UML are used within an enumeration to define a set of named constants.
According to the UML specification: