scholarly journals Software Development Technique for the Betterment of End User Satisfaction using Agile Methodology

TEM Journal ◽  
2020 ◽  
pp. 992-1002
Author(s):  
Lalband Neelu ◽  
D. Kavitha
Keyword(s):  
Customer Satisfaction ◽  
Software Development ◽  
Present State ◽  
User Satisfaction ◽  
Development Process ◽  
Software Development Process ◽  
End User ◽  
Traditional System ◽  
Agile Methodology ◽  
User Priority

Agile methodology mainly focuses on the end user priority during the each and every stage of software development process. There is a huge scope in this technique in order to alter the major/minor modifications at each stage of software development for attaining the customer satisfaction. The main aim of the present work is to compare agile methodology with the traditional system methodologies. The present state of using the agile technologies for customer satisfaction at every phase by delivering valuable software continuously is also discussed in the present work. Based on the pitfalls in the existing models, a new model is proposed here in the present study.

A Proposal to Elicit Usability Requirements within a Model-Driven Development Environment

2014 ◽  
Vol 5 (4) ◽  
pp. 1-21
Author(s):  
Yeshica Isela Ormeño ◽  
Jose Ignacio Panach ◽  
Nelly Condori-Fernández ◽  
Óscar Pastor
Keyword(s):  
Software Development ◽  
Development Process ◽  
Design Guidelines ◽  
Tree Structure ◽  
Software Development Process ◽  
End User ◽  
Model Driven Development ◽  
Model Driven ◽  
Early Stages ◽  
Usability Requirements

Nowadays there are sound Model-Driven Development (MDD) methods that deal with functional requirements, but in general, usability is not considered from the early stages of the development. Analysts that work with MDD implement usability features manually once the code has been generated. This manual implementation contradicts the MDD paradigm and it may involve much rework. This paper proposes a method to elicit usability requirements at early stages of the software development process such a way non-experts at usability can use it. The approach consists of organizing several interface design guidelines and usability guidelines in a tree structure. These guidelines are shown to the analyst through questions that she/he must ask to the end-user. Answers to these questions mark the path throughout the tree structure. At the end of the process, the paper gathers all the answers of the end-user to obtain the set of usability requirements. If it represents usability requirements according to the conceptual models that compose the framework of a MDD method, these requirements can be the input for next steps of the software development process. The approach is validated with a laboratory demonstration.

A CRITICAL ANALYSIS AND COMPARISON OF AGILE WITH TRADITIONAL SOFTWARE DEVELOPMENT PROCESS

2017 ◽  
Vol 5 (4) ◽  
pp. 88-93
Author(s):  
Priyanka Kataria ◽  
Shweta Shrivas ◽  
Ishita Shukla ◽  
A. Hemlata
Keyword(s):  
Software Development ◽  
Creative Thinking ◽  
Development Process ◽  
Software Development Process ◽  
Agile Methodology ◽  
Short Period ◽  
Marginal Prices ◽  
Agile Software ◽  
New Software Development

During the past years, new software development approaches were introduced to suit within the new trend of the software development corporations. Most Software Corporation’s today aim to provide valuable software in short period of time with marginal prices and among unstable, ever-changing environments. Agile methodology focuses on the challenges of unpredictability of the real world by relying on individuals and their creative thinking instead of method. In this paper we tend to explore about the current agile methods, strengths and weaknesses of agile strategies and numerous problems with their relevancy. We have conjointly enclosed comparison between traditional software development process and agile software development process. This paper also includes brief discussion about the benefits and problems associated with these methodologies by performing case study of two corporations.

Agile Methodology of Development and How to be Compliant

2015 ◽  
pp. 268-283
Author(s):  
Yerramalli Subramaniam ◽  
Avik Pal ◽  
Arindam Dey
Keyword(s):  
Process Control ◽  
Software Development ◽  
Development Process ◽  
Life Science ◽  
Agile Software Development ◽  
Software Development Process ◽  
Agile Methodology ◽  
Agile Methodologies ◽  
Product And Process ◽  
Agile Software

Given that Agile software development is preferred methodology for products and services in life science industry, in this chapter we will describe how to adopt Agile software development process and still be compliant. We will focus on few Agile methodologies and provide details on what design controls we can adopt in order for the product and process to be compliant. We will also focus on some of the tools that can be used to help put such design and process control in place where we can have complete transparency and traceability.

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.

Sign in / Sign up

Export Citation Format

Share Document