For classes
Instructor guide: teaching a course with Holarch
How to set up a class in Holarch and run three ready-made modules on it: requirements and verification, functional and physical architecture, and SysML v2 basics. Each module lists the training chapters students watch, the in-app tutorials they complete and the EO-1 class assignment they hand in. A group-project option follows.
On this page
Before you start
Holarch is free for students and instructors (see For classes). Students learn the tool from three sources, so class time can go to the method:
- Training chapters at /training/: short videos, one task each.
- In-app tutorials: guided steps on a small Weather Station model, with a panel that checks the work. Students start them from Help → Tutorials in the rail. Tutorial projects do not count toward a student's active projects.
- Exercise sheets with answer keys, one per training track (listed below), for practice outside class.
The graded work uses the EO-1 Open MBSE Reference Model, a fictional CubeSat with gaps, failed tests and an open requirement change built in on purpose. The Teaching with Holarch guided tour shows the instructor side in five minutes.
Class setup checklist
Do this a week or two before the first session. Training Track 8, Teaching with Holarch, shows each step on screen once it is published on the training page.
- Create the class organization. Account Settings → Organizations → Create Organization, named after the course. You become its org admin. (Track 8.1, Setting Up a Class Organization.)
- Request class status. In Organization Settings, open the organization and, under Class, click Request Class Status…. Enter the course, the school and the end of term, attach the syllabus (PDF or Word) and send it. Holarch reviews the request and emails you. Class status gives the organization's projects 6 collaborators for a member's project and 50 for yours, 2,000 items each, and the Class Review tab, and its projects do not count toward their owners' active projects. See Run a class. (Track 8.2, Class Status and the Syllabus.)
- Add the members. Under Members, enter each student's email address, choose Member and click Add Member. An address without an account gets an invitation.
- Make your teaching assistants org admins. Add each TA with Org admin, so they see Class Review and can manage the roster. Administering an organization gives no access to project content: projects are opened through their own sharing.
- Have each group create its project. The group lead creates the EO-1 model (Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering)), chooses the class organization under Share → Organization, invites the group as editors and you and your TAs as Reviewer. Reviewers are not counted against the collaborator limit; they can read, export, comment and approve or reject requirements and document reviews, but not edit.
- Publish your templates. If an assignment starts from a document, build it once from a built-in template, add your instructions to its sections and save it with Write ▾ → Templates ▸ Save as Template… to the organization, as the default for its type. Students then find it preselected in + New Document. See Save a document as a template. (Track 8.3, Assignments from Templates.)
- Add the due dates. Organization Settings → Class Review → + New Assignment, with a name and the due date and time. At that moment Holarch keeps a version of every group project and each member's counts, so you can compare later work with the due date. See Set an assignment due date.
- Decide on AI. AI follows the class organization's setting. For an exam, clear Allow AI in this organization's projects and keep Also turn off API and MCP access ticked, so AI tools connected through MCP are off too. Afterwards, tick the AI box again and turn API access back on separately. See Turn AI off for an organization. (Track 8.5, Turning AI Off for an Exam.)
- Tell students to keep copies. Students can export a project at any time. Ask for an export before each deadline.
Using Class Review
Class Review is where you read group work at a due date. Open it under Organization Settings → Class Review, or press ⌘K / Ctrl+K and choose Class Review.
- Read the work. Under Group projects, click a project to see it without joining it. Item names open a preview with the item's text and comments.
- Compare with a due date. Choose the assignment under Compare with: counts show their value at the due date, and work changed or added later is marked Changed after due date or Added after due date. Holarch marks late work; it does not lock a project at the due date.
- Comment and approve in the project. As a Reviewer of the group project, add comments on items and use Approve and Reject… on requirements under review. (Track 8.4, Reviewing and Commenting on Student Work.)
- Export for the gradebook. Under Class roll-up, Export (Excel) gives one sheet for the class, one per group and one per student. Grades and rubrics stay in your own gradebook.
Grade the model and the reasoning you read in it. Per-member counts and Activity are evidence for the rare case where a member's share of the group work is in question; they are not a measure of quality and not a reason to watch every student. (Track 8.6, Evidence for Grading: Class Review and Activity.)
Module 1: Requirements and verification (2 weeks)
Students learn to write and review requirements, trace them to needs, and read verification coverage.
Week 1: needs, requirements and tracing
- Watch: Writing Requirements and the Quality Check, Tracing Needs to Requirements, Open Items and Approvals. New users first watch The Holarch Workspace.
- Tutorials: Write Good Requirements and Trace Requirements.
- Hand in: A1 Trace a need (individual, a written note).
- Class Review: A1 changes nothing in the model, so it needs no due date in Class Review. Add the A2 due date now so groups see the deadline.
Week 2: review, baselines and verification
- Watch: Baselines and Links to Review, Verification and the Test Center, RVTM and VCRM.
- Tutorials: Verify the Requirements.
- Hand in: A2 Requirements rework and review (groups). Plan the review round in the middle of the week: groups set their three requirements to In Review, you comment and approve or reject as Reviewer, and they answer before the due date.
- Class Review: compare each group project with the A2 due date, read the three requirements, their review comments and the baselined specification. Optional follow-up: A3 Find the coverage gaps as a third week or as homework.
Module 2: Functional and physical architecture (3 weeks)
Students decompose functions, build a logical layer between the functions and the parts, derive interfaces, and follow a change through the architecture.
Week 1: functions and coverage
- Watch: Functions and the FFBD, Action Diagrams.
- Tutorials: Functional Analysis.
- Hand in: A3 Find the coverage gaps (groups). It shows students where the architecture is thin before they extend it.
Week 2: allocation and interfaces
- Watch: Allocation, Interfaces.
- Tutorials: Physical Architecture and Allocation and Interfaces.
- Start: A4 Extend the architecture (groups, due at the end of week 3).
Week 3: analysis and change
- Watch: Simulation, Budgets and TPMs.
- Tutorials: Simulate the Functional Flow and Baseline, Change, Impact.
- Hand in: A4. If the module has room for a fourth week, add A5 Work the change: the power equations and TPM-2 from this week's chapters are its inputs.
- Class Review: add a due date per assignment. For A4, compare with the due date and open the new logical elements and their allocations in each group's project; the architecture description they hand in should match what the model holds.
Module 3: SysML v2 basics (2 weeks)
Students write a small model in SysML v2 textual notation, see it as views, and learn what the tool's checks prove. Each group creates a SysML v2 project for its work; the SysML v2 tutorials build parts of a hybrid car.
Week 1: structure
- Watch: Definitions and Attributes, Ports and Interfaces, Actions and Flows.
- Tutorials: Getting Started, Definitions and Attributes and Ports and Interfaces.
- In class: go through the SysML v2 teaching boundaries: what the Editor checks, what it keeps without interpreting, and why "not yet in Holarch" is not "not allowed".
Week 2: requirements and constraints
- Watch: Requirements, Verification and Traceability, Constraints and Calculations.
- Tutorials: Requirements and Constraints and Calculations.
- Hand in: A6 part B on its own: the EO-1 power subsystem in SysML v2, the 30 W change, a design that meets it, and the half page on what was checked and what was only kept.
- Class Review: add the due date. Read the file and the half page together: the grade rests on the explanation, since 0 diagnostics alone proves only what the checks cover.
Group-project option
For a term project, each group models a system of its own choice, not EO-1, from needs to verification. The class features carry the course structure:
- A project per group in the class organization. The group lead creates the project (blank, or from the example class starter on For classes), chooses the class organization under Share → Organization, invites the group as editors and the teaching staff as Reviewer.
- Milestones as due dates. Add one Class Review assignment per milestone, for example concept and needs, requirements review, architecture, and verification plan. Each due date keeps a version of every group project to grade against.
- A review round as Reviewer. Before the requirements milestone, groups set their requirements to In Review; you and the TAs comment, approve or reject, and the groups rework and resubmit, as in A2. Peer review works the same way: add another group's members to a project as Reviewer.
- An exam window without AI. Turn AI off for the organization, with API and MCP access, for the exam and back on afterwards (checklist step 8).
- A final baseline as the submission. Each group saves a project baseline under Control & Reviews → Baselines & Versions → + Save Baseline…, named for the submission, and exports its deliverables (for example the specification and the verification plan to Word). Grade the baseline, not the live project.
- Contribution evidence only when needed. Grade the group on the model and its reasoning. Open a member's contributions in Class Review only where that member's share is in question.
Adapt the rubrics of the EO-1 assignments for each milestone: they grade judgment (completeness of the chain, the quality of each decision, verification against validation) rather than the number of items.
Exercise sheets
Each sheet holds short practice tasks for one training track, with an answer key, for students who want more practice than the assignments give. They are public, so they are not graded work.
- Getting Started
- Requirements and Verification
- Behavior and Architecture
- Documents and Deliverables
- SysML v2 Fundamentals
Getting help
For class setup, a class status question or the solution notes for A1 to A6, contact us with the topic Instructor. The Run a class and Contributions pages of the Docs hold the details of every step above.