Software Engineering: Process

Presentasi berjudul: "Software Engineering: Process"— Transcript presentasi:

1 Software Engineering: Process
Romi Satria Wahono

2 Romi Satria Wahono SD Sompok Semarang (1987) SMPN 8 Semarang (1990)
Object-Oriented Programming Romi Satria Wahono SD Sompok Semarang (1987) SMPN 8 Semarang (1990) SMA Taruna Nusantara, Magelang (1993) B.Eng, M.Eng and Ph.D in Software Engineering from Saitama University Japan ( ) Universiti Teknikal Malaysia Melaka (2014) Research Interests: Software Engineering, Intelligent Systems Founder dan Koordinator IlmuKomputer.Com Peneliti LIPI ( ) Founder dan CEO PT Brainmatics Cipta Informatika

3 Course Contents -1- Introduction to Software Engineering
What is Software What is Software Engineering Discipline and Curriculum of Software Engineering Software Engineering Profession Profession, Ethics and Certification Software Industry and Market Internet Business Model and Trends

4 Course Contents -2- Software Engineering Process Software Construction
Software Development Life Cycle (SDLC) Software Development Methodologies Software Development Notation (UML) and Tools Object-Oriented Paradigm Software Construction Software Construction Process Estimating the Size of Software Project

5 Course Contents -3- Software Quality Assurance
The Uniqueness of Software Quality Assurance What is Software Quality Software Quality Factor Software Testing Software Engineering Research Computing Research Methodology Research Trends in Software Engineering Case Study: Developing Research Proposal in Software Engineering Field

6 Software Engineering Process

7 Contents Software Development Life Cycle (SDLC)
Software Development Methodologies Software Development Notation and Tools Object-Oriented Paradigm

8 1. Systems Development Life Cycle (SDLC)
Object-Oriented Programming 1. Systems Development Life Cycle (SDLC)

9 Systems Development Life Cycle (SDLC)
Object-Oriented Programming Systems Development Life Cycle (SDLC) Planning Analysis Design Implementation

10 Project Phases Planning: Why build the system?
Object-Oriented Programming Project Phases Planning: Why build the system? System request, feasibility analysis, project size estimation Analysis: Who, what, when, where will the system be? Requirement gathering, business process modeling Design: How will the system work? Program design, user interface design, data design Implementation: System construction and delivery System construction, testing, documentation and installation

11 Planning Identifying business value (System Request)
Object-Oriented Programming Planning Identifying business value (System Request) Lower costs Increase profits Analyze feasibility Technical Feasibility Economic Feasibility Organizational Feasibility Estimating the size of project (System Proposal)

12 Analysis Requirement gathering by answering the questions:
Object-Oriented Programming Analysis Requirement gathering by answering the questions: Who will use the system? What will the system do? When will it be used? Investigate the current system Identify possible improvements Develop a concept for new system (Business Process Model)

13 Design (System Specification) Program Design (UML Diagrams)
Object-Oriented Programming Design Program Design (UML Diagrams) What programs need to be written Exactly what each program will do User Interface Design How users interact with system Forms / reports used by the system Data Design (ER Diagrams) What data is to be stored What format the data will be in Where the data will be stored (System Specification)

14 Implementation Construction Testing Installation
Object-Oriented Programming Implementation Construction New system is built and tested Often testing is the longest part Testing Unit Testing Integration Testing System Testing User Acceptance Test Installation Old system is turned off New system is turned on

15 Processes and Deliverables
Object-Oriented Programming Processes and Deliverables Process Product Planning Analysis Design Implementation System Proposal System Specification New System with Testing/Maintenance Plan

16 SDLC and Deliverables Planning Analysis (System Specification)
Object-Oriented Programming SDLC and Deliverables Planning (System Proposal) Analysis (System Specification) Design (System Specification) Implementation (New System)

17 2. Systems Development Methodologies
Object-Oriented Programming 2. Systems Development Methodologies

18 Object-Oriented Programming What Is a Methodology? A formalized approach to implementing the SDLC (series of steps and deliverables) Writing code without a well-thought-out system request may work for small programs, but rarely works for large ones

19 Major Methodologies Structured Design RAD Development
Object-Oriented Programming Major Methodologies Structured Design Waterfall method Parallel development RAD Development Phased Development Prototyping Throw-away Prototyping Agile Development Extreme Programming (XP) Scrum

20 Structured Design Methodology
Object-Oriented Programming Structured Design Methodology Projects move methodically from one to the next step Generally, a step is finished before the next one begins

21 Waterfall Method

22 Pros - Cons of the Waterfall Method
Object-Oriented Programming Pros - Cons of the Waterfall Method Pros Cons Design must be specified on paper before programming begins Identifies systems requirements long before programming Begins, it minimizes change to the requirements as the project proceed (mature) Long time between system proposal and delivery of new system Rework is very hard

23 Object-Oriented Programming Parallel Development Addresses problem of time gap between proposal and delivery General process: Breaks project into parallel subproject Integrates them at the end

24 Parallel Development romi@romisatriawahono.net
Object-Oriented Programming Parallel Development

25 Rapid Application Development
Object-Oriented Programming Rapid Application Development Phased development A series of versions Prototyping System prototyping Throw-away prototyping Design prototyping

26 Rapid Application Development
Object-Oriented Programming Rapid Application Development Critical elements to speed up the SDLC: CASE tools Visual programming languages Code generators

27 RAD: Phased Development
Object-Oriented Programming RAD: Phased Development Break overall system into a series of versions Each version has Analysis, Design, and Implementation Output from on version is the input to the next Incorporate ideas, issues, lessons learned in one version into the next version

28 Object-Oriented Programming

29 RAD: Phased Development
Object-Oriented Programming RAD: Phased Development Pros Cons Gets useful system to users quickly Most important functions tested most Initial system is intentionally incomplete System requirements expand as users see versions

30 Object-Oriented Programming RAD: Prototyping Analysis, Design, Implementation are performed concurrently Start with a "quick-and-dirty" prototype Provides minimal functionality Repeat process, refining the prototype each time Stop when prototype is a working system

31 RAD: Prototyping romi@romisatriawahono.net Object-Oriented Programming

32 RAD: Prototyping Pros Cons
Object-Oriented Programming RAD: Prototyping Pros Cons Fast paced. Hard to conduct careful, methodical analysis Gets working system to users quickly Reassures users that the project is progressing Initial design decisions have long term staying power Problems may come to light late in design, requiring re-design Quickly refines true requirements

33 RAD: Throw-Away Prototyping
Object-Oriented Programming RAD: Throw-Away Prototyping Use prototypes only to understand requirements Example: use html to show UI Prototype is not a working design Once requirements are understood, the prototypes are thrown away The system is then built using SDLC

34 RAD: Throw-Away Prototyping
Object-Oriented Programming RAD: Throw-Away Prototyping

35 Agile Development Just a few rules that are easy to learn and follow
Object-Oriented Programming Agile Development Just a few rules that are easy to learn and follow Streamline the SDLC Eliminate much of the modeling and documentation Emphasize simple, iterative application development Examples include: Extreme Programming (XP) Scrum Dynamic Systems Development Model (DSDM)

36 Extreme Programming (XP)
Object-Oriented Programming Extreme Programming (XP) “Core Values” of XP Communication – All to All Simplicity – KISS, refactoring Feedback – Embrace Change Courage – Quality First, test and efficient coding

37 Extreme Programming (XP)
Object-Oriented Programming Extreme Programming (XP)

38 Scrum Together with a user, the project members form a Scrum Team consisting of 5–9 people During discussions with the Product Owner, the goal of the Sprint is determined and the prioritized functionality is broken down into detailed tasks The team is self-organized and the members have a joint responsibility for the results Each Sprint enhances the product’s market value and adds new functions and improvements that can be delivered to the customer

39 Scrum

40 Scrum

41 Scrum

42 Scrum

43

44 XP vs Scrum vs Lean XP deals with how to work with programming
Scrum deals with how the project is organized and planned Lean Development deals with which comprehensive principles should apply for the entire development organization

45 Selecting the Right Methodology
Object-Oriented Programming Selecting the Right Methodology Clarity of User Requirements Familiarity with Technology System Complexity System Reliability Short Time Schedules Schedule Visibility

46 Selecting the Right Methodology
Object-Oriented Programming Selecting the Right Methodology

47 Exercise: Selecting Methodology
Object-Oriented Programming Exercise: Selecting Methodology Suppose you are an analyst for the Roanoke Software Consulting Company (RSCC), a large consulting firm with offices around the world. The company wants to build a new knowledge management system that can identify and track the expertise of individual consultants anywhere in the world based on their education and the various consulting projects on which they have worked. Assume that this is a new idea that never done before been attempted in RSCC or elsewhere. RSCC has an international network, but the offices in each country may use somewhat different hardware and software. RSCC management wants the system up and running within a year.

48 3. Software Development Notation and Tools
Object-Oriented Programming 3. Software Development Notation and Tools

49 Analysis Design Paradigm and Diagrams
Data-oriented  DFD Process-oriented  Flowchart Object-oriented (data + process)  UML

50 Booch, Jacobson, Rumbaugh
Sejarah UML In the 90s many people creating OO diagramming languages Three different ones created by Grady Booch, Ivar Jacobson, James Rumbaugh Joined forces with Rational (company) to create Unified Modeling Langauge (UML) Booch, Jacobson, Rumbaugh

51 Sejarah UML  UML 2.4

52 What is the UML? UML: Unified Modeling Language
UML can be used for modeling all processes in the development life cycle and across different implementation technologies (technology and language independent) UML is the standard language for visualizing, specifying, constructing, and documenting the artifacts of a software-intensive system UML is a communication tool – for the team, and other stakeholders

53 Why Modeling? Business Process Computer System
Modeling captures essential parts of the system (James Rumbaugh) Business Process Computer System Visual Modeling is modeling using standard graphical notations

54 The Triangle of Success in Software Dev.
Notation: Standard Tools: Support Standard and Process Process: Customer-Oriented Methodology

55 UML Tools Rational Rose Visual Paradigm Enterprise Architect
Microsoft Visio Star UML Netbeans UML Plugin

56 Collaboration Diagram Forward and Reverse Engineering
UML Diagrams Use-Case Diagram Statechart Diagram The point to be made is that the UML is the langua ge we use to visuall y model. Since it is a widely adopte d standa rd, it facilitat es the unders tandin g and comm unicati on of the visual model s we create. Activity and object diagrams are not shown on this slide. These diagrams can be used to model workflows in business process engineering. Class Diagram Use Case 1 GrpFile read( ) open( ) create( ) fillFile( ) rep Repository name : char * = 0 readDoc( ) readFile( ) (from Persistence) FileMgr fetchDoc( ) sortByName( ) DocumentList add( ) delete( ) Document name : int docid : int numField : int get( ) close( ) sortFileList( ) fillDocument( ) fList 1 FileList File read() fill the code.. Actor A Actor B Use Case 2 Use Case 3 Deployment Diagram Collaboration Diagram 9: sortByName ( ) Document FileManager GraphicFile File Repository DocumentList FileList mainWnd : MainWnd Window95 Windows95 1: Doc view request ( ) Windows95 L 2: fetchDoc( ) 4: create ( ) gFile : GrpFile ¹®¼­°ü¸® Ŭ¶óÀ̾ðÆ®.EXE ¹®¼­°ü¸® ¾ÖÇø´ 8: fillFile ( ) Windows user : Clerk NT Solaris fileMgr : FileMgr ¹®¼­°ü¸® ¿£Áø.EXE 6: fillDocument ( ) 3: create ( ) Alpha Windows UNIX NT ÀÀ¿ë¼­¹ö.EXE 5: readDoc ( ) 7: readFile ( ) Mainframe IBM repository : Repository document : Document µ¥ÀÌŸº£À̽º¼­¹ö Component Diagram mainWnd fileMgr : FileMgr document : Document gFile repository user Target System Visual modeling with the UML makes application architecture tangible, permitting us to assess it in multiple dimensions. How portable is it? Can it exploit expected advances in parallel processing? How can you modify it to support a family of applications? We have discussed the importance of architectural resilience and quality. The UML enables us to evaluate these key characteristics during early iterations — at a point when design defects can be corrected before threatening project success. Advances in forward and reverse engineering techniques permit changes to an application’s model to be reflected automatically in its source code, and changes to its source code to be automatically reflected in its model. This is critical when using an iterative process, in which we expect such changes with each iteration. »ç¿ëÀÚ°¡ ¿äûÇÑ´Ù. ƯÁ¤¹®¼­¿¡ ´ëÇÑ º¸±â¸¦ 1: Doc view request ( ) 2: fetchDoc( ) 3: create ( ) 4: create ( ) 5: readDoc ( ) È­ÀÏ°ü¸®ÀÚ´Â Àоî¿Â °´Ã¼¿¡ ¼³Á¤À» ¿äûÇÑ´Ù. ¹®¼­ÀÇ Á¤º¸¸¦ ÇØ´ç ¹®¼­ 6: fillDocument ( ) 7: readFile ( ) 8: fillFile ( ) Forward and Reverse Engineering °´Ã¼µé¿¡ ´ëÇØ À̸§º°·Î È­¸é °´Ã¼´Â ÀоîµéÀÎ Á¤·ÄÀ» ½ÃÄÑ È­¸é¿¡ º¸¿©ÁØ´Ù. 9: sortByName ( ) Sequence Diagram Module 1 - Best Practices of Software Engineering

57 UML 2.0 UML version 2.0 has 14 diagrams in 2 major groups:
Object-Oriented Programming UML 2.0 UML version 2.0 has 14 diagrams in 2 major groups: Structure Diagrams Behavior Diagrams

58 UML 2.0 Diagram

59 UML Structure Diagrams
Represent the data and static relationships in an information system Class Diagram Object Diagram Package Diagram Deployment Diagram Component Diagram Composite Structure Diagram

60 Structure Diagrams Class Diagrams Object Diagrams Package Diagrams
Common vocabulary used by analyst and users Represent things (employee, paycheck,…) Shows the relationships between classes Object Diagrams Similar to class diagrams Instantiation of a class diagram Relationships between objects Package Diagrams Group UML elements together to form higher level constructs

61 Structure Diagrams Deployment Diagrams Component Diagrams
Shows the physical architecture and software components of system For example, network nodes Component Diagrams Physical relationships among software components Example – Client/Server (Which machines run which software) Composite Structure Illustrates internal structure of a complex class

62 UML Behavior Diagrams Depict the dynamic relationships among the instances or objects that represent the business information system Activity Diagram Timing Diagram Sequence Diagram Behavior State Machine Communication Diagram Protocol State Machine Interaction Diagram Use Case Diagrams

63 Behavior Diagrams Activity Diagrams Interaction Diagrams
Model processes in an information system Example: Business workflows, business logic Interaction Diagrams Shows interaction among objects Sequence Diagrams Time-based ordering of the interaction Communication Diagrams Communication among a set of collaborating objects of an activity

64 Behavior Diagrams Interaction Diagrams Timing Diagrams State Machines
Overview of flow of control of a process Timing Diagrams Show how an object changes over time State Machines Examines behavior of one class Models the different states and state transitions an object can experience Use-Case Diagrams Shows interaction between the system and environment Captures business requirements

65 UML Problems UML is modeling notation, it is not a development process or a methodology UML driven development process? UML is too complex, difficult to understand quickly Should we use all UML diagrams?

66 Object-Oriented Programming UML Process (EA Sparx) Display the boundary of a system and its major functions using use cases and actors Model the organization’s business process with activity diagram Illustrate use case realizations with sequence diagrams Represent a static structure of a system using class diagrams Reveal the physical implementation architecture with deployment diagrams

67 UML Process (EA Sparx) Use Cases Diagram Activity Diagram
Object-Oriented Programming UML Process (EA Sparx) Use Cases Diagram Activity Diagram Sequence Diagram Class Diagram Deployment Diagrams

68 UML Process (Kendal, 2011) A use case diagram, describing how the system is used. Analysts start with a use case diagram An activity diagram, illustrating the overall flow of activities. Each use case may create one activity diagram Sequence diagrams, showing the sequence of activities and class relationships. Each use case may create one or more sequence diagrams Class diagrams, showing the classes and relationships. Sequence diagrams are used to determine classes Statechart diagrams, showing the state transitions. Each class may create a statechart diagram, which is useful for determining class methods

69 (Kendall and Kendall, 2011)

70 UML Process (Barclay, 2004)

71 System Analysis and Design with UML
Business Process Identification Use Case Diagram Business Process Modeling Activity Diagram or Business Process Modeling Notation (BPMN) Business Process Realization Sequence Diagram (Buat untuk setiap use case dengan menggunakan pola Boundary-Control-Entity) System Design Program Design Class Diagram (Gabungkan Boundary-Control-Entity Class dan susun story dari sistem yang dibangun) Package Diagram (Gabungan class yang sesuai, boleh menggunakan pola B-C-E) Deployment Diagram (arsitektur software dari sistem yang dibangun) User Interface Design (Buat UI design dari Boundary Class) Entity-Relationship Model (Buat ER diagram dari Entity Class)

72 Case Study: ATM System romi@romisatriawahono.net
Object-Oriented Programming Case Study: ATM System

73 ATM System romi@romisatriawahono.net Object-Oriented Programming

74 ATM System Layar Kotak Uang Kotak Kartu Kotak Kuitansi
Object-Oriented Programming ATM System Layar Kotak Uang Kotak Kartu Kotak Kuitansi

75 Masukkan PIN: Kotak Uang Kotak Kartu Kotak Kuitansi
Object-Oriented Programming Masukkan PIN: Kotak Uang Kotak Kartu Kotak Kuitansi

76 Menu Utama Melihat Saldo Mentransfer Uang Mengambil Uang Logout
Object-Oriented Programming Menu Utama Melihat Saldo Mentransfer Uang Mengambil Uang Logout Kotak Uang Kotak Kartu Kotak Kuitansi

77 Saldo anda adalah …. Menu Melihat Saldo Kotak Uang Kotak Kartu
Object-Oriented Programming Menu Melihat Saldo Saldo anda adalah …. Kotak Uang Kotak Kartu Kotak Kuitansi

78 No Account Penerima: Menu Mentransfer Uang Kotak Uang Kotak Kartu
Object-Oriented Programming Menu Mentransfer Uang No Account Penerima: Kotak Uang Kotak Kartu Kotak Kuitansi

79 Jumlah uang yang dikirim:
Object-Oriented Programming Menu Mentransfer Uang Jumlah uang yang dikirim: Kotak Uang Kotak Kartu Kotak Kuitansi

80 Uang berhasil terkirim
Object-Oriented Programming Menu Mentransfer Uang Uang berhasil terkirim Kotak Uang Kotak Kartu Kotak Kuitansi

81 Jumlah uang yang diambil:
Object-Oriented Programming Menu Mengambil Uang Jumlah uang yang diambil: Kotak Uang Kotak Kartu Kotak Kuitansi

82 Uang berhasil diambil Menu Mengambil Uang Kotak Uang Kotak Kartu
Object-Oriented Programming Menu Mengambil Uang Uang berhasil diambil Kotak Uang Kotak Kartu Kotak Kuitansi

83 Use Case Diagram

84 Use Case Diagram (Alternatif)

85 Activity Diagram: Memasukkan Kartu

86 Activity Diagram: Memasukkan PIN

87 Activity Diagram: Mengecek Saldo

88 Activity Diagram: Mentransfer Uang

89 Activity Diagram: Mengambil Uang

90 Activity Diagram: Melakukan Logout

91 Sequence Diagram: Memasukkan Kartu

92 Type of Class Boundary Class Control Class Entity Class
Object-Oriented Programming Type of Class Boundary Class Class yang berhubungan dengan actor (user interface) Control Class Class yang berhubungan dengan pemrosesan, komputasi, penghitungan, dsb Entity Class Class yang berhubungan dengan data (flat file or database)

93 Sequence Diagram: Memasukkan PIN

94 Sequence Diagram: Mengecek Saldo

95 Sequence Diagram: Mentransfer Uang

96 Sequence Diagram: Mengambil Uang

97 Sequence Diagram: Melakukan Logout

98 Class Diagram

99 Deployment Diagram (2 Tier)

100 Data Model

101 User Interface Design

102 User Interface Design (Netbeans)

103 4. Object-Oriented Paradigm
Object-Oriented Programming 4. Object-Oriented Paradigm

104 Konsep Dasar Pemrograman Berorientasi Objek
Object-Oriented Programming Konsep Dasar Pemrograman Berorientasi Objek Class , Object, Method, Attribute

105 Berorientasi Objek? Attribute: Topi, Baju, Jaket,
Object-Oriented Programming Berorientasi Objek? Attribute: Topi, Baju, Jaket, Tas Punggung, Tangan, Kaki, Mata Behavior: Cara Jalan ke Depan Cara Jalan Mundur Cara Belok ke Kiri Cara Memanjat

106 Berorientasi Objek? Attribute (State): Behavior:
Object-Oriented Programming Berorientasi Objek? Attribute (State): Ban, Stir, Pedal Rem, Pedal Gas, Warna, Tahun Produksi Behavior: Cara Menghidupkan Mesin Cara Manjalankan Mobil Cara Memundurkan Mobil Attribute  Variable(Member) Behavior  Method(Fungsi)

107 Perbedaan Class dan Object
Object-Oriented Programming Perbedaan Class dan Object Class: konsep dan deskripsi dari sesuatu Class mendeklarasikan method yang dapat digunakan (dipanggil) oleh object Object: instance dari class, bentuk (contoh) nyata dari class Object memiliki sifat independen dan dapat digunakan untuk memanggil method Contoh Class dan Object: Class: mobil Object: mobilnya pak Joko, mobilku, mobil berwarna merah

108 Perbedaan Class dan Object
Object-Oriented Programming Perbedaan Class dan Object Class seperti cetakan kue, dimana kue yg dihasilkan dari cetakan kue itu adalah object Warna kue bisa bermacam-macam meskipun berasal dari cetakan yang sama (object memiliki sifat independen)

109 Class = Method + Variable
Object-Oriented Programming Class = Method + Variable Class Sepeda gir kecepatan variable tampilkan kecepatan ubah gir method

110 Object = Method + Variable yg Memiliki Nilai
Object-Oriented Programming Object = Method + Variable yg Memiliki Nilai Object Sepedaku gir = 3 instance variable kecepatan = 10km/jam tampilkan kecepatan () kecepatan = 10 km/jam instance method ubah gir (2) gir = 5

111 Object-Oriented Programming Attribute Variable yang mengitari class, dengan nilai datanya bisa ditentukan di object Variable digunakan untuk menyimpan nilai yang nantinya akan digunakan pada program Variable memiliki jenis (tipe), nama dan nilai Name, age, dan weight adalah atribute (variabel) dari class Person

112 Membuat Class, Object dan Memanggil Atribut
Object-Oriented Programming Membuat Class, Object dan Memanggil Atribut Mobil.java public class Mobil { String warna; int tahunProduksi; } MobilBeraksi.java public class MobilBeraksi{ public static void main(String[] args){ // Membuat object Mobil mobilku = new Mobil(); /* memanggil atribut dan memberi nilai */ mobilku.warna = "Hitam"; mobilku.tahunProduksi = 2006; System.out.println("Warna: " + mobilku.warna); System.out.println("Tahun: " + mobilku.tahunProduksi); }

113 Latihan: Membuat Program dg Netbeans
Object-Oriented Programming Latihan: Membuat Program dg Netbeans Buka Netbeans IDE Ikuti langkah berikut

114 Object-Oriented Programming

115 Object-Oriented Programming

116 Object-Oriented Programming

117 Object-Oriented Programming

118 Object-Oriented Programming

119 Object-Oriented Programming

120 Object-Oriented Programming

121 Object-Oriented Programming

122 Object-Oriented Programming

123 Method Method adalah urutan instruksi yang mengakses data dari object
Object-Oriented Programming Method Method adalah urutan instruksi yang mengakses data dari object Method melakukan: Manipulasi data Perhitungan matematika Memonitor kejadian dari suatu event

124 Method romi@romisatriawahono.net Object-Oriented Programming

125 Membuat dan Memanggil Method
Object-Oriented Programming Membuat dan Memanggil Method public class Mobil2{ String warna; int tahunProduksi; void printMobil(){ System.out.println("Warna: " + warna); System.out.println("Tahun: " + tahunProduksi); } Mobil2.java public class Mobil2Beraksi{ public static void main(String[] args){ Mobil2 mobilku = new Mobil2(); mobilku.warna = "Hitam"; mobilku.tahunProduksi = 2006; mobilku.printMobil(); } Mobil2Beraksi.java

126 Latihan Buat class Handphone yang berisi empat method: hidupkan()
Object-Oriented Programming Latihan Buat class Handphone yang berisi empat method: hidupkan() lakukanPanggilan() kirimSMS() matikan() Isi masing-masing method dengan tampilan status menggunakan System.out.println() Buat class HandphoneBeraksi, dan panggil method-method diatas dalam class tersebut

127 Latihan: Hasil Tampilan
Object-Oriented Programming Latihan: Hasil Tampilan Handphone hidup … Kring, kring, kring … panggilan dilakukan Dung, dung … sms berhasil terkirim Handphone mati …

128 Jenis Method: Mutator dan Accessor
Object-Oriented Programming Jenis Method: Mutator dan Accessor

129 Object-Oriented Programming Parameter Sepeda akan berguna apabila ada object lain yang berinterasi dengan sepeda tersebut Object software berinteraksi dan berkomunikasi dengan object lain dengan cara mengirimkan message atau pesan Pesan adalah suatu method, dan informasi dalam pesan dikenal dengan nama parameter

130 Pengiriman Pesan dan Parameter
Object-Oriented Programming Pengiriman Pesan dan Parameter You  object pengirim YourBicycle  object penerima changeGears  pesan berupa method yang dijalankan lowerGear parameter yang dibutuhkan method (pesan) untuk dijalankan

131 Object-Oriented Programming

132 Object-Oriented Programming Sepeda.java public class Sepeda{ int gir; // method (mutator) dengan parameter void setGir(int pertambahanGir) { gir= gir+ pertambahanGir; } // method (accessor) int getGir() { return gir;

133 Object-Oriented Programming SepedaBeraksi.java public class SepedaBeraksi{ public static void main(String[] args) { // Membuat object Sepeda sepedaku = new Sepeda(); // Memanggil method dan menunjuk nilai parameter sepedaku.setGir(1); // menset nilai gir = 1 System.out.println(“Gir saat ini: “ + sepedaku.getGir()); sepedaku.setGir(3); // menambahkan 3 pada posisi gir saat ini (1) System.out.println(“Gir saat ini: “ + sepedaku.getGir()); }

134 Latihan: Class Matematika dan Parameter
Object-Oriented Programming Latihan: Class Matematika dan Parameter Buat Class bernama Matematika, yang berisi method dengan dua parameter: pertambahan(int a, int b) pengurangan(int a, int b) perkalian(int a, int b) pembagian(int a, int b) Buat Class bernama MatematikaBeraksi, yang mengeksekusi method dan menampilkan: Pertambahan: = 40 Pengurangan: 10-5 = 5 Perkalian: 10*20 = 200 Pembagian: 21/2 = 10

135 Object-Oriented Programming Variasi Tampilan pertambahan(int a, int b){ System.out.println(a + “ + “ + b + “ = “ + (a+b)) } System.out.println(“Hasil = “ + (a+b)) int hasil = a + b; System.out.println(“Hasil = “ + hasil)

136 Object-Oriented Programming Konstruktor -1- Method yang digunakan untuk memberi nilai awal pada saat object diciptakan Dipanggil secara otomatis ketika new digunakan untuk membuat instan class Sifat konstruktor: Nama konstruktor sama dengan nama class Tidak memiliki nilai balik dan tidak boleh ada kata kunci void

137 Konstruktor -2- Mobil.java MobilKonstruktor.java
Konstruktor -2- Object-Oriented Programming Mobil.java public class Mobil { String warna; int tahunProduksi; public Mobil(String warna, int tahunProduksi){ this.warna = warna; this.tahunProduksi = tahunProduksi; } public void info(){ System.out.println("Warna: " + warna); System.out.println("Tahun: " + tahunProduksi); public class MobilKonstruktor{ public static void main(String[] args){ Mobil mobilku = new Mobil(“Merah”, 2003); mobilku.info(); } MobilKonstruktor.java

138 Object-Oriented Programming Kata Kunci this Digunakan pada pembuatan class dan digunakan untuk menyatakan object sekarang public class Mobil{ String warna; int tahunProduksi; void isiData(String aWarna, int aTahunProduksi){ warna = aWarna; tahunProduksi = aTahunProduksi; } public class Mobil{ String warna; int tahunProduksi; void isiData(String warna, int tahunProduksi){ this.warna = warna; this.tahunProduksi = tahunProduksi; }

139 Latihan Buat class Bank
Object-Oriented Programming Latihan Buat class Bank Buat konstruktor class Bank dengan parameter: saldo Buat method: simpanUang, ambilUang, dan getSaldo Buat class BankBeraksi, tetapkan saldo awal lewat konstruktur Rp , jalankan 3 method di atas, dan tampilkan proses sebagai berikut: Selamat Datang di Bank ABC Saldo awal: Rp Simpan uang: Rp Saldo saat ini: Rp Ambil uang: Rp Saldo saat ini: Rp

140 Karakteristik Pemrograman Berorientasi Objek
Object-Oriented Programming Karakteristik Pemrograman Berorientasi Objek Abstraction, Encapsulation, Inheritance, Polymorphism

141 Object-Oriented Programming Abstraction Cara kita melihat suatu sistem dalam bentuk yang lebih sederhana, yaitu sebagai suatu kumpulan subsistem (object) yang saling berinteraksi. Mobil adalah kumpulan sistem pengapian, sistem kemudi, sistem pengereman Alat meng-abstraksikan sesuatu adalah class Object bersifat modularity. Object dapat ditulis dan dimaintain terpisah (independen) dari object lain

142 Object-Oriented Programming

143 Object-Oriented Programming

144 Object-Oriented Programming Encapsulation Mekanisme menyembunyikan suatu proses dan data dalam sistem untuk menghindari interferensi, dan menyederhanakan penggunaan proses itu sendiri Tongkat transmisi (gigi) pada mobil Tombol on/off/pengaturan suhu pada AC Class access level (public, protected, privat) adalah implementasi dari konsep encapsulation Enkapsulasi data dapat dilakukan dengan cara: mendeklarasikan instance variable sebagai private mendeklarasikan method yang sifatnya public untuk mengakses variable tersebut

145 Object-Oriented Programming

146 Encapsulation dan Access Modifier
Object-Oriented Programming Encapsulation dan Access Modifier Modifier Dalam Class yang Sama Dalam Package yang Sama Dalam SubClass Dalam Package Lain private  tanpa tanda protected public   

147 Encapsulation Enkapsulasi data juga dapat dilakukan dengan cara:
Object-Oriented Programming Encapsulation Enkapsulasi data juga dapat dilakukan dengan cara: mendeklarasikan instance variable sebagai private mendeklarasikan method yang sifatnya public untuk mengakses variable tersebut

148 Object-Oriented Programming Sepeda.java public class Sepeda{ int gir; void setGir(int pertambahanGir) { gir= gir+ pertambahanGir; } int getGir() { return gir;

149 Object-Oriented Programming SepedaBeraksi.java public class SepedaBeraksi{ public static void main(String[] args) { Sepeda sepedaku = new Sepeda(); sepedaku.setGir(1); /* Variabel bisa diubah atau tidak sengaja diubah. Hal ini berbahaya dan sering menimbulkan bug. Berikan access modifier private pada instance variable */ sepedaku.gir = 3; System.out.println(“Gir saat ini: “ + sepedaku.getGir()); }

150 Object-Oriented Programming Sepeda.java public class Sepeda{ private int gir; // access modifier private pada instance variable void setGir(int pertambahanGir) { gir= gir+ pertambahanGir; } int getGir() { return gir;

151 Inheritance (Pewarisan)
Object-Oriented Programming Inheritance (Pewarisan) Suatu class dapat mewariskan atribut dan method kepada class lain (subclass), serta membentuk class hierarchy Penting untuk Reusability Java Keyword: extends

152 Object-Oriented Programming Sepeda.java public class Sepeda{ private int gir; void setGir(int pertambahanGir) { gir= gir+ pertambahanGir; } int getGir() { return gir;

153 Class SepedaGunung Mewarisi Class Sepeda
Object-Oriented Programming Class SepedaGunung Mewarisi Class Sepeda public class SepedaGunung extends Sepeda{ private int sadel; void setSadel (int jumlah) { sadel = getGir() - jumlah; } int getSadel(){ return sadel; public class SepedaGunungBeraksi { public static void main(String[] args) { SepedaGunung sg=new SepedaGunung(); sg.setGir(3); System.out.println(sg.getGir()); sg.setSadel(1); System.out.println(sg.getSadel()); } SepedaGunung.java SepedaGunungBeraksi.java

154 Latihan: Inheritance Matematika
Object-Oriented Programming Latihan: Inheritance Matematika Buat class MatematikaCanggih yang merupakan inherit dari class Matematika Tambahkan method modulus(int a, int b) yang menghitung modulus dari a dan b Operator modulus adalah % Buat class MatematikaCanggihBeraksi yang memanggil method pertambahan, perkalian dan modulus

155 Object-Oriented Programming Polymorphism Kemampuan untuk memperlakukan object yang memiliki perilaku (bentuk) yang berbeda Implementasi konsep polymorphism: Overloading: Kemampuan untuk menggunakan nama yang sama untuk beberapa method yang berbeda parameter (tipe dan atau jumlah) Overriding: Kemampuan subclass untuk menimpa method dari superclass, yaitu dengan cara menggunakan nama dan parameter yang sama pada method

156 Polymorphism – Overloading
Object-Oriented Programming Polymorphism – Overloading class Mobil { String warna; int tahunProduksi; public Mobil(String warna, int tahunProduksi){ this.warna = warna; this.tahunProduksi = tahunProduksi; } public Mobil(){ void info(){ System.out.println("Warna: " + warna); System.out.println("Tahun: " + tahunProduksi); public class MobilKonstruktor{ public static void main(String[] args){ Mobil mobilku = new Mobil(“Merah”, 2003); mobilku.info(); Mobil mobilmu = new Mobil(); mobilmu.info(); }

157 Polymorphism – Overloading
Object-Oriented Programming Polymorphism – Overloading class Lingkaran{ void gambarLingkaran(){ } void gambarLingkaran(int diameter){ ... void gambarLingkaran(int diameter, int x, int y){ ... void gambarLingkaran(int diameter, int x, int y, int warna, String namaLingkaran){ ...

158 Polymorphism - Overriding
Object-Oriented Programming Polymorphism - Overriding public class Sepeda{ protected int gir; void setGir(int pertambahanGir) { gir= gir+ pertambahanGir; } int getGir() { return gir;

159 Polymorphism - Overriding
Object-Oriented Programming Polymorphism - Overriding public class SepedaGunung extends Sepeda{ void setGir(int pertambahanGir) { super.setGir(pertambahanGir); gir = 2*getGir(); } public class SepedaGunungBeraksi { public static void main(String[] args) { SepedaGunung sg=new SepedaGunung(); sg.setGir(2); System.out.println(sg.getGir()); sg.setGir(3); } SepedaGunung.java SepedaGunungBeraksi.java

160 Latihan: Overloading pada Matematika
Object-Oriented Programming Latihan: Overloading pada Matematika Kembangkan class Matematika, MatematikaCanggih dan MatematikaBeraksi Lakukan overloading pada Method yang ada (pertambahan, pengurangan, perkalian, pembagian, modulus) Tambahkan method baru bertipe data double (pecahan) dan memiliki 3 parameter: double a, double b, double c Uji di kelas MatematikaBeraksi dengan parameter pecahan: 12.5, 28.7, 14.2 Misalnya: pertambahan(12.5, 28.7, 14.2) pertambahan(12, 28, 14) pertambahan(23, 34) pertambahan(3.4, 4.9)

161 Object-Oriented Programming Matematika.java public class Matematika{ void pertambahan (int a, int b){ int hasil= a + b; System.out.println(“hasil:” + hasil); } void pertambahan (double a, double b, double c){ int hasil= a + b + c; ...

162 Referensi (Foundation)
Roger S. Pressman, Software Engineering: A Practitioner’s Approach Sevent Edition, McGraw-Hill, 2009 Ian Sommerville, Software Engineering 9th Edition, Addison-Wesley, 2010 Albert Endres dan Dieter Rombach, A Handbook of Software and Systems Engineering, Pearson Education Limited, 2003 Yingxu Wang, Software Engineering Foundations: A Software Science Perspective, Auerbach Publications, Taylor & Francis Group, 2008 Guide to the Software Engineering Body of Knowledge 2004 Version (SWEBOK), IEEE Computer Society,

163 Referensi (Process) Alan Dennis et al, Systems Analysis and Design with UML – 3rd Edition, John Wiley and Sons, 2010 Dan Pilone and Russ Miles, Head First Software Development, O’Reilly Media, 2008 Barclay and Savage, Object-Oriented Design with UML and Java, Elsevier, 2004 Paul Kimmel, UML Demystified, McGraw-Hill, 2005 Kim Hamilton and Russell Miles, Learning UML 2.0, O'Reilly, 2006 Howard Podeswa, UML for the IT Business Analyst, Course Technology, 2009 Deloitte, Business Process Modeling – Basic Guideline and Tips, 2008

164 Referensi (Quality Assurance)
Daniel Galin, Software Quality Assurance, Addison-Wesley, 2004 Jeff Tian, Software Quality Engineering, John Wiley & Sons, Inc., 2005 G. Gordon Schulmeyer, Handbook of Software Quality Assurance Fourth Edition, Artech House, 2008 Kshirasagar Naik and Priyadarshi Tripathy, Software Testing and Quality Assurance, John Wiley & Sons, Inc., 2008