Interaction Analysis
| last edited by: erin decaprio on Oct 7, 2006 2:20 PM | login/register to edit this page | ||
To complete the information architecture, it is necessary to analyze the interaction of entity types and activities. Activities can be seen to either Create, Read, Update, or Delete (CRUD) at least one entity type. Entity types, in turn, need to be used by at least one activity. At the architectural level, we want to know answers to the following:
Applications
Procedures
InstructionsTo begin the analysis, review the entity type definitions to get a feel for the information being modeled. For each activity, think about the main pieces of information the activity needs to operate properly. In other words, what entity types does this activity create, update, delete, or read. Identify and document each of the entity actions for all remaining activities. If you get stuck, check the details of the activity profile, review the activity flow, and/or check the entity relationship diagram for clues. The analysis is completed by performing an affinity analysis which looks at all interactions identified and suggests clusters of data and activities which should be analyzed together. (See the figure below for an example displaying the entity type/activity interaction.) The results of this analysis helps identify and plan for business applications systems and databases (The Business System Architecture).
|
|||
| last edited by: erin decaprio on Oct 7, 2006 2:20 PM | login/register to edit this page | ||
|
"Ambition is like a frog sitting on a Venus Flytrap. The flytrap can bite and bite, but it won't bother the frog because it only has little tiny plant teeth. But some other stuff could happen and it could be like ambition." - Jack Handey |