Pertemuan 23 Sequence Diagram

Slides:



Advertisements
Presentasi serupa
Bab 8 collaboration diagram
Advertisements

Interaction Diagram.
SEQUENCE DIAGRAM.
2. Introduction to Algorithm and Programming
Lecture 5 Nonblocking I/O and Multiplexing Erick Pranata © Sekolah Tinggi Teknik Surabaya 1.
ARRAY RUBY. PENDAHULUAN Ruby's arrays are untyped and mutable. The elements of an array need not all be of the same class, and they can be changed at.
Activity Diagram Shinta P.. For Bussiness Modeling, Activity diagrams describe the activities of a class. It is used for the following purposes: (Bennet.
1 DATA STRUCTURE “ STACK” SHINTA P STMIK MDP APRIL 2011.
Presented By : Group 2. A solution of an equation in two variables of the form. Ax + By = C and Ax + By + C = 0 A and B are not both zero, is an ordered.
1 Pertemuan 17 Input / Output Matakuliah: T0316/sistem Operasi Tahun: 2005 Versi/Revisi: 5.
Propagasi Gelombang Pertemuan 8 Matakuliah: H0122 / Dasar Telekomunikasi Tahun: 2008.
1 Pertemuan 09 Kebutuhan Sistem Matakuliah: T0234 / Sistem Informasi Geografis Tahun: 2005 Versi: 01/revisi 1.
Ruang Contoh dan Peluang Pertemuan 05
Collaboration Diagram
Metode Perancangan Program
Pertemuan 7 Unified Modelling Language (UML)
Masalah Transportasi II (Transportation Problem II)
Design View 2.
1 Pertemuan 21 Function Matakuliah: M0086/Analisis dan Perancangan Sistem Informasi Tahun: 2005 Versi: 5.
PERTEMUAN KE-6 UNIFIED MODELLING LANGUAGE (UML) (Part 2)
Layer Data Link Pertemuan 13 Matakuliah: H0484/Jaringan Komputer Tahun: 2007.
1 Pertemuan 5 Komunikasi antar Proses / Interprocess Communication (IPC) Matakuliah: T0316/sistem Operasi Tahun: 2005 Versi/Revisi: 5 OFFCLASS01.
1 Pertemuan 26 Review Matakuliah: M0086/Analisis dan Perancangan Sistem Informasi Tahun: 2005 Versi: 5.
1 Pertemuan 23 Sequence Diagram Matakuliah: M0086/Analisis dan Perancangan Sistem Informasi Tahun: 2005 Versi: 5.
1 Minggu 10, Pertemuan 20 Normalization (cont.) Matakuliah: T0206-Sistem Basisdata Tahun: 2005 Versi: 1.0/0.0.
1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >
1 Pertemuan 11 Function dari System Matakuliah: M0446/Analisa dan Perancangan Sistem Informasi Tahun: 2005 Versi: 0/0.
1 Pertemuan 13 Algoritma Pergantian Page Matakuliah: T0316/sistem Operasi Tahun: 2005 Versi/Revisi: 5.
1 Pertemuan 12 B-Tree Matakuliah: T0534/Struktur Data Tahun: 2005 Versi: September 2005.
9.3 Geometric Sequences and Series. Objective To find specified terms and the common ratio in a geometric sequence. To find the partial sum of a geometric.
KONSEP DASAR PENDEKATAN OBJEK
Sequence Diagram AND Communication Diagram Pertemuan 0102
Matakuliah : M0086/Analisis dan Perancangan Sistem Informasi
KOMUNIKASI DATA Materi Pertemuan 3.
Notasi Object Oriented System
Rekayasa Perangkat Lunak Class Diagram
Pertemuan 5 Struktur dan Hubungan Antara Class dan Object
Konsep pemrograman LOOP
SEQUENCE DIAGRAM.
Sequence Diagram.
KOMUNIKASI DATA S. Indriani L, M.T
COMPOUND NOMENCLATURE AND EQUATION OF REACTION
Pengujian Hipotesis (I) Pertemuan 11
Object oriented analyst and design
CLASS DIAGRAM.
Dasar-Dasar Pemrograman
Citra N., S.Si, MT Sisfo - UNIKOM
Collaboration Diagram
OOAD – TI S1 Defri Kurniawan UDINUS
Pertemuan 17 Aplication Domain
ANALISIS DAN PERANCANGAN BERORIENTASI OBJEK
Collaboration Diagram and Sequence Diagram
Pertemuan 16 Layer Data Link - Lanjutan
SISTEM INFORMASI ENTERPRISE
Pertemuan 4 Menentukan Class
SISTEM INFORMASI ENTERPRISE
DESIGN VIEW 2 Pertemuan 18 Matakuliah : Konsep object-oriented
Kk ilo Associative entity.
ANALISIS & DESAIN SISTEM
UML- UNIFIED MODELING LANGUAGE
Pertemuan 4 CLASS DIAGRAM.
Pertemuan 5 Computer Components
Database User Account.
ELASTIC PROPERTIS OF MATERIAL
Matakuliah : M0086/Analisis dan Perancangan Sistem Informasi
Oleh : Cosmas Haryawan -- Pengenalan UML --
Oleh : Cosmas Haryawan -- Pengenalan UML --
Describing process how something is made or done.
Object oriented analyst and design
Draw a picture that shows where the knife, fork, spoon, and napkin are placed in a table setting.
Transcript presentasi:

Pertemuan 23 Sequence Diagram Matakuliah : M0086/Analisis dan Perancangan Sistem Informasi Tahun : 2005 Versi : 5 Pertemuan 23 Sequence Diagram

Learning Outcomes Pada akhir pertemuan ini, diharapkan mahasiswa akan mampu : Mahasiswa dapat Menerangkan Sequence Diagram (C2) Mahasiswa dapat Membuat diagram / skema Sequence (C4)

Konsep dasar dan Notasi Time Constrains Branching and Recursion Outline Materi Konsep dasar dan Notasi Time Constrains Branching and Recursion Dialoque Management (Interface Classes) Modelling real-time systems and concurrency

What is Sequence Diagram? Sequence Diagram is a dynamic model of a use case, showing the interaction among classes during a specified time period. Sequence Diagram is used primarily to show the interactions between objects in the sequential order that those interactions occur. Illustrates how objects interacts with each other. Emphasizes time ordering of messages. Can model simple sequential flow, branching, iteration, recursion and concurrency.

What is Sequence .. (Cont’s) Illustrates how objects interacts with each other. Emphasizes time ordering of messages. Can model simple sequential flow, branching, iteration, recursion and concurrency.

Elements of Sequence Diagram Notasi Object Object Nama Object Lifeline Activation

Notasi Actor Actor (Initiator) Actor Lifeline Actor Activation Elements of (Con’t…….) Notasi Actor Actor Name Actor (Initiator) Actor Lifeline Actor Activation

Notasi Bentuk Panah Elements of (Con’t…….) filled solid arrowhead Procedure call or other nested flow of control. The entire nested sequence is completed before the outer level sequence resumes. The arrowhead may be used to denote ordinary procedure calls, but it may also be used to denote Concurrently active instances when one of them sends a Signal and waits for a nested sequence of behavior to complete before it continues. stick arrowhead Message ; that is, no nesting of control. The sender dispatches the Stimulus and immediately continues with the next step in the execution. dashed arrow with stick arrowhead Return from procedure call.

Elements of (Con’t…….) X-Axis (objects) Y-Axis (time) Synchronous Actor Synchronous message :A :B Procedure Call Asynchronous message Y-Axis (time) Return Synchronous message : the caller has to wait for the receiving object to complete execution of the called operation before it can resume execution. Asynchronous message : The caller can execute immediately after sending the message, it does not has to wait for the recipient to handle the message

Control information Condition syntax: ‘[‘ expression ’]’ message-label The message is sent only if the condition is true example: Iteration syntax: * [ ‘[‘ expression ‘]’ ] message-label The message is sent many times to possibly multiple receiver objects. :CompoundShape :Shape draw() *draw()

Recursion in SD :A Recursive

Object Creation An object may create another object via a <<create>> message :A <<create>> :B Object Contruction (Object Creation) Object Destruction (Object Deletion)

Branching A branch is shown by multiple arrows leaving a single point, each possibly labeled by a condition. Depending on whether the conditions are mutually exclusive, the construct may represent conditionality or concurrency. :B :C :A [Gaji >= PKP] Hitung Pajak() [Gaji < PKP] Hitung Gaji Bersih()

Contoh Berdasarkan Use Case Diagram ini kita akan membuat Sequence Diagram dan hasilnya adalah sebagai berikut

Contoh Pembuatan PO Dari Sequence Diagram ini dapat Dilihat bentuk dari Class Diagramnya

To be Continue…..

Object Object dalam Sequence Diagram digambar dengan segiempat yang berisi nama Object yang diberi garis bawah. syntax: [Obiect Name][:className] Object dapat diberi nama berdasarkan : Nama Object saja • Nama Class Saja Gabungan Nama Class dan Nama Object OOAD :Matakuliah OOAD:Matakuliah Back

Lifeline Tiap obyek juga mempunyai Lifeline (Biasa disebut juga dengan Timeline / Garis Waktu) yang direpresentasikan dengan garis putus-putus dibawah obyek Lifeline menggambarkan waktu selama Obyek yang diatas bisa berhubungan dengan obyek lain didalam use case. Back

Activation Activation digambarkan dengan bentuk empat persegi panjang sempit yang menutupi Lifeline. Activation menunjukkan kapan sebuah object mengirim atau menerima message. Back

Messages An interaction between two objects is performed as a message sent from one object to another (simple operation call, Signaling, RPC) If object obj1 sends a message to another object obj2 some link must exist between those two objects (dependency, same objects) A message is represented by an arrow between the life lines of two objects. Self calls are also allowed The time required by the receiver object to process the message is denoted by an activation-box. A message is labeled at minimum with the message name. Arguments and control information (conditions, iteration) may be included.