Introduction to Unified Modelling Language

Slide 2

Tujuan Mengetahui latar belakang terbentuknya UML Mengetahui tentang Unified Process (UP)

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

Slide 4

Background

Slide 5

Authors

Slide 6

Development Process

Slide 7

UML Building Blocks

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)

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

Slide 10

Things : Grouping Grouping elements of UML models together. Include :

Package : conceptual grouping of the systems

Slide 11

Things : Annotational A mechanism to capture remarks,

descriptions, and comments of UML model elements

Include :Note

Slide 12

Relationship Shows how elements are associated with

each other. Describe the functionality of an application.

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.

Slide 14

UML Diagrams

Slide 15

Diagram di UML 2.0

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.

Slide 17

Prinsip UP

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

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.

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

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.

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.

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.

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

Slide 25

Alur Iterasi

Slide 26

Pemetaan SDLC dalam Fase UP

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

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

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

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

Slide 31

Pengembangan UP

Slide 32

Minimalis OO Software AD

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.