Reconciliation of object interaction models

This paper presents Reconciliation+, a tool-supported method which identifies overlaps between models of different object interactions expressed as UML sequence and/or collaboration diagrams, checks whether the overlapping elements of these models satisfy specific consistency rules, and guides developers in handling these inconsistencies. The method also keeps track of the decisions made and the actions taken in the process of managing inconsistencies

Supporting the reconciliation of models of object behaviour

This paper presents Reconciliation+, a method which identifies overlaps between models of software systems behaviour expressed as UML object interaction diagrams (i.e., sequence and/or collaboration diagrams), checks whether the overlapping elements of these models satisfy specific consistency rules and, in cases where they violate these rules, guides software designers in handling the detected inconsistencies. The method detects overlaps between object interaction diagrams by using a probabilistic message matching algorithm that has been developed for this purpose. The guidance to software designers on when to check for inconsistencies and how to deal with them is delivered by enacting a built-in process model that specifies the consistency rules that can be checked against overlapping models and different ways of handling violations of these rules. Reconciliation+ is supported by a toolkit. It has also been evaluated in a case study. This case study has produced positive results which are discussed in the paper

Identifying Conflicting Requirements in Systems of Systems

A System of Systems (SoS) is an arrangement of useful and independent sub-systems, which are integrated into a larger system. Examples are found in transport systems, nutritional systems, smart homes and smart cities. The composition of component sub-systems into an SoS enables support for complex functionalities that cannot be provided by individual sub-systems on their own. However, to realize the benefits of these functionalities it is necessary to address several software engineering challenges including, but not limited to, the specification, design, construction, deployment, and management of an SoS. The various component sub-systems in an SoS environment are often concerned with distinct domains; are developed by different stake-holders under different circumstances and time; provide distinct functionalities; and are used by different stakeholders, which allow for the existence of conflicting requirements. In this paper, we present a framework to support management of emerging conflicting requirements in an SoS. In particular, we describe an approach to support identification of conflicts between resource-based requirements (i.e. requirements concerned with the consumption of different resources). In order to illustrate and evaluate the work, we use an example of a pilot study of an IoT SoS ecosystem designed to support food security at different levels of granularity, namely individuals, groups, cities, and nations

Human resource allocation to multiple projects based on members’ expertise, group heterogeneity and social cohesion

Project managers regularly allocate human resources to construction projects. This critical task is usually executed by fulfilling the minimum project staffing requirements normally based around the quantity and competence of project members. However, research has shown that team performance can increase by up to 10% and 18%, respectively, as a consequence of the group members’ heterogeneity and social cohesion. Also, there is currently no practical quantitative tool which incorporates these aspects to allow project managers to achieve this task efficiently and objectively. A new quantitative model for the effective allocation of human resources to multiple projects, which takes into account group heterogeneity and social cohesion is proposed. This model is easy to build, update and use in real project environments with the use of a spreadsheet and a basic optimization engine (e.g. Excel Solver). A case study is proposed and solved with a Genetic Algorithm to illustrate the model implementation. Finally, a validation example is provided to exemplify how group heterogeneity and social cohesion condition academic achievement in an academic setting

The optimisation of a strategic business process

The optimisation of a Tendering Process for Warship Refit Contracts is presented. The Pre Contract Award process (PCA) involves all the activities needed to successfully win a Refit Contract, e.g. estimating, planning, tendering and negotiation. Process activities and information flows have been modelled using Integrated computer aided manufacturing DEFinition methodology (IDEF0) and a Design Structure Matrix (DSM) with optimisation performed via a Genetic Algorithm (DSM-GA) search technique [1]. The aim of the DSM-GA is to provide the user with an enhanced sequence of performing process activities. A new process was extracted from the optimised solution, showing an improved sequence with reduced iteration and planned activity concurrency based on carefully considered information requirements. This is of practical benefit to enhance understanding and to provide a guide to implementation. The approach suggests an enhanced sequence of process activities, based on information requirements, and can lead to improved business practice. This Paper discusses the potential benefits and limitations of this approach in a practical setting

Organizing the Technical Debt Landscape

To date, several methods and tools for detecting source code and design anomalies have been developed. While each method focuses on identifying certain classes of source code anomalies that potentially relate to technical debt (TD), the overlaps and gaps among these classes and TD have not been rigorously demonstrated. We propose to construct a seminal technical debt landscape as a way to visualize and organize research on the subjec

Academic Cloud Computing Research: Five Pitfalls and Five Opportunities

This discussion paper argues that there are five fundamental pitfalls, which can restrict academics from conducting cloud computing research at the infrastructure level, which is currently where the vast majority of academic research lies. Instead academics should be conducting higher risk research, in order to gain understanding and open up entirely new areas. We call for a renewed mindset and argue that academic research should focus less upon physical infrastructure and embrace the abstractions provided by clouds through five opportunities: user driven research, new programming models, PaaS environments, and improved tools to support elasticity and large-scale debugging. The objective of this paper is to foster discussion, and to define a roadmap forward, which will allow academia to make longer-term impacts to the cloud computing community.Comment: Accepted and presented at the 6th USENIX Workshop on Hot Topics in Cloud Computing (HotCloud'14

Formal specification of human-computer interfaces

A high-level formal specification of a human computer interface is described. Previous work is reviewed and the ASLAN specification language is described. Top-level specifications written in ASLAN for a library and a multiwindow interface are discussed