Search

Blockchain technology has gained significant prominence in the business world. Its impact has been felt in many sectors, but its integration and interoperability remain complex. Many challenges remain, both for users and business consultants, as well as for IT engineers. One of the challenges identified by the research community is the need to provide mechanisms to specify, verify and validate the requirements and business rules that smart contracts must comply with before they can be deployed in a blockchain network. This paper describes a proposal, based on model-driven and useroriented engineering, that aims to obtain functional verification from smart contract specifications in a systematic way. This proposal has been validated in the SmartISBN project, an R+D+i project whose objectives included ensuring the software quality of smart contracts and, above all, improving the traceability of digital publishing (electronic books and journals) using blockchain technology. In this context, this proposal has facilitated the communication between functional experts (authors, publishers, booksellers, etc.) and IT engineers during the specification phase of the global SmartISBN solution and in particular of the smart contracts, as well as during the definition of the functional tests necessary for the validation of the project. [ABSTRACT FROM AUTHOR]

Copyright of Revista Cubana de Ciencias Informáticas is the property of Universidad de las Ciencias Informaticas (UCI) and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

Copyright of Revista Cubana de Ciencias Informáticas is the property of Universidad de las Ciencias Informaticas (UCI) and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

Copyright of Avances is the property of Instituto de Informacion Cientifica y Tecnologica and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

This paper presents a proposal for assigning priorities to test cases in agile development environments. Through mathematical methods, a function is obtained to calculate the priority of the test cases of the software projects and their relationship with the phases of the project development life cycle. The defined function is based on four indicators whose information is possible to obtain in each of the project's iterations. A case study is also presented that allows comparing the results of ordering of the test cases, according to the priority with their effectiveness for the detection of potential errors and get expected result. [ABSTRACT FROM AUTHOR]

Copyright of Revista Colombiana de Investigaciones Agroindustriales is the property of Revista Colombiana de Investigaciones Agroindustriales del Centro Agropecuario Sena Buga and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

An activity of vital importance in software testing is the design and creation of effective test cases associated with adequate generation of test values, because empirical tests can't guarantee detection of all errors and the exhaustive testing is very costly in time and effort. Therefore, the strategy is try to make the tests the most inclusive possible to consider a subset of possible cases and test values most likely to detect errors. In this context, the need arises for using test case design techniques for the automatic generation of test cases, which ensure high levels of error coverage. This paper presents a component that generates automatically, values for unit testing, using design techniques Loops and Conditions. [ABSTRACT FROM AUTHOR]

The outsourcing of software testing is a current trend and enables organizations to reduce costs, time and improve the quality of process and product. Testing Factories using reference models have applied this principle. These models are not defined as an organizational model and are not aimed at increasing efficiency in the execution of software tests. In this paper is presented the basis of a new organizational model for Testing Factories, formed by the integration of the custom perspectives of the Balanced Scorecard, the disciplines of Intelligent Organizations and international quality standards. It defines a fifth perspective, considering the characteristics of the organization. The proposal was validated from its application in the test laboratory of the National Centre for Software Quality, showing increase in testing efficiency for four years of work. [ABSTRACT FROM AUTHOR]

Test Driven Development (TDD) is one of the most referenced agile practices, however, one of the least used in the industry. In this paper TDD it is considered like an imaginary medical pill, and its effects are described from a pharmacological point of view instead of providing a formal systematic review report. It invites the reader to imagine the rest of this document is a piece of medical information for TDD pill, and continue reading with the following question in mind: if TDD out a pill, would accept to improve my health? [ABSTRACT FROM AUTHOR]

Copyright of Revista Cubana de Ciencias Informáticas is the property of Universidad de las Ciencias Informaticas (UCI) and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

This paper describes the design of a computational tool for software test documentation. The tool manages documents as the master plan test; level plans, cases and procedures test; anomalies report and test reports, which are part of a proper documentation of software testing. Using package and use cases diagrams the functionality available in the tool is described, which has been designed from the IEEE 829 Standard. [ABSTRACT FROM AUTHOR]

One of the central problems of current economic development and industrial competitiveness, social and scientific, is the complexity of large and intensive software systems, and processes for their development and implementation. This complexity is defined by the amount and heterogeneity of the interaction of the hardware with the software components, their inter-relationships, of incorporation of the technical and organizational environments, and the interfaces to humans. The domain of these systems requires actions and scientific thoughts, hierarchical and systematic; also, the success of the products, services and organizations, is increasingly determined by the availability of suitable software products. Therefore, highly qualified professionals, able to understand and master the systems, involved in the entire life cycle of software engineering, and adopt different roles during the development. This is the reason that guide the thinking of this Manifesto, which aims is to achieve the Professionalization of Software Development. [ABSTRACT FROM AUTHOR]

The evaluation of software products will reach full maturity when executed by the scheme and provides third party certification. For the validity of the certification, the independent laboratory must be accredited for that function, using internationally recognized standards. This brings with it a challenge for the Industrial Laboratory Testing Software (LIPS), responsible for testing the products developed in Cuban Software Industry, define strategies that will permit it to offer services with a high level of quality. Therefore it is necessary to establish a system of quality management according to NC-ISO/IEC 17025: 2006 to continuously improve the operational capacity and technical competence of the laboratory, with a view to future accreditation of tests performed. This article discusses the process defined in the LIPS for the implementation of a Management System of Quality, from the current standards and trends, as a necessary step to opt for the accreditation of the tests performed. [ABSTRACT FROM AUTHOR]

The article is associated with the creation of a usability lab where various types of tests performed using static and dynamic tools for evaluating the characteristics of usability, accessibility and Communicability by indicators in the software testing process with the user's presence. It also addresses the current situation in Cuba on the issue of evidence of these characteristics and the impact it could bring to the development teams. In addition, an analysis of the result of applying a tool (check list) to multiple Web applications on tests conducted at the National Center for Software Quality Cuba (CALISOFT). We also present a set of best practices that support the development of web applications to suit the user. [ABSTRACT FROM AUTHOR]

Needs about security are matters little taken into account when managing requirements engineering, and when considered in the life cycle of the system, they tend to become a general list of functions, as password of protection, firewalls, virus detection tools, and other similar. But in fact, they cannot be considered as requirements of security, because they are implementation mechanisms to try to meet unspecified requirements, as an authenticated access. As a result, the security requirements for the system are ignored, which are required to protect essential services and assets, besides, when are specified, is not considered the prospect of future attacks. This paper describes the need for a systematic approach to managing security requirements engineering, in order to help avoid the problem of generic lists and take into account the future perspective. Several related approaches are described and also are provided references additional material that can help requirements engineers to ensure that their products be taken into account, effectively, the security requirements. [ABSTRACT FROM AUTHOR]

Copyright of Revista Virtual Universidad Católica del Norte is the property of Revista Virtual Universidad Catolica del Norte and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

Software testing probably is the least understood part of the software testing life cycle. In this work, by means of a methodological proposal of four stages, is showed why is complex the process of carrying out the testing software, why is necessary to pay it more attention and why is so difficult to detect and delete the mistakes. [ABSTRACT FROM AUTHOR]

This reflexion paper aims at discussing a number of issues that typically arise when performing empirical studies with software testing techniques. Though some problems are general to all empirical disciplines, software testing studies face a number of specific challenges. Some of the main ones are discussed below. [ABSTRACT FROM AUTHOR]

Copyright of Revista Cubana de Ciencias Informáticas is the property of Universidad de las Ciencias Informaticas (UCI) and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

Testing is a main aspect in quality control of software development, especially functional tests. The aim of functional testing is to dynamically verify the system behavior, based on the observation of a given set of controlled executions or test cases. Planning is required to make functional tests, defining the aspects to be checked and the way to verify its proper operation; this allows test cases make sense. In this paper (research based), we propose a method to generate functional test cases from system use cases, based on the co-financed project "Tool for Documenting Functional Testing." [ABSTRACT FROM AUTHOR]

Use cases are used to express the functionality required by a system. Use test cases derived directly from use cases take advantage of having the complete specification and documentation that exists from those last ones, to obtain a solid basement to make the necessary tests to the system. The capacity to create test cases from use cases, and to make a trace between them, is a crucial ability to ensure the quality of the software product. [ABSTRACT FROM AUTHOR]