Captura de requisitos de sistemas de información a partir de procesos de negocio y metas

Esta tesis presenta una aproximación para la captura de los requisitos de un sistema de información para una organización a partir de sus procesos de negocio y las metas del sistema. Además, la aproximación facilita la comunicación entre los analistas de sistema y los stakeholders, y posibilita el alineamiento estratégico de una organización.De La Vara González, JL. (2008). Captura de requisitos de sistemas de información a partir de procesos de negocio y metas. http://hdl.handle.net/10251/12450Archivo delegad

Analysis of requirements quality evolution

Proceedings of: 40th International Conference on Software Engineering in Gothenburg, Sweden, May 27 - June 03, 2018A fundamental aspect in the requirements engineering process is to know the quality of a specification, including how the quality evolves over time. This paper introduces an industrial approach for analysis of requirements quality evolution. The approach has been implemented in the System Quality Analyzer tool, exploits quality metrics for requirements correctness, consistency, and completeness, and is based on the storage of quality information in snapshots that are combined and displayed in charts. This can help practitioners to assess the progress and status of a requirements engineering process and to make decisions.The AMASS project (H2020-ECSEL grant agreement no 692474; Spain's MINECO ref. PCIN-2015-262) has funded this work

Do Models Improve the Understanding of Safety Compliance Needs?: Insights from a Pilot Experiment

Context. Many critical systems must meet safety compliance needs from safety standards. These standards are usually large textual documents whose compliance needs can be hard to understand. As a solution, the use of models has been proposed. Goal. We aim to provide evidence of the extent to which models improve the understanding of safety compliance needs. Method. We designed an experiment and ran a pilot to study the effectiveness, efficiency, and perceived benefits of understanding these needs, with the text of standards and with models in the form of UML object diagrams. Results. The overall results from 15 Bachelor students show that the effectiveness of understanding safety compliance needs increases very little with models (2%), and the efficiency even decreases (24%). Nonetheless, the results improve when the potential complexity in navigating the models is taken into account (15% effectiveness increase). The students find benefits in using the models but most consider that the models are hard to understand. Conclusions. The extent to which models improve the understanding of safety compliance needs seems to be lower than what the research community expects. New studies are necessary to confirm our initial insights.European CommissionThe research leading to this paper has received funding from the AMASS project (H2020-ECSEL grant agreement no 692474; Spain’s MINECO ref. PCIN-2015-262) and the AMoDDI project (Ref. 11130583)

Towards Effective SysML Model Reuse

The Systems Modeling Language (SysML) is spreading very fast. Most modelling tool vendors support it and practitioners have adopted it for Systems Engineering. The number of SysML models is growing, increasing the need for and the potential benefit from platforms that allow a user to reuse the knowledge represented in the models. However, SysML model reuse remains challenging. Each tool has its own implementation of SysML, hindering reuse between tools. The search capabilities of most tools are also very limited and finding reusable models can be difficult. This paper presents our vision and initial work towards enabling an effective reuse of the knowledge contained in SysML models. The proposed solution is based on a universal information representation model called RSHP and on existing technology for indexing and retrieval. The solution has been used to index models of all SysML diagram types and preliminary validated with requirements diagrams. The results from the validation show that the solution has very high precision and recall. This makes us confident that the solution can be a suitable means for effective SysML model reuse.European CommissionThe research leading to this paper has received funding from the AMASS project (H2020-ECSEL grant agreement no 692474; Spain's MINECO ref. PCIN-2015-262)

An analysis of safety evidence management with the Structured Assurance Case Metamodel

SACM (Structured Assurance Case Metamodel) it a standard for assurance case specification and exchange. It consists of an argumentation metamodel and an evidence metamodel for justifying that a system satisfies certain requirements. For assurance of safety-critical systems, SACM can be used to manage safety evidence and to specify safety cases. The standard is a promising initiative towards harmonizing and improving system assurance practices, but its suitability for safety evidence management needs to be further studied. To this end, this paper studies how SACM 1.1 supports this activity according to requirements from industry and from prior work. We have analysed the notion of evidence in SACM, its evidence lifecycle, the classes and associations of the evidence metamodel, and the link of this metamodel with the argumentation one. As a result, we have identified several improvement opportunities and extension possibilities in SACM

Variability management in process families through change patterns

© 2016. This manuscript version is made available under the CC-BY-NC-ND 4.0 license http://creativecommons.org/licenses/by-nc-nd/4.0/Context: The increasing adoption of process-aware information systems together with the high variability in business processes has resulted in collections of process families. These families correspond to a business process model and its variants, which can comprise hundreds or thousands of different ways of realizing this process. Managing process variability in this context can be very challenging, labor-intensive, and error-prone, and new approaches for managing process families are necessary. Objective: We aim to facilitate variability management in process families, ensure process family correctness, and reduce the effort needed for such purposes. Method: We have derived a set of change patterns for process families from variability-specific language constructs identified in the literature. For validation, we have conducted a case study with a safety standard in which we have measured the number of operations needed to model and evolve the variability of the standard with and without the patterns. Results: We present 10 change patterns for managing variability in process families and show how they can be implemented. The patterns support the modeling and evolution of process families and ensure process family correctness by automatically introducing and deleting modeling elements. The case study results show that the application of the defined change patterns can reduce the number of operations when modeling a process family by 34% and when evolving it by 40%. Conclusions: The application of the change patterns can help in effectively modeling and evolving large and highly-variable process families. Their application can also considerably reduce variability management effort. (C) 2016 Elsevier B.V. All rights reserved.This work has been developed with the financial support of Spanish Ministry of Economy and Competitiveness under the project SMART-ADAPT TIN2013-42981-P. We also want to thank Barbara Weber and Manfred Reichert for their valuable input and feedback on the design and development of the set of change patterns for process families.Ayora Esteras, C.; Torres Bosch, MV.; De La Vara González, JL.; Pelechano Ferragud, V. (2016). Variability management in process families through change patterns. Information and Software Technology. 74:86-104. https://doi.org/10.1016/j.infsof.2016.01.007S861047

Enabling system artefact exchange and selection through a linked data layer

The use of different techniques and tools is a common practice to cover all stages in the systems development lifecycle, generating a very good number of system artefacts. Moreover, these artefacts are commonly encoded in different formats and can only be accessed, in most cases, through proprietary and non-standard protocols. This scenario can be considered a real nightmare for software or systems reuse. Possible solutions imply the creation of a real collaborative development environment where tools can exchange and share data, information and knowledge. In this context, the OSLC (Open Services for Lifecycle Collaboration) initiative pursues the creation of public specifications (data shapes) to exchange any artefact generated during the development lifecycle, by applying the principles of the Linked Data initiative. In this paper, the authors present a solution to provide a real multi-format system artefact reuse by means of an OSLC-based specification to share and exchange any artefact under the principles of the Linked Data initiative. Finally, two experiments are conducted to demonstrate the advantages of enabling an input/output interface based on an OSLC implementation on top of an existing commercial tool (the Knowledge Manager). Thus, it is possible to enhance the representation and retrieval capabilities of system artefacts by considering the whole underlying knowledge graph generated by the different system artefacts and their relationships. After performing 45 different queries over logical and physical models stored in Papyrus, IBM Rhapsody and Simulink, results of precision and recall are promising showing average values between 70-80%.The research leading to these results has received funding from the AMASS project (H2020-ECSEL grant agreement no 692474; Spain's MINECO ref. PCIN-2015-262) and the CRYSTAL project (ARTEMIS FP7-CRitical sYSTem engineering AcceLeration project no 332830-CRYSTAL and the Spanish Ministry of Industry)

The AMASS approach for assurance and certification of critical systems

Safety-critical systems are subject to rigorous assurance and certification processes to guarantee that they do not pose unreasonable risks to people, property, or the environment. The associated activities are usually complex and time-consuming, thus they need adequate support for their execution. The activities are further becoming more challenging as the systems are evolving towards open, interconnected systems with new features, e.g. Internet connectivity, and new assurance needs, e.g. compliance with several assurance standards for different dependability attributes. This requires the development of novel approaches for cost-effective assurance and certification. With the overall goal of lowering assurance and certification costs in face of rapidly changing features and market needs, the AMASS project has created and consolidated the de-facto European-wide open solution for assurance and certification of critical systems. This has been achieved by establishing a novel holistic and reuse-oriented approach for architecture-driven assurance, multi-concern assurance, and for seamless interoperability between assurance and engineering activities along with third-party activities. This paper introduces the main elements of the AMASS approach and how to use them and benefit from them.The work leading to this paper has received funding from the AMASS project (H2020-ECSEL grant agreement no 692474; Spain’s MINECO ref. PCIN-2015-262)

Real-world effectiveness of caplacizumab vs the standard of care in immune thrombotic thrombocytopenic purpura

Immune thrombotic thrombocytopenic purpura (iTTP) is a thrombotic microangiopathy caused by anti-ADAMTS13 antibodies. Caplacizumab is approved for adults with an acute episode of iTTP in conjunction with plasma exchange (PEX) and immunosuppression. The objective of this study was to analyze and compare the safety and efficacy of caplacizumab vs the standard of care and assess the effect of the concomitant use of rituximab. A retrospective study from the Spanish TTP Registry of patients treated with caplacizumab vs those who did not receive it was conducted. A total of 155 patients with iTTP (77 caplacizumab, 78 no caplacizumab) were included. Patients initially treated with caplacizumab had fewer exacerbations (4.5% vs 20.5%; P <.05) and less refractoriness (4.5% vs 14.1%; P <.05) than those who were not treated. Time to clinical response was shorter when caplacizumab was used as initial treatment vs caplacizumab used after refractoriness or exacerbation. The multivariate analysis showed that its use in the first 3 days after PEX was associated with a lower number of PEX (odds ratio, 7.5; CI, 2.3-12.7; P <.05) and days of hospitalization (odds ratio, 11.2; CI, 5.6-16.9; P <.001) compared with standard therapy. There was no difference in time to clinical remission in patients treated with caplacizumab compared with the use of rituximab. No severe adverse event was described in the caplacizumab group. In summary, caplacizumab reduced exacerbations and refractoriness compared with standard of care regimens. When administered within the first 3 days after PEX, it also provided a faster clinical response, reducing hospitalization time and the need for PEX

Real-world effectiveness of caplacizumab vs the standard of care in immune thrombotic thrombocytopenic purpura

Immune thrombotic thrombocytopenic purpura (iTTP) is a thrombotic microangiopathy caused by anti-ADAMTS13 antibodies. Caplacizumab is approved for adults with an acute episode of iTTP in conjunction with plasma exchange (PEX) and immunosuppression. The objective of this study was to analyze and compare the safety and efficacy of caplacizumab vs the standard of care and assess the effect of the concomitant use of rituximab. A retrospective study from the Spanish TTP Registry of patients treated with caplacizumab vs those who did not receive it was conducted. A total of 155 patients with iTTP (77 caplacizumab, 78 no caplacizumab) were included. Patients initially treated with caplacizumab had fewer exacerbations (4.5% vs 20.5%; P < .05) and less refractoriness (4.5% vs 14.1%; P < .05) than those who were not treated. Time to clinical response was shorter when caplacizumab was used as initial treatment vs caplacizumab used after refractoriness or exacerbation. The multivariate analysis showed that its use in the first 3 days after PEX was associated with a lower number of PEX (odds ratio, 7.5; CI, 2.3-12.7; P < .05) and days of hospitalization (odds ratio, 11.2; CI, 5.6-16.9; P < .001) compared with standard therapy. There was no difference in time to clinical remission in patients treated with caplacizumab compared with the use of rituximab. No severe adverse event was described in the caplacizumab group. In summary, caplacizumab reduced exacerbations and refractoriness compared with standard of care regimens. When administered within the first 3 days after PEX, it also provided a faster clinical response, reducing hospitalization time and the need for PEX