<mods:mods version="3.3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" xmlns:mods="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><mods:titleInfo><mods:title>Architectural Considerations for Decision Analysis Software</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">M.</mods:namePart><mods:namePart type="family">Danielson</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">L.</mods:namePart><mods:namePart type="family">Ekenberg</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>In classic decision theory, it is assumed that a decision-maker can assign precise numerical values corresponding to the true value of each consequence, as well as precise numerical probabilities for their occurrences. However, in real-life situations, the ordering of alternatives from most to least preferred is often a delicate matter and an adequate mathematical representation is crucial. In attempting to address real-life problems, where uncertainty about data prevails, some kind of representation of imprecise information is important and several have been proposed. However, general methods have turned out to be insufficient and we demonstrate in this article that there is not one set of coding techniques that result in the best performing software for decision analysis.</mods:abstract><mods:originInfo><mods:dateIssued encoding="iso8601">2016-08</mods:dateIssued></mods:originInfo><mods:originInfo><mods:publisher>IOS Press</mods:publisher></mods:originInfo><mods:genre>Book Section</mods:genre></mods:mods>