Decision Support Systems Development
Decision Support Systems Development
Decision Support Systems Development
System development life cycle (SDLC) Prototyping Forming the development team Complex process Technical issues Behavioral issues Different approaches
System
Planning
Why Build the System?
Minor Step 1. Identify business value 2. Analyze feasibility 3. Develop work plan 4. Staff project 5. Control and direct project
Deliverable System request Feasibility study Work plan Staffing plan, Project charter Project management tools CASE tool Standards list Project binders / files Risk assessment
7
Analysis
Who, What, When, Where?
Minor Step 6. Analyze problem 7. Gather information 8. Model process(es) Deliverable Analysis plan Information Process model
9. Model data
Data model
Design
How Will the System Work?
Deliverable Design plan Architecture design, Infrastructure design Interface design Data storage design Program design
9
12. Design interface 13. Design database and files 14. Design program(s)
Implementation
System Delivery
16. Installation
10
11
No project team or management support Hazy purpose; no defined schedule; ballooning scope Unclear aspects of make vs. buy decisions Few project integrations are functional out of the box Qualitative benefits No user buy in Poor project management skills No accountability / no responsibility
12
CASE Tools
Information systems for systems analysts Can help manage system development Upper CASE (assists in analysis) Lower CASE (manages diagrams and code generation) Integrated CASE (both)
13
CASE Tools
Oracle Enterprise Development Suite Rational Rose Paradigm Plus Visible Analyst Logic Works Suite AxiomSys and AxiomDsn V32 & X32 Visual Studio
14
Visible Analyst
Courtesy of Visible System Corporation (Figure 6.2)
15
17
No user involvement No clear objectives stated early No real executive sponsorship More in DSS in Focus 6.5
18
19
20
Parallel Development
Multiple copies of design and implementation phases To develop separate subsystems All come together in a single implementation phase
21
Phased Development
Break system up into versions developed sequentially Each version has more functionality Evolves into a final system Users gain functionality quickly But initial systems are incomplete
22
Prototyping
Performing analysis, design, and implementation phases concurrently, and repeatedly Users see system functionality quickly and provide feedback Decision maker learns about problem But can lose gains in repetition
23
24
Throwaway Prototyping
Like prototyping and SDLC Analysis phase is thorough Design prototypes assist in understanding the system Example: can use Excel, then Visual Basic (Figure 6.4)
25
26
Problems are semistructured or unstructured Managers and developers may not completely understand problem Use prototyping
27
Prototyping Terms
Iterative design Evolutionary development Middle-out process Adaptive design Incremental design
28
29
Why Prototyping?
Users and managers involved in every phase and iteration Learning is part of design Prototyping bypasses the information requirement definition (step 7) Short interval between iterations Initial prototype must be low cost
30
Advantages of Prototyping
Short development time Short user reaction time Improved user understanding Low cost
31
Disadvantages of Prototyping
Lack of a thorough understanding ISs benefits and costs- not using SDLC Lack of a detailed description of information needs Lack of an easy to maintain IS design Lack of a well-tested IS Unprepared users- not using SDLC
32
Specific DSS [the application] DSS integrated tools (generators) [Excel] DSS primary tools [programming languages] DSS integrated tools
Plus
Now all with Web hooks and easy GUI interfaces Relationships among the three levels (Figure 6.5)
33
General-purpose programming language Fourth-generation language (4GL) OLAP with a data warehouse or large database DSS integrated development tool (generator, engine) Domain-specific DSS generator Use the CASE methodology Integrate several of the above
35
Hardware Selection
PCs Unix workstations Network of Unix workstations Web servers Mainframes Typically use existing hardware
36
Software Selection
Complex because
At start, information requirements, etc. are unknown Hundreds of packages Software updated rapidly Price changes Many people involved in decision Language capability problems (More)
37
Different tools might be needed Many criteria Technical, functional, end-user, and managerial issues Inaccurate published software reviews Might prefer a single vendor Maybe use the AHP!!!
38
Team-Developed DSS
Substantial effort Extensive planning and organization Some generic activities Group of people to build and to manage it Size depends on
Effort Tools
39
DSS 1970s and early 1980s Large-scale, complex systems Primarily provided organizational support Team efforts
40
End-User-Developed Systems
Personal computers Computer communication networks PC-mainframe communication Friendly development software Reduced cost of software and hardware Increased capabilities of personal computers Enterprise-wide computing Easy accessibility to data and models Client/server architecture Now OLAP Balance
41
42
End-user Computing (end-user development): development and use of computer-based information systems by people outside the formal information systems areas End-users
At any level of the organization In any functional area Levels of computer skill vary Growing
43
44
Substandard or inappropriate tools and facilities Development process risks Data management risks
3. Increased Security Risks 4. Problems from Lack of Documentation and Maintenance Procedures
45
Error detection Use of auditing techniques Determine the proper amount of controls Investigate the reasons for the errors Solutions Spreadsheet errors
46
Development tools and generators Use of highly automated tools Use of prefabricated pieces Both increase the developers productivity
47
Request (query) handler System analysis and design facility Dialog management system Report generator Graphics generator Source code manager (more)
48
Model base management system Knowledge-base (management) system Object-oriented tools Standard statistical and management science tools Special modeling tools Programming languages Document imaging tools
49
Some may be integrated into a DSS generator Others may be added as needed Components used to build a new DSS Core of system includes development language or DSS generator Construction by combining programming modules Windows environment handles the interface
50
More AI Faster, more powerful computers The Web - interfaces and DB and model access More and better GSS ERM/ERP Knowledge management Better GUI Better telecommunications More research on theories More research on methods
51
Summary
DSS are complex and their development can be too SDLC Prototyping DSS technologies DSS teams or individuals End user computing Tool and generator selection can be tricky DSS research continues
52