Patterns of Interaction Description Including Aspects of Constraints
Download as PPTX, PDF•1 like•420 views
The document discusses the development of a pattern language aimed at designing software products with a focus on user experience, highlighting the importance of defining and categorizing interaction design patterns. A survey of academics and business professionals revealed key aspects deemed important for pattern classification, including problem, solution, and examples. It concludes with a proposal for a template to describe interaction patterns, emphasizing the need to consider interrelationships and implementation constraints.
![33
TEMPLATE
Among the most representative examples are those of
Seffah [4], Master Detail [12] and Tydwell [9], in relation
to the number and significance of the criteria considered,
however after evaluating these criteria to experts, the
proposal that comes closest is the Sefah [4], considering
that includes aspects of implementation.
Although Master Detail [12] turns out to be a complete,
to inquire among experts as the structure, justification,
the applicability proposal. While Tidwell’s [9] proposal
does not include aspects of implementation.](https://image.slidesharecdn.com/ponenciainteractionpatterns-160805032119/85/Patterns-of-Interaction-Description-Including-Aspects-of-Constraints-33-320.jpg)
![34
TEMPLATE
According to these findings it is considered using the
template describing patterns Seffah proposal [4] with
some variations. This template comes together most
aspects identified as relevant here both by the authors of
the languages of interaction as respondents, especially as
a proposal that includes implementation issues and
relationships between patterns, the latter of great
importance in creating a language of interaction patterns.](https://image.slidesharecdn.com/ponenciainteractionpatterns-160805032119/85/Patterns-of-Interaction-Description-Including-Aspects-of-Constraints-34-320.jpg)
![35
TEMPLATE
Another aspect identified as of great importance, not
included in the proposed Seffah [4] correspond to the
restrictions, which provide much information as to the
limitations of the pattern, so it was decided to include
them.](https://image.slidesharecdn.com/ponenciainteractionpatterns-160805032119/85/Patterns-of-Interaction-Description-Including-Aspects-of-Constraints-35-320.jpg)
Patterns of Interaction Description Including Aspects of Constraints
- 1. Patterns of Interaction Description Including Aspects of Constraints Puebla-México 28-04-16 1
- 2. Work Team 2 PhD. César A. Collazos Universidad del Cauca [email protected] Popayán-Colombia PhD. Josefina Guerrero G. Benemérita Universidad de Puebla [email protected] Puebla-México PhD(c) Yuliana Puerta C. Universidad del Cauca [email protected] Cartagena-Colombia PhD. Juan González Calleros Benemérita Universidad de Puebla [email protected] Puebla-México
- 3. • Development of a doctoral thesis aimed to develop a Pattern Language Interaction to design software products focused on user experience. Motivation 3
- 4. 1. Standard Defining Patterns: refers to a format to define patterns. 2. The language must grouping patterns. • For example Tidwell organizes them according to the different aspects of user interface design, including: content organization, navigation, page layout and actions. • Coram and read cater more specific aspects of the user experience. The group addressing aspects of UI and interaction style, explorable interface, symbols. 1. Description of the interrelationships between Patterns: should be described and mapped. Relationships are assigned by arrows, creating a flow of language. Motivation Elements of a Language Patterns (Seffah, 2015) 4
- 5. 1. Conceptual Review. Design Patterns Category Patterns Interaction Patterns Describing Patterns Interaction 2. Survey prepared for review of interaction characteristics of patterns. 3. Choise of Template Content 5
- 7. A pattern is a description of a problem that occurs again and again in our environment, then build the core of the solution to that problem, so that this solution can be used over a million times without do not even two times in the same way. Timeless Way of Building (Alexander, 1979) Design Patterns 7
- 8. • Ui –patterns1 design patterns UI as recurring solutions that solve common design problems are defined. Design patterns are the standard reference points for the designer of user interfaces. • In (Seffah, 2015)defined the patterns of interaction as a proven solution for professional interaction design , usability and user experience that provides best practices for designing human interaction computer to any of the phases the design, engineering , evaluation or use of interactive systems , generally characterized by the user interface Interaction Patterns 81http://ui-patterns.com/
- 9. FEATURE DESCRIPTION Name: Name by which the pattern is identified. Problem: This item is described the situation that the pattern will solve. Context: User features and characteristics of the tasks to be performed. Forces: How they influence different aspects of the problem. Solution: Clear description of the proposed solution. Consequences Describes the results of applying the pattern. Usability principles: Describes the principles or ergonomic criteria on which the employer is based. Examples: An illustrative example of a successful solution. Description of Patterns (Tidwell et al,2011) Describing Patterns Interaction 9
- 10. Description of Patterns (Van Welie et al, 2000) FEATURE DESCRIPTION Name: Pattern title, which must be representative, clear and concise concept you want to communicate. Context: A description of the situation in which the pattern can be used, what are the characteristics of the context, in terms of tasks, the user. Forces: Contextual aspects that need to be optimized. Solution: Clear description of the proposed solution. Consequences Describes the results of applying the pattern. Examples: An illustrative example of a successful solution. Describing Patterns Interaction 10
- 11. Description of Patterns (Vanderdonckt et al,2008) FEATURE DESCRIPTION Problem It described the situation that the pattern will solve. Context Characteristics of the context in which the problem occurs are described Forces Aspects that influence with great importance in the situation. Solution Description of the proposed solution. Comments Additional information that enables implementation of pattern Describing Patterns Interaction 11
- 12. Description of Patterns (Van Duyne et al,2002) FEATURE DESCRIPTION Title Pattern It refers to the name of the pattern. Background Context pattern describes the relationship of this with other patterns. Forces Described in more detail people, tasks, technology and society affect design problems. Solution: It shows how to solve the problem, provide an outline of how to solve the problem Consequence Describes the results of applying the pattern. Other Patterns Other patterns that help to complete this pattern is recommended Describing Patterns Interaction 12
- 13. Description of Patterns (Master Detail,2015) FEATURE DESCRIPTION Pattern Name: It refers to how the pattern will be appointed. Also known as: Another name for the pattern. Classification: It represents the type of pattern: Motivation or Problem: What is the sample scenario to implement this pattern? Solution: What problems are solved patterns? Constraint: What restrictions required? Forces: Advantages and strengths of using Weakness: Disadvantages or limitations to use this patterns. Justification: What is the story behind this patterns because it works? Applicability or content: When this pattern is applied? Context of use: What are the category of user, the environment and the platform that this pattern can be applied? Structure What are the class hierarchy diagrams for objects in this pattern? Competitor: What are the objects participating in this pattern? Consequences: What are the advantages and disadvantages of using this pattern? Implementation: What techniques or problems arise in the application of these patterns? Know uses: What are some examples of real systems using this pattern? Related Patterns: What other models in this collection are related to pattern this pattern? Describing Patterns Interaction
- 14. Description of Patterns (Seffah ,2015) Describing Patterns Interaction Pattern Identification Pattern Name It describes how the pattern will be called Alias: It describes what the employer receives Author: Who designed the pattern? Category: Pattern Classification Keywords: Allowing be found Related Patterns: They can be (Super ordinated, Subordinated Brothers / Neighbors, Competitors) Context of Use User: Categories of users, people, profiles, etc. Tasks: Tasks are structured hierarchically. All sub-tasks must originate from a root. Platform Capacity: Information should be organized in devices independently. Problem It gives an idea of the problem that the pattern solves. This could be represented as a question. Forces The forces described aspects of influence of the problem and the solution. This aspect can be represented in a list. Solution It gives a state of the solution to the problem including the justification of the solution. This should also provide references for further understanding. Implementation Structure This is a high level of abstraction, by visual modeling notation Strategy It includes examples, figures, and sample codes. Consequences Consequences and results of using the pattern. This can be described by a list of metrics, criteria or factors usability.
- 15. FEATURES AUTHORS Tydwell Van Welie Vanderdonckt Van Duyne Master Detail Seffah Name X X X X X Alias X X Author X Classification X X Problem X X X X Keywords X Solution X X X X X X Constraints X Forces X X X X X X Weakness X Justification X Applicability X Context X X X X X X Consequences X X X X X X Structure X X Participants X Contributors Implementation X X Example X X Usability principles X Related Patterns X X X X Relationship Characteristics Authors
- 16. 2. SURVEY PREPARED FOR REVIEW OF INTERACTION CHARACTERISTICS OF PATTERNS.
- 18. Variables Valores Error Muestral 5% Confianza 95% Muestra Definida 35 Muestra Obtenida 35 Total Académicos 25 Total Empresarial 10 18 Ficha Técnica de la Encuesta
- 19. 19 Preguntas Diseñadas Área de Desarrollo a. Academy b. Bussines Tiempo de Experiencia en el Uso de Patrones a. Inferior a un año. b. Entre 1 a 5 años c. Entre 5 y 10 años
- 20. Features Level of Importance HIGH MEDIUM LOW NOT NECESSARY NAME ALIAS AUTHOR CLASSIFICATION PROBLEM KEYWORDS SOLUTION CONSTRAINTS FORCES WEAKNESS JUSTIFICATION APPLICABILITY CONTEXT CONSEQUENCES STRUCTURE PARTICIPANTS CONTRIBUTORS IMPLEMENTATION EXAMPLE USABILITY PRINCIPLES RELATED PATTERNS Relationship Characteristics Authors 20
- 21. 21 Preguntas Diseñadas 5. ¿Considera Usted que debe agregarse otras características a las Estructuras de Patrones de Interacción? a. YES b. NO En caso de haber respondido de forma positiva, por favor indique cual o cuales características podrían ser consideradas RESPUESTA ABIERTA
- 23. 23 Work Area of Respondents(%) 71,43% 28,57% Academy Bussines 0.00 10.00 20.00 30.00 40.00 50.00 60.00 70.00 80.00 Academy Bussines (%) RESPONDENTS-WORK AREA
- 24. 24 Time Work in the Area-(%) Respondents 0% 57%29% 14% (%) RESPONDENTS-TIME WORK IN THE AREA Inferior a un año Entre 1 y 5 años Entre 5 y 10 años Mas de 10 años
- 25. 25 Other Features - (%) Respondents 57,14% 42,86% YES NO 0.00 10.00 20.00 30.00 40.00 50.00 60.00 YES NO (%) RESPONDENTS-OTHER FEATURES
- 26. Level of Importance- (%) Respondents 0.00 10.00 20.00 30.00 40.00 50.00 60.00 70.00 80.00 90.00 Level of Importance (%) High Level of Importance (%) Medium Level of Importance (%) Low Level of Importance (%) Not Necessary
- 27. 27 Level of Importance High- (%) Respondents 0.00 10.00 20.00 30.00 40.00 50.00 60.00 70.00 80.00 90.00 Name Alias Author Problem Solution Constraints Forces Weakness Justification Applicability Context Consequences Structure Participants Contributors Implementation Example Related Patterns Name Author Problem Solution Constraints Weakness Aplicability Example
- 28. 28 Level of Importance Medium- (%) Respondents Alias Forces Justification Context Structure Participants Contributors Implementation0.00 10.00 20.00 30.00 40.00 50.00 60.00 Name Alias Author Problem Solution Constraints Forces Weakness Justification Applicability Context Consequences Structure Participants Contributors Implementation Example Related Patterns Level of Importance (%) Medium
- 29. 29 Level of Importance Low- (%) Respondents 0.00 10.00 20.00 30.00 40.00 50.00 60.00 Name Alias Author Problem Solution Constraints Forces Weakness Justification Applicability Context Consequences Structure Participants Contributors Implementation Example Related Patterns Las muestras obtenidas para bajo no son significativas
- 30. 30 Analiysis of Results • Respondents are academics and the business sector with experience in interaction patterns mostly between 5 and 10 years. For some cases it was possible to survey people over 10 years of experience. • Aspects such as classification, problem, solution and examples have been chosen as very important by 100% of respondents. • In the case of other aspects, such as the pattern name, restrictions, applicability and consequences they were selected high importance by 80 % of respondents. • Other aspects such as strength, context, structure, implementation and related patterns have been chosen as very important for 60% of respondents.
- 31. 31 Analiysis of Results • The level of importance for the following characteristics was half weakness, participants and collaborators. • Alias was minor feature. • In relation to include other features in describing patterns only 15% of respondents said yes, making suggestions such as include aspects of design decisions and the context should be broader, for example device or platform, environment work (organizational unit).
- 33. 33 TEMPLATE Among the most representative examples are those of Seffah [4], Master Detail [12] and Tydwell [9], in relation to the number and significance of the criteria considered, however after evaluating these criteria to experts, the proposal that comes closest is the Sefah [4], considering that includes aspects of implementation. Although Master Detail [12] turns out to be a complete, to inquire among experts as the structure, justification, the applicability proposal. While Tidwell’s [9] proposal does not include aspects of implementation.
- 34. 34 TEMPLATE According to these findings it is considered using the template describing patterns Seffah proposal [4] with some variations. This template comes together most aspects identified as relevant here both by the authors of the languages of interaction as respondents, especially as a proposal that includes implementation issues and relationships between patterns, the latter of great importance in creating a language of interaction patterns.
- 35. 35 TEMPLATE Another aspect identified as of great importance, not included in the proposed Seffah [4] correspond to the restrictions, which provide much information as to the limitations of the pattern, so it was decided to include them.
- 36. 36
- 37. Although there is no consensus among the authors of patterns and pattern languages interaction about which elements to consider, and that each author chooses freely about these features, it is worth noting that each of them to a greater or lesser importance represents an element of judgment to define or characterize the pattern. When it comes to implementing interaction patterns it is important to consider implementing elements from the definition thereof. On the other hand, when it comes to creating interaction pattern languages it is important to consider their interrelationships as a feature in the definition or description of the patterns. 37 CONCLUSIONS
- 38. After defining the template for describing patterns of interaction, from this proposal gives way to design interaction patterns proposed for the language patterns of interaction focused on user experience, the main objective of this research, then automate the process interfaces generation from these patterns. 38 CONCLUSIONS
- 39. 39 REFERENCES • Seffah, A. (2015). Patterns of HCI Design and HCI Design of Patterns. Human- Computer Interaction Series, Bridding HCI Design and Model-Driven Software Engineering, A. Seffah, DOI 10.1007/978-3-319-15687-3_2, © Springer International Publishing Switzerland 15 ISBN 978-3-319-15686-6. • Alexander, C. (1979). A Pattern Language .Center for Enviromental Structure, Berkrley California. • Tidwell, J. (2011). Designing Interfaces (Vol. 2). O'Reilly Media. • Pribeanu, C., & Vanderdonckt, J. (2008, March). A transformational approach for pattern-based design of user interfaces. In Autonomic and Autonomous Systems, 2008. ICAS 2008. Fourth International Conference on (pp. 47-54). IEEE. • Van Duyne, Douglas, Landay, James and Hong Jason. Design of Sites: Pattern Language for Web, 2002. Pearson Education. • Thanh-Diane Nguyen, Jean Vanderdonckt, Ahmed Seffah, Generative Patterns for Cross-Platform User Interfaces Engineering: The Case of the Master Detail Pattern. 2015 Louvain School of Management. • van Welie, M., van der Veer, G., & Eliens, A. (2000). Patterns as Tools for User Interface Design .Amstemdarnd
- 40. 05/08/2016 40