10,846 research outputs found
Ontological Reengineering for Reuse
This paper presents the concept of Ontological Reengineering as the process of retrieving
and transforming a conceptual model of an existing and implemented ontology into a new, more correct and more complete conceptual model which is reimplemented. Three activities have been identified in this process: reverse engineering, restructuring and forward engineering. The aim of Reverse Engineering is to output a possible conceptual model on the basis of the code in which the ontology is implemented. The goal of Restructuring is to reorganize this initial conceptual model into a new conceptual model, which is built bearing in mind the use of the restructured ontology by the ontology/application that reuses it. Finally, the objective of Forward Engineering is output a new implementation of the ontology. The paper also discusses how the ontological reengineering process has been applied to the Standard-Units ontology [18], which is included in a Chemical-Elements [12] ontology. These two ontologies will be included in a Monatomic-Ions and Environmental-Pollutants ontologies
Issues with implementing ERP in the public administration
As governments work to transform their environments from an internal resource optimization to a process integration and external collaboration focus, integrated systems stand at the forefront of solutions that will achieve this goal. Enterprise Resource Planning (ERP) is proven to significantly increase efficiency, improve information access, reduce total cost of ownership, and help government achieve the highest levels of accountability and constituent service. Yet implementing ERP in a manner that achieves its promises is no easy task. Public sector organizations often rationalize their ERP modernization initiatives within the context of budgetary constraints and are faced with multiple ERP providers that, on the surface, are difficult to discern. In addition, adjudicating between competing ERP solutions on their functional merit is not only difficult because of the complexity of ERP systems, but it is further complicated by the intricacy of the government acquisition process. Therefore, it is particularly important that the business value be sold at the executive and political levels of government and, to be successful, that government embeds the ERP solution within its culture and processes. What's more, the level of detailed analysis required to map functional requirements to ERP solutions is an arduous task that, even if done thoroughly, hasn't always delivered a successful implementation. In this article, we will address these issues by examining the evolution and shortcomings of ERP solutions; by defining the features and functionality needed to address government transformation; and by recommending the steps to take to position for success.government, public organizations, ERP, integrated systems
Organizational and national issues of an ERP implementation in a Portuguese company
This technical research report describes a case
of an Enterprise Resource Planning (ERP) implementation in
a Portuguese SME. We focused on the identification of
organizational factors that affect the ERP implementation
project. We also analyzed the ERP implementation project
from a national cultural perspective using Geert Hofstede's
dimensions. These dimensions were used to explain some of
the attitudes and behaviours during the ERP implementation
project. The findings suggest that some of the problems in
ERP implementation projects are not of technological nature
but may be attributed to organizational factors while some
issues related to national culture.Postprint (published version
A Retrospective View of Software Maintenance and Reengineering Research.
As a summary of past, current, and future trends in software maintenance and reengineering research, we give in this editorial a retrospective look from the past 14 years to now. We provide insight on how software maintenance has evolved and on the most important research topics presented in the series of the European Conference on Software Maintenance and Reengineering
A Model-Based Approach to Impact Analysis Using Model Differencing
Impact analysis is concerned with the identification of consequences of
changes and is therefore an important activity for software evolution. In
modelbased software development, models are core artifacts, which are often
used to generate essential parts of a software system. Changes to a model can
thus substantially affect different artifacts of a software system. In this
paper, we propose a modelbased approach to impact analysis, in which explicit
impact rules can be specified in a domain specific language (DSL). These impact
rules define consequences of designated UML class diagram changes on software
artifacts and the need of dependent activities such as data evolution. The UML
class diagram changes are identified automatically using model differencing.
The advantage of using explicit impact rules is that they enable the
formalization of knowledge about a product. By explicitly defining this
knowledge, it is possible to create a checklist with hints about development
steps that are (potentially) necessary to manage the evolution. To validate the
feasibility of our approach, we provide results of a case study.Comment: 16 pages, 5 figures, In: Proceedings of the 8th International
Workshop on Software Quality and Maintainability (SQM), ECEASST Journal, vol.
65 201
Automatic Detection of Public Development Projects in Large Open Source Ecosystems: An Exploratory Study on GitHub
Hosting over 10 million of software projects, GitHub is one of the most
important data sources to study behavior of developers and software projects.
However, with the increase of the size of open source datasets, the potential
threats to mining these datasets have also grown. As the dataset grows, it
becomes gradually unrealistic for human to confirm quality of all samples. Some
studies have investigated this problem and provided solutions to avoid threats
in sample selection, but some of these solutions (e.g., finding development
projects) require human intervention. When the amount of data to be processed
increases, these semi-automatic solutions become less useful since the effort
in need for human intervention is far beyond affordable. To solve this problem,
we investigated the GHTorrent dataset and proposed a method to detect public
development projects. The results show that our method can effectively improve
the sample selection process in two ways: (1) We provide a simple model to
automatically select samples (with 0.827 precision and 0.947 recall); (2) We
also offer a complex model to help researchers carefully screen samples (with
63.2% less effort than manually confirming all samples, and can achieve 0.926
precision and 0.959 recall).Comment: Accepted by the SEKE2018 Conferenc
We Don't Need Another Hero? The Impact of "Heroes" on Software Development
A software project has "Hero Developers" when 80% of contributions are
delivered by 20% of the developers. Are such heroes a good idea? Are too many
heroes bad for software quality? Is it better to have more/less heroes for
different kinds of projects? To answer these questions, we studied 661 open
source projects from Public open source software (OSS) Github and 171 projects
from an Enterprise Github.
We find that hero projects are very common. In fact, as projects grow in
size, nearly all project become hero projects. These findings motivated us to
look more closely at the effects of heroes on software development. Analysis
shows that the frequency to close issues and bugs are not significantly
affected by the presence of project type (Public or Enterprise). Similarly, the
time needed to resolve an issue/bug/enhancement is not affected by heroes or
project type. This is a surprising result since, before looking at the data, we
expected that increasing heroes on a project will slow down howfast that
project reacts to change. However, we do find a statistically significant
association between heroes, project types, and enhancement resolution rates.
Heroes do not affect enhancement resolution rates in Public projects. However,
in Enterprise projects, the more heroes increase the rate at which project
complete enhancements.
In summary, our empirical results call for a revision of a long-held truism
in software engineering. Software heroes are far more common and valuable than
suggested by the literature, particularly for medium to large Enterprise
developments. Organizations should reflect on better ways to find and retain
more of these heroesComment: 8 pages + 1 references, Accepted to International conference on
Software Engineering - Software Engineering in Practice, 201
- …