Teknik Informatika S1

Transkripsi

1 Teknik Informatika S1 Rekayasa Perangkat Lunak Lanjut Pengenalan OOA (UML) Disusun Oleh: Egia Rosi Subhiyakto, M.Kom, M.CS Teknik Informatika UDINUS

2 Evolution of OO Development Methods

3 History of UML

4 UML Diagrams (1)

5 UML Diagrams (2)

6 Diagrams and Process

7 Diagrams and Process Use Case Diagrams

8 Diagrams and Process Class & Package Diagrams

9 Diagrams and Process Interaction Diagrams (Scenarios)

10 Diagrams and Process Activity Diagrams (Workflow, Interclass Behavior)

11 Diagrams and Process State Transition Diagrams (Intraclass Behavior)

12 Texts and Process Source Code

13 Diagrams and Process Deployment Diagrams

14 Use case Diagrams UML Menggambarkan perilaku fungsional sistem seperti yang terlihat oleh penggunanya. Class diagrams Menggambarkan struktur statis sistem ini: Classes, Associations Sequence diagrams Menggambarkan perilaku dinamis sebuah sistem: Actors, objects, messages Statechart diagrams Menggambarkan perilaku dinamis dari objek individu dari sistem: states, events, transitions Activity Diagrams Memodelkan perilaku dinamis sistem ini: activities, workflows (flowcharts)

15 Use Case Diagram

16 Use Case Diagram Merupakan fungsionalitas sistem dari sudut pandang pengguna Memodelkan dan menyatakan unit fungsi/ layanan yang disediakan oleh sistem (atau bagian sistem; subsistem atau class) Use Case dapat dilingkupi dengan batasan sistem yang diberi label nama sistem

17 Elemen/ Simbol: Use case diagrams 1. Aktor (Merepresentasikan seseorang atau sesuatu seperti perangkat atau sistem lain) 2. Use Case (Merepresentasikan tugas aktor, pola perilaku perangkat lunak, apa yang harus dilakukan oleh sistem/ fitur kunci sistem) 3. Boundary (Merepresentasikan batasan/ ruang lingkup sistem) 4. Package (Merepresentasikan ruang lingkup class)

18 1. Asosiasi Relasi: Use case diagrams (Menghubungkan antara aktor dengan use case) 2. Generalisasi (Konsep Inheritance/ pewarisan) 3. Dependensi: Include (Dimana use case yang dituju harus melewati proses lain) 4. Dependensi: Extend (Dimana use case yang dituju berdiri sendiri tanpa harus melewati prose yang lain)

19 Use Case Diagram Syntax Actor o person or system that derives benefit from and is external to the subject Use Case o Merupakan bagian utama dari fungsi sistem Association Relationship Include Relationship Extend Relationship Generalization Relationship <<includes>> <<extends>>

20 Use Case A major piece of system functionality Can extend other Use Cases Placed inside system boundary Use Case Labeled with descriptive verb-noun phrase

21 System Boundary Includes the name of the system inside or on top Represents the scope of the system Actors are outside the scope of the system Boundary

22 Actor A person or another system that interacts with the current system A role, not a specific user Provides input, receives output, or both actor Actor/Role

23 Association Relationship Links actor and the Use Case Shows two-way communication o If one-way, arrows are used * is for "multiplicity of the Association" * *

24 Extends Relationship Extends Use Case to include Optional behavior Arrow points from the extension Use Case to the base Use Case extend Make Pmt Arrangements extend Make Appointment

25 Include Relationship Include one Use Case from within another Arrow points from base Use Case to the included Use Case include Record Availability include Manage Schedule

26 Generalization Relationship A specialized Use Case to a more generalized Use Case Arrow points from specialized to general Use Case Make Old Appointment Make Appointment

27 Menyusun Use case diagram 1. Identifikasi Aktor 2. Identifikasi Use Case 3. Membuat diagram use case 4. Mendokumentasikan naratif setiap use case (Skenario/ tabel use case)

28 Tutorial Enterprise Architect

29 TERIMA KASIH