ALM Tool Data Usage in Software Process Metamodeling

Picha, Petr; Brada, Přemek

doi:10.1109/seaa.2016.37

Cited by 9 publications

(3 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Afterwards, the companies were asked to identify the main method meta elements that they would be interested in reconstructing from the software repositories. Linking data from software repositories to SPEM metaelements has also been done by others [27,28]. The final selection, that was influenced also by the data that is actually captured in software repositories, included the following method meta elements:…”

Section: Metamodels Of Software Development Methodsmentioning

confidence: 99%

“…There are also other research areas related to our research such as Organizational patterns, which also can be used to capture software development methods [45,46,47]. Mainly organizational patterns are still captured and documented manually, but some of the researchers are trying to use data from software repositories to detect bad practices (anti-patterns) [27,28]. These approaches could benefit from our research since they could analyze the behavior and patterns on the higher level, level of activities.…”

Section: Other Related Approachesmentioning

confidence: 99%

See 1 more Smart Citation

Reconstructing de facto software development methods

Janković¹,

Žitnik²,

Bajec³

2019

COMSIS J

View full text Add to dashboard Cite

Software development is a complex process that requires disciplined engineering approaches. Empirical studies show that companies still don't document their development practice, or if they do, these are not up-to-date and do not reflect how they really develop software. The main objective of this paper is to propose an approach that can help companies in documenting their real development practice. Comparing to existing approaches that require substantial effort on the side of project members, our approach extracts information on development practice directly from software repositories. Five companies have been studied to identify information that can be retrieved from software repositories. Based on this, an approach to reconstruct development practice has been developed. The approach has been evaluated on a real software repository shared by an additional company. The results confirm that software repository information suffice for the reconstruction of various aspects of development process, i.e. disciplines, activities, roles, and artifacts.

show abstract

Section: Metamodels Of Software Development Methodsmentioning

confidence: 99%

Section: Other Related Approachesmentioning

confidence: 99%

Reconstructing de facto software development methods

Janković¹,

Žitnik²,

Bajec³

2019

COMSIS J

View full text Add to dashboard Cite

show abstract

“…An ALM platform can be seen as a supervisor that covers the whole development process from the initial idea to the end of the product lifecycle through different core aspects: governance, development, and operations . They combine supporting tools such as version control systems (VCS) to handle the artifacts to issue tracking applications . Nowadays, many companies adopt ALM platforms to follow the entire lifecycle of their software product.…”

Section: Introductionmentioning

confidence: 99%

Using tool integration for improving traceability management testing processes: An automotive industrial experience

Amalfitano

Simone

Maietta

et al. 2019

J Software Evolu Process

View full text Add to dashboard Cite

Despite the high relevance of traceability in software processes, the activities of traceability creation and management are not always adequately supported in practice. The lack of integration between the tools adopted in the development processes is one of the main causes of such an ineffective management, where traceability relationships are still manually generated and maintained. In this paper we present an industrial experience we performed for improving the traceability management in a testing process performed in the Fiat Chrysler Automobiles company. In this context, we carried out a process for analyzing and identifying the main issues due to the ineffective traceability management and proposed a solution for addressing them.We designed and implemented a software architecture for integrating the existing application lifecycle management platform with the tools used in the process with the aim of automating the process execution and the traceability links management. The new architecture was validated by a case study that showed how the integration solution produced beneficial effects on quality attributes of the testing process. KEYWORDS automotive, industrial case study, software process improvement, tool integration, traceability management 1 INTRODUCTION Requirement traceability was defined by Gotel et al, 1 as the ability to describe and follow the life of a requirement, in both forward and backward directions.It is realized in practice by establishing relationships, usually defined trace links, between the requirements and one or more artifacts of the system. 2 Since then, this definition was extended, and nowadays, we talk more in general about software traceability for indicating the creation and the use of links (or connections) between different kinds of software artifacts such as requirements, models, source code, test cases, or test results. These connections are called trace links and connect in a bidirectional way a source artifact to a target artifact. The research community is devoting great efforts for addressing the topic of the traceability management that is the planning, the organization, and the coordination of all the activities related to traceability, including the creation, maintenance, and use of trace links. 3 Moreover, both software development standards and process assessment frameworks, such as ISO/IEC 15504, automotive SPICE, capability maturity model integration (CMMI), ISO 26262, and IEC 61508, suggest the companies to adopt traceability management solutions to guarantee Abbreviations: ALM, application lifecycle management; API, application programming interface; DSML, domain-specific modeling language; ECU, electronic control unit; FCA, Fiat Chrysler Automobiles; GUI, graphical user interface; ITL, incorrect traceability links; ITLRP, incorrect traceability links reduction percentage; MIL, model in the loop; MTL, missing traceability links; MTLRP, missing traceability links reduction percentage; RQ, research question; SP, speedup percentage; SPEM, software and system pr...

show abstract