Chapter 1:
Introduction to Systems Analysis and Design
Alan Dennis, Barbara Wixom, and David Tegarden
John Wiley & Sons, Inc.
Slide 1
Chapter 1
Slide 2
1996
Survei by The Standish Group
46% of all corporate IS project were
abandoned before completion
1996
Survei by General Accounting Office
53% of all U.S. Government IS were
abandoned
Slide 3
 Analysts tried to build
wonderful systems without
understanding the
organization
 The primarily goal is to create
value for the organization
Systems analyst adalah orang utama yang
menganalisa
proses
business,
mengidentifikasikan kesempatan perbaikan,
dan pendesainan sistem informasi untuk
menerapkan konsep ini.
Merupakan hal yang penting untuk memahami
dan mengembangkan melalui melatih skill yang
diperlukan
untuk
mendesain
dan
mengimplementasikan sistem informasi baru
yang sukses
Slide 4
Slide 5
The project
Bergerak sistematis pada fase – fase dimana
setiap fase memiliki output
Menghasilkan project deliverables
Menggunakan deliverables pada
implementasi
Hasil pada actual information system
menggunakan gradual refinement
Slide 6
Kenapa sistem informasi harus di bangun?
Bagaimana project team menanganinya?
?
Slide 7
Step #1 (Project initiation)
System request
Project sponsor
IS Department
Generate the request
Feasibility analysis
Technical feasibility
Economic feasibility
Organization feasibility
Slide 8
Can we build it?
Will it provide business value?
If we build, will it be used?
IS Approval Commitee
(Steering commitee)
Step #2 (Enters project management)
Project manager
Workplan
Staff the project
Techniques
Help the project team control and direct the project
Slide 9
Siapa yang menggunakan sistem tersebut?
Apa yang dilakukan sistem tersebut?
Dimana sistem tersebut digunakan?
?
Slide 10
Project team
Investigate any
current system(s)
Slide 11
Identifies improvement
opportunities
Develops a concept
for the new system
Analysis strategy
Developed to guide the project team’s effort
Analysis of the current system (as-is system) & it’s problems
Ways to design a new system (to be system)
Requirement gathering
System proposal
= analysis + system concept + models
Presented to teh project sponsor and other key decision makers
Decide whether the project sholud be continue to move forward
Slide 12
Bagaimana sistem akan beroperasi
Hardware, software, network infrastructure, user
interface ....
?
Slide 13
Design strategy
Whether the system will be operate by the company’s own programmer
Whether the system will be outsourced to another firm
Whether the company will buy an existing software package
Basic Architecture Design
Database and file specifications
Program design
Slide 14
Construction
System is built and tested to ensure it performs as designed
Installation
Direct customer approach
Parallel convertion approach
Phase conversion strategy
Support plan
Forma and informal post-implementation review
Slide 15
A “Simple” Process for Making Lunch
Slide 16
Processes and
Deliverables
Process
Planning
Project Plan
Analysis
System Proposal
Design
Implementation
Slide 17
Product
System
Specification
New System and
Maintenance Plan
SYSTEM DEVELOPMENT
Methodologies
Slide 18
Pendekatan formal pada rangkaian tahap
Menulis code tanpa kejelasan mungkin berhasil
untuk program yang kecil, tapi apakah berhasil
pada sistem yang besar?
Slide 19
Berpindah secara metodis dari satu langkah ke
yang lain
Secara umum, sebuah langkah selesai sebelum
masuk ke langkah berikutnya
Slide 20
Slide 21
Pros
Identifies systems
requirements long
before programming
begins
Cons
Design must be
specified on paper
before programming
begins
Long time between
system proposal and
delivery of new
system
Slide 22
Slide 23
Rapid Application Development (RAD)
Phased Development
Prototyping
Throw-Away Prototyping
Slide 24
Critical elements
CASE tools
JAD (Join Application Design) sessions
Fourth generation/visualization programming
languages
Code generators
Slide 25
Phased development
A series of versions
Prototyping
System prototyping
Throw-away prototyping
Design prototyping
Agile Development
Extreme Development
Slide 26
Slide 27
Slide 28
Clarity of User Requirements
Familiarity with Technology
System Complexity
System Reliability
Short Time Schedules
Schedule Visibility
Slide 29
Slide 30
Slide 31
Business analyst
System analyst
Infrastructure analyst
Change management analyst
Project manager
Slide 32
Slide 33
The Systems Development Lifecycle berisi 4
tahapan: Planning, Analysis, Design, and
Implementation
The major development methodologies:
Structured design


the waterfall method
Parallel development
RAD development

Prototyping (regular and throwaway)
Agile development

Slide 34
XP streamline SDLC
Ada 5 peran penting dalam team: business
analyst, systems analyst, infrastructure analyst,
change management analyst dan project
manager.
Slide 35