User Guides

These guides walk you through using MEMO for a real medical device project — from cloning the repo to passing design reviews with complete traceability.

Who is this for?

• Systems engineers starting a new medical device and want model-based traceability from Day 1.
• Software / hardware leads who already have requirements in spreadsheets and need to import them into a SysML v2 model.
• Quality / regulatory engineers who need to demonstrate closure (ISO 14971, IEC 62304) before submission.

New to MEMO?

Start with the Medical Device Quick Start Tutorial — a single end-to-end walkthrough that takes you from cloning the repo to achieving full ISO traceability with your existing data.

Guides

Guide	What you'll learn
Medical Device Tutorial	End-to-end tutorial — import CSV data, build traceability, validate closure
Starting a New Project	Scaffold a project, understand the folder layout, run the dev server
Importing Existing Data	Bring requirements, hazards, and components from CSV into MEMO
Modeling Your Device	Write SysML elements, add relationships, organize by CoSMA layers
Validation & Closure Rules	Run memo validate, read the gap bar, fix traceability gaps
Viewpoints & Diagrams	Switch viewpoints, create diagrams, export for documentation

Typical Workflow

graph LR
    A[Clone MEMO] --> B[memo init my-device]
    B --> C[Import CSV data]
    C --> D[Add relationships in .sysml]
    D --> E[memo-architect dev — visual review]
    E --> F[memo validate — fix gaps]
    F --> G[memo-architect build — static report]

Already have requirements in Excel?

Jump straight to Importing Existing Data — you can generate a CSV template that matches your ontology, paste your data in, and import with a single command.