Build Notifications in Agile Environments

In an agile software development environment, developers write code that should work together to fulfill the wishes of the customer. Continuous integration (CI) ensures that code from different individuals integrates properly. CI compiles the entire codebase, deploys and tests it with each change. CI alerts developers of any problems as errors can be fixed more easily if caught earlier in the process. This paper compares the effectiveness of different types of mechanisms for notifying developers to a successful or unsuccessful build. Two different quantitative and qualitative user studies were performed testing the effectiveness of three types of notification devices one virtual e-mail based mechanism, one using ambient lava lamps, and one robotic device. The results show that most developers preferred an easily visible but unobtrusive ambient device combined with an e-mail describing the problem in more detail.We are currently acquiring citations for the work deposited into this collection. We recognize the distribution rights of this item may have been assigned to another entity, other than the author(s) of the work.If you can provide the citation for this work or you think you own the distribution rights to this work please contact the Institutional Repository Administrator at [email protected]

Service Monitoring for a Mobile Money System

Mobile applications are gaining more and more market share and virtually everyone today has smartphones. This reality is no different in Africa, where the use of mobile payment systems has grown and allowed people without access to bank accounts to use their phones to perform banking operations. Currently, WIT Software provides these countries with a Mobile Money System solution providing a Backend and Mobile Application, that allows users to make and receive payments, lend money and pay into mortgages, check statements, and transactions’ history. Still, another important aspect is the availability and functionality so that users can use it without interruption. In this way, was proposed to design a monitoring platform that will allow users to perceive the health status of the total system from the users' side, to detect problems either in applications, servers or even in network components that may be running. Prevent the correct functioning of this system that allows millions of people to have their bank account associated with their mobile phone number. This report describes all the work carried out for nine months at the company WIT Software, which involves the design and implementation of a Monitoring Platform for a Mobile Payments System

A framework for selecting workflow tools in the context of composite information systems

When an organization faces the need of integrating some workflow-related activities in its information system, it becomes necessary to have at hand some well-defined informational model to be used as a framework for determining the selection criteria onto which the requirements of the organization can be mapped. Some proposals exist that provide such a framework, remarkably the WfMC reference model, but they are designed to be appl icable when workflow tools are selected independently from other software, and departing from a set of well-known requirements. Often this is not the case: workflow facilities are needed as a part of the procurement of a larger, composite information syste m and therefore the general goals of the system have to be analyzed, assigned to its individual components and further detailed. We propose in this paper the MULTSEC method in charge of analyzing the initial goals of the system, determining the types of components that form the system architecture, building quality models for each type and then mapping the goals into detailed requirements which can be measured using quality criteria. We develop in some detail the quality model (compliant with the ISO/IEC 9126-1 quality standard) for the workflow type of tools; we show how the quality model can be used to refine and clarify the requirements in order to guarantee a highly reliable selection result; and we use it to evaluate two particular workflow solutions a- ailable in the market (kept anonymous in the paper). We develop our proposal using a particular selection experience we have recently been involved in, namely the procurement of a document management subsystem to be integrated in an academic data management information system for our university.Peer ReviewedPostprint (author's final draft

Towards an institutional PLE

PLEs in their broader sense (the ad-hoc, serendipitous and potentially chaotic set of tools that learners bring to their learning) are increasingly important for learners in the context of formal study. In this paper we outline the approach that we are taking at the University of Southampton in redesigning our teaching and learning infrastructure into an Institutional PLE. We do not see this term as an oxymoron. We define an Institutional PLE as an environment that provides a personalised interface to University data and services and at the same time exposes that data and services to a student’s personal tools. Our goal is to provide a digital platform that can cope with an evolving learning and teaching environment, as well as support the social and community aspects of the institution

Proceedings of International Workshop "Global Computing: Programming Environments, Languages, Security and Analysis of Systems"

According to the IST/ FET proactive initiative on GLOBAL COMPUTING, the goal is to obtain techniques (models, frameworks, methods, algorithms) for constructing systems that are flexible, dependable, secure, robust and efficient. The dominant concerns are not those of representing and manipulating data efficiently but rather those of handling the co-ordination and interaction, security, reliability, robustness, failure modes, and control of risk of the entities in the system and the overall design, description and performance of the system itself. Completely different paradigms of computer science may have to be developed to tackle these issues effectively. The research should concentrate on systems having the following characteristics: • The systems are composed of autonomous computational entities where activity is not centrally controlled, either because global control is impossible or impractical, or because the entities are created or controlled by different owners. • The computational entities are mobile, due to the movement of the physical platforms or by movement of the entity from one platform to another. • The configuration varies over time. For instance, the system is open to the introduction of new computational entities and likewise their deletion. The behaviour of the entities may vary over time. • The systems operate with incomplete information about the environment. For instance, information becomes rapidly out of date and mobility requires information about the environment to be discovered. The ultimate goal of the research action is to provide a solid scientific foundation for the design of such systems, and to lay the groundwork for achieving effective principles for building and analysing such systems. This workshop covers the aspects related to languages and programming environments as well as analysis of systems and resources involving 9 projects (AGILE , DART, DEGAS , MIKADO, MRG, MYTHS, PEPITO, PROFUNDIS, SECURE) out of the 13 founded under the initiative. After an year from the start of the projects, the goal of the workshop is to fix the state of the art on the topics covered by the two clusters related to programming environments and analysis of systems as well as to devise strategies and new ideas to profitably continue the research effort towards the overall objective of the initiative. We acknowledge the Dipartimento di Informatica and Tlc of the University of Trento, the Comune di Rovereto, the project DEGAS for partially funding the event and the Events and Meetings Office of the University of Trento for the valuable collaboration

Agile Scalability Engineering: The ScrumScale Method

While agile methods have had a great uptake and impact in software engineering, managing non‑functional qualities still seems to be a challenge. We focus on the scalability of software systems and how this critical quality can be managed and controlled, while still benefiting from the advantages of an agile process. Scalability is a property of a system that must be carefully designed in to avoid potential disastrous behavior when load and work fluctuate. Through a collaboration with and a case study at the largest Norwegian public portal operator, Altinn, we have proposed and tested additions to the Scrum process framework. With our approach named ScrumScale, scalability concerns may be identified and related to user stories. The roles in a Scrum project can collaborate without adding more ceremony than strictly necessary. The paper provides an overview of the ScrumScale method and lessons learned from Altinn.publishedVersio