Re: Business view vs. Functional view - for consideration

[Mike Rawlins <rawlins@metronet.com>]

Tom,

That is an interesting suggestion.  However, I wonder if all of our team members
are familiar with the Open-edi Reference Model and the BOV, FSV, and other
concepts explained in it.  Even at that, I tend to view almost everything about
the ebXML effort as within the FSV, i.e., the technical layer.  This includes
even the specific set of core components (element names, attributes, re-usable
structures, etc.).   Only the base semantics (independent of presentation or
dictionaries such as X12, EDIFACT, etc.) and the UML models live in the BOV.

Our issue #3 concerning ebXML's scope as encompassing B2B only, or also B2C,
could be considered as having BOV aspects.  It will almost certainly also have
FSV aspects if it is determined that B2C has non-functional requirements unique
to it.

Mike


"Warner, Thomas" wrote:

> 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
>
>   ------------------------------------------------------------------------
>                          Name: XML News-004AE.pdf
>    XML News-004AE.pdf    Type: Acrobat (application/pdf)
>                      Encoding: base64

--
Michael C. Rawlins, Rawlins EDI Consulting
http://www.metronet.com/~rawlins/