Constructing a DSS

Dekar Urumsah DSS 1

What is a DSS? (early definition)

 DSS is as a system intended to support

managerial decision makers in
semistructured decision situations.
 DSS were to be an adjunct/add-on to
decision makers to extend their
capabilities but not to replace their
judgment.
DSS Definitions
 Little (1970) defines DSS as “a model-based
set of procedures for processing data and
judgement to assist a manager in his decision
making”.
 Moore and Chang (1980) defines DSS as
extenddible systems capable of supporting ad
hoc data analysis and decision modeling,
oriented toward future planning, and used at
irreguler, unplanned intervals.
DSS Definitions
 Keen (1980) defines DSS as the product
of a developmental process in which the
DSS user, the DSS builder and the DSS
itself are all capable of influencing one
another, resulting in system evolution
and patterns of use.
 Thus, DSS is to support and improve
decision making.
 DSS vs EDP
Dimension DSS EDP

Use Active Passive

User Line and Staff Clerical

management
Goal Effectiveness Mechanical efficency

Time horizon Present and future Past

Objective Flexibility Consistency

Prototyping Versus Life Cycle
 SDLC (Systems Development Life Cycle)
- Analysis then design then implementation
- Assumes information requirements can be determined in one
hit and then proceed to design and then implementation
- nature of DSS is that problems are unstructured and thus
requirements are not well understood
- need to acknowledge learning of users about
requirements during design and implementation

Dekar Urumsah DSS 6

Prototyping
 other names - "evolutionary", "iterative"
 "build DSS prototype quickly, obtain
immediate feedback from users, improve and
repeat cycle"

Dekar Urumsah DSS 7

Prototyping activities
 Identify an important sub-problem jointly
- high value interest to user
- build relationship between user and developer
 Develop a small but usable system
- quickly go through analysis, design, construction,
implementation
- a mock-up?
- form of entry, reporting - engine later

Dekar Urumsah DSS 8

Prototyping activities (ctd.)
 evaluate constantly
- helps keep cost/benefit in balance
- decide whether to further refine or stop
 refine, expand and modify the system in
cycles
- Analysis, design, construction, implementation,
evaluation repeated in each successive refinement
- repeat until relatively stable and comprehensive
system go forward

Dekar Urumsah DSS 9

Features / Advantages
 High user involvement
 balance - user uses and evaluates, while developer
designs and implements
 user has a joint and active role rather than reactive
or passive
 mutual learning can occur through the iterative
process
 short development time
 low cost
 improved mutual understanding of system needs and
capabilities
Dekar Urumsah DSS 10
Features / Advantages
 Note : Prototyping for multi-user DSS is more
complex and may have to be more formal,
structured e.g.:
- establish checkpoints to define each usage/evaluation
cycle
- formalise lines of communication between users and
developers

Dekar Urumsah DSS 11

ROMC
 Representations, Operations, Memory, Control
 a framework for DSS analysis and design
 process independent
 It is user-oriented approach for stating system
performance requirements

Dekar Urumsah DSS 12

ROMC
 Representations
- to communicate problem
- Usually visual
 Operations
- to manipulate/influence representations
 Memory aids
- to assist user in linking representations and operations
 Control mechanisms
- to integrate representations, operations and memory aids

Dekar Urumsah DSS 13

Assumptions
 Decision makers prefer graphic representations
 intelligence/ design / choice framework can be
applied to DSS analysis
 memory aids are useful
- reports, windowing, hierarchies, metaphors ("drill down")
 DSS should support individual's style, skills and
knowledge
 Decision maker expects to exercise direct personal
control so must understand and be comfortable with
input and output

Dekar Urumsah DSS 14

Flexibility in DSS
 Need for flexibility of DSS in solving, modifying,
adapting and evolving arises because of
- difficulty of specifying functional requirements in advance
- users do not know or cannot articulate until they have an
initial system to react to
- concept of task and problem changes as the system is used
- solutions derived through DSS are subjective
- wide variations among individuals in how they use DSS

Dekar Urumsah DSS 15