Developing A Program Logic - A Step-by-step Guide

1y ago
9 Views
3 Downloads
5.10 MB
28 Pages
Last View : 1m ago
Last Download : 3m ago
Upload by : Troy Oden
Transcription

Developing a Program LogicA step-by-step guideMarch 2021Department of Communities and JusticeFamily and Community Services Insights Analysis and Research (FACSIAR)

Prepared byEvaluationFamily and Community Services Insights Analysis and Research (FACSIAR)Published byNSW Department of Communities and JusticeFamily and Community Services Insights Analysis and Research (FACSIAR)320 Liverpool Road, Ashfield NSW 2131Email: FACSIAR@dcj.nsw.gov.auWebsite www.dcj.nsw.gov.auMarch 2021 NSW Department of Communities and Justice 2021.We want our tools and guides to be as helpful as possible. You can leave a comment to let us knowwhat works well and what could be improved by contacting FACSIAR@dcj.nsw.gov.auWe will be regularly updating this guide. Please check the DCJ website to make sure you have thelatest version.

NSW Department of Communities and Justice GuideContentsIntroduction5What is a program logic?5When to develop a program logic?6Benefits of a program logic6Developing a program logic7What is not included in the FACSIAR program logic?Who should be involved in developing a program logic?88Step 1: Define the need or problem and outcomes10Step 2: Review the evidence of “what works” to achieve desired outcomes11Step 3: Describe the program components12Step 4: Articulate the mechanisms of change12Step 5: Identify the program outputs13Step 6: Define expected client outcomes13Step 7: Review the program logic15Using Program Logic in Monitoring & Evaluation17Step 1: Allocate indicators to the activities and outputs17Step 2: Allocate indicators to the intended outcomes17Step 3: Review18Other data sources to capture insights18Useful resources19Need more support?20Glossary21Appendix A: FACSIAR Program Logic Template24Appendix B26References27List of FiguresFigure 1. FACSIAR Program Logic Template (abbreviated)Figure 2. NSW Human Services Outcomes Framework domainsDeveloping a Program Logic – A step-by-step guide7143

There is growing emphasis in humanservices on making service deliverychoices that are based on the bestavailable evidence for what works,with program development andfunding streams increasingly tied toresearch evidence.

NSW Department of Communities and Justice GuideIntroductionThe NSW Department of Communities and Justice (DCJ) is committed to the development of evidenceinformed policies and programs, and rigorous evaluation of its existing policies and programs.This guide has been developed to support DCJ staff to use program logics to design, implement andevaluate evidence-informed programs. It summarises what a program logic is, when and how to use it, andprovides templates and step-by-step instructions for developing a program logic and using it to identify thedata you need to collect to measure program success.What is a program logic?A program logic is a simple graphic that explains what a program is and how it ‘works’. It clearly articulatesthe program activities and rationale for change: that is, why and how the program is expected to achieveits outcomes.Program logics are an important tool to support program design because they prompt us to think throughand demonstrate the links between program activities, outputs, short- and medium-term outcomes andlonger term impact using the best available evidence.1 They can also be a powerful communication tool toconvey to funders, partner organisations, staff and potential clients how a program operates, and what it isexpected to achieve and when.ProgramIn this guide, a program is defined as: a set of activities managed together over a sustainedperiod of time that aim to achieve an outcome for a client or client group.NSW Government Program Evaluation Guidelines, 2016Program logics are an essential tool in evaluation. They can be used to guide decisions about when andwhat to evaluate, ensuring resources are used efficiently and effectively. A program logic also helpsevaluators to identify, select and embed appropriate implementation and outcome measures to empiricallytest whether a program was delivered as intended and had an impact on client outcomes. Evaluationfindings should be used to update and refine the program logic, as well as help to prioritise thecommissioning of programs that are most likely to impact positively on client outcomes and to modify, orcease, programs that do not contribute to the intended outcomes.Developing a Program Logic – A step-by-step guide5

NSW Department of Communities and Justice GuideWhen to develop a program logic?Ideally, a program logic should be developed as part of the program design process (Steps 1 – 3 of the DCJCommissioning Cycle). This helps to ensure that program design decisions are based on the best availableevidence of what works to achieve intended outcomes, and that these outcomes are clearly linked to theneeds of clients. Engaging stakeholders in the development of a program logic during the program designphase can also help to strengthen commitment to the program and foster a shared understanding of how itwill operate and what it intends to achieve.It is important to periodically review your program logic to check that it is still an accurate representation ofthe program. This process can also help drive continuous improvement by prompting stakeholders toassess whether the program is operating as intended and that program components and outcomes arealigned. Where differences between the program logic and delivery emerge, consider whether it is theprogram or the logic that needs to be adapted.Benefits of a program logicUsing a program logic to support program design and evaluation has many benefits. A program logic: Places client needs at the centre of program design. Ensures program design and implementation are grounded in evidence. Brings together existing evidence about a program and highlights where there are gaps in the evidencethat need to be addressed by research and evaluation.2 Enhances engagement with stakeholders in program design and fosters a shared understanding of howa program operates and the outcomes it aims to achieve.3 Helps to develop a greater understanding of how a program ‘works’ by clearly articulating how and whyprogram activities are expected to lead to particular outcomes, making the process of change explicit.4 Provides a framework for a systematic, integrated approach to program planning, implementation, andevaluation.5 Helps to determine when and what to evaluate so that resources are used efficiently and effectively.6Developing a Program Logic – A step-by-step guide6

NSW Department of Communities and Justice GuideDeveloping a program logicThere are many different ways to develop and present a program logic. The approach outlined in this guide isbased on the pipeline model, which links the program activities to program outputs and outcomes in a linearprocess.7 You can use the FACSIAR program logic template (shown at Appendix A and accompanied by aworked example) as you work through the guide to build your program logic. While it’s not mandatory, usingthis template will help drive consistency in the approach to developing program logics in DCJ. The programlogic template implies a causal direction from left to right.Figure 1. FACSIAR Program Logic Template (abbreviated)Describe the programcomponents and activitiesDescribe theneed or problembeing targetedWhat outputs will theprogram produce?1.2.3.4.5.6.NEED /PROBLEMEVIDENCEPROGRAMCOMPONENTSMECHANISMSOF CHANGEOUTPUTSOUTCOMESInclude evidence thatshows the programcomponents andactivities can effectivelyaddress the problemsHow and whyare these likelyto be effective?What are the intendedoutcomes for our clientsand communities?A distinguishing feature of this template is the inclusion of a column to articulate the research evidence forprograms (or program components) that have proven to effectively address the identified problems. Thisprompts you to incorporate evidence in program design, wherever possible, and promotes evidence-basedpractice. Another innovation is the inclusion of the mechanisms of change column. This column helps you tobe clear about how and why change is expected to occur to improve outcomes for clients.The template is designed to be a working document that supports you to develop and refine your program.As the strength of evidence and mechanisms of change that underpin the program are important toconsider in this process, these columns are included in the FACSIAR program logic template. However,these columns can disrupt the visual representation of the connection between the problem, activities,outputs and outcomes, and it may be useful to also create a simplified version of the program logic,designed to support communications with stakeholders, that doesn’t include this content.Developing a Program Logic – A step-by-step guide7

NSW Department of Communities and Justice GuideWhat is not included in the FACSIAR program logic?Many program logics include sections for articulating program inputs, assumptions and external factors.A brief explanation of these three elements is provided in Appendix B. The FACSIAR program logic templatedoes not include sections to record this information as incorporating too much detail can make the logiccluttered and hard to read. However, this does not imply that these elements are not important to consider.Programs are implemented within broader economic, political and cultural contexts, and the extent to whichthese help or hinder program success should be taken into account. The relationship between programinputs, activities and intended outcomes are often based on assumptions which, if untrue, may be thereason for disappointing results. FACSIAR suggests this information is captured in a separate table that isrelated to the program logic.Who should be involved in developing a program logic?While developing a program logic can at first seem daunting, the main expertise required is knowledge of theprogram. For this reason, program managers and staff involved in the delivery of the program should haveconsiderable input into a program logic.Developing a program logic is a participatory and iterative exercise. It is important to involve a range ofprogram stakeholders to draw on their understanding of the program and its intended outcomes andimpacts. Involving partner agencies and clients can also provide important insights into what is needed tomake a program work in a specific setting. Engaging stakeholders has the added benefit of generatingbuy-in and ownership of the final program logic, as well as the program itself.8Program logic development is often undertaken in a workshop format to allow input from multiplestakeholders. In addition, structured interviews with subject matter experts and program stakeholders canbe conducted to develop a better understanding of the problem being addressed by the program, itscauses and consequences, and how the program can contribute to positive change.9Useful resources: Better Evaluation – Understand and Engage Stakeholders MEASURE Evaluation – Stakeholder Engagement ToolRelevant DCJ Commissioning Toolkit resources include the Stakeholder Engagement Plan (Step 1) andStakeholder Value Matrix (Step 2).Suggested steps for developing a program logic using the FACSIAR template are summarised below. Thesteps described follow the logical progression from left to right of the FACSIAR program logic template.Developing a Program Logic – A step-by-step guide8

Developing a program logic togetherwith stakeholders helps to create ashared understanding of a program’saims and supports all stakeholdersto work towards achieving acommon set of client outcomes.

NSW Department of Communities and Justice Guide Step 1: Define the need or problem and outcomesThe first step in developing a program logic is to clearly define the problem, or unmet need the program istrying to address. This column should answer questions such as: Why should this program exist? What need is it meeting? Who are the intended beneficiaries?It is important to be as specific as possible, making sure to describe the population group or cohortimpacted by the problem, their needs or common risk factors, and the setting in which the problem ismost prevalent (e.g. community, schools, hospitals, social housing estates).To identify the problem areas the program will seek to change, you should complete a needs assessment.Understanding what the true needs of the target population are provides a solid basis for determining whata program should aim to achieve and how well it is doing. In other words, the inverse of the needs youidentify in this step become the intended outcomes of the program (e.g. if the identified need is an increasein the number of people experiencing homelessness, then the programs’ intended outcome would be areduction in the number of people who are homeless).The needs assessment should triangulate evidence of the problem based on: Population and client-level data Client, community and staff (DCJ and NGO) perspectives Existing research literature Conversations with experts and stakeholdersA thorough needs assessment not only helps to define intended program outcomes, but the data collectedduring the needs assessment phase can often double as baseline data to track change in outcomes over time.Useful resources: Australian Institute of Family Studies – Needs AssessmentRelevant DCJ Commissioning Toolkit resources include the Needs Assessment and Cohort DefinitionTool (Step 1).At this stage, it can be helpful to make a note of the outcomes the program will aim to achieve, based onthe problem you have described. It is important to be realistic about what change the program will be ableto achieve with the available resources, and within specified timeframes. Many programs fail to succeedsimply because of unrealistic expectations of the change they should achieve.Developing a Program Logic – A step-by-step guide10

NSW Department of Communities and Justice Guide Step 2: Review the evidence of “what works” to achievedesired outcomesThe next step is to review and summarise the evidence on the most effective programs, and/or programcomponents and activities, to address the identified problems and achieve intended outcomes.Take the time to do a systematic search and appraise the evidence you identify to make sure you end upwith a comprehensive summary of relevant, high-quality research. The best research evidence is frompublished systematic reviews and high-quality randomised controlled trials that demonstrate effectiveness.It is also important to include evidence from relevant high-quality evaluation reports.Useful resources:DCJ has a suite of guides to help you find and interpret research evidence on programeffectiveness and assess its quality, including: What is evidence? Finding quality research and evidence Assessing the quality of research evidenceThese guides and others can be found in the FACSIAR evidence hub.For assistance finding research evidence DCJ staff can request a literature search through the DCJLibrary at Library@dcj.nsw.gov.au.If you are struggling to find evidence on effective programs or interventions, it can be helpful to look forevidence of individual program components, activities or approaches that address the problem you haveidentified. Subject matter experts may also be able to provide important insights into the evidence base,and how it can be applied to your specific population and setting. While some interventions do not lendthemselves to randomised controlled trials, generally there will be other forms of high-quality evidence thatdescribe their impacts. It is very rare that there is absolutely no evidence on how to address a problem.The point is to use the best evidence that’s available. It’s also important to consider the relevance of theevidence for your population and intended setting. It may be that studies focused on a similar age group orcohort are more relevant than research on the same or very similar programs that were delivered to a verydifferent cohort.Developing a Program Logic – A step-by-step guide11

NSW Department of Communities and Justice GuideStep 3: Describe the program componentsBased on the identified problems (step 1) and what the evidence suggests is the most effective way tointervene to address these problems (step 2), describe what your program will look like. There is no limit tohow many program components and activities you can include in this section, so long as there is evidencethat they will lead to a desired outcome. It is important to be specific, without going into too much detail.Ideally, someone with no prior knowledge of the program should have a good understanding of what will bedelivered, to whom and when after reading this section.Step 4: Articulate the mechanisms of changeThe mechanisms of change section describes the ways in which the program components and activitiesbring about the program’s effects, or the theory of change underpinning the program. When completingthis column in the program logic, you should describe how and why the proposed program is expected toachieve the intended outcomes.A good mechanism of change takes into account context, as certain combinations of factors are more likelyto result in the program producing the intended effects. For example, the success of a prisoner educationprogram might be most likely for those without drug and alcohol dependence, those with aspirations to gainskills or employment as well as the presence of supportive community factors, such as businesses willing toemploy people post-release from custody10 (pg. 8, Pawson & Tilley, 2004). This contextual information isuseful to policy-makers as it informs them about the contexts under which the program will be successful,or produce its intended outcomes.Clearly describing the programs' theory of change supports evaluators to decide what data to collect toempirically test whether, and if so which, mechanisms are important to achieving outcomes. This canstrengthen conclusions about which clients the program works best for and whether impacts on clientoutcomes can be attributed to the program, rather than external factors. Ultimately, this enables DCJ toadapt and prioritise funding of programs that are more likely to improve client outcomes.Breakfast Club: An example of identifying mechanisms of changeWhen trying to identify mechanisms of change it can be helpful to think about how theresources the program provides enable participants to change their knowledge, behaviouror skills. In other words, how the program participants make the program ‘work’. It is important to notethat program activities might trigger more than one mechanism. For example, delivering a before-school‘breakfast club’ intervention may trigger the following mechanisms of change:A breakfast club may aid classroom attentiveness by offering the kids a ‘nutritious kick-start’ (M1) to theday, which they might not otherwise get. And/or it may act as a ‘summoning point’ (M2) to prevent kidsloitering or absconding or misbehaving in the chaotic period before school. And/or it may act as an‘energy diffuser’ (M3) to soak up gossip and boisterousness before formalities commence.(Pawson & Tilley, 2004)Developing a Program Logic – A step-by-step guide12

NSW Department of Communities and Justice GuideStep 5: Identify the program outputsThe next step is to list the outputs of the program. Outputs are the tangible results, products or servicesthat are generated by the program. The focus here is usually on what is delivered by the program. Outputsare things that can be counted or seen, such as the number of people who received support or participatedin a program component, the number of assessments completed, or the materials created by the program.Describing outputs supports your ability to monitor and improve the implementation of the program.Step 6: Define expected client outcomesClient outcomes should have been identified in step 1 and refined in step 2. Remember that it is importantto make sure that the intended outcomes are realistic and can be achieved with the available resources, andwithin the specified timeframes.Distinguishing between outputs and outcomesOutcomes are often confused with outputs in program logics. Outputs are what is delivered (e.g.number of training sessions held) whereas outcomes are the changes the program or interventionintends to bring about for the client (e.g. a change in wellbeing, skills or employment).It can be useful to order outcomes from short-, to medium-, to long-term to show the cause-and-effectrelationships between the outcomes. To support the ordering of outcomes you can use the evidencegathered in steps 1 and 2 (i.e. research evidence or conversations with experts).In general, program outcomes will represent medium-term (intermediate) client outcomes in the programlogic because longer term impacts may not be seen for several years—sometimes decades. It is alsoimportant to consider the scale of the program in relation to the problem statement, and to identify issuesthat are out of scope. Short-term (immediate) outcomes are usually expected during, or on completion of, the program, andoften include changes in knowledge, skills, awareness, attitudes or motivation. Medium-term (intermediate) outcomes may not occur until sometime after the program, and often includethe application of knowledge and skills, and changes in behaviours, practice or systems. Long-term outcomes are overarching objectives and should resolve issues outlined in the problem statement.These will often take a long time to occur and be influenced by a range of factors other than the program.Developing a Program Logic – A step-by-step guide13

NSW Department of Communities and Justice GuideUsing the NSW Human Services Outcomes FrameworkDCJ has been working to align outcomes across programs within the Department by applying theNSW Human Services Outcomes Framework. The Outcomes Framework is a cross-agency frameworkdesigned to support NSW Government agencies and non-government organisations (NGOs) adopt anoutcomes-focused approach in human services design, delivery and evaluation.Figure 2. NSW Human Services Outcomes Framework domainsThe Outcomes Framework identifies relevant outcomes for clients across seven domains: Educationand Skills, Economic, Health, Home, Social and Community, Empowerment and Safety. To assist inmeasuring the of impact DCJ services 37 Core Client Outcomes have been developed across thesedomains, supported by outcome indicators. You should consult the DCJ Core Client Outcomes to seehow your program aligns with the Outcomes Framework, and incorporate relevant indicators wherepossible. Using valid and reliable indicators of client outcomes is essential to build evidence of whatworks. Keeping these outcome measures consistent also allows us to more easily compare the relativeeffectiveness DCJ programs.Very few programs will have an impact on every domain in the Outcomes Framework, so it is unlikelythat all the outcome domains will be represented in your program logic. The critical part of any programlogic should be its ability to visually represent the links between the problem, activities and the solution(the outcome).For more information about how you can use the Outcomes Framework, visit the DCJ website.Developing a Program Logic – A step-by-step guide14

NSW Department of Communities and Justice GuideStep 7: Review the program logicOnce you have completed the program logic, check that it is clear, comprehensive, and that theconnections between the columns are logical.An effective program logic should:11 Present a coherent causal model that explains how the program contributes to the desired outcomes(i.e. it should visually represent the links between the problem and the outcome). Be logical, so the expected change is clearly depicted and the links between evidence, program activities,outputs and outcomes make sense. Act as an effective communication tool for internal and external stakeholders.Program Logic ChecklistIs the model logical? Do the program components and activities, outputs, and outcomeslink together and make sense?Have you drawn on evidence from research and experience demonstrating that clients withsimilar characteristics and needs have engaged with the activities described?Have you described the evidence that the activities/outputs will lead to the short-termoutcomes, and that the short-term outcomes will lead to the medium- and long-termoutcomes?Do the program components and outputs columns make it clear what the program willactually do?Is each outcome truly a client-focused outcome? It can be easy to confuse program outputswith outcomes.Have you consulted the DCJ Core Client Outcomes and Indicators to ensure your programaligns with the NSW Human Services Outcomes Framework?Are the outcomes realistic, attainable and measurable?Have you considered how the program context may impact outcomes?Developing a Program Logic – A step-by-step guide15

We should strive to continuallyassess how effective our servicesare, whether they continue toachieve the best value for moneyand whether they remain relevant tothe evolving needs of our customers.

NSW Department of Communities and Justice GuideUsing Program Logic in Monitoring & EvaluationTo effectively monitor and evaluate programs we need to collect data on what is delivered, to whom, whenand how, and measure progress towards achieving the intended outcomes. A program logic is a useful toolto help you develop a monitoring and evaluation framework because it identifies the program activities,outputs and outcomes that need to be measured. It also helps to ensure monitoring and evaluation resourcesare used efficiently and effectively. By breaking down program outcomes into the short- and medium-term,program logics can guide decisions not only about what should be measured but also when. This ensuresthat resources are not wasted measuring outcomes that the program is not designed to impact or bymeasuring appropriate outcomes at inappropriate time-points.Ideally, the data required to monitor and evaluate a program should be mapped out as part of the programlogic development process. Identifying the data that your program will need to collect during the programdesign phase is important to help embed data collection in program delivery where possible and establisha good foundation to monitor progress. It will also allow you to identify data that may need to be collectedbefore the program commences so that robust evaluation is possible.The steps to use program logic to help develop a monitoring and evaluation framework are outlined below.Step 1: Allocate indicators to the activities and outputsThe program components and outputs columns in the program logic tell you what should be delivered.This is a useful starting point to identify the data that needs to be collected for program monitoring andevaluation. Allocate indicators to each program component and activity that capture when, how and towhom these are delivered. This will allow you to monitor implementation of the program and ensure thatfidelity to the program model can be assessed.Step 2: Allocate indicators to the intended outcomesThe outcomes columns specify what client outcomes the program intends to impact. It is these outcomesthat should be measured to track progress and evaluate whether the program is effective. In this step, it isimportant to consider when you might expect to see change in each outcome in your program logic, andalign the timing of the data collection and evaluation accordingly.Developing a Program Logic – A step-by-step guide17

NSW Department of Communities and Justice GuideCapturing data on service delivery and outcomes: why is it important?Collecting data on both program implementation (activities and outputs) and outcomes isessential to meaningful evaluation. Measuring outcomes is how we can tell whether our programs aremaking a difference. In addition to measuring outcomes, it is important to consider whether a programis being implemented as intended – that is, the fidelity of implementation.If fidelity to the program model is high, then evaluation is a “true test” of the intended intervention. Iffidelity is low however, evaluation results may have more to do with how the program was implementedthan its design. It may be that an otherwise effective program does not achieve results simply because itwas poorly implemented. If data on program implementation is not collected an evaluation will not beable to determine whether the program model is effective or not, making it difficult to decide whether tocontinue or expand a program to other locations even if it has shown promising results.Considering implementation and outcome data together can also drive program improvement. Identifyingthe practices that are most strongly linked to improvements in outcomes, allows you to identify andsupport sites that struggle the most to implement those practices.Step 3: ReviewFinally, it is important to check that every activity, output and outcome in the program logic has at leastone indicator that has been mapped to a data source. This will ensure that the monitoring and evaluationframework is supported by data and allow you to identify and address any major gaps in implementationand outcome data early on (e.g. by making adjustments to routinely collected administrative data orembedding additional data collection activities in program delivery).Other data sources to capture insightsA comprehensive monitoring and evaluation framework will include information that may not be listed in theprogram logic, such as information on contract management and compliance. Moreover, to gain deeperinsights into program implementation and outcomes an evaluation will need to collect a broad range of data,which may also involve interviews or focus groups with important s

Step 1: Define the need or problem and outcomes 10 Step 2: Review the evidence of "what works" to achieve desired outcomes 11 Step 3: Describe the program components 12 Step 4: Articulate the mechanisms of change 12 Step 5: Identify the program outputs 13 Step 6: Define expected client outcomes 13 Step 7: Review the program logic 15

Related Documents:

Dynamic Logic Dynamic Circuits will be introduced and their performance in terms of power, area, delay, energy and AT2 will be reviewed. We will review the following logic families: Domino logic P-E logic NORA logic 2-phase logic Multiple O/P domino logic Cascode logic

Logic models are tools for program design, implementation, and evaluation. The process of developing a logic model is important: Engage stakeholders in developing a logic model. Logic models should be living documents and returned to frequently. Logic models are useful for evaluation but best when developed at the program design .

MOSFET Logic Revised: March 22, 2020 ECE2274 Pre-Lab for MOSFET logic LTspice NAND Logic Gate, NOR Logic Gate, and CMOS Inverter Include CRN # and schematics. 1. NMOS NMOSNAND Logic Gate Use Vdd 10Vdc. For the NMOS NAND LOGIC GATE shown below, use the 2N7000 MOSFET LTspice model that has a gate to source voltage Vgs threshold of 2V (Vto 2.0).File Size: 586KB

Digital Logic Fundamentals Unit 1 – Introduction to the Circuit Board 2 LOGIC STATES The output logic state (level) of a gate depends on the logic state of the input(s). There are two logic states: logic 1, or high, and logic 0, or low. The output of some gates can also be in a high-Z (high impedance) state, which is neither a high

categorical and hypothetical syllogism, and modal and inductive logic. It is also associated with the Stoics and their propositional logic, and their work on implication. Syllogistic logic and propositional logic led later to the development of predicate logic (or first order logic, i.e. the foundational logic for mathematics)

BRIEF LADDER LOGIC OVERVIEW Page 2 18.05.2015 1.2 What is Ladder logic? Ladder logic, also known as a Ladder diagram, is a method for programming for Program-mable Logic Controls. Ladder Logic is a standardized type of graphic programming, which is similar to a circuit diagram. Programming with ladder logic is used, in particular, for creat-

The University of Texas at Arlington Sequential Logic - Intro CSE 2340/2140 – Introduction to Digital Logic Dr. Gergely Záruba The Sequential Circuit Model x 1 Combinational z1 x n zm (a) y y Y Y Combinational logic logic x1 z1 x n z m Combinational logic with n inputs and m switching functions: Sequential logic with n inputs, m outputs, r .

2.2 Fuzzy Logic Fuzzy Logic is a form of multi-valued logic derived from fuzzy set theory to deal with reasoning that is approximate rather than precise. Fuzzy logic is not a vague logic system, but a system of logic for dealing with vague concepts. As in fuzzy set theory the set membership values can range (inclusively) between 0 and 1, in