Search

Blockchain technology promises to spark a real revolution. One of most important concepts associated with this technology is smart contracts, which enable the automatic execution of agreements and augur a world without intermediaries. The conditions and rules of “contracts” are established in a computer codes and trust is enforced by consensus among the participants. One relevant feature associated with smart contract is the immutability property, which establishes the non-alteration of blockchain network data after the clauses of the contract are been approved by all parties or entities involved. For this reason, smart contract development requires more effort and care than the development of other common programs. They require systematic mechanisms to collect requirements and functional specifications. In addition, it is necessary to verify and validate the agreed functionality and the implemented code before they are deployed in the blockchain platform. This article presents a systematic literature review of primary studies in the field of Software Development Life Cycle, focusing on model-based software design and testing in the blockchain domain of smart contracts. This research aims to identify gaps and/or opportunities for further research. After carried out this review, it was observed that no clear methodology exists for evaluating and validating the quality either of this software or the overall development process. This means that software developers may implement smart contract code in which bugs and serious security vulnerabilities appear when the software is delivered to their customers.

The use of smart contract augurs a world without intermediaries because the code and the agreements contained therein exist across a distributed, decentralized blockchain network. In software engineering, this collaboration is usually represented by using business process models and smart contracts can be used to implement business collaborations in general and inter-organizational business processes. The validation of this contract and the assurance of its quality are critical for its right application. Early testing in smart contract definition is the fact of this paper. The paper discusses the possibility to use transformation protocols to obtain derived artefacts like test case definitions and smart contract code scaffolds. Generation of derived artefacts significantly reduces the number of defects before deploying the smart contract code in the blockchain network. Transformations protocols are created using model-based software development and modelling techniques. This approach allows to simplify and improve the management and execution of collaborative business processes. This would allow, in addition, the application of systematic mechanisms to evaluate and validate the smart contract and, particularly, the application of early testing techniques which would help to reduce the number of defects and, ultimately, the cost of the final review.

Business process management (BPM) is a strategic advantage for all kinds of organizations, including information technology companies (ITCs), which cannot stay out of the BPM approach. ITCs manage business processes like projects to create and maintain software. Although Project Management Systems (PMSs), such as Microsoft™ Project Server® (MPS®), are considered as non-process-aware information systems (Non-PAISs), they may be a source to generate processes. In this paper, we propose a reverse engineering approach, which uses patterns to transform software projects stored in MPS® legacy databases into software business processes. For this, we base on the model-driven engineering paradigm and deal with the time perspective of the processes. &is kind of experiences are scarce or almost nonexistent, so we show the AQUA-WS project case study, which runs with MPS® as source system and software process modeling languages as target systems. ITCs can benefit from this research by gathering knowledge about perspectives of their processes that would otherwise be wasted, such as executed projects or expired documents used in Non-PAISs. &is fact can become a key factor for ITCs, which can increase their competitiveness and reduce software costs, as part of the BPM lifecycle of continuous improvement. Ministerio de Economía y Competitividad TIN2016-76956-C3-2-R

GUI is one of the key aspect of an information system from the pointof view of customers and users. This paper introduces PLEC, a par-ticipative process for designing GUI interfaces with the collaborationof the final users and stakeholders. Participants do not need technicalknowledge of GUI prototype. A case study has been developed andcarried out to verify if PLEC process is feasible. 2019-20

We present an approach for early testing based on the Model-Driven paradigm.We offer the view of a tool for solve this problem.We present some real experiences where this approach was offered. Test phase is one of the most critical phases in software engineering life cycle to assure the final system quality. In this context, functional system test cases verify that the system under test fulfills its functional specification. Thus, these test cases are frequently designed from the different scenarios and alternatives depicted in functional requirements. The objective of this paper is to introduce a systematic process based on the Model-Driven paradigm to automate the generation of functional test cases from functional requirements. For this aim, a set of metamodels and transformations and also a specific language domain to use them is presented. The paper finishes stating learned lessons from the trenches as well as relevant future work and conclusions that draw new research lines in the test cases generation context. Display Omitted

Testing in Software Engineering is one of the most important phases although, unfortunately, it cannot be always successfully fulfilled due to time constraints. In most cases, the development phase takes more time than it was estimated, entailing negative effects on the testing phase. The delay increases even more in Research and Development (R + D) projects, where the real time to execute tasks is more difficult to control. Model Driven Engineering (MDE) offers a solution to avoid testing costs without affecting the execution quality of the applied test. This paper presents a practical overview of a Model Driven Testing (MDT)-based methodology and its impact on CALIPSOneo project, which was carried out in liaison with Airbus Defense and Space and, particularly, with the Product Lifecycle Management (PLM) department.

Despite the fact that the test phase is described in the literature as one of the most relevant for quality assurance in software projects, this test phase is not usually developed, among others, with enough resources, time or suitable techniques. To offer solutions which supply the test phase, with appropriate tools for the automation of tests generation, or even, for their self-execution, could become a suitable way to improve this phase and reduce the cost constraints in real projects. This paper focuses on answering a concrete research question: is it possible to generate test cases from functional requirements described in an informal way? For this aim, it presents an overview of a set of relevant approaches that works in this field and offers a set of comparative analysis to determine which the state of the art is.

The response over time of the QT interval and the Transmural Dispersion of Repolarization (TDR) to Isoproterenol infusion (ISO) in an 85 year-old-man with severe and syntomatic bradycardia, in the setting of an Amiodarone-induced Long QT Syndrome (LQTS) is the subject of this communication. ISO shortened the QT and decreased the TDR. We propose that ISO increased the generation of signals from the β-Adrenergic Receptor (β-AR) restoring the components of the hKCNQ1 macromolecular complex, thereby enhancing the I Ks function; shortening of the QT interval, reduction of the TDR and normalization of the T wave morphology was then possible. In Amiodarone-induced LQTS, the increase in I Ks activity promoted by β-AR stimulation is prominent; at the same time, during I Kr block, I Ks activation limits excessive QT prolongation. Clinically, severe and syntomatic bradycardia was the main concern: ISO activation of the β-AR proved useful both to increase heart rate and to reduce QT prolongation. A slow heart rate, associated to a prolonged QT interval and to a big TDR, are not sufficient to develop Torsades de Pointes in Amiodarone-induced LQTS.

We describe full exposure of an acquired Long QT Syndrome (aLQTS) in an elderly female patient on long-term Amiodarone treatment. We propose that the aLQTS is the result of combined block of the rapid (I Kr ) and delayed (I Ks ) components of the outward potassium current (I K ), translated to the ECG in a (more than expected) prolonged QT interval, an augmented transmural dispersion of repolarization (TDR) and an interrupted T wave. The unequal regression of repolarization lengthening made possible to individualize I K current components in the inscription of the interrupted T wave, which argues against the U wave as a separate entity. Silent ion channel gene mutations or polymorphisms and downregulation of β-adrenergic activation of I Ks may underlie the unusual repolarization behaviour. The unequal regression over time of Amiodarone-induced repolarization lengthening could have clinical significance.

This paper aims at giving a global vision of the most popular web engineering approach. Web systems have woken up a high interest in companies and in the research community in the last years. Thus, techniques and methods are being proposed in order to offer a suitable framework to deal with the special characteristics of the web. For these reasons, some years ago a new line in the software engineering appeared. This line, then named web engineering, has grown in the last years, proving that web systems have special characteristics that require a special treatment. One of the most treated characteristic is the navigation. Navigation is a critical aspect in web systems and its suitable development in the life cycle is a basic need to guarantee the project quality. This survey shows how navigation is treated in 15 web proposals, which are the most referenced ones, and it analyses the available techniques, models and the possible gaps in the treatment.

The acquired Long QT Syndrome (aLQTS) is attributed to subtle defects in genes encoding potassium currents (Ik) that may become clinically significant when associated with other factors that impair ventricular repolarization, such as female gender, bradycardia, hypokalemia or the administration of ion channel blocking drugs. We describe full exposure of an aLQTS in a elderly female patient on long-term Risperidone treatment just when bradycardia due to complete AV block developed. We postulate that the aLQTS induced is the result of a combined block of the rapid (I(Kr))and delayed (I(Ks)) components of the Ik current. The electrocardiographic manifestation of (likely) phase 2 early afterdepolarizations and a critical transmural dispersion of repolarization (TDR), both required for the initiation and maintenance of the polymorphic ventricular tachycardia associated with the syndrome (Torsades de Pointes), are as well shown. Risperidone should be used with caution in female patients prone to bradycardia.

The Holter recording in an elderly female patient on Risperidone treatment who developed a longer than expected prolonged QT interval and associated torsades de pointes (TdP) at the onset of complete AV block is presented. The electrocardiographic manifestation of (likely) phase 2 early afterdepolarizations (EAD) as a trigger of TdP episodes; the TdP undulating or monomorphic morphologies as a counterpart of drifting or stationery scrolls, respectively, and the TdP final extinction leading to asystole and death are shown.

The model-driven development defi nes the software development process as a set of iterations to create models and a set of transformations to obtain new models. From this point of view, this paper presents the enhancement of a model- driven approach, called navigational development techniques (NDT), by means of new models and transformations in order to generate test cases. It also states some conclusions from the research work and practical cases in which this approach was used. Ministerio de Ciencia e Innovación TIN2010-20057-C03-02 Ministerio de Ciencia e Innovación TIN 2010-12312-E

Model-driven web engineering (MDWE) is a new paradigm which provides satisfactory results in the development of web software systems. However, as can be concluded from several research works, MDWE provokes traceability problems and the necessity of managing constraints in metamodel instances and transformation executions. The management of these aspects is usually executed manually in the most of MDWE approaches. Nevertheless, model-driven paradigm itself can offer suitable ways to manage them. This chapter presents NDT-Quality, an approach to measure the quality of web projects developed with NDT (navigational development techniques), and offers a view about the application of this tool in real web projects. Ministerio de Educación y Ciencia TIN2007-67843-C06-03 Ministerio de Educación y Ciencia TIN2007-30391-E

Model-Driven Web Engineering (MDWE) is a new paradigm which provides satisfactory results in software development. However, most experiments with MDWE towards the development of software from the requirements to the implementation stages. However, in practice, sometimes software development does not follow this classic path. In this paper, MDWE is presented as a suitable selection in software projects of technological evolution. The AQUA project is a very large and important project which is a fusion of three previous systems. Thus, this project starts with the original code of these three systems. The paper introduces the power of MDWE in this kind of systems.

The test phase is one of the most important phases in software development. However, in practice, little research has been carried out in this field. Model-Driven Engineering is a new paradigm that can help to minimize test cases generation costs and can ensure quality of results. This paper presents the application of the MDE paradigm in the systematic, even automatic, generation of System Test Software.

The application of a model-driven paradigm in the development of Web Systems has yielded very good research results. Several research groups are defining metamodels, transformations, and tools which offer a suitable environment, known as model-driven Web engineering (MDWE). However, there are very few practical experiences in real Web system developments using real development teams. This chapter presents a practical environment of MDWE based on the use of NDT (navigational development techniques) and Java Web systems, and it provides a practical evaluation of its application within a real project: specialized Diraya. Ministerio de Educación y Ciencia TIN2007-67843-C06-03 Ministerio de Educación y Ciencia TIN2007-30391-E

The verification of the correct implementation of use cases is a vital task in software development and quality assurance. Although there are many works describing how to generate test cases from use cases, there are very few case studies and empirical results of their application and effectiveness. This paper introduces a first case study that test the correct implementation of use cases in a web system and a command line system, analyses the results and exposes that generation of use cases has a successful about 80%.

The process of testing software system is gaining more importance every day [6]. Software applications are growing in size and complexity quickly. It makes more necessary to dispose techniques to assure quality of the systems and that the result satisfied initial specifications [1].

*´ ˜˜ ´ Patients with coronary artery disease without an- B), Lp(a), LDL cholesterol (LDL) and total corrected giographic coronary atherosclerosis have a good cholesterol (TCC) were analysed after patients had prognosis [1‐3]. Fournier et al. found that young fasted for more than 12 hours. patients with myocardial infarction have good prog- Differences were found in the levels of HDL: nosis irrespective of the coronary anatomie, although 3269 mg / dl in abnormal coronariography compared patients with normal coronary angiograms had less with 38610 mg / dl in normal coronariography (p, risk factors and less frequent new ischaemic events 0.05); Lp(a): 37 mg / dl (16‐65) compared with 12 [1]. However other studies [2] found no differences mg / dl (6‐34) (p50.006); TG: 152 mg / dl (124‐209) in coronary risk factors between patients with compared with 115 mg / dl (95‐184) (p,0.05). No myocardial infarction and normal coronary arteries differences were found in the levels of Apo AI, Apo and those with acute myocardial infarction and B, Tchol, LDL and TCC nor in the prevalence of coronary arterial lesions. hypertension, diabetes and smoking habits. We conTo determine common characteristics of patients clude that patients with early-onset coronary disease under 50 years of age with coronary disease and under the age of 50 years and with normal normal coronariography a group of 230 male patients coronariography present a more favourable lipid before 50 years of age (mean age 4365 years), who profile with higher levels of HDL and lower levels of were admitted to our Coronary Care Unit as result of TG and Lp(a) than those patients with the same an episode of coronary disease, were prospectively characteristics and with coronary stenosis shown on studied. Cardiac catheterism was made in 140 pa- coronariography. tients, and normal coronariography was seen in 13 of these. Smoking habits, arterial hypertension, diabetes and dyslipemia were determined during the acute References phase by means of a questionnaire, physical examen and fasting analysis. Levels of Total cholesterol [1] Fournier JA, Sanchez-Gonzalez A, Quero J, Cortacero JA, Cabello A, Revello A. Normal angiogram after myocardial infarction in (Tchol), HDL cholesterol (HDL), triglycerides (TG)

A vital task of software development is to test the correct implementation of functional requirements. Use cases are widely used artefacts that define the functionality of a software system in early stages of the development process. This paper exposes the lack of automatism in existing approaches that deal with the derivation of test cases, and introduces a new approach and tool to derive systematically test objectives from the use cases of the system under test.