Anda di halaman 1dari 45

Analisis Perancangan SI

STMIK Tasikmalaya

Analisis Perancangan
SI
Teuku Mufizar, S.Kom., M.Kom
0425038701
Analisis Perancangan SI
STMIK Tasikmalaya

TOPIK 5
SYSTEM LIFE CYCLE (SLC),
SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC),
SYSTEMS DEVELOPMENT METHODOLOGIES,
SYSTEMS DEVELOPMENT PARADIGM,

2
Analisis Perancangan SI
STMIK Tasikmalaya

TOPIK 5
SYSTEM LIFE CYCLE
(SLC)

3
System Life Cycle (SLC)
System Life Cycle (SLC) = pemfaktoran umur
hidup sebuah sistem informasi ke dalam dua
tahap,
1) Pengembangan Sistem, dan
2) Operasi dan Perawatan Sistem

Pertama Anda membangunnya, kemudian


Anda menggunakan dan merawatnya.
Pada akhirnya, Anda kembali ke
pengembangan ulangn sebuah sistem baru.
4
System Life Cycle (SLC)

5
System Life Cycle (SLC)
Proses pengembangan sistem, berasal dari
siklus hidup sistem.
Ada 2 kejadian kunci yang memicu sebuah
perubahan dari satu tahap ke tahap lainnya
Konversi (convertion) = Ketika sistem berputar
dari pengembangan ke operasi dan perawatan
Penuaan/penurunan (obsolescence) = muncul dan
sebuah sistem berputar dari operasi dan
perawatan ke pengembangan ulang.

6
Analisis Perancangan SI
STMIK Tasikmalaya

TOPIK 5
SYSTEMS DEVELOPMENT LIFE CYCLE
(SDLC)

7
Systems Development Life Cycle (SDLC)
SDLC = sebuah proses pengembangan
terstandarisasi yang mendefinisikan satu set
aktivitas, metode, praktik terbaik, barang siap
dikirim, dan perangkat terotomasi yang akan
digunakan oleh pengembang sistem dan
manajer proyek untuk mengembangkan dan
secara berkesinambungan memperbaiki
sistem informasi dan perangkat lunak.

8
Systems Development Life Cycle (SDLC)

Planning

Implementation Analysis

Design

9
Project Phases
1. Planning: Mengapa membangun sistem?
Mendefinisikan Masalah, Menetapkan Aktifitas/Jadwal,
Analisis Kelayakan, Pembagian Tim,
2. Analysis: Siapa, Apa, Kapan, Dimana sistem dibangun nanti?
Pengumpulan Kebutuhan, pemodelan sistem/ proses bisnis
3. Design: Bagaimana sistem bekerja nantinya?
Perancangan program, Perancangan Antarmuka , Perancangan
Basis Data
4. Implementation: Pembangunan Sistem and Pelayanan
Pembangunan Sistem, Pengujian , Dokumentasi and Instalasi
Planning
1. Mendefinisikan Masalah = Analisis PIECES
2. Menetapkan Aktifitas dan Penjadwalan =
Gant Chart, Diagram PERT
3. Melakukan Analisis Kelayakan
Kelayakan Teknis
Kelayakan Ekonomis
Kelayakan Organisasi
4. Pembentukan tim dan job desk

(System Proposal)
Analysis
1. Pengumpulan Kebutuhan dengan menjawab pertanyaan :
Siapa yang akan menggunakan sistem?
Apa yang bisa dilakukan oleh sistem?
Kapan sistem bisa digunakan ?
2. Menginvestigasi sistem berjalan
Pemodelan Sistem
3. Mengidentifikasi kemungkinan Perubahan
4. Membangun konsep sistem yang baru

(Business Process Model)


Design
1. Perancangan Program (Flowchart Program)
2. Perancangan Antar Muka
Perancangan Menu Utama, Login
Perancangan Input, Proses dan Output
3. Perancangan Database
Teknik Perancangan Basis Data
• Normalisasi/ ERD
• Relasi Tabel
• Kamus Data

(System Specification)
Implementation
Kontruksi
Sistem baru dibangun dan diuji
Sering pengujian merupakan aktifitas yg cukup lama
Pengujian
Pengujian Unit
Pengujian Integrasi
Pengujian Sistem
Pengujian Penerimaan User
Instalasi
Sistem lama dimatikan
Sistem Baru dijalankan
Processes and Deliverables
Process Product

Planning System Proposal

Analysis System Modeling

Design System Specification

New System with


Implementation Testing/Maintenance Plan
SDLC and Deliverables

Planning
(System Proposal)

Implementation Analysis
(New System) (System Modeling)

Design
(System Specification)
Analisis Perancangan SI
STMIK Tasikmalaya

TOPIK 5
SYSTEMS DEVELOPMENT
METHODOLOGIES

17
Apa itu Methodologi?
Sebuah pendekatan formal untuk meng-
implementasikan SDLC (urutan tahapan and
pelaksanaan)
Menulis kode tanpa mengetahui kebutuhan
sistem mungkin bisa dilakukan unuk program
kecil, tetapi jarang terjadi untuk sistem yang
besar.
Major Methodologies
1. Structured Design
Waterfall method
Parallel development
2. RAD Development
Phased Development
Prototyping
Throw-away Prototyping
3. Agile Development
Extreme Programming (XP)
Scrum
Structured Design Methodology
Projects move methodically from one to
the next step
Generally, a step is finished before the
next one begins
Waterfall Method
Parallel Development
Rapid Application Development
1. Phased development
A series of versions

2. Prototyping
System prototyping

3. Throw-away prototyping
Design prototyping
Rapid Application Development

Critical elements to speed up the SDLC:


CASE tools
Visual programming languages
Code generators
RAD: Phased Development
Break overall system into a series of
versions
Each version has Analysis, Design, and
Implementation
Output from on version is the input to
the next
Incorporate ideas, issues, lessons
learned in one version into the next
version
Phased Development
RAD: Prototyping
Analysis, Design, Implementation are
performed concurrently
Start with a "quick-and-dirty" prototype
Provides minimal functionality
Repeat process, refining the prototype
each time
Stop when prototype is a working system
RAD: Prototyping
RAD: Throw-Away Prototyping
Use prototypes only to understand
requirements
Example: use html to show UI
Prototype is not a working design
Once requirements are understood, the
prototypes are thrown away
The system is then built using SDLC
RAD: Throw-Away Prototyping
Agile Development
Just a few rules that are easy to learn and
follow
Streamline the SDLC
Eliminate much of the modeling and documentation
Emphasize simple, iterative application development
Examples include:
Extreme Programming (XP)
Scrum
Dynamic Systems Development Model (DSDM)
Extreme Programming (XP)
“Core Values” of XP
1. Communication – All to All
2. Simplicity – KISS, refactoring
3. Feedback – Embrace Change
4. Courage – Quality First, test and efficient coding
Extreme Programming (XP)
1. User Stories about system do
2. Code small program using defined
standards
• Naming conventions
• Coding practices
3. User Feedback
4. Repeat
Extreme Programming (XP)
Selecting the Appropriate
Methodology
1. Clarity of User Requirements
2. Familiarity with Technology
3. System Complexity
4. System Reliability
5. Short Time Schedules
6. Schedule Visibility
Selecting the Right Methodology
Analisis Perancangan SI
STMIK Tasikmalaya

TOPIK 5
SYSTEMS DEVELOPMENT
PARADIGM

37
Oriented and Diagrams
1. Process-oriented DFD
2. Data-oriented ERD
3. Object-oriented (data + process)
UML
Systems Development Approach
and Diagrams
1. DFD + ERD => SSAD ( Structured
System Analys Design )
2. UML => OOAD ( Object Oriented
Analys Design )
Systems Development Paradigm
and Programming
1. SSAD ( Structured System Analys Design )
= Structured Programming/ Modular
Programming
2. OOAD ( Object Oriented Analys Design ) =
Object Oriented Programming (OOP)
Data Flow Diagram
Diagram Konteks

DFD LEVEL

41
Entity Relationship Diagram
ERD

42
UML Diagrams
Use-Case
Diagram Statechart
Class Diagram Diagram add file

DocumentList

Use Case 1 FileMgr Document

add( )
name : int
Actor A Actor B fetchDoc( ) delete( )
docid : int
sortByName( ) numField : int Writing
add file [ numberOffile==MAX ] /
flag OFF
get( )
open( ) read() fill the
Use Case 2 close( ) code..
Openning
FileList read( )
sortFileList( )
fList create( )
fillDocument( ) close file
add( )
delete( )
1

Use Case 3 Reading


close file
Closing

rep

File
Repository

(from Persistence)

name : char * = 0

readDoc( )
readFile( )
read( )
GrpFile

read( )
open( )
create( )
Deployment
fillFile( )

Collaboration 9: sortByName ( )
Repository DocumentList
Diagram
Diagram 1: Doc view request ( )
mainWnd : MainWnd
L
FileManager
Window95
Windows95

Windows95

2: fetchDoc( ) ¹®¼-°ü¸®
Ŭ¶óÀ̾ðÆ®.EXE

4: create ( ) gFile : GrpFile Document ¹®¼-°ü¸® ¾ÖÇø´

8: fillFile ( ) Windows
NT

user : Clerk Solaris

fileMgr : FileMgr ¹®¼-°ü¸® ¿£Áø.EXE

3: create ( ) GraphicFile Alpha


UNIX
ÀÀ¿ë¼-¹ö.EXE
6: fillDocument ( )
File FileList Windows
NT

IBM

7: readFile ( ) Mainframe

5: readDoc ( )
document : Document
repository : Repository
µ¥ÀÌŸº£À̽º¼-¹ö

user
mainWnd fileMgr :
FileMgr
document :
Document
gFile repository
Component
ƯÁ¤¹®¼-¿¡ ´ëÇÑ º¸±â¸¦ 1: Doc view request ( )

Diagram
Target
»ç¿ëÀÚ°¡ ¿äûÇÑ´Ù.

2: fetchDoc( )

3: create ( )

4: create ( )

5: readDoc ( )

È-ÀÏ°ü¸®ÀÚ´Â Àоî¿Â
¹®¼-ÀÇ Á¤º¸¸¦ ÇØ´ç ¹®¼-
°´Ã¼¿¡ ¼³Á¤À» ¿äûÇÑ´Ù.
6: fillDocument ( )

8: fillFile ( )
7: readFile ( )
System
Forward and
È-¸é °´Ã¼´Â ÀоîµéÀÎ 9: sortByName ( )
°´Ã¼µé¿¡ ´ëÇØ À̸§º°·Î
Á¤·ÄÀ» ½ÃÄÑ È-¸é¿¡
º¸¿©ÁØ´Ù.

Sequence Reverse
Diagram Engineering
Referensi
1. Kenneth E. Kendall and Julie E Kendall, Systems Analysis and
Design 8th Edition, Prentice Hall, 2010
2. Jeffrey L. Whitten, et al, Systems Analysis and Design ,
McGraw Hill C, 2012
3. Systems Analysis and Design in a Changing World, 4th
Edition
4. Romi Satrio Wahono, Systems Analysis and Design , Slide
Perkuliahan, 2014
5. Universitas Indonesia, Systems Analysis and Design , Faculty
Of Computer Science
Q&A

45