Structured Scenarios in documentation

[m0nal1sa]

Why do none of the Structured Specifications come out in the documentation? Neither rtf or html. Is there a different method to exporting this out?

[AndyJ]

I am seeing the same problem.

Structured scenarios are not exporting in version 8.0.856

Has anyone raised a bug on this yet?

[AndyJ]

I hate to answer my own question, but...

...I've raised a registered user support request on this.

[Eve]

For RTF generation it depends on your template.  There are at least two templates provided by Sparx Systems that do generate it and of course you can add it to your own templates.

For HTML generation, it isn't done in the current version, but will be available soon.

[m0nal1sa]

I haven't worked out which RTF reports do contain the structured scenarios, however I have created my own template.

A big problem for me is that there is does not seem to be a field for the Entry Points or Joins for the alternate/exception paths. Thus the report shows steps 1 - n for alternate/exception paths, but not where they come in from the basic path. Or am I missing something?

cheers

[AndyJ]

The Use Case and Use Case Scenario templates pick up the structured scenarios...

In Use Case Scenario template an alternative flow is flagged within the basic flow.

In the use case that I'm working on at the moment, it looks like this:

7. The System displays a method to identify Location as Licensed Premises., Uses: Location

---> Exception 7a Licensed Premises

However, in the body of the document, this alternative flow is presented above the basic flow, which is a little counter-intuitive.

The use case scenarios template is a good place to look.

Andy.

[m0nal1sa]

I don't see that on the default Use Case templates. I get the text on the Description subtab of the Scenarios tab, but not the Structured Specification subtab text.

Editing my own template, I can get the text shown below. But as you can see, each scenario starts at step 1. It doesn't show that exception 'No records found' is at step 3a, or the alternate path 'User does not have Workgroup role' is at step 2a.
 

Type: Basic Path. Name: Basic Path
Structured Steps:
1. User. On Jobs > Outage tab, click Add. Result: Search Outages form launched
2. System. Prepopulate default filter values based on Job. Result: From and To dates match Job dates
3. System. Search database for matching records. Result: Matching records displayed in Search Results grid
4. User. Select one or more records. Result: Selected rows highlighted
5. User. Click Add. Result: Selected records are added to the Job and Search Outages form closed

Type: Alternate. Name: Change search parameters
Structured Steps:
1. User. Enter alternate search filters
2. User. Click Search

Type: Alternate. Name: User does not have Workgroup role
Structured Steps:
1. System. User has Workgroup role. Result: My Workgroups checkbox = true

Type: Exception Name: No records found
Structured Steps:
1. System. If no results found, display message "No matching results"

Any and all advice appreciated.
cheers
Naomi

[AndyJ]

Hmmm...

When you created the alternate flows, did you use the button with a yellow symbol above a symbol that looks like the symbol on a USB connector? If you hover over that button, the pop-up text reads: Add alternate path...

Step 7a does not appear in the basic flow list, but I added that alternate flow with step 7 highlighted.

In the bottom half of the Structure Specification tab, the alternate flow appears with an entry point defined as 7a.

I've also set that alternative flow to Join the basic flow at step 8.

Are you seeing something similar?

I'm working on modifying the Use Case Scenarios template, as that's a better starting point for me so far. That's the template that is showing the insertion point.

Andy.

[AndyJ]

I've had a look at the template and think you are probably missing:

exception>
        Exception Step   Exception Name
<exception

[AndyJ]

I'm looking in a copy of the Use Case Scenarios template, and suspect that you need to include the following selections in your template:



Andy