29,229 research outputs found
Safety-Critical Systems and Agile Development: A Mapping Study
In the last decades, agile methods had a huge impact on how software is
developed. In many cases, this has led to significant benefits, such as quality
and speed of software deliveries to customers. However, safety-critical systems
have widely been dismissed from benefiting from agile methods. Products that
include safety critical aspects are therefore faced with a situation in which
the development of safety-critical parts can significantly limit the potential
speed-up through agile methods, for the full product, but also in the
non-safety critical parts. For such products, the ability to develop
safety-critical software in an agile way will generate a competitive advantage.
In order to enable future research in this important area, we present in this
paper a mapping of the current state of practice based on {a mixed method
approach}. Starting from a workshop with experts from six large Swedish product
development companies we develop a lens for our analysis. We then present a
systematic mapping study on safety-critical systems and agile development
through this lens in order to map potential benefits, challenges, and solution
candidates for guiding future research.Comment: Accepted at Euromicro Conf. on Software Engineering and Advanced
Applications 2018, Prague, Czech Republi
Process of designing robust, dependable, safe and secure software for medical devices: Point of care testing device as a case study
This article has been made available through the Brunel Open Access Publishing Fund.Copyright © 2013 Sivanesan Tulasidas et al. This paper presents a holistic methodology for the design of medical device software, which encompasses of a new way of eliciting requirements, system design process, security design guideline, cloud architecture design, combinatorial testing process and agile project management. The paper uses point of care diagnostics as a case study where the software and hardware must be robust, reliable to provide accurate diagnosis of diseases. As software and software intensive systems are becoming increasingly complex, the impact of failures can lead to significant property damage, or damage to the environment. Within the medical diagnostic device software domain such failures can result in misdiagnosis leading to clinical complications and in some cases death. Software faults can arise due to the interaction among the software, the hardware, third party software and the operating environment. Unanticipated environmental changes and latent coding errors lead to operation faults despite of the fact that usually a significant effort has been expended in the design, verification and validation of the software system. It is becoming increasingly more apparent that one needs to adopt different approaches, which will guarantee that a complex software system meets all safety, security, and reliability requirements, in addition to complying with standards such as IEC 62304. There are many initiatives taken to develop safety and security critical systems, at different development phases and in different contexts, ranging from infrastructure design to device design. Different approaches are implemented to design error free software for safety critical systems. By adopting the strategies and processes presented in this paper one can overcome the challenges in developing error free software for medical devices (or safety critical systems).Brunel Open Access Publishing Fund
Rethinking Security Incident Response: The Integration of Agile Principles
In today's globally networked environment, information security incidents can
inflict staggering financial losses on organizations. Industry reports indicate
that fundamental problems exist with the application of current linear
plan-driven security incident response approaches being applied in many
organizations. Researchers argue that traditional approaches value containment
and eradication over incident learning. While previous security incident
response research focused on best practice development, linear plan-driven
approaches and the technical aspects of security incident response, very little
research investigates the integration of agile principles and practices into
the security incident response process. This paper proposes that the
integration of disciplined agile principles and practices into the security
incident response process is a practical solution to strengthening an
organization's security incident response posture.Comment: Paper presented at the 20th Americas Conference on Information
Systems (AMCIS 2014), Savannah, Georgi
Psychological Safety and Norm Clarity in Software Engineering Teams
In the software engineering industry today, companies primarily conduct their
work in teams. To increase organizational productivity, it is thus crucial to
know the factors that affect team effectiveness. Two team-related concepts that
have gained prominence lately are psychological safety and team norms. Still,
few studies exist that explore these in a software engineering context.
Therefore, with the aim of extending the knowledge of these concepts, we
examined if psychological safety and team norm clarity associate positively
with software developers' self-assessed team performance and job satisfaction,
two important elements of effectiveness.
We collected industry survey data from practitioners (N = 217) in 38
development teams working for five different organizations. The result of
multiple linear regression analyses indicates that both psychological safety
and team norm clarity predict team members' self-assessed performance and job
satisfaction. The findings also suggest that clarity of norms is a stronger
(30\% and 71\% stronger, respectively) predictor than psychological safety.
This research highlights the need to examine, in more detail, the
relationship between social norms and software development. The findings of
this study could serve as an empirical baseline for such, future work.Comment: Submitted to CHASE'201
Why and How Your Traceability Should Evolve: Insights from an Automotive Supplier
Traceability is a key enabler of various activities in automotive software
and systems engineering and required by several standards. However, most
existing traceability management approaches do not consider that traceability
is situated in constantly changing development contexts involving multiple
stakeholders. Together with an automotive supplier, we analyzed how technology,
business, and organizational factors raise the need for flexible traceability.
We present how traceability can be evolved in the development lifecycle, from
early elicitation of traceability needs to the implementation of mature
traceability strategies. Moreover, we shed light on how traceability can be
managed flexibly within an agile team and more formally when crossing team
borders and organizational borders. Based on these insights, we present
requirements for flexible tool solutions, supporting varying levels of data
quality, change propagation, versioning, and organizational traceability.Comment: 9 pages, 3 figures, accepted in IEEE Softwar
Boundary Objects and their Use in Agile Systems Engineering
Agile methods are increasingly introduced in automotive companies in the
attempt to become more efficient and flexible in the system development. The
adoption of agile practices influences communication between stakeholders, but
also makes companies rethink the management of artifacts and documentation like
requirements, safety compliance documents, and architecture models.
Practitioners aim to reduce irrelevant documentation, but face a lack of
guidance to determine what artifacts are needed and how they should be managed.
This paper presents artifacts, challenges, guidelines, and practices for the
continuous management of systems engineering artifacts in automotive based on a
theoretical and empirical understanding of the topic. In collaboration with 53
practitioners from six automotive companies, we conducted a design-science
study involving interviews, a questionnaire, focus groups, and practical data
analysis of a systems engineering tool. The guidelines suggest the distinction
between artifacts that are shared among different actors in a company (boundary
objects) and those that are used within a team (locally relevant artifacts). We
propose an analysis approach to identify boundary objects and three practices
to manage systems engineering artifacts in industry
Cyber physical systems implementation for asset management improvement: A framework for the transition
Libro en Open AccessThe transformation of the industry due to recent technologies introduction is an evolving
process whose engines are competitiveness and sustainability, understood in its broadest sense (environmental,
economic and social). This process is facing, due to the current state of scientific and technological
development, a new challenge yet even more important: the transition from discrete technological solutions
that respond to isolated problems, to a global conception where the assets, plant, processes and engineering
systems are conceived, designed and operated as an integrated complex unit. This vision is evolving
besides a set of concepts that are, in some way, to guide this development: Smart Factories, Cyber-Physical
Systems, Factory of the Future or Industry 4.0, are examples. The full integration of the operation and
maintenance (O&M) processes in the production systems is a key topic within this new paradigm. Not
only that, this evolution necessarily results in the emergence of new processes and needs of O&M, i.e.
also, the O&M will undergo a profound transformation. The transition from actual isolated production
assets to such Industry 4.0 with CPS is far from easy. This document presents a proposal to develop such
transition adapting one iteration of the Model of Maintenance Management (MMM) integrated into
ISO 55000 to the complexity of incorporating âSystem of Systemsâ CPSs maintenance. It involves several
stages: identification, prioritization, risk management, planning, scheduling, execution, control, and
improvement supported by system engineering techniques and agile/concurrent project managemen
- âŠ