The Influence of the Application of Agile Practices in Software Quality Based on ISO/IEC 25010 Standard

Agile practices are activities or procedures that are applied during the software development process in order to improve its quality and productivity. The objective of this study is to determine the influence of agile practices on software quality. For this purpose, a model composed of 4 groups of agile practices and 8 quality characteristics according to the ISO/IEC 25010 standard has here been proposed. The results of 146 questionnaires addressed to people involved in the software development process show that the application of agile engineering and project management practices have a significant positive influence on the quality attribute functionality. On the other hand, project management practices have a low impact on the quality characteristics of compatibility, portability, security, and usability.

Software Defect Fault Intelligent Location and Identification Method Based on Data Mining

With the advancement of the times, computer technology is also constantly improving, and people’s requirements for software functions are also constantly improving, and as software functions become more and more complex, developers are technically limited and teamwork is not tacitly coordinated. And so on, so in the software development process, some errors and problems will inevitably lead to software defects. The purpose of this paper is to study the intelligent location and identification methods of software defects based on data mining. This article first studies the domestic and foreign software defect fault intelligent location technology, analyzes the shortcomings of traditional software defect detection and fault detection, then introduces data mining technology in detail, and finally conducts in-depth research on software defect prediction technology. Through in-depth research on several technologies, it reduces the accidents of software equipment and delays its service life. According to the experiments in this article, the software defect location proposed in this article uses two methods to compare. The first error set is used as a unit to measure the subsequent error set software error location cost. The first error set 1F contains 19 A manually injected error program, and the average positioning cost obtained is 3.75%.

Boosting the Competitiveness of Organizations With the Use of Software Engineering

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.

Migration from DevOps to DevSecOps - A complete migration framework, challenges and evaluation

DevOps development strategy is based on lean and agile principles and developed to ensure faster delivery. It ensures the collaboration of all stakeholders in the software development process and incorporates user’s feedback in a faster manner. This strategy is developed to guarantee customer satisfaction, increased business value, reduced time for bagging the feedback and adjusting the deliverables. They identified a requirement of prioritizing security in DevOps and started conferring about security to be embedded in DevOps. This introduced a mission-critical issue in many organizations as it requires breaking down of the barriers of operations and security team and review of many security policies in place. The challenge is to find the best way in DevOps can still perform Continuous Integration and Continuous Delivery after implanting security in a DevOps environment. This paper introduces a complete migration framework from DevOps to DevSecOps.This paper also identifies the attributes on which the migration framework can be evaluated.

End-to-end design of automated systems based on ontologies

Currently, a large number of studies are being carried out on the use of ontologies in the development of automated sys-tems. Ontological modeling improves the efficiency of the software development process. The division of labor in the development of automated systems contributes to the appearance of semantic gaps between the phases of the design process. The practice of using a wide range of reusable design artifacts is a risk factor for violation of conceptual integ-rity, consistency and completeness of the developed design solutions. The article proposes a new approach to ontologi-cal modeling of automated systems, which serves the design process for their development at all stages of design up to implementation; and a new structure of metadata of ontological specifications of automated systems, which allows tak-ing into account semantically important entities and features of the system being developed. It is shown that the use of this approach significantly reduces labor costs in the design of a complex automated system in the face of changing re-quirements at different stages of system creation. The use of ontological models in the design process helps to increase the conceptual integrity, consistency and completeness of the developed design solutions.

Working in the COVID-19 pandemic: an observational study

The restrictions of social isolation adopted to contain the spread of the COVID-19 pandemic have led many companies to adopt remote work in a mandatory and unplanned way. This sudden transition has caused profound changes in personal and professional relationships. In this article, we present the results of a qualitative observational study on the adaptations made in the activities of the software development process of two companies. These adaptations were intended to support the transition to teleworking during the pandemic. They were analyzed based on the theoretical framework of Olson and Olson for distributed collaboration. Software developers’ motivations and observed challenges are also presented. Based on these results, the article presents recommendations to facilitate the adaptation to remote work in software development teams.

Comparative Study of Different SDLC Models

The Software Development Life Cycle (SDLC) refers to a methodology with clearly defined processes for creating highquality software which are cost effective and reliable. This method of software developing process is quite systematic and structural. SDLC defines the framework that has different activities and tasks to be administered during the software development process. Software development process is quite complex, and to do it without any proper planning would be inefficient. So, we use these SDLC models to make the Software development process simple and systematic. There are various software development life cycle models that are used in the software development process, all having their own advantages and limitations. In this paper, we have included six of these SDLC models - Waterfall Model, Spiral Model, V Model, Agile Model, Iterative Model and Rapid Application Development (RAD) Model. These Software Development processes have their own Advantages and Disadvantages, and the main purpose of this paper is to explain these models and know the difference between them. Keywords: Software Development life cycle, Models, Risk Analysis, Framework, SRS.

Study on Go Programming Language

When developing software today, we still use old tools and ideas. Maybe it is time to start from scratch and try tools and languages that are more in line with how we actually want to develop software. The Go Programming Language was created at Google by a rather famous trio: Rob Pike, Ken Thompson and Robert Griesemer. Before introducing Go, the company suffered from their development process not scaling well due to slow builds, uncontrolled dependencies, hard to read code, poor documentation and so on. Go is set out to provide a solution for these issues. The purpose of this master’s thesis was to review the current state of the language. This is not only a study of the language itself but an investigation of the whole software development process using Go. The study was carried out from an embedded development perspective which includes an investigation of compilers and cross-compilation. We found that Go is exciting, fun to use and fulfills what is promised in many cases. However, we think the tools need some more time to mature.