We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3
CpE CAD Midterm Reviewer 3.
Data can not flow directly from an entity to a
DATA FLOW DIAGRAM - provide a graphical data store – Data Flow from an entity must be representation of the system that aims to be processed by a process before going to the data accessible to computer specialist and store and vice versa. non-specialist users. It describes the 4. Miracle (Spontaneous generation) processes that are involved in a system to 5. Black Hole transfer data from the input to the file 6. Gray Hole storage and reports generation. APPLICATIONS OF DFDS DATA FLOW DIAGRAM ELEMENTS 1. SOFTWARE ENGINEERING - data flow ENTITIES – represented people, organizations, or diagramming provides structure before coding other things that interact with the system, i.e. begins and is one of the most helpful application Entities are “outside of the system,” that is they are architecture diagrams. part of the process, but external to the information 2. AGILE DEVELOPMENT- allows developers to system. better visualize requirements as they build on PROCESSES – are actions that directly change the existing work. data. Whenever an action takes place, a new output 3. BUSINESS ANALYSIS - these diagrams provide a is formed based on that action. Typical processes framework to examine existing system and remove include calculations, data sorting or set of specific inefficiencies. rules that a business may follow LEVELS OF DATA FLOW DIAGRAM DATA FLOW – is the lines with arrows that are used 1. Level 0 Context Diagram to mark where the data flows. As external entities ● 1 Process represent the entire system create processes and interact with data stores, ● High Level I/0 data flow lines map out these input and outputs ● No Data Store DATASTORES - are files or storage areas that 2. Level 1 Overview Diagram contain information that can be called on at a later ● Can Use All 4 Elements (Entities, Data date. They typically appear as database tables or Store, Data Flow, Processes) spreadsheets. ● LIMIT 9-10 PROCESS Like processes, data stores receive simple labels 3. Level 2 explaining their purpose or order. ● BREAKDOWN THE PROCESS. RULES OF DATA FLOW ● ADD MORE DETAILED DATA STORE 1. Data can not flow between two entities – Data flow must be from entity to a process or a process USE CASE DIAGRAM to an entity. There can be multiple data flows Is a behavioral UML diagram type and frequently between one entity and a process used to analyze various systems. 2. Data can not flow between two data stores – Enables you to visualize the different types of roles Data flow must be from data store to process or a in a system and how those roles interact with the process to a data store. Data flow can occur from system. one data store to any many process UML (Unified Modeling Language) RELATIONSHIP RULES Is a standardized modeling language consisting of 1. The 2 or more base use case can included 1 sub an integrated set of diagrams, developed to help use case system and software developers for specifying, 2. Relationship can be only used to main use to sub visualizing, constructing, and documenting the use case artifacts of software systems, as well as for 3. Actors should not be able to access the included business modeling and other non-software systems. or extended use-case USE CASE DIAGRAM ELEMENTS 1. SYSTEM – is used to define the scope of the use PRACTICE QUESTION FOR FILL IN THE BLANKS: case and drawn as a rectangle. This is an optional 1. __________ represent people, element but useful when you’re visualizing large organizations, or other things that interact systems with the system but are external to the 2. ACTOR – Is any entity that performs a role in one information system. given system. This could be a person, organization 2. __________ are actions that directly change or an external system and usually drawn like a the data, such as calculations, data sorting, skeleton. or following specific business rules. 3. USE CASE – Represents a function or an action 3. __________ are lines with arrows used to within the system. It’s drawn as an oval and named mark where data flows as external entities with the function. interact with processes and data stores. 4. COMMUNICATION LINK - Use to show the 4. According to the rule of data flow, data connection of an actor to a use case by a solid line. cannot flow directly between two Actors may be connected to use cases by __________; it must flow from an entity to associations, indicating that the actor and the use a process or from a process to an entity. case communicate 5. Data cannot flow directly from an 5. RELATIONSHIP – Illustrate relationship between __________ to a data store; it must be an actor and use case with a simple line. For processed by a __________ before reaching relationships among use cases, use arrows labeled the data store. either “<<include>>” or “<<Extend>>” : 6. In a Level 0 Context Diagram, there is no *WHEN TO USE <<INCLUDE>>* __________, and only one process 1. The Base use case is INCOMPLETE without the represents the entire system. included use case 7. A Level 1 Overview Diagram can include all 2. The included use case is mandatory process and four elements: __________, __________, not optional __________, and __________. *WHEN TO USE <<EXTEND>>* 8. A __________ represents a situation where 1. The extending use case is usually a conditional data appears to come from nowhere, also process. known as "spontaneous generation." 2. The main use case can work without the extending use case 9. The term __________ is used when data 20. A __________ occurs when a process seems to disappear within a process receives insufficient data to produce the without producing any output. required output. 10. In Agile Development, data flow diagrams 21. In Level 0 Context Diagrams, the entire help developers visualize __________ as system is represented by a __________ they build on existing work. process and does not display internal 11. During Business Analysis, data flow __________. diagrams are used to __________ and 22. Data Flow Diagrams are particularly useful remove inefficiencies from an existing in the __________ phase of Agile system. Development for visualizing and refining 12. In Software Engineering, data flow diagrams system requirements. provide structure before __________ 23. In Business Analysis, one primary purpose begins, helping to map out the system's of using DFDs is to identify and eliminate architecture. __________ in the system. 13. A Level 2 diagram provides a detailed 24. A Level 2 diagram breaks down processes __________ of the process and includes into more __________ components, more specific __________. allowing for greater detail in __________ 14. In a Data Flow Diagram, __________ are and data manipulation. considered to be "outside of the system" 25. Data Flow Diagrams serve as a blueprint for but still interact with its processes. system architecture in __________ before 15. When a process takes place, a new the actual coding phase begins. __________ is formed based on the action 26. The primary goal of using a Level 1 or manipulation of data. Overview Diagram is to provide a clearer 16. Data flow lines in a DFD map out the view of how data __________ between __________ and __________ between entities, data stores, and processes. entities, processes, and data stores. 27. According to the rules of DFD, data must 17. The rule that states data cannot flow flow from a __________ to a process or vice directly between two data stores ensures versa, ensuring structured data movement. that all data must be routed through a 28. During software development, DFDs help __________. manage __________ and reduce the risk of 18. If a DFD contains a __________, it indicates errors in the later stages of coding. a logical error where data appears without a clear source. 19. A __________ is a situation in which input data flows into a process but no output data is generated.
Knight's Microsoft Business Intelligence 24-Hour Trainer: Leveraging Microsoft SQL Server Integration, Analysis, and Reporting Services with Excel and SharePoint