The compact city and the residential developer

Although the compact city is widely promoted as a sustainable form of urban development, little attention has been paid to the feasilibity of its implementation in practice. This paper addresses this isse by presenting the findings of a questionnaire study into the viability of the compact city from the perspective of the volume housebuilder. The study shows that, although well aware of the inherent problems witht the compact city, most were generally positive about the need to redirect more development back into urban areas. In addition, they suggested a large number of strategies for change, including i) a role for public sector agencies in overcoming the condstraints on urban sites; ii) the need for an upward reveision of acceptable densities in local plans and design guides; and iii) the creation of a separate, or revised, Use Class Order to enable mixed use development to compete on a level playing field. It is concluded that the residential developer could be engaged in the process of urban containment provided proposals for implementing the compact city of devised. The need for continuing research to test the actual effects of specific schemes is emphasised.

Interactive theorem provers: issues faced as a user and tackled as a developer

Interactive theorem provers (ITP for short) are tools whose final aim is to certify proofs written by human beings. To reach that objective they have to fill the gap between the high level language used by humans for communicating and reasoning about mathematics and the lower level language that a machine is able to “understand” and process. The user perceives this gap in terms of missing features or inefficiencies. The developer tries to accommodate the user requests without increasing the already high complexity of these applications. We believe that satisfactory solutions can only come from a strong synergy between users and developers. We devoted most part of our PHD designing and developing the Matita interactive theorem prover. The software was born in the computer science department of the University of Bologna as the result of composing together all the technologies developed by the HELM team (to which we belong) for the MoWGLI project. The MoWGLI project aimed at giving accessibility through the web to the libraries of formalised mathematics of various interactive theorem provers, taking Coq as the main test case. The motivations for giving life to a new ITP are: • study the architecture of these tools, with the aim of understanding the source of their complexity • exploit such a knowledge to experiment new solutions that, for backward compatibility reasons, would be hard (if not impossible) to test on a widely used system like Coq. Matita is based on the Curry-Howard isomorphism, adopting the Calculus of Inductive Constructions (CIC) as its logical foundation. Proof objects are thus, at some extent, compatible with the ones produced with the Coq ITP, that is itself able to import and process the ones generated using Matita. Although the systems have a lot in common, they share no code at all, and even most of the algorithmic solutions are different. The thesis is composed of two parts where we respectively describe our experience as a user and a developer of interactive provers. In particular, the first part is based on two different formalisation experiences: • our internship in the Mathematical Components team (INRIA), that is formalising the finite group theory required to attack the Feit Thompson Theorem. To tackle this result, giving an effective classification of finite groups of odd order, the team adopts the SSReflect Coq extension, developed by Georges Gonthier for the proof of the four colours theorem. • our collaboration at the D.A.M.A. Project, whose goal is the formalisation of abstract measure theory in Matita leading to a constructive proof of Lebesgue’s Dominated Convergence Theorem. The most notable issues we faced, analysed in this part of the thesis, are the following: the difficulties arising when using “black box” automation in large formalisations; the impossibility for a user (especially a newcomer) to master the context of a library of already formalised results; the uncomfortable big step execution of proof commands historically adopted in ITPs; the difficult encoding of mathematical structures with a notion of inheritance in a type theory without subtyping like CIC. In the second part of the manuscript many of these issues will be analysed with the looking glasses of an ITP developer, describing the solutions we adopted in the implementation of Matita to solve these problems: integrated searching facilities to assist the user in handling large libraries of formalised results; a small step execution semantic for proof commands; a flexible implementation of coercive subtyping allowing multiple inheritance with shared substructures; automatic tactics, integrated with the searching facilities, that generates proof commands (and not only proof objects, usually kept hidden to the user) one of which specifically designed to be user driven.

A Trustability Metric for Code Search based on Developer Karma

The promise of search-driven development is that developers will save time and resources by reusing external code in their local projects. To efficiently integrate this code, users must be able to trust it, thus trustability of code search results is just as important as their relevance. In this paper, we introduce a trustability metric to help users assess the quality of code search results and therefore ease the cost-benefit analysis they undertake trying to find suitable integration candidates. The proposed trustability metric incorporates both user votes and cross-project activity of developers to calculate a "karma" value for each developer. Through the karma value of all its developers a project is ranked on a trustability scale. We present JBENDER, a proof-of-concept code search engine which implements our trustability metric and we discuss preliminary results from an evaluation of the prototype.

Replaying past changes in multi-developer projects

What was I working on before the weekend? and What were the members of my team working on during the last week? are common questions that are frequently asked by a developer. They can be answered if one keeps track of who changes what in the source code. In this work, we present Replay, a tool that allows one to replay past changes as they happened at a fine-grained level, where a developer can watch what she has done or understand what her colleagues have done in past development sessions. With this tool, developers are able to not only understand what sequence of changes brought the system to a certain state (e.g., the introduction of a defect), but also deduce reasons for why her colleagues performed those changes. One of the applications of such a tool is also discovering the changes that broke the code of a developer.

Categorizing Developer Information Needs in Software Ecosystems

We present the results of an investigation into the nature of the information needs of software developers who work in projects that are part of larger ecosystems. In an open- question survey we asked framework and library developers about their information needs with respect to both their upstream and downstream projects. We investigated what kind of information is required, why is it necessary, and how the developers obtain this information. The results show that the downstream needs are grouped into three categories roughly corresponding to the different stages in their relation with an upstream: selection, adop- tion, and co-evolution. The less numerous upstream needs are grouped into two categories: project statistics and code usage. The current practices part of the study shows that to sat- isfy many of these needs developers use non-specific tools and ad hoc methods. We believe that this is a largely unexplored area of research.

A Quantitative Analysis of Developer Information Needs in Software Ecosystems

We present the results of an investigation into the nature of information needs of software developers who work in projects that are part of larger ecosystems. This work is based on a quantitative survey of 75 professional software developers. We corroborate the results identified in the sur- vey with needs and motivations proposed in a previous sur- vey and discover that tool support for developers working in an ecosystem context is even more meager than we thought: mailing lists and internet search are the most popular tools developers use to satisfy their ecosystem-related information needs.

NakInfo online: Developer's manual

The Local Urban Observatory in Nakuru (LUO, Kenya 2003) has developed a progressive and to date unique electronic information service called NakInfo. The objective of LUO is to make residents aware of public services delivery by their Local Authority, in this case the Municipal Council of Nakuru, and give them a voice in achieving improved quality of life. NakInfo facilitates community participation in local government business and demonstrates how to implement such participation in a developing country. The LUO project was formally initiated by the Municipal Council of Nakuru in January 2003, in collaboration with the Centre for Development and Environment (CDE) of the University of Berne (Switzerland) with funding from the Swiss Agency for Development and Cooperation (SDC).

Modification and Developer Metrics at the Function Level: Metrics for the Study of the Evolution of a Software Project

Software evolution, and particularly its growth, has been mainly studied at the file (also sometimes referred as module) level. In this paper we propose to move from the physical towards a level that includes semantic information by using functions or methods for measuring the evolution of a software system. We point out that use of functions-based metrics has many advantages over the use of files or lines of code. We demonstrate our approach with an empirical study of two Free/Open Source projects: a community-driven project, Apache, and a company-led project, Novell Evolution. We discovered that most functions never change; when they do their number of modifications is correlated with their size, and that very few authors who modify each; finally we show that the departure of a developer from a software project slows the evolution of the functions that she authored.

Valuation: Developer support for by-references to by-value type conversion.

Modern object oriented languages like C# and JAVA enable developers to build complex application in less time. These languages are based on selecting heap allocated pass-by-reference objects for user defined data structures. This simplifies programming by automatically managing memory allocation and deallocation in conjunction with automated garbage collection. This simplification of programming comes at the cost of performance. Using pass-by-reference objects instead of lighter weight pass-by value structs can have memory impact in some cases. These costs can be critical when these application runs on limited resource environments such as mobile devices and cloud computing systems. We explore the problem by using the simple and uniform memory model to improve the performance. In this work we address this problem by providing an automated and sounds static conversion analysis which identifies if a by reference type can be safely converted to a by value type where the conversion may result in performance improvements. This works focus on C# programs. Our approach is based on a combination of syntactic and semantic checks to identify classes that are safe to convert. We evaluate the effectiveness of our work in identifying convertible types and impact of this transformation. The result shows that the transformation of reference type to value type can have substantial performance impact in practice. In our case studies we optimize the performance in Barnes-Hut program which shows total memory allocation decreased by 93% and execution time also reduced by 15%.

The usefulness of Usability and User Experience evaluation methods on an e-Learning platform development from a developer's perspective: A case study

The development of a web platform is a complex and interdisciplinary task, where people with different roles such as project manager, designer or developer participate. Different usability and User Experience evaluation methods can be used in each stage of the development life cycle, but not all of them have the same influence in the software development and in the final product or system. This article presents the study of the impact of these methods applied in the context of an e-Learning platform development. The results show that the impact has been strong from a developer's perspective. Developer team members considered that usability and User Experience evaluation allowed them mainly to identify design mistakes, improve the platform's usability and understand the end users and their needs in a better way. Interviews with potential users, clickmaps and scrollmaps were rated as the most useful methods. Finally, these methods were considered unanimously very useful in the context of the entire software development, only comparable to SCRUM meetings and overcoming the rest of involved factors.

Developer incentives in Illinois tax increment districts.

"April 1988."

Co-creative expertise : Auran Games and Fury - a case study

This article discusses the ways in which the relations among professional and non-professional participants in co-creative relations are being reconfigured as part of the shift from a closed industrial paradigm of expertise toward open and distributed expertise networks. This article draws on ethnographic consultancy research undertaken throughout 2007 with Auran Games, a Brisbane, Australia based games developer, to explore the co-creative relationships between professional developers and gamers. This research followed and informed Auran’s online community management and social networking strategies for Fury (http://unleashthefury.com), a massively multiplayer online game released in October 2007. This paper argues that these co-creative forms of expertise involve co-ordinating expertises through social-network markets.

Sustainable suburbs : the developer’s challenge

As our cities expand, developers are transforming more and more land to create our suburbs of the future. Developers and government bodies have a golden opportunity to design suburbs that are not only great places to live, but also are environmentally sensitive and sustainable. This is a unique opportunity, as significant changes after development are constrained by the configuration of the subdivision, and then by the construction of the dwellings. This paper explores some of these issues by presenting initial findings from the CRCCI, Sustainable Subdivisions Project. The Project examines the drivers and barriers that land developers face when trying to achieve sustainable subdivisions. This paper will review the results from a series of industry interviews and workshops and explore possible ways forward. In addition, the possible effect on the way future land subdivision is managed and planned as a result of recent changes in the energy efficiency provisions of the Building Code of Australia will be explored. This paper highlights problems that both builders and land developers may face through poor subdivision design. Finally an innovative program being driven by a major land developer will be introduced. The program aims to deliver over 400 energy and water efficient homes through a series of compulsory and voluntary schemes that the developer is designing, funding and implementing. This program is the first large-scale development in Australia that demonstrates how developers can help achieve environmentally sensitive and sustainable suburbs of the future.