Despite the growing importance for practice, user experience is often a blurry and doubtful concept both for newcomers and for the industry. Such ambiguity stems from a emergent community of practitioners with diverse backgrounds, to whom user experience encompasses countless interpretations. This paper reports on an online survey deployed to grasp the state of user experience evaluation practice. We learned that evaluations are mainly conducted by HCIs, software engineers or designers and are perceived to strongly impact the user interface, as well as the business logic level. Additionally, informal, low cost methods are widely used and, although most methods rely on paper prototypes, a single artifact is used per evaluation and working prototypes are favored. Moreover, evaluations happen at multiple project phases and various methods are used. Finally, results shows that evaluations are constrained by evaluators' background or occupation. This compels the community to pursue an end-to-end methodology to prevent it.
OATAO is an open access repository that collects the work of Toulouse researchers and makes it freely available over the web where possible. This is an author-deposited version published in : http://oatao.univ-toulouse.fr/ Eprints ID : 18843The contribution was presented at HCSE 2016:http://www.hcse-hessd.org/ Abstract. Business Process Improvement (BPI) is a key issue in the development of the enterprise competitiveness. However, achieving a level of software development performance that matches enterprise BPI needs in terms of producing noticeable results in small amounts of time requires the existence of a comprehensive and also agile Software Development Process (SDP). Quite often, SDPs do not deliver software architectures that can be directly used for in-house development, as specifications are either too close to the user interface design or too close to business rules and application domain modeling, and produce architectures that do not cope with software development concerns. In this paper we present the Goals Approach, which structures business processes to extract requirements, and methodologically details them in order to specify the user interface, the business logic and the database structures for the architecture of a BPI. Our approach aims in-house software development in small and medium enterprises.
OATAO is an open access repository that collects the work of Toulouse researchers and makes it freely available over the web where possible. Abstract. Continuous Business Process Improvement (BPI) is necessary in order to maintain and develop the enterprise competitiveness. However, achieving a level of software development performance that matches enterprise needs in terms of producing noticeable results within small amounts of time is a persnickety task, mainly because most available methods do not deliver full software architectures that can be directly used for in-house software development without iterations between implementation and design, as produced specifications are too close to the user interface, or too close to business regulations and domain modeling. Our approach applies a method that structures business processes, business rules and domain concepts, and uses this information in order to identify user tasks (use cases) and interaction spaces, and by means of their detail, methodically specify the software architecture for a particular BPI, bridging business and software using cross-consistent concepts. We present a theoretical example, and the validation of our method.
OATAO is an open access repository that collects the work of Toulouse researchers and makes it freely available over the web where possible. Abstract. The development of Web-based Information Systems is crucial in the quest to maintain and develop the enterprise competiveness. However, capturing requirements from Business Processes (BP) is still an issue, as existing methods mostly focus, or on human aspects and the user interface, or on business concerns as rules and workflow coordination, and therefore do not specify all the Software Architectural components which are relevant for software development. We present the Goals Approach, which analyzes BPs and User Tasks and details them in the process of methodically designing and structuring the User Interface, the Business Logic and the Database of the Information System given a Model-View-Controller (MVC) architectural pattern. In this paper we focus on how to obtain the Goals business model of requirements based on the DEMO method. The approach can be used for in-house software development, and the method is straightforward fitting Small and Medium Enterprises agility needs.
Bringing human-centric models into the software development lifecycle provides unique opportunities to enhance development practice. Modeling the interactive aspects of a software system ensures a better understanding of user requirements leading to improved user interface and general usage and acceptance of the system. It also provides a unique opportunity to enhance conventional software development practices, such as effort estimation, which is known to have major deviations. In this paper we illustrate this mutual benefit presenting a statistical analysis of the effort estimation for seven real world software development projects. We contrast a conventional use-case points (UCP) method with iUCP an HCI enhanced method Here we propose an enhancement of the iUCP original effort estimation formula. This results in an improved mean deviation of iUCP over UCP supporting the claim that reflecting HCI concerns into internal SE artifacts generates more accurate estimations of software development effort. Our results provide additional evidence of the benefits of using human-centric models to enhance the software development practice, in particular for long lasting challenges like generating accurate project estimates early in the development lifecycle.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.