Cs230 Tanner Final Flash Cards Set3.2 2015

Front 1

Flow Oriented Modeling

Back 1

• Structured analysis and design• Top-down methodology• Graphical technique depicting information flows and the transformationsthat are applied as data moves from input to output

Front 2

Modeling Tools

Back 2

• Context Diagram• Data flow diagram• Entity-relationship diagram• Control-flow diagram• State-transition diagram• Data dictionary• Process specification (PSPEC)• Control Specification (CSPEC)

Front 3

Steps

Back 3

• Develop Context Diagram -- diagram 0• Decompose the Process into high level processes• In Parallel– Develop Data Flow Diagram(s)– Develop Entity-Relationship Diagram– Develop State-Transition Diagram• Define data stores– normalization• Develop Data Dictionary• Finalize DFD, ER, STD• Develop Process Specifications– PDL, Decision Tables or Trees• Perform Transformational Analysis– Develop Structure Charts

Front 4

Data Flow Diagrams

Back 4

• Hierarchically structured• each level in the hierarchy shows increased detail– each level continues the same inputs/outputs as previous level Classical Analysis Modeling 2Copyright © C. Tanner 2014• data dictionary is used to document the data flowing– leaves diagrams less cluttered• do not show control: iteration or selection• each level of the diagram must fit on one page

Front 5

Usage Rules

Back 5

• a data flow is either output or input but not both• if 2 data flows exist between two nodes (either process bubbles, externalentities, or data stores) the data flowing must be different• must be a transformation (process bubble) between nodes• each process must have both input and output

Front 6

Reading a Data Flow Diagram

Back 6

• Start in upper left hand corner with lowest numbered process and moveto right• follow the output then the input to next in numbered sequence• continue until entire diagram has been traveled

Front 7

Building the Data Flow Diagram

Back 7

• Provides an indication of how data is transformed as it moves throughthe system• Depicts the functions and sub-functions that transform data• Start with the context diagram• Decompose the system into 5-7 sub-processes• Level 0 diagram depicts the 5-7 sub-process and the data stores used bythe sub processes• Check for consistency with the context diagram• Each sub-process is then decomposed into sub-functions which are thendiagramed• For each process bubble on any diagram there is an accompanyingPSPEC depicting detailed logic

Front 8

Steps in Developing a Data Flow Diagram

Back 8

• establish conceptual view– identify the outputs and their sinks– identify the inputs and their sources• define top level processes– 5-7 sub functions– where data is transformed - not stored• diagram each top level process• define data stores• build single diagram -- level 0

Front 9

Defining the Top Level Processes

Back 9

• determine the events that drive the system– examine each external entity and ask what effects their actions haveon the system– examine each event and determine if all instances of the event involvethe same data– event lists must include normal and abnormal processingConsistency Checking with the Context Diagram– each input flow is needed by the system to recognize that an eventhas occurred, or is needed to produce a response to an event– each output flow is the response to an event– each non temporal event should have input from which the system candetect that the event has occurred (control events)

Front 10

Data Modeling 1

Back 10

• Describe the logical, not physical makeup of the data• Database– Collection of related information which can be implemented using standard filetechniques or a Database Management System• Describe the associations between the entities and a strategic overviewof data– Specify the data objects, their attributes, and the relationships between them• Entity– Thing that exists and is distinguishable– Anything we store data about– Real world objects with common properties

Front 11

Data Modeling 2

Back 11

• Instance– Particular occurrence in an entity– Videos • “Office Space”• Relationship between entities– Connection between entities– Example customer-video • Rents– Cardinality • Indicates # of instances in one class which can be associated with instances in another• One-one, one-many, many-many– Modality • Association between instances is mandatory or optional– Attributes • Defines the properties of an entity– Key -- unique identifier– Descriptive– Referential – used to tie one entity with another

Front 12

Entity Relationship Diagram

Back 12

• Graphical representation of the data model• Full blown diagram shows entities, relationships, and attributes• Ours will only show entities, relationships. Attributes will be shown onWarnier-Orr diagram.• Diagramming symbols• Entity -- Labeled rectangle• Relationship – arc connecting two entities– Cardinality – labeled at both ends of the relationship arc– Modality – labeled at both ends of the relationship arc

Front 13

Constructing E-R diagrams

Back 13

• Iteratively– During elicitation ask customers to list “things” the applications addresses • Things may evolve into external entities, actors, or data objects– Taking each object individually determine if it is related to any other object– Create relationship pairs • Diagram the relationship, cardinality, and modality• Handle any many-many relationships• Build a single diagram from refined relationship pairs

Front 14

Warnier-Orr diagrams

Back 14

• Method of representing hierarchical information• Decomposition diagram– Horizontal rather than vertical• Contains constructs for sequence, iteration and selection• Brackets depict subordination– Functional breakdown of item at the head of the bracket– Sequence – top to bottom– Iteration – (n), (1,n), (0,1), (0,n)– Selection • + mutual inclusion – one or other or both• mutual exclusion – one or other but not both