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.
Use cases are sometimes formally defined, true. Often they're not. In
an agile environment, if you're doing it right, the use cases should
be clear from the user story and acceptance criteria.
Without a use case, a feature is useless. If nobody can come up with a
use case for something, probably it shouldn't be documented or exposed
to the customer.
On Tue, Feb 3, 2015 at 10:11 AM, Mike Starr <mike -at- writestarr -dot- com> wrote:
> Many development processes are based on use cases... the use cases are
> developed before coding is started and guide the programmers in how the
> software should enable the user to use it. The product manager must provide
> you access to the use cases in order for you to develop documentation based
> on them.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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
