How to determine the right modeling methods

You can model any part of a system or an interaction with a system. Because of this, you can pick from a number of different modeling techniques to fit the needs of your project. You've already learned about Business Process modeling and Dataflow Diagramming (DFD). You've also probably seen ERDs likely in MIS325. So when do you pick one modeling method over another? Do we have to use them all!?!

First, think about how a system is broken down. If you recall from MIS301, every system is made up of 5 parts: Hardware, Software, Data, Process, and People. When you think about a system this way, you may find that parts of the system you are building are well defined while others are not. e.g. Perhaps you know how the process works but you're unsure what data is specifically captured or by who. In your client projects, we recommend that you choose the modeling method that will help you flush out detail and gain more clarity on parts don't fully understand. See below:

Second, you can decide the extent to which a more concrete or more abstract modeling method would work best for the given situation. Some modeling methods are rigid and strict (e.g. proper DFDs follow rules), while others are less strict. The last method of modeling we'll touch on is "Concept Modeling" which simply follows the 5 sketching rules mentioned in the Day 4 module. Concept modeling only follows the following guidelines: title your model/sketch/prototype, combine simple shapes, express emotion, label nouns, and use arrows to depict relationships between things. Sometimes this method of modeling is more fun for you and your client because you can be very creative when considering how to express ideas/people/data/etc.

In the end, before you model your As-Is or To-Be system or process, be sure to determine what areas need further clarification. Then select the best type of modeling to create a conversation and clarity around that area.

Concept Diagram using 5 simple sketching tips

Follow these basic 5 steps when trying to visualize how stakeholders and a system interact. By doing this, you'll be able to capture a combination of what a business process and DFD both show which is the human interaction with the system but includes both process and data in the form of labeled arrows with simple shapes.

Title your sketch: Don't worry about getting the title right. You can change it later. But getting a title down on the board gets you and everyone else in the room thinking about the problem, ready to break it down, describe, and solve it!
Combine simple shapes: The most elementary shapes can be combined into very recognizable symbols. Everyone noun depicted here is composed of simple boxes, lines, and circles or curves. This is more than enough detail to communicate meaning (and understanding).
Express emotion or state: Simple changes in the lines used for eyebrows or mouths can dramatically change the emotion of a simple "smiley" face. Using a triangle, circle, and a few lines we can illustrate a wide range of physical activity of a person.
Label each noun: Some people learn visually. Some learn audibly. When we label our pictures we cater to both and remove ambiguity. These images are easier to identify because they are all labeled.
Arrows demonstrate relationships: Connecting your nouns using arrows creates visual sentences. A connection might show steps in a process or even cause and effect. Once you have a simple, rough concept diagram, you can use that to inform to the creation of other models like web flows or ERDs. You can also clean up in Visio to improve readability before sharing with others.

* - These tips are part of a Mark Kraemer's Sketching 101 guide.

Additional Resources and Examples:

System Architecture - How to analyze and model it
Data Process Modeling: Context Diagrams & Data Flow Diagrams (DFDs)
- DFD model rules
Example - Business Process - Goodwill
Example - System Architecture - Fall 2017 Example (Custom)
Example - Various - House of Songs (Wordpress)
Example - Various - Asset Mapping (Custom)
Example - Web Flow Diagrams - CCP | Latakoo