Why Gamification Is Not the Solution for Everything

2021 ◽  
pp. 20-33
Author(s):  
Tiago Pereira da Silva
Keyword(s):  
Software Development ◽  
Health Sector ◽  
User Feedback ◽  
Design Technique ◽  
End User ◽  
High Quality ◽  
User Adaptation ◽  
Industry Standard

Gamification is a very well-known design technique in software development that applies the principles of gaming to non-gaming contexts and environments to increase the user adaptation and engagement of applications. Examples of gamified applications can be seen across all kinds of software categories from health to finance, always with the same goal: provide a better experience to the end-user. This chapter reflects upon the user feedback of gamified applications, especially on health sector, and concludes that gamification is not a solution that can be successfully applied to every context. In the end, industry standard alternatives to gamification are analyzed in order to produce high quality non-gamified applications.

scholarly journals An Adaptive Bitrate Switching Algorithm for Speech Applications in Context of WebRTC

2021 ◽  
Vol 17 (4) ◽  
pp. 1-21
Author(s):  
Mohannad Alahmadi ◽  
Peter Pocta ◽  
Hugh Melvin
Keyword(s):  
Real Time ◽  
Data Exchange ◽  
Quality Of Experience ◽  
End User ◽  
High Quality ◽  
Content Type ◽  
Switching Algorithm ◽  
Wide Range ◽  
The Impact

Web Real-Time Communication (WebRTC) combines a set of standards and technologies to enable high-quality audio, video, and auxiliary data exchange in web browsers and mobile applications. It enables peer-to-peer multimedia sessions over IP networks without the need for additional plugins. The Opus codec, which is deployed as the default audio codec for speech and music streaming in WebRTC, supports a wide range of bitrates. This range of bitrates covers narrowband, wideband, and super-wideband up to fullband bandwidths. Users of IP-based telephony always demand high-quality audio. In addition to users’ expectation, their emotional state, content type, and many other psychological factors; network quality of service; and distortions introduced at the end terminals could determine their quality of experience. To measure the quality experienced by the end user for voice transmission service, the E-model standardized in the ITU-T Rec. G.107 (a narrowband version), ITU-T Rec. G.107.1 (a wideband version), and the most recent ITU-T Rec. G.107.2 extension for the super-wideband E-model can be used. In this work, we present a quality of experience model built on the E-model to measure the impact of coding and packet loss to assess the quality perceived by the end user in WebRTC speech applications. Based on the computed Mean Opinion Score, a real-time adaptive codec parameter switching mechanism is used to switch to the most optimum codec bitrate under the present network conditions. We present the evaluation results to show the effectiveness of the proposed approach when compared with the default codec configuration in WebRTC.

scholarly journals SOME ASPECTS OF AGILE APPROACH IN PRAXIS

2015 ◽  
Vol 3 ◽  
pp. 348-355
Author(s):  
Jaroslava Kniežová
Keyword(s):  
Software Development ◽  
Development Process ◽  
Traditional Approach ◽  
High Quality ◽  
Modern Times ◽  
Effective System ◽  
Agile Approach ◽  
Traditional Process ◽  
Short Time

In modern times, competitiveness in the market depends on having a good information system. The companies developing and supplying information systems are in competition too, and having an effective system of delivery is critical for obtaining lucrative offers. Therefore, the software development companies continuously try to improve their development process to supply the product in a short time and with high quality. The agile approach potentially shortens this time and is very often used. This approach has almost replaced the traditional process. More and more companies implement agile approach in these times to be competitive in the software development market and hasten product delivering.The traditional and agile approaches differ in certain perspectives. Hence, the question arises as to whether the agile approach is the best for the software development company in every case. This article contains a comparison of these two approaches, as well as a case study relating to the agile approach in a real software development company, which had previously used the traditional approach. The article also describes situation where replacing the traditional approach with agile would improve results.

scholarly journals Dimensional Modeling Using Star Schema for Data Warehouse Creation

2017 ◽  
Vol 10 (04) ◽  
pp. 745-754
Author(s):  
Mudasir M Kirmani
Keyword(s):  
Data Warehouse ◽  
Transformation Model ◽  
Data Warehouses ◽  
Design Technique ◽  
End User ◽  
Conversion Model ◽  
Know How ◽  
Dimensional Modeling ◽  
Star Schema ◽  
Logical Design

Data Warehouse design requires a radical rebuilding of tremendous measures of information, frequently of questionable or conflicting quality, drawn from various heterogeneous sources. Data Warehouse configuration assimilates business learning and innovation know-how. The outline of theData Warehouse requires a profound comprehension of the business forms in detail. The principle point of this exploration paper is to contemplate and investigate the transformation model to change over the E-R outlines to Star Schema for developing Data Warehouses. The Dimensional modelling is a logical design technique used for data warehouses. This research paper addresses various potential differences between the two techniques and highlights the advantages of using dimensional modelling along with disadvantages as well. Dimensional Modelling is one of the popular techniques for databases that are designed keeping in mind the queries from end-user in a data warehouse. In this paper the focus has been on Star Schema, which basically comprises of Fact table and Dimension tables. Each fact table further comprises of foreign keys of various dimensions and measures and degenerate dimensions if any. We also discuss the possibilities of deployment and acceptance of Conversion Model (CM) to provide the details of fact table and dimension tables according to the local needs. It will also highlight to why dimensional modelling is preferred over E-R modelling when creating data warehouse.

scholarly journals Rational Unified Process Part-1

2002 ◽  
Vol 1 (1) ◽  
pp. 81-94
Author(s):  
Manoj Tharian
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Unified Modeling Language ◽  
Modeling Language ◽  
Engineering Process ◽  
Unified Modeling ◽  
Industry Standard ◽  
Development Teams ◽  
Software Engineering Process ◽  
Unified Process

This paper presents an overview of the Rational Unified Process. The Rational unified Process is a software engineering process, delivered through a web-enabled, searchable knowledge base. The process enhances team productivity and delivers software best practices via guidelines, templates and tool mentors for all critical software lifecycle activities. The knowledge base allows development teams to gain the full benefits of the industry-standard Unified Modeling Language(UML). The rational Unified Process is a software Engineering Process. It provides a disciplined approach to assigning tasks and responsibilities within development organization. Its goal is to ensure the production of high-quality software that meets the needs of its end-users, within a predictable schedule and budget.[11,13] The rational Unified Process is a process product , developed and maintained by Rational Software. The development team for the Rational Unified Process are working closely with customers, partners, Rational's that the process is continuously updated and improved upon to reflect recent experiences and evolving and proven best practices. The Rational Unified Process is a guide for how to effectively use the Unified modeling Language(UML). The UML is a industry-standard language that allows us to clearly communicate requirements, architectures and designs. The UML is a industry-standard language that allows us to clearly communicate requirements architectures and designs. the UML originally created by Rational Software, and is now maintained by the standards organization Object Management Group(OMG).[4] the Rational Unified Process captures many of the best practices in modern software development in a form that is suitable for a wide range of projects and organizations. Deploying these best practices 3/4 using the Rational Unified Process as your guide 3/4 offers development teams a number of key advantages. In next section, we describe the six fundamental best practices of the Rational Unified Process. The Rational Unified Process describes how to effectively deploy commercially proven approaches to software development for software development teams. These are called "best practices" not so much because you can precisely quantify their value, but rather, because they are observed to be commonly used in industry by successful organizations.

On the Maturity of Software Maintenance and Other IT Services

2011 ◽  
pp. 51-74
Author(s):  
Frank Niessink
Keyword(s):  
Service Quality ◽  
Software Development ◽  
Software Maintenance ◽  
Two Dimensions ◽  
Point Of View ◽  
Technical Quality ◽  
It Services ◽  
High Quality ◽  
Functional Quality

In this chapter, we examine the differences between software maintenance and software development from a service point of view, and the consequences thereof for the maturity of software maintenance organizations. We argue that software maintenance can be seen as providing a service, whereas software development is primarily concerned with the development of products. Differences between products and services affect the way in which customers assess their respective quality. In particular, service quality is assessed in two dimensions: the technical quality — what the result of the service is — and the functional quality — how the service is delivered. Consequently, customers will judge the quality of software maintenance differently from that of software development. This in turn means that to deliver high quality results in software maintenance, both the functional quality and the technical quality dimension are important.

Open Source Software Systems

2010 ◽  
pp. 439-459
Author(s):  
R. B. Lenin ◽  
S. Ramaswamy ◽  
Liguo Yu ◽  
R. B. Govindan
Keyword(s):  
Software Development ◽  
Software Systems ◽  
The Internet ◽  
Development Projects ◽  
Work Processes ◽  
High Quality ◽  
Software Products ◽  
Geographic Boundaries ◽  
Doing Business ◽  
Development Costs

Complex software systems and the huge amounts of data they produce are becoming an integral part of our organizations. We are also becoming increasingly dependent on high quality software products in our everyday lives. These systems ‘evolve’ as we identify and correct existing defects, provide new functionalities, or increase their nonfunctional qualities - such as security, maintainability, performance, etc. Simultaneously, more software development projects are distributed over multiple locations (often globally) and are often several millions of dollars in development costs. Consequently, as the Internet continually eliminates geographic boundaries, the concept of doing business within a single country has given way to companies focusing on competing in an international marketplace. The digitalization of work and the reorganization of work processes across many organizations have resulted in routine and/or commodity components being outsourced.

CMMI Implementation and Results

2015 ◽  
pp. 48-63 ◽  
Author(s):  
Marco Liberato ◽  
João Varajão ◽  
Paulo Martins
Keyword(s):  
Software Development ◽  
Quality Standards ◽  
Model Integration ◽  
Maturity Model ◽  
High Quality ◽  
Capability Maturity ◽  
Information Technology Services ◽  
Technology Services ◽  
Development Processes ◽  
Level 2

Companies focus on software development in order to survive in a highly competitive world. They not only need to keep up to date with the changes that are occurring in their environment, but they also need to assure the effectiveness of their processes. One way to do that is pursuing high quality standards by continuously improving the development processes. In this chapter, the authors describe the project of CMMI (Capability Maturity Model Integration) implementation in a software company specialized in information technology services for banking. The project was initiated with the aim of optimizing the software development process. Throughout the chapter, various aspects of the project are covered, such as the actions taken to implement the CMMI maturity level 2, the tools used to support the implementation, and the obtained results. These are useful and could serve as a reference basis for companies that consider the implementation of a maturity model.

XML-Based Analysis of UML Models for Critical Systems Development

2011 ◽  
pp. 257-274
Author(s):  
Jan Jurjens ◽  
Pasha Shabalin
Keyword(s):  
Unified Modeling Language ◽  
Systems Development ◽  
Industrial Applications ◽  
Tool Support ◽  
Modeling Language ◽  
Critical Systems ◽  
High Quality ◽  
Unified Modeling ◽  
Industry Standard ◽  
System Properties

High-quality development of critical systems poses serious challenges. Formal methods have been proposed to address them, but their use in industry is not as widespread as originally hoped. This chapter proposes to use the Unified Modeling Language (UML), the de-facto industry standard specification language, as a notation together with a formally based tool-support for critical systems development. The authors extend the UML notation with new constructs for describing criticality requirements and relevant system properties, and introduce their formalization in the context of the UML executable semantics. Furthermore tool-support concepts for this approach are presented, which facilitate transfer of the methodology to industrial applications.

scholarly journals Quickly Evaluating an Emerging Medical Technology Using Feedback From the Field: A Case Study of the BrainScope One and Infrascanner 2000 User Evaluation

2020 ◽  
Vol 185 (9-10) ◽  
pp. e1787-e1793 ◽  
Author(s):  
Stephen Krauss ◽  
Sarah Sanjakdar ◽  
Andrew Wilson ◽  
Brian Dacanay ◽  
Louis Jasper ◽  
...  
Keyword(s):  
Head Injuries ◽  
Field Evaluation ◽  
Medical Personnel ◽  
User Feedback ◽  
User Evaluation ◽  
Operational Environment ◽  
End User ◽  
Acquisition Process ◽  
Field Efficacy ◽  
Medical Teams

Abstract Introduction Gathering end-user feedback about candidate technologies in the operational environment prior to fielding helps to ensure that far-forward medical teams receive the most suitable technology. It is therefore a crucial step in the defense medical acquisition process. The current article reviews the methodology and provides an illustrative example of how end-user feedback was collected to evaluate the current suitability and future promise of two FDA-approved devices, the BrainScope One and Infrascanner 2000, that could potentially aid in the field evaluation of head injuries by far-forward medical teams. Materials and Method The BrainScope One and Infrascanner 2000 end-user evaluation is used as an example to illustrate how to collect end-user feedback from the field in order to rapidly assess the candidate technology. In this evaluation of whether and how to implement FDA-approved technology candidates for head injury assessment by far-forward medical teams, end-user feedback was collected from 158 medical personnel at 8 bases in Afghanistan, Iraq, and Kuwait using focus groups and interviews. Results The end users reported consistent concerns about the operational efficacy and suitability of the current versions of the devices as well as the areas where the devices showed promise for the Department of Defense (DoD). End-user feedback is shown in detail to demonstrate the depth and richness of feedback that can be gathered using this methodology. Conclusion Overall, the BrainScope One and Infrascanner 2000 end-user evaluation shows the necessity and value of gathering end-user field efficacy and suitability feedback during the medical acquisition process. Limitations and best practices for this approach are discussed.

Sign in / Sign up

Export Citation Format

Share Document