Let's image a new simple CRM, where...
- some external system A uploads new data, CRM saves them
- CRM validates the data and creates eg. new cases from them
- user displays the cases
These requirements relate to systems and external systems, and I have some doubts about whether these qualify as actor or not:
1st possible use-case diagram:
2nd possible use-case diagram:
My question about the borderline between system and actor can be decomposed as follows:
I believe, that the 1st diagram is wrong, because the system shouldn't be an actor. And it should look like the 2nd diagram. Correct?
The use cases "validate data" and "create new cases" will include in the scenario only steps made by the system (System validates number of columns;System validates data types;System validates mandatory values...).The system shouldn't be an "actor entity", however it's not against the rules to have a uc where the system is the only acting part, right? It's just important, that the uc has a relationship to some another uc which is really valuable for some actor. Correct?
Is it correct to show "external system A" as an actor? Executing the usecase should bring a value to the actor... I am not sure, whether system A makes happy to upload the data :) however systems may have a different point of view on what is a "value"
Thank you for your advices!