0% found this document useful (0 votes)
16 views

Chapter2 The Design Rules 2.2.4

Uploaded by

Fahmi Mahizar
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
16 views

Chapter2 The Design Rules 2.2.4

Uploaded by

Fahmi Mahizar
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 25

Chapter 2

Explain Design
Rationale

Prepared by Mdm PYTan


LEARNING OUTCOME:

• Organize a various styles of interfaces


interaction of software and hardware
products (P3, PLO2)

Prepared by Mdm PYTan


Design Rationale
• Is the information that explains why a
computer system is the way it is, including :
- its structural or architectural description
- its functional or behavioral description
Design rationale
• There are THREE type Design rationale:
– Process-oriented design rationale
– Design space analysis (Structure-oriented )
– Psychological design rationale
Process-oriented design rationale
• Is based on Rittel’s issue-based information
system (IBIS)
• A style for representing design and planning
dialog develop in 1970s.
Process-oriented design rationale
• IBIS : is a hierarchical structure to a design
rationale is created
• Issues : a root issue is identified which
represents the main problem or question that
the argument is addressing
• Position : various positions are put forth as
potential resolutions for the root issue
• Argument : modify the relationship between
positions and issues
Process-oriented design rationale
• A graphical version of IBIS has been define
which makes the structure of the design
rationale more apparent visually in the form
of a directed graph which can be directly
edited by the creator of the design rationale
The Structure of a
gIBIS design rationale
Example
• The situation: Our finance data mart is
updated overnight through a batch job that
takes a few hours. This is good enough for
most purposes. However, a small (but very
vocal!) number of users need to be able to
report on transactions that have occurred
within the last hour or so – waiting until the
next day, especially during month-end, is
simply not an option. The dev team had to
figure out the best way to do this.
• The discussion was launched with the issue
stated up-front: How should we update our
data mart during business hours?
Stage 1
Stage 2
Final
Map
Reference
• IBIS example:
– http://eight2late.wordpress.com/2009/04/07/
issues-ideas-and-arguments-a-communication-
centric-approach-to-tackling-project-complexity/
#comments
Design space analysis
(Structured oriented)
• Design space is initially structured by a set of
questions representing the major issues of the
design
• Structured oriented
• QOC (Question Option Criterion)
Design space analysis
• QOC – hierarchical structure:
– Questions (and sub-questions)
• represent major issues of a design
– Options
• provide alternative solutions to the question
– Criteria
• the means to assess the options in order to
make a choice
• DRL(Decision Representation Language) – similar
to QOC with a larger language and more formal
semantics
Design space analysis
Psychological design rationale
Example
• Designing a system to help programmers learn the Smalltalk
OO programming language environment.
• Main task: support learning how Smalltalk works.
• The programmer (user) will perform tasks that help her
answer the questions:
– What can I do: what are the possible operations or functions that this
programming environment allows?
– How does it work: what do the various functions do?
– How can I do this: once I know a particular operation I want to
perform, how I go about programming it?
Scenarios are suggested to test task…
• To address the question ‘What can I do?’:
– Designers describe a scenario whereby the novice
programmer use the system for the first time.
– Provide demos to support user to investigate how
Smallwork programs work.
Psychological claims of system made
explicit…

• Observe user use the system (once the system


running).
• For example, the psychological claim on demo
system, user learns by doing.
• Negative aspect, user may not learn anything
from the demo (may not be interactive).
• The negative aspect can be addressed in new
version.
Benefits of Design Rationale
1. Provides a communication mechanism
among members of a design team to avoid
incorrect assumptions later
2. Accumulated knowledge can be reused which
has similar needs
3. Forces the designer to deliberate more
carefully about design decisions
Benefits of Design Rationale
4. The designer will determine which criteria for
evaluating the options more important
5. The designer indicates all alternatives that
have been investigated
6. Capturing the context in which a design
decision is made will help later when new
products are designed
Discussion:
• How interface design can benefit from design
rationale
• Which design rational will produce the best
result? Explain why?
• Can you combine all design rational to
produce the best result? Explain why?
Prepared by Mdm PYTan

You might also like