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.
I think you need to redefine what you're looking for, Tony. You're
talking about systems scoping, which is different from project
scoping. But to answer your question in a nutshell, read up on PMI.
On 1/5/06, Tony Markos <ajmarkos -at- yahoo -dot- com> wrote:
> --- Bill Swallow <techcommdood -at- gmail -dot- com> wrote:
>
> I am well aware of what a context diagram is. It's a
> good [system scoping] tool, but not the only one to
> use in proper project scoping
> and estimation.
>
> Tony Markos asks:
>
> Errr, can you name a couple (besides Use Cases (i.e.,
> poor-man data flowing)). The fine folks on the
> requirements engineering listerv were not aware of
> any.
--
Bill Swallow
HATT List Owner
WWP-Users List Owner
42.8162,-73.7736 http://techcommdood.blogspot.com
============================
I support Char James-Tanny for STC Secretary.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-