Automatically Adapting Source Code to Document Provenance

Being able to ask questions about the provenance of some data requires documentation on each influence on that data's existence and content. Much software exists, and is being developed, for which there is no provenance-awareness, i.e. at best, the data it outputs can be connected to its inputs, but with no record of intermediate processing. Further, where some record of processing does exist, e.g. as logs, it is not in a form easily connected with that of other processes. We would like to enable compiled software to record useful documentation without requiring prior manual adaptation. In this paper, we present an approach to adapting source code from its original form without manual manipulation, to record information on data provenance during execution.

I would like to change the world, but they wouldn't let me have the source code

In this paper we present the findings of a group problem-solving task involving eight randomly selected students. The focus of this study was to identify and explore students' application of generic skills, cross-disciplinary knowledge and skills, innovative thinking and engineering disciplinary knowledge. While this was the main aim of this study, we also used the findings of this study to triangulate the findings of a broader study which aims to identify and explore students' perceptions of problem based learning (PBL) in first year electrical engineering. The broader qualitative study of learners in a problem based engineering context will identify, explore and report on the factors that influence student learning behaviours and their attitudes as future engineers. Studying the learning cultures from the students' view point in a diverse student group should provide evidence to further theorize about the models of self-regulation in autonomous learners. For this group problem solving activity, we designed a problem (advanced lift controller system) and allowed students one hour to work on a solution for this problem. The eight students from a number of actual PBL groups were divided into two groups depending upon their availability. Both groups were given the same problem. The researcher played the role of a facilitator and collected the data simultaneously. Students were given access to books relevant to the problem, computer access and access to the Internet. They were also provided with links to sample websites such as the University's electronic library and other technology related websites on the World Wide Web. The activity was designed such that students were not required to arrive at a definite outcome. However, they were asked to brainstorm ideas, and as a group, to decide on ways that they would obtain and share information and to formulate and suggest possible innovative solutions to the problem. Data for this activity was collected by means of observation. The activity was audio and video recorded in order to help revisit the data at any stage. At the time this study was conducted, students had completed two PBL units in their first year of an electronic and electrical engineering undergraduate degree course. This study also provided insight into students' attitudes and their behaviours towards learning in a group setting, learning approaches and outcomes, different responses to the heterogeneity of the students in the group, and their responsibility and accountability in an autonomous learning setting such as PBL.

Using Source-Code Analysis to Help End-user Programmers Create Dependable Software

Not long ago, most software was written by professional programmers, who could be presumed to have an interest in software engineering methodologies and in tools and techniques for improving software dependability. Today, however, a great deal of software is written not by professionals but by end-users, who create applications such as multimedia simulations, dynamic web pages, and spreadsheets. Applications such as these are often used to guide important decisions or aid in important tasks, and it is important that they be sufficiently dependable, but evidence shows that they frequently are not. For example, studies have shown that a large percentage of the spreadsheets created by end-users contain faults. Despite such evidence, until recently, relatively little research had been done to help end-users create more dependable software. We have been working to address this problem by finding ways to provide at least some of the benefits of formal software engineering techniques to end-user programmers. In this talk, focusing on the spreadsheet application paradigm, I present several of our approaches, focusing on methodologies that utilize source-code-analysis techniques to help end-users build more dependable spreadsheets. Behind the scenes, our methodologies use static analyses such as dataflow analysis and slicing, together with dynamic analyses such as execution monitoring, to support user tasks such as validation and fault localization. I show how, to accommodate the user base of spreadsheet languages, an interface to these methodologies can be provided in a manner that does not require an understanding of the theory behind the analyses, yet supports the interactive, incremental process by which spreadsheets are created. Finally, I present empirical results gathered in the use of our methodologies that highlight several costs and benefits trade-offs, and many opportunities for future work.

Automatic Labeling of Software Components and their Evolution using Log-Likelihood Ratio of Word Frequencies in Source Code

As more and more open-source software components become available on the internet we need automatic ways to label and compare them. For example, a developer who searches for reusable software must be able to quickly gain an understanding of retrieved components. This understanding cannot be gained at the level of source code due to the semantic gap between source code and the domain model. In this paper we present a lexical approach that uses the log-likelihood ratios of word frequencies to automatically provide labels for software components. We present a prototype implementation of our labeling/comparison algorithm and provide examples of its application. In particular, we apply the approach to detect trends in the evolution of a software system.

A flowchart-to-source-code conversion program for GPSS/360 /

Originally presented as the author's thesis (M.S.), University of Illinois at Urbana-Champaign.

Position Paper: Improving Source Code Reuse through Documentation Standardization

In the context of Software Reuse providing techniques to support source code retrieval has been widely experimented. However, much effort is required in order to find how to match classical Information Retrieval and source code characteristics and implicit information. Introducing linguistic theories in the software development process, in terms of documentation standardization may produce significant benefits when applying Information Retrieval techniques. The goal of our research is to provide a tool to improve source code search and retrieval In order to achieve this goal we apply some linguistic rules to the development process.

Review and Outlooks of the Means for Visualization of Syntax Semantics and Source Code. Procedural and Object Oriented Paradigm – Differences

In the article, we have reviewed the means for visualization of syntax, semantics and source code for programming languages which support procedural and/or object-oriented paradigm. It is examined how the structure of the source code of the structural and object-oriented programming styles has influenced different approaches for their teaching. We maintain a thesis valid for the object-oriented programming paradigm, which claims that the activities for design and programming of classes are done by the same specialist, and the training of this specialist should include design as well as programming skills and knowledge for modeling of abstract data structures. We put the question how a high level of abstraction in the object-oriented paradigm should be presented in simple model in the design stage, so the complexity in the programming stage stay low and be easily learnable. We give answer to this question, by building models using the UML notation, as we take a concrete example from the teaching practice including programming techniques for inheritance and polymorphism.

Generation of Testing Source Code for Object-Oriented Programs

Красимир Манев, Антон Желязков, Станимир Бойчев - В статията е представена имплементацията на последната фаза на автоматичен генератор на тестови данни за структурно тестване на софтуер, написан на обектно-ориентиран език за програмиране – генерирането на изходен код на тестващия модул. Някои детайли от имплементацията на останалите фази, които са важни за имплементацията на последната фаза, са представени първо. След това е описан и алгоритъмът за генериране на кода на тестващия модул.