uml (unified modeling language) -...

UML

(Unified Modeling Language)

What is UML?

UML stands for Unified Modeling Language.

This object-oriented system of notation has evolved from the work of Grady Booch, James Rumbaugh, Ivar Jacobson, and the Rational Software Corporation.

These renowned computer scientists fused their respective technologies into a single, standardized model.

Today, UML is accepted by the Object Management Group (OMG) as the standard for modeling object oriented programs.

Andi Sunyoto, M.Kom 2

Types of UML Diagrams

UML defines nine types of diagrams:

class (package),

object,

use case,

sequence,

collaboration,

statechart,

activity,

component, and

deployment.


USE CASE DIAGRAM


What is a UML Use Case Diagram?

The use case model captures the requirements of a system.

Use cases are services or functions provided by the system to its users.

A use case is a set of scenarios that describing an interaction between a user and a system.

Use case diagrams model the functionality of a system using actors and use cases.


The two main components of a use case diagram are use cases and actors.

An actor is represents a user or another system that will interact with the system you are modeling.

A use case is an external view of the system that represents some action the user might perform in order to complete a task.


System

Draw your system's boundaries using a rectangle that contains use cases. Place actors outside the system's boundaries.


Use Case Symbol

Use Case

Draw use cases using ovals. Label with ovals with verbs that represent the system's functions.


Actors

Actors are the users of a system.

When one system is the actor of another system, label the actor system with the actor stereotype.


Relationships

Illustrate relationships between an actor and a use case with a simple line. For relationships among use cases, use arrows labeled either "uses" or "extends." A "uses" relationship indicates that one use case is needed by another in order to perform a task. An "extends" relationship indicates alternative options under a certain use case.


Tipe relationship

Associations

Includes

Generalization

Extends


Associations

On a use case diagram, associations are drawn between actors and use cases to show that an actor carries out a use case.

A use case can be carried out by many actors and an actor may carry out many use cases.

In the above diagram, the actors are shown as the green stick figure shapes on the left, the use cases are the blue ellipses, and the associations between them are represented by the connecting lines.

The developer and the stakeholder both are responsible for specifying the system roles, but only the developer creates the model.


Includes

Within an include relationship, one use case explicitly includes the behavior of another use case at a specified point within a course of action.

The included use case doesn't stand alone; it has to be connected with one or more base use cases. The include mechanism is very useful for factoring out behavior that would otherwise appear within multiple use cases.


Within Figure, the Add to Wish List and Check Out use cases include the behavior captured within the Log In use case, because a Customer must be logged in before he or she can add a book to a wish list or make a purchase.


Generalization

Generalization refers to a relationship between a general case and a more specific version.

Generalization is used to express some high-level functional need of a system without going into specifics. Specializations of a general use case introduce specific functionality.

Figure shows use cases that describe three different searches that a Customer can perform, all of which use the basic search technique defined by the Perform Search use case.


Extends

Within an extend relationship, a base use case implicitly includes the behavior of another use case at one or more specified points. These points are called extension points.

You generally use this construct to factor out behavior that's optional or that occurs only under certain conditions. One way to use extends is in creating a new use case in response to an alternate course of action having several steps associated with it.

Figure shows that a Customer has the option of canceling an Order in conjunction with checking the status of that Order.


Contoh Use Case #1


Contoh Use Case #2


Contoh Use Case #3


Contoh Use Case #4


Contoh Use Case #5


Referensi http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/what_is_uml.htm

http://www.smartdraw.com/resources/tutorials/UML-Sequence-Diagram

http://www.visualcase.com/tutorials/use-case-diagram.htm

http://www.visual-paradigm.com/VPGallery/usecase/index.html

Building Web Applications with UML Second Edition, By Jim Conallen, Publisher : Addison Wesley

Fast Track UML 2.0, by Kendall Scott, Apress © 2004

UML 2.0 in a Nutshell, By Dan Pilone, Neil Pitman, Publisher: O'Reilly


http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/what_is_uml.htm














CLASS DIAGRAM


What is Class Diagram ?

The class diagram is core to object-oriented design.

It describes the types of objects in the system and the static relationships between them.

Illustrate classes with rectangles divided into compartments.

Place the name of the class in the first partition (centered, bolded, and capitalized), list the attributes in the second partition, and write operations into the third.


Sample Class Diagram

Classes are divided into three sections: Top: The name, package and stereotype are shown in the upper

section of the class. You can optionally assign a stereotype to a class.

Centre: The centre section contains the attributes of the class.

Bottom: In the lower section are the operations that can be performed on the class.


Attributes

An attribute is a property of a class. In the example above, we are told that a Contact has an address, a city, a province, a country and a postal code.

The format for attributes is:

visibility name: type = defaultValue

The visibility is as follows:

- Private : Private visibility hides information from anything outside the class partition.

+ Public : Public visibility allows all other classes to view the marked information.

# Protected : Protected visibility allows child classes to access information they inherited from a parent class.


In object oriented design, it is generally preferred to keep most attributes private as the accessor methods allow you to control access to the data.

The most common exception to this preference are constants.


Operation

The operations listed in a class represent the functions or tasks that can be performed on the data in the class.

In the List class, there is one attribute (a private array of Objects) and three operations.


The format for operations is:

visibility name (parameters): type

The format is very similar to that of the attribute except with the removal of a default value and the addition of parameters.

Parameters take the format:

direction name: type = default value


Class Relationship

Class diagrams also display relationships:

inheritance,

associations and others.2

Below is an example of an associative relationship:


The association relationship is the most common relationship in a class diagram.

The association shows the relationship between instances of classes.

For example, the class Order is associated with the class Customer.

The multiplicity of the association denotes the number of objects that can participate in then relationship.

For example, an Order object can be associated to only one customer, but a customer can be associated to many orders.


Generalization

A generalization is used when two classes are similar, but have some differences. Look at the generalization below:


Contoh Class Diagram


uml (unified modeling language) -...

Documents