Academia.eduAcademia.edu

Outline

Title
Abstract
Introduction
Design Process
Use Case View
Ui Design Principles
Conclusion
References
All Topics
Computer Science
Human-Computer Interaction

An Innovative Approach to User Interface Engineering

Profile image of Pradip DeyPradip Dey

2019, 9th International Conference on Computer Science, Engineering and Applications (CCSEA 2019)

https://doi.org/10.5121/CSIT.2019.90926
visibility

…

description

12 pages

link

1 file

Abstract

If a computational system is to be successful, it must have an impressive user interface endowed with appealing usability features for providing exceptional user experience. User interface engineering requires an innovative approach because it is one of the most challenging areas given the diversity of knowledge, ideas, skills and creativity needed for building smart interfaces in order to succeed in today's rapidly paced and tough, competitive marketplace.Modern engineering aspects including analytical, intuitive, user experience, artistic, technical, graphical, mathematical, psychological and programming models need to be considered in the development process of a user interface. This paper critically examines some of the past practices and recommends a set of principles for designing alluring user interfaces.It also demonstrates how UML use case diagrams can be improved by naturally relating use cases to user interface elements. The improved design constructs of an enhanced UML view are presented with examples for highlighting and clarifying important user interface engineering issues.

Related papers

Tools and methodology for user interface development
John Bennett

ACM SIGGRAPH Computer Graphics, 1987

View PDFchevron_right
Automatic generation of user interface models and prototypes from domain and use case models
João Pascoal Faria

2009

The development of interactive systems typically involves the separate design and development of disparate system components by different software developers. The user interface (UI) is the part of an interactive system through which a user can access the system functionality. User interface development is a complex task that typically involves the construction of prototypes and/or models.

View PDFchevron_right
Current trends in computer-aided design of user interfaces
Jean Vanderdonckt

1996

Designing interactive applications today could no longer be thought without considering extensive use of computer systems during the whole life cycle. Any development environment is generally expected to provide a complete and consistent set of software tools that enable designers to develop new applications as fast and as best as possible. Computer-Aided Design of interactive systems should namely and significantly participate in a high quality result.

View PDFchevron_right
User Interface Modeling in UMLi
Paulo Silva

IEEE Software, 2003

Although user interfaces represent an essential part of software systems, the Unified Modeling Language )UML) seems to have been developed with little specific attention given to user interface issues. Several researchers have investigated integrating interface modeling techniques with UML. In UML, one models tasks using extended activity diagrams rather than by incorporating a completely new notation into UML. UMLi also addresses the relationships between use cases, tasks, and views, and thoroughly addresses the relationship between tasks and the data on which they act. UMLi is probably the most technically mature proposal for interface development in UML.

View PDFchevron_right
Software Engineering for User Interfaces
Don Norman

IEEE Transactions on Software Engineering, 2000

View PDFchevron_right
Engineering Interactive Systems 2008
Fabio Paternò

Lecture Notes in Computer Science, 2008

View PDFchevron_right
Improving Uml Support for User Interface Design: A Metric Assessment of Umli
Paulo Pinheiro da Silva

ICSE Workshop on SE-HCI, 2003

View PDFchevron_right
USER INTERFACE DESIGN
Kristina Wayangkau

The user interface is arguably the most important element of a computer-based system or product. If the interface is poorly designed, the user's ability to tap the computational power of an application may be severely hindered. In fact, a weak interface may cause an otherwise well-designed and solidly implemented application to fail. Three important principles guide the design of effective user interfaces: (1) place the user in control, (2) reduce the user's memory load, and (3) make the interface consistent. To achieve an interface that abides by these principles, an organized design process must be conducted. User interface design begins with the identification of user, task, and environmental requirements. Task analysis is a design activity that defines user tasks and actions using either an elaborative or object-oriented approach. Once tasks have been identified, user scenarios are created and analyzed to define a set of interface objects and actions. This provides a basis for the creation of screen layout that depicts graphical design and placement of icons, definition of descriptive screen text, specification and titling for windows, and specification of major and minor menu items. Design issues such as response time, command and action structure, error handling, and help facilities are considered as the design model is refined. A variety of implementation tools are used to build a prototype for evaluation by the user. The user interface is the window into the software. In many cases, the interface molds a user's perception of the quality of the system. If the "window" is smudged, wavy, or broken, the user may reject an otherwise powerful computer-based system.

View PDFchevron_right
The Crucial Part of a Software Product from the User’s Perspective: A Lesson for User Interface Designers
Fergus Onu

2020

The emergence of touch screen interfaces and devices have changed the orientation of application users. No computer application user looks for the text-based/command driven applications again. This research paper seeks to show that computer application users are much more concerned with the effectiveness of the user interface of the applications they use than any other part of the application. The work has taken a study of the evolution of computer application interfaces, both in convenience and complexities through materials from secondary sources and interaction with experienced practitioners in software industry. The research has shown that application users tend to focus more on how easily and effectively they can navigate through the application than any other functionality of the application. It then recommends that application developers should not pay less attention to user interface part of their software to enable their products appeal to their clients-the application user...

View PDFchevron_right
Model and software tool for automatic generation of user interface based on use case and data model
S. Vlajić

IET Software, 2012

The aim of this study is to identify the correlations between the use case model, data model and the desired user interface (UI). Since use cases describe the interaction between the users and the system, implemented through the user interface with the aim to change the state of the system, the correlation between these three components should be taken into account at the software requirements phase. In this study, the authors have introduced the meta-model of software requirements developed on the identified correlations. Based on this meta-model, it is possible to create a model of concrete software requirements, which enables not only the design and implementation of the user interface, but also the automation of this process. In order to prove the sustainability of this approach, they have developed a special software tool that performs the transformation of the model to an executable source code. They have considered different ways of user interaction with the system, and consequently, they have recommended the set of most common user interface templates. Thus the flexibility of the user interface is achieved, as the user interface of the same use case could be displayed in several different ways, while still maintaining the desired functionality.

View PDFchevron_right

References (34)

  1. Hong, J. (2010) "Why is Great Design so Hard?" Communications of the ACM, July 2010.
  2. Ousterhout, J. (2018) A Philosophy of Software Design, Yaknyam Press.
  3. Pressman, R. & Maxim, B. (2015) Software Engineering: A Practitioner's Approach, 8th edition, McGraw-Hill.
  4. Sommerville, I. (2010) Software Engineering, 9th Edition, Addison Wesley.
  5. Wang, Y. (2008) Software Engineering Foundations: A Software SciencePerspective,Auerbach Publications.
  6. Shaw, M. & Garlan, D. (1995) "Formulations and Formalisms in Software Architectures", Computer Science Today: Recent Trends and Developments, Springer-Verlag LNCS, 1000, 307-323, 1995.
  7. Braude, E. & Bernstein, M. (2011) Software Engineering: Modern Approaches, (2nd Edition), John Wiley & Sons.
  8. Leffingwell, D. & Widrig, D. (2003) Managing Software Requirements: A Use Case Approach, Addison Wesley.
  9. Rumbaugh, R. Jacobson, I. & Booch, G. (2005) The Unified Modeling Language Reference Manual. (2nd Edition), Addison Wesley.
  10. Baniassad, E., Clements, P., Araujo, J., Moreira, A., Rashid, A. & Tekinerdogan, B. (2006) "Discovering Early Aspects," IEEE Software, 2006.
  11. Krechetov, I., Tekinerdogan, B. & Garcia, A. (2006) "Towards an integrated aspect-oriented modeling approach for software architecture design," 8th Aspect-Oriented Modeling Workshop, Aspect-Oriented Software Development (AOSD) 2006.
  12. Navasa, A. Pérez, M. A., Murillo, J. M. & Hernández, J. (2002) "Aspect Oriented Software Architecture: A Structural Perspective," Proceedings of the Aspect-Oriented Software Development (AOSD), 2002.
  13. Azevedo, J. L., Cunha, B. & Almeida, L. (2007) "Hierarchical Distributed Architectures for Autonomous Mobile Robots: A case study", Proceedings of the IEEE Conference on Emerging Technologies and Factory Automation, 2007.
  14. Cerny, T., Cemus, K., Donahoo, M. & Song, E. (2013) "Aspect-driven, Data-reflective and Context- aware User Interfaces Design", ACM SIGAPP Applied Computing Review, volume 13(4), page 53- 65, 2013.
  15. Knuth, D. E. (1969) Seminumerical Algorithms: The Art of Computer Programming 2. Addison- Wesley, Reading, Mass.
  16. Gries, D. (1981) The Science of Programming. Springer, 1981.
  17. Humphrey, W. (1989) Managing the Software Process, Reading, MA. Addison-Wesley.
  18. Pfleeger, S. & Atlee, J. (2010) Software Engineering, Prentice-Hall.
  19. Agarwal, B., Tayal, S. & Gupta, M. (2010) Software Engineering and Testing, Jones and Bartlet.
  20. Tsui, F. & Karam, O. (2011) Essentials of Software Engineering, 2nd Ed., Jones and Bartlet.
  21. Bass, L. Clements, P. & Kazman, R. (2003) Software Architecture in Practice, 2nd Edition, Addison- Wesley.
  22. Miller, J. & Mujerki, J. Editors, (2003) MDA Guide, Version 1, OMG Technical Report. Document OMG/200-05-01, http://www.omg.org/mda
  23. Boehm, B. (1986) "A Spiral Model of Software Development and enhancement," ACM SIGSOFT Software Engineering Notes, ACM, 11(4):14-24, 1986.
  24. Dey, P. P, Sinha, B. R., Amin, M. & Badkoobehi, H. (2012) "Augmenting Use Case View for Modeling", World Academy of Science, Engineering and Technology, Vol.6 (12), pages 1318-21.
  25. Nielsen, J. (1993) "Iterative User Interface Design," IEEE Computer vol.26 no.11 pp 32-41, 1993.
  26. Hong, J. (2010) "Why is Great Design so Hard (Part Two)?" Communications of the ACM, August 2010.
  27. Hursch, W. L. & Lopes, C. (1995) "Separation of Concerns", Technical Report, Northeastern University.1995, Retrieved, July11, 2014 fromftp://ftp.ccs.neu.edu/pub/people/lieber/crista/techrep95/separation.pdf
  28. Shneiderman, B., Plaisant, C., Cohen, M. & Jacobs, S. (2009) Designing the User Interface: Strategies for Effective Human-Computer Interaction (5th Edition), Prentice Hall.
  29. Tidwell, J. (2011) Designing Interfaces, O'Reilly, 2nd Edition.
  30. Nielsen, N. Gr. (2019) Why User Interviews fail? Retrieved June 14, 2019 from www.nngroup.com
  31. Loranger, H. (2014) UX Without User Research is not UX, retrieved April 14, 2015 from http://www.nngroup.com/articles/ux-without-user-research/
  32. Dijkstra, E. W. (1974) "On the role of scientific thought ", Retrieved August 15, 2015, from https://www.cs.utexas.edu/users/EWD/transcriptions/EWD04xx/EWD447.html See also Effective Software Design, IASA Israel Meeting, retrieved April 12, 2019 from http://effectivesoftwaredesign.com/2012/02/05/separation-of-concerns/
  33. Agile Modelling, (2019) Introduction to the Diagrams of UML 2.X, retrieved April 14, 2019 fromhttp://www.agilemodeling.com/essays/umlDiagrams.htm
  34. Ambler, S. (2004) The Object Primer: Agile Model-Driven Development with UML 2, 3rd Edition.Cambridge University Press

Related papers

Best Practices for Improving User Interface Design
Pradip Dey

International Journal of Software Engineering & Applications

A rich and effective computational system must have a friendly user interface with appealing usability features that provides excellent user experience. In order to develop interactive systems with the best user experience, an innovative iterative approach to user interface engineering is required because it is one of the most challenging areas given the diversity of knowledge, ideas, skills and creativity needed for building smart interfaces in order to succeed in today's rapidly paced and tough, competitive marketplace. Many modeling aspects including analytical, intuitive, artistic, technical, graphical, mathematical, psychological and programming models need to be considered in the development process of an effective user interface. This research examines some of the past practices and recommends a set of guidelines for designing effective user interfaces. It also demonstrates how UML use case diagrams can be enhanced by relating user interface elements to use cases.

View PDFchevron_right
User Interface Design: A Software Engineering Perspective
Søren Lauesen

2004

Preface Part A: Best of the Classics 1.Usability 2. Prototyping and iterative design 3. Data presentation 4. Mental models and interface design Part B: Systematic Interface Design 5. Analysis, visions and domain description 6. Virtual windows design 7. Function design 8. Prototypes and defect correction 9. Reflections on user interface design Part C: Supplementary Design Issues 10. Web-based course rating 11. Designing an e-mail system 12. User documentation and support 13. More on usability testing 14. Heuristic evaluation 15. Systems development 16. Data modelling 17. Exercises 18. References Index

View PDFchevron_right
A Case Study in the Specification and Analysis of Design Alternatives for a User Interface
Bob Fields

Formal Aspects of Computing, 1999

There is considerable interest within the Human Computer Interaction (HCI) community in the use of media spaces to enhance awareness and interaction between workers in o ces or other spatially distributed environments. In addition to the technical challenges of providing reliable and e cient audio-visual communication, there are important social questions, in particular how users are able to control access to their personal environments, and how to advise other users about their level of availability. Within AMODEUS-2, an ESPRIT Basic Research Action concerned with the development, transfer and assessment of techniques for modelling human-computer interaction, a prototype media space has been analysed by various user and system oriented modelling techniques. This paper describes how formal speci cation can be used to express requirements on the interfaces needed to control access and availability in a media space. Beyond its obvious use in clarifying the subtle relationship between these concerns, the paper describes how the speci cation assists in assessing design options originating from other modelling disciplines.

View PDFchevron_right
A UML-Based Tool for Designing User Interfaces
Nuno J Nunes

2004

Existing software modeling tools are widely recognized to be hard to use and, hence, to adopt. We believe those usability problems are related to a legacy of formalism-centric tools that don’t promote the new challenges of modern software development. In this short paper, we briefly describe a new tool, under development, that tries to promote usability in modeling tools to support collaborative development of interactive software. It focuses on usable, real-world languages and a developer-centered design.

View PDFchevron_right
Towards a Rational Basis for User Interface Design Methods
Bizhan Jamshidnezhad

Proceedings of ICAD2004. Seoul, 2004

This paper contributes towards a rational foundation for User Interface Design (UID) methods. Currently UID process is primarily based on the trial-and-error approach, supported with miscellaneous testing techniques. In fact, we lack a scientific model for UID, explaining the objectives and concepts of UID and clarifying the solutions. There is an emergent need for a UID process to be not only broad enough to be applicable in different situations but also to be accurate enough to be applicable for specific cases. The current UID methods are based on an iterative process approaching the satisfactory solution in a successive chain of activities. In this paper, we strive to constitute the foundation of this challenging, rational design process. Usability may be defined as "quality of use" and it must be planned and engineered from a human perspective. Therefore, we need to systematically respect human needs, opinions, values, feelings, skills and limitations. Since the usability of a system stems from user, task, and context of use, we base our structure on the knowledge of these three elements. We construct our design model based on a pyramid of three elements: User-System-Context Needs, Concepts, and Principles. By means of AD theory, we linked these elements together to form the overall structure in which User-System-Context Needs, Concepts, and Principles play the roles of Customer Needs (CNs), Functional Requirements (FRs), and Design Parameters (DPs), respectively. The top level contains user-system-context needs, followed by Concepts (FRs) and Principles (DPs). Through AD approach, we seek the underlying concepts and principles in UID process. This model brings about both documenting design knowledge and facilitating communication. AD provide a good format for capturing background information and describing generically good solutions. Regarding these objectives, we act according to the following stages:

View PDFchevron_right

Related topics

  • Computer Science
  • Human Computer Interaction
  • Usability
  • Usability and user experience
  • User Interface Design
  • Unified Modeling Language (UML)
    • 580 California St., Suite 400
    San Francisco, CA, 94104
    © 2025 Academia. All rights reserved