| 1. |
- Backhouse, Roland, et al.
(författare)
-
Generic Programming: An Introduction
- 1999
-
Ingår i: Advanced Functional Programming. ; 1608, s. 28--115-
-
Bokkapitel (övrigt vetenskapligt/konstnärligt)
|
|
| 2. |
- Bellotti, Francesco, et al.
(författare)
-
Alessandro De Gloria-1955-2023
- 2023
-
Ingår i: INTERNATIONAL JOURNAL OF SERIOUS GAMES. - : Serious Games Society. - 2384-8766. ; 10:1, s. 2-3
-
Tidskriftsartikel (övrigt vetenskapligt/konstnärligt)
|
|
| 3. |
- Börstler, Jürgen, 1960-, et al.
(författare)
-
Developers talking about code quality
- 2023
-
Ingår i: Empirical Software Engineering. - : Springer. - 1382-3256 .- 1573-7616. ; 28:6
-
Tidskriftsartikel (refereegranskat)abstract
- 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.
|
|
| 4. |
- Börstler, Jürgen, et al.
(författare)
-
I know it when I see it : Perceptions of Code Quality ITiCSE'17 Working Group Report
- 2017
-
Ingår i: ITICSE-WGR'17: PROCEEDINGS OF THE 2017 ITICSE CONFERENCE WORKING GROUP REPORTS. - New York, NY, USA : ACM Digital Library. - 9781450347044 ; , s. 70-85
-
Konferensbidrag (refereegranskat)abstract
- 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 or within these groups. Quality was mostly described in terms of indicators that could measure an aspect of code quality. Among these indicators, readability was named most frequently by all groups. The groups showed significant differences in the sources they use for learning about code quality with education ranked lowest in all groups.Conclusions. Code quality should be discussed more thoroughly in educational programs.
|
|
| 5. |
- Börstler, Jürgen, et al.
(författare)
-
"I know it when I see it" : perceptions of code quality
- 2017
-
Ingår i: ITiCSE '17: Proceedings of the 2017 ACM Conference on Innovation and Technology in Computer Science Education. - New York, NY, USA : Association for Computing Machinery (ACM). - 9781450347044 ; , s. 389-389
-
Konferensbidrag (refereegranskat)abstract
- Code quality is a key issue in software development. The ability to develop software of high quality 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 consideredweak. Furthermore, there are many facets to code quality. Defining and explaining the concept of code quality is therefore a challenge faced by many educators. In this working group, we investigate the perceptions of code quality of students, teachers, and professional programmers. In particular, we are interested in the differences in views of code quality by students, educators, and professional programmers and which quality aspects they consider as more or less important. Furthermore, we are interested in which sources of information on code quality and its assessment are used by these groups. Eventually, this will help us to develop resources that can be used to broaden students' views on software quality.
|
|
| 6. |
- Börstler, Jürgen, et al.
(författare)
-
"I know it when I see it" - Perceptions of Code Quality ITiCSE'17 Working Group Report
- 2018
-
Ingår i: ITICSE-WGR'17. - New York, NY, USA : ACM Publications. ; , s. 70-85
-
Konferensbidrag (refereegranskat)abstract
- 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 or within these groups. Quality was mostly described in terms of indicators that could measure an aspect of code quality. Among these indicators, readability was named most frequently by all groups. The groups showed significant differences in the sources they use for learning about code quality with education ranked lowest in all groups. Conclusions. Code quality should be discussed more thoroughly in educational programs.
|
|
| 7. |
- Gerdes, Alex, 1978, et al.
(författare)
-
Ask-Elle: an Adaptable Programming Tutor for Haskell Giving Automated Feedback
- 2017
-
Ingår i: International Journal of Artificial Intelligence in Education. - : Springer Science and Business Media LLC. - 1560-4306 .- 1560-4292. ; 27:1, s. 65-100
-
Tidskriftsartikel (refereegranskat)abstract
- Ask-Elle is a tutor for learning the higher-order, strongly-typed functional programming language Haskell. It supports the stepwise development of Haskell programs by verifying the correctness of incomplete programs, and by providing hints. Programming exercises are added to Ask-Elle by providing a task description for the exercise, one or more model solutions, and properties that a solution should satisfy. The properties and model solutions can be annotated with feedback messages, and the amount of flexibility that is allowed in student solutions can be adjusted. The main contribution of our work is the design of a tutor that combines (1) the incremental development of different solutions in various forms to a programming exercise with (2) automated feedback and (3) teacher-specified programming exercises, solutions, and properties. The main functionality is obtained by means of strategy-based model tracing and property-based testing. We have tested the feasibility of our approach in several experiments, in which we analyse both intermediate and final student solutions to programming exercises, amongst others.
|
|
| 8. |
- Jansson, Patrik, 1972, et al.
(författare)
-
A Framework for Polytypic Programming on Terms, with an Application to Rewriting
- 2000
-
Ingår i: Workshop on Generic Programming.
-
Konferensbidrag (refereegranskat)abstract
- Rewriting is a typical example of a polytypic function. Given any value of a datatype (an algebra of terms), and rules to rewrite values of that datatype, we want a function that rewrites the value to normal form if the value is normalizable. This paper develops a polytypic rewriting function that uses the parallel innermost rewriting strategy. It improves upon our earlier work on polytypic rewriting in two fundamental ways. Firstly, the rewriting function uses a term interface that hides the polytypic part from the rest of the program. The term interface is a framework for polytypic programming on terms. This implies that the rewriting function is independent of the particular implementation of polytypism. We give several functions and laws on terms, which simplify calculating with programs. Secondly, the rewriting function is developed together with a correctness proof. We just present the result of the correctness proof, the proof itself is published elsewhere.
|
|
| 9. |
- Jansson, Patrik, 1972, et al.
(författare)
-
Functional Pearl: Polytypic Unification
- 1998
-
Ingår i: Journal of Functional Programming. - 1469-7653 .- 0956-7968. ; 8:5, s. 527-536
-
Tidskriftsartikel (refereegranskat)abstract
- Unification, or two-way pattern matching, is the process of solving an equation involving two first-order terms with variables. Unification is used in type inference in many programming languages and in the execution of logic programs. This means that unification algorithms have to be written over and over again for different term types. Many other functions also make sense for a large class of datatypes; examples are pretty printers, equality checks, maps etc. They can be defined by induction on the structure of user-defined datatypes. Implementations of these functions for different datatypes are closely related to the structure of the datatypes. We call such functions polytypic. This paper describes a unification algorithm parametrised on the type of the terms, and shows how to use polytypism to obtain a unification algorithm that works for all regular term types.
|
|
| 10. |
- Jansson, Patrik, 1972, et al.
(författare)
-
PolyLib - a polytypic function library
- 1998
-
Ingår i: Workshop on Generic Programming.
-
Konferensbidrag (refereegranskat)abstract
- A polytypic program is a program that behaves uniformly over a large class of datatypes. For functional polytypic programming this uniformity is achieved by parameterizing functions over type constructors to obtain polytypic functions. A polytypic function is defined either by induction on the structure of regular type constructors or in terms of other polytypic functions. PolyP is an extension of the functional programming language Haskell with a construct for defining polytypic functions. PolyP is a type guided preprocessor that generates instances of polytypic functions and inserts applications of these instances where needed.During the last few years we have used PolyP to construct a number of polytypic programs, for example for unification, parsing, rewriting, pattern matching, etc. These polytypic programs use several basic polytypic functions, such as the relatively well-known cata and map, but also less well-known functions such as propagate and thread. We have collected these basic polytypic functions in the library of PolyP: PolyLib. This paper describes the polytypic functions in PolyLib, motivates their presence in the library, and gives a rationale for their design. Thus we hope to share our experience with other researchers in the field. We will assume the reader has some familiarity with the field of polytypic programming.Of course, a library is an important part of a programming language. Languages like Java, Delphi, Perl and Haskell are popular partly because of their useful and extensive libraries. For a polytypic programming language it is even more important to have a clear and well-designed library: writing polytypic programs is difficult, and we do not expect many programmers to write polytypic programs. On the other hand, many programmers use polytypic programs such as parser generators, equality functions, etc.This is a first attempt to describe the library of PolyP; we expect that both the form and content of this description will change over time. One of the goals of this paper is to obtain feedback on the library design from other researchers working within the field. At the moment the library only contains the basic polytypic functions. In the future we will develop special purpose sublibraries for polytypic functions with more advanced functionality, for example for parsing and the other programs mentioned above.
|
|
