Rekayasa Perangkat Lunak

User Interface Design

Pertemuan : Ke-sembilan

Jakarta, 14 Juni 2022

Ir. Kezaldo Firdaus , MM

Requirements Model -> Design Model

Co m p o n e n t -
s c e na rio - ba s e d f lo w- o rie nt e d Le v e l D e s ig n
e le me nt s e le me nt s
use-cases - text data flow diagrams
use-case diagrams control-flow diagrams
activity diagrams processing narratives
s wim lane diagrams
In t e rf a c e D e s ig n
Ana lysis Mode l

A rc h it e c t u ra l D e s ig n
c la ss- ba se d be ha v io ra l
e le me nt s e le me nt s
class diagrams state diagrams
analysis packages sequence diagrams
CRC models D a t a / Cla s s D e s ig n
collaboration diagrams

Desig n Mod el

These slides are designed to

accompany Software
 Design
• The data/class design transforms class models into design class
realizations and the requisite data structures required to implement
the software. The objects and relationships defined in the CRC
diagram and the detailed data content depicted by class attributes and
other notation provide the basis for the data design action. Part of class
design may occur in conjunction with the design of software
architecture.
• The architectural design (framework of a computer-based system)
defines the relationship between major structural elements of the
software, the architectural styles and design patterns that can be used
to achieve the requirements defined for the system, and the constraints
that affect the way in which architecture can be implemented.

These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.
Design
• The interface design describes how the software communicates with
systems that interoperate with it, and with humans who use it. An
interface implies a flow of information (data/control) and a specific
type of behavior. Therefore, usage scenarios and behavioral models
provide much of the information needed.
• The component-level design transforms structural elements of the
software architecture into a procedural description of software
components. Information obtained from the class-based models, flow
models, and behavioral models serve as the basis for component
design.

These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.
 Design and Quality

• The importance of design can be stated with a single word – quality. It

is the place where quality is fostered in software engineering. Design
provides you with representations of software that can be assessed for
quality. Design is the only way that you can accurately translate
stakeholder’s requirements into a finished software products or
system.
• Software design serves as the foundation for all the software
engineering and support activities that follow.
• Without design, you risk building an unstable system – one that will
fail when small changes are made; one that may be difficult to test; one
whose quality cannot be assessed until late in the software process,
when time is short and many dollars have already been spent.

These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.
 Design Process
• It is an iterative process through which requirements are translated
into a “blueprint” for constructing the software.

• Initially, the blueprint depicts a holistic view of software. That is the

design is represented at a high level of abstraction- a level that can be
directly traced into the specific system objective and more detailed
data, functional, and behavioral requirements.

• As design iteration occur, subsequent refinement leads to design

representations at much lower level of abstraction with subtle
connection to requirements.

These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.
Design Model Elements
• Data elements
– Data model --> data structures
– Data model --> database architecture
• Architectural elements
– Application domain
– Analysis classes, their relationships, collaborations and
behaviors are transformed into design realizations
– Patterns and “styles” (Chapters 9 and 12)
• Interface elements
– the user interface (UI)
– external interfaces to other systems, devices,
networks or other producers or consumers of
information
– internal interfaces between various design
components.
• Component elements
•7 Deployment elements

These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.
 Interface Elements
 How information flows Mo b ile Ph o n e

in and out of the system

Wire le s s PDA

and how components

communicate and
collaborate. Co n t ro lPa n e l

 Three major elements: LCDdis pla y

LEDindic a t ors
 User interface ke yPa dCha ra c t e ris t ic s
s pe a ke r
Ke y Pa d

wire le s s Int e rfa c e

 External interface to other re a dKe ySt roke ()

system, device, networks de c ode Ke y ()

dis pla ySt a t us ()
light LEDs ()
or producers or consumers s e ndCont rolMs g( )

of information < < in t e rfa c e > >

Ke y Pa d

 Internal interfaces between re a dKe ys t roke()

components. de c ode Ke y()

8
Fig u re 9 . 6 UML in t e rfa c e re p re s e n t a t io n fo r Co n t ro lP a n e l

These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.
Interface Elements

These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.
Referensi
• Software Engineering : Practioner’s Approach - Pressman
• Software Engineering – Tenth Edition – Ian Sommerville
• Modul Perkuliahan – Rekayasa Perangkat Lunak – Universitas Mercu
Buana