Skip to content
Docs

Explore the sample project

Open the pre-populated autonomous ground vehicle sample to see requirements, risks, verification, schedule and trade studies working together.

The fastest way to understand Ngenaire is to see a real program in it. The sample project, an autonomous ground vehicle, is a fully populated project created just for you, so every page shows realistic content instead of an empty state.

Where: Open the sample project on the workspace home · /home

What's inside

  • Requirements — six numbered sections (perception, navigation, safety, connectivity, HMI, cybersecurity) with priorities, statuses and EARS-style wording.
  • Risks — technical, schedule, cost and programmatic risks with likelihood and impact scoring and mitigation plans.
  • Verification — an approved test plan, a test case per requirement, recorded executions (pass, fail and blocked) and requirement-to-test traceability.
  • Schedule — a Gantt plan with dependencies, three-point (PERT) estimates, a milestone, and phases in different states of completion.
  • Trade studies — two Pugh studies: one carried through weight lock, scoring and a recorded decision; one still in draft.
  • ConOps — an approved concept of operations document.
  • Diagrams — a context-level data flow diagram and a UML sequence diagram.
  • Project memory — pinned decisions and constraints that the co-engineer reads for context.

How to open it

  • Right after you sign up, the welcome card on /home offers Open the sample project.
  • If you have no projects yet, the empty project list offers Explore a sample.
  • The Getting started checklist has an Explore the sample project step.

The first time, Ngenaire builds the project in your personal workspace, which takes a few seconds, and then opens its overview. Later clicks reopen the same project. It carries a Sample badge on your home page and in the project switcher.

Good things to try

  1. Read the project brief on the Overview page.
  2. Open Define → Requirements, switch to the Quality tab and run an analysis.
  3. Open Verify → Traceability matrix to follow requirements to their tests, including a failed and a blocked execution.
  4. Press ⌘K, type req-1 and press Enter to open REQ-000001 in its detail sheet.
  5. Press ⌘J and ask the co-engineer to audit the project:
Audit this project. Which requirements are untested, which risks lack a measurable mitigation, and what should I fix first?

It's yours to break

The sample is an ordinary project and you are its owner. Edit anything, delete artifacts, invite a colleague to look at it with you, or delete the whole project from Project settings. If you delete it and want it back, the same buttons build a fresh copy.

AI actions you run in the sample use your credits like anywhere else.

PreviousGetting started checklistGetting startedNext Create your first projectGetting started