CASE Methodology question
Date: 1995/08/15
Message-ID: <40ou6e$9a7_at_ixnews4.ix.netcom.com>#1/1
Questions on Oracle CASE Methodology....
Hi,
I have couple of questions on defining functions in the CASE tool.
How do you decide which function is a elementary function? Here is an example -
A purchase order contains
Purchase order header information Line items Header Attachments or different type of notes Line item notes - different types Line item accounting information Routing information Approval authority
Here one Purchase order may contain many lineitems.
line item may contain many lineitem atttachments lineitem may contain may charged to many accounts
Purchase header may have many attachments ( header attachments )
Purchase order may be routed to many people
Purchase order may need approval from more than one authority
While defining functions
Should we consider Maintain Purchase order as an elementary function or
Should we split the Maintain Purchase order into number of small
elementary
functions because of the complexity of the functional activities of the
PO
creation process ( meaning each sub function itself is complex enough
to be
identified as an elementary function )
What is the dest mechanism to identify an elementary function or "Draw
the
Boundary" ?
What is the effect of splitting "Maintain PO" into number of elementary
function on the implementation?
One effect that I know of is -
Each elementary function becomes Module in the design phase, so all
the
elementary functions like ( maintain header attachments, maintain
routing
information , maintain accounting information etc... ) will become
screens.
But if I define Maintain PO as one activity - then
Lineitem attachments , routing etc.. will be different blocks.
Could you please give some suggestions on the above problem?
I would like to thank you in advance.. for your help.
Regards ,
Suresh Anantpurkar
anantpur_at_ix.netcom.com Received on Tue Aug 15 1995 - 00:00:00 CEST