Learn about Data Flow Diagrams (DFDs), Context-level DFDs, and Rigorous Physical Process Models (RPPM), what they are, why they are important, and who can use them.
Use Data Flow Diagrams to Visualize Workflows
An old Chinese proverb says, “A picture is worth a thousand words.” In the world of Information Technology (IT), we maintain that it may even be worth a whole lot more. For most people, it is difficult or impossible to envision a process flow, especially when someone else is describing it.
Understanding current workflows, however, is critical to defining a future IT solution. Just as critical is understanding how data is created and consumed throughout the workflow.
To truly understand problems inherent in a business process or workflow, you need to help the practitioners visualize what they do. Visualization lets them identify better ways of working that remove current restrictions.
Data Flow Diagrams are phenomenal tools for visualization. Working with business experts, you can help them identify problems and inefficiencies they don’t even know they have. These are not people problems; they are process problems. Understanding when and how to create and use Data Flow Diagrams will help you discover and capture the requirements for improving the use of information technology.
Why Should You Take this Course?
In this 90 minute video course, you will learn the benefits of process visualization for the business community, for the one wearing the BA hat, for those tasked with developing the solution, and ultimately for the entire organization.
You will also discover how DFDs are powerful tools for recognizing and eliminating two of the major problems that haunt IT projects, namely Scope Creep and Project Overruns caused by late project change requests.
“Data Flow Diagrams – Simply Put!” uses a concrete business scenario to present a simple, easy-to-learn approach for creating and using Data Flow Diagrams depicting workflow and data manipulation from interviews with Subject Matter Experts.
You will learn how to create a Context-Level Data Flow Diagram and explode relevant process(es) to reveal the nitty-gritty detail (i.e., individual process and data specifications) that developers need to create IT solutions that the business community needs.
This course answers the following questions:
- What is a Data Flow Diagram (DFD)?
- What is a Rigorous Physical Process Model?
- What is a Context-Level DFD?
- Why should I use Data Flow Diagrams?
- What symbols can I use on each type of diagram?
- How can I drill down into a process?
- How can I show internal processes and flows that produce the results?
- What does balancing a Data Flow Diagram mean and what is the business value?
- What is the most efficient approach to balancing a DFD?
- What business value do process specifications offer?
- How can I express detailed specifications for processes and data?
- What is “metadata" and why do you need it?
- What does a fully balanced DFD look like?
- What value does a DFD fragment provide?
Regardless of your job title or role, if you are tasked with communicating a workflow or functional requirements to others, this course is for you.
View Course Outline with Lesson Previews
Anyone involved in Business Process Modeling or Workflow Analysis, including (but not limited to):
- Subject Matter Experts (SME)
- Agile Product Owners
- Business Process Managers
- Business Process Users
- Project Leaders and Managers
- Business Analysts
- Business Architects
- Systems Analysts
- Software Testers
- User liaison personnel
- and anyone wearing the BA hat
Upon completion of this course, you can:
- Document existing business processes and workflows in Data Flow Diagrams (DFD) to initiate business process analysis
- Defend the need for Data Flow Diagrams, Context Diagrams, and Rigorous Physical Process Models
- Use the right symbols for each type of diagram to ensure a common interpretation by all parties
- Explode a high level Data Flow Diagram to its lower level details to reveal underlying processes and procedures
- Balance DFD’s to identify missing processes and reduce late project change requests
- Use Horizontal Balancing to discover missing data and minimize redundancies
- Document process specifications for functional primitives to guide the solution providers
- Express metadata to reveal informational details that developers need to build the solution