05 System Analyst

SYSTEMS ANALYSIS

This repository of slides is intended to support the named chapter. The slide repository should be used as follows:
Copy the file to a unique name for your course and unit.Edit the file by deleting those slides you dont want to cover, editing other slides as appropriate to your course, and adding slides as desired.Print the slides to produce transparency masters or print directly to film or present the slides using a computer image projector.
Each slide includes instructor notes. To view those notes in PowerPoint, click left on the View Menu; then click left on Notes View sub-menu. You may need to scroll down to see the instructor notes.

The instructor notes are also available in hard copy as the Instructor Guide to Accompany Systems Analysis and Design Methods, 5/ed. Contact your Irwin/McGraw-Hill sales representative if you need a hard copy.

Chapter 1 Players in the Systems Game

Chapter Map

No additional notes


Systems Analysis vs. Systems Design

Systems analysis teknik pemecahan masalah yang menguraikan sistem kedalam komponen-komponen untuk mempelajari bagaimana bagian-bagian komponen tsb bekerja & berinteraksi untuk mencapai tujuan sistem.

Conversion Notes

In previous editions, we used the term systems synthesis for systems design. We thought it best to change to reinforce the text title and course subject matter.

Teaching Notes

Systems modeling corresponds precisely with this classical definition of systems analysis and design.


Systems Analysis vs. Systems Design

Systems design (systems synthesis) adalah teknik pemecahan masalah yang melengkapi systems analysis yang merakit bagian-bagian komponen sistem kembali ke sistem yang lengkap(sistem yang lebih baik). Termasuk penambahan, penghapusan, & pengubahan bagian-bagian terhadap sistem yang asli.

Conversion Notes

In previous editions, we used the term systems synthesis for systems design. We thought it best to change to reinforce the text title and course subject matter.

Teaching Notes

Systems modeling corresponds precisely with this classical definition of systems analysis and design.


Information Systems Analysis

Analisis sistem informasi didefinisikan sebagai fase-fase pembangunan dalam projek yang fokus utamanya pada masalah-masalah bisnis, tidak tergantung pada teknologi tertentu yang dapat atau akan digunakan untuk mengimplementasikan solusi terhadap masalah tsb.

Conversion Notes

Technically, in this edition we return the decision analysis phase to the systems analysis chapter. At first glance, that may appear to violate the nontechnical focus of the book. In practice, this is merely a transition to technical concerns. The decision analysis phase does look at technical feasibility, but it focuses more on economic, operational, and schedule feasibilityall of which are firmly in the business domain.


Context of Systems Analysis

Teaching Notes

This context comes directly from Chapter 3. The blue processes and the blue and black data flows define systems analysis.


Repository
Repository adalah lokasi (sekumpulan lokasi) dimana system analysts, systems designers, dan system builders menyimpan semua dokumentasi yang berhubungan dengan 1 atau lebih sistem atau proyek.
Network directory dari computer-generated files yang berisi project correspondence, reports, dan dataCASE tool dictionary atau encyclopedia (Chapter 3)Dokumentasi tercetak (binders dan system libraries)Intranet website interface untuk komponen-komponen diatas
No additional notes


Model-Driven Analysis Methods

Model-driven analysis menekankan pada penggambaran model sistem utk mendokumentasi dan memvalidasi sistem yang sudah ada dan/atau sistem yang diusulkan. Pada akhirnya, model sistem menjadi blueprint untuk pendesainan & konstruksi sistem.

Model adalah representasi dari realitas atau pengelihatan. banyak model menggunakan gambar untuk merepresentasikan realitas atau pengelihatan.

Ct: flowchart, hierarchy chart, organization chart

Saat ini pendekatan model driven ddiperkuat dengan peralatan terotomasi seperti : Visio Profesioanal, juga penggunaan CASE yang berbasis reposititory seperti System Architect, Visible Analist,atau Rational ROSE -> analisis konsisten dan lengkap

Teaching Notes

In previous editions, we tried to distinguish between information systems and computer applications (the latter being a subset of the former). This created more confusion with students than it was worth.

Some books use the term computer technology. We prefer the more contemporary term, information technology as a superset of computer technology.


Model-Driven Methods

Structured analysis adalah teknik model-driven, process-centered yang digunakan untuk menganalisa sistem yang ada, mendefinisikan kebutuhan bisnis untuk sistem baru, atau keduanya. Model disini adalah gambar yang mengilustrasikan bagian komponen sistem: proses-proses, input, output, dan file-file yang berhubungan dengannya.,misal dengan DFD

Conversion Notes

We played down the methodology coverage in this edition. Several reviewers felt it was too much, too soon.

In some books, information engineering is considered a structured technique as is structured analysis. We cannot argue this. Both methods use the same diagrammatic tools to model a system.

Information engineering is more complex and comprehensive than the oversimplified presentation in this editions chapter. But we have found few organizations that still practice pure IE. But many organizations still practice data-driven analysis and design.


Model-Driven Methods

Information engineering (IE) adalah teknik model-driven dan data-centered, tetapi process-sensitive untuk merencanakan, menganalisa, dan mendesain SI. Model IE berupa gambar yang mengilustrasikan dan mensinkronkan data dan proses sistem. (ERD)

Object-oriented analysis (OOA) atau Analisis Berorientasi Obyek : adalah teknik model-driven yang mengintegrasikan data dan proses kedalam konstruksi yang disebut objek. Model OOA berupa gambar yang mengilustrasikan objek sistemdari berbagai perspektif seperti struktur & behavior.

Conversion Notes

We played down the methodology coverage in this edition. Several reviewers felt it was too much, too soon.

In some books, information engineering is considered a structured technique as is structured analysis. We cannot argue this. Both methods use the same diagrammatic tools to model a system.

Information engineering is more complex and comprehensive than the oversimplified presentation in this editions chapter. But we have found few organizations that still practice pure IE. But many organizations still practice data-driven analysis and design.


A Simple Process Model

Teaching Notes

It is not the intent to teach the tool in this chapter. DFDs will be taught in Chapter 8.


Diagram aliran data (DFD) di atas membantu organisasi memvisualisasikan proses-proses merekaModel tersebut menunjukkan aliran data diantara dan melalui proses-proses dan menunjukkann tempat data disimpan

A Simple Data Model

Teaching Notes

It is not the intent to teach the tool in this chapter. ERDs will be taught in Chapter 7.


IE untuk mengintegrasikan dan mensikronkan model-model data dan proses

Pemodelan obyek menggunakan UML(Unified Modelling Language)

+Admit()

+Regsiter for Classes()

+Withdraw()

+Change Address()

+Calculate GPA()

+Graduate()

-ID Number

-Name

-Grade Point Average

STUDENT

+Create a Course()

+Delete from Course Master()

+Change in Course Master()

-Subject

-Number

-Title

-Credit

COURSE

+Add()

+Drop()

+Complete()

+Change Grade()

-Semester

-Division

-Grade

TRANSCRIPT COURSE

1

1

has record for>

0..*

0..*

Teaching Notes

It is not the intent to teach the tool in this chapter. Object Models using the UML will be taught in Part Five, Module A.


OOA suatu rancangan yang mengintegrasikan antara data dan prosesObyek : pembungkusan data yang mendiskripsikan orang,objek,tempat,kejadian atau sesuatu yang berlainan dengan semua proses yang diijinkan untuk menggunakan atau memperbarui data

Pendekatan Analisis Sistem Terakselerasi

Antara lain:

Discovery prototyping

Rapid architecture analysis

No additional notes


Pendekatan Analisis Sistem Terakselerasi

Pendekatan analysis terakselerasi menekankan pada konstruksi prototipe untuk mengidentifikasi kebutuhan bisnis & kebutuhan user untuk sistem baru secara lebih cepat.

Prototype: contoh sistem diinginkan yang berskala kecil, tidak lengkap, tapi berfungsi

Menggunakan pendekatan RAD (rapid Aplication Development ) menggunakan CASE repository al : MSAccess

No additional notes


Accelerated Analysis Methods

Discovery prototyping (requirements prototyping) digunakan untuk mengidentifikasi kebutuhan bisnis user dengan mengijinkan mereka bereaksi terhadap implementasi yang quick-and-dirty ( bijaksana dan efektif tapi tanpa cacat/efek samping yang tidak diinginkan ) dari kebutuhan-kebutuhan tersebut.

Menggunakan teknologi pengembangan cepat untuk membantu para pengguna menemukan persyaratan bisnis mereka

Misal MS Access : membuat dbase, form input, laporan -> untuk lebih cepat membuat prototype pengguna

Teaching Notes

Some might consider rapid architecture analysis to be a model-driven approach since it results in system models. We elected to classify it as an accelerated analysis approach because of the technique used to build those models.

Teaching Tip

Demonstrate reverse engineering to transform an Access database into a data model.


Accelerated Analysis Methods

Rapid architecture analysis adalah

pendekatan yang mencoba menurunkan model sistem dari sistem yang sudah ada atau dari discovery prototypes.

Gabungan dari pendekatan model driven dan
analisis terakselerasi
Teknologi Reverse engineering membaca kode program untuk basisdata, program aplikasi, dan/atau user interface dan secara otomatis menghasilkan model sistem yang ekuivalen.
Teaching Notes

Some might consider rapid architecture analysis to be a model-driven approach since it results in system models. We elected to classify it as an accelerated analysis approach because of the technique used to build those models.

Teaching Tip

Demonstrate reverse engineering to transform an Access database into a data model.


Metode Penemuan Persyaratan
Requirements discovery (Penemuan Persyaratan) terdiri dari teknik-teknik yang digunakan oleh system analyst untuk mengidentifikasi atau mengekstrak masalah-masalah sistem dan kebutuhan solusi dari komunitas user. Fact-finding (information gathering)/Teknik Penemuan Fakta : adalah sekumpulan teknik klasik yang digunakan untuk mengumpulkan masalah, peluang, kebutuhan solusi, dan prioritas sistem. Sampling: dokumentasi,laporan formulir,file database yang adaResearch: buku2 yang relevan, kunjungan ke situs2,solusi orang lainObservation :kerja sistem dan lingkungan kerjaQuestionnaires dan surveys : manajemen dan penggunaInterviews:manajer,user dan staf teknis
Conversion Notes

In this edition, we have separated joint application development (JAD) into its component parts, joint requirements planning (JRP) and joint application design (also JAD). Only JRP is applicable to this chapter.


Metode Penemuan Persyaratan
Teknik Joint requirements planning (JRP)/perencanaan persyaratan gabungan : menggunakan pertemuan bersama untuk mengajak semua system owners, system users, systems analysts, dan beberapa systems designer dan builders melakukan analisis sistem bersama. -> digunakan bersama dengan model driven lalu digabung dengan RAD
Conversion Notes

In this edition, we have separated joint application development (JAD) into its component parts, joint requirements planning (JRP) and joint application design (also JAD). Only JRP is applicable to this chapter.


Metode Desain ulang Proses Bisnis

Business process redesign adalah aplikasi dari metode analisis sistem untuk tujuan mengubah & memperbaiki proses bisnis dasar dari sebuah organisasi, tidak tergantung pada IT.

No additional notes


Systems Analysis Phases
Preliminary Investigation Phase
Problem Analysis Phase
Requirements Analysis Phase
Decision Analysis Phase
Conversion Notes

The phases correspond to the following fourth edition terms:

Preliminary investigation = former survey phase
Problem analysis = former study phase
Requirements analysis = former definition phase
Decision analysis = former configuration phase


Preliminary Investigation Phase Context

Conversion Notes

In this edition we are trying hard to reinforce the building blocks.

Teaching Notes

The focus system owner perspectives.


Preliminary Investigation Phase Tasks

Teaching Notes

This is called a task diagram for a phase.

It is only a guideline. Each project will adapt these tasks to the project at hard. Tasks may be added, split, or deleted according to the methodology and route used.

The dashed line is a control flow (as contrasted to a solid data flow). In this case, it represents a decision that determines whether the next task is necessary.


Sample Request for System Services

Teaching Notes

Not all businesses have a formal document to initiate projects.


Problem Statements

Teaching Notes

Alternatively, this information could be documented in a business memo or report.


Problem Analysis Phase Context

Conversion Notes


Teaching Notes

The focus is on both system owner and system user perspectives.

We are looking at the building blocks of the existing system.


Problem Analysis Phase Context

No additional notes


Cause-and-Effect Analysis

Cause-and-effect analysis adalah teknik dimana masalah-masalah dipelajari untuk mengetahui penyebab & efeknya.

Dalam kenyataannya, efek dapat merupakan gejala dari masalah dasar yang lebih dalam, dimana pada gilirannya, harus dianalisa penyebab & efeknya sampai suatu saat penyebab & efek tsb tidak menghasilkan gejala dari masalah yang lain.

Teaching Tip

Analyze a problem using cause-and-effect analysis.

If you know fishbone diagrams, demonstrate cause-and-effect analysis using the diagrams.


System Improvement Objectives

Objective adalah pengukuran kesuksesan. Merupakan sesuatu yang diharapkan untuk dicapai, jika diberikan sumber daya yang cukup.
Menurunkan jumlah rekening pelanggan yang tidak ditagih sebanyak 50 persen dalam tahun depan. Menaikkan sebanyak 25 persen jumlah peminjaman yang dapat diproses selama shift 8 jam.
Teaching Tips

Formulate objectives as an in-class exercise.


System Improvement Objectives

Menurunkan sebanyak 50 persen waktu yang dibutuhkan untuk menjadualkan kembali produksi saat sebuah workstation mengalami malfunction.

Constraint adalah sesuatu yang membatasi fleksibilitas dalam mendefinisikan solusi untuk sebuah objective. Biasanya, constraint tidak dapat diubah.

Ct: deadlines, budget

Jenis-jenis: schedule, cost, technology, policy

Teaching Tips

Formulate objectives as an in-class exercise.


Cause-and-Effect / System Improvement Objectives

PROBLEMS, OPPORTUNITIES, OBJECTIVES, AND CONSTRAINTS MATRIX

No additional notes


Requirements Analysis Phase Context

Conversion Notes


Teaching Notes

The focus is on system user perspectives.

Requirements can be expressed in narrative, model, and prototype forms, or any combination thereof.


Requirements Analysis Phase Tasks

Teaching Notes

Some of the tasks are completed in parallel.


Business Requirements

Functional requirement adalah deskripsi dari aktivitas-aktivitas & layanan-layanan yang harus disediakan oleh sistem.

Nonfunctional requirement adalah deskripsi dari fitur-fitur, karakteristik, dan batasan-batasan yang lain yang mendefinisikan sistem yang memuaskan.

Ct: unjuk kerja, kemudahan dipelajari & digunakan, budget, biaya, dll.

No additional notes


Logical System Models

Logical system models menggambarkan apa sistem itu atau apa yang harus dikerjakan sistem itubukan bagaimana sistem akan diimplementasikan. Karena logical models menggambarkan kebutuhan yang pokok dari sistem, kadang disebut dengan essential system models.
Process models (e.g., data flow diagrams)Data models (e.g., entity relationship diagrams)Interface models (e.g., context diagrams)Object models (e.g., Uniform Modeling Language diagrams)
Teaching Notes

The opposite is physical system models, which will be introduced in the systems design chapter.


A Simple Interface Model

No additional notes


Requirements Statement

No additional notes


Decision Analysis Phase Context

Conversion Notes


Teaching Notes

The focus is on system user and system designer perspectives.

Notice the transition to technical concerns leading to a system proposal that includes data, process, and interface elements.


Decision Analysis Phase Tasks

No additional notes


Feasibility Analyses
Technical feasibility. Apakah solusi mudah dilaksanakan secara teknis? Apakah staf kita memiliki keahlian teknis untuk mendesain & membangun solusi?
Operational feasibility. Akankah solusi memenuhi kebutuhan user? Sampai tingkat mana? Bagaimana solusi bisa mengubah lingkungan kerja user? Bagaimana pendapat user tentang solusi semacam itu?
Economic feasibility. Apakah solusi tsb. cost-effective?
Schedule feasibility. Dapatkah solusi didesain dan diimplementasikan dalam periode waktu yang ditentukan?
No additional notes


Candidate Systems Matrix

(Continued)

No additional notes


Candidate Systems Matrix

No additional notes


Feasibility Matrix

No additional notes


05 System Analyst

Documents

Transcript of 05 System Analyst