01. A change board reviews model changes by comparing the serialized files the configuration management system stores for each revision. Reviewers report that they cannot tell what actually changed.
What explains the difficulty?
a) The serialization is compressed by the configuration management system, so a textual comparison reports the whole file as changed whenever part of it is rewritten.
b) The serialization records how the model is written out, so a reordered file differs in many places where no element changed.
c) The serialization holds one revision at a time, so a comparison cannot report the sequence of changes.
d) The serialization omits stereotype applications, so any change made through a profile is invisible in the stored file and has to be described by its author.
02. A model applying an in-house profile is exported as XMI and imported into a second conforming tool. The blocks and their relationships arrive intact, but none of the in-house classifications the source model carried appear on the imported elements.
What is the most likely cause?
a) The receiving tool holds no definition of the applied profile, so the applications of that profile have nothing to bind to.
b) The two tools implement different XMI versions, so the model content transfers while the stereotype applications are written in a form the receiver skips.
c) The receiving tool imported the model before the profile was applied to the package, so the classifications will appear once the package has been imported again.
d) The exporting tool writes stereotype applications only for stereotypes drawn from a standard profile, so applications of an in-house profile are dropped as the file is written.
03. A power budget analysis performed on an approved endurance requirement produces a new statement bounding the standby draw of one subsystem. The statement came from the analysis rather than from the customer, and the team has to record how it stands to the endurance requirement.
Which record states that relationship correctly?
a) A satisfy relationship from the new statement to the endurance requirement, recording that holding the standby draw within the bound is what fulfills the endurance requirement and discharges it.
b) A deriveReqt relationship from the new statement to the endurance requirement, recording a requirement that follows from analysis of the source and carries an obligation of its own.
c) Containment of the new statement within the endurance requirement, recording it as one of the parts that the endurance requirement was decomposed into when the customer wrote and baselined it.
d) A refine relationship from the new statement to the endurance requirement, recording a clarification that states in more precise terms what the endurance requirement already obliges the system and its subsystems to do.
04. A program's requirements are held in a requirements management tool with a rich attribute schema, review states and baseline history. An integration mirrors them into the SysML model as requirement elements so satisfy and verify relationships can be drawn against the design.
What should the team expect the SysML side of the mirror to hold?
a) The requirement text and identifier, plus the traceability the design needs, and nothing the managing tool is responsible for.
b) The full attribute set and the review state, making the mirrored requirement element show exactly the record that the reviewers approved in the managing tool.
c) The baseline history, the only reference against which a trace to the approved design carries meaning.
d) The requirement text, its rationale and its priority, with the SysML requirement element taking its identifier from the design rather than the managing tool.
05. A systems team integrates its SysML tool with the mechanical group's design tools. The system model allocates mass and power budgets to physical components, and the mechanical designs hold geometry, materials and manufacturing detail.
Which exchange between the two is worth building?
a) The block decomposition into the mechanical tools, so each assembly is created from the system model's structure and cannot diverge from it.
b) The allocated budget values against the achieved values for each component, so an overrun in the mechanical design shows against the allocation constraining it.
c) The geometric definition of each component into the system model, so the physical design and the system description are held in one place.
d) The material and manufacturing properties into the system model, so the system description carries the same detail the mechanical group works from.
06. An organization is selecting a SysML modeling tool. The evaluation team has built a scored checklist covering several hundred capabilities and proposes to select whichever candidate reaches the highest total.
What would make the selection more defensible?
a) Weighting each criterion by how far the organization's own engineering work depends on it, so the total measures fit to that work rather than a count of capabilities.
b) Removing the criteria that all candidates satisfy, so the total is decided by the capabilities on which the candidates actually differ from each other.
c) Extending the checklist until every capability of every candidate appears on it, so no tool is credited for a capability that its competitors were never scored on.
d) Having two evaluators score the checklist independently and reconciling their differences, so the total is not shaped by the familiarity that one evaluator brings.
07. An organization maintains its own SysML profile and two model libraries, and every project applies them. It is now choosing a modeling tool.
Which criterion should carry the most weight?
a) A supplied library of predefined stereotypes for common engineering domains, reducing what the organization defines.
b) Report generation across the model, assembling the project reports and review packs from the stereotype properties the organization defines in its own profile.
c) Support for defining, applying and evolving a profile, including how models behave when a profile they apply is revised.
d) The range of diagram types, the layout controls and the rendering options, which carry project output to stakeholders well outside the modeling team.
08. An organization needs timing and resource properties on the elements of its embedded models. Rather than adopt MARTE, an architect proposes a small in-house profile carrying just the stereotypes the programs need.
What should weigh against the in-house profile?
a) A standard profile carries meanings that analysis tooling and partner organizations already share, which an in-house vocabulary has to earn.
b) A standard profile covers real-time and embedded concerns broadly, so the programs would not have to extend it later for a new concern.
c) A standard profile is maintained by the body that owns it, so the organization would not have to revise the in-house one as programs change.
d) A standard profile applies to a model without the packages needing to be re-applied, which an in-house profile would require of them.
09. Two engineers change the same block in one working session: one adds a value property, the other renames the block and changes an association end. The team's configuration management scheme uses the MOF versioning standard for model versioning and expects it to settle the outcome.
What should the team expect the standard to provide here?
a) A merge of the additive change with the rename raised for decision under a versioning scheme that separates element creation from element alteration.
b) A merge of the two changes, element-level versioning holding the value property addition and the rename as two separate changes applicable to the block in either order.
c) Version identity and change semantics for the individual element, which records the clash without settling it.
d) A rejection of the second change; element-level versioning admits one version of an element at a time, and the earlier change has claimed it.
10. Two organizations agree to exchange requirements using ReqIF v1.2. The supplier's requirements carry attributes for verification method, allocated subsystem and maturity, and the customer's carry a different set.
What remains for the two parties to settle?
a) Which of the two attribute sets becomes the standard, because the exchange transfers a single attribute definition set and drops whatever the other side defined.
b) Which tool each side uses to read the exchange, because the format is defined against a requirements management tool's own schema rather than a neutral one.
c) Whether requirements travel as text or as model elements, because the exchange carries requirement content rather than the design elements that satisfy them.
d) Which attributes each side sends and what each of them means, because the exchange carries the attribute definitions without agreeing them on the parties' behalf.