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.
Subject:Re: Requirements in Phases From:Jo Baer <jbaer -at- mailbox1 -dot- tcfbank -dot- com> To:"Charter, Tara M." <Charter -dot- Tara -at- mayo -dot- edu> Date:Fri, 19 May 2000 16:32:16 -0500
HA! How about "The Impossible Dream." Only Phase I of any project is
ever really completed. Future phases are promised, but somehow they
never get done because everyone's busy doing Phase I of the next
project. And so on, and so on...
"Charter, Tara M." wrote:
>
> I'm attempting to create a section in a software requirements spec called
> Future Phases. The development process is iterative. I'm also considering:
>
> Phases of Development
> The 4 Seasons (since there are 4 phases)
> Priority Phases
> Development Process
> Likely Revisions
> Future Revisions
>
