21,280 research outputs found
A framework for decision making on teleexpertise with traceability of the reasoning
This paper provides a methodological framework for decision making process to ensure its traceability generally in the context of telemedicine and particularly in the act of teleexpertise. This act permits to medical professionals and/or health professionals to collaborate in order to take suitable decisions for a patient diagnosis or treatment. The main problem dealing with teleexpertise is the following: How to ensure the traceability of the decisions making process? This problem is solved in this paper through a conceptualisation of a rigorous framework coupling semantic modelling and explicit reasoning which permits to fully support the analysis and rationale for decisions made. The logical semantic underlying this framework is the argumentative logicto provide adequate management of information with traceability of the reasoning including options and constraints. Thus our proposal will permit to formally ensure the traceability of reasoning in telemedicine and particularly in teleexpertise in order to favour the quality of telemedicine’s procedure checking. This traceability is to guarantee equitable access to the benefits of the collective knowledge and experience and to provide remote collaborative practices with a sufficient safety margin to guard against the legal requirements. An illustrative case study is provided by the modelling of a decision making process applied to teleexpertise for chronic diseases such as diabetes mellitus type2
Benefits of traceability in software development
PhD ThesisFor an engineer to be able to modify successfully a complex computer-based
system, he will need to understand the system's functionality. Traceability can
help the engineer to gain that understanding, but several surveys have observed
that traceability information is poorly recorded. This thesis argues, based on a
survey of nine aerospace projects, that one of the main causes of poor recording is
that Traceability does not directly benefit the development process. The recording
of traceability information is best performed by the engineers directly involved in
the development process, yet it is precisely these engineers who seem to obtain no
direct benefit in performing this task. This can be summarised as the Traceability
Benefit Problem. To overcome this problem the recording of traceability data
must provide immediate, tangible benefits to the engineers involved in the current
development process.
A related problem that occurs in large multi-team projects that follow
development processes based on predictive models (such as Waterfall or VModel)
is the changing of interface documentation without adequate negotiation
(referred to as Throwing the Problem over the Wall). This thesis describes, in
detail, how a small automotive sensor project addressed these problems by
developing a Requirements Traceability system that enabled the reuse of software
and provided a basis for the negotiation of changes with their customer. Analysis
of the lessons learnt from the automotive sensor and aerospace projects lead to the
definition of the Traceable Development Contract.
The contribution of this thesis is the description and discussion of the Traceable
Development Contract, a method of coordinating the interaction of related
development teams in development process that is based on a predictive
development model. The Traceable Development Contract is proposed as a means
of controlling the upstream team bias with respect to the imposition of changes,
by employing traceability to provide a basis for the negotiation of change. By
VI
employing traceability in this way, it becomes beneficial to the development
engineers and therefore overcomes the Traceability Benefit Problem.
Finally, the thesis considers how the Traceable Development Contract traceability
information can be exploited further to provide solution maturity and design
metrics
Extended requirements traceability: results of an industrial case study
Contribution structures offer a way to model the network of people who have participated in the requirements engineering process. They further provide the opportunity to extend conventional forms of artifact-based requirements traceability with the traceability of contributing personnel. In this paper, we describe a case study that investigated the modeling and use of contribution structures in an industrial project. In particular, we demonstrate how they made it possible to answer previously unanswerable questions about the human source(s) of requirements. In so doing, we argue that this information addresses problems currently attributed to inadequate requirements traceability
Requirements traceability in model-driven development: Applying model and transformation conformance
The variety of design artifacts (models) produced in a model-driven design process results in an intricate relationship between requirements and the various models. This paper proposes a methodological framework that simplifies management of this relationship, which helps in assessing the quality of models, realizations and transformation specifications. Our framework is a basis for understanding requirements traceability in model-driven development, as well as for the design of tools that support requirements traceability in model-driven development processes. We propose a notion of conformance between application models which reduces the effort needed for assessment activities. We discuss how this notion of conformance can be integrated with model transformations
- …