Usability—context, framework, definition, design and evaluation
Human factors for informatics usability
Developing user interfaces: ensuring usability through product & process
Developing user interfaces: ensuring usability through product & process
The usability engineering lifecycle: a practitioner's handbook for user interface design
The usability engineering lifecycle: a practitioner's handbook for user interface design
SHS Orcas: the first integrated information system for long-term healthcare facility management
Case Studies of the CHI2002|AIGA Experience Design FORUM
Personas in action: ethnography in an interaction design team
Proceedings of the second Nordic conference on Human-computer interaction
Usability Basics for Software Developers
IEEE Software
About Face 2.0: The Essentials of Interaction Design
About Face 2.0: The Essentials of Interaction Design
Proceedings of the 2003 conference on Designing for user experiences
The obstacles and myths of usability and software engineering
Communications of the ACM - The Blogosphere
The Persona Lifecycle: Keeping People in Mind Throughout Product Design
The Persona Lifecycle: Keeping People in Mind Throughout Product Design
CLIHC '05 Proceedings of the 2005 Latin American conference on Human-computer interaction
Getting the most out of personas for product usability enhancements
UI-HCII'07 Proceedings of the 2nd international conference on Usability and internationalization
The Essential Persona Lifecycle: Your Guide to Building and Using Personas
The Essential Persona Lifecycle: Your Guide to Building and Using Personas
Hi-index | 0.00 |
Context: To develop usable software we need to understand the users that will interact with the system. Personas is a HCI technique that gathers information about users in order to comprehend their characteristics. This information is used to define fictitious persons on which development should focus. Personas provides an understanding of the user, often overlooked in SE developments. Objective: The goal of our research is to modify Personas to readily build the technique into the requirements stage of regular SE developments. Method: We tried to apply Cooper's version of the Personas technique and we found shortcomings in both the definition of the procedure to be enacted and the formalization of the product resulting from the execution of each step of the Personas technique. For each of these limitations (up to a total of 11), we devised an improvement to be built into Personas. We have incorporated these improvements into a SE version of Personas. The improved Personas avoid the weaknesses encountered by an average software developer unfamiliar with HCI techniques applying the original Personas. Results: We aim to improve requirements elicitation through the use of Personas. We have systematized and formalized Personas in the SE tradition in order to build this new version of the technique into the requirements stage. We have applied our proposal in an application example. Conclusion: The integration of Personas into the SE requirements stage might improves the understanding of what the software product should do and how it should behave. We have modified the HCI Personas technique to comply with the levels of systematization required by SE. We have enriched the SE requirements process by incorporating Personas activities into requirements activities. Requirements elicitation and requirements analysis are the RE activities most affected by incorporating Personas.