Structural Analysis of Large TTCN-3 Projects

Szabados, Kristóf

doi:10.1007/978-3-642-05031-2_19

Cited by 8 publications

(4 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We have previously defined ( [29]) several code smells for test systems written in TTCN-3 and have shown ( [28]) that publicly available TTCN-3 test systems have room for improvement. We have also already shown ( [26]), that test systems written in TTCN-3, can become large and complex structures. In this article we studied the long term evolution of a large test system in the industry.…”

Section: Discussionmentioning

confidence: 79%

“…In [26] we have shown that automated test systems written in TTCN-3 can grow large and complex similar to the structures studied in [31]. In [29] we have defined 86 code smells for TTCN-3 and their relations to international software quality standards.…”

Section: Our Contributionsmentioning

confidence: 98%

“…To support the testing these systems need, ETSI 2 developed the TTCN-3 3 language, which can be used in testing of reactive systems. By now test systems developed by ETSI, 3GPP 4 and in the industry, have evolved to be comparable to the tested systems in both size and complexity ( [26]). Standardized test systems were shown to contain design problems similar to those present in other (C / C++ / Java) systems ( [29,28]).…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Internal quality evolution of a large test system – an industrial study

Kovács

Szabados

2016

Acta Universitatis Sapientiae, Informatica

Self Cite

View full text Add to dashboard Cite

This paper presents our empirical observations related to the evolution of a large automated test system. The system observed is used in the industry as a test tool for complex telecommunication systems, itself consisting of more than one million lines of source code. This study evaluates how different changes during the development have changed the number of observed Code Smells in the test system. We have monitored the development of the test scripts and measured the code quality characteristics over a five years period.The observations show that the introduction of continuous integration, the existence of tool support for quality improvements in itself, changing the development methodologies (from waterfall to agile), changing technical and line management structure and personnel caused no measurable change in the trends of the observed Code Smells. Internal quality improvements were achieved mainly by individuals intrinsic motivation. Our measurements show similarities with earlier results on software systems evolutions presented by Lehman.