A use case is a sequence of actions that provide a measurable value to an actor. Another way to look at it is a use case describes a way in which a real-world actor interacts with the system. In a system use case you include high-level implementation decisions. System use cases can be written in both an informal manner and a formal manner. Techniques for identifying use cases are discussed as well as how to remain agile when writing use cases.
Informal System Use Cases
Introduction to System Use Cases
I update this blog when i am in the development mode, most of the times when I am developing systems, and i find new things that I believe are interesting, I post them on this blog, this helps me a lot too for future references and when i repeat the things i've already done. Hope this helps others too.
Wednesday, October 12, 2005
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2005
(24)
-
▼
October
(10)
- How would you initialize the child class from the ...
- a great article on the inheritence in c#. This art...
- Have you ever wanted to strip all of the HTML tags...
- How to fix bugs in the Live / Production environme...
- Google Groups : microsoft.public.inetserver.iis
- A use case is a sequence of actions that provide a...
- Building Object Applications: Your Step-By-Step ...
- The Full-Lifecycle Object-Oriented Testing (FLOOT)...
- A fundamental concept of the Unified Modeling Lang...
- Project documentation and analysis is the most imp...
-
▼
October
(10)
No comments:
Post a Comment