Holarch

Control & Reviews

Product Line

Features, their rules, and the configurations built from them. A feature is a choice that differs between products; a configuration is one product, a selection of features.

Where to find it

  • In the navigation rail: Control & Reviews → Product Line.
  • The page and the inspector's Product Line group appear once the project has a Feature or a Configuration. Before that, start with ⌘K / Ctrl+K Start a Product Line… or the Feature and Configuration classes in + New.

Main actions

  • Page header: + New Feature (next number F-n), Check Configurations (lists every configuration with Valid or its first problem, and whether it is complete, with its gaps), + New Configuration (CFG-n), and ⋯ (Export CSV: features by configurations with the verdicts; Help).
  • Features (tree grid): Feature, Kind (Mandatory: every configuration that has the parent has it; Optional: chosen per configuration), Children (Any number, Choose one, Choose at least one) and Used by (items whose Applies To names it). Rules show as tags such as “requires F-3”. Set Kind and Children in the inspector (Enter on the row). Row ⋯: Add Child Feature…, Rename, Rules… (Requires and Excludes checklists), Constraint…, Show Items Using It, Delete….
  • Configurations (grid): one column per configuration with its Status (Draft, Released, Retired). Cells are checkboxes, or radio buttons under a Choose one feature; an implied cell is included by a parent or a Mandatory child. The Verdict row shows Valid, Breaks: … or Incomplete: … (the feature rules only). The Completeness row shows completeness at the configuration's Stage and, separately, its verification, for example Complete at CDR · 12/40 verified (point at it for the gaps). Without a Stage it checks that every leaf requirement is verified by an item in it, every connection has both ends in it and every item's parent is in it. Column ⋯: View as This Configuration, Rename…, Effectivity…, Owner… (Team), Baseline CFG-2… (Team), Release Configuration… (Draft), Withdraw Release… and Show Releases (Released; Record Release… for one released before release records existed), Duplicate (selection and values; a Draft named “… (copy)”), Retire or Restore to Draft (a retired configuration's view is read-only), Delete… (to the Trash; Restore brings back its values).
  • Keyboard: Tab moves between the header and the grids and never indents. Features: ↑/↓ rows, ←/→ collapse and expand, Home/End first and last, Enter while naming saves and starts a sibling, on a selected row opens the feature in the inspector; F2 renames, ⌥↑ / Alt+↑/⌥↓ / Alt+↓ re-order (swapping numbers), ⌥⇧→ / Alt+Shift+→/⌥⇧← / Alt+Shift+← indent and outdent, Delete deletes. Configurations: arrow keys move, Space ticks, Enter on a column header opens its menu, Home/End first and last column.

Tips

  • A configuration's effective selection also holds the parents of its features, the Mandatory children of selected features and the Mandatory root features.
  • Release Configuration… (column ⋯, ⌘K / Ctrl+K, or Status → Released in the inspector or Database) is the one way to release a configuration; a copy of a Released configuration (Duplicate, copy and paste, import into a project) starts as Draft, and a change request releases one only when the release is staged in it (see below). It shows the feature rules, revisions, completeness at the chosen Stage and verification; at a level 5 (Production) stage it also lists the configuration's open high risks and hazards, a warning that blocks nothing and needs no reason. A configuration that breaks a rule cannot be released. While it is not complete, enter a Reason (10–2,000 characters) and the Approver: a typed name on the desktop (recorded as entered by name); online, yourself on the Individual plan, or on the Team plan the configuration's Owner or a project owner, who approves the pending release with their password. The release and its release record (stage, completeness, verification, reason, approver and the released definition) are recorded together, and a single Undo takes them all back. Withdraw Release… asks for a reason and keeps the record; release records are never deleted. Several configurations set to Released in the Database each get the dialog in turn; an AI or MCP proposal cannot release one (its review offers Release Configuration…).
  • Release through a change request: in a change request, stage the release with Add Change ▾ → Release a Configuration…, the column ⋯ Release with CR-12…, or Status → Released. The dialog checks completeness (and, at level 5, open high risks and hazards) against the model as the request leaves it, warns when the stage reports less than the last release, and asks for a Reason when incomplete; the request's approvers approve it, and the configuration counts as affected (its Owner approves). Add to CR-12 stages it. Applying the approved request records the release (via CR-12, with the request's approvers) as part of the same change, or lists why not (deleted, retired, already released, breaks a rule, gaps not accepted); the rest still applies. Online, approvals come from the votes, and only the person applying may record the release, within an hour of the approval check.
  • Stages: the Stage list holds the SE Process review gates, or Concept, Preliminary design, Detailed design, Test and Production. Each stage uses a completeness level: 1 parents; 2 also connection ends and requirements satisfied; 3 also requirements verified; 4 also a procedure and a result for each verifying test case; 5 also every result Passed and no open issues. Change a stage's level in ⋯ → Settings… → Stages.
  • Releases on Baselines & Versions lists the release records: Open Released Definition (the released items and their values, read only), Verify (the record is intact and rebuilds exactly from its own snapshot, frozen library items and schema ids, whatever changed since), Compare with Today (also names a library that moved to another release), Export (JSON) and Withdraw…. Completeness is recorded as computed in the browser at release; Holarch online checks the released definition against its digest, not the completeness. A project save cannot remove or change a release record.
  • Model Checks runs the Product line rule set (ProductLine.1–11, 13–16, 18, 19) once the project has a Feature or Configuration: missing terms in Applies To, broken configurations Released configurations with requirements not verified in them (ProductLine.16, at stages from Test on, without a Stage, or without a release record) and gaps not accepted at release (ProductLine.19) are errors; Released configurations without a release record (ProductLine.18), requirements not verified in a configuration (ProductLine.10) and connections with an end missing in a configuration (ProductLine.11) are warnings and name the configurations, marked (Released) when released; unused features, items in no configuration, overlapping serial numbers, revisions in effect together or leaving units without a revision (ProductLine.13–14) and test results without a configuration (ProductLine.15) are warnings. For values of configurations an item is not in (ProductLine.9), Fix → Remove Values removes them, and a single Undo takes it all back.
  • ProductLine.17 (warning) lists test results reused for a configuration with Reuse Result… (Test Center), with their justification, so a reused result is never counted silently.
  • Baselines & Versions → Baseline a Configuration… (Team) records the product line labelled with one configuration (not yet a released-definition record of its verdict, choices and approvals); Compare has Configuration ▾ and Compare with ▾. A change request's Configurations card lists the configurations it changes, and a configuration's Owner must approve it. On app.holarch.app product lines are part of the Individual and Team plans, and baselines per configuration, configuration owners and the configurations a change request changes are part of the Team plan; the project owner's plan decides. Without the plan nothing is deleted and the product line is read-only: the Product Line page, View as ▾ and the fields show it, and the commands that change it are disabled or say why.

Related

Start a Product Line · Applies To · View as Configuration · Effectivity · Model Checks