I85PREP
⌘ K
OCSMP Model Builder Advanced study materials
OCSMP Model Builder Advanced study resources

OCSMP Model Builder Advanced practice questions

One question at a time. Build your OCSMP Model Builder Advanced understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

In the SysML language architecture, which layer defines the abstract syntax of modeling constructs such as Block and Port, independent of any concrete notation?

  1. The user model layer (M1) that contains the actual system model
  2. The MOF meta-metamodel layer (M3) that defines Class and Association
  3. The UML metamodel layer (M2) reused and extended by SysML Correct answer.
  4. The concrete syntax layer that specifies diagram notation

Explanation

SysML is defined by extending the UML metamodel, so the abstract syntax of constructs like Block and Port lives at the metamodel layer (M2). The M1 layer holds the user's model instances of those metaclasses, and M3 is the meta-metamodel that defines the metamodeling language itself. Concrete syntax concerns notation, not abstract syntax.

Question 2Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A profile defines a stereotype «SafetyCritical» with a property maxFaultRate. How does a modeler apply this stereotype to a Block in a compliant SysML tool?

  1. Apply the stereotype to the block, creating an extension link that supplies the tagged value Correct answer.
  2. Subclass the Block metaclass to create a new metaclass carrying maxFaultRate
  3. Replace the Block metaclass with the stereotype in the metamodel
  4. Instantiate the stereotype as a separate block and connect it by a dependency

Explanation

A stereotype extends one or more metaclasses, and applying it to a model element creates an extension relationship whose slots hold the stereotype's properties as tagged values. Subclassing a metaclass changes the metamodel rather than annotating a model element. The stereotype is not a replacement metaclass nor a standalone block.

Question 3Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Which statement best describes a SysML model library as used in a profile-based customization effort?

  1. A profile that stereotypes every element in the user model automatically
  2. A diagram type that renders library elements as icons on a canvas
  3. A configuration-management baseline that freezes the model for release
  4. A read-only model of reusable definitions referenced by other models, typically not meant to be modified Correct answer.

Explanation

Model libraries package reusable definitions, such as type libraries or unit libraries, that other models import by reference. They are generally treated as read-only so that consumers depend on stable definitions. They are model content, not a diagram type, an automatic stereotyping mechanism, or a release baseline.

Question 4Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

In the SysML viewpoint mechanism, what is the relationship between a viewpoint and a view?

  1. A viewpoint is a package of diagrams while a view is a single diagram frame
  2. A view specifies the rules and a viewpoint is one rendered diagram instance
  3. A viewpoint specifies the concerns, stakeholders, and rules; a view conforms to a viewpoint and presents the model accordingly Correct answer.
  4. A viewpoint and a view are synonyms in SysML and may be used interchangeably

Explanation

A viewpoint defines the concerns of stakeholders and the modeling rules or conventions used to address them. A view is a model element that conforms to a viewpoint and represents the system from that perspective. The two are distinct concepts, not synonyms, and neither is merely a diagram frame.

Question 5Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Which mechanism is the standard way to extend SysML with new properties and semantics without changing the language metamodel?

  1. Defining a profile with stereotypes and applying them to model elements Correct answer.
  2. Renaming existing metaclasses to reflect domain terminology
  3. Adding new diagram types to the tool's palette
  4. Editing the SysML metamodel directly in the tool's repository

Explanation

Profiles are the lightweight extension mechanism: stereotypes add properties and constraints to existing metaclasses without altering the metamodel. Direct metamodel edits are heavyweight and non-portable, and neither palette changes nor renaming add semantics. Profiles keep extensions interoperable across compliant tools.

Question 6Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A team wants every requirement in their model to carry a verificationMethod property. Which profile construct should they define to add this property to the Requirement stereotype?

  1. A model library package containing a Requirement subclass
  2. An actor that owns the property and is associated with each requirement
  3. A new metaclass that inherits from Requirement in the metamodel
  4. A stereotype that specializes the SysML Requirement stereotype and adds the property Correct answer.

Explanation

Specializing the existing Requirement stereotype through a profile adds the property while preserving requirement semantics. The specialization inherits Requirement's metaclass extensions and contributes the new tagged value. Creating metaclasses or unrelated model elements does not attach the property to requirements.

Question 7Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

When a profile is applied to a package, what does application actually do to the model?

  1. It locks the package so that stereotypes cannot be removed later
  2. It copies the profile's metaclasses into the package as new model elements
  3. It makes the profile's stereotypes available for application to elements within that package's scope Correct answer.
  4. It automatically applies every stereotype in the profile to all contained elements

Explanation

Applying a profile scopes its stereotypes so they can be used on elements in that package and its contents. It does not automatically apply stereotypes, copy metaclasses, or lock the package. The modeler still chooses which stereotypes to apply to which elements.

Question 8Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A modeler needs a stereotype to be applicable to both Blocks and Actors. How is this expressed in the profile?

  1. Apply the stereotype only to Block and manually annotate Actors
  2. Define one extension to Block and rely on inheritance to reach Actor
  3. Define two extensions from the stereotype, one to each metaclass Correct answer.
  4. Create a shared superclass metaclass and extend only that

Explanation

A stereotype can extend multiple metaclasses, each extension making it applicable to that metaclass. Block and Actor do not share a useful generalization that would let one extension cover both. Manual annotation is not a profile mechanism, and inventing a superclass metaclass is unnecessary.

Question 9Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

What distinguishes a SysML profile from a metamodel in terms of conformance and portability?

  1. A profile is tool-specific while a metamodel is always portable across tools
  2. A profile replaces the metamodel while a metamodel only annotates elements
  3. A profile and a metamodel are identical in scope and differ only in file format
  4. A profile extends the standard metamodel and stays portable; a metamodel replaces the language definition Correct answer.

Explanation

Profiles are lightweight extensions layered on the standard metamodel, so models using them remain portable across compliant tools. A metamodel defines or replaces the language's abstract syntax and is a heavier, less portable commitment. They are not interchangeable, and portability favors profiles.

Question 10Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A viewpoint is defined with stakeholder concerns about fault tolerance and a rule requiring each safety block to carry a «SafetyCritical» stereotype. What does a conforming view guarantee?

  1. The view presents the model per the viewpoint's rules, so selected elements carry the required stereotype Correct answer.
  2. The view forbids displaying elements that lack the stereotype anywhere in the model
  3. The view converts the stereotype into a metaclass for the displayed blocks
  4. The view automatically adds the stereotype to any block it displays

Explanation

A view conforms to its viewpoint, meaning it is constructed according to the viewpoint's concerns and rules, so displayed safety blocks carry the required stereotype. The view does not mutate the model by auto-applying stereotypes, nor does it convert stereotypes into metaclasses.

Question 11Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Which SysML construct is used to define a reusable collection of model elements, such as units or quantity kinds, intended for import by other models?

  1. A stereotype extension
  2. A model library package Correct answer.
  3. A dependency from a block to an actor
  4. A viewpoint

Explanation

Model libraries are packages of reusable definitions, such as the standard units and quantity-kind libraries, meant to be imported rather than redefined. Viewpoints define stakeholder perspectives, stereotype extensions add properties, and dependencies relate elements. Only the library package serves as a reusable definitions collection.

Question 12Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A profile package imports the UML metamodel. Why must the profile reference metaclasses such as Class or Property?

  1. Because the profile package must duplicate the metamodel for portability
  2. Because stereotypes must inherit all properties of every metaclass they mention
  3. Because metaclasses provide the diagram notation for the stereotype
  4. Because stereotype extensions must target metaclasses to define where the stereotype can be applied Correct answer.

Explanation

An extension in a profile points from a stereotype to a metaclass, declaring the kind of element the stereotype may annotate. Referencing metaclasses is about applicability, not inheritance of all properties, duplication, or notation. Without the metaclass reference the extension is undefined.

Question 13Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Which statement correctly characterizes the relationship between SysML and UML at the language level?

  1. SysML is an entirely independent language that shares no metaclasses with UML
  2. SysML replaces UML entirely and deprecates all UML metaclasses
  3. SysML is a tool vendor's proprietary dialect with no standardized metamodel
  4. SysML reuses a subset of UML and adds extensions, defined as a UML profile plus metamodel changes Correct answer.

Explanation

SysML is built on UML by reusing a subset of its constructs and adding SysML-specific extensions, specified through a profile and metamodel adaptations. It is not independent, proprietary, or a wholesale replacement of UML. This reuse is why UML metaclasses appear in SysML profiles.

Question 14Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A modeler applies the same stereotype twice to one element with conflicting tagged values. What is the sound modeling practice?

  1. Apply the stereotype once and set the tagged values to the intended single set of values Correct answer.
  2. Apply it twice and let the tool merge the conflicting values arbitrarily
  3. Apply it twice because multiple applications always override earlier values
  4. Remove the stereotype and encode the data in the element's name

Explanation

A stereotype applied to an element should carry one consistent set of tagged values; conflicting duplicate applications create ambiguity. The modeler should apply it once and set the intended values. Relying on arbitrary merging or encoding data in names loses semantics and violates modeling discipline.

Question 15Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Which element in a profile declares that a stereotype may be applied to a specific kind of model element?

  1. An association between two stereotypes
  2. A generalization from the stereotype to the metaclass
  3. An extension between the stereotype and the metaclass Correct answer.
  4. A dependency from the profile package to the metaclass

Explanation

The extension relationship links a stereotype to a metaclass and defines the applicability of the stereotype. Generalization would imply inheritance, not applicability, and stereotype-to-stereotype associations or package dependencies do not declare target element kinds. Extension is the defining construct.

Question 16Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A team wants to constrain a stereotype so that maxFaultRate must be a positive real number. Where should this constraint be expressed?

  1. As a note on each diagram that displays the stereotyped element
  2. As an actor requirement associated with the block
  3. As a comment in the model library that defines the units
  4. As a constraint owned by the stereotype in the profile, evaluated when the stereotype is applied Correct answer.

Explanation

Constraints that govern a stereotype's tagged values belong with the stereotype in the profile so they apply wherever the stereotype is used. Diagram notes, library comments, and associated actors do not enforce the rule. Placing the constraint in the profile keeps the extension consistent and reusable.

Question 17Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Which statement about importing a model library into a user model is most accurate?

  1. Importing prevents the user model from defining its own types
  2. Importing deletes the library after the definitions are transferred
  3. Importing by reference lets the user model reuse definitions while the library remains a separate, maintainable package Correct answer.
  4. Importing copies all library elements into the user package permanently

Explanation

Library import by reference lets consumers reuse definitions while the library stays a distinct package that can be maintained and versioned independently. Import does not copy-and-delete content or block local type definitions. This separation is central to library reuse.

Question 18Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A viewpoint is intended to address the concerns of a specific stakeholder group. Which element should the viewpoint reference to make this explicit?

  1. The tagged values it defines
  2. The diagrams it renders
  3. The metaclasses it extends
  4. The stakeholder it addresses Correct answer.

Explanation

A viewpoint names the stakeholders whose concerns it addresses, making the perspective explicit and traceable. Stereotypes extend metaclasses, tagged values belong to stereotypes, and diagrams are renderings. Stakeholder reference is the correct association for a viewpoint.

Question 19Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A profile defines a stereotype «Mode» with a property modeName. A modeler needs two distinct modes on one block. What is the recommended approach?

  1. Define two separate stereotypes or use two distinct elements, since duplicate application to one element is ambiguous Correct answer.
  2. Apply «Mode» twice to the same block and accept the ambiguity
  3. Apply «Mode» to the block's ports instead of the block
  4. Encode both mode names into a single tagged value string

Explanation

Because applying the same stereotype twice to one element creates ambiguous tagged values, distinct modes should be modeled with separate stereotypes or separate elements. Encoding names in one string loses structure, and moving the stereotype to ports changes the intended subject. Clear separation preserves semantics.

Question 20Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Which characteristic makes profiles preferable to direct metamodel modification for most domain-specific extensions?

  1. Profiles eliminate the need for model libraries entirely
  2. Profiles are layered on the standard metamodel, preserving tool interoperability and standard conformance Correct answer.
  3. Profiles remove the need for any metaclass references in extensions
  4. Profiles permanently alter the metamodel so all tools must adopt the change

Explanation

Profiles extend the standard metamodel without replacing it, so models remain interoperable and conformant across compliant tools. Direct metamodel modification forces non-standard tooling. Profiles still require metaclass references for extensions and do not replace libraries. Interoperability is the decisive advantage.

Question 21Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A view is defined to conform to a fault-tolerance viewpoint. If a safety block lacks the required «SafetyCritical» stereotype, what is the correct interpretation?

  1. The viewpoint is invalid and must be redefined to match the model
  2. The view silently adds the missing stereotype to satisfy conformance
  3. The model violates the viewpoint's rule and the view should surface the nonconformance Correct answer.
  4. The block is automatically excluded from the model entirely

Explanation

Conformance means the view is built per the viewpoint's rules; a block missing the required stereotype is a nonconformance the view should reveal. The view does not silently mutate the model, invalidate the viewpoint, or delete elements. Surfacing nonconformance is the purpose of viewpoint rules.

Question 22Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Which pairing correctly matches a SysML extension mechanism with what it contributes?

  1. Viewpoint replaces the metamodel with stakeholder concerns
  2. Model library adds new metaclasses to the language
  3. Extension relationship adds a new diagram type to the tool
  4. Stereotype adds properties and constraints; profile packages and applies stereotypes Correct answer.

Explanation

Stereotypes contribute properties and constraints, and profiles package them for application to model elements. Libraries hold reusable definitions rather than new metaclasses, viewpoints express perspectives rather than replacing the metamodel, and extensions declare applicability rather than adding diagram types.

Question 23Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A modeler wants to reuse the standard quantity-kind and unit definitions in a model. What is the appropriate action?

  1. Import the relevant model library packages and reference their definitions Correct answer.
  2. Apply a stereotype that generates units automatically
  3. Create a viewpoint that computes units for each value property
  4. Redefine quantity kinds locally in each package to avoid dependencies

Explanation

Standard quantity-kind and unit definitions live in model libraries and should be imported and referenced to ensure consistency. Redefining them locally invites inconsistency, and neither stereotypes nor viewpoints generate units automatically. Import-by-reference is the intended reuse path.

Question 24Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Which statement about the scope of a profile application is correct?

  1. Applying a profile to one element makes its stereotypes available model-wide
  2. Applying a profile to a package makes its stereotypes available within that package's scope Correct answer.
  3. A profile must be applied to every element individually before use
  4. A profile application has no scope and always affects the whole repository

Explanation

Profile application is scoped to the package to which it is applied, making the stereotypes available for elements within that scope. It is not applied per element, and it does not automatically extend to the entire repository. Scoping supports controlled, modular use of extensions.

Question 25Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

How does a stereotype specialization inherit applicability from its parent stereotype in a profile?

  1. The specialization loses all extensions and must redefine them from scratch
  2. The specialization applies only to the profile package itself
  3. The specialization converts the parent's extensions into generalizations
  4. The specialization retains the parent's extensions, so it is applicable wherever the parent is applicable Correct answer.

Explanation

A stereotype that specializes another inherits the parent's extension relationships, so it remains applicable to the same metaclasses while adding its own properties. Extensions are not lost or converted, and the specialization is not confined to the profile package. Inheritance of extensions is the key behavior.

Question 26Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

In a SysML profile, which element owns the definitions that a stereotype extends and that a tool uses to decide where the stereotype may be applied?

  1. The metamodel referenced through the profile's package import of UML or SysML metaclasses Correct answer.
  2. The model library package that stores unit and quantity-kind definitions
  3. The user model package that applies the profile
  4. The viewpoint that specifies stakeholder concerns

Explanation

A profile is defined relative to a reference metamodel, and stereotypes extend metaclasses from that metamodel. The extension relationship to a metaclass is what establishes where the stereotype may be applied. User model packages and libraries consume the profile rather than define its applicability.

Question 27Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A profile author writes a stereotype «Sensor» and gives it a property named sampleRate typed by a ValueType. What does this property become on an element to which «Sensor» is applied?

  1. A constraint that the tool evaluates automatically
  2. A tagged value whose value is held per application of the stereotype Correct answer.
  3. A new metaclass that other stereotypes may extend
  4. A view that conforms to the profile

Explanation

Stereotype properties are surfaced as tagged values on each element the stereotype is applied to. Each application carries its own value, so two sensors can have different sample rates. They do not create metaclasses, constraints, or views.

Question 28Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Which statement best describes how a SysML profile is packaged and reused across projects?

  1. As a separate model file that replaces the UML metamodel for the project
  2. As a package of stereotype and related definitions that is applied to user model packages Correct answer.
  3. As a library of instance specifications copied into each block
  4. As a set of views generated from an existing user model

Explanation

A profile is a package whose contents are stereotype definitions and supporting elements, and it is reused by applying it to packages in a user model. It extends the language rather than replacing the metamodel. Views and instance data are separate concerns.

Question 29Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A model library defines a ValueType for temperature with a base unit. A user model imports the library package. What is the effect of the import?

  1. The user model can reference the library's definitions by name, but the definitions remain owned by the library Correct answer.
  2. The user model takes ownership of copies of every library element
  3. The library package is deleted from the model once imported
  4. The library's stereotypes become applicable to the user model's blocks

Explanation

A package import makes the imported package's members visible by name to the importing package while ownership stays with the library. This supports reuse without duplication. It does not transfer ownership, apply stereotypes, or remove the library.

Question 30Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Which element in a profile carries the textual statement of a modeling rule that a stereotype's instances must satisfy?

  1. A generalization between two stereotypes
  2. A constraint owned by the stereotype, optionally expressed in a formal language Correct answer.
  3. A comment attached to the profile package
  4. A dependency from the stereotype to the metamodel

Explanation

Constraints attached to a stereotype state rules that apply wherever the stereotype is used, and they may be written formally so a tool can evaluate them. Comments and dependencies carry no enforceable rule. Generalization expresses inheritance between stereotypes, not a validity rule.

Question 31Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Which pairing of a SysML adaptation mechanism with its purpose is correct?

  1. Stereotype - replaces the reference metamodel for a project
  2. Viewpoint - extends the metamodel with new metaclasses
  3. Model library - defines stakeholder concerns for a view
  4. Profile - extends the language with stereotypes for a domain Correct answer.

Explanation

Profiles extend the modeling language with domain-specific stereotypes and their properties. Viewpoints frame views for stakeholders, libraries hold reusable model content, and stereotypes extend rather than replace the metamodel.

Question 32Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A view is created to conform to a viewpoint that requires every safety block to be shown with its failure rate. Which element should the view reference to declare that conformance?

  1. The package that owns the safety blocks
  2. The model library that defines the failure-rate unit
  3. The profile that defines the «SafetyCritical» stereotype
  4. The viewpoint that specifies the concerns and rules the view must satisfy Correct answer.

Explanation

A view conforms to a viewpoint, and that conformance is declared by referencing the viewpoint. The viewpoint carries the stakeholder concerns and the rules the view must meet. Profiles, libraries, and owning packages do not express view conformance.

Question 33Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Which statement correctly describes the relationship between a stereotype and the metaclass it extends?

  1. The extension makes the stereotype a kind of model library
  2. The extension copies the metaclass features into the stereotype
  3. The extension makes the stereotype applicable to instances of that metaclass Correct answer.
  4. The extension makes the metaclass a subtype of the stereotype

Explanation

An extension associates a stereotype with a metaclass so the stereotype may be applied to elements of that kind. The stereotype adds domain properties to those elements. It does not reverse the subtype relationship, copy features, or create a library.

Question 34Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A team defines «Actuator» in a profile and applies the profile to package P. A block in a different package Q, outside P, should also carry «Actuator». What must the team do?

  1. Nothing; applying the profile once makes the stereotype available model-wide
  2. Apply the profile to Q as well, or to a package that contains Q Correct answer.
  3. Move the stereotype definition into Q and delete it from the profile
  4. Convert «Actuator» into a model library element

Explanation

Stereotype availability follows profile application, so a package whose contents should use the stereotype must have the profile applied, directly or through an enclosing package. A single application does not make stereotypes available across the whole model. Moving or reclassifying the definition does not solve availability.

Question 35Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A profile author wants «Redundant» to be applicable only to blocks that are already «SafetyCritical». Which profile construct expresses this restriction?

  1. A constraint on «Redundant» requiring the base element to also carry «SafetyCritical» Correct answer.
  2. A package import of the safety package into the profile
  3. A generalization from «SafetyCritical» to «Redundant»
  4. A dependency from «Redundant» to the «SafetyCritical» metaclass

Explanation

Conditional applicability is a rule about the base element, so it is expressed as a constraint on the stereotype. Generalization would make «Redundant» a specialization of «SafetyCritical» and thereby change inheritance rather than state a condition. Imports and dependencies do not impose the condition.

Question 36Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Two stereotypes in the same profile both define a property named mass with different types. A modeler applies both to one block. What is the sound resolution?

  1. Rename or reconcile the properties in the profile so the combined application has one consistent definition Correct answer.
  2. Move one stereotype into a model library
  3. Apply the stereotypes anyway and let the tool pick one type arbitrarily
  4. Delete one stereotype from the profile after application

Explanation

When stereotypes are combined on one element, their properties must not conflict, so the profile should be designed so names and types are consistent. Relying on arbitrary tool choice makes the model ambiguous. Deleting definitions or moving them to a library breaks the intended extension.

Question 37Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A profile defines «Fault» with a property severity typed by an enumeration. A modeler needs several distinct faults recorded against one block. Which approach fits SysML best?

  1. Define a «Fault»-typed part or reference property on the block so each fault is a separate instance Correct answer.
  2. Apply «Fault» repeatedly to the block, each time with a different severity
  3. Add a separate comment to the block for each fault
  4. Create a subclass of the block for each fault

Explanation

When multiple occurrences of a stereotyped concept are needed, the stereotype is applied to a classifier and the block holds multiple instances through part or reference properties. Reapplying one stereotype to the same element with conflicting values is not sound. Subclassing and comments do not record distinct fault instances.

Question 38Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A modeling team needs a stereotype property whose value must be one of a fixed set of modes. Which profile design is most appropriate?

  1. Type the property with a block and let modelers enter free text
  2. Type the property with a ValueType and add a comment listing the modes
  3. Type the property with an enumeration whose literals are the allowed modes Correct answer.
  4. Leave the property untyped and record modes in the stereotype name

Explanation

An enumeration restricts a property to a fixed set of literals, which is exactly the need. A ValueType with a comment does not enforce the set, an untyped property allows any value, and encoding modes in a name prevents multiple or structured values.

Question 39Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A library of quantity kinds and units is imported into a model that also applies a units profile. Which statement about the two mechanisms is correct?

  1. Both mechanisms only provide documentation for the model
  2. Both mechanisms extend the metamodel with new metaclasses
  3. The library extends the metamodel, and the profile supplies instance data
  4. The library supplies reusable definitions, while the profile supplies stereotypes that extend the language Correct answer.

Explanation

Model libraries contribute reusable model content such as units and quantity kinds, whereas profiles contribute language extensions through stereotypes. Libraries do not add metaclasses, and neither mechanism is merely documentation.

Question 40Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A viewpoint specifies that views must show each requirement with its verification method. A view is built that omits the verification method for several requirements. What does this situation indicate?

  1. The view does not conform to the viewpoint and should be corrected or the viewpoint revisited Correct answer.
  2. The viewpoint is automatically invalid because a view disagreed with it
  3. The profile that defines requirements must be reapplied
  4. The requirements are invalid because they lack a verification method

Explanation

A view is expected to satisfy the rules stated by its viewpoint, so an omission is a conformance gap in the view. The remedy is to correct the view or, if the rule is wrong, to revise the viewpoint. Neither the viewpoint nor the requirements become invalid merely because a view is incomplete.

Question 41Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A profile author wants every «Requirement»-stereotyped element to have a nonempty identifier. Where should this rule be placed so it applies wherever the stereotype is used?

  1. As a comment on each element that receives the stereotype
  2. As a property of the profile package itself
  3. As a constraint on the user model package that applies the profile
  4. As a constraint owned by the «Requirement» stereotype in the profile Correct answer.

Explanation

A constraint owned by the stereotype travels with the stereotype and applies to every element it is applied to. Per-element comments are not enforced, and a constraint on the applying package or on the profile package does not target stereotype instances.

Question 42Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A profile is intended for reuse by several programs. Which design choice best supports that goal?

  1. Include project-specific instance data in the profile package
  2. Define the profile inside each user model package separately
  3. Embed copies of all unit and quantity-kind definitions inside the profile
  4. Keep the profile focused on domain concepts and reference standard libraries rather than duplicating them Correct answer.

Explanation

Reusable profiles stay focused on domain extensions and rely on standard libraries for shared definitions. Duplicating library content or embedding instance data makes the profile heavy and hard to maintain, and defining it separately per package defeats reuse.

Question 43Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A stereotype «Mode» is defined as a specialization of «OperatingState» in the same profile. What does the specialization imply about where «Mode» may be applied?

  1. «Mode» cannot be applied anywhere until it is redefined in a user model
  2. «Mode» may be applied only to metaclasses that «OperatingState» does not extend
  3. «Mode» automatically becomes a metaclass in the reference metamodel
  4. «Mode» inherits the applicability of «OperatingState» and may add its own extension to the same or other metaclasses Correct answer.

Explanation

A stereotype specialization inherits the extension of its parent, so it is applicable wherever the parent is applicable, and it may declare additional extensions. It does not lose applicability, require redefinition, or become a metaclass.

Question 44Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A team wants to enforce that a «SafetyCritical» block must reference at least one «Hazard» element. Which profile element should carry this rule?

  1. A dependency from the profile package to the hazard package
  2. A constraint owned by the «SafetyCritical» stereotype that checks for a linked «Hazard» Correct answer.
  3. A comment on the «Hazard» stereotype
  4. A generalization from «Hazard» to «SafetyCritical»

Explanation

The rule constrains instances of «SafetyCritical», so it belongs as a constraint on that stereotype. A package dependency, a generalization, or a comment cannot express the required link.

Question 45Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A modeler applies a profile to package P and then moves a block from P into package Q, which does not apply the profile. What happens to the block's stereotype application?

  1. The profile is automatically applied to Q by the modeling tool
  2. The application is no longer supported by Q's scope and should be resolved by applying the profile to Q or moving the block back Correct answer.
  3. The stereotype is silently converted into a model library element
  4. The stereotype application becomes a metaclass in Q

Explanation

Stereotype availability depends on the profile being applied in the scope of the element, so moving an element out of that scope creates an inconsistency that must be resolved. The stereotype does not become a library element or a metaclass, and tools do not generally apply profiles automatically.

Question 46Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A profile author wants to constrain a stereotype so that its property must be a positive real number. Where should the constraint be defined?

  1. On the metaclass in the reference metamodel
  2. On the model library that supplies the real number type
  3. On the user model package that applies the profile
  4. On the stereotype, expressed in a formal constraint language over the property Correct answer.

Explanation

A rule about a stereotype's property value is a constraint on the stereotype, written formally so a tool can evaluate it. Constraints placed on the applying package, the metaclass, or a library do not target the stereotype property.

Question 47Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A team defines a profile with a stereotype «Requirement» and separately imports a model library of verification methods. Which statement best explains why both are needed?

  1. The stereotype adds requirement-specific properties and rules, while the library provides reusable verification-method definitions to reference Correct answer.
  2. Both are required because a profile cannot be applied without a library import
  3. Both are interchangeable ways to add properties to a requirement
  4. The stereotype provides verification methods, while the library extends the metamodel

Explanation

Profiles extend the language with domain properties and rules, while libraries supply reusable model content such as verification-method definitions. They serve different purposes and neither substitutes for the other. A profile does not depend on a library import to be applied.

Question 48Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A viewpoint requires that every view show a traceability path from requirement to test case. A team proposes satisfying this by adding a comment to each view listing the paths. Why is this insufficient?

  1. The viewpoint rule concerns model content shown by the view, and a comment does not establish the required traceability Correct answer.
  2. Comments are prohibited inside views by the SysML specification
  3. A viewpoint can only be satisfied by applying a profile
  4. Traceability paths cannot be modeled in SysML

Explanation

Viewpoint rules address what the view presents from the model, so the traceability must exist as model relationships that the view exposes. A comment does not create those relationships. Comments are not prohibited, profiles are not the only route, and traceability is a standard SysML capability.

Question 49Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

Two profiles each define a stereotype named «Mode» with different properties, and both are applied to the same package. What is the most defensible modeling decision?

  1. Apply both stereotypes to the same elements and rely on position to distinguish them
  2. Resolve the name clash by qualifying or renaming one stereotype so applications are unambiguous Correct answer.
  3. Discard one profile entirely and lose its other definitions
  4. Merge both stereotypes into a model library

Explanation

When two applied profiles introduce the same stereotype name, applications become ambiguous, so the names should be qualified or one renamed. Relying on position is not sound, discarding a profile loses unrelated definitions, and a library cannot carry stereotype extensions.

Question 50Concepts for adapting SysML (e.g., metamodeling, profiles, model libraries and viewpoints)

A profile author wants a stereotype to be applicable to both a block and an actor through a single declaration. Which approach is consistent with profile semantics?

  1. Declare two extensions from the stereotype, one to each metaclass Correct answer.
  2. Declare a dependency from the stereotype to each metaclass
  3. Declare the stereotype as a subclass of both metaclasses
  4. Declare one extension to a common superclass and rely on inheritance of the stereotype

Explanation

Applicability is declared by extension relationships, so a stereotype applicable to two kinds of element declares an extension to each metaclass. Subclassing metaclasses or using dependencies does not establish applicability, and relying on an unrelated superclass is not equivalent to declaring both.