RE: Business view vs. Functional view - for consideration

["Warner, Thomas" <Thomas.Warner@MW.Boeing.com>]

Teammates,
I too have some confusion about the "functional service" versus the
"business operational" view/scope of the requirements effort.  In SITG we
found that we had to segregate the two and draw a demarcation line to help
us keep the correct view during discussions. This corrected the tendency to
mix the two.

May I suggest that we consider differentiating issues according to these  2
views (as best we can) while applying Garrets ebXML stack.  In that stack,
there seem to be 4 functional pieces and 2 business pieces to the
requirements.  This might help us to stop muddling the views on the issues.


As an added bonus - FYI - Attached is an 1/12/00  Automation Research
Article on XML.
It has some good basic ideas / news for review.  Particularly the caution at
the end.
 <<XML News-004AE.pdf>> 
Tom Warner
Manager, Electronic Commerce Initiatives
Integrated Digital Environment Program
Aircraft and Missiles Systems
The Boeing Company
(T) 314-232-0615
(F) 314-777-1704
e-mail: thomas.warner@boeing.com

XML News-004AE.pdf