1) The document discusses mConcAppt, a method for requirements engineering for mobile applications that combines requirements engineering activities with UI and interaction design. 2) mConcAppt includes conducting a requirements elicitation workshop to document stakeholders, user personas, current processes, desired future processes, system functions, and other essential requirements. 3) The workshop documentation forms the basis for further development activities. The method aims to address challenges of mobile applications like usability, limited functionality, and integration with existing systems.

1. Requirements Engineering for
Mobile Devices
Tamim Ryhan
Moshfiqur Rahman

2. Agenda

Motivation

Challenges

mConcAppt: Overview

mConcAppt: Requirements Elicitation

Conclusion

Questions/Answers
Requirements Engineering for Mobile Devices

3. Motivation

Mobile business apps
− Integrated in existing IT infrastructure
− Running on mobile devices
− Task oriented
− Limited scope of functionality
Requirements Engineering for Mobile Devices

4. 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
Requirements Engineering for Mobile Devices

5. 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
Requirements Engineering for Mobile Devices

6. mConcAppt: Overview

Combination of requirements engineering and UI &
interaction design activities

Based on TORE

Acts as a mediator between all software engineering
activities
Requirements Engineering for Mobile Devices

7. mConcAppt: Overview
Requirements Engineering for Mobile Devices

8. 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
Requirements Engineering for Mobile Devices

9. mConcAppt: Requirements Elicitation
(contd.)
Requirements Engineering for Mobile Devices

10. mConcAppt: Requirements Elicitation
(contd.)

Workshop preparation

Workshop agenda

Selection and invitation of participants

Initial elicitation of information

Ensure supply of needed materials for the workshop
Requirements Engineering for Mobile Devices

11. mConcAppt: Requirements Elicitation
(contd.)
Requirements Engineering for Mobile Devices

12. mConcAppt: Requirements Elicitation
(contd.)

Requirements workshop

Conducted following the agenda

Keep the discussion on track without interrupting the free flow of
ideas and comments

Ensure equal participation
Requirements Engineering for Mobile Devices

13. mConcAppt: Requirements Elicitation
(contd.)
Figure: Steps in a workshop
Requirements Engineering for Mobile Devices

14. mConcAppt: Requirements Elicitation
(contd.)

Elicitation of Stakeholders and user roles

Identify involved stakeholders

Identify stakeholders main goals clearly
Requirements Engineering for Mobile Devices

15. mConcAppt: Requirements Elicitation
(contd.)
Figure: Stakeholder’s role description template
Requirements Engineering for Mobile Devices

16. mConcAppt: Requirements Elicitation
(contd.)

Creating user persona
Figure: User persona template
Requirements Engineering for Mobile Devices

17. mConcAppt: Requirements Elicitation
(contd.)

Elicitation of as-is situation and related problems

Get a common understanding of the actual situation

Derive technical constraints and requirements
Requirements Engineering for Mobile Devices

18. mConcAppt: Requirements Elicitation
(contd.)
Figure: As-is situation description template
Requirements Engineering for Mobile Devices

19. mConcAppt: Requirements Elicitation
(contd.)

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
Requirements Engineering for Mobile Devices

20. mConcAppt: Requirements Elicitation
(contd.)
Figure: Product philosophy description template
Requirements Engineering for Mobile Devices

21. mConcAppt: Requirements Elicitation
(contd.)

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
Requirements Engineering for Mobile Devices

22. mConcAppt: Requirements Elicitation
(contd.)
Figure: To-be situation collection format
Requirements Engineering for Mobile Devices

23. mConcAppt: Requirements Elicitation
(contd.)

Collection and discussion of relevant system functions

Identifies the main system functions based on the previously
elicited to-be scenarios

Represent the core functionality
Requirements Engineering for Mobile Devices

24. mConcAppt: Requirements Elicitation
(contd.)
Figure: System function description format
Requirements Engineering for Mobile Devices

25. mConcAppt: Requirements Elicitation
(contd.)

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
Requirements Engineering for Mobile Devices

26. mConcAppt: Requirements Elicitation
(contd.)

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
Requirements Engineering for Mobile Devices

27. mConcAppt: Requirements Elicitation
(contd.)
Figure: Workshop documentation template
Requirements Engineering for Mobile Devices

28. Thanks for your attention!
Questions?
Requirements Engineering for Mobile Devices