Class Attributes in Use Case Structured Scenarios

[Shapirho]

Hi,

I am kindly asking for advise on how to call class attributes in Use Case Structured Scenarios. I have searched the forums and I could not find anywhere, where this is discussed prior.
Currently I am working on an engagement where use cases are used to define calculation logic for the domain. E.g. Calculating the discount on products based on their category, season, previous performance in sales, etc.

We have a constructed a conceptual model for the domain and the client is keen on calling the identified classes and attributes in use cases. I have advised that use cases are not the best to handle this type of information but this is what they want.

A simple example is the use case (calculate discount adjustment) where class/attributes required for the calculation are
- PRODUCT.TYPE,
- PERIOD.START DATE,
- PERIOD.END DATE,
- previous discount amount,
- SALES.AMOUNT (total for previous reference period),
- Inflation Coefficient.

The client wants to be able to call out these attributes in the structured scenario. At the moment, if I pull in the various classes into the Context Reference, the class is highlighted (blue text that is underlined) but the attribute is not. This inability to have the attributes highlighted means that users are prone to making errors (typos) and I suspect that traceability will not be possible?

I kindly anticipate your response.

[Geert Bellekens]

That is not possible at the moment, but you can send in a feature request if you want Sparx to consider it: https://www.sparxsystems.com/support/forms/feature_request.html

Geert

[Richard Freggi]

I think you are trying to mix use cases with interaction diagrams.
It's much easier and more effective to separate WHAT needs to be done (use case) with HOW it must be done (interaction diagram e.g. sequence diagram)

Mixing apples and oranges can be done, but can be a recipe for trouble

[Shapirho]

That is not possible at the moment, but you can send in a feature request if you want Sparx to consider it: https://www.sparxsystems.com/support/forms/feature_request.html

Geert

Thanks for the advise...

I think you are trying to mix use cases with interaction diagrams.
It's much easier and more effective to separate WHAT needs to be done (use case) with HOW it must be done (interaction diagram e.g. sequence diagram)

Mixing apples and oranges can be done, but can be a recipe for trouble

Noted. You are preaching to the converted on this one.