1. DECISION SUPPORT SYSTEM DEVELOPMENT
Mata Kuliah : CSM 211 , Management Support System
Tahun Akademik : 2014/2015
DECISION SUPPORT SYSTEM DEVELOPMENT
Pertemuan_6
6-1

2. Sasaran Pembelajaran
Understand the basic concepts of system development
Describe the four phases of the (PADI) system development life cycle “ planning, analysis, development and implementation
Understand prototyping and throwaway prototyping and why DSS are typically developed using these methods
Describe the factors that lead to DSS success or failure
Discuss the importance of project management and the necessary skills of a good project manager
Describe the three technology levels of DSS : DSS primary tools, DSS integrated tools (generators), and specific DSS
Understand the learning process that occurs during DSS development
6-2

3. PROCESS DEVELOPING A SYSTEM
Target Pembelajaran
The student can describe about development strategic of Decision Support System (DSS)
PROCESS DEVELOPING A SYSTEM
1. PLANNING
Determine business needed
Feasibility study (technical, cost, organizational)
Decision (approved) top management
Project Planning
2. ANALYSIS
Analysis of existing system
Fact Finding and Data
Making Process modeling and data modeling
6-3

4. PROCESS DEVELOPING A SYSTEM
3. DESIGN
Design user interface, form, screen, report, application programs and database
Procurement of Hardware, software, Network Infrastructure
Design system specification and program design
4. IMPLEMENTATION
Testing and code debugging
Installation and production
6-4

5. The Traditional System Development Life Cycle (SDLC)
6-5

6. CASE TOOLS
Case tools assist in the analysis phase in creating system diagram.
CASE is software to supporting system analist to accomplish phase of system development
UPPER CASE : Tools Analysis
LOWER CASE : Tools generate program application and database
Integrated CASE : combination
Example : ORACLE/9i Developer Suite, Rational Rose & RSAS ( IBM Corp),Paradigm Plus (Platinum Technology), Visible, Logic Work, Axiomsys, VS.Net
6-6

7. PROJECT MANAGEMENT Defining requirement Managing change
Obtaining executive level buy in
Setting project timelines based on realistic goals and prorities
Solving project management problems with a technology silver bullet or training (software may help use it)
6-7

8. PROJECT IMPLEMENTATION FAILURE
Lack of stakeholder involvement
Incomplete requirements
Lack of sponsor support
Unrealistic expectation
Lack of commitment from your business customers
The key factor of Failure implementaion influence of process and environment
6-8

9. FACTOR SUCCESS IMPLEMENTATION
Organization Culture
Commitment and support of top management levels
Attitude of Users and System Analist
Experience of Users
Capable and Adaptable of Developer System
FACTOR SUCCESS PROJECT IMPLEMENTATION ( process side)
Education
Supporting and involve actively of USERS
Training
6-9

10. Project Management Skills
Leadership
Communication
Conflict Resolution
Negotiation
Team Building
Listening Skills
Relationship Management
6-10

11. PROJECT SUCCES FACTORS
Support and Commitment of Executive/Top Management
End User Involve Actively
Experience Project Manager
Clear Business Objectives
Minimized Scope Project
Standard infrastructure
Organization Basic Requirement
Formal Methodology
Reliable Estimates
Skill and Commitment Staff (Team IT)
6-11

12. Project Management Tools
Software Project Management : Microsoft Project, Plan View, Active Project
Web-enable with collaboration :
Determined time and place
Human Resource and Application Programs
Portofolio Project
Web Enable
Analysis data project with comprehensive
6-12

13. ALTERNATIVE METHOLOGIES
Parallel Development
Development parallel with integrated on time implementation
2. RAD :
Quick development with standar function :
Phase Development
Prototyping
Throwaway Prototyping
6-13

14. Alternative Methodologies
a. Phase Development
Development partials as user requirement of the project
b. Prototyping
Analysis, design, implementation paralles and iteratif
Result Development can used USER to giving advice for evaluation and improvement systems
c. Throwaway Prototyping
Consolidate of SDLC with prototyping
Start development from simple of scope project
After finish prototipe, can continue with development system actualy
6-14

15. Prototyping Development Process A Rapid Application Development (RAD) Method
6-15

16. Throwaway Prototyping Development Process Another Rapid Application Development Method
6-16

17. Methodologies of Development DSS
AGILE METHODOLOGY
Rapid Prototyping, RAD to requirement system with change quickly or requirement that definition not clearly.
Characteristics :
Inputed more
Delivery partial in short time
Problem in time of integrated sistems
Methodologies of Development DSS
Prototyping
Iterative Design
Evolutionary Development
Middle Out Process
Adaptive Design
Incremental Design
6-17

18. Change Management (LEWIN)
Unfreezing
Create an awareness of the need for change and a climate receptive to change
Moving
Change the magnitude and direction of the forces defining the initial need for change by developing new methods and learning new attitudes and behaviors
Refreshing
Reinforce the desired changes that have cocurred and establish a maintainable and stable new equilibrium
6-18

19. Technologies (Tools) DSS
DSS Primary Tools ( elemen dasar)
Program languange, editor grafis, query
2. DSS Generator (software to built DSS)
Modeling, report generator, graphics, risk analysis
Spesific DSS
DSS application to specific tools
4. DSS Primary Tools to built integrate tools
6-19

20. DSS Technology Level/Tools and Web Impacts
6-20

21. Hardware DSS Personal Computer, multiprocessor, mainframe
Hardware Selection
Personal Computer, multiprocessor, mainframe
Software Selection
- Critiria multiple
- in-house, outsource or Buying
- Update software
- Fluctuation Price
- Difference tools
6-21

22. =============== thanks 4 your attention ===============
Team Development DSS
Focus Team Development to developing and improvement of DSS
Development of end-user :
Advantages :
Time more quickly
Spesification requirement user is not complety
Reduce problem implementation
Price is lower
Disadvantages :
Quality of sistem is not standard
No good documentation
Security Risk
=============== thanks 4 your attention ===============
6-22