TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
On Tue, Feb 3, 2015 at 1:48 PM, Robart, Kay <Kay -dot- Robart -at- tea -dot- texas -dot- gov> wrote:
> Well, a use case is sort of task-based, but it shows all the activities that a user wants to perform as well as alternate actions and the behavior of the software.
If they had that sort of formal document, Julie's manager could just
point to it.
Where I've worked, a use case is what one user would want to do with a
particular feature. It's not necessarily written down anywhere, it
might be just a point of discussion in meetings. One place I worked,
they had a fictional set of named users: Angie is a manager and needs
to do A, B, and C, Kevin is a case worker and needs to do C, D, and E,
etc. I think people in that company had too much time on their hands.
Agile user stories are similar, except that in agile the user story
comes first and the developers write the feature to satisfy the
associated acceptance requirements.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word | http://bit.ly/doctohelp2015
