Unit V

DSS Development

Arun Mishra
9893686820
arunjimishra@gmail.com
Introduction
Development of DSS is a complicated
process.
It involve issues ranging from Technical to
behavioral
There are a variety of tools available, roughly
falling into three categories:
Primary development tools
DSS generators
Specific DSS applications
Tools for DSS Development
Primary development tools these include
programming languages & database
query mechanisms.
DSS generators at a higher level of
technology, these possess integrated, diverse
functionality, including decision modeling,
sophisticated reporting, and database
management.
Specific DSS applications for some
problem types there may be a commercially
available package that can be acquired and
customized.
Approaches to DSS Development

There are mainly three approaches of DSS

Development:

System Development Life Cycle SDLC

End-User Development

Rapid Prototyping
System Development Life Cycle
Generalized DSS Development Process
DSS Development Process
1. Problem diagnosis formal identification
of the problem context
2. Identification of objectives and
resources specific objectives must be
described and available resources identified
3. System analysis three categories of
requirements (functional, interface, and
coordination) are established.
4. System design the determination of
components, structure, and platform
DSS Development Process
5. System construction an iterative
prototyping approach, with small but constant
refinement employed
6. System implementation where testing,
evaluation, and deployment occurs
7. Incremental adaptation this final stage
is a continual refinement of the activities of
the earlier six stages.
Rapid Application Development Methodologies
(RAD)
Quick development allowing fast, but limited
functionality i.e. system can be developed quickly &
users can obtain some functionality as soon as
possible. It includes:
Phased development
System broken up into a series of versions
Sequential serial development with incremental functionality
Prototyping
Rapid development of portions of projects for user input and
modification
Small working model or may become functional part of final
system
Throwaway prototyping
Simple development platforms
Used when the project idea is not clear
Prototype vs. Throwaway Prototype
Agile Development
A new form of rapid prototyping which
attempts to bypass much of the formalism
inherent in the system-development life cycle,
and even that of prototyping
Used for:
Unclear or rapidly changing requirements
Speedy development
General Characteristics of the Agile:
Heavy user input
Self organized team
Incremental delivery with short time frames
Tend to have integration problems
Create simple content
Test oriented
Several design models
Reasons for Prototyping
DSS development is done through proto typing
for the following reasons:
Users and managers are involved in every
phase and iteration.
Learning is explicitly integrated into the design
process
Prototyping essentially bypasses the formal life-
cycle
A key criterion associated with prototyping is the
short interval between iterations.
The initial prototype must be low-cost
Reasons for Prototyping
Short steps
Planning
Analysis
Design
Prototype
Immediate stakeholder feedback to ensure that
the development is proceeding correctly
Iterative
In development of prototype
Within the system in general
Evaluation is integral part of the development process
Control mechanism
End user development
User is also the developer
Single user systems
Fast, and to the users specifications
User may not use proper development
techniques / tools
May have many errors in design
User may need extensive support from IT people
May not be systematic
End user development
Decision-makers and knowledge workers
develop to solve problems or enhance
productivity
Advantages
Short delivery time
The prerequisites of extensive and formal user requirements
specifications are eliminated
Reduced implementation problems
Low costs
Risks
Quality may be low
May have lack of documentation
Security risks may increase