Minggu 4,5,6,7

59
Minggu 4,5,6,7 Materi Analisa Perancangan System

description

Materi Analisa Perancangan System. Minggu 4,5,6,7. Apa itu sistem ?. Sistem informasi ?. Sistem analis ?. Metodologi. Pendekatan ssadm. Ssadm stages. sdlc. Current system. Case study. steps. Gambarkan sistem secara umum (general) - PowerPoint PPT Presentation

Transcript of Minggu 4,5,6,7

Page 1: Minggu  4,5,6,7

Minggu 4,5,6,7Materi Analisa Perancangan System

Page 2: Minggu  4,5,6,7
Page 3: Minggu  4,5,6,7

Apa itu sistem?

Page 4: Minggu  4,5,6,7

Sistem informasi?

Page 5: Minggu  4,5,6,7

Sistem analis?

Page 6: Minggu  4,5,6,7

Metodologi

Page 7: Minggu  4,5,6,7

Pendekatan ssadm

Page 8: Minggu  4,5,6,7

Ssadm stages

Page 9: Minggu  4,5,6,7

sdlc

Page 10: Minggu  4,5,6,7

Current system

Page 11: Minggu  4,5,6,7

Case study

Page 12: Minggu  4,5,6,7

steps1. Gambarkan sistem secara umum

(general) Dalam penggambaran sistem

tersebut, sebutkan siapa saja user/actor/sistem lain yang berperan di dalamnya.

Simpulkan permasalahan apa saja yang terjadi dalam sistem tersebut.

(see General Background.docx)

Page 13: Minggu  4,5,6,7

2. Investigasi lingkungan sistem

Page 14: Minggu  4,5,6,7

Fact-finding techniques Interview clarification. Forms and files users’ agreement,

Page 15: Minggu  4,5,6,7

Investigasi proses yang ada

Page 16: Minggu  4,5,6,7

DFDs

Page 17: Minggu  4,5,6,7

Elements of dfd

Page 18: Minggu  4,5,6,7

Process & Data Flow

Page 19: Minggu  4,5,6,7

External Entities & Data Stores

Page 20: Minggu  4,5,6,7

Partial DFD example

Page 21: Minggu  4,5,6,7

DFD rules Data flow diagram rulesThe analyst needs to be aware of some rules which apply to DFDs. These rules

exist not to make life difficult, but to ensure consistency in diagramming.

Process rules Processes must have both inputs and outputs. If there is no input, but there is

an output, then the output has been created from thin air. Sadly, this does not happen. If there is an input but no output, then the process is a waste of everyone’s time and should be scrapped.

Data flow rules Data flows must go through a process box. It is not allowed to have a data flow

going directly from an external entity to a data store, for example.

External entity rules The label must be a noun, e.g. SUPPLIER.

Data store rules A data flow into a data store means update the data store. A data flow from a data store means retrieve data from the data store.

See – Materi APS – Pengenalan DFD.pptx

Page 22: Minggu  4,5,6,7

Simple steps in data flow modelling The main tasks to be completed, in order,

are:1 Draw a context diagram.2 Draw a document flow diagram.3 Draw a top-level data flow diagram.4 Draw lower level data flow diagrams.

Page 23: Minggu  4,5,6,7

Context Diagram & Document Flow Diagram

Page 24: Minggu  4,5,6,7

Splitting the Steps – Study Case

Page 25: Minggu  4,5,6,7

2. Draw context diagram

Page 26: Minggu  4,5,6,7

3. Identify internal areas/departments

Page 27: Minggu  4,5,6,7

4. Draw Document Flow Diagram

Page 28: Minggu  4,5,6,7

5. Convert to top-level Data Flow Diagram

Page 29: Minggu  4,5,6,7

Level 1 Current Physical DFD

Page 30: Minggu  4,5,6,7

6. Fungsional decomposition

Page 31: Minggu  4,5,6,7

Cont…

Page 32: Minggu  4,5,6,7
Page 33: Minggu  4,5,6,7

Limitation of DFD Our current physical DFDs are now complete. They should give us a

picture of what the Medical Centre currently does. They should be understandable and be useful as a communications tool with the user. However,

there are limitations with DFDs. They don’t do everything (which is why we need other techniques). Here are a few limitations:

They don’t show us how the data is structured. They don’t show the effect of time or sequence. They may not help communicate with the user – they may be too

complex. They take a long time to draw and redraw. They may never be complete

While these limitations are real enough, the experienced analyst can use DFDs as a useful tool and not allow the limitations to become a problem.

Page 34: Minggu  4,5,6,7

Tugas1. Buat General Background dari sistem

yang anda pilih.2. Buat Problem/Requirements Catalouge3. Buat Daftar External Entiti4. Gambar Context Diagram5. Buat Daftar Internal Entiti6. Gambar Dokumen Flow Diagram7. Gambar Top Level Data Flow Diagram8. Gambar DFD Level 1 dan DFD level 2

masing – masing proses.

Page 35: Minggu  4,5,6,7

Pemodelan Struktur Data

Page 36: Minggu  4,5,6,7

Pemodelan Entitas/ Entity Entitas

Things/ Sesuatu tempat informasi berada▪ People, customer, member, student▪ Object, product, recipes,

Page 37: Minggu  4,5,6,7

Entity

Page 38: Minggu  4,5,6,7

Atribut

Bits of Data yang menerangkan Entitas Entitas MEMBER Atribut

Page 39: Minggu  4,5,6,7

Atribut

Page 40: Minggu  4,5,6,7

Keys

Cara untuk mengidentifikasi sesuatu Contoh orang, untuk

mengidentifikasi digunakan NAMA Primary Key, Key yang unik

MEMBER, MEMBERSHIP NUMBER STUDENT, NRP PATIENT, PATIENT NUMBER

Page 41: Minggu  4,5,6,7

Relationship

Hubungan antar Entitas

Page 42: Minggu  4,5,6,7

Relationship Type

Page 43: Minggu  4,5,6,7

Datastore - Entity

Page 44: Minggu  4,5,6,7
Page 45: Minggu  4,5,6,7

For Further study please read :System Analysis A Beginners Guide

Page 46: Minggu  4,5,6,7

Analisa Data System1.Data entitas yang ada pada sistem2.Masing-masing entitas dibuatkan atributnya dan contoh isiannya3. Memilih Key4. Menentukan relasi dan Tipe relasinya5. Mencocokkan datastore DFD dengan diagram entitas6. Membuat ERD.

Page 47: Minggu  4,5,6,7
Page 48: Minggu  4,5,6,7

Logicalization List Data Stores Produce the logical data store/entity cross-reference Remove time dependencies Remove names and departments from the process

boxes Change processes so that they describe what is

done to the data Remove any physical references from the process

box Make sure that the data flows refer to logical items

of data Data flows between processes should be removed

Page 49: Minggu  4,5,6,7
Page 50: Minggu  4,5,6,7

Business System Options

1. Identifikasi alternative solusi untuk menjawab hasil analisis2. Menentukan alternative solusi yang dipilih

Page 51: Minggu  4,5,6,7

Requirements Specification

Software Design

Page 52: Minggu  4,5,6,7

Elementery Process Description

Page 53: Minggu  4,5,6,7

Structured english and Decision Trees

Page 54: Minggu  4,5,6,7

Decision Tree

Page 55: Minggu  4,5,6,7

Decision Table

Page 56: Minggu  4,5,6,7

INPUT/ OUTPUT DESIGN

Page 57: Minggu  4,5,6,7

INPUT/ OUTPUT DESIGN

Page 58: Minggu  4,5,6,7

Tugas

1. Buat Analisa Data System2. Logikalisasi 3. Buat Business System Options4. Buat Elementary process descriptions5. Buat Decision Tree / Pseudo-Code /

Structured English6. Buat Design Input / Output

Page 59: Minggu  4,5,6,7