Can there be different use case diagrams for the same system with differing levels of complexity?.
My question arises due to the fact that use case diagrams can represent a single system in a complex way (more use cases and different relations with detailed representation of each feature) or in a simple way (just an overview). But as it turns out if a Stakeholderstakeholder who is from a non-IT domain would want to look at the use case diagram, we would want it to be simple and make him understand what the system does on a higher level, whereas when a developer looks at the use case diagram he would want to know about the detailed diagram for developing a feature.
How would such a scenario be handled?