I am new to working with use cases but would like to implement them in our shop. Can anyone suggest a way to capture non-functional requirements with use cases so that the use cases can be used directly for testing?
As part of our methodology we capture requirements as follows: Use Case Model, Object Model, System Operations and Non-Functional Requirements.
Those inputs are inputs to Test Case / Test Plan creation. Not so much with the object model, but the other three are leveraged heavily.
Our testing methodology and is a subset of our overall development methodology so the integration is fairly well defined.
I hope that helps.
If it is still clear as mud I would consider taking this offline if you like. I know it has been a while since your original post, but the offer stills stands. Saving Changes...
Leslee Probasco and Dean Leffingwell (Rational) wrote about this exact topic. See their article "Combining Software Requirements Specifications with Use-Case Modeling."
It suggests using traditional requirements documentation for non-functional requirements. Saving Changes...
I am trying to get a handle on this myself. My IT folks are telling me there is no way to effectively test non-functional requirements defined by business.
If this is the case, why does business define these non-functional requirements.
I feel my IT folks are not trying hard enough here.
Any thoughts would be helpful (including a strategy).
