Use Cases
Writing down simple statements is an excellent way to capture and to prioritize performance, hardware, deployment, and usability requirements but is a little lacking for capturing functional ones. Functional requirements describe how the system behaves in response to user and external system input. They tend to be more dynamic and often require more detail in order to clearly understand them. Use cases are a powerful technique for capturing and expressing detailed system behavior. Use cases were first put forward by Ivar Jacobson.[2] Another excellent resource on use cases is the work of Alistair Cockburn.[3]
[2] Ivar Jacobson, Magnus Christerson, Patrik Jonsson and Gunnar Övergaard, Object-Oriented Software Engineering: A Use Case ...
Get Building Web Applications with UML now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
