usability through software design final

Usability through Software DesignThis require dealing with software Architecture and Design

Group No . 01 ASSA MSSE Fall 15Safwan HashmiSabah-ud-Din waqarFarrukh Latif

OBJECTIVES

1 USABILITY

2 USEABILITY GUIDELINES FOR SOFTWARE DEVELOPMENT

3 USABILITY GUIDELINES IN USE

REF: IEEE TRANSACTION ON SOFTWARE ENGINEERING VOL. 39, NO. 11, NOVEMBER

2013 Laura Carvajal, Ana

M. Moreno, Maria-Isabel Sanchez-Segura, and Ahmed Seffah

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.

4 EMPIRICAL STUDY

SECTIONS

1 USABILITY

2 MOTIVATION AND BACKGROUND

3 USEABILITY GUIDELINES FOR SOFTWARE DEVELOPMENT

4 WARNING USABILITY GUIDLINES

5 USABILITY GUIDELINES IN USE

6 EMPIRICAL STUDY

SECTION I - WHAT IS USABILITY

1 EASE OF LEARING

2 EASE OF USE

3 EASE OF REMEMBERING

4 EFFICIENCY OF USE

5 EFFECTIVENESS OF USE

SECTION 1- ISO – USABILITY

“The capability of a software product to be understood, learned, used and attractive to the user “




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

SECTION III- USABILITY GUIDELINES OF SOFTWARE DEVELOPMENT

1 ANALYSIS ARTIFACTS

2 DESIGN ARTIFACTS




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.

SECTION III- ANALYSIS ARTIFACTS

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

2 Usability Elicitation Cluster , a graphic representation of the Usability Elicitation Guideline, designed partly to help analysts

understand the flow of the requirements discussion items




The Usability Requirements Analysis guideline is made up of the following 4 artifacts:

3 Usability Use Case Meta Model , a use case representation of the usability needs covered by the UEG to help designers include them

in their use case models

4 System Responsibilities, are the main functionalities that the system should accomplish in order to fulfill all of what has been elicited

with the UEG.

SECTION III- DESIGN ARTIFACTS

1 High level design component responsibility for usability, given an abstract description of the system responsibilities (Software

Components).

2 Low level design component responsibility for usability , given an concreate description of the system responsibilities in term of

classes, method.




The Usability Design guideline is made up of the following 3 artfacts:

3 Software design Meta Model, are the UML representation of low level design component responsibilities for usability.

SECTION IV - EXAMPLE : WARNING USABILITY GUIDLINES

1 Usability Elicitation

Guideline

2 Usability Elicitation Cluster




ANALYSIS ARTIFACT

3 Usability Use Case Meta

4 System Responsibilities

1 High level design component responsibility for usability

2 Low level design component responsibility for

usability

3 Software design Meta Model

DESIGN ARTIFACT

The warning feature deals with the user’s 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 – Usability Elicitation Guidelines





ANALYSIS ARTIFACT – Usability Elicitation Cluster





ANALYSIS ARTIFACT – Use Case Metamodeling





ANALYSIS ARTIFACT – System Responsibilities





DESIGN ARTIFACT – High level design component responsibilities





DESIGN ARTIFACT – Low level design component responsibilities





DESIGN ARTIFACT – Usability Software Design Metamodels

SECTION V - USABILITY GUIDELINES IN USE

1 ELICITATION AND ANALYSIS

2 DESING




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• 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





The system use case model will contain use cases like the ones depicted in gray





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





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.

SECTION VI- EMPIRICAL STUDY

1 HYPOTHESES

2 EXPERIMENTAL DESING




The Purpose this research was Reduce Development Time, Reduce Perceived Complexity, Improve Design Qualities.

3 EXPERIMENTAL PROCEDURE

4 DATA

5 ANALYSIS

EMPIRICIAL STUDY - HYPOTHESES




1 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.

2 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

3 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.

As there are three possible modes of use (NG,PG,FG), the research hypotheses are refined for validation purpose as below .

EMPIRICAL STUDY – Experimental Design

1 VARIABLES - Independent Variables (modes of use NG,PG,FG) , Dependent Variables (Mean time, Complexity and Design quality

2 EXPERIMENTAL UNITS - Online Task Manager, Console for a home automation system , Auction Site




3 PARTICIPANTS - 9 Participant

EMPIRICAL STUDY – Experimental Procedures




Project are allocated to Participant by dividing into three categories . PG, FG and NG

1 45 Minutes tutorial guideline to FG participants on design and analysis

artefacts.

2 15 Minutes tutorial guideline to PG participants on analysis

artefact only.

3 No tutorial guideline to NG participants

EMPIRICAL STUDY - Data

1 Development Time Data 2 Perceived Complexity Data




The Purpose this research was Reduce Development Time, Reduce Perceived Complexity, Improve Design Qualities.

3 Design Quality Data

EMPIRICAL STUDY - Analysis

1 Development Time





2 Perceived Complexity





3 Design Quality




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

Documents

software engineering

iso usability

usability needs

usability design guidelines

software development

software architects

software developers

software requirementsbass