An Exploratory Study of Forces and Frictions affecting Large-Scale Model-Driven Development

In this paper, we investigate model-driven engineering, reporting on an exploratory case-study conducted at a large automotive company. The study consisted of interviews with 20 engineers and managers working in different roles. We found that, in the context of a large organization, contextual forces dominate the cognitive issues of using model-driven technology. The four forces we identified that are likely independent of the particular abstractions chosen as the basis of software development are the need for diffing in software product lines, the needs for problem-specific languages and types, the need for live modeling in exploratory activities, and the need for point-to-point traceability between artifacts. We also identified triggers of accidental complexity, which we refer to as points of friction introduced by languages and tools. Examples of the friction points identified are insufficient support for model diffing, point-to-point traceability, and model changes at runtime.Comment: To appear in proceedings of MODELS 2012, LNCS Springe

Improving root cause analysis through the integration of PLM systems with cross supply chain maintenance data

The purpose of this paper is to demonstrate a system architecture for integrating Product Lifecycle Management (PLM) systems with cross supply chain maintenance information to support root-cause analysis. By integrating product-data from PLM systems with warranty claims, vehicle diagnostics and technical publications, engineers were able to improve the root-cause analysis and close the information gaps. Data collection was achieved via in-depth semi-structured interviews and workshops with experts from the automotive sector. Unified Modelling Language (UML) diagrams were used to design the system architecture proposed. A user scenario is also presented to demonstrate the functionality of the system

Grand Challenges of Traceability: The Next Ten Years

In 2007, the software and systems traceability community met at the first Natural Bridge symposium on the Grand Challenges of Traceability to establish and address research goals for achieving effective, trustworthy, and ubiquitous traceability. Ten years later, in 2017, the community came together to evaluate a decade of progress towards achieving these goals. These proceedings document some of that progress. They include a series of short position papers, representing current work in the community organized across four process axes of traceability practice. The sessions covered topics from Trace Strategizing, Trace Link Creation and Evolution, Trace Link Usage, real-world applications of Traceability, and Traceability Datasets and benchmarks. Two breakout groups focused on the importance of creating and sharing traceability datasets within the research community, and discussed challenges related to the adoption of tracing techniques in industrial practice. Members of the research community are engaged in many active, ongoing, and impactful research projects. Our hope is that ten years from now we will be able to look back at a productive decade of research and claim that we have achieved the overarching Grand Challenge of Traceability, which seeks for traceability to be always present, built into the engineering process, and for it to have "effectively disappeared without a trace". We hope that others will see the potential that traceability has for empowering software and systems engineers to develop higher-quality products at increasing levels of complexity and scale, and that they will join the active community of Software and Systems traceability researchers as we move forward into the next decade of research

The Stores Model of Code Cognition

Program comprehension is perhaps one of the oldest topics within the psychology of programming. It addresses a central issue: how programmers work with and manipulate source code to construct effective software systems. Models can play an important role in understanding the challenges developers and engineers contend with. This paper presents a model of program comprehension, or code cognition, which has been derived from literature found within the disciplines of computing and psychology. Drawing on direct experimentation, this paper argues that a model of code cognition should take account of the visual, spatial and linguistic abilities of developers. The strengths and weaknesses of this model are discussed and further research directions presented

A systematic approach for monitoring and evaluating the construction project progress

A persistent problem in construction is to document changes which occur in the field and to prepare the as-built schedule. In current practice, deviations from planned performance can only be reported after significant time has elapsed and manual monitoring of the construction activities are costly and error prone. Availability of advanced portable computing, multimedia and wireless communication allows, even encourages fundamental changes in many jobsite processes. However a recent investigation indicated that there is a lack of systematic and automated evaluation and monitoring in construction projects. The aim of this study is to identifytechniques that can be used in the construction industry for monitoring and evaluating the physical progress, and also to establish how current computer technology can be utilised for monitoring the actual physical progress at the construction site. This study discusses the results of questionnaire survey conducted within Malaysian Construction Industry and suggests a prototype system, namely Digitalising Construction Monitoring (DCM). DCM prototype system integrates the information from construction drawings, digital images of construction site progress and planned schedule of work. Using emerging technologies and information system the DCM re-engineer the traditional practice for monitoring the project progress. This system can automatically interpret CAD drawings of buildings and extract data on its structural components and store in database. It can also extract the engineering information from digital images and when these two databases are simulated the percentage of progress can be calculated and viewed in Microsoft Project automatically. The application of DCM system for monitoring the project progress enables project management teams to better track and controls the productivity and quality of construction projects. The use of the DCM can help resident engineer, construction manager and site engineer in monitoring and evaluating project performance. This model will improve decision-making process and provides better mechanism for advanced project management