Requirements engineering: a review and research agenda

This paper reviews the area of requirements engineering. It outlines the key concerns to which attention should be devoted by both practitioners, who wish to "reengineer" their development processes, and academics, seeking intellectual challenges. It presents an assessment of the state-of-the-art and draws conclusions in the form of a research agenda

The Instrumental Genesis of Collective Activity. The Case of an ERP Implementation in a Large Electricity Producer

Collective activity should be a focal subject to study organizational dynamics, particularly in relation with the implementation of management systems such as ERPs. Collective activity is analyzed here as an ongoing dialogical construction by actors. It is always mediated by signs and particularly by instruments. To design and adapt collective activity, a reflexive dialogical exchange between actors, a “collective activity about collective activity”, mediated by instruments, is necessary: we call it “the instrumental genesis of collective activity”. We analyze the case of an ERP implementation at EDF, a large electricity company, in the purchase and procurement area of the production division. The design and implementation of the new system was not clearly viewed as the instrumental genesis of collective activity. Difficulties appeared particularly for cross-functional cooperation and for the construction of new professional profiles of competence. In the light of this case, we suggest that key conditions for the intelligibility and the actionability of collective activity are the establishment of communities and the hybridization of professional competences.Collective Activity; Collective Sensemaking; Community; Dialogical; ERP; Instruments; Instrumental Genesis of Activity; Interpretation; Sign

Stylistic Creativity in the Utilization of Management Tools

We analyze the role of management instruments in the development of collective activity and in the dynamics of organization, recurring to pragmatic and semiotic theories. In dualist representation-based theories (rationalism, cognitivism), instruments are seen as symbolic reflections of situations, which enable actors to translate their complex concrete activities into computable models. In interpretation-based theories (pragmatism, theory of activity, situated cognition), instruments are viewed as signs interpreted by actors to make sense of their collective activity, in an ongoing and situated manner. Instruments combine objective artefacts and interpretive schemes of utilization. They constrain interpretation and utilization, but do not completely determine them: they define genus (generic classes) of collective activity, but they leave space for individual or local interpretive schemes and stylistic creation in using them. A major part of organizational dynamics takes place in the permanent interplay between instrumental genus and styles. Whereas representation-based theories can be acceptable approximations in stable and reasonably simple organizational settings, interpretation-based theories make uncertain and complex situations more intelligible. They view emotions and creativity as a key part of the interpretive process, rather than as external biases of a rational modelling process. For future research, we wish to study how interpretation-based theories should impact managerial practices and improve, not only intelligibility, but also actionability of instruments and situations.Collective Activity; Genus; Instruments; Interpretation; Management Instruments; Performance Management; Pragmatism; Semiotics; Style

Instrumenting gait with an accelerometer: A system and algorithm examination

Gait is an important clinical assessment tool since changes in gait may reflect changes in general health. Measurement of gait is a complex process which has been restricted to the laboratory until relatively recently. The application of an inexpensive body worn sensor with appropriate gait algorithms (BWM) is an attractive alternative and offers the potential to assess gait in any setting. In this study we investigated the use of a low-cost BWM, compared to laboratory reference using a robust testing protocol in both younger and older adults. We observed that the BWM is a valid tool for estimating total step count and mean spatio-temporal gait characteristics however agreement for variability and asymmetry results was poor. We conducted a detailed investigation to explain the poor agreement between systems and determined it was due to inherent differences between the systems rather than inability of the sensor to measure the gait characteristics. The results highlight caution in the choice of reference system for validation studies. The BWM used in this study has the potential to gather longitudinal (real-world) spatio-temporal gait data that could be readily used in large lifestyle-based intervention studies, but further refinement of the algorithm(s) is required

Instrumenting gait with an accelerometer: A system and algorithm examination

Gait is an important clinical assessment tool since changes in gait may reflect changes in general health. Measurement of gait is a complex process which has been restricted to the laboratory until relatively recently. The application of an inexpensive body worn sensor with appropriate gait algorithms (BWM) is an attractive alternative and offers the potential to assess gait in any setting. In this study we investigated the use of a low-cost BWM, compared to laboratory reference using a robust testing protocol in both younger and older adults. We observed that the BWM is a valid tool for estimating total step count and mean spatio-temporal gait characteristics however agreement for variability and asymmetry results was poor. We conducted a detailed investigation to explain the poor agreement between systems and determined it was due to inherent differences between the systems rather than inability of the sensor to measure the gait characteristics. The results highlight caution in the choice of reference system for validation studies. The BWM used in this study has the potential to gather longitudinal (real-world) spatio-temporal gait data that could be readily used in large lifestyle-based intervention studies, but further refinement of the algorithm(s) is required

Detecting and Refactoring Operational Smells within the Domain Name System

The Domain Name System (DNS) is one of the most important components of the Internet infrastructure. DNS relies on a delegation-based architecture, where resolution of names to their IP addresses requires resolving the names of the servers responsible for those names. The recursive structures of the inter dependencies that exist between name servers associated with each zone are called dependency graphs. System administrators' operational decisions have far reaching effects on the DNSs qualities. They need to be soundly made to create a balance between the availability, security and resilience of the system. We utilize dependency graphs to identify, detect and catalogue operational bad smells. Our method deals with smells on a high-level of abstraction using a consistent taxonomy and reusable vocabulary, defined by a DNS Operational Model. The method will be used to build a diagnostic advisory tool that will detect configuration changes that might decrease the robustness or security posture of domain names before they become into production.Comment: In Proceedings GaM 2015, arXiv:1504.0244

Industrially Applicable System Regression Test Prioritization in Production Automation

When changes are performed on an automated production system (aPS), new faults can be accidentally introduced in the system, which are called regressions. A common method for finding these faults is regression testing. In most cases, this regression testing process is performed under high time pressure and on-site in a very uncomfortable environment. Until now, there is no automated support for finding and prioritizing system test cases regarding the fully integrated aPS that are suitable for finding regressions. Thus, the testing technician has to rely on personal intuition and experience, possibly choosing an inappropriate order of test cases, finding regressions at a very late stage of the test run. Using a suitable prioritization, this iterative process of finding and fixing regressions can be streamlined and a lot of time can be saved by executing test cases likely to identify new regressions earlier. Thus, an approach is presented in this paper that uses previously acquired runtime data from past test executions and performs a change identification and impact analysis to prioritize test cases that have a high probability to unveil regressions caused by side effects of a system change. The approach was developed in cooperation with reputable industrial partners active in the field of aPS engineering, ensuring a development in line with industrial requirements. An industrial case study and an expert evaluation were performed, showing promising results.Comment: 13 pages, https://ieeexplore.ieee.org/abstract/document/8320514

The development of a program analysis environment for Ada

A unit level, Ada software module testing system, called Query Utility Environment for Software Testing of Ada (QUEST/Ada), is described. The project calls for the design and development of a prototype system. QUEST/Ada design began with a definition of the overall system structure and a description of component dependencies. The project team was divided into three groups to resolve the preliminary designs of the parser/scanner: the test data generator, and the test coverage analyzer. The Phase 1 report is a working document from which the system documentation will evolve. It provides history, a guide to report sections, a literature review, the definition of the system structure and high level interfaces, descriptions of the prototype scope, the three major components, and the plan for the remainder of the project. The appendices include specifications, statistics, two papers derived from the current research, a preliminary users' manual, and the proposal and work plan for Phase 2

Software Engineers' Information Seeking Behavior in Change Impact Analysis - An Interview Study

Software engineers working in large projects must navigate complex information landscapes. Change Impact Analysis (CIA) is a task that relies on engineers' successful information seeking in databases storing, e.g., source code, requirements, design descriptions, and test case specifications. Several previous approaches to support information seeking are task-specific, thus understanding engineers' seeking behavior in specific tasks is fundamental. We present an industrial case study on how engineers seek information in CIA, with a particular focus on traceability and development artifacts that are not source code. We show that engineers have different information seeking behavior, and that some do not consider traceability particularly useful when conducting CIA. Furthermore, we observe a tendency for engineers to prefer less rigid types of support rather than formal approaches, i.e., engineers value support that allows flexibility in how to practically conduct CIA. Finally, due to diverse information seeking behavior, we argue that future CIA support should embrace individual preferences to identify change impact by empowering several seeking alternatives, including searching, browsing, and tracing.Comment: Accepted for publication in the proceedings of the 25th International Conference on Program Comprehensio