Models

A model is an abstract representation of a thing. So that could be a process or architectural design or or thinking or a structure, and models can be used to help people to understand concepts or complexity of that thing. And they can be created in many different formats too. So whiteboard drawings, logical flow diagrams, maps, like main maps or even written text or even verbally described. 

There are some common process models that you may be familiar with, like an agile sprint cycle or the agile testing quadrants, for example, or the many different automation triangles. There's some other business specific models that people might be familiar with, which are business process diagrams or risk maps. 

So models can help provide information. They can help understand a problem space. They can also trigger test ideas and models stem more creative thinking as well. 

Where all models are flawed. A map of the UK, showing roads, is gonna be different to showing weather. For example, so a specific model won't have a specific purpose, but it can be used for many different purposes. And models are based upon perspective as well, meaning that assumptions are made that baked into the models.

Models are an informative representations of a system. They are a means of communication that has a specific intent that the creator has in mind.

A model provides some kind of structure that gets people talking and have the different perspectives at it.

What is a model? Simply put, it’s a simpler version of something complicated. Think of a map, it doesn’t show every tree, hill or crack in the road, but it gives you enough information to get where you’re going.