Extending KobrA methodology to support human-centered design Jairson Vitorino jv@cin.ufpe.br Centro de Informática - UFPE

Contents Human Computer Interface Design Human centered-design process KobrA Method overview KobrA Process and KobrA Artifacts Extending KobrA to provide HCD features Proposed experiments Conclusions Future Works

Human Computer Interface Design Most software engineering methods do not include HCD guidelines HCD provides: Good user interface design Usability and productivity

Human-centered design process

Human-centered design process phases Planning Usability planning and scoping; usability cost-benefit analysis Context of use Identify stakeholders; context of use analysis; survey of existing users; field study/user observation; diary keeping; task analysis Requirements Stakeholder analysis; user cost-benefit analysis; user requirements interview; focus groups; scenarios of use; existing system/ competitor analysis; task/function mapping; user, usability and organizational requirements Design Brainstorming; parallel design; design guidelines and standards; storyboarding; software prototyping; organizational prototyping Evaluation Participatory evaluation; assisted evaluation; heuristic or expert evaluation; controlled user testing; satisfaction questionnaires; assessing cognitive workload; critical incidents; post-experience interviews

KobrA method overview KobrA – Komponentenbasierte Anwendungsentwicklung Developed at Fraunhofer IESE Integrates Component based development (CBD) Model-driven architecture (MDA) Product-line approach

KobrA process Komponents creation applied on a recursive fashion

KobrA artifacts

Extending KobrA to provide HCD features Approaches have common features HCD mapping into KobrA method Three initial HCD phases map into KobrA context realization Fourth HCD phase map into KobrA Komponent realization Last HCD phase maps iton KobrA Komponent specification

HCD KobrA Planning Context Realization: Usability planning and scoping; usability cost-benefit analysis Context of use Context Realization: Context of use Analysis; survey of existing users; field study/user observation OR Task analysis Requirements Context Realization: Focus groups; existing system/ competitor analysis; task/function mapping; user, usability and organizational requirements Design Komponent Realization: Brainstorming; design guidelines and standards; storyboarding; software prototyping Evaluation Komponent Implementation: Participatory Evaluation; assisted evaluation; heuristic or expert evaluation; controlled user testing; satisfaction questionnaires

Proposed Experiments Goal: validate Kobra enhanced version via a controlled experiment two software development teams will be assigned to develop two identical modules of a system Case study comparison: pure KobrA approach X human-centered design enhanced KobrA version Evaluate time elapsed Field survey with users to measure system usability

Conclusions Proposal KobrA and HCD Trade-off between cost and quality Integrate software development methods with a human-centered design process KobrA and HCD approaches are complementary Trade-off between cost and quality Consider number of users and profile Better user experience keep a software product market share

Future work In software Engineering: Investigate Object Constraint Language (OCL) to map it into constraint logic programs Applications: component certification, consistency checking, component assertion, component testing.

Extending KobrA methodology to support human-centered design Jairson Vitorino jv@cin.ufpe.br Centro de Informática - UFPE