ANALISIS dan PERANCANGAN SISTEM (INFORMASI)

(1)

ANALISIS dan PERANCANGAN

SISTEM (INFORMASI)

Catur Iswahyudi, S.Kom, S.E

email:[email protected]

Department of Informatics Engineering

Institute of Science and Technology AKPRIND Yogyakarta

(2)

Gambaran Umum

 Tujuan :

 Agar mahasiswa mengerti dan mampu menggunakan teknik-teknik

serta perangkat untuk analisis, perancangan, dan pemodelan sistem.

 Kompetensi :

 Mampu mengimplementasikan Analisis & Perancangan Sistem

menggunakan alat bantu perangkat lunak

 Prasyarat :

 Sistem Informasi (TIFS 1407)

 Penunjang :

 Prakt. Analisis & Perancangan Sistem

 Tools :

 Easy CASE

 Microsoft Access

 Microsoft Visio  Microsoft Project

(3)

MATERI

1. Pendahuluan : Kontrak Pembelajaran, RPP

2. Konsep Dasar Sistem

3. Analisis Sistem

4. Siklus Hidup Sistem

5. Perancangan Sistem Secara Umum

6. Pendekatan Perancangan Terstruktur

7. Pemodelan Sistem (DFD)

8. Flowchart

9. Perancangan Sistem Terinci (Output dan Input)

10.Perancangan Sistem Terinci (Basisdata)

11.Pengujian dan Jaminan Kualitas Sistem

12.Manajemen pengembangan sistem

(4)

Kalau diringkas

1. Perencanaan sistem (System Planning)

2. Analisis Sistem (System Analysis)

3. Perancangan Sistem (System Design)

4. Implementasi Sistem (System

Implementation)

5. Pendukung sistem dan Keamanan

(System Support and Security)

(5)

PUSTAKA

 Kenneth E. Kendall dan Julie E. Kendall, System

Analysis and Design 8th _{Edition, Pearson Education}

Ltd, 2011 (printed only)

 Gary B. Shelly dan Harry J. Rosenblatt, System

Analysis and Design 8th _{Edition, Course Technology,}

2010 (ebook available)

 Arthur M. Langer, Analysis and Design of

Information Systems 3rd _{Edition, Springer-Verlag}

London Limited, 2008 (ebook available)

 Jeffrey L. Whitten dan Lonnie D. Bentley, Systems

Analysis and Design Methods 7th _Edition,

(6)

Penilaian Acuan Patokan



Skor Nilai Akhir :

 Dasar :

SK No. 073/Skep/Rek/2008, tanggal 20 Peb 2008

 NA = 0,5*Tugas+0,2*UTS+0,2*UAS+0,1*Hadir  A  NA = 80 – 100  B  NA = 60 – 79  C  NA = 40 – 59  D  NA = 20 – 39  E  NA = 0 - 19

(7)

1-7

IS and IT

An information system (IS) is an arrangement of people, data, processes, and information

technology that interact to collect, process, store, and provide as output the information needed to support an organization.

Information technology is a contemporary term

that describes the combination of computer technology (hardware and software) with

telecommunications technology (data, image, and voice networks).

(8)

(9)

9



Project Planning



System Analysis



System Design



Construction/Implementation



Integration and Testing



Installation



Operation & Maintenance

Systems Development Life

Cycle (SDLC)

(10)

10

 Project Planning

 Put project in context

 Small part of a much larger system?

 New system or modify old?

 System Analysis

 Define user requirements

 Analyze tasks

 Develop specifications

 System Design - Define the system to be built

 Logical design

 Physical design

(11)

11

 Construction

 Write (or buy) the code

 Integration and Testing

 Unit testing, system testing, acceptance testing

 Installation

 Testing, training, conversion

 Operations & Maintenance

 Put into production  Fix bugs, add facilities

(12)

12 Perubahan lingkup / kebutuhan Desain Sistem Desain Sistem Implementasi Sistem Analisis Sistem Operasi dan Pemeliharaan Kebutuhan Sistem Kesalahan atau masalah yang tak memungkinkan implementasi dilaksanakan Sistem Siap Beroperasi Mandiri Perancangan konseptual Perancangan fisik Studi Kelayakan Analisis Kebutuhan Implementasi kurang lengkap / ada permintaan baru Pemrograman dan Pengujian Konversi

(13)

13 Desain Sistem Perancangan Fisik Analisis Sistem Perancangan Konseptual Evaluasi Alternatif Rancangan Penyiapan Laporan Rancangan Sistem Konseptual Penyiapan Spesifikasi Rancangan Rancangan Keluaran dan Masukan Rancangan Platform Rancangan Antarmuka Pemakai & Sistem Rancangan Basis data Rancangan Modul Rancangan Kontrol Implementasi Sistem Operasi dan Pemeliharaan

(14)

Generic Life Cycle Models



The Waterfall Model



Prototyping



Iterative and Incremental Development



The Unified Process Life Cycle

(15)

Waterfall Life Cycle

System System Engineering Engineering Design Design Code Construction Testing Maintenance Maintenance Analysis Requirements Analy sis Code Installation Requirements specification Functional specification

Acceptance test specifications

Unit test report

Sub-system test report System test report Acceptance test report Completed system

Software architecture specification System test specification

Design specification

Sub-system test specification Unit test specification

Change requests

(16)

TLC (

traditional life cycle

) with Iteration

System EngineeringSystem Engineering Design Design Code Construction Testing Maintenance Maintenance Requirements Analy sis Code Installation The cost of this form of iteration increases as the project progresses making it impractical and not effective

(17)

Problems with TLC

 Real projects rarely follow such a simple sequential life cycle

 Lapsed time between systems engineering and the final installation is long

 Iterations are almost inevitable in real projects but are expensive & problematic with the TLC

 Unresponsive to changes during project as iteration is difficult

 Therefore, this model is only appropriate when the requirements are well-understood

(18)

Strengths of TLC



Provide a very structured way to system

development



Tasks in phases may be assigned to

specialized teams.



Project progress evaluated at the end of each

phase, and assessment made as to whether

the project should proceed

(19)

Prototyping Life Cycle

Initial analys is Define objectives Specify Cons truct Evaluate Prototyping com pleted

• Not intended to deliver the final working system

• Quickly built up to explore some aspects of the system • May be used as part of other iterative life cycle

(20)

Prototyping – Advantages

 Early demonstrations of system functionality help

identify any misunderstandings between developer and client

 Client requirements that have been missed are

identified

 Difficulties in the interface can be identified

 The feasibility and usefulness of the system can be

tested, even though, by its very nature, the prototype is incomplete

(21)

Prototyping – Problems:



The client may perceive the prototype as part

of the final system



The prototype may divert attention from

functional to solely interface issues



Prototyping requires significant user

involvement



Managing the prototyping life cycle requires

careful decision making

(22)

The Spiral Model (Boehm, 1988) Progress towards final system Develop first increment Develop next increment Risk analysis based on initial requirements

Planning Risk analysis

User evaluation Software development

Risk analysis based on user reaction to plan

Go, no-go decision Risk assessment User evaluation of increments Further planning based on user comments Initial requirements gathering and project planning

Incremental Development

(23)

Incremental Development

 Iterative problem solving: repeats activities, each can be viewed as a mini-project

 Incremental delivery, either external or internal release

 New release = new functionality + (improved) previous release

 Several approaches to structuring iterations

 Define and implement the key system functions

 Focus on one subsystem at a time

(24)

The Unified Process System Development Life Cycle

(25)

(26)

Unified Process Life Cycle



Captures many elements of best practice



The phases are:

 Inception is concerned with determining the scope

and purpose of the project;

 Elaboration focuses requirements capture and

determining the structure of the system;

 Construction's main aim is to build the software

system;

 Transition deals with product installation and rollout.

(27)

Predictive versus adaptive approaches to the SDLC

Choose Appropriate Life Cycle

• TCL is highly predictive

• Prototyping, Spiral and UP life cycle models are highly adaptive

(28)

28

Problem Biaya

(Kasus Gunung Es)

` Analisis, Desain, Implementasi, & Konversi Pemeliharaan

(29)

29

Distribusi Usaha

Pengembangan Sistem

Analisis Sistem 20% Desain Sistem 15% Pengkodean 20% Pengujian 45%

(30)

30

Problem Kesalahpahaman

(a)

Kebutuhan pemakai menurut analis sistem

saat wawancara

(b)

Kebutuhan pemakai yang cukup direalisasikan menurut analis sistem

(c)

Pemrogram melakukan penyederhanaan

(d)

Sistem yang sebenarnya diinginkan oleh pemakai

(31)

1-31

System Designers and System Builders

System designer – a technical specialist who

translates system users’ business requirements and constraints into technical solution. She or he designs the computer databases, inputs, outputs, screens, networks, and software that will meet the system users’ requirements.

System builders – a technical specialist who

constructs information systems and components based on the design specifications generated by the system designers.

(32)

1-32

Systems Analysts

Systems analyst – a specialist who studies

the problems and needs of an organization to determine how people, data, processes, and information technology can best accomplish improvements for the business.

• A programmer/analyst includes the responsibilities of both the computer programmer and the systems analyst. • A business analyst focuses on only the