11
« on: June 05, 2018, 08:59:09 am »
Hi All,
a colleague is modelling a system and has asked me if it is possible to make a generic type of Use Case, he has has several system use cases that do a similar thing (following is 3 steps in a basic scenario for the use case):
1 - System A sends request to System B
2 - System B validates request
3 - User gains access System B
This scenario plays out between 3 different systems in an authentication protocol (sort of a proxy oidc authentication), in the first use case, A is a relying party and B is an authentication proxy, in the next use case A is the proxy, and B is the identity provider, same basic path scenario in both, just different source and targets.
Is it possible/wise/appropriate to somehow have a generic (super-class?) Use Case , and have other use cases as sub-classes or implementations of the use case, a-la OO classes?
Or is it better to just clone one to create the other, no inheritance or relationship between them, then change the source and target systems, and some labels (or have some sort of template use case)?
The rationale is that we don't want to create unnecessary objects, and to re-use if possible, or is this idea taking that concept too far (this is a business process model, not a class diagramme)?
I was a bit stumped by this, so I thought I'd throw it to the community.
Cheers.