Skip to end of metadata
Go to start of metadata

Global information

Goal of STR Input

STR Input is used to extract sent requirements from Stakeholder and other systems (Enabling system and requirement) to selected system breakdown by refine. The used format is an Excel and the used view is “2.1. Define requirements”.

Requirements concerned are those descendants of the selected system breakdown with an input refine from a requirement of a stakeholder or another system (Enabling system or Requirement defined as a system). Data are extracted in three sheets "STK to System", "Other systems to system" and "ES to System by refine". The following image shows you exported relation if you select [ELECTRIC DRIVE] Breakdown.


Access to the STR Sys

The result of running the script "STR Input" will constitute the STR Input document.


Go to the Process view.

Enter the box Object Tools.

Once inside, find the Object DEA-ME and double click on it.

Find the script "STR Input" then, right-click on it and click on run.

Prerequisites

You must have created in view “2.1 Define requirements” :

  • "System concept requirement" types under a System breakdown.
  • Refines in input of "System concept requirement"

You must have cleaned requirements view with reporting tool on the following subjects (See Reporting):

  • Duplicated inside and outside the system
  • Linked with refines to bad or no objects
  • Has multiple parents through refine
  • Allocated to multiple function(s), ES(s), or requirement(s) through refine


Expected results

Description of the Result

After running the script, you have to select a "system breakdown" then click on OK. For our example, we have selected "[ELECTRIC DRIVE] Breakdowns".

Details of the Specific columns for sheet :

STK to System :

  • stakeholder : stakeholder emitting requirement
  • stk requirement id : Id of the emitting requirement
  • stk requirement name : name of the emitting requirement
  • stk requirement description : description of the emitting requirement

Other systems to system : 

  • other system : System requirement emitting requirement
  • os requirement id : Id of the emitting requirement
  • os requirement name : name of the emitting requirement
  • os requirement description :  description of the emitting requirement

ES to System by refine :

  • enabling system :  Enabling system emitting requirement
  • es requirement id : Id of the emitting requirement
  • es requirement name : name of the emitting requirement
  • es requirement description : description of the emitting requirement

Common columns  :

  • system : selected system breakdown receiving the requirement
  • requirement id : Id of the refined requirement
  • requirement name : Name of the refined requirement
  • requirement description : Description of the refined requirement

The following result depends on our example above.

STK to System :

Other systems to system :

ES to System by refine :

  • No labels