1 / 120

TOGAF 9 Fundamental: 6. UML Introduction

TOGAF 9 Fundamental: 6. UML Introduction. Romi Satria Wahono romi@romisatriawahono.net http:// romisatriawahono.net. Romi Satria Wahono. SD Sompok Semarang (1987) SMPN 8 Semarang (1990) SMA Taruna Nusantara Magelang (1993)

shanon
Download Presentation

TOGAF 9 Fundamental: 6. UML Introduction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TOGAF9 Fundamental:6. UML Introduction Romi Satria Wahonoromi@romisatriawahono.nethttp://romisatriawahono.net

  2. Romi Satria Wahono • SD SompokSemarang (1987) • SMPN 8 Semarang (1990) • SMA Taruna NusantaraMagelang (1993) • B.Eng, M.Eng and Dr.Eng(on-leave)Department of Computer ScienceSaitama University, Japan (1994-2004) • Research Interests: Software Engineering and Intelligent Systems • Founder IlmuKomputer.Com • LIPI Researcher (2004-2007) • Founder and CEO PT BrainmaticsCiptaInformatika

  3. Course Outline • Introduction • Basic Concepts • Core Concepts • Key Terminology • ADM Introduction • UML Introduction • TOGAF Case Study

  4. 6. UML Introduction

  5. The Nature of Software Development

  6. IsitPossible?

  7. Systems Analysis and Design with UML

  8. System Analysis and Design with UML • System Analysis • 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)

  9. 1. Business Process Identification:Use Case Diagram

  10. Use Case Diagrams • Summarized into a single picture • All of the use cases for the part of the system being modeled • Use case represents the discrete activities performed by the user • Use Case Diagram tells what the system will do • Good for communicating with users

  11. Use Case Diagram Syntax • Actor • person or system that derives benefit from and is external to the subject • Use Case • Represents a major piece of system functionality • Association Relationship • Include Relationship • Extend Relationship • Generalization Relationship <<includes>> <<extends>>

  12. Use Case • A major piece of system functionality • Can extend otherUse Cases • Placed inside system boundary • Labeled with descriptiveverb-noun phrase Use Case

  13. System Boundary Boundary • Includes the nameof the systeminside or on top • Represents thescope of the system • Actors are outside the scope of the system

  14. Actor • A person or anothersystem that interactswith the current system • A role, not a specific user • Provides input, receives output, or both actor Actor/Role

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

  16. Extends Relationship • Extends Use Case to include Optional behavior • Arrow points from the extension Use Case to the base Use Case extend MakeAppointment extend Make Payment Arrangement

  17. Include Relationship • Include one Use Case from within another • Arrow points from base Use Case to the included Use Case include include Create New Patient Make New Patient Appointment

  18. Generalization Relationship • A specialized Use Case to a more generalized Use Case • Arrow points from specialized to general Use Case Make OldAppointment MakeAppointment

  19. Use Case Diagram for Appointment System

  20. Use Case Diagram with Specialized Actor

  21. Extend and Include Relationships

  22. StudiKasus: ATM System

  23. ATM System

  24. ATM System Layar KotakUang KotakKartu KotakKuitansi

  25. Masukkan PIN: KotakUang KotakKartu KotakKuitansi

  26. Menu Utama • MelihatSaldo • MentransferUang • MengambilUang • Logout KotakUang KotakKartu KotakKuitansi

  27. Menu MelihatSaldo • Saldoandaadalah …. KotakUang KotakKartu KotakKuitansi

  28. Menu MentransferUang • No Account Penerima: KotakUang KotakKartu KotakKuitansi

  29. Menu MentransferUang • Jumlahuang yang dikirim: KotakUang KotakKartu KotakKuitansi

  30. Menu MentransferUang • Uangberhasilterkirim KotakUang KotakKartu KotakKuitansi

  31. Menu MengambilUang • Jumlahuang yang diambil: KotakUang KotakKartu KotakKuitansi

  32. Menu MengambilUang Uangberhasildiambil KotakUang KotakKartu KotakKuitansi

  33. Use Case Diagram

  34. UseCase Diagram (Alternatif)

  35. 2. Business Process Modeling

  36. System Analysis and Design with UML • System Analysis • 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)

  37. 2.1 Business Process Modeling: Activity Diagram

  38. BPM With Activity Diagrams • A number of activities support a business process across several departments • Activity diagrams model the behavior in a business process

  39. Actions and Activities • Performed for a specific business reason • Names begin with a verb and end with a noun • “Make Appointment” • Each activity normally associated with a use case

  40. Object Nodes • Activity and Actions usually modify objects • Object nodes model these objects • Objects represent a flow of information from between activities or actions

  41. Control & Object Flows • Control Flows (solid line) • Paths of execution through the business process • Can only be attached to actions or activities • Object Flows (dashed line) • Model the flow of objects through a business process • Show actual objects entering and exiting the system • An object is on one end, an action or activity is on the other end

  42. Control Nodes • Initial – Only one, at top left • Final Activity – Stop the process • Final Flow – Stop this flow only • Decision – Guarded test conditions • Merge – Following decisions • Fork – Split parallel execution • Join – Join parallel execution

  43. Swimlanes • The business process may be broken into persons of responsibility • Identify this with swimlanes

  44. Activity Diagram Example

  45. Creating Activity Diagrams • Set the context or scope of the activity being modeled • Identify the activities and control/object flows between activities • Identify any decisions made • Look for opportunities for parallelism • Draw the diagram

  46. 2.2 Business Process Modeling: Business Process Modeling Notation

More Related