Abstract

During validation of software requirements and specifications, the use of accessible notations and techniques is vital to stakeholder involvement. A commonly used notation for system specification is the use case notation. Use cases specify system behavior in terms of interactions between external users and the system. Typically, interactions imply dependencies among constituent steps; however, use cases do not provide any means for clarifying intra- and inter‐use case dependencies. This entry presents a state-based approach (and associated tool support) to dependency analysis in use case specifications.