Re: Business Requirements

[HBacheler -at- aol -dot- com]

Gene,
 
Could not your description be viewed as a 'mission statement' rather than a  
business requirement?
 
How you would implement it would be in a business pla, and a business  
requirements document.
 
It is too high a level.  Each of the topics is a different business  
requirement and has its one (in)finite interpretations.
 
Semantics possibly, but the business requirements get down to the  
nitty-gritty of HOW we describe WHAT we want to do, and WHO is going to do  it.
 
 
 
Harry
(old  grey/gray hair)



************************************** See what's free at http://www.aol.com.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/ for more resources and info.