Rekayasa Perangkat

Lunak
Aries Saifudin, A.Md., S.T., M.Kom.
0812 883 84 85
aries.saifudin@yahoo.co.id
aries.saifudin@gmail.com

Aries Saifudin

SD Negeri Wonoagung I, Malang (1990)

SMP Negeri Kasembon, Malang (1993)
SMA Negeri Batu, Malang (1996)
Politeknik Universitas Brawijaya, Malang (2000): A.Md. (Teknik
Elektronika)
Universitas Mercu Buana, Jakarta (2006): S.T. (Teknik Informatika)
STMIK ERESHA, Jakarta (2014): M.Kom. (Teknik Informatika)
Dosen Tetap Teknik Informatika Universitas Pamulang
Minat Penelitian: Rekayasa Perangkat Lunak, Sistem Cerdas
Pengalaman: Programmer (microcontroller, desktop, android, dan
web), dan Dosen
Bahasa Pemrograman: Java, VB .NET, Delphi, PHP, HTML, Pascal,
C/C++, Dbase/FoxBase/FoxPro/Clipper, microprocessor (Intel dan
Zilog)

3. Software Development
Notation (UML) and Tools

Analysis Design Paradigm and

Diagrams
1. Data-oriented DFD
2. Process-oriented Flowchart
3. Object-oriented (data + process)
UML

Sejarah UML
In the 90s many people
creating OO diagramming languages
Three different ones created by Grady Booch,
Ivar Jacobson, James Rumbaugh
Joined forces with
Rational (company) to
create Unified Modeling
Langauge (UML)

Sejarah UML
2011

UML 2.4

What is the UML?

UML: Unified Modeling Language
UML can be used for modeling all processes
in the development life cycle and across
different implementation technologies
(technology and language independent)
UML is the standard language for visualizing,
specifying, constructing, and documenting
the artifacts of a software-intensive system
UML is a communication tool for the team,
and other stakeholders

Why Modeling

Business Process

Computer
System

Visual Modeling is modeling using

standard graphical notations

The Triangle of Success in Software

Development

UML Tools

Rational Rose
Visual Paradigm
Enterprise Architect
Microsoft Visio
Star UML
Netbeans UML Plugin

UML 2.0
UML version 2.0 has 14 diagrams
in 2 major groups:
1. Structure Diagrams
2. Behavior Diagrams

UML 2.0 Diagrams Summary

UML Diagrams
Use-Case
Diagram

Statechart
Class Diagram Diagram

add file

DocumentList

Use Case 1

FileMgr

Actor A

Actor B

Document
add( )
delete( )

fetchDoc( )
sortByName( )

name : int
docid : int
numField : int
get( )
open( )
close( )
read( )
sortFileList( )
create( )
fillDocument( )

Use Case 2
FileList
fList
add( )
delete( )

Writing

add file [ numberOffile==MAX ] /

flag OFF
read() fill the
code..

Openning

close file

Use Case 3

close file

Closing

Reading

rep
Repository
(from Persistence)

File

read( )

Deployment
Diagram

GrpFile

name : char * = 0
readDoc( )
readFile( )

Collaboratio
n Diagram

read( )
open( )
create( )
fillFile( )

9: sortByName ( )

Repository

mainWnd : MainWnd

1: Doc view request ( )

DocumentList

Windows95

Window95

FileManager

Windows95

2: fetchDoc( )

Document

gFile : GrpFile

4: create ( )

.EXE

8: fillFile ( )

Windows
NT

user : Clerk

Solaris

fileMgr : FileMgr

.EXE

GraphicFile

3: create ( )

Alpha
UNIX
.EXE

6: fillDocument ( )

File

FileList

Windows
NT

IBM
Mainframe

7: readFile ( )
5: readDoc ( )

document : Document

repository : Repository

mainWnd
user

fileMgr :
FileMgr

document :
Document

gFile

1: Doc view request ( )

2: fetchDoc( )

repository

Component
Diagram

3: create ( )

4: create ( )

5: readDoc ( )

6: fi llDocument ( )

7: readFile ( )

8: fillFile ( )

9: sortByName ( )

Sequence
Diagram

Forward
and
Reverse

Target
Syste
m

UML Structure Diagrams

Represent the data and static
relationships in an information
system
1.
2.
3.
4.
5.
6.

Class Diagram
Object Diagram
Package Diagram
Deployment Diagram
Component Diagram
Composite Structure Diagram

Structure Diagrams
1. Class Diagrams

Common vocabulary used by analyst and users

Represent things (employee, paycheck,)
Shows the relationships between classes

2. Object Diagrams

Similar to class diagrams

Instantiation of a class diagram
Relationships between objects

3. Package Diagrams
Group UML elements together to form
higher level constructs

Structure Diagrams
4. Deployment Diagrams
Shows the physical architecture and software
components of system
For example, network nodes

5. Component Diagrams
Physical relationships among software
components
Example Client/Server (Which machines run
which software)

6. Composite Structure
Illustrates internal structure of a complex class

UML Behavior Diagrams

Depict the dynamic relationships
among the instances or objects that
represent the business information
system
1.
Activity Diagram
2. Sequence Diagram
3. Communication Diagram
4. Interaction Diagram
5. Timing Diagram
6. Behavior State Machine
7. Protocol State Machine

Behavior Diagrams
1. Activity Diagrams

Model processes in an information system

Example: Business workflows, business logic

2. Interaction Diagrams

Shows interaction among objects

3. Sequence Diagrams

Time-based ordering of the interaction

4. Communication Diagrams

Communication among a set of collaborating

objects of an activity

Behavior Diagrams
5.

Interaction Diagrams

6.

Timing Diagrams

7.

State Machines

8.

Use-Case Diagrams

Overview of flow of control of a process

Show how an object changes over time
Examines behavior of one class
Models the different states and state
transitions an object can experience
Shows interaction between the system and
environment
Captures business requirements

UML Problems
UML is modeling notation, it is not a
development process or a
methodology
UML driven development process?

UML is too complex, difficult to

understand quickly
Should we use all UML diagrams?

UML Process (EA Sparx)

1. Display the boundary of a system and its
major functions using use cases and actors
2. Model the organizations business process
with activity diagram
3. Illustrate use case realizations with
sequence diagrams
4. Represent a static structure of a system
using class diagrams
5. Reveal the physical implementation
architecture with deployment diagrams

UML Process (EA Sparx)

1.
2.
3.
4.
5.

Use Cases Diagram

Activity Diagram
Sequence Diagram
Class Diagram
Deployment Diagrams

UML Process (Kendal, 2011)

1. A use case diagram, describing how the system is used.
Analysts start with a use case diagram
2. An activity diagram, illustrating the overall flow of
activities. Each use case may create one activity
diagram
3. Sequence diagrams, showing the sequence of activities
and class relationships. Each use case may create one
or more sequence diagrams
4. Class diagrams, showing the classes and relationships.
Sequence diagrams are used to determine classes
5. Statechart diagrams, showing the state transitions. Each
class may create a statechart diagram, which is useful
for determining class methods

UML Process (Barclay, 2004)

System Analysis and Design with

UML
1. System Analysis
1.

Business Process Identification

2.

Use Case Diagram

Business Process Modeling

3.

Activity Diagram or Business Process Modeling Notation (BPMN)

Business Process Realization

Sequence Diagram (Buat untuk setiap use case dengan menggunakan pola Boundary-ControlEntity)

2. System Design
1.

Program Design
1.

Class Diagram

(Gabungkan Boundary-Control-Entity Class dan susun story dari sistem yang

dibangun)

2.
3.

Package Diagram
(Gabungan class yang sesuai, boleh menggunakan pola B-C-E)
Deployment Diagram (arsitektur software dari sistem yang dibangun)

2. User Interface Design (Buat UI design dari Boundary Class)

3. Entity-Relationship Model (Buat ER diagram dari Entity Class)

References
Dennis, A., Wixom, B. H., & Tegarden, D.
(2009). System Analysis Design UML
Version 2.0. An Object-Oriented Approach
(3rd ed.). New Jersey: John Wiley & Sons.
Pressman, R. S. (2015). Software
Engineering. A Practitioner's Approach (8th
ed.). New York: McGraw-Hill Education.
Sommerville, I. (2011). Software
Engineering (9th ed.). Boston: AddisonWesley.