How to Use These Pages
A short guide to getting the most out of the glossary — whether you are a systems engineer, software designer, or MBSE architect.
What this glossary covers
Every entry explains a concept, artifact, or diagram used across the Mission Planning Environment sandbox. The glossary is built for four audiences: program managers, systems/software designers, MBSE architects, and V&V engineers. You can read any entry in the perspective that matches your current role.
Finding terms quickly
- Use the search box on the glossary index to filter by name, tag, or keyword (e.g., L1, ICD, V-Model).
- Click a category chip (Requirements, SysML, DoDAF, Process, Mission Planning) to narrow the list to one domain.
- Each card shows the term, a one-line summary, and tags so you can scan quickly.
Switching views on a term
Open any term and use the four perspective buttons at the top of the page to change what you see:
What the term means and why it exists in the lifecycle.
How a design engineer reads, writes, or validates it.
How it lives in the model, traces to other elements, and is represented in SysML or DoDAF.
A worked public example plus common mistakes to avoid.
Related terms
At the bottom of each entry you will find a See Also section with links to related glossary items. Use these to move horizontally across the lifecycle — for example, from an L2 requirement down to its L4 software requirement, or from a SysML block definition diagram to its corresponding internal block diagram.
Getting the most value
- Start with Definition & Purpose if you are new to the term.
- Switch to MBSE Architect when you need to know which SysML diagram or DoDAF view to use.
- Read Example & Pitfalls before a review or sprint planning — it lists the mistakes teams make most often.
- Use your browser find-in-page (Ctrl+F / Cmd+F) to scan within a long entry.