Event Management Software Evolution Using FOP and AOP Integration Approach in Eclipse-Based Open Source Environment

Author(s):  
Amita Sharma ◽  
S. S. Sarangdevot
2021 ◽  
Vol 11 (12) ◽  
pp. 5690
Author(s):  
Mamdouh Alenezi

The evolution of software is necessary for the success of software systems. Studying the evolution of software and understanding it is a vocal topic of study in software engineering. One of the primary concepts of software evolution is that the internal quality of a software system declines when it evolves. In this paper, the method of evolution of the internal quality of object-oriented open-source software systems has been examined by applying a software metric approach. More specifically, we analyze how software systems evolve over versions regarding size and the relationship between size and different internal quality metrics. The results and observations of this research include: (i) there is a significant difference between different systems concerning the LOC variable (ii) there is a significant correlation between all pairwise comparisons of internal quality metrics, and (iii) the effect of complexity and inheritance on the LOC was positive and significant, while the effect of Coupling and Cohesion was not significant.


Author(s):  
Nisha Ratti ◽  
Parminder Kaur

Software evolution is the essential characteristic of the real world software as the user requirements changes software needs to change otherwise it becomes less useful. In order to be used for longer time period, software needs to evolve. The software evolution can be a result of software maintenance. In this chapter, a study has been conducted on 10 versions of GLE (Graphics Layout Engine) and FGS (Flight Gear Simulator) evolved over the period of eight years. An effort is made to find the applicability of Lehman Laws on different releases of two softwares developed in C++ using Object Oriented metrics. The laws of continuous change, growth and complexity are found applicable according to data collected.


DEDIKASI ◽  
2020 ◽  
Vol 22 (2) ◽  
Author(s):  
Muhammad Kasim Aidid ◽  
M. Nadjib Bustan ◽  
Ruliana Ruliana

Based on the situation analysis, a Community Partnership Program (PKM) activity is proposed to train the use of reference management software for teachers in which SMA Negeri 4 Pinrang Regency is the partner. The identified problems are: (1) Lack of skills in using reference manager software, (2) Zotero as open source software is unknown, (3) The need for the ability to use reference manager software that can be applied in writing scientific papers. The material is presented through zoom meetings in plenary and in groups according to the schedule. In the plenary presentation of the material, material on basic concepts in research and writing of scientific papers was presented then continued with the provision of material on the use of Zotero in writing scientific articles. Some of the requirements to become a participant are: (1) having an interest in learning the basic concepts of reference management, (2) having never attended a similar training. (3) must attend all training activities. From the PKM activities that have been carried out as well as the team's internal survey, it can be concluded that in the implementation of this activity: (1) Participants become literate and skilled in operating the Zotero software, (2) The Zotero menu is well known to PKM participants, (3) Participants have the ability to use Zotero in writing scientific articles.


2018 ◽  
Author(s):  
Alvaro Ortiz-Troncoso

Open source projects may face a forking situation at some point during their life-cycle. The traditional view is that forks are a waste of project resources and should be avoided. However, in a wider technological and organisational context, forks can be a way to foster the creation of a software ecosystem. Either way, forking is explicitly allowed by open source licenses. Notwithstanding, methods for quantifying the evolution of forks are currently scarce. The present work attempts to answer the question whether a real-life project has forked. It does so by considering code and organisational characteristics of the project, and analysing these characteristics by applying methods ported from biological phylogenetics. After finding that the project is forked, implications for project governance are discussed.


Sign in / Sign up

Export Citation Format

Share Document