scholarly journals DYNAMIC DETECTION OF DESIGN INCONSISTENCY DURING SOFTWARE DEVELOPMENT USING DAID APPROACH

2014 ◽  
pp. 169-172
Author(s):  
SUMA. V ◽  
ARFA BAIG ◽  
DIVYASHREE B J ◽  
N B SONALI ◽  
S AKSHAYA
Keyword(s):  
Software Development ◽  
Development Process ◽  
High Quality ◽  
Dynamic Design ◽  
Static Mode ◽  
Software Products ◽  
The Core ◽  
Software Models ◽  
Inconsistency Detection ◽  
Validation Testing

Evolution of software has lead to the fast growth of technology whose impact can be witnessed in all the domains of scientific and engineering applications. Hence engineering high quality software is one of the core challenges of all IT industries. The software models which are being used for the development of the software products may lead to inconsistencies. Nevertheless, theexistence of several methodologies during the development process in order to overcome inconsistencies operates at static mode leading towards expensive nature of rework on those inconsistencies. Therefore, this paper presents a dynamic model which resolves the aforementioned issue by capturing inconsistencies dynamically in an automated mode using Dynamic automated inconsistency detection (DAID) model. The implementation results of DAID capture the design inconsistencies dynamically at the time of their injection points in lieu of inconsistency detection during validation testing. This approach of dynamic design inconsistency detection reduces cost, time and its associated overheads. Further implementation of DAID in an automated mode increases productivity, quality and sustainability in IT industries.

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 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.

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.

Boosting the Competitiveness of Organizations With the Use of Software Engineering

2021 ◽  
pp. 198-216
Author(s):  
Mirna Muñoz
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Software Quality ◽  
Development Process ◽  
Research Work ◽  
Software Development Process ◽  
The Core ◽  
Development Organizations ◽  
Technological Base ◽  
The One

Software has become the core of organizations in different domains because the capacity of their products, systems, and services have an increasing dependence on software. This fact highlights the research challenges to be covered by computer science, especially in the software engineering (SE) area. On the one way, SE is in charge of covering all the aspects related to the software development process from the early stages of software development until its maintenance and therefore is closely related to the software quality. On the other hand, SE is in charge of providing engineers able to provide technological-base solutions to solve industrial problems. This chapter provides a research work path focused on helping software development organizations to change to a continuous software improvement culture impacting both their software development process highlighting the human factor training needs. Results show that the implementation of best practices could be easily implemented if adequate support is provided.

An Effective Approach for Context Driven Testing in Practice — A Case Study

2020 ◽  
Vol 30 (09) ◽  
pp. 1245-1262
Author(s):  
Quyet-Thang Huynh ◽  
Le-Trinh Pham ◽  
Nhu-Hang Ha ◽  
Duc-Man Nguyen
Keyword(s):  
Software Development ◽  
Development Process ◽  
Continuous Process ◽  
Minimum Cost ◽  
Agile Development ◽  
Software Products ◽  
Engineering Company ◽  
Quality Product ◽  
Software Engineers ◽  
Agile Software

Software testing is a continuous process during the software development stages to ensure quality software products. Researchers, experts and software engineers keep going on studying new techniques, methods and approaches of testing to accommodate changes in software development because of the flexible requirement along with the changing of technology. So, developers and testers need to have effective methods, tools and approaches to create a high-quality product at an efficient cost. This paper provides an effective approach for context-driven testing (CDT) in an agile software development process. CDT is a testing approach that supports the tester to choose their testing techniques and test objectives based on specific contexts. The aim of this paper is to propose an effective approach for implementing the CDT in practice, called CDTiP. Through an analysis of two case studies using an agile development process with different contexts, we validate the effectiveness of the approach in terms of test coverage, detect errors, test effort. The empirical results show that CDTiP is suitable for the agile development process that can help the tester to detect defects faster at minimum cost. The results of this method have been applied at Enclave, an ODC Software Engineering company, on real projects.

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.  

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.

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