RSTrace+: Reviewer suggestion using software artifact traceability graphs

2021 ◽  
Vol 130 ◽  
pp. 106455
Author(s):  
Emre Sülün ◽  
Eray Tüzün ◽  
Uğur Doğrusöz
Keyword(s):  
Software Artifact

On Software Architecture Processes and their Use in Practice

2014 ◽  
pp. 198-218
Author(s):  
Perla Velasco-Elizondo ◽  
Humberto Cervantes
Keyword(s):  
Software Architecture ◽  
Level Structure ◽  
Practical Experience ◽  
High Quality ◽  
Software Artifact ◽  
High Level ◽  
Architecture Development

Software architecture is a very important software artifact, as it describes a system’s high-level structure and provides the basis for its development. Software architecture development is not a trivial task; to this end, a number of methods have been proposed to try to systematize their related processes to ensure predictability, repeatability, and high quality. In this chapter, the authors review some of these methods, discuss some specific problems that they believe complicate their adoption, and present one practical experience where the problems are addressed successfully.

Analysis and Evaluation of Software Artifact Reuse Environments

Gamification ◽  
2015 ◽  
pp. 1212-1222
Author(s):  
Sajjad Mahmood ◽  
Moataz Ahmed ◽  
Mohammad Alshayeb
Keyword(s):  
Life Cycle ◽  
Software Reuse ◽  
Lower Cost ◽  
Early Stage ◽  
Future Research ◽  
Software Life Cycle ◽  
Analysis And Evaluation ◽  
Software Artifacts ◽  
Software Artifact ◽  
Systematic Reuse

Software reuse enables the development of software that is of better quality and at lower cost. Software reuse environments are sought to enhance the reuse of software artifacts especially when done at early-stage of the software life cycle. A number of software reuse environments have been proposed, however, there is no framework that helps in analyzing and evaluating such environments. In this paper the authors provide an attribute-based framework to analyze, evaluate, classify and compare the reuse environments in order to aid practitioners and researchers to select the appropriate reuse environments for their use. The authors first present a survey of existing reuse environments for systematic reuse of software artifacts. Then, they use the framework to analyze those reuse environments. The evaluation of existing environments provides an understanding of current reuse approaches and identifies gaps for future research.

scholarly journals Publish or perish, but do not forget your software artifacts

2020 ◽  
Vol 25 (6) ◽  
pp. 4585-4616 ◽  
Author(s):  
Robert Heumüller ◽  
Sebastian Nielebock ◽  
Jacob Krüger ◽  
Frank Ortmeier
Keyword(s):  
Software Engineering ◽  
Open Science ◽  
Positive Trend ◽  
Scientific Impact ◽  
Engineering Research ◽  
Publish Or Perish ◽  
Software Artifacts ◽  
Research Track ◽  
Software Artifact ◽  
Software Engineering Research

Abstract Open-science initiatives have gained substantial momentum in computer science, and particularly in software-engineering research. A critical aspect of open-science is the public availability of artifacts (e.g., tools), which facilitates the replication, reproduction, extension, and verification of results. While we experienced that many artifacts are not publicly available, we are not aware of empirical evidence supporting this subjective claim. In this article, we report an empirical study on software artifact papers (SAPs) published at the International Conference on Software Engineering (ICSE), in which we investigated whether and how researchers have published their software artifacts, and whether this had scientific impact. Our dataset comprises 789 ICSE research track papers, including 604 SAPs (76.6 %), from the years 2007 to 2017. While showing a positive trend towards artifact availability, our results are still sobering. Even in 2017, only 58.5 % of the papers that stated to have developed a software artifact made that artifact publicly available. As we did find a small, but statistically significant, positive correlation between linking to artifacts in a paper and its scientific impact in terms of citations, we hope to motivate the research community to share more artifacts. With our insights, we aim to support the advancement of open science by discussing our results in the context of existing initiatives and guidelines. In particular, our findings advocate the need for clearly communicating artifacts and the use of non-commercial, persistent archives to provide replication packages.

Software Artifact for Article

2018 ◽  
Author(s):  
Ulan Degenbaev ◽  
Jochen Eisinger ◽  
Kentaro Hara ◽  
Marcel Hlopko ◽  
Michael Lippautz ◽  
...  
Keyword(s):  
Software Artifact

Software Artifact Prioritization based on the Frequency of Use

2009 ◽  
Vol 7 (3) ◽  
pp. 369-376 ◽  
Author(s):  
D. Cabrero ◽  
J. Garzas ◽  
M. Piattini
Keyword(s):  
Frequency Of Use ◽  
Software Artifact

scholarly journals Description model of programming style ecosystem

2020 ◽  
pp. 074-081
Author(s):  
N.A. Sydorov ◽  
◽  
N.N. Sydorova ◽  
E.N. Sydorov ◽  
◽  
...  
Keyword(s):  
Generalized Model ◽  
Software Artifacts ◽  
Software Product ◽  
Software Artifact ◽  
First Time

In the process of developing and maintaining a software product, many things are created and used that are called software artefacts. Software artifacts are changed, reused, and change relationships in the development and maintenance processes of a software product. The complexity and variety of software artifact relationships require adequate means of description and management. They may be a software artifact ecosystem. In the article, for the first time, a concept of a software artifact ecosystem is proposed. The concept describes a generalized model of the software artifact ecosystem, which is the Cornerstone ecosystem type and consists of three actors – the platform, the software, and the artifact. The roles of actors in the ecosystem are indicated, the relationships between actors are described. As an example, based on the generalized model of the software artifact ecosystem, a declarative model of the programming style ecosystem has been developed.

scholarly journals DESENVOLVIMENTO DE UMA FERRAMENTA PARA CONSTRUIR DINAMICAMENTE RELATÓRIOS NO CRYSTAL REPORTS

2013 ◽  
Vol 5 (1) ◽  
pp. 26-42
Author(s):  
Luiz Felipe Stangarlin ◽  
Francisco Assis da Silva ◽  
Marcelo Vinícius Creres Rosa
Keyword(s):  
Visual Information ◽  
Source Code ◽  
Dynamic Link Library ◽  
Repetitive Tasks ◽  
Development Tools ◽  
Building Process ◽  
Software Artifact ◽  
Crystal Report ◽  
Crystal Reports ◽  
Dynamic Link

The use of tools has always been necessarysince the beginning of computing, due to repetitive tasks or due to complexity when they were made manually. Because of this, there were several kindsof development tools over the time. Nowadays, CASE tools can generate severalkindsof artifacts suchasforms, source code, documentation and diagrams. However, the report building process is still done by the developer, where he needs to create layout and to add the items what he wants, assembling the report (artifact).This paper describes a tool that generates this software artifact, through the manipulation of objects in the Crystal Report dynamic link library (used for reporting purposes). To generate the artifact templates are used as a base from which visual information are copied, which simplify the definition and improve reuse. The developed architecture is modular and allows the tool to be attached by application developer or to work in conjunction with CASE generators

Analysis and Evaluation of Software Artifact Reuse Environments

2014 ◽  
Vol 2 (2) ◽  
pp. 54-65 ◽  
Author(s):  
Sajjad Mahmood ◽  
Moataz Ahmed ◽  
Mohammad Alshayeb
Keyword(s):  
Life Cycle ◽  
Software Reuse ◽  
Lower Cost ◽  
Early Stage ◽  
Future Research ◽  
Software Life Cycle ◽  
Analysis And Evaluation ◽  
Software Artifacts ◽  
Software Artifact ◽  
Systematic Reuse

Software reuse enables the development of software that is of better quality and at lower cost. Software reuse environments are sought to enhance the reuse of software artifacts especially when done at early-stage of the software life cycle. A number of software reuse environments have been proposed, however, there is no framework that helps in analyzing and evaluating such environments. In this paper the authors provide an attribute-based framework to analyze, evaluate, classify and compare the reuse environments in order to aid practitioners and researchers to select the appropriate reuse environments for their use. The authors first present a survey of existing reuse environments for systematic reuse of software artifacts. Then, they use the framework to analyze those reuse environments. The evaluation of existing environments provides an understanding of current reuse approaches and identifies gaps for future research.

Ontological Rules for UML-Based Conceptual Modeling

2011 ◽  
Vol 2 (1) ◽  
pp. 24-44
Author(s):  
Shan Lu ◽  
Jeffrey Parsons
Keyword(s):  
Software Design ◽  
Design Research ◽  
Conceptual Modeling ◽  
Implementation Strategies ◽  
Object Oriented ◽  
Research Approach ◽  
Case Tool ◽  
Software Artifact ◽  
Uml Specification ◽  
Shed Light

UML is used as a language for object-oriented software design, and as a language for conceptual modeling of applications domains. Given the differences between these purposes, UML’s origins in software engineering might limit its appropriateness for conceptual modeling. In this context, Evermann and Wand have proposed a set of well-defined ontological rules to constrain the construction of UML diagrams to reflect underlying ontological assumptions about the real world. The authors extend their work using a design research approach that examines these rules by studying the consequences of integrating them into a UML CASE tool. The paper demonstrates how design insights from incorporating theory-based modeling rules in a software artifact can be used to shed light on the rules themselves. In particular, the authors distinguish four categories of rules for implementation purposes, reflecting the relative importance of different rules and the degree of flexibility available in enforcing them. They propose distinct implementation strategies that correspond to these four rule categories and identify some redundant rules as well as some rules that cannot be implemented without changing the UML specification. The rules are implemented in an open-source UML CASE tool.

Sign in / Sign up

Export Citation Format

Share Document