2018
DOI: 10.1016/j.ifacol.2018.06.239
|View full text |Cite
|
Sign up to set email alerts
|

Technical Debt indication in PLC Code for automated Production Systems: Introducing a Domain Specific Static Code Analysis Tool

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
2
1

Relationship

1
2

Authors

Journals

citations
Cited by 3 publications
(1 citation statement)
references
References 14 publications
0
1
0
Order By: Relevance
“…hardware, software, electrical/electronics) following the V-Model, and (2) risk trace matrix and corresponding internal guidelines following GAMP 5. While TD in the classical software engineering domain can be identified with code analysis, the work on TD in the aPS domain is still limited [6]. Recent work on TD identification in the aPS domain still focuses on software discipline [7]. Thus, a systematic method is lacking to identify TD in other fields in the aPS domain.…”
Section: Introductionmentioning
confidence: 99%
“…hardware, software, electrical/electronics) following the V-Model, and (2) risk trace matrix and corresponding internal guidelines following GAMP 5. While TD in the classical software engineering domain can be identified with code analysis, the work on TD in the aPS domain is still limited [6]. Recent work on TD identification in the aPS domain still focuses on software discipline [7]. Thus, a systematic method is lacking to identify TD in other fields in the aPS domain.…”
Section: Introductionmentioning
confidence: 99%