The Basic SystemWeaver Script Language together with SystemWeaver Contexts can be used to generate information for complex scenarios that the basic script language cannot handle. It provides a means of counting items, following parts backwards in the defined context, and of "merging" different perspectives. You basically build a virtual context tree so that only the information of interest is displayed. The typical use case is to separate needed information from redundant information. 

Example Use Cases for Contexts

The context tags enable you to remove information, such as old versions, other development projects, etc from view. To do this, you 1) build the context tree using different building blocks, and then 2) you define how to navigate through the context. 

Example Meta Model

Example Use Case

From the Architecture, list all E2E Functions in the E2E Function List using the script language and contexts.

Example Solution

<Report>
  <Context name="architectureTop">
    <AddParts owner="main" sid="3EFL" part="archToE2EList" defobj="E2EList"/>
    <AddParts owner="E2EList" sid="3PEN" part="E2EListToE2E" defobj="E2Es"/>
  </Context>
  <ForEachInContext name="architectureTop" group="E2Es">
    <Text>#{Name}</Text>
  </ForEachInContext>
</Report>

What's Next?

Learn how to define a context.