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 say go right to the business requirements for A2, noting where A1
satisfies them, where it almost satisfies them and where it doesn't address
them at all. You don't need two separate business requirements documents...
A1 is already in place and being used.
Mike Starr WriteStarr Information Services
Technical Writer - Online Help Developer - Website developer
Graphic Designer - Desktop Publisher - MS Office Expert
Phone: (262) 694-1028 - Tollfree: (877) 892-1028 - Fax:(262) 697-6334
Email: mike -at- writestarr -dot- com - Web: http://www.writestarr.com
----- Original Message -----
From: "James Barrow" <vrfour -at- verizon -dot- net>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Sent: Wednesday, April 04, 2007 11:51 PM
Subject: Business Requirements
> Awright kids, this is an invitation to brainstorm for 60 seconds.
> One of my projects at work is documenting the re-platforming of a legacy
> app. The A1 system was developed and used for four years.without any
> documentation at all. No business requirements before the development, no
> functional specs, no technical specs, no user guides.
> The project team for the A2 project has been assembled and were to begin
> development once the business requirements were determined (for both the
> leagcy app and the new app). In fact, there was a lot of emphasis placed
> producing the 'as is' documentation for the legacy app. This is what I
> been working on for a few weeks.
> Today, one of the powers that be sneezed, shifted a brain cell, and
> decided that no documentation was needed for the 'as is' app. In fact, he
> decided that we could skip the business requirements for the A2 app and go
> directly to the functional requirements.
> At the moment I'm putting together a brief memo that details the
> of establishing business requirements before starting the A2 project, and
> establishing at least some business requirements for the legacy app.
> Do you agree? Disagree? Why?
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-