Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
78:process_architecture [2022/01/31 12:38] – sph78:process_architecture [2022/04/12 20:06] – emr
Line 73: Line 73:
 In the image below, “Program A” needs to have interfaces with “Component A1 Hardware” and “Component A2 Software”, but not “Component B1 Hardware”, “Component B2 Software”, or “Component B3 Software”, even if the same process modules are integrated there. In the image below, “Program A” needs to have interfaces with “Component A1 Hardware” and “Component A2 Software”, but not “Component B1 Hardware”, “Component B2 Software”, or “Component B3 Software”, even if the same process modules are integrated there.
  
-[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=7dd61d&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/multilevelprogram.png|{{https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/multilevelprogram.png?direct&800x381}}]]The above structure can be correctly instantiated **by using workspaces collections** to control the creation of interfaces. By creating workspace collections depicted by the colored dots in the image above, the interfaces will be correctly created, because **all workspaces within all collections of the current workspace** are being searched for interface candidates. The interface search uses internal identifiers instead of just names, which makes it very robust and allows the workspaces to have arbitrary names.+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=7dd61d&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/multilevelprogram.png|{{https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/multilevelprogram.png?direct&800x381}}]] 
 + 
 +The above structure can be correctly instantiated **by using workspaces collections** to control the creation of interfaces. By creating workspace collections depicted by the colored dots in the image above, the interfaces will be correctly created, because **all workspaces within all collections of the current workspace** are being searched for interface candidates. The interface search uses internal identifiers instead of just names, which makes it very robust and allows the workspaces to have arbitrary names.
  
 In addition, this allows the same process module to be integrated into different workspaces with different tailorings. For example, the “Component B2 Software” and “Component B3 Software” workspaces can have the same software development process module integrated but might have different tailorings or even different versions of the same module, and it will correctly interface with its parent “Program B” workspace. In addition, this allows the same process module to be integrated into different workspaces with different tailorings. For example, the “Component B2 Software” and “Component B3 Software” workspaces can have the same software development process module integrated but might have different tailorings or even different versions of the same module, and it will correctly interface with its parent “Program B” workspace.