WP7.1: requisiti per applicazioni multicanale

1. WP7.1: requisiti per applicazioni multicanale Davide Bolchini - HOC Politecnico di Milano / Tech Lab Università della Svizzera Italiana Milano – 18 novembre 2004 Requirements engineering methodology for multichannel and multimodal interactive applications D. Bolchini, L. Mainetti

2. Outline • Multichannel Requirements Analysis • AWARE: goal-oriented requirements analysis • IDM: dialogue-based design • … by example

3. AWARE • AWARE modelAnalysis of Web Application Requirements • Provide conceptual support to: • Requirements Elicitation * • Requirements Analysis *** • Requirements Specification *** • Requirements Validation ** • Background: • Requirements Engineering • Goal-oriented models • Scenario-based reasoning

4. AWARE • A complex interactive (online) application is conceived • by a variety of stakeholders • Who is interested in it? • for a variety of objectives • What are the desired benefits? • addressed to a variety of users • Who would be willing to use it? • enabling them to accomplish a variety of goals • What do they want to achieve?

5. AWARE • Stakeholder • Goal • Refinement process • User and Client Scenarios • Requirement • Hypermedia taxonomy

6. Stakeholders • “Stakeholder” is a common concept in requirements engineering. • Stakeholders are those who have an interest in the success of the application.

8. Site Users Internet expertise Disabilities motion expert Profile X hearing Attitude generic visual impatient Disposed To seek out novice tourist journalist curious teacher Profession student E-news reading First time < 14 56Kbs E-shopping generic Mp3 14-25 In-depth 56-256Kbs Site knowledge Preferences 25-35 > 256Kbs > 35 Age Access Speed

10. Goal analysis - 2 • Goal laddering • Refinement • Strategy definition Traceability

11. Types of scenarios • Analysts should create two types of scenarios: • User scenario • What the user would liketo do on the site • User goal drives the scenario • Client Scenario: • What a main stakeholder would likethe user to do on the site • Scenario is driven by the main stakeholder’s goal as it is projected on the user experience • Channel-scenarios, cross-channel scenarios

12. Requirements taxonomy • Requirements are different in nature • A design dimension is assigned to each requirement. • Type of Channel • Content • Structure of Content • Access Paths to Content • Navigation • Presentation • User Operation • System Operation • Interaction

13. IDM • Interactive Dialogue Model • To brainstorm (in a structured way) about how to meet the requirements • A dialogue-based design model to shape interactive applications • Tailored to master multichannel applications • The graphic representation of these structures is very readable, compact and expressed in a conceptually simple way • Easy to use for brainstorming and sketching ideas not for describing fully-developed solutions

14. IDM Conceptual Design

15. IDM Web

16. IDM GPS

17. IDM Palm

18. Conclusions • AWARE: understand and specify requirements • Stakeholder-centered • Goal-oriented • Scenario-based • IDM: shape the dialogue with the user according to the requirements • Define the overall dialogue strategies • Shape the user experience on given channels • Brainstorming-wise