Context. Code quality is a key issue in software development. The ability to develop high quality software is therefore a key learning goal of computing programs. However, there are no universally accepted measures to assess the quality of code and current standards are considered weak. Furthermore, there are many facets to code quality. Defining and explaining the concept of code quality is therefore a challenge faced by many educators. Objectives. In this working group, we investigated code quality as perceived by students, educators, and professional developers, in particular, the differences in their views of code quality and which quality aspects they consider as more or less important. Furthermore, we investigated their sources for information about code quality and its assessment. Methods. We interviewed 34 students, educators and professional developers regarding their perceptions of code quality. For the interviews they brought along code from their own experience to discuss and exemplify code quality. Results. There was no common definition of code quality among * Working group co-leaders: Jürgen Börstler, Harald Störrle, and Daniel Toll
9 December 2024 in Digital Threats: Research and Practice
Advanced persistent threat (APT) attacks present a significant challenge for any organization, as they are difficult to detect due to their elusive nature and characteristics. In this article, we conduct a comprehensive literature review to investigate the various APT attack detection systems and approaches and classify them based on their threat model and detection method. Our findings reveal common obstacles in APT attack detection, such as correctly attributing anomalous behavior to APT attack activities, limited availability of public datasets and inadequate evaluation methods, challenges with detection procedures, and misinterpretation of requirements. Based on our findings, we propose a reference architecture to enhance the comparability of existing systems and provide a framework for classifying detection systems. In addition, we look in detail at the problems encountered in current evaluations and other scientific gaps, such as a neglected consideration of integrating the systems into existing security architectures and their adaptability and durability. While no one-size-fits-all solution exists for APT attack detection, this review shows that graph-based approaches hold promising potential. However, further research is required for real-world usability, considering the systems’ adaptability and explainability.
21 September 2023 in Empirical Software Engineering
There are many aspects of code quality, some of which are difficult to capture or to measure. Despite the importance of software quality, there is a lack of commonly accepted measures or indicators for code quality that can be linked to quality attributes. We investigate software developers’ perceptions of source code quality and the practices they recommend to achieve these qualities. We analyze data from semi-structured interviews with 34 professional software developers, programming teachers and students from Europe and the U.S. For the interviews, participants were asked to bring code examples to exemplify what they consider good and bad code, respectively. Readability and structure were used most commonly as defining properties for quality code. Together with documentation, they were also suggested as the most common target properties for quality improvement. When discussing actual code, developers focused on structure, comprehensibility and readability as quality properties. When analyzing relationships between properties, the most commonly talked about target property was comprehensibility. Documentation, structure and readability were named most frequently as source properties to achieve good comprehensibility. Some of the most important source code properties contributing to code quality as perceived by developers lack clear definitions and are difficult to capture. More research is therefore necessary to measure the structure, comprehensibility and readability of code in ways that matter for developers and to relate these measures of code structure, comprehensibility and readability to common software quality attributes.
1 April 2013 in HMD Praxis der Wirtschaftsinformatik
Aktuelle Endgeräte wie Smartphones und Tablets sind komfortabel zu transportieren und bieten vielfältige Einsatzmöglichkeiten; im privaten Bereich ist ihr Einsatz daher populär. Auch der betriebliche Einsatz derartiger Geräte ist weit verbreitet. Doch wer will schon zwei Geräte, eines für den privaten und eines für den betrieblichen Einsatz? Als Lösung wird »dual use« propagiert: ein einziges Gerät für die private und betriebliche Nutzung. Daraus wird »Bring Your Own Device« (BYOD), wenn Benutzer ihre privaten Geräte für die betriebliche Nutzung einsetzen. Dies birgt für Unternehmen Chancen und Risiken. Das Spektrum möglicher technischer Ansätze für BYOD wird vorgestellt und diskutiert, um Entscheidungsunterstützung bei der Wahl eines geeigneten Ansatzes zu bieten.
Several tools to support autograding of student provided SQL statements have already been introduced. The full potential of such tools can only be leveraged, if they extend beyond grading efficiency by also providing tutoring capabilities to the students. With that, tools become really useful by offering self-paced and individually timed learning experiences. In this paper we present an extension for an SQL autograder which improves the hints generated for students in cases where their solution is not entirely correct. Our approach is to compare the student's solution with the model solution structurally to identify differences between the syntax trees describing the statements. This complements comparing the student's query with a model solution based on query results. In addition to improving the quality of hints generated for the students, this concept can also be used easily for data manipulation language (DML) or data definition language (DDL) statements, thus extending the applicability of the autograder. Along with details about the concept we present some example hints generated to illustrate the usefulness of the approach. We also report anecdotally on experiences with the system in two different level database courses. Results from different instances of one of them show improvements of student learning as well as student involvement by using the newly generated hints.