Informative list of tasks and dependencies related to mapping and requirement (re)numbering

[elarlang]

Just for your information, what kind of tasks do we.. (I?) have and what are the dependencies between them

• Activities that makes work after reordering easier
  • All content of requirements are in - (soft requirement) later it is annoying to track changes
  • Requirements texts as style finetuned (soft requirement)
  • Levels are defined (especially L1)
  • Levels are changed - required for reordering, that L1 requirements come first
• Prep to keep v4.0.3 to v5.0.BE mapping
  • step 1.1 - Update current mapping tags to include version (v4.0.3 or v5.0.BE [bleeding edge] requirement)
  • step 1.2 - v4.0.3 to v5.0.BE mapping tags are exported to a separate file - precondition for placeholder cleanup.
    • For separate file, Column 1 = current req number, Column 2 = mapping tag.
  • step 1.3 - Current requirement number ("v5.0.BE / bleeding edge req number") is copied/duplicated to last/additional column to keep info on where the requirement was located before reordering / renumbering.
• "Rebuild" the document
  • step 2.1 - Remove empty placeholders for deleted and moved requirements
  • step 2.2 - Reorder requirements into correct order, based on level. Close section gaps.
  • step 2.3 - Renumber everything
• Update mapping to now also include v4.0.3 to v5.0.0 mapping
  • step 3.1 - Update mapping to also include new v5.0.0 numbers
  • step 3.2 - v5.0.0 to v4.0.3 Mapping to a separate file
  • step 3.3 - Provide web-output of mapping to https://asvs.dev
  • step 3.4 - Validate the mapping
• Cleanup
  • step 4.1 - Remove additional column with old requirement number
  • step 4.2 - Remove change label from requirement text

The rest of the document finetuning