Oracle Designer Tutorial |
Functions are arranged in a hierarchy. A function hierarchy shows the information used by functions, in terms of entities and attributes. Each function in the hierarchy is decomposed until the lowest level functions (called elementary business functions) that comprise it have been identified. It is the elementary functions that become the forms, reports and utilities in the finished system.
You use the Function Hierarchy Diagrammer to decompose functions, define elementary functions and show how functions use data.
The process model showed the process steps for the business carried out by Speedy Pizza. All of the process steps were recorded in the repository as functions, but only some of these functions are suitable for automation (e.g. "Record customer order"). The remaining functions (e.g. "Assemble products in a box") will be implemented as manual processes.
To identify which of the existing functions are to be automated.
If you are prompted to select a default container for the diagram, select TUTORIAL.
The New Diagram dialog box appears.
The DELI 1 SATISFY CUSTOMER ORDER function and its child functions appear.
Hint: You might have to resize the window or use zoom to view the entire function hierarchy.
This new root function can now be used as the parent of functions that already exist on the diagram. To do this, you drag the child functions and drop them onto the root function. It is important when doing this that you position the mouse pointer precisely in the centre of the root function before releasing the mouse button. Otherwise, the moved function will become another root function. The mouse pointer changes shape to help with this.
Releasing the mouse button reparents DELI 1.1 (AUTO) Record Customer Order under the AUTO 1 root function.
DELI 1.3 (AUTO) | Print customer's order |
DELI 10.3 (AUTO) | Record time to transport and payment |
DELI 10.4 (AUTO) | Add new product to the menu |
DELI 10.5 (AUTO) | Publish menu on the Web |
The new function hierarchy for the AUTO 1 module is as follows:
To create working applications, the information used by a function must be identified. This typically involves specifying whether a function can create, retrieve, update or delete an instance of an entity.
To specify how the PRODUCT entity is used by the "Add new product to the menu" and "Publish menu on the Web" functions.
Entity |
Create |
Retrieve |
Update |
Delete |
Archive |
Other |
PRODUCT |
þ |
þ |
þ |
þ |
|
|
PRICED PRODUCT |
þ |
þ |
þ |
þ |
|
|
The usage flags indicate how the function uses the information represented by the entities.
Hint: Use the horizontal scrollbar to see the Delete, Archive and Other usage flags.
Entity |
Create |
Retrieve |
Update |
Delete |
Archive |
Other |
PRODUCT |
|
þ |
|
|
|
|
PRICED PRODUCT |
|
þ |
|
|
|
|
Having specified the entities used by a business function, and how those entities are used, you specify how the function uses the attibutes of those entities, including whether a function can:
You can use the Function/Attribute Matrix utility to create usages for all attributes of the entities used by a function.
To create attribute usages for the "Add new product to the menu" and "Publish menu on the Web" functions.
This displays the Create Function/Attribute Matrix dialog box.
DELI 10.4 (AUTO) Add new product to the menu
DELI 10.5 (AUTO) Publish menu on the Web
The Create Function/Attribute dialog box closes and the attribute usages are created.
To confirm that the attribute usages have been created, open the Edit Function dialog box for the functions (see previous section) and view the Attribute Usages tab. For each entity used by the function, the attributes will be listed and the usages shown by completed check boxes. If you scroll across to the Comments column, you will see "Created by system on <date>".
In this lesson you identified which functions should be automated and created entity and attribute usages.
|
|