introduction to unified modelling language
DESCRIPTION
Introduction to Unified Modelling Language. Tujuan. Mengetahui latar belakang terbentuknya UML Mengetahui tentang Unified Process ( UP). Definisi. - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/1.jpg)
Introduction to Unified Modelling Language
![Page 2: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/2.jpg)
Slide 2
Tujuan Mengetahui latar belakang terbentuknya UML Mengetahui tentang Unified Process (UP)
![Page 3: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/3.jpg)
Slide 3
Definisi
A language for specifiying, constructing, visualizing, and documenting the artifacts of a software-intensive system for
Business Modelling and other non-software systems
![Page 4: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/4.jpg)
Slide 4
Background
![Page 5: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/5.jpg)
Slide 5
Authors
![Page 6: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/6.jpg)
Slide 6
Development Process
![Page 7: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/7.jpg)
Slide 7
UML Building Blocks
![Page 8: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/8.jpg)
Slide 8
Things : Structural Define the static part of the model. Represents physical and conceptual
elements. Including :
Class Interface Collaboration : a collection of UML building
blocksUse case : a set of actions represents by a
systemComponent : physical part of a systemNode : a physical element that exist at run-
time & represents a computational resource (typically, hardware resources)
![Page 9: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/9.jpg)
Slide 9
Things : Behavioural Consists of the dynamic parts of UML models. Include :
Interaction : messages exchanged among objects
State machine : sequence of states of an object during its lifetime
![Page 10: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/10.jpg)
Slide 10
Things : Grouping Grouping elements of UML models together. Include :
Package : conceptual grouping of the systems
![Page 11: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/11.jpg)
Slide 11
Things : Annotational A mechanism to capture remarks,
descriptions, and comments of UML model elements
Include :Note
![Page 12: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/12.jpg)
Slide 12
Relationship Shows how elements are associated with
each other. Describe the functionality of an application.
![Page 13: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/13.jpg)
Slide 13
Jenis RelationshipDependency: Dependency is a relationship between two things in which change in one element also affects the other one.Association: Association is basically a set of links that connects elements of an UML model. It also describes how many objects are taking part in that relationship.Generalization:Generalization can be defined as a relationship which connects a specialized element with a generalized element. It basically describes inheritance relationship in the world of objects.Realization:Realization can be defined as a relationship in which two elements are connected. One element describes some responsibility which is not implemented and the other one implements them. This relationship exists in case of interfaces.
![Page 14: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/14.jpg)
Slide 14
UML Diagrams
![Page 15: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/15.jpg)
Slide 15
Diagram di UML 2.0
![Page 16: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/16.jpg)
Slide 16
Unified Process Definition : The unified process provides a
disciplined approach to assigning tasks and responsibilities within a development organization, to ensure production of a high-quality software product that meets the needs of its end users within a predictable schedule and budget.
![Page 17: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/17.jpg)
Slide 17
Prinsip UP
![Page 18: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/18.jpg)
Slide 18
Manage Requirements Describes how to elicit, organize, and
document required functionality and constraints; track and document tradeoffs and decisions; and easily capture and communicate business requirements
![Page 19: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/19.jpg)
Slide 19
Develop Iteratively Given today’s sophisticated software systems,
it is not possible to sequentially first define the entire problem, design the entire solution, build the software and then test the product at the end.
An iterative approach is required that allows an increasing understanding of the problem through successive refinements, and to incrementally grow an effective solution over multiple iterations.
![Page 20: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/20.jpg)
Slide 20
Visually Model Software The process shows you how to visually model
software to capture the structure and behavior of architectures and components.
This allows you to hide the details and write code using “graphical building blocks.”
Visual abstractions help you communicate different aspects of your software; see how the elements of the system fit together; make sure that the building blocks are consistent with your code; maintain consistency between a design and its implementation; and promote unambiguous communication
![Page 21: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/21.jpg)
Slide 21
Verify Software Quality Quality should be reviewed with respect to
the requirements based on reliability, functionality, application performance and system performance.
Quality assessment is built into the process, in all activities, involving all participants, using objective measurements and criteria, and not treated as an afterthought or a separate activity performed by a separate group.
![Page 22: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/22.jpg)
Slide 22
Use Component-based Architecture
It describes how to design a resilient architecture that is flexible, accommodates change, is intuitively understandable, and promotes more effective software reuse.
Components are non-trivial modules, subsystems that fulfill a clear function.
![Page 23: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/23.jpg)
Slide 23
Control Changes to Software The ability to manage change is making
certain that each change is acceptable, and being able to track changes is essential in an environment in which change is inevitable.
The process describes how to control, track and monitor changes to enable successful iterative development.
![Page 24: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/24.jpg)
Slide 24
UP Axioms Use-case and risk driven Architecture centric Iterative and incremental Supports object oriented techniques A configurable process Encourages ongoing quality control and risk
management
![Page 25: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/25.jpg)
Slide 25
Alur Iterasi
![Page 26: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/26.jpg)
Slide 26
Pemetaan SDLC dalam Fase UP
![Page 27: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/27.jpg)
Slide 27
Fase 1 : Inception Define the scope of the project and develop
business caseGoal: Get the project of the ground
The goal is to achieve concurrence among all stakeholders on the lifecycle objectives for the project.
To get the project of the groundThe primary objectives of the inception phase
include:Establishing feasibilityCreating a business caseCapturing essential requirementsIdentifying critical risksEstimating the overall cost and schedule for the
entire projectFocus on requirements and analysisMilestone: Life cycle objectives
![Page 28: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/28.jpg)
Slide 28
Fase 2 : Elaboration Plan project, specify features, and baseline
the architectureGoals:
Create an executable architectural baselineRefine the risk assessmentCapture use cases to 80% of the functional
requirementsCreate a detailed plan for the construction phase
Milestone: Life cycle architecture
![Page 29: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/29.jpg)
Slide 29
Fase 3 : Construction Build the product
Goals:To complete all requirements, analysis and
design into a final system.Focus:Requirements
Uncover missed requirementsAnalysis
Finish the analysis modelDesign
Finish the design modelImplementation
Build the initial operational capabilityTest
Milestone: Initial Operational Capability
![Page 30: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/30.jpg)
Slide 30
Fase 4 : Transition Transition the product to its users
Starts when beta testing is completed and the system is deployed
Goals:Correct defectsTailor the software to operate at the user siteCreate manuals
Milestone: product release
![Page 31: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/31.jpg)
Slide 31
Pengembangan UP
![Page 32: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/32.jpg)
Slide 32
Minimalis OO Software AD
![Page 33: Introduction to Unified Modelling Language](https://reader035.vdocuments.net/reader035/viewer/2022062302/5681637e550346895dd45e43/html5/thumbnails/33.jpg)
Slide 33
References http://www.sa-depot.com Rational Company. Rational Unified Process :
Best Practices for Software Development Teams.
Dennis, Alan, et.al. System Analysis and Design with UML Version 2.0. John Wiley & Sons, Inc.