Download
1 / 36
360 likes | 365 Views
This chapter covers various process techniques, including data flow diagrams, decision tables, decision trees, structured English, structure diagrams, matrices, action diagrams, and entity life cycle analysis.
E N D
Chapter 12 ProcessTechniques
Learning Objectives • To describe the mechanics of :- • Data flow diagram • Decision table • Decision tree • Structured English • Structure diagram • Matrices • Action diagram • Entity life cycle
Structure diagrams Structure diagrams and structure definition diagrams allow you to automatically rearrange the layout of the diagram so that containment relationships appear with parents above their children.
A Warnier/Orr diagram is a style of diagram which is extremely useful for describing complex processes (e.g. computer programs, business processes, instructions) and objects (e.g. data structures, documents, parts explosions). Warnier/Orr diagrams are elegant, easy to understand and easy to create. References : http://varatek.com/warnierorr.html
Matrices CRUD (“create”, “read”, “update”, “delete”) matrix maps data to process to action (C or R or U or D). References: http://www.cbu.edu/~dbrandon/CRUD_with_Figures.doc.
Action diagrams An Action Diagram provides a graphical overview of the structural elements of the software in addition to pseudo-code like text. Use an Action Diagram to represent either the high level overview of software structure or the detailed program logic. References : http://blogs.ittoolbox.com/eai/implementation/archives/using-action-diagrams-16414
Action diagrams • Steps:- • Identify the process and data components and their relationships. • Develop the action diagram.
Action diagrams Use the diagram constructs: sequence, repetition, condition, module, and data store, to develop an Action Diagram that represents the structure of the process as identified.
Action diagrams Action Diagrams can be derived from correctly drawn Dependency Diagrams, Data Navigation Diagrams, or Decision Trees. Action Diagrams may be decomposed into program code. Some CASE tools generate program code directly from Action Diagrams.
Entity Life History (ELH) • Method Entity Life History (ELH) analyses the life cycle of the entities in information systems; in this connection it investigates which integrity requirements and successor actions are relevant for each definition of a new entity, the administration of the entity, and the deletion of the entity. ELH is thus used to define the rules and regulations required for the actions with entities (insert, update, delete). • Means of representation is Entity Life Cycle.
Entity life cycle An Entity Life Cycle Diagram is generated for each entity. This diagram illustrates all possible entity states and the (elementary) functions changing the states of the entity
End of Chapter 12 Thank You for Your Attention
