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.
>John Rosberg said:
>>John Posada wrote:
>>>Jim Barrow said:
>>>
>>>At the moment I'm putting together a brief memo that details the
>>>importance 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?
>>
>>I totally agree that you need business requirements on your A2 project.
>>Not so sure about the legacy app unless you plan on doing some new
>>development for it.
>
>I don't consider Busness Requirements (BR) as important as Functional
>Requirements (FS), except to write the FS, and if whoever is writing the FS
>thinks they don't need the BR, maybe they do and maybe they don't. It could
>be that the person writing the FS knows that business and its requirements
>very well. Once you have the FS, you are writing about the application that
>conforms to those requrements.
Doesn't this depend on the audience? Developers really don't care about
'why' an application needs to be developed. Maybe thorough developers would
read business requirements to get an idea of what stakeholders had in mind
when they sat down and first brain-stormed, but I think they would only want
to know 'how' an application is expected to function.
Business units (stakeholders), on the other hand, want to see this same
information one level higher. They don't want to read how the A2 app does
what it does, they want to know why they've invested their resources in the
first place i.e., "The IT department needs to send and receive files
electronically").
The functional requirement of this would be "The A1 system will provide FTP
functionality..."
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-
