Search

Digital data is increasingly important and becoming more prevalent in research. As such, a significant and growing fraction of that data is subject to complex security and privacy standards for its storage and processing. With the introduction of contractual requirements for NIST Special Publication 800-171 and other compliance frameworks, universities are under expanded pressure to secure research infrastructure to ensure their researchers comply with laws, regulations, and contractual requirements. The University of Florida developed tiCrypt, a bundled security middleware product, and implemented their ResVault system to meet the growing need for secure research infrastructure. The University of Maryland and Princeton University, both seeking to meet compliance requirements for secure research, have also implemented systems using tiCrypt. As new institutions adopt tiCrypt, the Tera Insights development team continues to add functionality to meet the needs of a broad range of research workflows.

To evaluate educational games, several techniques have been proposed considering different quality attributes. However, there are still several educational games for the mobile context that have low scores in the app stores. These stores allow users to make comments to evaluate the applications, as this data can be useful for the development team that aims to meet users' expectations. The analysis of comments made by users can help identify which attributes impact the use of mobile educational games. In this paper, an inspection checklist is proposed to evaluate mobile educational games. To complement the attributes identified in the analysis of comments, attributes from existing techniques for evaluating mobile educational games were also considered. The final evaluation form contains a total of 82 attributes distributed in evaluation categories, such as: user interface, mobility, pedagogy, gameplay, among others. To evaluate the proposed technique, an evaluation was carried out with the checklist in two mobile educational games available in the Google Play Store, different from those used to define the technique. The initial results indicate that the proposed checklist allows the identification of problems pointed out by users in the comments left in the app store.

Google provides Android Vitals, a set of reports and tools for Android Developers as part of Google Play Console. Android Vitals can help developers improve their Android apps after an app has been launched by providing information on how their app is performing in key areas such as battery use, performance, and stability (freezes and crashes). Android Vitals also provides various comparisons, including against global bad behavior thresholds, against various peer groups of apps, and across releases of this app. Developers confirm Android Vitals notifies them of relevant problems and they found it valuable even if they also use crash reporting and mobile analytics. The underlying data is used by Google to assess the relative quality of Android apps; and the perceived quality may materially affect the visibility of an app in the Google Play Store. Yet little is known about the tools. This paper outlines various experiences from the developers' perspective of using Android Vitals with several popular Android apps to help open discussions and suggest further research areas. It introduces an open source project, created as part of our work, that enables developers to download pertinent data, particularly crash reports. The data can be analysed both by the development team and others. A particular benefit of this tool is to make the data available outside of the Google platform, which allows developers and (indirectly) researchers to develop additional analysis techniques not currently provided by the platform.

Over the course of the last year Lexum has started exploring the potential of deep learning (DL) and machine learning (ML) technologies for legal research. Although these projects are still under the umbrella of Lexum's research and development team (Lexum Lab, https://lexum.com/en/ailab/), concrete applications have recently started to become available. This demo focuses on one of these applications: Facts2Law. The project benefits from a combination of factors. First, the millions of legal documents available in the CanLII database in parsable format along with structured metadata constitute a significant dataset to train AI algorithms. Second, Lexum has direct access to the knowledge and experience of one of the leading teams in AI and deep learning worldwide at the Montreal Institute for Learning Algorithms (MILA) of the University of Montreal. Third, the availability of computer engineers with cutting-edge expertise in the specifics of legal documents facilitates the transition from theory to practical applications. Regarding concrete outcomes, Lexum's Facts2Law can predict the most relevant sources of law for any given piece of text (incorporating legal citations or not).

As an industrial designer I have worked in collaboration with various researchers and scientists since the beginning of this century. I have made many prototypes showing the possibility of their leading edge technologies, and exhibited them in these years. As the archives of academic documents and papers have became open, and the internet gave public access to the recordings of various experiments being conducted throughout the world, technology in laboratories are now constantly exposed to the public. In this context, prototypes are becoming more important as the medium that bridges between advanced technology and society. Now a prototype is not merely an experimental machine. It is a device created to present user experience in advance, to share the benefits of the technology with many others. The role of a prototype is not limited to just sharing of values within the development team, but goes beyond that: it is a medium used to voice the significance of research and development to society; an inspiration to stimulate future markets; and also a tool to secure development budgets. A prototype is the physical embodiment of speculative story that connects people to technology that has yet to be brought to society. I would like to introduce some of the prototypes we developed and share the future vision they invoke.

Open-source software (OSS) often evolves from volunteer contributions, so OSS development teams must cooperate with their communities to attract new developers. However, in view of the myriad ways that developers interact over platforms for OSS development, observers of these communities may have trouble discerning, and thus learning from, the successful patterns of developer-to-team interactions that lead to eventual team acceptance. In this work, we study project communities on GitHub to discover which forms of software contribution characterize developers who begin as development team outsiders and eventually join the team, in contrast to developers who remain team outsiders. From this, we identify and compare the forms of contribution, such as pull requests and several forms of discussion comments, that influence whether new developers join OSS teams, and we discuss the implications that these behavioral patterns have for the focus of designers and educators.

Software ecosystems evolve through an active community of developers who contribute to projects within the ecosystem. However, development teams change over time, suggesting a potential impact on the evolution of the technical parts of the ecosystem. The impact of such modifications has been studied by previous works, but only temporary changes have been investigated, while the long-term effect of permanent changes has yet to be explored. In this paper, we investigate the evolution of the ecosystem of Ruby on Rails in GitHub in terms of such temporary and permanent changes of the development team. We use three viewpoints of the Rails ecosystem evolution to discuss our preliminary findings: (1) the base project; (2) the forks; and (3) the entire ecosystem containing both base project and forks.

Prior to developing learning games, it is useful for game developers to assess similar games. This process is addressed through the immersion component in the Pre-Development Phase of the Learning Games Design Model. This paper describes a more structured approach to the immersion component used by one development team to analyze early algebra games, offering a framework to discuss and analyze such games. The game development team reviewed more than 20 algebra games to identify effective design components and used to inform development of a new game and related tools. Through this process, which serves to enhance the existing Learning Games Design Model, the team was able to articulate their theoretical framework for future development, identifying specific recommendations that should yield effective games.

In this paper, we describe the practical considerations and challenges of studying an agile, co-located software development community by assimilating among them over many months. We have adopted a fully immersive ethnographic approach using semistructured and unstructured interviews. In many ways, the design choices in our study mirrored those faced by the development team, as we adjusted our methods on the fly to accommodate our richer knowledge of the work environment and adapted to changes on the ground. We share our process of determining and adjusting an operating procedure for the ethnographic observation and we reflect on the challenges faced in choosing subjects to study, getting them on board, planning questions and conducting interviews without disrupting the regular process of software development.

Examining work activity patterns is a problem of enduring research in organizations. The fortuitous availability of a whole new set of data collection mechanisms such as mobiles, activity loggers, GPS based location detectors, provide us new ways of studying workplace behaviour. We present a data collection framework that helps in collection, anonymization, fusion, processing and mining of behavioural data. We use the framework to study the activities in a research and development team with an aim to find the relationship between behavioural traits, states, and activity patterns. We find partial support for the claim that behavioral states and activity patterns are associated.

In this paper we introduce Mokap, a novel authoring and development toolset for serious games. Mokap aims to address two specific challenges: provide support for early development stage design and facilitate involvement of domain experts. More specifically, on the one hand, it aims to make serious game authoring possible for people with no technical background. On the other hand, Mokap provides explicit support for activities related to analysis and design, especially useful during the early stages of development. In this sense, Mokap aims to facilitate the transition from the designers' board to the programmers' environment and also to enhance communication between the different roles of the development team. Developed as an open source environment, Mokap is oriented to mobile devices (tablets and smartphones), a kind of technology most educational stakeholders are familiar with. We present the main design concepts behind Mokap, along with some technical insight into the platform and the description of the game Listen With Lemur as a case study.

In this paper we discuss the implementation of UNICORE in XSEDE. UNICORE is a Grid middleware tool that was identified by XSEDE to further the areas of remote job submission, campus bridging and workflows. We talk about the overall architecture of UNICORE, a typical HPC environment at XSEDE and why UNICORE is a good fit for this environment. We also discuss the initial efforts made by the UNICORE development team as well as XSEDE's Software development team to integrate UNICORE into the XSEDE landscape. We detail how UNICORE went through the XSEDE engineering process and highlight deployment details at XSEDE. We touch upon how UNICORE is beneficial to the HPC user community. In our final section we talk about future efforts to better integrate UNICORE within XSEDE.

In corporations where the focus is a very dynamic business inserted in web environments, agile methods can fully meet almost all needs. However, in some particular companies, there are multiple stakeholders, who represent different interests in prioritizing activities. There is, consequently, a heavy challenge to implement agile methodologies which deal with such conflicts in order to prioritize the features of the system. It is important to focus on higher earned value as possible and consider the technical risks exposed by the development team. These barriers often lead these companies to abandon such agile methods, incorporating an approach of a chaotic work environment. This paper proposes an agile technique for prioritizing features in environments with multiple stakeholders and reports a successful experience in its usage.

Intelligent Tutoring Systems are software applications capable of complementing and enhancing the learning process by providing direct customized instruction and feedback to students in various disciplines. Although Intelligent Tutoring Systems could differ widely in their attached knowledge bases and user interfaces (including interaction mechanisms), their behaviors are quite similar. Therefore, it must be possible to establish a common software model for them. A common software model is a step forward to move these systems from proof-of-concepts and academic research tools to widely available tools in schools and homes. The work reported here addresses: (1) the use of Design Patterns to create an object-oriented software model for Intelligent Tutoring Systems; (2) our experience using this model in a three-year development project and its impact on facets such as creating a common language among stakeholders, supporting an incremental development, and adjustment to a highly shifting development team; and (3) the qualities achieved and trade-offs made.

A flexible cooperative task board for supporting daily scrum meetings is described as an application of different hypermedia domains. In addition, change structure is introduced as a means to explicitly model changes in task management. It helps the scrum development team in a sprint retrospective to improve their planning.

How do individual HCI-practitioners evaluate their own work practice? And how would they like to evaluate it? Answers to these questions will give new knowledge on the state-of-the-practice in this area, and provide insight for researchers trying to improve practitioners' ability to evaluate their development project activities. The questions were investigated through questionnaire survey responses of 179 HCI-practitioners from the Nordic countries. It was found that the general maturity for evaluation of own practice were fairly high. However, the results indicate that HCI-practitioners tend not to evaluate their practice with regard to its impact on the development team and project leader; which may be counter productive to the downstream utility of HCI activities. Presentation of ongoing development of evaluation procedures, based on the results, will be included in the talk at NordiCHI 2006.

This report describes some characteristics of the development team of PostgreSQL that were uncovered by analyzing the history of its software artifacts as recorded by the project's CVS repository.

This Report discusses how a web-based application development project adopted XP and passed its first ISO audit. The practitioners report will consist of background material, a discussion of XP-friendly practices that the development team adopted, a discussion of how ISO-friendly practices were incorporated, and a summary of the results of the ISO audit.

Digital web-accessible annotations are a compelling medium for personal comments and shared discussions around documents. Only recently supported by widely used products, "in-context" digital annotation is a relatively unexamined phenomenon. This paper presents a case study of annotations created by members of a large development team using Microsoft Office 2000-approximately 450 people created 9,000 shared annotations on about 1,250 documents over 10 months. We present quantitative data on use, supported by interviews with users, identifying strengths and weaknesses of the existing capabilities and possibilities for improvement.