requirements engineering for mobile devices

Requirements Engineering for Mobile Devices

Tamim RyhanMoshfiqur Rahman

Agenda

Motivation Challenges mConcAppt: Overview mConcAppt: Requirements Elicitation Conclusion Questions/Answers


Motivation

Mobile business apps− Integrated in existing IT infrastructure− Running on mobile devices− Task oriented− Limited scope of functionality


Challenges

High usability and user experience

− Expectation of immediate productive use

− Familiarity with legacy system

Clear and limited scope of functionality

− Identification of clearly defined tasks

Enhancement of existing business processes

− Improvement of existing business processes

Usage context and environment

− Consideration of the application usage environment

Performing early usability testing

− Performing test in the actual usage context


Challenges (contd.)

Consistent look and feel

− Familiarity with legacy system

Limited user attention

− Defining user's range of usage

Short time to market

− Quick delivery of product for business opportunities

Integration into existing IT infrastructure

− Confirmation of back-end support

Support of various device platforms

− Compatibility with different mobile device platforms


mConcAppt: Overview

Combination of requirements engineering and UI & interaction design activities

Based on TORE

Acts as a mediator between all software engineering activities


mConcAppt: Overview


mConcAppt: Requirements Elicitation (contd.)

Comprises all requirements engineering activities regarding a specific app

Conduct a requirements elicitation workshop and document the elicited results

Requirements workshop Workshop preparation

Requirements workshop

Requirements documentation



Workshop preparation Workshop agenda

Selection and invitation of participants

Initial elicitation of information

Ensure supply of needed materials for the workshop



Requirements workshop Conducted following the agenda

Keep the discussion on track without interrupting the free flow of ideas and comments

Ensure equal participation




Figure: Steps in a workshop


Elicitation of Stakeholders and user roles Identify involved stakeholders

Identify stakeholders main goals clearly




Figure: Stakeholder’s role description template


Creating user persona


Figure: User persona template


Elicitation of as-is situation and related problems Get a common understanding of the actual situation

Derive technical constraints and requirements




Figure: As-is situation description template


Product Philosophy Creates the product philosophy based on the company philosophy

and user experience factors

Should reflect the special user experience factors that have to be addressed by the app




Figure: Product philosophy description template


Elicitation of to-be situation Elicited based on the as-is description

Should always be as complete as possible

Steps of the to-be situation should be identified as: Human activities: steps that only performed by human Human-system activities: performed by human with system support System activities: automatically performed by the system System-system activities: performed by the system with the help of external

system




Figure: To-be situation collection format


Collection and discussion of relevant system functions Identifies the main system functions based on the previously

elicited to-be scenarios

Represent the core functionality




Figure: System function description format


Wrap-up and next steps Next steps are written down and contact persons are named in

case of any future questions

Moderator also takes notes of any open issues left in the workshop



Workshop Documentation Processing of information gathered during the workshop

Part of the interaction concept description

Basis for all upcoming activities

Lightweight documentation focusing on the information that is needed in further steps




Figure: Workshop documentation template

Thanks for your attention!Questions?


requirements engineering for mobile devices

Self Improvement

requirements elicitationcontd

requirements workshopconducted

user persona figure

elicitation of stakeholders

user rolesidentify

motivationmobile business

legacy systemclear

infrastructure confirmation