Holarch

Instructor package · v1.0

Teaching with Holarch: instructor package

Course learning outcomes and six assignments with rubrics for a one-semester systems engineering or MBSE course, all built on the EO-1 Open MBSE Reference Model v1.1, a fictional 6U Earth observation CubeSat. Free under CC BY 4.0.

Download the instructor package v1.0

All files (.zip, 17 KB)

Markdown files that open in any editor. Uses the EO-1 Reference Model v1.1. License: CC BY 4.0, credit "Holarch".

On this page
  1. What it holds
  2. How to use it
  3. Solution notes
  4. Learning outcomes
    1. Mapping to the assignments
  5. A1 · Trace a need
  6. A2 · Requirements rework and review
  7. A3 · Find the coverage gaps
  8. A4 · Extend the architecture
  9. A5 · Work the change
  10. A6 · Validation plan
  11. Teaching SysML v2 with Holarch: what it checks and what it only keeps
  12. Downloads
  13. Versions
  14. How to cite
  15. License

What it holds

FileForWhat it holds
learning-outcomes.mdInstructors, accreditation recordsThe course learning outcomes, the assignments that assess each, and the Holarch features used.
assignments/A1-trace-a-need.md to A6-validation-plan.mdStudents (hand out)Six assignments on EO-1, each with background, task, what to hand in and a rubric.
sysml-v2-teaching-boundaries.mdInstructorsWhat Holarch's SysML v2 projects check, what they keep without interpreting, and what is not available yet.

How to use it

  1. Give each group its own copy of EO-1 v1.1. In Holarch: Manage Projects → Project Files ▾ → New Demo Project → CubeSat EO-1, or download eo-1-v1.1.holarch.json from holarch.app/reference-models/eo-1/ and import it with Manage Projects → Project Files ▾ → Import Project…. Every assignment starts from the model as it ships.
  2. Run the course in a class organization. Add each assignment with its due date under Organization Settings → Class Review → + New Assignment. Class Review keeps a version of every group project at each due date and shows each student's work.
  3. For A2, join each group project as a Reviewer: you can comment, approve, reject and reopen requirements, and nothing else.
  4. For A6, students start from the built-in Verification and Validation Plan template. To give them a trimmed version with your own instructions, save one as an organization template (Write ▾ → Templates ▸ Save as Template…, Save to: Organization) and make it the default for Test Plan Document.
  5. Set the weights, group sizes and due dates for your course. The weights given are suggestions.

The assignments name Holarch pages, but every question can also be answered from the EO-1 CSV files, so students who work in another tool can take part.

Solution notes

Solution notes with expected findings, sample answers and common mistakes for A1 to A6 are not published, so students cannot download the answers. Instructors download them in Holarch: Organization Settings → Class Review → Download Solution Notes. The button shows for organization administrators (instructors and teaching assistants) of an organization with class status.

Learning outcomes

Course: Model-Based Systems Engineering, one semester, upper-level undergraduate or first-year graduate.

By the end of the course, students can:

#OutcomeAssessed byHolarch features used
LO1Distinguish stakeholder needs from system requirements, and trace each need to the requirements that formalize it.A1, midtermStatements, traced to relationships, the Item View's Trace section, Traceability Matrix
LO2Write requirements that are necessary, singular, unambiguous and verifiable, with a verification method and success criteria.A2, midtermRequirement attributes, Quality, TBD/TBR
LO3Run a review and approval cycle on requirements, and respond to review comments with changes to the model.A2, review participationReviewer role, Approvals (Approve, Reject…, Reopen), comments with mentions
LO4Analyze traceability and verification coverage, and decide for each gap whether the model or the requirement is wrong.A3Traceability Matrix, RVTM, Model Checks
LO5Decompose functions, define a logical architecture, allocate functions to logical and physical elements, and derive the interfaces that follow.A4, finalAction diagrams and FFBDs, Assets, allocation, Interface Register
LO6Assess the impact of a requirement change through the model, and record a decision for each affected item.A5, finalLinks to Review, impact analysis, Change Requests, Baselines & Versions
LO7Plan verification and validation: tell them apart, choose methods, write test and validation procedures in the right terms, and read an RVTM.A6, finalTest cases and suites, Test Center, RVTM and VCRM, document templates
LO8Produce engineering deliverables from the model and keep them consistent with it: baselined documents and matrices exported for review.A2, A6, finalDocuments, live matrices, baselines, Word and Excel export
LO9 (optional)Read and write SysML v2 textual notation for a subsystem, and state which properties a tool checked and which it only kept.Optional part of A6SysML v2 project, the Editor's checks, the SysML v2 teaching note

Mapping to the assignments

OutcomeA1 Trace a needA2 Requirements reworkA3 Coverage gapsA4 ArchitectureA5 Change impactA6 Validation plan
LO1●○○
LO2●○
LO3●
LO4○●○
LO5●
LO6●
LO7○○○●
LO8○●

● main outcome assessed, ○ also contributes.

Notes for the instructor

  • The outcomes describe systems engineering ability, not tool skill. Holarch is where students practice; the EO-1 CSV files let a student show every outcome without it.
  • The outcomes follow common systems engineering practice, for example the ISO/IEC/IEEE 15288 technical processes: stakeholder needs and requirements definition, system requirements definition, architecture definition, verification and validation. Map them to your program's accreditation criteria as your school requires.

A1 · Trace a need

Outcomes: LO1 (main), LO4, LO7 · Group size: individual · Suggested weight: 8 %

Background

EO-1's customer, an agricultural analytics company, stated three needs. N2 Twice-Weekly Revisit reads: "Farm customers need fresh imagery of their fields at least twice a week in the growing season." A need is met only when the requirements that formalize it are satisfied by the design and verified, and the need itself is validated with the customer.

Task

  1. Follow N2 through the model: the requirements it traces to, their children, the functions and components that satisfy each one, and the test cases that verify them, with each test's status.
  2. Draw the chain as a table or a small diagram: one row or box per item, with its number, name, status and the relationship that connects it.
  3. Find the validation activity for N2 and its status.
  4. Answer: What evidence is still missing before N2 counts as validated? List each missing piece, the item it belongs to, and what would close it.
  5. Look for requirements that support N2 but do not trace to it. Name one candidate and argue for or against adding the trace. Do not add it to the model.

In Holarch: open N2 in the Item View and read its Trace section, then use Verification → Traceability Matrix, Verification → RVTM and Verification → Test Center. Without Holarch: eo-1-v1.1-traceability.csv and eo-1-v1.1-rvtm.csv.

Hand in

A note of one to two pages (Word or PDF) with the chain, the missing evidence and your answer to step 5. Do not change the model for this assignment.

Rubric

Criterion4 Exemplary3 Proficient2 Developing1 Beginning
Chain complete and correct (40 %)Every item from N2 to the tests, with the right relationships and statuses, including both children and the validation activity.One item or status missing or wrong.The chain stops at the requirements or misses a child.Items listed without relationships.
Missing evidence (35 %)Names every gap (tests not run, a parent without its own verification, requirements not yet approved, the validation not run, the child without a function) and what closes each.Most gaps, with what closes them.Lists gaps without saying what closes them.Says only "tests are missing".
Verification vs validation (15 %)Keeps the two apart throughout: requirements are verified, the need is validated.One slip.Treats a passed test as validating the need.No distinction.
Candidate trace (10 %)A specific requirement with a reasoned argument either way.A candidate with a thin argument.A candidate without an argument.Missing.

A2 · Requirements rework and review

Outcomes: LO2 (main), LO3, LO8 · Group size: group · Suggested weight: 10 %

Background

Three EO-1 requirements are still drafts and score 44 % in Holarch's quality check:

  • 2.5 Safe Mode Recovery: "The spacecraft should recover from safe mode quickly and resume imaging as appropriate"
  • 3.5 Battery Thermal Control: "The thermal design shall keep the battery warm enough (TBD)."
  • 6.4 Operator Interface: "The operator interface shall be user friendly and/or easy to use."

3.5 also has an open issue, ISS-3 Battery heater set point not chosen, and a review comment from the design review board, RID-1 No cold-case analysis for the battery heater.

Task

  1. For each of the three, list what makes it weak, word by word where it matters.
  2. Rewrite each in the group project: one "shall", one measurable condition, and a stated starting point or condition where time or range is involved. Replace every TBD with a value and record its rationale, or keep a TBR with an owner and a date. For 3.5, say how your rewrite answers ISS-3 and RID-1.
  3. Fill in Verification Method, Verification Level and Success Criteria for each.
  4. Trace each to where it comes from (a need, a parent requirement or a source) and to the function that satisfies it. If no function exists, name the function that is missing.
  5. Set each to In Review. Your instructor reviews them as a Reviewer. Answer every comment in the model (change the requirement, or reply with a reason), then resolve the comment.
  6. Save a baseline of the document EO-1 System Requirements Specification (SRS-001) named "A2 handed in" and export it to Word.

In Holarch: Needs & Requirements → Quality, the requirement's inspector, Needs & Requirements → Approvals, and in the document Version ▾ → Save Baseline… and Deliver ▾ → Specification (Word).

Hand in

The Word export, plus a half-page note on the weaknesses you found in step 1. The model as it stands at the due date is graded with it.

Rubric

Criterion4 Exemplary3 Proficient2 Developing1 Beginning
Rewritten requirements (40 %)All three singular, measurable and verifiable; conditions and starting points stated; values justified.One requirement still has a vague term or a missing condition.Values added, but conditions or rationale missing.Wording changed, still not verifiable.
Verification attributes (20 %)Method, level and success criteria fit each requirement and could be run as written.One mismatch, for example Test where only Analysis is possible.Methods set, success criteria vague.Missing.
Traceability (15 %)Each traced to its source and its satisfying function, or the missing function named.One trace missing.Sources only.None.
Review cycle (15 %)Every review comment answered in the model and resolved; rejected requirements reworked and resubmitted.One comment left open.Comments answered without model changes.Comments ignored.
Weakness analysis (10 %)Precise: names each vague term and why it cannot be verified.General but correct.Restates the quality score.Missing.

A3 · Find the coverage gaps

Outcomes: LO4 (main), LO1, LO2, LO7 · Group size: group · Suggested weight: 10 %

Background

EO-1 is at its critical design review. The model is deliberately imperfect: some requirements have no function satisfying them, some have no test, some tests failed, and one equation is linked to nothing.

Task

Work from the model as it ships in v1.1. Use a fresh copy if your group project has changed.

  1. List every requirement that no function satisfies.
  2. List every requirement that no test case verifies, and those whose tests failed, with the open issue and any deviation recorded against them.
  3. List the requirements with no satisfying component. Decide which of them need one and which are rightly satisfied at mission or segment level.
  4. Find model items that nothing traces to. Hint: look at the power equations.
  5. For each gap, decide: is the model missing something (a function, a component, a test, a link), or is the requirement not needed or wrongly written? Give one sentence of reasoning per gap.
  6. Close three gaps of your choice in the group project, each as one change you can point to in Control & Reviews → Activity.

In Holarch: Verification → Traceability Matrix, Verification → RVTM, Verification → Model Checks and Risks, Issues & Decisions → Issues & Actions. Without Holarch: eo-1-v1.1-traceability.csv (its Coverage column), eo-1-v1.1-rvtm.csv, eo-1-v1.1-issues-actions.csv and eo-1-v1.1-deviations-waivers.csv.

Hand in

A gap table (gap, item, decision, reasoning, closed yes or no) as Excel or Word, and a list of the three changes you made.

Rubric

Criterion4 Exemplary3 Proficient2 Developing1 Beginning
Gaps found (35 %)All function, test, component and orphan gaps, including the failed tests with their issues and deviation.One or two gaps missed.Only the obvious drafts found.Fewer than half.
Decisions (35 %)Each gap gets a defensible decision; distinguishes missing design from unneeded or mis-scoped requirements and from mission-level satisfaction.Most decisions sound.Every gap treated as "add a link".No decisions.
Changes made (20 %)Three changes that really close gaps, each one clean step in the record.Two good changes.Changes that hide a gap, such as a link added without a reason.None.
Presentation (10 %)Table is sortable and complete.Minor omissions.Hard to follow.Missing.

A4 · Extend the architecture

Outcomes: LO5 (main), LO4 · Group size: group · Suggested weight: 12 %

Background

EO-1's logical architecture (L0) covers only the power and data handling slices: L1 Power Generation to L6 Fault Management. Each logical element groups functions (allocated to) and is realized by a physical part (related to); for example F3.1 Convert Sunlight to Power is allocated to L1, and 1.3.1 Solar Arrays realizes L1. Attitude determination and control has the functions F4.1 Estimate Attitude, F4.2 Compute Control Torques, F4.3 Drive Reaction Wheels and F4.4 Unload Wheel Momentum, and physical parts under 1.2 ADCS, but no logical layer.

Task

  1. Add logical elements for attitude determination and control under L0. Each element states its purpose without naming hardware.
  2. Allocate F4.1 to F4.4 to them, and relate each logical element to the physical parts under 1.2 ADCS that realize it, following the pattern of L1 to L6.
  3. Draw the action diagram of F4 with the items that flow between its subfunctions, for example the attitude estimate and the torque commands, if your group project does not have one yet.
  4. From the flows that cross element boundaries, derive the interfaces. Compare them with the existing interfaces IF-06, IF-16, IF-17 and IF-18: which match, which are missing, and which carry items no function uses?
  5. Check that 2.1 to 2.4 are each satisfied by the function that does the work, and say which logical element is then responsible for each requirement.

In Holarch: Architecture → Assets, Behavior → Action Diagrams (F4), the inspector's Trace section for the allocations, Interfaces → Interface Register, and the Allocation Hierarchy preset of the hierarchy diagram. Without Holarch: eo-1-v1.1-allocation-chain.csv and eo-1-v1.1-icd.csv.

Hand in

A short architecture description (two to three pages, Word or PDF): the logical elements with their purposes, the allocation table (function → logical element → physical part), the F4 action diagram, and the interface comparison.

Rubric

Criterion4 Exemplary3 Proficient2 Developing1 Beginning
Logical elements (25 %)Solution-independent, cohesive, each with a clear purpose; no hardware names.One element names hardware or mixes purposes.Elements copy the physical parts.Missing or unclear.
Allocation (30 %)Every subfunction allocated once to the right element; elements realized by parts; consistent in the model.One allocation questionable.Allocations only to parts, skipping the logical layer.Incomplete.
Flows and interfaces (30 %)Interfaces derived from boundary-crossing flows; precise comparison with IF-06, IF-16, IF-17 and IF-18, including gaps both ways.Comparison mostly right.Interfaces listed, not derived.Missing.
Requirement responsibility (15 %)Each of 2.1 to 2.4 traced through its function to a logical element, inconsistencies named.One missing.Listed without checking.Missing.

A5 · Work the change

Outcomes: LO6 (main), LO7 · Group size: group · Suggested weight: 10 %

Background

After the design review, requirement 3.1 Orbit Average Power changed from 28 W to 30 W orbit-average power at end of life. Test case TC-06 Solar Array Power Test passed against the old value. Holarch marked the links of 3.1 for review.

Task

  1. List every item the change reaches: forward through the links from 3.1, backward to what 3.1 derives from, and items that mention the old value without a link to 3.1. Say how you found each one.
  2. For each item, write the question the change raises, your finding (with numbers where the model has them), and a decision: no change (mark the link reviewed with a comment), update, or escalate to the change board.
  3. Decide what to do with TC-06: does a test that passed at 28 W still prove 30 W? Show the arithmetic from the model's equations.
  4. Find one item the link-based analysis misses and say why it matters.
  5. Record your decisions in the group project: a comment on each link you mark reviewed, a change request for what the board must decide, and a baseline before and after.

In Holarch: Needs & Requirements → Links to Review, the impact analysis from 3.1 (Open in ▾ → Spider, then Impact), the inspector's Trace section, the power equations EQ-1.1 to EQ-1.4 and TPM-2 (Architecture → Budgets & TPMs), Control & Reviews → Change Requests and Control & Reviews → Baselines & Versions. Without Holarch: eo-1-v1.1-traceability.csv and eo-1-v1.1-change-impact-3.1.csv, the published impact record; do your own analysis first, then compare.

Hand in

An impact record (a table: item, how reached, question, finding, decision, status) and a one-paragraph recommendation to the change board.

Rubric

Criterion4 Exemplary3 Proficient2 Developing1 Beginning
Reach (30 %)Forward, backward and text-search items found, including those no link reaches.Links only, all of them.Some forward links.3.1 and TC-06 only.
Findings with numbers (30 %)Uses the model's values and equations; the TC-06 shortfall is computed and explained.Numbers mostly right.Qualitative only.Wrong conclusions.
Decisions (25 %)Each item has a decision that fits the finding; links marked reviewed only with a reason; board items kept separate.One decision weak.Marks links reviewed without reasons.No decisions.
Record in the model (15 %)Comments, change request and baselines in place and consistent with the record.One missing.Only the document.Nothing in the model.

A6 · Validation plan

Outcomes: LO7 (main), LO8, LO1 · Group size: group · Suggested weight: 10 %

Background

Verification asks whether EO-1 was built right against its requirements; validation asks whether it is the right system for the farm customers. EO-1's validation suite TS-3 Mission Validation holds VAL-01 Customer Alert Pilot (for N1, not run), VAL-02 Growing Season Revisit Simulation (for N2, not run) and VAL-03 Agronomist Map Review (for N3, passed).

Start the plan in Needs & Requirements → Documents → + New Document. Under Template, set Templates for to Test Plan Document and choose the built-in Verification and Validation Plan with Include writing guidance, or the organization template your instructor published for this assignment.

Task

  1. 5.1 Operational Scenarios: write the scenario for VAL-01 in the customer's terms: who does what, on which day, with which result. Name the need it exercises.
  2. 5.2 Users and Participants: name the representative users and what each one decides.
  3. 5.3 Validation Environment: describe the environment, how it differs from operations, and what that difference means for the result.
  4. Write VAL-01's acceptance criteria so that a customer could say yes or no without engineering judgment, and record them in the test case's Expected Result.
  5. 8 Verification Status: read the live matrix. Pick the failed test TC-04 Pointing Accuracy Test and say what VAL-01's result would mean if TC-04 is still failed at the time of the pilot.
  6. Export the plan to Word.

Optional: SysML v2 bonus (LO9, up to 10 % extra)

Create a SysML v2 project from eo-1-v1.1-power-subsystem.sysml (Manage Projects → Project Files ▾ → Import SysML v2 Files…). The file still holds requirement 3.1 at 28 W. Change the required orbit-average power to 30 W, the change from A5, and read what the Editor reports. Is it a modeling error or a design finding? Then change the design values, not the requirement, until the Editor's status line says No problems, and say whether your new values are physically credible. In half a page, state which of your claims the tool checked and which it only kept; the SysML v2 teaching note your instructor shares lists both.

Hand in

  • The Word export of the plan.
  • For the SysML v2 bonus: the .sysml file and the half page.

Rubric

Criterion4 Exemplary3 Proficient2 Developing1 Beginning
Scenario in customer terms (30 %)Concrete, day-in-the-life, no engineering jargon; clearly exercises N1.Clear, with some jargon.A test procedure, not a scenario.Missing or generic.
Acceptance criteria (25 %)Observable, yes or no, owned by the customer; tied to N1's "on the day of an overpass".Mostly observable.Engineering thresholds only.Vague.
Participants and environment (20 %)Representative users named with their decisions; differences from operations and their effect stated.One missing.Listed without effect.Missing.
V&V reasoning (15 %)Explains why a validation pilot can succeed or fail independently of TC-04 and what each outcome means.Mostly sound.Confuses verification and validation.Missing.
Deliverable (10 %)Clean Word export, template guidance replaced by content.Leftover guidance text.Partly exported.Missing.
SysML v2 bonus (up to +10 %)Finding explained; No problems, with credible values; precise statement of what was checked and what was kept.No problems; statement general.Requirement weakened instead of the design changed, or problems left.No credit.

Teaching SysML v2 with Holarch: what it checks and what it only keeps

Holarch's SysML v2 projects support a subset of the OMG SysML v2 specification. The current state of each area is on the SysML v2 language coverage page (holarch.app/sysml-v2-coverage/); check it before each term. When you teach the language with Holarch, keep three kinds of statement apart, so students do not learn a tool limit as a language rule, or take a construct the tool kept for one it checked:

  • Checked: the Editor parses the construct and checks it as you type, and the views and pages use it. When the Editor's status line says No problems, these checks passed.
  • Kept, not interpreted: parsed and kept exactly as written, in the text and in exports, but given no meaning. No problems says nothing about whether it is right.
  • Not yet in Holarch: the construct or feature is not available in Holarch. It is still valid SysML v2.

Checked: safe to teach and assess with the tool

AreaWhat students can rely on the Editor to catch
SyntaxCharacters, comments, strings, braces, ;, expected names and tokens.
Names and importsUnresolved, ambiguous, duplicate and private names; membership, namespace, recursive and filtered imports.
Definitions, usages, specializationpart, attribute, port, action, state, requirement and the other kinds and their definitions; typing, subsetting, redefinition and conjugation; cycles and the wrong kind of definition.
Multiplicities, values and unitsValid bounds; quantities with the ISQ quantity kinds and SI and US customary units; dimension checks: a power where a mass is expected is an error.
Constraints and calculationsOperand types, calculation arguments, Boolean conditions, and evaluation: constraints, requirements and objectives that do not hold for the current values are reported.
StructureConnection ends; port, flow and message directions; interfaces and binding connectors.
Actions and statesSuccession targets, control nodes, the values a for loop iterates over, initial transitions, parallel regions, transition triggers and do effects.
Requirements and use casessubject, actor, stakeholder, require and assume constraint, satisfy, verify and frame targets in the right places.
Allocationallocate … to …, allocation definitions, dependencies.
VariabilityA variation owns only variants of its kind, a choice is a variant of its point, and the choice's values are evaluated.
Individuals, snapshots and time slicesEach has the features of the occurrence it belongs to; its own values are read first.

Partly checked: teach with the limit named

AreaChecked or runLimit to tell students
ActionsThe Simulator runs action flows, including Monte Carlo runs.Step durations, branch probabilities and loop counts are Simulator settings kept in Holarch, not in the text, so a .sysml export does not carry them.
StatesThe Simulator runs state machines with stimuli and shows the active states.The same: Simulator settings are not part of the text.
Analysis and verification casesSubject, objective, return result; verify and a verdict.An analysis case is evaluated only when every input has a value; there is no solver. In a Parametric View, Solve finds one unknown per constraint. Trade-study analyses from the standard library are not evaluated.
Viewsview, view def, expose, filters, viewpoints and the standard view definitions; Sequence Views draw alt, opt, loop and par fragments.The layout belongs to Holarch, not to the model.
VariabilityVariations, variants and configurations are checked and evaluated.Holarch does not yet search for or list every valid combination.
Metadata and keywords@Name, #Name, metadata … about, user-defined keywords from semantic metadata.Other user-defined metadata has no meaning beyond its values; metadata written with about adds no base type.
Textual representationsrep … language bodies in SysML and KerML are checked, and a SysML constraint body is evaluated.Bodies in other languages, such as Python, OCL or MATLAB, are kept as text and never run.
SysML v2 JSON exchangeImport and export of the Systems Modeling API element format, with element ids kept.Element kinds Holarch does not interpret are kept as imported and written back unchanged; they have no text and cannot be edited.

Kept, not interpreted: No problems proves nothing here

  • Bodies of textual representations in languages other than SysML and KerML.
  • The values of user-defined metadata other than semantic metadata.
  • doc text and comments: never compared with the model. In the EO-1 power subsystem, changing requirement 3.1 to 30 W leaves its doc saying 28 W, with no problem reported. A good exercise.
  • Element kinds Holarch does not interpret in an imported SysML v2 JSON file.

The reverse also matters: requirement status, verification results and labels are Holarch data. They are not in the text and not in a .sysml export.

Not yet in Holarch

  • .kerml files: not imported, and models written in KerML are not checked. KerML is read for the standard library only.
  • Language extensions other than user-defined keywords; the standard library cannot be edited.
  • A solver for analysis cases, and a search for valid variant combinations in Holarch's pages.
  • Systems Modeling API commits to main, tags and merges: other tools commit into change request branches, and an approver applies them in Holarch.

How to use this in a course

  • Say "the tool checked" only for the checked areas. For example, No problems means the units are consistent and the requirements hold for the current values. It does not mean the doc text matches the values or that a Python body is right.
  • Assess the kept constructs by reading them. Grade them by inspection, not by the problem count.
  • Behavior runs in the Simulator for both action flows and state machines. The durations and probabilities the Simulator uses are Holarch settings: if students hand in only the .sysml file, ask for the settings too.
  • Language rules come from the specification, not from any tool. Where Holarch has not implemented something, say "not yet in Holarch", not "not allowed".
  • The A6 bonus builds on this note: students change 3.1 to 30 W in the EO-1 power subsystem, see the evaluation check report it, fix the design, and write down what was checked and what was only kept.

Downloads

The package is one zip file. It carries the version in its name, so a course can point to exactly the copy it used. The assignments' CSV and project files are the EO-1 Reference Model v1.1 downloads on the EO-1 page.

FileWhat it holds
teaching-with-holarch-v1.0.zipAll the files below in one folder.
README.txtThe contents, how to use the package, the license notice and the change history.
LICENSE.txtThe license notice.
learning-outcomes.mdThe course learning outcomes and their mapping to the assignments.
assignments/A1-trace-a-need.mdA1 Trace a need.
assignments/A2-requirements-rework.mdA2 Requirements rework and review.
assignments/A3-coverage-gaps.mdA3 Find the coverage gaps.
assignments/A4-extend-the-architecture.mdA4 Extend the architecture.
assignments/A5-work-the-change.mdA5 Work the change.
assignments/A6-validation-plan.mdA6 Validation plan.
sysml-v2-teaching-boundaries.mdTeaching SysML v2 with Holarch: what it checks and what it only keeps.

The solution notes are not in the zip; see Solution notes.

Versions

This is Teaching with Holarch instructor package v1.0, written for EO-1 Reference Model v1.1. A new version gets new file names; earlier versions stay available at their addresses.

  • v1.0: First release: the course learning outcomes and assignments A1 to A6 with rubrics, for EO-1 Reference Model v1.1.

How to cite

Cite the version you used:

Holarch. Teaching with Holarch: instructor package, version 1.0. https://holarch.app/academic/instructor-package/. Licensed under CC BY 4.0.

License

The instructor package files are licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0). You may copy, share and adapt them for any purpose, including commercially, if you give appropriate credit, link to the license and say whether you made changes. Credit: "Teaching with Holarch instructor package v1.0, Holarch, CC BY 4.0". Each download carries this notice.

The EO-1 Reference Model keeps its own credit line: "EO-1 Reference Model v1.1, Holarch, CC BY 4.0". All names, people and results in EO-1 are invented.

The license covers the package files only. The solution notes are not part of the package, and the Holarch software is not covered by it.

Published by Holarch