Team-oriented process programming

Team-oriented process programming promises to provide significant support for the planning, directing, and controlling of software engineering projects. In this paper we apply process programming to software engineering teams and show how this can provide powerful new capabilities for the management of software projects. We identify key issues which must be addressed to apply process programming to teams, and present our vision for team-oriented process programming

Rapid prototyping and fast user trial of multimedia broadcast and cellular services

This paper presents the results of fast user trial of multimedia services that are enabled when a mobile terminal has access to converged services over digital broadcast and mobile telecommunications networks. It first describes the motivations behind developing this system and describes the service scenarios that benefit most from it. It then provides an overview of the service components of the test case scenario. Finally, it presents the results of fast user trials on end users of the services that were developed. This work was conducted as part of the EU-funded CISMUNDUS project

Requirements for building information modeling based lean production management systems for construction

Smooth flow of production in construction is hampered by disparity between individual trade teams' goals and the goals of stable production flow for the project as a whole. This is exacerbated by the difficulty of visualizing the flow of work in a construction project. While the addresses some of the issues in Building information modeling provides a powerful platform for visualizing work flow in control systems that also enable pull flow and deeper collaboration between teams on and off site. The requirements for implementation of a BIM-enabled pull flow construction management software system based on the Last Planner System™, called ‘KanBIM’, have been specified, and a set of functional mock-ups of the proposed system has been implemented and evaluated in a series of three focus group workshops. The requirements cover the areas of maintenance of work flow stability, enabling negotiation and commitment between teams, lean production planning with sophisticated pull flow control, and effective communication and visualization of flow. The evaluation results show that the system holds the potential to improve work flow and reduce waste by providing both process and product visualization at the work face

Enabling Data-Driven Transportation Safety Improvements in Rural Alaska

Safety improvements require funding. A clear need must be demonstrated to secure funding. For transportation safety, data, especially data about past crashes, is the usual method of demonstrating need. However, in rural locations, such data is often not available, or is not in a form amenable to use in funding applications. This research aids rural entities, often federally recognized tribes and small villages acquire data needed for funding applications. Two aspects of work product are the development of a traffic counting application for an iPad or similar device, and a review of the data requirements of the major transportation funding agencies. The traffic-counting app, UAF Traffic, demonstrated its ability to count traffic and turning movements for cars and trucks, as well as ATVs, snow machines, pedestrians, bicycles, and dog sleds. The review of the major agencies demonstrated that all the likely funders would accept qualitative data and Road Safety Audits. However, quantitative data, if it was available, was helpful

Culture in the design of mHealth UI:An effort to increase acceptance among culturally specific groups

Purpose: Designers of mobile applications have long understood the importance of users’ preferences in making the user experience easier, convenient and therefore valuable. The cultural aspects of groups of users are among the key features of users’ design preferences, because each group’s preferences depend on various features that are culturally compatible. The process of integrating culture into the design of a system has always been an important ingredient for effective and interactive human computer interface. This study aims to investigate the design of a mobile health (mHealth) application user interface (UI) based on Arabic culture. It was argued that integrating certain cultural values of specific groups of users into the design of UI would increase their acceptance of the technology. Design/methodology/approach: A total of 135 users responded to an online survey about their acceptance of a culturally designed mHealth. Findings: The findings showed that culturally based language, colours, layout and images had a significant relationship with users’ behavioural intention to use the culturally based mHealth UI. Research limitations/implications: First, the sample and the data collected of this study were restricted to Arab users and Arab culture; therefore, the results cannot be generalized to other cultures and users. Second, the adapted unified theory of acceptance and use of technology model was used in this study instead of the new version, which may expose new perceptions. Third, the cultural aspects of UI design in this study were limited to the images, colours, language and layout. Practical implications: It encourages UI designers to implement the relevant cultural aspects while developing mobile applications. Originality/value: Embedding Arab cultural aspects in designing UI for mobile applications to satisfy Arab users and enhance their acceptance toward using mobile applications, which will reflect positively on their lives.</p

Counterfactual Explanations without Opening the Black Box: Automated Decisions and the GDPR

There has been much discussion of the right to explanation in the EU General Data Protection Regulation, and its existence, merits, and disadvantages. Implementing a right to explanation that opens the black box of algorithmic decision-making faces major legal and technical barriers. Explaining the functionality of complex algorithmic decision-making systems and their rationale in specific cases is a technically challenging problem. Some explanations may offer little meaningful information to data subjects, raising questions around their value. Explanations of automated decisions need not hinge on the general public understanding how algorithmic systems function. Even though such interpretability is of great importance and should be pursued, explanations can, in principle, be offered without opening the black box. Looking at explanations as a means to help a data subject act rather than merely understand, one could gauge the scope and content of explanations according to the specific goal or action they are intended to support. From the perspective of individuals affected by automated decision-making, we propose three aims for explanations: (1) to inform and help the individual understand why a particular decision was reached, (2) to provide grounds to contest the decision if the outcome is undesired, and (3) to understand what would need to change in order to receive a desired result in the future, based on the current decision-making model. We assess how each of these goals finds support in the GDPR. We suggest data controllers should offer a particular type of explanation, unconditional counterfactual explanations, to support these three aims. These counterfactual explanations describe the smallest change to the world that can be made to obtain a desirable outcome, or to arrive at the closest possible world, without needing to explain the internal logic of the system