Usability Through Software Design Final

Usability through Software
Design
This require dealing with software Architecture and Design
Group No . 01 ASSA MSSE

Fall 15
Safwan Hashmi
Sabah-ud-Din waqar
Farrukh Latif
OBJECTIVES
Is to put another brick in the wall by defining guidelines to help the developers build specific usability characteristics into their application in
order to reduce development time , Complexity and Improving the quality of the software.
USABILITY
USEABILITY GUIDELINES FOR SOFTWARE DEVELOPMENT
USABILITY GUIDELINES IN USE
EMPIRICAL STUDY
REF: IEEE TRANSACTION ON SOFTWARE ENGINEERING VOL. 39, NO. 11, NOVEMBER
2013
Laura Carvajal, Ana
M. Moreno, Maria-Isabel Sanchez-Segura, and Ahmed Seffah
SECTIONS
USABILITY
MOTIVATION AND BACKGROUND
USEABILITY GUIDELINES FOR SOFTWARE DEVELOPMENT
WARNING USABILITY GUIDLINES
USABILITY GUIDELINES IN USE
EMPIRICAL STUDY
SECTION I - WHAT IS
USABILITY
EASE OF LEARING
EASE OF USE
EASE OF REMEMBERING
EFFICIENCY OF USE
EFFECTIVENESS OF USE
SECTION 1- ISO USABILITY
The capability of a software product to be understood, learned, used and

attractive to the user
2013
Laura Carvajal, Ana
SECTION II MOTIVATIONAL BACKGROUND
Bass et al. sequence diagrams for each of the chosen usability scenarios.
John et al Text-based recommendations for software architects as an integral part of their solutions.
Ferre et al. Incorporated usability patterns into the architecture of software applications.
Seffah et al. Proposed an algorithm for matching solutions to existing patterns.
Above research efforts do not provide any means of traceability between the proposed design solutions and software requirements
2013
Laura Carvajal, Ana
SECTION III- USABILITY GUIDELINES OF SOFTWARE DEVELOPMENT

The aim of this research is to provide software developers with recommendations to help them incorporate certain usability features into
software systems.
They have named these recommendations Usability Guidelines, from which Usability Design Guidelines are the main
contribution of this work.
ANALYSIS ARTIFACTS
DESIGN ARTIFACTS
REF: IEEE TRANSACTION ON SOFTWARE ENGINEERING VOL. 39, NO. 11, NOVEMBE
2013
Laura Carvajal,
SECTION III- ANALYSIS ARTIFACTS

The Usability Requirements Analysis guideline is made up of the following 4 artifacts:
Usability Elicitation Guideline , aim is to help in eliciting usability requirements
Usability Elicitation Cluster , a graphic representation of the Usability Elicitation Guideline, designed partly to help analysts
understand the flow of the requirements discussion items
3
4
Usability Use Case Meta Model ,

in their use case models
a use case representation of the usability needs covered by the UEG to help designers include them
System Responsibilities, are the main functionalities that the system should accomplish in order to fulfill all of what has been elicited
with the UEG.
2013
Laura Carvajal, Ana
SECTION III- DESIGN ARTIFACTS

The Usability Design guideline is made up of the following 3 artfacts:
High level design component responsibility for usability, given an abstract description of the system responsibilities (Software
Components).
Low level design component responsibility for usability , given an concreate description of the system responsibilities in term of
classes, method.
Software design Meta Model,
are the UML representation of low level design component responsibilities for usability.
2013
Laura Carvajal, Ana
SECTION IV - EXAMPLE : WARNING USABILITY GUIDLINES

The warning feature deals with the users need to receive different alert types upon execution of sensitive (potentially damaging) actions.
In this section, we briefly describe the usability guideline developed for this feature.
ANALYSIS ARTIFACT
DESIGN ARTIFACT
Usability Elicitation
Guideline
High level design component responsibility for usability
Usability Elicitation Cluster
Low level design component responsibility for

usability
3
4
Usability Use Case Meta
Software design Meta Model
System Responsibilities
2013
Laura Carvajal, Ana

ANALYSIS ARTIFACT Usability Elicitation Guidelines
2013
Laura Carvajal, Ana
ANALYSIS ARTIFACT Usability Elicitation Cluster
2013
Laura Carvajal, Ana
ANALYSIS ARTIFACT Use Case Metamodeling
2013
Laura Carvajal, Ana
ANALYSIS ARTIFACT System Responsibilities
2013
Laura Carvajal, Ana
DESIGN ARTIFACT High level design component responsibilities
2013
Laura Carvajal, Ana
DESIGN ARTIFACT Low level design component responsibilities
2013
Laura Carvajal, Ana
DESIGN ARTIFACT Usability Software Design Metamodels
2013
Laura Carvajal, Ana
SECTION V - USABILITY GUIDELINES IN USE

The aim of this research is to provide software developers with recommendations to help them incorporate certain usability features into
software systems.
They have named these recommendations Usability Guidelines, from which Usability Design Guidelines are the main
contribution of this work.
ELICITATION AND ANALYSIS
DESING
2013
Laura Carvajal, Ana

Elicitation and Analysis
During elicitation the analyst, gathers a list of requirements.
One of these requirements is shown is below :
The system must allow users to delete any task from their task list.
The analyst will use the usability elicitation guideline and usability elicitation cluster map to add usability Information to functional
requirements like
For example, adding usability information about the warning feature would imply redefining the requirement as Req(3)
The system must allow users to delete any task from their task list. It must show an alert asking the user to confirm the
action before permanently deleting the task.
In this case stakeholders suggest a list of actions
2013
Laura Carvajal, Ana
2013
Laura Carvajal, Ana

The system use case model will
contain use cases like the ones
depicted in gray
2013
Laura Carvajal, Ana

Software design, the development team identifies the
high- and/or low-level design component responsibilities
that will be present in their system. discard
responsibilities that correspond to the previously
discarded system responsibilities and retain only the
applicable component responsibilities
2013
Laura Carvajal, Ana

A partial view of the class diagram not considering
usability for this example might be made up of the
domain classes shown in gray in Fig below.
2013
Laura Carvajal, Ana
2013
Laura Carvajal, Ana
2013
Laura Carvajal, Ana
SECTION VI- EMPIRICAL STUDY

The Purpose this research was Reduce Development Time, Reduce Perceived Complexity, Improve Design Qualities.
HYPOTHESES
EXPERIMENTAL DESING
EXPERIMENTAL PROCEDURE
DATA
ANALYSIS
2013
Laura Carvajal, Ana
EMPIRICIAL STUDY - HYPOTHESES

As there are three possible modes of use (NG,PG,FG), the research hypotheses are refined for validation purpose as below .
H0-1. There are no significant differences in mean development time among the three modes of use.
H-1. There are significant differences in mean development time among the three modes.
H0-2. There are no significant differences in mean perceived complexity among the three modes.
H-2. There are significant differences in mean perceived complexity among the three modes
H0-3. There are no significant differences in mean design quality among the three modes.
H-3. There are significant differences in mean design quality among the three modes.
2013
Laura Carvajal, Ana
EMPIRICAL STUDY Experimental Design

1
VARIABLES - Independent Variables (modes of use NG,PG,FG) , Dependent Variables (Mean time, Complexity and Design quality
EXPERIMENTAL UNITS - Online Task Manager, Console for a home automation system , Auction Site
PARTICIPANTS - 9 Participant
2013
Laura Carvajal, Ana
EMPIRICAL STUDY Experimental Procedures

Project are allocated to Participant by dividing into three categories . PG, FG and NG
45 Minutes tutorial guideline to FG participants on design and analysis

artefacts.
15 Minutes tutorial guideline to PG participants on analysis

artefact only.
No tutorial guideline to NG participants
2013
Laura Carvajal, Ana
EMPIRICAL STUDY - Data

The Purpose this research was Reduce Development Time, Reduce Perceived Complexity, Improve Design Qualities.
Development Time Data
Perceived Complexity Data
Design Quality Data
2013
Laura Carvajal, Ana
EMPIRICAL STUDY - Analysis

1
Development Time
2013
Laura Carvajal, Ana

2
Perceived Complexity
2013
Laura Carvajal, Ana

3
Design Quality
2013
Laura Carvajal, Ana
CONCLUSIONS
In this paper, we set out to contribute to this field by proposing usability guidelines for software development describing a possible solution for
incorporating some of the best-known usability features into software applications. The key guideline artifacts specify the responsibilities that the
system and its parts must fulfill to conform to these usability features, making them directly implementable from design.
ANY QUESTION?

Usability Through Software Design Final

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Usability Through Software Design Final

Загружено:

Авторское право:

Доступные форматы

Usability through Software

Group No . 01 ASSA MSSE

USEABILITY GUIDELINES FOR SOFTWARE DEVELOPMENT

USABILITY GUIDELINES IN USE

MOTIVATION AND BACKGROUND

USEABILITY GUIDELINES FOR SOFTWARE DEVELOPMENT

WARNING USABILITY GUIDLINES

USABILITY GUIDELINES IN USE

SECTION 1- ISO USABILITY

The capability of a software product to be understood, learned, used and

SECTION II MOTIVATIONAL BACKGROUND

Seffah et al. Proposed an algorithm for matching solutions to existing patterns.

SECTION III- USABILITY GUIDELINES OF SOFTWARE DEVELOPMENT

SECTION III- ANALYSIS ARTIFACTS

Usability Elicitation Guideline , aim is to help in eliciting usability requirements

Usability Use Case Meta Model ,

SECTION III- DESIGN ARTIFACTS

Software design Meta Model,

SECTION IV - EXAMPLE : WARNING USABILITY GUIDLINES

High level design component responsibility for usability

Usability Elicitation Cluster

Low level design component responsibility for

Usability Use Case Meta

Software design Meta Model

SECTION IV - EXAMPLE : WARNING USABILITY GUIDLINES

SECTION IV - EXAMPLE : WARNING USABILITY GUIDLINES

ANALYSIS ARTIFACT Usability Elicitation Cluster

SECTION IV - EXAMPLE : WARNING USABILITY GUIDLINES

ANALYSIS ARTIFACT Use Case Metamodeling

SECTION IV - EXAMPLE : WARNING USABILITY GUIDLINES

ANALYSIS ARTIFACT System Responsibilities

SECTION IV - EXAMPLE : WARNING USABILITY GUIDLINES

DESIGN ARTIFACT High level design component responsibilities

SECTION IV - EXAMPLE : WARNING USABILITY GUIDLINES

DESIGN ARTIFACT Low level design component responsibilities

SECTION IV - EXAMPLE : WARNING USABILITY GUIDLINES

DESIGN ARTIFACT Usability Software Design Metamodels

SECTION V - USABILITY GUIDELINES IN USE

ELICITATION AND ANALYSIS

SECTION V - USABILITY GUIDELINES IN USE

SECTION V - USABILITY GUIDELINES IN USE

SECTION V - USABILITY GUIDELINES IN USE

SECTION V - USABILITY GUIDELINES IN USE

SECTION V - USABILITY GUIDELINES IN USE

SECTION V - USABILITY GUIDELINES IN USE

SECTION V - USABILITY GUIDELINES IN USE

SECTION VI- EMPIRICAL STUDY

EMPIRICIAL STUDY - HYPOTHESES

EMPIRICAL STUDY Experimental Design

EMPIRICAL STUDY Experimental Procedures

45 Minutes tutorial guideline to FG participants on design and analysis

15 Minutes tutorial guideline to PG participants on analysis

No tutorial guideline to NG participants

EMPIRICAL STUDY - Data

Development Time Data

Perceived Complexity Data

Design Quality Data

EMPIRICAL STUDY - Analysis

EMPIRICAL STUDY - Analysis

EMPIRICAL STUDY - Analysis

Вам также может понравиться