Below are notes to accompany the diagram in the pdf file Business high level functions v0.3 .  This document shows the initial grouping and naming of the business use cases that we would like to confirm during the first JAD session.  

Definition of function: the actions and activities assigned to or required or expected of a person.

ZIMS BUSINESS FUNCTION/SUB-FUNCTION DIAGRAM NOTES

 Business Functions:  

Source – from requirements functions and workflow categorizations 
Some names changed – based on use case, workflow and requirements analysis
New functions - based on workflow and requirements analysis

Business Sub-functions:

Source – mainly from sub-functions associated with requirements, or workflow analysis
Some name changes – based on use case, workflow and requirements analysis
New sub-functions - based on workflow and requirements analysis
Names – the objective is to illustrate the business action in the name, either by a verb or noun e.g. Identify an animal or animal identification.

Use Case, Workflow or Requirements References in the boxes:

The references indicate which use case, workflow or requirements covers the sub-function (in whole or in part).  These were derived based on the most relevant cross-references provided/determined for use cases, workflows and requirements.  Generally, workflow or requirements references are included only if no associated use case was found.

The sub-function references are different from the lists of cross references provided for use cases and requirements, which we assume also point to related other components (use cases, workflows or requirements).

Boxes:

Boxes with double lines highlight those sub-functions identified as duplicate use cases (that belong to both Core and Vet functions) in the Discovery Document.  These duplicate functions were included in the Core set.

 Review process:

·        Check names - Review/revise function and sub-function names – to reflect the true business activities.  Names should reflect the action involved (see above under “sub-functions.”

·        Consistency of information levels - Confirm function and sub-function level – based on the significance or summary level of the business activity.  All sub-functions should reflect a consistent level.

·        Ensure correct groupings - Review/modify sub-function organization/relevance – to reflect the true business breakdown of functions i.e. put under the function of which they are a part.

·        Gap analysis - Once sub-functions are validated, examine use case, workflow, requirements or report gaps in the function/sub-function list where they appear i.e. in the original or proposed list.  These would indicate missing use cases.  Missing use cases can also be identified in the boxes with no use case reference.