activity
20172022
most citedTowards the Trustworthy Development of Active Medical Devices: A Hemodialysis Case Study

12 citations · 29 across the 8 of their papers we have counts for

collaborators

10 papers

cs.LO2022

Formalization of Advanced VOs semantics and VO Refinement

Sebastian Stock, Fabian Vu, David Geleßus +3

This document lays out the foundations for VO and requirement refinement, abstractions of models, and instantiations. Also, VOs on abstractions and instantiations are considered.

cs.LO20222 cited

IVOIRE Deliverable 1.1: Classification of existing VOs & tools and Formalization of VOs semantics

Sebastian Stock, Fabian Vu, Atif Mashkoor +2

This report discusses the foundations of the VO approach. Then, it explores multiple directions and argues about structure and applications.

cs.SE2021

Do Communities in Developer Interaction Networks align with Subsystem Developer Teams? An Empirical Study of Open Source Systems

Usman Ashraf, Christoph Mayr-Dorn, Atif Mashkoor +2

Studies over the past decade demonstrated that developers contributing to open source software systems tend to self-organize in "emerging" communities. This latent community struct…

cs.SE2021

Team-oriented Consistency Checking of Heterogeneous Engineering Artifacts

Michael Alexander Tröls, Atif Mashkoor, Alexander Egyed

Consistency checking of interdependent heterogeneous engineering artifacts, such as requirements, specifications, and code, is a challenging task in large-scale engineering project…

cs.SE2021

TaskAllocator: A Recommendation Approach for Role-based Tasks Allocation in Agile Software Development

Saad Shafiq, Atif Mashkoor, Christoph Mayr-Dorn +1

In this paper, we propose a recommendation approach -- TaskAllocator -- in order to predict the assignment of incoming tasks to potential befitting roles. The proposed approach, id…

cs.SE2021

Validation Obligations: A Novel Approach to Check Compliance between Requirements and their Formal Specification

Atif Mashkoor, Michael Leuschel, Alexander Egyed

Traditionally, practitioners use formal methods pre-dominately for one half of the quality-assurance process: verification (do we build the software right?). The other half -- vali…