Rational Unified Process

1. Process Overview 1.1. Objectives Pengenalan Rational Unified Process Rational Unified Prosess pertama kali diperkenalkan oleh Ivar Jacobson, Grady Booch, dan James Rumbaugh yang disebut Three Amigos The Unified Software Development Process Definisi kunci konsep models workflows and workers phases and iterations

1.2. Unified Process Use-Case Driven Merupakan sistem iterasi dengan menggunakan user (manusia atau sistem eksternal) dan menggambarkan fungsional requirement.

Arsitektur Centric Arsitektur Struktur elemen dan organisasinya, kolaborasi dan perilaku. Memperkenalkan dan menghias bentuk atau hubungan. form bagian dari function and form Iterasi (langkah-langkah workflow) and penambahan (penambahan fungsional) Setiap iterasi adalah proyek kecil yang menyediakan fungsionalitas dari use case yang dipilih dan mengalamtkan resiko yang paling signifikan. Setiap iterasi terdiri atas setiap development workflow

1.3. Workflows in a Waterfall view

Requirements
Feature lists Domain models Use cases Customer language External view

Analysis

Design

Implementation

Test
Test cases, procedures, components Integration and system tests Feed results back into process

Unambiguous Physical Implement models Technologies details Consistent use and -ilities (source, cases Many scripts, Developer abstractions, binaries, language subsystems, executables, Internal view interfaces etc.) Sets solution Detailed Distribute architecture Formal executable Conceptual components Informal models across Few abstractions, computing subsystems, nodes interfaces Unit test

1.4. Models in the Unified Process

Requirements workflow Use-case model Analysis workflow Analysis model Design workflow Design model, deployment model Implementation workflow Implementation model Test workflow Test model 1.5. Essential Software Process

Conceptual Models

Transform
Formal Models Implementation Domain

1.6. Model Development

Transform Models
Inception
U A D D I T

Elaboration
U A D D I T

Construction
U A D D I T

Transition
U A D D I T

Models

1.7. Core Workflows Applied in each iteration 1.8. Model Requirements

List feature Model bisnis atau model utama. Objek yang paling penting; sesuatu yang siap atau kejadian yang terjadi. relationships: Bagian dari, type dari, assocsiasi dengan, dsb.

Model Use-case process dan workflow workers/actors dan work produk (objek utama) 1.9. Analyze Requirements

Model Analisis Statement yang lebih tepat dari requrement dibandingkan dengan model utama use cases. Bahasa dari developer Struktur dan mengorganisasikan requirement Set rata-rata system architecture; structures system design

1.10.

Requirements dan Analysis

Analysis Model Language of developer Structures internal views of system Developers use to shape design and implementation No redundancies and inconsistencies Outlines how to realize functionality (first-cut design)

Requirements Model Language of customer Structures external views of system Contract between customer and developer Probably redundant, inconsistent, etc. Captures functionality

1.11.

Design

Mengembangkan dan pemahaman model dari tujuan dan ketidak fungsian requrement dan hubungan-hubungan (constrain-constrain). Teknologi Bahasa perograman, sistem operasi, networks, distribution, databases, userinterface technology, dsb. Sistem -ilities Keaslian , kecepatan, security, maintainability, dsb. Identifikasi subsystems, interfaces dan object classes Identifikasi development team task partitioning 1.12. Analysis dan Design Implementasi Rencana system integrasi untuk setiap iterasi. kecil, kemungkinan unutk memanage langkah skope dari tes dan debug. Distribusikan komponen executable kedalam distribusi bentuk computerisasi. Implementasiskan design class dan subsystems (source code, scripts, binaries, executables, libraries, dsb.)

Unit test komponen Integrate komponent (compile dan link) 1.13. Test

Rencana integrasi test dan system test termasuk dalam setiap iterasi. Design dan implementasi kasus test Apa yang akan di test, procedure test, executable komponen test Kecepatan tests dan penanganan systematically yang ada. Dampak balik iterasi kedalam workflows yang lain(implementation, design, requirement)

1.14.
Requirements
Feature lists Domain models Use cases Customer language External view

Ringkasan Workflow
Analysis Design Implementation
Implement details (source, scripts, binaries, executables, etc.) Distribute executable components across computing nodes Unit test

Test

Unambiguous models Physical Consistent use cases Technologies and -ilities Developer language Many abstractions, Internal view subsystems, interfaces Sets solution architecture Detailed Conceptual Formal Informal models Few abstractions, subsystems, interfaces

1.15.

Worker

Worker: aturan dari pengguna (atau orang) yang menggunakan software development User Project manager System analyst Architect Designer Tester dsb. 1.16. Iterasi dan Fase

Fase (didalam satuan waktu) Inception Elaboration Construction Transition Multiple iterations per phase Risk management

Do the hard stuff first! Masing-masing wokflow (requirements, analysis, design, implementation, test) dilakukan disetiap iterasi Inception Phase

1.17.

Inception: establish business case Ruang lingkup, batasan Kandidat Arsitektur Resiko-resiko proof-of-concept prototype (System dapat memuaskan keinginan konsmen) user interface key algorithms throw-away Perkiraan sumberdaya kebutuhan dalam pengembangan Elaboration Phase

1.18.

Elaboration: do-ability architectural baseline Mencakup fungsionalitas use cases untuk ~80% dari fungsionalitas quality levels resiko yagn signifikan berubah menjadi aktifitas yang berupa waktu dan harga resource requirements bid schedule, staff, cost Construction Phase

1.19.

Construction: build initial operational capability All use-cases are identified, described and realized (mapped to design models) Finish analysis (remaining ~50%) Finish design, implementation and test (remaining ~90%) Protect architectural integrity Monitor and mitigate risks

1.20.

Transition Phase

Transisi : bergerak ke user environment site preparation (physical) operating environment update (hardware, operating systems, communications protocols, shared components, etc.) manual lengkap dan semua dokumentasi konfigurasi perangkat lunak untuk lingkungan user yang tertentu Correct defects from beta-test feedback Modify software as needed Generic iteration workflow

1.21.

rencana Iteration Identifikasi dan manage resiko Memprioritaskan use case Identifikasi dan mengalokasikan sumber daya (orang, uang, facilitas, capital, alatalat, komponen, dsb.) Empat bentuk rencana : waktu, milestones, iterasi, iteratsi kretirea kompleks. Execute Iterasi Inti workflows dan semua workers Akses Iterasi dan bentuk Kretirea tidak berbentuk; criteria diri sendiri Mengulangi itersi selanjutnya. Mengevaluasi perubahan dari model set. Mengembangkan proses, alat-alat, latihan, dsb. 1.22.

Kesimpulan

The Rational Unified Process mendefinisikan proses pengembangan software

yaitu use-case driven architecture centric iterative dan incremental The Rational Unified Process dapat diidentifikasi dari workflows yang membuat model: requirement, analysis, design/deployment, implementation, test workers yang implementasikan workflows: user, manager, analysis, architect, designer, tester, dsb. development phases dan iterations: inception, elaboration, construction, transition activities dalam generic iteration: planning, workflow execution, assessment