--- title: "Model Common Understanding" slug: "model-common-understanding" description: "Model Common Understanding. It's important to understand some of the basic functionality and how modelling defines a process." tags: ["Art of Modelling", "Learning Portal", "Get Started", "Test Modeller"] updated: 2024-09-27T15:01:03Z published: 2024-09-27T15:01:03Z canonical: "knowledge.curiositysoftware.ie/model-common-understanding" --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledge.curiositysoftware.ie/llms.txt > Use this file to discover all available pages before exploring further. # Model Common Understanding As we continue this Art of Modelling series, it's important to understand some of the basic functionality and how Modelling defines a process, but equally it builds a common understanding of what's occurring and allows you to scope and articulate the flow of a particular process. Be mindful of decision gates and the consequences of those decision gates, overlay logic to reduce repetition and get the most out of your testing. ## 3.1 Scope & Articulate Flow Decision Gates get laid down on the Quality Modeller canvas to serve the nodes to Generate Tests. These tests are based on Coverage Profiles. In this example, Test Generation results in four possible flows, which terminate in being able to make a perfect cup of tea, or not. [Embedded content](https://www.youtube.com/embed/bzZkgDlTojs?&wmode=opaque&rel=0) You’ll meet Huw Price (Managing Director, Curiosity Software) as he navigates the need to throw down a rough process flow to help articulate a series of data states as decision groups ahead of starting to visually model. This approach favours seeing the bigger picture in which test steps can be agreed, modified and refined in the model amongst all stakeholders including testers, business users, SMEs, developers, SDETS, manual testers and likely end-users. --- ## 3.2 Be Mindful of Decision Gates What we're doing is we're putting everything, so it is visual. The reason we're doing, this is because we need to put it all into a visual representation. So once you've finished with your preliminary Model, what you need to do then is to start thinking about creating some tests or user stories. [Embedded content](https://www.youtube.com/embed/QkaY70POa5Y?&wmode=opaque&rel=0) This features ahead of the subsequent clip, which shows the use of Rules as a way of limiting the amount of possible scenarios. But equally how a mixed approach using Rules with Logic Gates can be used to inform best practice modelling when executing test steps. --- ## 3.3 Overlay Logic to Reduce Repetition Where the previous clip introduced a fully visual model, Logic Gates though had to be repeated, which may be tricky to maintain. So Boolean states are a more embedded solution and though less overtly visualized - you have to look at the Boolean logic itself - if you're only interested in the User Stories or Test Cases, that's the way to go. [Embedded content](https://www.youtube.com/embed/lSaOp4uiirQ?&wmode=opaque&rel=0) Finally, what you may find is to use a mixed approach where you're balancing the visual elements to make the model more understandable while overlaying complexity through Boolean logic states. This shows you a different way to solve the same problem, where we're going to use constraints or Boolean logic to overlay onto the model. And what we've done is add in a new endpoint called no tea. What you'll see is that we have a little hexagon here; we have some rules to find here. Associated with each block in the Assignment we've picked up, HaveTea Yes, HaveTea No, like so; and we've done that for each of the data states. You need to go in and define Rules; and we've created a very simple one here. So if any of these is not true, we cannot make a cup of tea. Modelling or modelling systems or functions is the main function of Modeller. Modelling or system modelling is the use of models to conceptualize and construct systems in business and IT development. A common type of systems modelling is function modelling, with specific techniques such as the Functional Flow Block Diagram and BPMN Diagrams. Quality Modeller is Curiosity's flow-driven model-based tool which provides a range of accelerators and connectors for building flowcharts rapidly. Align all stakeholders to quality outcomes and create critical assets early, delivering superior software at speed. Coverage Profiles are a wrapper for Coverage settings and options. Any number of Coverage Profiles can be created as required, each with its own Coverage settings. The Coverage button is on the Test Generation tab of a Model. Quality Modeller Models come with Default Profile, User Stories and Test Cases Profiles built in. A Model is a canvas and the Flow that is built onto it. There are several types of Model, some of which display different tabs and tools on the toolbar in Quality Modeller. Rules are conditions placed on Model Nodes of a Non-Linear Model that control whether the processing of a Flow passes through that branch. The Rules tool can be found on the Test Generation tab. When a Rule has been applied, a Rules logo appears in the Node were the rule was applied, and when that Node is selected, number appears next to the Rules button to show how many Rules have been applied on that Node. Test cases are equivalent to paths through the model of a system under test. They are generated automatically from a model, with or without test data and test automation associated with them. Test Modeller has coverage techniques using advanced algorithms to generate the smallest set of test cases needed to test given features with a required level of rigour. ## Related - [The Art of Modelling](/the-art-of-modelling.md) - [Test Case Vocabulary](/test-case-vocabulary.md) - [Modelling UIs](/modelling-uis.md) - [Coverage in Test Case Design](/coverage-in-test-case-design.md) - [Form, Cause and Change](/form-cause-and-change.md) - [The Art of Modelling Test Approaches](/the-art-of-modelling-test-approaches.md)