This document outlines a process for including usability requirements in software development. It asks a series of yes/no questions to determine whether use cases, system responsibilities, and design components will be modeled or identified to account for usability. Depending on the answers, the process will result in either a standard or usability-enhanced use case model, identification of system responsibilities considering usability, or an object-oriented software design that applies usability best practices.
1 of 2
Download to read offline
More Related Content
Presentation1
1. Functional Usability
requirements elicitation
Will model UCs? Usability Use Case
Modeling
Will identify System
Responsibilities
End
No
Identification of System
Responsibilities
Yes
Requirements with
Usability
Use case model
with Usability
Applicable System
Responsibilities
for Usability
End
Will apply Design
Process for Usability?
2. Identification of
high-level design
component
responsibilities for
Usability
Identification of
low-level design
component
responsibilities for
Usability
Identification of
low-level design
component
responsibilities for
Usability
Applicable high-
level design
component
responsibilities
for Usability
Applicable low-
level design
component
responsibilities
for Usability
Object Oriented
Software design
with usability
Will apply OO
Software Design?
Will use MVC to
Design?
YesNo
No
Yes