scholarly journals Are UX Evaluation Methods Providing the Same Big Picture?

Sensors ◽  
2021 ◽  
Vol 21 (10) ◽  
pp. 3480
Author(s):  
Walter Takashi Nakamura ◽  
Iftekhar Ahmed ◽  
David Redmiles ◽  
Edson Oliveira ◽  
David Fernandes ◽  
...  
Keyword(s):  
Software Development ◽  
Decision Process ◽  
Development Process ◽  
Evaluation Methods ◽  
Sentence Completion ◽  
Software Development Process ◽  
Software Application ◽  
Software Products ◽  
Big Picture ◽  
The Impact

The success of a software application is related to users’ willingness to keep using it. In this sense, evaluating User eXperience (UX) became an important part of the software development process. Researchers have been carrying out studies by employing various methods to evaluate the UX of software products. Some studies reported varied and even contradictory results when applying different UX evaluation methods, making it difficult for practitioners to identify which results to rely upon. However, these works did not evaluate the developers’ perspectives and their impacts on the decision process. Moreover, such studies focused on one-shot evaluations, which cannot assess whether the methods provide the same big picture of the experience (i.e., deteriorating, improving, or stable). This paper presents a longitudinal study in which 68 students evaluated the UX of an online judge system by employing AttrakDiff, UEQ, and Sentence Completion methods at three moments along a semester. This study reveals contrasting results between the methods, which affected developers’ decisions and interpretations. With this work, we intend to draw the HCI community’s attention to the contrast between different UX evaluation methods and the impact of their outcomes in the software development process.

scholarly journals A Formal Protocol to Conduct Usability Heuristic Evaluations in the Context of the Software Development Process

2018 ◽  
Vol 7 (2.28) ◽  
pp. 10 ◽  
Author(s):  
Freddy Paz ◽  
Freddy A. Paz ◽  
José Antonio Pow-Sang ◽  
César Collazos
Keyword(s):  
Software Development ◽  
Development Process ◽  
Evaluation Method ◽  
Evaluation Process ◽  
Usability Evaluation ◽  
Comprehensive Analysis ◽  
Heuristic Evaluation ◽  
Software Development Process ◽  
Software Products ◽  
Software Product

Heuristic evaluation is one of the most used techniques to evaluate the level of usability of a software product. In this research, we performed a comprehensive analysis of the recent studies which report the use of this method in the context of a software development process. The purpose was to identify the specific way in which each author performs this usability evaluation method, in order to propose a formal protocol. After an indeed examination of these studies, we have determined there are several differences in the way this technique is conducted according to the literature. There is no agreement about the number of inspectors that should participate, the usability principles that should be used, the profile of the specialists who must be part of the assessment team, or the evaluation process that should be followed. This work highlights the available settings and a detailed procedure to perform a heuristic evaluation in the domain of software products.  

Towards Measuring the Change Impact in ATL Model Transformations

2016 ◽  
Vol 26 (02) ◽  
pp. 153-181 ◽  
Author(s):  
Andreza Vieira ◽  
Franklin Ramalho
Keyword(s):  
Software Development ◽  
Static Analysis ◽  
Development Time ◽  
Development Process ◽  
Model Transformations ◽  
Software Development Process ◽  
Model Driven ◽  
Change Impact ◽  
The Impact

The Model-Driven Development (MDD) approach shifts the focus on code to models in the software development process. In MDD, model transformations are elements that play an important role. MDD-based projects evolve along their lifecycle in a way that changes in their transformations are frequent. Before applying changes it is important to measure their impacts within the transformation. However, currently no technique helps practitioners in this direction. We propose an approach to measure the change impact in ATL model transformations. Based on static analysis, it detects the elements impacted by a change and calculates the change impact value through three metrics we defined. By using our approach, practitioners can (i) save effort and development time since the elements impacted with the change are automatically detected and (ii) better schedule and prioritize changes according to the impact value. To empirically evaluate our approach we conducted a case study.

scholarly journals Measuring the Quality Of the Development Process Academic System with E-GQM Method

2021 ◽  
Vol 5 (1) ◽  
Author(s):  
Sarwosri Sarwosri ◽  
Umi Laili Yuhana ◽  
Siti Rochimah ◽  
Rizky Januar Akbar ◽  
Maidina Choirun Nisa
Keyword(s):  
Software Development ◽  
Development Process ◽  
Software Process ◽  
Development Project ◽  
Average Score ◽  
Software Development Process ◽  
Software Development Project ◽  
Software Products ◽  
Academic System

In a software development project, aspects of software quality are very important. All stakeholders expect high quality of software. To ensure the quality of software products, it is also necessary to ensure that the process that is carried out have a quality. Research that is mostly done is in terms of assessing the quality of software products. But the software process is also very important to be assessed from their quality too. In every software development process, the developer needs guidance in carrying out every aspect of it. In each of these aspects, it must be determined what goals are to be achieved and how to measure whether those goals have been achieved or not. One method that can be used for this is the Extended Goal Question Metric method. In this method, for each development process in software, will be determined what aspects must be achieved, from each aspect there are defined a number of goals to measure these aspects. For each goal, one or more goal will be determined one or more questions that are relevant to that. For each Question an appropriate metric will be determined. The next step is mapping between G to Q and Q to M. The measurement is done by calculating the goal value obtained from the metric calculation. From this metric, the value of each Goal will be obtained, whether it was achieved or not. Tests were carried out on the software process for the development of academic system features at DPTSI ITS. The value of each goal has exceeded 0.51 (for a scale of 0-1) so that it achieved the quality of the Software development process. The total average score was 0.889. 

scholarly journals Merancang Perangkat Lunak Sistem Penjaminan Mutu Internal (SPMI) Perguruan Tinggi yang Memiliki Daya Adaptasi Terhadap Perubahan Kebutuhan Pengguna secara Cepat dan Sering

2020 ◽  
Vol 5 (3) ◽  
pp. 121
Author(s):  
Acep Taryana ◽  
Ari Fadli ◽  
Siti Rahmah Nurshiami
Keyword(s):  
Software Development ◽  
Development Process ◽  
Method Development ◽  
User Requirements ◽  
Software Development Process ◽  
Application Development ◽  
Software Products ◽  
Rapid Application Development ◽  
Large Step ◽  
The Right

<p><em>Abstrak</em> – <strong>Salah satu permasalahan mendasar proses pengembangan perangkat lunak adalah kebutuhan yang tidak tertangkap lengkap saat awal pengembangan, atau abstraksi kebutuhan pengguna yang kurang terpetakan secara sistematis, runut oleh pengembang. Ketidaksempurnaan pengungkapan kebutuhan pengguna tersebut dapat mengakibatkan produk perangkat lunak yang kurang lengkap bahkan bisa tidak sesuai dengan kebutuhan pengguna. Ketidaksesuaian baru dapat diamati oleh pengguna setelah pengembang menyelesaikan setiap rilis produk. Pada paper ini akan ditunjukkan bagaimana sebuah perangkat lunak SPMI dirancang, diterima oleh pengguna, diberikan masukan oleh pengguna atas masukan perbaikan pada kurun waktu tertentu. Metode yang digunakan dalam proses pengembangan perangkat lunak adalah metode DevOps yang memiliki kemampuan untuk mensinkronkan kebutuhan pengguna dengan pengembangan aplikasi yang berkelanjutan, cepat selama pengembangan dan pengoperasian berlangsung. Metode DevOps tidak hanya mengelola bagian pengembangan tetapi juga mengelola bagian pengoperasian. Hasil perancangan menunjukkan bahwa DevOps menjadi pendekatan tepat agar perangkat lunak pengembangan SPMI dikembangkan dari kecil menjadi besar, <em>step by step</em> tetapi tanpa kehilangan penelusuran antara rilis produk. Dan yang lebih mendasar, DevOps mampu memperkecil gap antara pengembang dengan pengguna aplikasi SPMI-PT. Melalui metode DevOps, pengembangan dan pengoperasian memiliki keterhubungan sebagai timbal balik antara pengembangan dengan pengoperasian maupun sebaliknya.</strong></p><p><em>Abstract</em> – <strong>One of the fundamental problems of the software development process is the requirement that is not completely captured at the beginning of development, or the abstraction of user requirements that are less systematically mapped out, by the developer. Imperfections in disclosing the requirements of these users can result in incomplete software products that may not even match the user's needs. New nonconformities can be observed by users after the Developer completes each product release. In this paper, we will show how an SPMI software is designed, accepted by the user, given input by the user for input improvement in a certain period time. The method used in the software development process is the DevOps method which can synchronize user requirements with rapid, rapid application development during development and operation. The DevOps method not only manages the development part but also manages the operation part. The design results show that DevOps is the right approach so that SPMI development software is developed from small to large, step by step but without losing traces between product releases. And more fundamentally, DevOps can reduce the gap between developers and SPMI-PT application users. Through the DevOps method, development and operation have a relationship as a trade-off between development and operations and vice versa.</strong></p><strong><em>Keywords</em></strong> – <em>Software engineering, Devops, Continuous improvement</em>

Trust Elements in Open Source

2010 ◽  
pp. 334-342
Author(s):  
Barbara Russo ◽  
Marco Scotto ◽  
Alberto Sillitti ◽  
Giancarlo Succi
Keyword(s):  
Software Development ◽  
Development Process ◽  
Automatic Measurement ◽  
Automatic Process ◽  
Software Development Process ◽  
Software Products ◽  
Development Tools ◽  
On Line ◽  
Measurement Approach

The quality of a software development process is based on a large spectrum of various elements that must be identified and assessed. The majority of elements can be measured quantitatively and possibly using an automatic process. Some elements, however, are rather subjective and depend strongly on different opinions of people using or evaluating the software development process. An automatic measurement approach is difficult to achieve (for example by on-line questionnaires or surveys inserted inside software products or software development tools). The foundation for all assessments is a set of elements that will be at a certain point of development or use measured and evaluated.

Component-based software development for integrated construction management software applications

2001 ◽  
Vol 15 (2) ◽  
pp. 173-187 ◽  
Author(s):  
FENIOSKY PEÑA-MORA ◽  
SANJEEV VADHAVKAR ◽  
SIVA KUMAR DIRISALA
Keyword(s):  
Software Development ◽  
Construction Management ◽  
Design Patterns ◽  
Development Process ◽  
Software Components ◽  
Design Rationale ◽  
Software Development Process ◽  
Software Application ◽  
Software Applications ◽  
Specific Implementation

This paper presents a framework and a prototype for designing Integrated Construction Management (ICM) software applications using reusable components. The framework supports the collaborative development of ICM software applications by a group of ICM application developers from a library of software components. The framework focuses on the use of an explicit software development process to capture and disseminate specialized knowledge that augments the description of the ICM software application components in a library. The importance of preserving and using this knowledge has become apparent with the recent trend of combining the software development process with the software application code. There are three main components in the framework: design patterns, design rationale model, and intelligent search algorithms. Design patterns have been chosen to represent, record, and reuse the recurring design structures and associated design experience in object-oriented software development. The Design Recommendation and Intent Model (DRIM) was extended in the current research effort to capture the specific implementation of reusable software components. DRIM provides a method by which design rationale from multiple ICM application designers can be partially generated, stored, and later retrieved by a computer system. To address the issues of retrieval, the paper presents a unique representation of a software component, and a search mechanism based on Reggia's setcover algorithm to retrieve a set of components that can be combined to get the required functionality is presented. This paper also details an initial, proof-of-concept prototype based on the framework. By supporting nonobtrusive capture as well as effective access of vital design rationale information regarding the ICM application development process, the framework described in this paper is expected to provide a strong information base for designing ICM software.

scholarly journals The Effect of Team Dynamics on Software Development Process Improvement

2012 ◽  
Vol 3 (3) ◽  
pp. 13-26 ◽  
Author(s):  
Rory O’Connor ◽  
Shuib Basri
Keyword(s):  
Software Development ◽  
Process Improvement ◽  
Development Process ◽  
Software Process ◽  
Software Process Improvement ◽  
Working Environment ◽  
Team Dynamics ◽  
Software Development Process ◽  
Software Development Teams ◽  
The Impact

This article identifies the effect of team dynamics in the context of software development teams and its impact on software process improvement (SPI) activities in very small companies, in order to understand the relationship between these two variables. Most software development work is done by teams of software engineers working together in a collaborative manner to execute a software development process. Although there is much literature examining software process and how to improve it, less attention has been paid to the issues of team-working and specifically the impact of team dynamics on the software development process. Team dynamics is the term used to define how people work and interact together in teams. Teamwork is more effective with the existence of positive team dynamic, as it encourages a better working environment with satisfied, fulfilled employees who will in turn be more productive. This paper presents the results of a research study of team dynamics in very small software development companies and its impact on the software development process and software process improvement activities.

scholarly journals Reuse Alternatives based on the Sources of Software Assets

2021 ◽  
Vol 10 (1) ◽  
Author(s):  
Anas AL-Badareen
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Software Reuse ◽  
Development Process ◽  
Software Systems ◽  
Software Development Process ◽  
Software Products ◽  
Engineering Discipline

    Abstract— Since the idea of software reuse appeared in 1968, software reuse has become a software engineering discipline. Software reuse is one of the main techniques used to enhance the productivity of software development, which it helps reducing the time, effort, and cost of developing software systems, and enhances the quality of software products. However, software reuse requires understanding, modifying, adapting and testing processes in order to be performed correctly and efficiently. This study aims to analyze and discuss the process of software reuse, identify its elements, sources and usages. The alternatives of acquiring and using software assets either normal or reusable assets are discussed. As a result of this study, four main methods are proposed in order to use the concept of reuse in the software development process. These methods are proposed based on the source of software assets regardless the types of software assets and their usages.

Sign in / Sign up

Export Citation Format

Share Document