RPL. (Rekayasa Perangkat Lunak) SOFTWARE PROSES TP - AKN BOJONEGORO

dokumen-dokumen yang mirip
REKAYASA PERANGKAT LUNAK I ALIF FINANDHITA, M.T. - TEKNIK INFORMATIKA UNIKOM 1

REKAYASA PERANGKAT LUNAK I

The Process. A Layered Technology. Software Engineering. By: U. Abd. Rohim, MT. U. Abd. Rohim Rekayasa Perangkat Lunak The Process RPL

THE SOFTWARE PROCESS

Teknik Informatika S1

PROSES DESAIN. 1. Metodologi Pengembangan Sistem

3. The Software Process

SOFTWARE PROCESS MODEL I Disiapkan oleh: Umi Proboyekti, S.Kom, MLIS


Teknik Informatika S1

Teknik Informatika S1

Mata Kuliah Testing & Implementasi Sistem Program Studi Sistem Informasi 2014/2015 STMIK Dumai -- Pertemuan 2 --

SDLC Concepts. Muhammad Yusuf D3 Manajemen Informatika Universitas Trunojoyo

Review of Process Model. SE 3773 Manajemen Proyek Teknologi Informasi *Imelda Atastina*

REKAYASA PERANGKAT LUNAK I ALIF FINANDHITA, M.T. - TEKNIK INFORMATIKA UNIKOM 1

Software Engineering - Defined

System Development Life Cycle (SDLC)

Review Rekayasa Perangkat Lunak. Nisa ul Hafidhoh

Software Proses. Model Proses Perangkat Lunak. Pengembangan Perangkat Lunak. Framework activities 3/20/2018. System Development Life Cycle (SDLC)

Systems Development Life Cycle (SDLC)

SOFTWARE PROCESS MODEL

Ratna Wardani. Department of Electronic Engineering Yogyakarta State University

MODUL 4 Unified Software Development Process (USDP)

Manajemen Proyek. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 1

DASAR-DASAR PERANCANGAN PERANGKAT LUNAK

INTRODUCTION TO SOFTWARE ENGINEERING

1 BAB 1 PENDAHULUAN. 1.1 Latar Belakang

Tugas Softskill. Universitas Gundarma. : Sistem Informasi Manajemen. : Waldhi Supriono NPM : Kelas : 2 DB 12

Aplikasi yang pendekatannya sistematis, disiplin, bisa terukur untuk pengembangan operasional dan pembuatan software. Tools. Methods.

A Layered Technology

SOFTWARE PROCESS & METHOD

Pengembangan Sistem Informasi

SOFTWARE ENGINEERING (REKAYASA PERANGKAT LUNAK)

BAB 1 PENDAHULUAN. Excel dalam mencatat aliran data transaksi perusahaan. Penggunaan program

PENGENALAN. Perancangan Perangkat Lunak. (Software Engineering) Bertalya Program Pascasarjana Univesitas Gunadarma

Pertemuan 2 SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)

Metode-Metode Pengembangan Desain Aplikasi

BAB I PENDAHULUAN.

REKAYASA PERANGKAT LUNAK. Ramadhan Rakhmat Sani, M.Kom

SDLC : Project Planning

Rekayasa Perangkat Lunak

Pengembangan Sistem Informasi

PENGANTAR MANAJEMEN PROYEK PERANGKAT LUNAK MATA KULIAH MANAJEMEN PROYEK PERANGKAT LUNAK

Software Development Life Cycle (SDLC)

BAB I PENDAHULUAN I-1

Paktikum : 4-7 Judul Praktikum : System Development Life Cycle (SDLC)

Hanif Fakhrurroja, MT

PENGEMBANGAN PERANGKAT LUNAK

BAB II KONSEP PEMBANGUNAN SISTEM DARI PERSPEKTIF SOFTWARE ENGINEERING

Proses Pengembangan 1

PERTEMUAN 2 METODE PENGEMBANGAN SISTEM

Hanif Fakhrurroja, MT

BAB I PENDAHULUAN. 1.1 Latar Belakang

Produk perangkat lunak tersebut:

SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC) Siklus Hidup Perangkat Lunak (SWDLC/Software Development Life Cycle)

FAKULTAS TEKNIK UNIVERSITAS NEGERI YOGYAKARTA SILABUS REKAYASA PERANGKAT LUNAK

PERTEMUAN 2 METODE PENGEMBANGAN SISTEM

REKAYASA PERANGKAT LUNAK

Models of Software Evolution: Life Cycle Model. Aktivitas dalam daur hidup perangkat lunak. Aktivitas dalam daur hidup perangkat lunak

APLIKASI PERANGKAT LUNAK

MINGGU 6. Proses Perancangan. Suzan Agustri

Successful Project Management. Manajemen Proyek Teknologi Informasi

What is Behind the Names???

METODOLOGI PENGEMBANGAN SOFTWARE

Pertemuan 2 SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC) POKOK BAHASAN

REKAYASA PERANGKAT LUNAK 1

SILABUS MATAKULIAH. Indikator Pokok Bahasan/Materi Aktifitas Pembelajaran

Jenis Metode Pengembangan Perangkat Lunak

Jaka Adi Laksana Mohammad Asyam L Nareswara Driyanggara S Nur Adi Prasetyo Dewi Irbaya MH Aisyah Fathia Putri

STMIK AMIKOM YOGYAKARTA

Pengembangan Sistem Informasi

Garis-garis Besar Program Pembelajaran (GBPP)

Proyek Pengembangan Sistem Informasi

08 Pengembangan & Pemeliharaan Sistem Informasi [Bagian 1]

Adam Hendra Brata Teknik Informatika FILKOM UB Semester Genap 2015/2016

Testing dan Implementasi Sistem

Sekolah Tinggi Teknologi Adisutjipto Yogyakarta

STMIK AMIKOM YOGYAKARTA

Tujuan Perkuliahan. PENGANTAR RPL (Pert. 2 chapter 1 Pressman) Agenda. Definisi Software (Perangkat Lunak) Lunak) 23/09/2010

Rekayasa Perangkat Lunak DEPARTEMEN PENDIDIKAN NASIONAL UNIVERSITAS PENDIDIKAN INDONESIA 2008

Metodologi Pengembangan Sistem Informasi

Tren Terbaru Pengembangan Software (Software Development Life Cycle)

BAB I PENDAHULUAN. 1.1 Latar Belakang

BAB 4 Pendekatan-Pendekatan Pengembangan Sistem

BAB I PENDAHULUAN Latar Belakang

MAKALAH REKAYASA PERANGKAT LUNAK ( SIKLUS HIDUP PERANGKAT LUNAK )

BAB 6 METODOLOGI SIKLUS HIDUP SISTEM

ARTIKEL KERJA PRAKTEK RANCANG BANGUN SISTEM INFORMASI PENCATATAN PENJUALAN PADA CAFE WARUNK KOPI NOSTALGILA MENGGUNAKAN PHP DAN MYSQL

Software Quality Assurace 9/18/ :50 PM 1

PENDAHULUAN PENGEMBANGAN SISTEM INFORMASI

Software Process. Tim RPL. Program Studi Teknik Informatika

Analisis Pemilihan Penerapan Proyek Metodologi Pengembangan Rekayasa Perangkat Lunak

SIKLUS REKAYASA PERANGKAT LUNAK (SDLC)

yang disusun dalam suatu aliran kerja/work flow dimana tiap elemen proses di atas berelasi satu sama lain

Rekayasa Perangkat Lunak

Metodologi pengembangan sistem METODOLOGI PENGEMBANGAN SISTEM INFORMASI DIAN PALUPI RINI, M.KOM 1

ABSTRAK. Keyword : analisis, gap, resiko, audit kepatuhan. iii. Universitas Kristen Maranatha

BAB III LANDASAN TEORI

(Source: Pressman, R. Software Engineering: A Practitioner s Approach. McGraw-Hill, 2010)

ANALISIS DAN PERANCANGAN SISTEM (APS) Pengantar APS

Transkripsi:

RPL (Rekayasa Perangkat Lunak) SOFTWARE PROSES TP - AKN BOJONEGORO

SubBahasan 1. Software Engineering Layers 2. Software Process 3. Software Process Models

Software Engineering (SE) Layers Software engineering is a layered technology.

SE Layers 1. A Quality Focus Fokus terhadap kualitas SE yang dibangun. Setiap pendekatan rekayasa harus mengacu kepada A Quality Focus. The bedrock

SE Layers 2. Process Dasar untuk mengontrol manajemen dari software. Menentukan dalam beberapa hal, diantaranya: Metode yang digunakan. Hasil Produk : model, dokumen, data, laporan, form. Batasan produk Terjaminnya kualitas Pengelolaan perubahan dengan baik The foundation

SE Layers 3. Method Technical how-to s building software. Cakupannya diantaranya: Communication. Requirements analysis. Design modelling Program construction Testing Support

SE Layers 4. Tools Provide automated or semiautomated support for the process and the method. computer-aided software engineering : alat terintegrasi dengan SE.

SubBahasan 1. Software Engineering Layers 2. Software Process 3. Software Process Models

Software Process Bukan berarti cara membangun software Merupakan sekumpulan aktivitas yang tujuannya adalah pengembangan dan evolusi perangkat lunak. A generic process framework for software engineering encompasses five activities: Communication Planning Modelling Contruction Deployment

Software Process 1. Communication Before any technical work can commence It is critically important to communicate and collaborate with the customer (stakeholders). Untuk memahami tujuan stakeholder terkait deskripsi proyek dan pengumpulan data.

Software Process 2. Planning Any complicated journey can be simplified if a map exists. A software project is a complicated journey, and the planning activity creates a map that helps guide the team as it makes the journey. The map (software project plan) mendefinisikan tugas teknis perangkat lunak, resiko, sumber daya, produk pekerjaan yang harus diproduksi, dan jadwal kerja.

Software Process 3. Modelling Whether you re a landscaper, a bridge builder, an aeronautical engineer, a carpenter, or an architect, you work with models every day Sketsa (sketch) akan memberikan pemahaman lebih tentang RPL.

Software Process 4. Construction This activity combines: code generation (either manual or automated) and the testing that is required to uncover errors in the code.

Software Process 5. Deployment The software (as a complete entity or as a partially completed increment) is delivered to the customer who evaluates the delivered product and provides feedback based on the evaluation.

SubBahasan 1. Software Engineering Layers 2. Software Process 3. Software Process Models

Software Process Models [SPM] 1. Linear Process Flow 2. Iterative Process Flow 3. Evolutionary Process Flow 4. Parallel Process Flow

Software Process Models [SPM] 1. Linear Process Flow 2. Iterative Process Flow 3. Evolutionary Process Flow 4. Parallel Process Flow

SPM 1. Linear Process Flow A linear process flow executes each of the five framework activities in sequence, beginning with communication and culminating with deployment

SPM 1. Linear Process Flow Prescriptive Models The Waterfall Model Disebut juga classic life cycle Suggests a systematic, sequential approach to software development that begins with customer specification of requirements and progresses through planning, modeling, construction, and deployment, culminating in ongoing support of the completed software

Software Process Models [SPM] 1. Linear Process Flow 2. Iterative Process Flow 3. Evolutionary Process Flow 4. Parallel Process Flow

SPM 2. Iterative Process Flow An iterative process flow repeats one or more of the activities before proceeding to the next

SPM 2. Iterative Process Flow Prescriptive Models Incremental Process Models

Software Process Models [SPM] 1. Linear Process Flow 2. Iterative Process Flow 3. Evolutionary Process Flow 4. Parallel Process Flow

SPM 3. Evolutionary Process Flow An evolutionary process flow executes the activities in a circular manner. Each circuit through the five activities leads to a more complete version of the software

SPM 3. Evolutionary Process Flow Prescriptive Models Prototyping

SPM 3. Evolutionary Process Flow Prescriptive Models The Spiral Model.

Software Process Models [SPM] 1. Linear Process Flow 2. Iterative Process Flow 3. Evolutionary Process Flow 4. Parallel Process Flow

SPM 4. Parallel Process Flow A parallel process flow executes one or more activities in parallel with other activities (e.g., modeling for one spect of the software might be executed in parallel with construction of another aspect of the software).

SPM 4. Parallel Process Flow Prescriptive Models Rapid Application Development (RAD)

YUK DISKUSI

PERSPECTIVE PROCESS Berdasarkan strategi yang ada, pelajari lebih lanjut dan deskripsikan tentang keuntungan dan kelebihan dari masing-masing persrpective.

Software Process