In the wake of UML, use cases have become a popular means to capture requirements. But those who do requirements engineering and design at the system level are sceptic about their value, because use case descriptions in their popular form are perceived as inadequate at this level.
Members-Only Content
This content is restricted to members only.
You must be logged in with an active membership to access this page.
Please click the link below to log in. If you do not have an account or your membership is inactive, you may need to register or renew it.