Decision Analysis and Resolution (DAR)

process cycle
process cycle @Image courtesy of basketman/ FreeDigitalPhotos.net

Decision Analysis and Resolution (DAR)

Welcome to CodeSpread!

We divide the terms to understand them better.

Decision Analysis is related to analyze possible decisions. So we need a process to perform decision analysis.

Resolution is related to a proposed solution. These solutions are matched up against a benchmark.

Overall, Decision Analysis and Resolution (DAR) are used to analyze possible decisions for proposed solutions.

A popular definition is also available; The purpose of decision analysis and resolution is to analyze possible decisions using a formal evaluation process that evaluates identified alternatives against established criteria.

Why do we need DAR?

Software development involves different activities and there are chances we can make bad/sudden decisions which can lead to project risk.

With the help of DAR, we can avoid such circumstances to appear in our project.

Example: We have to use a configuration management tool in our project then we need to keep three-four options based on technologies compatibility and other parameters.

Where can we apply DAR to?

  1. Alternate Design decisions.
  2. Software Tool specific decisions in the project.
  3. Testing approaches.
  4. Technical Solutions.

When You Use the DAR Process?

DAR is used for decisions that are high risk, may result in loss of business or have legal implications.

Example:

  • Schedule impact of >xx days that may move the project deadlines.
  • A Cost impact of >xx% is anticipated.
  • Quality Impact of >xx% from established benchmarks.

How to perform DAR?

Specific Practices by Goal

  • SG 1 Evaluate Alternatives
    • SP 1.1 Establish Guidelines for Decision Analysis

We can take many possible decisions but are all our decisions require a formal evaluation process? Answer is No. The decision to conduct a formal evaluation process is determined by the established guidelines. We should have to maintain guidelines to determine which issues are subject to a formal evaluation process.

    • SP 1.2 Establish Evaluation Criteria

The evaluation criteria provide the basis for evaluating alternative solutions. Evaluation Criteria can be documented and maintained. The relative ranking of these criteria is required to find out the most ranked criteria.

    • SP 1.3 Identify Alternative Solutions

Practices like Brainstorming sessions may stimulate innovative alternatives and in short time, we can identify many alternative solutions.

    • SP 1.4 Select Evaluation Methods

Select the evaluation methods for evaluating alternative solutions against established criteria. For example: Survey, Prototyping

    • SP 1.5 Evaluate Alternative Solutions

Alternative solutions are evaluated using the established criteria and methods which involves analysis, discussion, and review.

    • SP 1.6 Select Solutions

Sum up all the outcomes of all previous activities and select solutions from the alternatives.

Ref: Wikipedia

Other Decision Making Tools and Techniques

  • Decision Trees
  • Six Thinking Hats
  • Grid Analysis
  • Pareto Analysis
  • Cost/Benefit Analysis
  • Matched Pairs
  • Brainstorming
  • Weighted Tables
  • Delphi Technique
  • Force Field Analysis
  • Nominal Group
  • Ranking Technique
  • One Half Plus One
  • Weighted Multivoting

Author: hershey

A passion for knowledge drives me to do programming, A passion for programming drives me to create something different, A passion for creation drives me to spread the knowledge.

Share This Post On

0 Comments

  1. nice superb explaination

    Post a Reply
  2. thanks for the tutorial
    I am having a problem.
    The feature “Create SQL server database” isn’t available , I can’t select it.
    Can you help, please ?

    Post a Reply

Submit a Comment

Your email address will not be published. Required fields are marked *

More from CodeSpread:

  • Agile Encounters UnpredictabilityAgile Encounters UnpredictabilityWhat is Agile? Wikipedia says “Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through...
  • Code Quality : Myth or RealityCode Quality : Myth or RealityWhat is Quality? Generic definition of Quality “The standard of something as measured against other things of a similar kind; the degree of excellence of something” . So what i can add here is tha...
  • Risk Management in IT: Another step for QualityRisk Management in IT: Another step for QualityWhat is Risk? Risk is an uncertainty. Here, this pertains to a situation where It is difficult to decide that whether a particular event will occur or not. But if it occurs then what impact it wil...
  • Lean in ITLean in ITWikipedia says ‘Lean IT is the extension of lean manufacturing and lean services principles to the development and management of information technology (IT) products and services.’ What are these ...
  • Few lines about Static code analysisFew lines about Static code analysisStatic code analysis We divide the term into two parts: Static+code analysis. Static in programming can be referred to as non-running/non-dynamic and code analysis is a process where the code is...
  • SDLC: Importance of Requirement Analysis.SDLC: Importance of Requirement Analysis.What is SDLC? SDLC is the acronym for Software Development Life Cycle or System Development Life Cycle.It is a conceptual model that describes the stages involved in development of a software or a...
  • Scrum is AgileScrum is AgileIn our last article,Agile Part 1, we have explained basics of Agile and now we are sharing an article on SCRUM What is SCRUM? Wikipedia says “Scrum is an iterative and incremental agile software ...
  • Importance of Software MaintenanceImportance of Software MaintenanceWhat is Software Maintenance? Software maintenance is an important phase of SDLC. It is defined as a set of activities to keep the software functional and behavioral as intended for as long as ...