Moors: requirements management

Specification levels, a document structure with section numbers, traceability links, coverage, a matrix, suspect links, draft and published baselines, review, approval and Excel/PDF/Word/Markdown specification exports.

Moors is MyWay’s requirements management board (introduced in v1.74.0, extended in v1.76.0 and v1.85.0). A requirement is a task on this board: its permanent ID (like REQ-42), workflow (In Review and Approved statuses with an approval lock), fields, the parent hierarchy that builds the document structure, history and Excel/CSV exchange all come from the task screen; the approval chain and formal review are for baselines. Two things are specific to Moors: a structure that reads the specification like a document (the Specification view and section numbers), and a traceability layer that ties a requirement to the need above it, the development work that satisfies it and the test that verifies it (link types, a coverage report, a matrix, suspect links, baselines with version codes). One Moors board is one specification; development and test work stays on its own Kanban or Scrum boards and links run across boards.

app.themyway.app/boards/brake-requirements/list
A Moors board: List is the main view with the Section column first (heading numbering such as 2-1, 2-2.1); under the "Approved 3 · +9 subtasks" header, Headings, Information and requirements in the document treeA Moors board: List is the main view with the Section column first (heading numbering such as 2-1, 2-2.1); under the "Approved 3 · +9 subtasks" header, Headings, Information and requirements in the document tree
A Moors board: List is the main view with the Section column first (heading numbering such as 2-1, 2-2.1); under the "Approved 3 · +9 subtasks" header, Headings, Information and requirements in the document tree

Creating a Moors board

In the new board dialog opened from the "+" in the sidebar, pick the "Moors (Requirements)" card. With the card picked, a "Level" field appears: Stakeholder needs, System requirements, Subsystem requirements, Software requirements, Hardware requirements, Interface requirements, Verification / test definitions or Other (System requirements by default). The level can be changed later under Board Settings > General > "Specification level". The preview on the right of the dialog shows the board name, colour and first task key. Creating boards is reserved for workspace admins. A new Moors board comes with the setup below; all of it consists of ordinary records that can be changed in Board Settings:

WhatComes with the board
WorkflowDraft, In Review, Approved, Implemented, Verified, Rejected. "Editing is locked for tasks in this status" is on for Approved: changing an approved requirement needs "Edit tasks in a locked status" or moving the status back
Level (board setting)The level picked in the new board dialog. On a stakeholder needs board Coverage does not look for a source; on other levels every requirement is expected to link to a higher-level requirement
Issue typesRequirement, Heading and Information. Heading and Information build the document structure and do not count as requirements; neither can be deleted, both can be renamed. The built-in Epic, Story, Task and Bug types are not set up. A Verification / test definitions board is set up with Test Case and Test Step instead of Requirement; a board whose level is later changed to verification gets these types added, and Test Step cannot be deleted (v1.104.0)
Attributes (custom fields)Source (text: the customer document, standard or stakeholder the requirement comes from), Verification Method (Test, Analysis, Inspection, Demonstration), Rationale (multi-line text), Acceptance Criteria (multi-line text), Requirement Class (Functional, Performance, Interface, Safety, Security, Design Constraint, Environmental, Usability, Regulatory), Criticality (High, Medium, Low)
Built-in fieldsPriority and Story Point come switched off (Criticality takes the place of priority on Moors); they are not deleted and can be switched on under Board Settings > Task Screen > Fixed fields
ViewsList (the main view), Kanban and Specification in the top bar; Coverage, Baselines, Matrix and Releases under "More" (v1.104.0). There are no sprints, backlog or planning, and sprint permissions do not appear in the role settings
  • Status, type and attribute names come in the interface language (Turkish or English) of the person who creates the board
  • No labels are set up on a Moors board; built-in labels such as Bug or Feature mean nothing on a requirement
  • The setup above comes when the workflow template in the new board dialog is "Requirements" (the default). With the "Simple" template the Moors statuses are not set up; when the board is created by taking settings from another board, the workflow, fields, issue types and the on/off state of Priority and Story Point are copied from that board and the Moors setup is not added. When the source is a Moors board, Heading and Information work as document structure just as on the source and cannot be deleted; numbering comes from the source, and the level is the one picked in the dialog
  • When the source is a board or a template, "Copy items with their relations" also brings the item tree, order, parent-child relations, descriptions, custom fields and links between items; numbering starts at 1 with the new short code and items open in the new board’s start status. Comments, attachments, baselines, assignees, sprints and links to other boards are not copied (v1.85.0). If the source has more items than the copy limit under Settings > System limits (5000 by default), the board is not created
  • An existing board can be switched to Moors under Board Settings > General. The switch adds the Requirement, Heading and Information types and any missing requirement attributes (Source, Verification Method, Rationale, Acceptance Criteria, Requirement Class, Criticality); an unset level becomes System requirements (v1.77.0) and numbering becomes heading numbering (v1.80.0). The existing workflow, types and fields are kept: the Moors statuses above are not added, and Priority and Story Point are not switched off. Every task except Heading and Information counts as a requirement, including tasks of the built-in Epic, Story, Task and Bug types. The Rejected status is not recognized: rejected tasks are counted in coverage and the matrix
  • Moors boards created before v1.76.0 keep working with the types they were set up with (Stakeholder Need, System Requirement, Subsystem Requirement, Software Requirement, Interface Requirement). On a board with no level set, Coverage recognises the top level by the Stakeholder Need type and rejected requirements by the Rejected status. Recognition goes by record ID: renaming does not break it, deleting and recreating under the same name does; for that reason the Stakeholder Need type cannot be deleted
app.themyway.app/boards/platform
The new board dialog: the Moors card picked, the Level select under Setup and a live preview on the rightThe new board dialog: the Moors card picked, the Level select under Setup and a live preview on the right
The new board dialog: the Moors card picked, the Level select under Setup and a live preview on the right

Levels and document structure

Levels (stakeholder need, system, subsystem, software...) are separate Moors boards: stakeholder needs on an STK board and system requirements on a REQ board, say. A lower-level requirement links to a requirement on the board above with "derived from" or "refines". The structure inside a board is the document structure: requirements, Heading and Information items are nested with "Parent task". A child requirement allocated from a system requirement can also sit under it on the same board. The "parent of / child of" link cannot be picked on a Moors board; existing links of that kind are kept and shown.

Specification and section numbers

The Specification tab flows the board’s items in reading order like a document: Headings as headings with their section number, requirements with their section number, permanent key, title, status, description and attributes, and Information items as unnumbered paragraphs. The order comes from the hierarchy and the order set by hand; items never moved sit at the end of their siblings in the numeric order of their key. Each item’s menu offers "Add above", "Add below" and "Add inside" for a Heading, Requirement or Information, and "Move up", "Move down", "Indent" and "Outdent" to move it. "Add at end" in the toolbar opens a menu to pick Heading, Requirement or Information and adds the item at the end of the document (v1.88.0). So you can put an explanation between two headings or bring a section forward; Information needs no separate link and belongs where it sits (v1.80.0). Adding an item needs both "Create tasks" and "Manage subtasks"; moving and indenting need "Manage subtasks". Numbers are not stored and are recalculated on every change; Information takes no number and does not advance the counter. The permanent key (REQ-12) never changes. Clicking an item opens it in a side panel. The view shows up to 5000 items. Requirement and Information text is justified, and left-aligned on narrow screens (v1.94.0).

app.themyway.app/boards/brake-requirements/specification
The menu of REQ-005 open in the Specification: "Add above", "Add below" and "Add inside" with Heading, Requirement or Information; "Move up", "Move down", "Indent", "Outdent"The menu of REQ-005 open in the Specification: "Add above", "Add below" and "Add inside" with Heading, Requirement or Information; "Move up", "Move down", "Indent", "Outdent"
The menu of REQ-005 open in the Specification: "Add above", "Add below" and "Add inside" with Heading, Requirement or Information; "Move up", "Move down", "Indent", "Outdent"
  • The source picker at the start of the toolbar shows the current state ("Current state (draft, after 1.0)"; with no baseline yet "Current state (draft 0.0)") or any baseline. A baseline is read-only: "Viewing baseline 1.0 · SRR · Published (read-only). Switch back to the current state to edit." is shown, "Add at end" and item menus are hidden, and statuses show as they were in the baseline. Clicking an item opens the task as it is today (v1.86.0)
  • "Search the specification" searches the key, title and description but does not filter the document: matching items are marked in the document, the match count shows inside the search box ("3 matches", "no matches"), and typing switches the navigation pane to the Results tab. To see only the matches with the headings above them, tick "Show only matches in the document" on the Results tab; then "No items match the search" appears in the document when nothing matches (v1.87.0)
  • A row with items under it collapses with the arrow to the left of its title; "Collapse all" and "Expand all" apply to every row. The choice is personal and remembered in the browser per board; collapsing is ignored while searching or filtering, and "Collapse all" and "Expand all" become inactive (v1.86.0)
  • The toolbar sticks to the top of the screen and stays in place as the document scrolls; while searching or filtering its buttons do not disappear, they only become inactive. The status line under it holds the version shown (e.g. "1.1 · Draft (current state)"), the collapse notice ("2 items are collapsed; the items under them are hidden." with "Expand all") and, past 5000 items, "Showing the first 5000 of 5230 items." The document is shown as a page set off from the background (v1.88.0)
  • "Export" downloads the source selected on screen as Excel, PDF, Word or Markdown; the panel says what it will download (e.g. "Exports: 1.0 · SRR · Published") and lets you choose what goes into the document (table below, v1.89.0). Search, collapsing and the navigation pane filters do not affect the output (v1.85.0; the on-screen source since v1.86.0)
  • The button at the start of the toolbar ("Open the navigation pane" / "Close the navigation pane") opens the Navigation pane to the left of the specification; it is open the first time, and the choice is remembered in the browser (v1.87.0)
  • The Headings tab is the document’s heading tree; with "Show all items" ticked, requirements (with their keys) and Information items join the tree. Clicking a row scrolls the document to that item, opens collapsed headings above it and briefly highlights it. If you have the permission and the current state is shown, the row menu has the same add and move commands as the document
  • Headings in the tree collapse one by one with the arrow, or with "Collapse all" and "Expand all" in the pane; when a heading is collapsed, "2 headings collapsed in the pane." appears with an "Expand all" link. Collapsing in the pane is separate from the document and remembered per board (v1.89.0, v1.91.0)
  • The Results tab lists the search matches with section number, key and title; when the match is in the description, a short snippet with the matching word highlighted shows too. With an empty search it reads "Type in the search box above; matching items are listed here."
  • Under Filters, Kind (Heading, Requirement, Information) and Status (the statuses in the shown source) are separate groups; the number of active filters shows in the header and "Clear filters" removes them all. A filter narrows both the tree and the document, keeping the headings above a matching item for context (v1.87.0, v1.91.0)
  • Drag the pane edge to resize it between 220 and 560 pixels; double-click resets it, and the width is remembered in the browser (v1.89.0)

Exporting the specification

app.themyway.app/boards/brake-requirements/specification
The published 1.0 selected as the source and the export panel open: section numbers, items to include, keys, MyWay links, descriptions, type and status, attributes; Excel, PDF or WordThe published 1.0 selected as the source and the export panel open: section numbers, items to include, keys, MyWay links, descriptions, type and status, attributes; Excel, PDF or Word
The published 1.0 selected as the source and the export panel open: section numbers, items to include, keys, MyWay links, descriptions, type and status, attributes; Excel, PDF or Word
OptionWhat it does
Section numbersOn all items (default), Headings only, Requirements only or None. Items left without a number lose their section number in the output; the option does not renumber, numbers stay as in the document
Items to includeHeading, Requirement, Information; all three ticked by default and at least one stays ticked. Without headings there is no table of contents in PDF and Word. If nothing is left, "No items match the options" appears
Write item keys (like MYW-12)On by default. Turned off, the requirement line has no [REQ-12] and Excel has no Key column
Link requirements to their MyWay recordOff by default. Turned on, every requirement links to its record at the MyWay address the export was made from: in PDF the requirement line, and in Word the key (or the title when keys are off), becomes clickable, and Excel gets a Link column at the end. Headings and Information are not linked
DescriptionsOn by default; turned off, descriptions are left out and Excel has no Description column
Type and statusOn by default; turned off, the item type and status are left out, and Excel has no Type or Status column
Justify textOn by default. In PDF and Word the body text is justified and the last line of a paragraph stays left-aligned; headings, item keys and the attribute table are unchanged. It does not affect Excel (v1.94.0)
Attributes (custom fields)On by default; turned off, fields such as Source and Verification Method and the attribute columns in Excel are left out
Remembering choicesChoices are remembered in the browser and come back on the next export, on other boards too; "Back to default options" resets them (v1.89.0)
OutputContents
PDFCover page: "Requirements specification", the board name, Version (code and baseline name, e.g. 1.0 · SRR; for the current state only the next draft code, e.g. 1.1 when 1.0 is published), Status (Draft or Published) and Date (the day the baseline was taken, today for the current state). If the board has baselines, the cover carries a Revision history table: Version, Name, Date, Status (Draft, Published or "Published as 1.0"), oldest first. Then Contents: every heading with its page number, clickable. Then the body in reading order, indented by depth: a Heading with its section number and title; on a requirement line the section number and [key] are bold and the requirement text is normal (v1.92.0), followed by type and status, description and filled attributes; Information as an unnumbered paragraph in normal weight. Every page except the cover shows the board name, version, status and date at the top and the generation time and "Page 3 / 12" at the bottom. The font is Arimo, metrically identical to Arial (v1.87.0)
WordThe cover matches the PDF. Contents is a Word table of contents field: headings are listed on first open, page numbers come in when Word updates the field; the field takes the first three heading levels. The body uses real heading styles, which Word’s navigation pane works from; attributes sit in a two-column table. The header has the board name, version, status and date, the footer the generation time and page number. The font is Arial (v1.87.0)
ExcelA single sheet named after the board and version code; no cover, revision history or contents. Columns Section, Key, Title (indented by depth), Type, Status, Description, one column per attribute that has a value, and Link when linking is on; a column the options leave empty is not written
MarkdownOne file in reading order with the heading structure; the options apply as in PDF and Word (v1.104.0).
Corporate templateThe docs space’s "Export" and "Confidentiality levels" sections are also under Board Settings > General on Moors ("Board configuration" permission). With "Corporate template" selected, PDF and Word print in the same layout as document pages: letterhead logo, margins, a cover (document code, version, publication date, confidentiality, submitted by, reviewed by, approved by), contents, and the chosen footer fields plus the submitter, reviewers and approvers. With the standard layout the output is as above; Markdown is not affected by the template (v1.104.0).
AllThe file name is the board name and version code (e.g. Brake-Requirements-1.0.pdf). Markdown in descriptions becomes plain text, option fields print their display name (v1.86.0), and empty attributes are skipped. The revision history lists the baselines taken up to that version: exporting an older version leaves out the ones taken after it. For the current state the file name and the cover carry the next draft code (1.1 when 1.0 is published) (v1.94.0). For baselines taken before v1.85.0 the reading order is rebuilt from the hierarchy; the manual order was not recorded in those snapshots, so siblings fall back to key order

Board Settings > General > "Numbering" offers two formats: "Headings get the section number; requirements are numbered after their heading (1.2-1)" or "Headings and requirements share one numbering (1.2)". With heading numbering, adding a requirement does not shift the numbers of sub-headings; a requirement under a requirement continues with a dot (1.2-1.1), and on a board with headings, requirements outside any heading get 0-1, 0-2. New boards and boards switched to Moors start with heading numbering; boards created before v1.80.0 keep the shared numbering and can switch in the setting. Baselines keep the number from the time they were taken. Whoever has "Board configuration" changes it.

  • In the list view the "Section" column comes first. With no sort chosen, and when sorted by "Section", the list follows the order of the specification, and child items are sorted at every level (v1.80.0). The column filters by prefix ("Section no., e.g. 2 or 2.1"): "2" brings section 2 and everything under it, "2.1" only that subtree. Saved filter results can be sorted by Section too
  • Heading and Information are not requirements: coverage, the matrix and suspect links leave them out; they are included in a baseline
  • On a Moors board the list export starts with the Section column
  • A row with tasks under it collapses with the arrow in front of it ("Collapse subtasks" / "Show subtasks"); the choice is personal and remembered in the browser per board (v1.86.0)
  • Rows with items under them close or open in one go with "Collapse all" and "Expand all" on the toolbar; while any row is collapsed, "3 rows are collapsed; their subtasks are hidden." appears above the list with an "Expand all" button (v1.87.0)
  • With one or more items selected in the list, "Move up", "Move down", "Indent" and "Outdent" appear under "More" in the bulk action bar; items move by the Specification rule, counting siblings that are not on the current page. The selection moves together and keeps its order, and an item whose parent is also selected moves with its parent. If none can move, "This item cannot be moved that way." appears; if some cannot, "2 items could not move that way and were skipped" (v1.86.0; several items since v1.88.0)
  • With a single item selected, the same menu has "Add above", "Add below" and "Add inside" to add a Heading, Requirement or Information item; the permissions are the same as in the Specification, Create tasks and Manage subtasks (v1.91.0)
app.themyway.app/boards/brake-requirements/specification
Specification: the Navigation pane (Headings tree) on the left; in the document, headings with section numbers (1, 2, 3), requirements numbered after their heading (2-1, 2-2, 2-2.1) with key, status and attributes, and the scope text as an unnumbered Information paragraph; at the top the sticky toolbar (source picker, search, "Add at end", "Collapse all", "Export") and the status line with the versionSpecification: the Navigation pane (Headings tree) on the left; in the document, headings with section numbers (1, 2, 3), requirements numbered after their heading (2-1, 2-2, 2-2.1) with key, status and attributes, and the scope text as an unnumbered Information paragraph; at the top the sticky toolbar (source picker, search, "Add at end", "Collapse all", "Export") and the status line with the version
Specification: the Navigation pane (Headings tree) on the left; in the document, headings with section numbers (1, 2, 3), requirements numbered after their heading (2-1, 2-2, 2-2.1) with key, status and attributes, and the scope text as an unnumbered Information paragraph; at the top the sticky toolbar (source picker, search, "Add at end", "Collapse all", "Export") and the status line with the version

Four traceability link types tie a requirement to the outside. Each type can be picked in either direction; when adding a link the dialog spells out the chosen direction in a sentence ("The item you pick becomes the SOURCE of REQ-4 (REQ-4 is derived from it)"), and the linked items list shows the task’s short code before its title.

LinkReverseMeaning and effect on coverage
derivesderived fromThe source item derives the target (need → system requirement). The target counts as "sourced"
refinesrefined byThe source item refines the target. The refining item counts as "sourced"
satisfiessatisfied byA design or development task satisfies the requirement. The requirement counts as "implemented"
verifiesverified byA test verifies the requirement. The requirement counts as "verified"
  • A parent requirement on the same board gives a source; a Heading or Information parent does not (that is document structure). Existing cross-board "parent of" links still count as a source. Text typed into the Source attribute does NOT count toward coverage: coverage looks at links and hierarchy
  • General-purpose links (relates to, blocks, duplicates, causes) do not count toward coverage
  • Adding a link needs "Edit tasks (fields, attachments, links)" on the board of the item it is added from, and membership of the other board. A link can be removed from either end; removing needs the same permission on the board of the item you remove it from
  • Links can also be added while creating a task (the Linked Items section), or for many selected tasks at once with "Add link" in the bulk action bar
  • You can search by link conditions: "Link" (type and direction, e.g. verifies / verified by; "none (no links at all)"), "Linked item" (e.g. REQ-12), "Suspect link" and "Subtask". They can be saved in a filter too (see Filters)

Coverage

The Coverage tab (in the "More" menu) gives the traceability state of the board’s requirements on one screen. The cards at the top show the number of requirements and three shares: sourced, implemented (satisfied) and verified, next to the number of requirements with a suspect link. Filters list the gaps in one click: No source, Not implemented, Not verified and Suspect link; "All" clears the filter. The table shows whether each requirement has a source, the items that satisfy and verify it (by short code), its suspect link count and its number of child requirements. The list is paged 50 rows at a time. The search and filters in the top bar (labels, assignee, status, custom field chips, advanced search) narrow the requirement set with the same rule as the List, and the shares at the top are calculated for the filtered set. Columns can be sorted, resized and filtered from their header (e.g. "Has a source" / "Unsourced", "Satisfied" / "Not satisfied", "Has suspect links", "Has child requirements"); "Clear column filters" removes them all. Hovering the icon in the Source column explains what it means.

  • On a stakeholder needs board every requirement is the top level: no source is expected, the table says "Root" and it is left out of the sourced share. On a board with no level set (from before v1.76.0) the rule applies to the Stakeholder Need type
  • On a Verification / test definitions board the Source column becomes "Verifies": it shows whether each test definition verifies a requirement through a "verifies" link; the cards read "Test definitions" and "Linked to a requirement", and the column filter offers "Linked to a requirement" / "Unlinked" (v1.80.0)
  • Requirements in the Rejected status and Heading and Information items are left out of coverage entirely
  • Linked items on boards you cannot access are not shown, only counted as "+N hidden"
  • Clicking an item in a row opens the task in a side panel on the same screen, with its own board’s fields and rules; it does not open if you are not allowed to see it
  • A "Traceability coverage" card can be added to a dashboard: it shows the three shares of a chosen Moors board as bars
app.themyway.app/boards/brake-requirements/coverage
Coverage: 8 requirements, 88 percent sourced; the unsourced new requirement shows a warning icon and REQ-011 has 3 suspect linksCoverage: 8 requirements, 88 percent sourced; the unsourced new requirement shows a warning icon and REQ-011 has 3 suspect links
Coverage: 8 requirements, 88 percent sourced; the unsourced new requirement shows a warning icon and REQ-011 has 3 suspect links

Matrix

On the Matrix tab (in the "More" menu), rows are the board’s requirements and columns are the items of the board chosen under "Target board" (a test or design board, say) that link to these requirements. Each cell shows the initial of the link type (D derives, S satisfies, V verifies, R refines, P parent of, for existing links). The list is paged; the search and filters in the top bar narrow only the rows (requirements), while the columns and unlinked items still follow all requirements. Requirements in the Rejected status and Heading and Information items are left out of the matrix. The matrix shows up to 150 columns and the unlinked list up to 200 items; only boards you can access can be chosen as the target board. The "Unlinked items" button lists the items on the target board that link to none of this board’s requirements: that is how you find tests that verify nothing.

app.themyway.app/boards/brake-requirements/matrix
Matrix: requirements in rows, the tests of the target board Brake Verification in columns; "Unlinked items (1)" points at the test that verifies nothingMatrix: requirements in rows, the tests of the target board Brake Verification in columns; "Unlinked items (1)" points at the test that verifies nothing
Matrix: requirements in rows, the tests of the target board Brake Verification in columns; "Unlinked items (1)" points at the test that verifies nothing

When one of the tracked fields of a requirement on a Moors board changes, the traceability links touching that requirement (derives, satisfies, verifies, refines) are marked "Suspect". A badge appears on both ends of the link, and its hint says what changed. The link is not invalidated automatically; the decision stays with a person: whoever reviews the link clears the mark with "Reviewed", and a "reviewed a suspect link" entry is written to the task history. Reviewing needs "Edit tasks (fields, attachments, links)" on the board of whichever end you review it from.

  • Tracked fields are chosen under Board Settings > General > "Fields tracked for suspect links". The default rule is title, description and the requirement attributes (fields whose key starts with req-, including ones added later). "Selected fields" narrows the list and "Back to default" brings the rule back; with no field selected, no link on the board is marked suspect. The list is changed by whoever has "Board configuration: fields, issue types, versions, templates, calendar". Title, description and custom fields can be tracked; a status change does not mark a link suspect
  • A change to a Heading or Information item marks no link suspect; those are not requirements
  • Parent/child links and general-purpose links are never marked suspect
  • A user without "View others’ tasks" sees only the items they can see in the Specification, Coverage, Matrix and in baseline snapshots and comparisons; section numbers do not change because they are computed from the whole document (v1.106.0)
  • On a verification board a Test Step appears numbered under its test case and goes into baselines, but Coverage, the matrix and suspect links count only the test case. The Specification add menu shows the board’s type names and offers Test Step on this board (v1.104.0)
  • On the Coverage tab, the "Suspect link" filter lists requirements with a link not yet reviewed; the "Suspect link" search condition does the same
app.themyway.app/boards/brake-requirements/tasks/REQ-011
REQ-011, whose description changed after the baseline: its "derived from" link to STK-001 is suspect, and "Reviewed" clears the markREQ-011, whose description changed after the baseline: its "derived from" link to STK-001 is suspect, and "Reviewed" clears the mark
REQ-011, whose description changed after the baseline: its "derived from" link to STK-001 is suspect, and "Reviewed" clears the mark

Baselines

On the Baselines tab (in the "More" menu), "New baseline" stores the current state of every item on the board and its links, unchangeably: a name ("SRR approval", say), an optional description, who created it and when, and a version code. Codes follow the version logic of the docs space (v1.85.0): a board with no baseline is draft 0.0, "New baseline" always takes a draft minor version (0.1, 0.2; after a publication 1.1, 1.2), and a major version (1.0, 2.0) is only created by "Publish". "Draft version code" in the form shows the code it will get; above the list, "Board version" shows the board’s highest code with a "Draft" or "Published" badge. Codes are unique per board and never change. The snapshot carries each item’s title, description, status, type, parent requirement, section number and reading order at that moment, its attributes (req- fields and any other fields tracked for suspect links), plus its traceability and parent/child links. A baseline cannot be taken while the board has no items; it holds up to 5000 items (Heading and Information included), and on a larger board it cannot be created. The search in the top bar narrows the Contents and Comparison rows by key or title.

  • Comparison: the selected baseline is compared with the "Current state" or with another baseline. The numbers of added, removed and changed requirements and of link changes sit at the top; below, each changed requirement shows which field changed from what to what; a section number change shows as a field change too
  • The Contents tab lists the items in the baseline. Contents and comparison download as Excel, CSV or Markdown; the file name starts with the version code
  • Creating, publishing and deleting a baseline needs the "Board configuration: fields, issue types, versions, templates, calendar" permission; reading one only needs board membership. These appear in the audit log as "Baseline created", "Baseline published" and "Baseline deleted"
  • The list is grouped by publication: a published version (e.g. 3.0) comes first with the drafts that led to it (2.1, 2.2) in a collapsible group below ("2 drafts"); unpublished drafts sit on top under "Unpublished drafts". Since a publication’s review and approval happen on its source draft, selecting the publication shows that draft’s review and approval ("3.0 was published from draft 2.2...") (v1.94.0)
  • When taking a baseline you enter a document code and a confidentiality level (from the board’s list); left empty, they come from the previous baseline, and a publication takes them from its draft. If the board uses the corporate template both are required and printed in the export footer; on an unpublished draft they can be changed with "Edit name and description" (v1.104.0)
  • An unpublished draft’s name and description are changed with "Edit name and description"; an open review or approval does not prevent it. A published version and the draft it was published from do not change. It needs "Board configuration" and is written to the audit log as "Baseline draft renamed" (v1.95.0)

From draft to publication

  1. 1Take a draft with "New baseline" (the first draft is 0.1) or use "Review the current state": the current state is frozen as a new draft named "Review draft" and the review dialog opens for it. If the latest draft is identical to the current state no new copy is taken and the dialog opens for that draft (v1.86.0)
  2. 2On the draft, collect feedback with "Start Review" and, if needed, get an approval with "Request Approval". Both open only on the board’s latest draft; on a published version, a published draft or a superseded draft the reason is shown instead of the button, e.g. "A newer draft exists (0.3); reviews and approvals only happen on the latest draft."
  3. 3If the board changed after the selected draft was taken, a warning appears: review and approval apply to that snapshot, and a new draft is taken from the current state to review the latest content
  4. 4When the draft is ready, "Publish" (shown only on the latest draft) asks "Publish as 1.0?". The publication records the draft’s snapshot as 1.0 with the same name and description; it publishes the draft, not the current state. The draft stays as it is and shows "Published as 1.0" in the list; its review is stamped "Published as 1.0" and its approval is marked with the published version. The next draft is 1.1 and its publication 2.0
  • Publishing is refused when the draft is not the latest one ("Only the latest draft baseline can be published."), when the draft has an open review or a pending approval, or when a condition of the publishing rule is missing ("The draft’s review must be completed before the baseline is published.", "The draft must be approved before the baseline is published.")
  • The publishing rule sits under Board Settings > General > "Publishing rule": "A completed review is required" (on by default) and "An approval is required" (off by default). A review or an approval backs a single publication. Whoever has "Board configuration" changes the rule; a board created by taking settings from this board takes the rule too
  • The rule has the same meaning and defaults as the publishing rule of a docs space, but it is each Moors board’s own setting; a docs space’s rule does not affect a Moors board. One difference: in a docs space "Order" only appears when both boxes are ticked, while on Moors "Review and approval order for baselines" is a separate section that applies regardless of the boxes
  • Baselines taken before v1.85.0 keep their codes. Codes ending in zero (1.0, 2.0) now count as published versions, show the "Published" badge and cannot get a new review or approval; if the board’s highest code is one of them, take a new draft first (1.1 after 1.0). The publishing rule comes with its defaults on existing Moors boards too: "Publish" needs a completed review
app.themyway.app/boards/brake-requirements/baselines
The published 1.0 SRR compared with the current state: REQ-012 added, the status of REQ-009 and the description of REQ-011 changed; a published version takes no review or approval, and draft 0.1 shows "Published as 1.0" in the listThe published 1.0 SRR compared with the current state: REQ-012 added, the status of REQ-009 and the description of REQ-011 changed; a published version takes no review or approval, and draft 0.1 shows "Published as 1.0" in the list
The published 1.0 SRR compared with the current state: REQ-012 added, the status of REQ-009 and the description of REQ-011 changed; a published version takes no review or approval, and draft 0.1 shows "Published as 1.0" in the list

Reviewing and approving a baseline

Two panels sit under the selected baseline: Approvals and Review. "Start Review" sends the baseline to a multi-round formal review like documents: you choose what to look at, a due date and the participants, feedback is written with a severity (Critical, Major, Minor, Editorial) and the presenter decides on each item. Feedback is written on the whole baseline or tied to a single requirement by picking "REQ-12 · title" in the quote box. The flow, report and decisions are the same as a document review (see Formal review). A review can only be opened on the board’s latest draft baseline (v1.86.1). Starting a review needs board membership and the "Request approval" permission.

  • Approval: approval, too, can only be requested on the latest draft. "Request Approval" sends the baseline through the same chain as document approval (serial or parallel approvers, the approval queue, notifications). The approval notification opens the baseline directly. On a Moors board, the request and decide approval permissions appear in the role settings. Decisions are made on the baseline opened from the approval notification, or in the "Approval Queue" tab of any docs space; the queue lists the person’s pending decisions across all boards, and a baseline row shows the type "Baseline". A pending request is cancelled by its requester or by someone with "Manage members and roles"
  • Order: the order of review and approval is chosen under Board Settings > General > "Review and approval order for baselines": Parallel (the default, the two are independent), "Review first, then approval" (approval can only be requested once a review is complete) or "Approval first, then review" (a review can only start once an approval has been given). Whoever has "Board configuration" changes it
  • A baseline with a pending approval or with a review (ongoing or completed, not cancelled) cannot be deleted; an approved baseline can never be deleted, since it is the record of what the approval accepted. A version created by "Publish" (1.0, 2.0) and the draft it was published from can never be deleted, since they are the record of the publication: the delete button is inactive and its hint reads "Publication records cannot be deleted" (v1.87.0). An unpublished baseline with no review (or only a cancelled one) whose approval was rejected or never requested can be deleted
app.themyway.app/boards/brake-requirements/baselines/1.1
Draft 1.1 PDR in review (collecting feedback, round 1): the Critical, Major and Minor feedback items are each tied to one requirement; "Publish" in the header and "Board version 1.1 Draft" at the topDraft 1.1 PDR in review (collecting feedback, round 1): the Critical, Major and Minor feedback items are each tied to one requirement; "Publish" in the header and "Board version 1.1 Draft" at the top
Draft 1.1 PDR in review (collecting feedback, round 1): the Critical, Major and Minor feedback items are each tied to one requirement; "Publish" in the header and "Board version 1.1 Draft" at the top

Moors supports a process; it does not produce a certificate of conformity to a standard. It makes it easier to build the traceability that a standard such as ISO/IEC/IEEE 29148, ISO 26262 or DO-178C asks for, but it does not replace a conformity assessment. There is no ReqIF exchange or direct import from DOORS; requirements are imported and exported with Excel or CSV (see Import & export). For an end-to-end setup see the Tracing a requirement to its test scenario.