12
« on: March 10, 2017, 02:34:42 am »
Hi Geert,
Unfortunately I am unable to add images to represent what is happening, but will try and explain in textual format (hopefully with more clarity than last time)
The package structure in the Project Browser:
1.Group
1.1 Catalogs
1.1.1 Actors
1.2 Projects
1.2.1 Example Project
1.2.1.1 Use Cases - contains 10 use cases
1.2.1.2 Traceability
I am running a report on package '1.2.1.1 Use Cases'. The report specification is called 'Use Case Specification' and is structured as follows:
package >
diagram >
{Diagram.DiagramImg}
< diagram
element >
{Template - Use Case Actor Names}
[---Contains element attributes---]
scenario >
Scenarios
structured scenarios >
{Scenario_Structured.Step} {Scenario_Structured.Action}
exception >
{Exception.Type}: {Exception.Name} - re-joins the basic path at step {Exception.Join}
< exception {Scenario_Structured.Uses}
< structured scenarios
< scenario
external requirements >
< external requirements
child elements >
< child elements
< element
child packages >
< child packages
< package
The fragment {Template - Use Case Actor Names} is structured as follows:
custom>
{ActorName}
<custom
The fragment has the following query as specified by Geert.
select act.Name AS ActorName, act.Note as [Description-Formatted]
from t_object act
inner join t_connector c on act.Object_ID in (c.Start_Object_ID, c.End_Object_ID)
inner join t_object uc on uc.Object_ID in (c.Start_Object_ID, c.End_Object_ID)
and uc.Object_Type = 'UseCase'
inner join t_diagramobjects uc_do on uc.Object_ID = uc_do.Object_ID
inner join t_diagram d on uc_do.Diagram_ID = d.Diagram_ID
where d.Diagram_ID = #PACKAGEID#
On running the 'Use Case Specification' report on package '1.2.1.1 Use Cases', all use cases are documented, but not the actors associated to the use cases.
I'd even considered creating a virtual document with 2 model documents. 1 model document which reports on the use cases, identifying all actors associated to each use case, removing duplicates and then outputting in a table format recording name and notes. This is what the sql script is trying to resolve. The 2nd model document will just concentrate on documenting the details of each use case.
Hopefully this provides additional clarity (hope so anyway).
Many thanks in advance,
TJ