Home

Home is where a project opens. The top shows what needs attention and where each lifecycle group stands. Below that, two lanes of panels show the work and status you follow: the next actions, the current SE Process gate, model check findings, requirement quality, verification, risks, milestones, the changes since the last baseline, open discussions, saved views, breakdown charts, notes and an AI project brief.

Every panel reads the model directly, so it updates as soon as anyone changes the items it shows. The panel layout is saved in the project: every member sees the same Home, and every change to it can be undone.

Concepts

• Header: the project name (in the top bar) and the first line of the project description, with Edit description.
• Needs attention: health cards that count problems: suspect links, overdue TBDsTo Be Determined A requirement value or detail that is not known yet. Holarch tracks TBDs with an owner and a due date., failing tests, TPMTechnical Performance Measure A key technical parameter, such as mass or power, tracked over time against its target and threshold. breaches, high risks, model checks and the save status. See Getting Started.
• Lifecycle: one card per rail group with its main number.
• Lane: a column of panels. The main lane takes about two thirds of the width, the side lane the rest. In a narrow window the side lane moves below the main lane.
• Panel: one box in a lane with a name, a ⋯ menu and its content. A panel is short (up to about 300 px high, then it scrolls) or tall (up to about 600 px).
• Single panels: most panels show one thing for the whole project and can be on Home once: Next actions, My Work, SE Process gate, Model checks, Requirement quality, Verification, Risks, Milestones, Changes since baseline, Open discussions, Project brief and Recent work. Saved view, Breakdown, Note, Pinned item and Gallery can be added as often as you need.
• Default panels: a new project gets panels that fit its stage. Early on (the first half of the SE Process phases, or no project baseline yet): Next actions, SE Process gate and Requirement quality in the main lane; Recent work, Milestones, Open discussions and Project brief in the side lane. Later: Next actions, Verification and Changes since baseline; Recent work, Risks, Milestones and Project brief.

How to use it

When and why

Use Home at the start of each working session and before reviews. Needs attention tells you what is broken; the panels show what you chose to follow.

• During requirements work: SE Process gate for the phase checks, Requirement quality for the weakest statements, and a Breakdown of requirement status.
• Before a review such as SRRSystem Requirements Review A milestone review that confirms the system requirements are complete and agreed before design starts. or PDRPreliminary Design Review A milestone review that confirms the preliminary design meets the requirements and is ready for detailed design.: Milestones for the review date, Open discussions for the comments still open, Changes since baseline for what changed since the last review, and a Project brief to start the review summary.
• During integration and test: Verification, a Breakdown of test case status and Model checks.
• For a class or a new team: SE Process gate walks everyone through the phase checks of the chosen process.

Arrange the panels

1. Click + Add panel at the end of the main or the side lane. (Or choose Home ▾ → Add Panel…, which adds to the main lane.)

   A menu lists the panels that are not on Home yet.

2. Click a panel.

   Most panels appear at the end of the lane at once. Saved view, Pinned item and Gallery first open a short form; fill it in and click Add Panel.

3. Drag the panel by its head to another place, in the same lane or the other one.

   A line shows where it will land. The layout saves when you release the mouse.

4. To change a panel, click ⋯ on its head:
   • Configure… opens its form (only panels with settings have it).
   • Rename… sets its name. Double-clicking the name renames it in place: Enter saves, Esc cancels. An empty name brings back the panel's own name.
   • Make Tall or Make Short changes its height.
   • Move Up, Move Down and Move to Side Lane (or Move to Main Lane) move it.
   • Export… downloads its content (only panels with exports have it).
   • Remove from Home removes it at once. The toast offers Undo.

Move panels with the keyboard

1. Tab to the panel (a focus ring shows around it), or click its head.
2. Press Alt+↑ or Alt+↓ to move it up or down in its lane.
3. Press Alt+→ to move it to the side lane, or Alt+← to move it to the main lane.

   The panel keeps the focus after each move.

Follow a query with a Saved view

1. Click + Add panel and choose Saved view.
2. Under Saved query, choose a query saved in the Database, or keep A query typed here and enter a Query (Database search), for example class:Risk.

   The number of matching items shows under the field as you type.

3. Set Show as to Count, List or Table, the Order (Last changed first, Newest first, Number or Name) and the number of Rows (1 to 50).
4. Click Add Panel.

   Open in Database at the bottom runs the same query in the Database. Export… → Table (CSV) downloads every matching item.

Count items with a Breakdown

1. Click + Add panel and choose Breakdown.

   A new Breakdown counts requirements by Status when the schema has that attribute, else items by class.

2. Choose ⋯ → Configure… and pick Count by: Class, Label or one enumeration attribute under Attribute (listed as Class: Attribute).
3. Click Save.

   With up to 6 values the panel draws a ring with the total in the middle; with more it draws horizontal bars. Point at a slice or bar to see its count; a class or label slice opens the Database filtered to it.

4. To use the chart elsewhere, choose ⋯ → Export… → Chart (SVG) or Chart (PNG). The PNG has a white background unless you tick Transparent background.

Write a project brief

1. Choose ✦ AI ▾ → Write Project Brief in the top bar, or click Write Brief in the Project brief panel.

   Holarch sends the AI the project summary, the changes since the latest project baseline (or the items changed in the last 30 days), the problems from the health checks (high risks, failing tests, breached measures, overdue TBDTo Be Determined A requirement value or detail that is not known yet. Holarch tracks TBDs with an owner and a due date./TBRTo Be Reviewed A requirement value that is filled in but still needs to be confirmed. items, suspect links, model check errors) and the current SE Process phase.

2. Read the brief in the preview. It has three parts: Changes, At risk and Next, with links to the items it names.
3. Click Keep on Home to store it in the Project brief panel (one undo step), or Close to discard it.

   The panel shows when the brief was written, by which model, and what it was written from. Write Again replaces it after a new preview.

Edit the project description

1. Click Edit description next to the description line (or Add a description when there is none), or choose Home ▾ → Edit Description….
2. Edit the text in the rich-text editor and click Save.

   The first line shows under the top bar. The description is the same as in Project Preferences….

Worked example: a review board for the CubeSat EO-1 demo

The CubeSat EO-1 demo opens with Next actions, Requirement Status and Test Case Status breakdowns, Verification, a Functional Flow pinned diagram, Milestones with the launch date first, a Model Walkthrough process gate, Open discussions, Recent work and Project brief. Prepare it for a design review:

1. Open the demo project. Home opens.
2. Click + Add panel at the end of the main lane and choose Saved view.
3. Enter class:Risk as the query, set Show as to Table and Rows to 10, and click Add Panel.

   The table lists RK-1 Reaction Wheel Failure, RK-3 Launch Slip and the other risks.

4. Double-click the new panel's name, type Risk Register and press Enter.
5. Drag the panel above Verification.
6. Choose ✦ AI ▾ → Write Project Brief, read the preview and click Keep on Home.
7. Before the review, choose ⋯ → Export… → Table (CSV) on the risk table to attach it to the review package.

Tips and good practice

• One question per panel. A Breakdown of requirement status and a Saved view of Draft requirements read faster than one crowded table.
• Name panels after the question, for example Unverified requirements.
• Keep the side lane short: milestones, discussions and recent work fit there; tables and charts need the main lane.
• Save a project baseline at each review. Changes since baseline and the brief then show what changed since that review.
• Use attribute tests in queries, such as Requirement:"Status=Draft". The panel's Order decides the order.

Common mistakes

• "Nothing to count by class. Choose what to count with ⋯ → Configure…." The Breakdown has no items to count. Choose another Count by.
• "No project baseline yet. Save one on Version Control to count the changes after it." Changes since baseline needs a project-wide baseline. Until then it lists the recently changed items.
• A panel does not move when dragged. Drag it by its head, not by its content, or use Alt+arrow keys.
• The brief is out of date. A brief is written once, on request. Click Write Again after larger changes.

How it connects

• Health and next actions: Next actions uses the same counts as Needs attention, the rail badges and the problems button.
• SE Process: SE Process gate shows the current phase of the SE Process guide, its open checks and the gate milestone and review package.
• Model and Database: Saved view and the Changes since baseline filter use the query syntax of the Database.
• Version Control: Changes since baseline compares the latest project baseline with the current model, as Compare does; Compare on Version Control opens the full comparison.
• Verification and risks: Verification uses the same rows as the RVTM; Risks uses the Risk Register and the project risk scale (Risk and Decisions).
• Export: the panel layout travels with a project export when Include Project Preferences is on (see Import and Export).

The Home page

Top bar

Reset Home… asks "Replace the panels with the default set for the project's stage? Undo brings the current panels back." Reset replaces every panel.

Panel head

Panels

Dashboards from earlier versions

A project saved with the earlier widget dashboard opens with its widgets converted to panels, in reading order. Widgets in the right third of the old grid go to the side lane; widgets 10 rows high or more become tall panels. A widget's own title becomes the panel's name.

A notice above the lanes says how many widgets became panels and names those that were not carried over. Keep these panels saves the converted layout; Use the default panels replaces it with the default set. The old layout stays in the project until it is deleted with the project.

Saving, undo and roles

• Every change to Home (add, move, resize, rename, settings, remove, reset, a kept brief) is one undo step. Press ⌘Z / Ctrl+Z to undo it.
• The layout is part of the project. All members see the same Home, and a change by one member reaches the others.
• Viewers and Reviewers see the panels but not Home ▾, + Add panel or the editing commands in ⋯.

Messages

Limits

• Two lanes; panels are short or tall.
• Saved view: up to 50 rows; the CSV holds every matching item.
• Project brief: at most 150 changes and 40 high risks go to the AI.
• One Home per project, shared by all members.

Related pages

• Getting Started
• SE Process
• Model and Database
• Verification
• AI