Search

Software developers in modern, large-scale software engineering should focus on writing code and continually examine monitoring data to justify dynamic behavior in their systems. In recent years, in light of the culture of development operations (DevOps), the monitoring responsibility of the developer has emerged. However, code violations may occur due to lack of experience, short deadlines, and market competition. This study discusses monitoring challenges and suggests improvements to improve the performance and quality of the software product so that developers can take advantage of these improvements in the future. This paper discusses code smell detection techniques, detection tools, classification, and how to refactor the code. In this review, we have presented several different techniques that detect code odor in the literature. These techniques were analyzed by examining the advantages, disadvantages, limitations, and efficiency of these techniques in code odor detection. A comparison was made of some advantages and disadvantages of the techniques used in odor detection and the limitations of the challenge. Finally, a solution was proposed to improve the performance of the odor detection process of the source code and thus improve the quality of the program produced by suggesting PyCos in odor detection for code through mining techniques Data contributing to the development of the Integrated Development Environment (IDE). [ABSTRACT FROM AUTHOR]

The main purpose of this research project is to develop an online education recommendation system that helps in decision making among students in selection of specific program in computer studies. Five number of lecturers and total of twenty number of degree students from computer program in University of Tuanku Abdul Rahman (UTAR) were used as the sampling users in this research. They attended a series of evaluation trials represent as 'crowd-voter' as a part of validation and verification. There are only three university programs that have been selected; (1) Software Engineering; (2) Multimedia and (3) Business Information System as to be an option of university program recommendation. Prototype methodology has been chosen and the feedbacks from the voting result are the parameters in system testing whether this crowd-voting method is useful to support university program recommendation or not. The limitations of this development also have been discovered and discussed at the end of this paper. [ABSTRACT FROM AUTHOR]

The first step in developing a system is to define it (requirement specification). In this paper, the combination of the complexity of the incremental model with the object-oriented software engineering model led to a new way of developing software system requirements based on the system's goal. This study focused on the earliest and most critical stage of a software system's life cycle: creating the software specifications that would be utilized to ensure its success. These requirements must be carefully examined when developing a trustworthy software system. This method is used to design and define requirements for COVID-19's social distance online reservation system, and it proved its efficiency in terms of describing what had to be done and the subsequent processes for design, building, and development. COVID-19 developed and enhanced the system. Use it afterwards to demonstrate how nicely it functions. [ABSTRACT FROM AUTHOR]

Requirement engineering is at the foundation of every successful software project. There are many reasons for software project failures; however, poorly engineered requirements process contributes immensely to the reason why software projects fail. Software project failure is usually costly and risky and could also be life threatening. Projects that undermine requirements engineering suffer or are likely to suffer from failures, challenges and other attending risks. The cost of project failures and overruns when estimated is very huge. Furthermore, software project failures or overruns pose a challenge in today's competitive market environment. It affects the company's image, goodwill, and revenue drive and decreases the perceived satisfaction of customers and clients. In this paper, requirements engineering was discussed. Its role in software projects success was elaborated. The place of software requirements process in relation to software project failure was explored and examined. Also, project success and failure factors were also discussed with emphasis placed on requirements factors as they play a major role in software projects' challenges, successes and failures. The paper relied on secondary data and empirical statistics to explore and examine factors responsible for the successes, challenges and failures of software projects in large, medium and small scaled software companies. [ABSTRACT FROM AUTHOR]

Understanding and maintaining the source code of industrial-scale software product is hard and time-consuming, and it is getting more difficult when the software implements parallel/concurrent/distributed computations and behaviours. Static source code analysis tools support program comprehension through detecting dependencies and relations among small (like functions and processes) or large (modules and components) software elements. For Erlang, which is a dynamically typed language, only an approximation of the real dependencies can be calculated statically. However it is possible to improve these analyses by adding application specific information, such as the most frequently used behaviours. In this paper we introduce an extension of the process relation analysis for Erlang which extract information of generic server behaviour implementations. The Communication Graph is extended with the result of the analysis. [ABSTRACT FROM AUTHOR]

Software estimation is vital for the success of software engineering projects. However, predicting software effort is difficult due to software solutions' complexity, intangibility, and diversity and their involved expertise and underlying technology. This paper aims to enhance the accuracy of software estimation using a data mining approach that combines Random Forests Regression with Use-Case Points analysis, which is typically used in estimating effort in object-oriented software engineering projects. The experimental results of applying our proposed approach have demonstrated a significant improvement in the prediction accuracy of software effort estimation when compared to Use-Case Points estimation based on R-Squared (R2) and other metrics such as Mean Absolute Error (MAE) and the Mean Squared Error (MSE). [ABSTRACT FROM AUTHOR]

In software engineering (SE), team roles play significant impact in determining the project success. To ensure the optimal outcome of the project the team is working on, it is essential to ensure that the team members are assigned to the right role with the right characteristics. One of the prevalent team roles is Belbin team role. A successful team must have a balance of team roles. Thus, this study demonstrates steps taken to determine balance of software team formation based on Belbin team role using fuzzy technique. Fuzzy technique was chosen because it allows analyzing of imprecise data and classifying selected criteria. In this study, two roles in Belbin team role, which are Shaper (Sh) and Plant (Pl) were chosen to assign the specific role in software team. Results show that the technique is able to be used for determining the balance of team roles. Future works will focus on the validation of the proposed method by using empirical data in industrial setting. [ABSTRACT FROM AUTHOR]