Cause Effect Graphing in Software Engineering Last Updated : 28 Mar, 2020 Summarize Comments Improve Suggest changes Share Like Article Like Report Prerequisite - Black Box Testing Cause Effect Graphing based technique is a technique in which a graph is used to represent the situations of combinations of input conditions. The graph is then converted to a decision table to obtain the test cases. Cause-effect graphing technique is used because boundary value analysis and equivalence class partitioning methods do not consider the combinations of input conditions. But since there may be some critical behaviour to be tested when some combinations of input conditions are considered, that is why cause-effect graphing technique is used. Steps used in deriving test cases using this technique are: Division of specification: Since it is difficult to work with cause-effect graphs of large specifications as they are complex, the specifications are divided into small workable pieces and then converted into cause-effect graphs separately. Identification of cause and effects: This involves identifying the causes(distinct input conditions) and effects(output conditions) in the specification. Transforming the specifications into a cause-effect graph: The causes and effects are linked together using Boolean expressions to obtain a cause-effect graph. Constraints are also added between causes and effects if possible. Conversion into decision table: The cause-effect graph is then converted into a limited entry decision table. If you're not aware of the concept of decision tables, check out this link. Deriving test cases: Each column of the decision-table is converted into a test case. Basic Notations used in Cause-effect graph: Here c represents cause and e represents effect. The following notations are always used between a cause and an effect: Identity Function: if c is 1, then e is 1. Else e is 0. NOT Function: if c is 1, then e is 0. Else e is 1. OR Function: if c1 or c2 or c3 is 1, then e is 1. Else e is 0. AND Function: if both c1 and c2 and c3 is 1, then e is 1. Else e is 0. To represent some impossible combinations of causes or impossible combinations of effects, constraints are used. The following constraints are used in cause-effect graphs: Exclusive constraint or E-constraint: This constraint exists between causes. It states that either c1 or c2 can be 1, i.e., c1 and c2 cannot be 1 simultaneously. Inclusive constraint or I-constraint: This constraint exists between causes. It states that atleast one of c1, c2 and c3 must always be 1, i.e., c1, c2 and c3 cannot be 0 simultaneously. One and Only One constraint or O-constraint: This constraint exists between causes. It states that one and only one of c1 and c2 must be 1. Requires constraint or R-constraint: This constraint exists between causes. It states that for c1 to be 1, c2 must be 1. It is impossible for c1 to be 1 and c2 to be 0. Mask constraint or M-constraint: This constraint exists between effects. It states that if effect e1 is 1, the effect e2 is forced to be 0. Comment More infoAdvertise with us Next Article What is Software Testing? P ps17 Follow Improve Article Tags : Software Engineering Software Testing Similar Reads Software Testing Tutorial Software testing is an important part of the software development lifecycle that involves verifying and validating whether a software application works as expected. It ensures reliable, correct, secure, and high-performing software across web, mobile applications, cloud, and CI/CD pipelines in DevOp 10 min read What is Software Testing? Software testing is an important process in the Software Development Lifecycle(SDLC). It involves verifying and validating that a Software Application is free of bugs, meets the technical requirements set by its Design and Development, and satisfies user requirements efficiently and effectively.Here 11 min read Principles of Software testing - Software Testing Software testing is an important aspect of software development, ensuring that applications function correctly and meet user expectations. In this article, we will go into the principles of software testing, exploring key concepts and methodologies to enhance product quality. From test planning to e 3 min read Software Development Life Cycle (SDLC) Software development life cycle (SDLC) is a structured process that is used to design, develop, and test good-quality software. SDLC, or software development life cycle, is a methodology that defines the entire procedure of software development step-by-step. The goal of the SDLC life cycle model is 11 min read Software Testing Life Cycle (STLC) The Software Testing Life Cycle (STLC) is a process that verifies whether the Software Quality meets the expectations or not. STLC is an important process that provides a simple approach to testing through the step-by-step process, which we are discussing here. Software Testing Life Cycle (STLC) is 7 min read Types of Software Testing Software testing is a important of software development life-cycle that ensures a product works correctly, meets user expectations, and is free of bugs. There are different types of software testing, each designed to validate specific aspects of an application, such as functionality, performance, se 15+ min read Levels of Software Testing Software Testing is an important part of the Software Development Life Cycle which is help to verify the product is working as expected or not. In SDLC, we used different levels of testing to find bugs and errors. Here we are learning those Levels of Testing in detail.Table of ContentWhat Are the Le 4 min read Test Maturity Model - Software Testing The Test Maturity Model (TMM) in software testing is a framework for assessing the software testing process to improve it. It is based on the Capability Maturity Model(CMM). It was first produced by the Illinois Institute of Technology to assess the maturity of the test processes and to provide targ 8 min read SDLC MODELSWaterfall Model - Software EngineeringThe Waterfall Model is a Traditional Software Development Methodology. It was first introduced by Winston W. Royce in 1970. It is a linear and sequential approach to software development that consists of several phases. This classical waterfall model is simple and idealistic. It is important because 13 min read What is Spiral Model in Software Engineering?The Spiral Model is one of the most important SDLC model. The Spiral Model is a combination of the waterfall model and the iterative model. It provides support for Risk Handling. The Spiral Model was first proposed by Barry Boehm. This article focuses on discussing the Spiral Model in detail.Table o 9 min read What is a Hybrid Work Model?Hybrid means a thing made by a combination of two different elements and the resulting hybrid element acquires characteristics of both underline elements. The following topics of the hybrid model will be discussed here:What is the Hybrid Model?Why the Hybrid Model?When To Use a Hybrid ModelProcess o 13 min read Prototyping Model - Software EngineeringPrototyping Model is a way of developing software where an early version, or prototype, of the product is created and shared with users for feedback. The Prototyping Model concept is described below: Table of ContentWhat is Prototyping Model?Phases of Prototyping ModelTypes of Prototyping ModelsAdva 7 min read SDLC V-Model - Software EngineeringThe SDLC V-Model is a Types of Software Development Life Cycle (SDLC), which is used in Software Development process. In V-Model is the extension of the Traditional Software Development Model.It is creating a Structure like the "V" which includes the different phases which we are discussing here in 10 min read TYPES OF TESTINGManual Testing - Software TestingManual testing is a crucial part of software development. Unlike automated testing, it involves a person actively using the software to find bugs and issues. This hands-on approach helps ensure the software works as intended and meets user needs. In this article, we'll explain what manual testing is 12 min read Automation Testing - Software TestingAutomated Testing means using special software for tasks that people usually do when checking and testing a software product. Nowadays, many software projects use automation testing from start to end, especially in agile and DevOps methods. This means the engineering team runs tests automatically wi 15+ min read Like