Agentic Systems > Agentic MBSE > Flashcards

Agentic MBSE Flashcards

(168 cards)

Study These Flashcards
1
Q
A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is an Activity Diagram in SysML/UML?

A

A behavior diagram for flows of control/data among actions

Agents can generate or validate action sequences against requirements (e.g., boot → init → safe mode).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Define Agentic System / Agent.

A

An automated software actor that senses, plans, and acts via APIs, often orchestrated by an MCP server

Drives hands-off updates (e.g., sync DNG requirements, edit Cameo models, run simulations, open reviews).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What does Alf stand for?

A

Action Language for fUML

OMG textual language that compiles to fUML for precise executable behaviors.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the purpose of Allocation in SysML?

A

Mapping of responsibilities (e.g., functions to components, requirements to elements)

Core to automated trace—agents keep allocations consistent as designs evolve.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is Ansys ModelCenter used for?

A

Workflow orchestrator linking models/analyses to MBSE

Agents can call analyses on model change, capture KPIs, and update verification status.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What does APS stand for?

A

Autodesk Platform Services

Cloud APIs (data, translate, view) for Autodesk ecosystems.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Define Baseline in DNG/GCM.

A

Immutable snapshot of a configuration at a point in time

Agents can compare baselines, reconstruct context (“as of CDR-2”), and produce audit packs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is a BDD in SysML?

A

Block Definition Diagram

SysML diagram defining structural elements and relationships.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What does Branch / Stream refer to in DNG, TWC?

A

Parallel lines of change enabling concurrent development

Agents can spawn experiment branches, later propose merges with summarized diffs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is CAD–MBSE Allocation?

A

Linking SysML elements to CAD parts/assemblies

Enables requirements to flow into geometry and vice versa (mass, envelope, interfaces).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is Cameo / MagicDraw?

A

SysML/UML/UAF modeling environment with simulation and TWC repo

Primary agent workbench for model CRUD, execution, and views.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is the function of Cameo Collaborator for Web?

A

Web publishing/viewing of model content

Agents publish evidence/ICDs and share approval views.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What does Cameo DataHub do?

A

Sync/trace bridge (incl. OSLC/ReqIF) between Cameo and RM tools like DNG

Low-friction DOORS↔Cameo alignment without custom glue.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is the Cameo Simulation Toolkit (CST) used for?

A

Executes state machines, activities, parametrics

Agents run trade studies and verification scenarios programmatically.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is a Change Set in DNG?

A

Scoped set of edits that can be reviewed/merged

Units of work agents open/close to keep governance clean.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Define Component in DNG.

A

Logical subdivision inside a DNG project for scoping artifacts/configuration

Agents target operations to relevant scopes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

What is Configuration Management in DNG/TWC?

A

Versioning with streams, change sets, baselines and compare/merge

Safe agent edits and reproducible states.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What does Coverage refer to in Traceability Coverage?

A

Degree to which requirements have linked design/tests/results

Agent dashboards track gaps; gates block release if coverage < target.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What is a Data Dictionary / Attribute Schema in DNG?

A

Artifact types, attributes, picklists, and rules

Agents enforce schema hygiene, normalize values, and prevent drift.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What is DOORS Next (DNG)?

A

Web-based RM in IBM ELM with configs, reviews, OSLC, JRS

Governance backbone; event source (TRS) to wake agents.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What does EARS stand for?

A

Easy Approach to Requirements Syntax

Template style for clear requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

What is ECAD?

A

Electronic design automation (schematic, PCB)

Agents propagate RM/MBSE changes into ECAD constraints and BOM.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

What is Executable Model?

A

A model whose behavior can be simulated/executed (fUML, parametrics)

Enables automated verification in the loop.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
What is a **Feature** in MBPLE?
A selectable capability in a product line ## Footnote Agents toggle features to derive variant-specific views, ICDs, and BOMs.
26
What does **fUML** stand for?
Foundational UML ## Footnote Executable subset semantics of UML.
27
What is **GCM**?
Global Configuration Management ## Footnote Composes versioned streams/baselines across tools.
28
What is **Generative Design** in CAD?
Algorithmic exploration of structures under constraints ## Footnote Agents can pipe requirements into CAD solvers and feed results back to MBSE.
29
What does **Governance** refer to in RM?
Reviews, approvals, policies, and auditability ## Footnote Agents automate review creation, evidence packaging, and status updates.
30
What is a **Hazard / FMEA Linkage**?
Trace from hazards to mitigations to verification ## Footnote Agents ensure risk controls stay linked and tested after changes.
31
What is an **IBD** in SysML?
Internal Block Diagram ## Footnote SysML structure diagram for parts/ports/flows.
32
What does **ICD** stand for?
Interface Control Document ## Footnote Formal interface spec between systems.
33
What is **INCOSE**?
Systems engineering professional body ## Footnote Aligns methods/terms; helps structure agent rules of engagement.
34
What is **Jazz Reporting Service (JRS)**?
Reporting suite over ELM/OSLC graphs ## Footnote Agents assemble compliance dashboards and export audit PDFs.
35
What is a **KiCad Python API**?
Scripting for pcbnew and related tools ## Footnote Opens an agent path for open-source PCB changes/DFM checks.
36
What are **KPIs**?
Key Performance Indicators ## Footnote Quantified targets (e.g., power margin ≥ 10%).
37
What is **LQE**?
Lifecycle Query Engine ## Footnote Indexer/query over OSLC resources; supports relational store.
38
What does **MBPLE** stand for?
Model-Based Product Line Engineering ## Footnote Managing variability in models.
39
What is **Merge** in TWC / DNG?
Integrating changes with conflict resolution and visual diffs ## Footnote Agents can propose merges and summarize impacts for reviewers.
40
What is a **Module** in DNG?
Structured document-like container for requirements ## Footnote Agent target for authoring, views, and reviews.
41
What does **Nexar** refer to?
Octopart GraphQL ## Footnote Component data (price/stock/specs).
42
What is **OSLC**?
Open Services for Lifecycle Collaboration ## Footnote Linked-data standard for lifecycle artifacts.
43
What is **Parametric Diagram** in SysML?
Constraint networks binding properties to equations ## Footnote Agents run sweeps/optimizations and check requirement satisfaction automatically.
44
What does **PCB DFM** stand for?
Manufacturability checks (clearances, widths, annular rings) ## Footnote Agents can gate merges/releases on DFM pass.
45
What is **Query-by-View** in DNG?
Saved filters and views over requirement sets ## Footnote Agents run named views for task queues (e.g., “Needs Test”).
46
What is **Reportable REST** in DNG?
Deterministic API for bulk read/export of RM data ## Footnote Agents pull snapshots for analysis and audit bundles.
47
What does **ReqIF** stand for?
Requirements Interchange Format ## Footnote Neutral XML format for requirements exchange.
48
What is **Requirement Satisfaction** in SysML?
Link asserting a model element satisfies a requirement ## Footnote Agents update satisfaction status from simulation or tests.
49
What is a **Review** in DNG?
Formal approval workflow with roles and dispositions ## Footnote Agents build review packages and nudge approvers.
50
What is a **Sequence Diagram** in SysML/UML?
Time-ordered interaction among lifelines ## Footnote Agents validate message timing and constraints versus requirements.
51
What is a **State Machine** in SysML/UML?
Mode/transition logic for a system ## Footnote Executable logic that agents verify early (faults, timeouts).
52
What are **Streams** in DNG, TWC?
Versioned lines of development ## Footnote Agents select correct stream to avoid cross-variant contamination.
53
What is a **Suspect Link** in DNG?
Flag indicating linked items may be invalid after a change ## Footnote Agents raise/clear suspects, route work to owners, and report lag.
54
What does **SysML** stand for?
OMG systems modeling language (structure/behavior/requirements/parametrics) ## Footnote Current dominant target for MBSE agents.
55
What is **Teamwork Cloud (TWC)**?
Versioned model repository for Cameo/MagicDraw ## Footnote REST APIs for agent CRUD, diff, auth, and collaboration.
56
What is a **Test Case** in ETM?
Executable or manual verification artifact ## Footnote Agents map requirements ↔ tests and ingest results.
57
What is **Traceability**?
Links across requirement → design → test → result → configuration ## Footnote Agents maintain links so reports and audits are always current.
58
What does **UAF** stand for?
Unified Architecture Framework ## Footnote UML profile for enterprise/mission architecture.
59
What is a **Variant**?
A configured product instance (features chosen, parameters set) ## Footnote Agents generate variant-specific docs (ICD, BOM, tests) on demand.
60
What is a **Work Item** in RTC/Jira?
Task/defect/change unit ## Footnote Agents open/close work and link it to requirements/tests for trace.
61
What is a **product instance**?
Features chosen, parameters set ## Footnote Agents generate variant-specific docs (ICD, BOM, tests) on demand.
62
What is a **Versioned Resource (OSLC Config)**?
Artifact bound to a configuration context ## Footnote Agents must pass config headers to avoid writing in the wrong place.
63
Define **Work Item (RTC/Jira)**.
Task/defect/change unit ## Footnote Agents open/close work and link it to requirements/tests for trace.
64
What are **XML/XMI (Model Interchange)**?
Serialization formats for models and requirements ## Footnote Backup/transfer path when REST/OSLC isn’t available.
65
What does **“Why-Because” / Causal Trace** refer to?
Causal explanation linking requirement → design choice → evidence ## Footnote Agents generate concise rationales for approvals and audits.
66
What are the components of the **mini concept maps**?
* DNG (modules, views, suspects, reviews, streams, baselines, JRS) * OSLC/TRS * Cameo (blocks, IBD/BDD, parametrics, state machines, Alf, CST, TWC) * ReqIF/DataHub/OpenMBEE/Syndeia * ECAD/CAD (APS, Onshape, KiCad scripts, Altium 365) * Nexar/SnapEDA/SamacSys for BOM/library * ModelCenter/Ansys for analysis orchestration ## Footnote This illustrates how various terms and tools connect within the context.
67
Fill in the blank: **Agents generate variant-specific docs (ICD, BOM, tests)** on demand because it is related to the **________**.
product instance ## Footnote This highlights the importance of product instances in documentation generation.
68
What is the **first rule** regarding governance and change control in DNG?
Any requirement change must originate (or be mirrored) in DNG and carry a rationale and verification method ## Footnote This ensures that all changes are traceable and justified.
69
When a requirement changes, all **suspect links** must be dispositioned within how many working days?
2 working days ## Footnote This rule ensures timely updates and management of potential issues.
70
What must reads/writes include according to the rule about **configuration**?
Stream/baseline context (DNG GC + TWC branch) ## Footnote This is crucial for maintaining the integrity of the data.
71
Before which events must a **baseline** be created?
* SRR * PDR * CDR * Automated refactor ## Footnote Baselines are essential for tracking changes and ensuring stability.
72
What is the rule regarding **duplicate blocks/requirements**?
No duplicate blocks/requirements for the same concept; prefer reuse with clear ownership ## Footnote This promotes clarity and reduces redundancy.
73
Every stakeholder or system requirement must be allocated to at least one **model element** and, where relevant, a _______.
CAD/PCB artifact ## Footnote This ensures that all requirements are linked to physical implementations.
74
Behavioral requirements should lead to the creation of _______.
State machines/activities ## Footnote This facilitates the execution of requirements in a structured manner.
75
Any numeric constraint must be bound in a _______.
Parametric network ## Footnote This allows for quantitative analysis and validation of requirements.
76
Explorations occur in TWC branches tied to DNG change sets, following the rule: **Branch for trades, merge for decisions**. True or False?
TRUE ## Footnote This approach helps manage experimental changes effectively.
77
What must pass before merging according to the rule about **merging**?
CST scenarios for affected behaviors and parametric checks ## Footnote This ensures that all changes are validated before integration.
78
Variant artifacts are generated from **feature selections**, not _______.
Copied ## Footnote This prevents inconsistencies and maintains the integrity of variant management.
79
A change in a shared feature must trigger suspecting across all affected _______.
Streams ## Footnote This ensures that all impacts of changes are accounted for.
80
Every physical interface in IBD must have an **ICD slice** with bounded parameters. True or False?
TRUE ## Footnote This is critical for ensuring compatibility and performance.
81
PCB/net rules and mechanical clearances must pass automated checks before _______.
Review ## Footnote This ensures that designs meet necessary standards before evaluation.
82
Alternates are required if lead time is greater than _______ weeks.
8 weeks ## Footnote This helps mitigate risks associated with supply chain issues.
83
Every requirement must have a **verification method** and an evidence link. True or False?
TRUE ## Footnote This is essential for validating that requirements are met.
84
KPIs must be defined in structured form, including metric, threshold, units, and _______.
Source ## Footnote This ensures clarity and traceability of performance metrics.
85
On any upstream change, only the impacted simulations/tests must be _______.
Re-run ## Footnote This optimizes testing efforts and resources.
86
CDR/PR/AR reviews are formal DNG packages with frozen views and _______.
Evidence attachments ## Footnote This formalizes the review process and maintains accountability.
87
Gate criteria include Coverage ≥ **95%**, Open Suspects = **0**, and KPI pass rate ≥ _______.
90% ## Footnote These thresholds ensure readiness for project milestones.
88
Every artifact must cite **GC/TWC context** and tool version. True or False?
TRUE ## Footnote This is necessary for reproducibility and traceability.
89
No agent writes without (a) config headers, (b) permissions check, and (c) _______.
Dry-run diff ## Footnote This prevents unintended changes and maintains system integrity.
90
Every compound change must have a prepared _______.
Rollback ## Footnote This allows for quick recovery from errors.
91
New/edited requirements must follow **EARS patterns**. True or False?
TRUE ## Footnote This ensures clarity and consistency in requirement formulation.
92
Any qualitative adjective must be paired with a measurable bound or it becomes a task to _______.
Specify ## Footnote This prevents ambiguity in requirements.
93
What is the **use case** for **Document-centric RM** in requirements management?
* Create a 'Power Subsystem Requirements' module * Build saved views like 'Needs Test', 'PCB-Impacts', 'Release-Candidate' * Each discipline opens their view and updates only what they own ## Footnote This prevents copy/paste or spreadsheet drift.
94
What does **suspect-link detection & handling** do in DNG?
* Flags downstream links when a stakeholder changes a requirement * Allows leads to bulk-clear suspects after updates * Ensures nothing 'silently' breaks ## Footnote Everyone sees the ripple effects and clears them deliberately.
95
What is the purpose of **formal reviews & approvals inside RM**?
* Assemble a Critical Design Review package * Assign roles like Author, Reviewer, Approver * Capture inline dispositions on each requirement ## Footnote This creates audit-ready approvals tied to exact artifact versions.
96
What is the **use case** for **built-in configuration management**?
* Run concurrent streams for different variants * Propose edits as change sets * Reviewers compare/merge into the stream and baseline for release ## Footnote This allows clean parallel development with traceable deltas.
97
What does **Global Configuration Management (GCM)** include?
* RM stream @ baseline CDR-2 * Test stream @ Sprint-15 * Design links to model/CAD snapshots ## Footnote This provides clarity for audits and root cause analysis.
98
What is the **use case** for **first-class OSLC linking**?
* Link each requirement to Cameo, Jira, or RTC work items * Roll up coverage in dashboards ## Footnote This allows one click from a requirement to its design, task, and test.
99
What can the **Jazz Reporting Service (JRS)** create?
* Compliance dashboard for ECSS / NASA-HDBK mapping * Widgets for requirements by verification method, open suspect links, coverage heatmap ## Footnote This enables live, cross-tool traceability reporting.
100
What is a **use case** for **DXL scripting (DOORS Classic)**?
* Flag requirements missing Rationale or Verification Method * Auto-generate a trace table * Post a summary to Slack/email ## Footnote This automates hygiene and trace tables without manual policing.
101
What is the **scenario** described for a payload mass change?
* PM edits top-level requirement in DNG * Suspects propagate to EPS and PCB constraints * Change set opened in LEO-A stream * OSLC links guide adjustments in Cameo * Review package created and approved * JRS snapshots trace coverage ## Footnote This ensures requirements governance stays in DNG while design/simulation happens in Cameo.
102
What is the **first example use case** for full SysML/UML modeling?
* CubeSat avionics architecture * Model EPS, OBC, COMMS, and payload * Define interfaces and allocate to PCB assemblies * Capture boot and safe-mode flows with activity/sequence diagrams * Bind power-budget equations to parts metadata ## Footnote A single, consistent model drives ICDs for your PCB team and STEP/IFC identifiers for your CAD assemblies.
103
What does the **Cameo Simulation Toolkit** allow for in executable models?
* Execute state machine for thermal control mode logic * Verify requirement “T ≤ 60 °C for 99% of time” * Use time-series temperature profiles from ModelCenter/Ansys ## Footnote Pass/fail KPIs auto-computed from the parametric constraints; trace results back to the requirement.
104
What is an example use case for **textual action code (Alf)**?
* FOC driver fault handling * Write Alf actions for over-current and over-temp responses * Execute activity with injected fault sequences ## Footnote Early, testable logic you can hand to embedded devs; traces link requirements → Alf behavior → test scenarios.
105
What is the **product-line/variability modeling (MBPLE)** use case?
* Model features like BatteryChemistry, RadioBand, CameraType * Derive concrete variants for educational LEO vs suborbital demo * Auto-filter parts, requirements, and tests per variant ## Footnote Clean reuse across missions; generated variant-specific ICDs and BOM slices for PCB/CAD teams.
106
What is the **mission architecture framework** example use case?
* Use UAF to link Operational Views to Resource Views * Map user stories to antennas, radios, on-board computer * Trace to tasking and downlink service/function views ## Footnote A compliance-ready set of views for stakeholders, with direct trace into SysML blocks and CAD/PCB allocations.
107
What is the **trade branch** example use case for model repository?
* Create a TWC branch for exploring an S-band radio * Allocate new interfaces and update power budgets * Merge when the design wins, resolving element-level diffs ## Footnote Safe concurrent MBSE work that mirrors Git-style flow used by your CAD/ECAD teams.
108
What is the **in-model requirements** use case?
* Import DOORS module for Thermal System Requirements * Satisfy them via parametric constraints tied to thermal model * Push status and rationale back to DOORS ## Footnote Single source of truth for governance (DOORS) with live, model-level satisfaction and verification evidence in Cameo.
109
What is an example of a **trade study via parametrics (CST)**?
* Sweep radiator area and heater power * Compute total mass and energy margin * Auto-rank designs and attach winning configuration to variant definition ## Footnote This allows for effective decision-making based on parametric analysis.
110
What is an example of **mode logic executed with Alf actions**?
* Simulate boot-to-detumble * Verify reaction-wheel enable occurs after IMU self-test passes * Ensure bus voltage > 7.2 V for ≥ 2 s ## Footnote This ensures that the system behaves correctly under specified conditions.
111
What does the **UAF operational → resource architecture** example entail?
* Map stakeholder “image latency < 5 min” to downlink service capacity * Trace to radio/EIRP block parameters * Flow into CAD constraints ## Footnote This ensures that operational requirements are met by physical resources.
112
What is the **branch → experiment → merge** example?
* Parallel teams trial two harness topologies in SysML * Visual diff highlights changed ports/flows on avionics IBD * Merge approval based on visual changes ## Footnote This facilitates collaborative design efforts while maintaining oversight.
113
What are the **agent assist** notes for modeling?
* Agents can CRUD elements via TWC REST to keep SysML aligned with CAD/PCB metadata ## Footnote This ensures that the model remains consistent with the latest design data.
114
What do agents do in **simulation**?
* Run CST scenarios on parameter changes * Post KPIs to DOORS ## Footnote This automates the verification process and ensures timely updates to requirements.
115
What is the role of agents in **Alf/fUML**?
* Auto-generate Alf test harnesses from requirements written in EARS style ## Footnote This streamlines the testing process and ensures alignment with requirements.
116
What do agents facilitate in **MBPLE**?
* Switch features to produce variant-specific ICDs/BOMs for procurement ## Footnote This enhances the efficiency of the procurement process by tailoring documents to specific variants.
117
What do agents do in **UAF**?
* Propagate requirement deltas across viewpoints * Flag cross-discipline impacts ## Footnote This ensures that changes in requirements are communicated effectively across all relevant teams.
118
What is the function of agents in **branch/merge**?
* Open experiment branches on TRS change events * Propose merges with summaries ## Footnote This allows for organized experimentation and integration of changes.
119
What do agents reconcile in **requirement sync**?
* Attribute mismatches * Nudge reviewers when satisfaction flips ## Footnote This maintains the integrity of requirement tracking and ensures timely reviews.
120
What are the **three main categories** of third-party helpers for agents?
* OSLC + Linked-Data building blocks * Digital-thread & federation * Analysis & simulation orchestration * CAD automation surfaces * PCB automation + libraries ## Footnote These categories enhance agent capabilities across various tools.
121
Name a tool for **OSLC** and Linked-Data building blocks.
* Eclipse Lyo (SDK & guides) ## Footnote Mature SDK to build OSLC consumers/providers, offering discovery, shapes, TRS, and CRUD.
122
What does the **IBM ELM Python client** provide?
* Reference scripts for DOORS Next OSLC/Reportable REST * ReqIF import/export ## Footnote Great patterns to copy into MCP tools.
123
What is **Intercax Syndeia** used for?
A digital thread platform that federates Cameo Teamwork Cloud with PLM/ALM/CAD ## Footnote Detects changes across versioned elements.
124
What does **OpenMBEE** allow you to do?
* Publish/query Cameo model content as web views/MMS resources * Push regenerated views or harvest structured docs ## Footnote Useful for agents needing to render web views.
125
What is the purpose of **Ansys ModelCenter**?
Orchestrates multi-tool workflows and links Cameo elements to analyses ## Footnote Can be automated via Python for running trades/verification.
126
What does **Autodesk Platform Services (APS)** provide?
* REST APIs for data management * Viewing * Translations ## Footnote Useful for agents that must fetch, convert, or annotate CAD.
127
What can the **Altium 365 APIs** be used for?
REST/Python endpoints on the Altium cloud side ## Footnote Useful for agent flows that sync requirements/attributes into ECAD context.
128
Fill in the blank: **ReqIF Studio** is a free editor/utilities for _______.
ReqIF exchange ## Footnote Handy for agent-managed baselines and audited RM handoffs.
129
True or false: **KiCad Python APIs** are used for agent-driven layout edits.
TRUE ## Footnote They allow for panelization or DFM checks in open-source flows.
130
What is the function of **Nexar (Octopart) GraphQL**?
Provides pricing/stock/specs via Octopart’s successor ## Footnote Perfect for agent BOM checks & risk scoring.
131
What does the **SnapEDA / SnapMagic Search API** provide?
Programmatic access to symbols/footprints/3D ## Footnote Agents can fetch ready-to-place ECAD models.
132
What is the role of **Syndeia** in the agent loop?
Trace impacted Cameo elements and linked CAD/PCB items ## Footnote Optionally render web views via OpenMBEE for human-in-the-loop gates.
133
What is the purpose of **RDFLib**?
A Python library for working with RDF ## Footnote It allows parsing/compiling RDF and running SPARQL queries.
134
What does the **OpenCascade / pythonOCC** library allow you to do?
Read-modify-write and perform geometry operations on STEP/IGES/AP242 ## Footnote Great for agent-side checks or converting neutral files.
135
What is the function of **SnapEDA**?
Access symbols, footprints, and 3D models via an API ## Footnote Useful for agents needing ready-to-place ECAD models.
136
Which workbench is better for **automating systems-engineering workflows**?
CATIA Magic/Cameo ## Footnote Especially when agents also design CAD models and PCBs.
137
What is the role of **DOORS/DOORS Next** in the systems-engineering workflow?
Governance backbone ## Footnote It handles reviews, baselines, and change feeds for events and approvals.
138
Name a key feature of **Cameo** that supports agentic automation.
* Programmable model access (Teamwork Cloud REST) * Server-side simulation via REST (CST) * OSLC exposure of model elements * Forward path to SysML v2 Services ## Footnote These features enhance automation and integration capabilities.
139
What does the **Server-side simulation via REST (CST)** allow agents to do?
* Start/stop simulations * Inject inputs * Collect results/KPIs ## Footnote This helps in auto-verifying requirements and trades.
140
What are the **event & snapshot interfaces** that agents can rely on in DOORS/DNG?
* Reportable REST for bulk, deterministic reads * OSLC + TRS change feeds ## Footnote These interfaces help agents respond to requirement edits and configuration changes.
141
What is the recommended pattern for agent interaction with **DNG** and **Cameo**?
* Sense (DNG) * Think/Act (Cameo) * Trace (Linked Data) * Exchange ## Footnote This pattern outlines the workflow for agents to manage requirements and simulations.
142
True or false: **Cameo** should be the primary integration surface for design-automation.
TRUE ## Footnote It is recommended for model CRUD and simulation.
143
What should be kept as the **system of record** for requirements governance?
DOORS/DNG ## Footnote It serves as the event bus (TRS) into the agent loop.
144
Fill in the blank: **Cameo** provides access to model elements via _______.
Teamwork Cloud REST ## Footnote This allows agents to read/write model elements and manage projects.
145
What are the **OSLC services** used for in IBM DOORS / DOORS Next (DNG)?
* Create/read/update artifacts * Manage links * Work in versioned streams/baselines ## Footnote Ideal for MCP tools that speak Linked Data.
146
What does the **Reportable REST API** provide access to?
* Modules * Artifacts * Attributes ## Footnote Great for agents that need bulk reads or snapshot pulls.
147
What is the purpose of **TRS (Tracked Resource Set)** change feeds via OSLC?
Subscribe/poll for incremental change events ## Footnote Drives event-based agent actions similar to webhook behavior.
148
What types of automation hooks are available in DNG?
* Reviews/approvals * Suspect management * Configurations ## Footnote Addressable via OSLC/REST for agent governance flows.
149
What is **DOORS Classic (DXL)** used for?
Deep on-server automations ## Footnote Agents can trigger DXL services or exchange files with a DXL runner.
150
What is a feature of **historical baselines** in DNG?
Create a baseline 'in the past' ## Footnote Handy for agents needing to reconstruct context/state for a specific timestamp.
151
What are the **roadmap callouts** for DNG?
* Baseline export via existing ReqIF definitions * Platform/service improvements across ELM ## Footnote Useful for faster queries in agent pipelines.
152
In typical MCP wiring, how does an agent **pull** data from DNG?
* Via Reportable REST (periodic) * Via TRS (event-driven) ## Footnote This is part of the data ingestion process.
153
What actions can an agent take to **act** on data in DNG?
* Propose changes (new artifact, link) * Open a review * Post rationale ## Footnote These actions are facilitated via OSLC.
154
What does an agent do to **trace** its decisions in DNG?
Stamps OSLC links back to its own 'decision' artifacts ## Footnote This is important for audit purposes.
155
What are the **Teamwork Cloud (TWC) REST APIs** used for?
* Manage projects * Manage users * Manipulate model content (create/read/update/delete elements) ## Footnote Suitable for agent “model-as-a-database” operations.
156
What does the **OSLC provider in TWC** expose?
* Model elements as OSLC resources * Links SysML/UML elements to DNG, ETM, Jira, etc. ## Footnote Facilitates navigation in a Linked Data thread for agents.
157
What is the purpose of the **Cameo DataHub OSLC connector**?
Off-the-shelf bridge for live sync/links with DNG ## Footnote Useful if your agent wants to operate through an established sync layer.
158
What can the **Server-side simulation REST (Cameo Simulation Toolkit)** do?
* Start/stop simulations * Feed inputs * Retrieve results/plots programmatically ## Footnote Ideal for agents that run trade studies or verify sequences.
159
What programming languages are supported by the **CST Java & scripting APIs**?
* Groovy * Python * JavaScript * Beanshell ## Footnote Allows embedding richer agent logic or registering listeners for run-time events.
160
What functionalities does **Cameo Collaborator for Web** provide?
* Publish views/documents * Push refreshed views * Extract rendered artifacts (images, tables) for reports * Link OSLC previews into other tools ## Footnote Enhances collaboration and presentation surfaces for agents.
161
What does the **SysML v2 API & Services (OMG)** offer?
* Standardized REST/HTTP service model (PIM/PSM) * Public cookbooks ## Footnote Aligns with CATIA Magic’s SysML v2 Early Experience for uniform, scriptable access for agents.
162
In typical MCP wiring, what does the **Pull** action involve?
Agent reads model state via TWC REST/OSLC; fetches viewpoints for context ## Footnote This is the initial step for agents to gather necessary information.
163
What does the **Act** action entail in typical MCP wiring?
* Proposes/creates elements (e.g., requirement proxy, param block) * Kicks off a simulation run * Captures KPIs ## Footnote This step involves taking action based on the model state.
164
What does the **Trace** action do in typical MCP wiring?
* Writes OSLC links back to DNG items * Publishes a Collaborator view with results ## Footnote Ensures that results and links are documented and accessible.
165
What is the purpose of using **OSLC TRS** from DNG?
To wake your agent on requirement edits ## Footnote Follow OSLC links to related Cameo elements via TWC OSLC.
166
Which REST service is used for **bulk read/snapshot**?
DNG Reportable REST for denormalized pulls ## Footnote TWC REST model queries for targeted element graphs.
167
What does the agent do in the **propose & verify** process?
* Creates/updates links/artifacts via OSLC (DNG) * Updates elements via TWC REST * Runs CST simulation to verify acceptance criteria ## Footnote This is done before requesting a DNG review.
168
What is the purpose of using **ReqIF** in interchange & governance?
For controlled, auditable exchanges ## Footnote Publish Cameo Collaborator docs for human approvals that your agent can reference.
Agentic Systems
flashcards
Decks in class (27)
# Cards
Brainscape helps you reach your goals faster, through stronger study habits.
© 2026 Bold Learning Solutions. Terms and Conditions