No full-text available
To read the full-text of this research,
you can request a copy directly from the authors.
Distributed System Integration Driven by Tests
Abstract
In complex distributed systems, the integration phase implies a lot of actions due to it is necessary to know how a component interacts with others. Usually, in the system design phase, modules are defined in a hierarchy in order to be easily integrated based on direct dependencies between the modules. That implies a sequential process of integration. In order to accelerate the integration process, agile-inspired integration method has been designed. The method is based in the moment that a unitary test of a component is passed, the dependencies can be started to be tested. The method has been applied in an intelligent system implemented in an indoor drone. First results show that the integration process based on this method is really accelerated, but the coordination between partners and the communication channels have a lot of influence to achieve the process with some minimum quality.
ResearchGate has not been able to resolve any citations for this publication.
Prioritization, selection and minimization of test
cases are well-known problems in software testing. Test case
prioritization deals with the problem of ordering an existing set
of test cases, typically with respect to the estimated likelihood
of detecting faults. Test case selection addresses the problem of
selecting a subset of an existing set of test cases, typically by
discarding test cases that do not add any value in improving the
quality of the software under test. Most existing approaches for
test case prioritization and selection suffer from one or several
drawbacks. For example, they to a large extent utilize static
analysis of code for that purpose, making them unfit for higher
levels of testing such as integration testing. Moreover, they do not
exploit the possibility of dynamically changing the prioritization
or selection of test cases based on the execution results of prior
test cases. Such dynamic analysis allows for discarding test cases
that do not need to be executed and are thus redundant. This
paper proposes a generic method for prioritization and selection
of test cases in integration testing that addresses the above issues.
We also present the results of an industrial case study where
initial evidence suggests the potential usefulness of our approach
in testing a safety-critical train control management subsystem.
Agile project management with Scrum derives from best business practices in companies like Fuji-Xerox, Honda, Canon, and Toyota. Toyota routinely achieves four times the productivity and 12 times the quality of competitors. Can Scrum do the same for globally distributed teams? Two Agile companies, SirsiDynix and StarSoft Development Laboratories achieved comparable performance developing a Java application with over 1,000,000 lines of code. During 2005, a distributed team of 56 Scrum developers working from Provo, Utah; Waterloo, Canada; and St. Petersburg, Russia, delivered 671,688 lines of production Java code. At 15.3 function points per developer/month, this is the most productive Java project ever documented. SirsiDynix best practices are similar to those observed on distributed Scrum teams at IDX Systems, radically different than those promoted by PMBOK, and counterintuitive to practices advocated by the Scrum Alliance. This paper analyzes and recommends best practices for globally distributed Agile teams.
The article focuses on integration of the information system in an organization The article focuses on integration of the information system in an organization. In many application areas, data is distributed over a multitude of heterogeneous information systems and the exchange of data between them is not easy. Each unit may be structured within three architectural layers. The business architecture layer defines the organizational structure and the workflows for business rules and processes. The application architecture layer defines the actual implementation of the business concepts in terms of enterprise applications. The technology architecture layer defines the information and communication infrastructure. At this layer, Information Technology is challenged to achieve the business requirements. It is important to consider all levels when integrating those systems. A horizontal integration of these layers is required to support the business processes effectively. Business engineering seeks to organize a commercial undertaking in a competitive way, whereby business processes cut horizontally through the traditional organization structure. INSETS: IT Disciplines involved in Information SI; Dimensions of Information SI.
The ever-increasing growth and complexity of software-intensive systems that has occurred over the last few years and the ensuing rise in geographically distributed projects are trends that are here to stay. Leading the charge into large, complex, dispersed systems is the government defense contracting industry. Government defense organizations have a critical need, the ability to make long-term investments based on the public interest, and a culture adapted to embracing distributed work. The Systems and Software Consortium, with a membership comprising most of the largest defense contractors, has a unique view into evolving initiatives both in and among its member companies. In this article, we describe an array of drivers, constraints, and enablers that are leading organizations to invest in real-time project management information systems. These systems must evolve to support increased decision velocity and cohesiveness in today's increasingly distributed world.
The purpose of this research is to contribute to a better understanding of information systems (IS) project management practice, by investigating the ISO 21500:2012/PMBoK 5 processes implemented by project managers in this kind of projects. Responses to an international web-based survey, representing 472 projects in total, showed that processes from knowledge areas as, for instance, scope management, cost management, and time management, are frequently implemented. However, there are processes from important areas as, for instance, quality management and risk management, that are being relegated to a second plane, what is a matter of concerning. Since IS projects do not have a very good reputation concerning success, these results can be of outmost importance to help researchers and practitioners to improve project management performance.
Three experimental environments traditionally support network and distributed systems research: network emulators, network simulators, and live networks. The continued use of multiple approaches highlights both the value and inadequacy of each. Netbed, a descendant of Emulab, provides an experimentation facility that integrates these approaches, allowing researchers to configure and access networks composed of emulated, simulated, and wide-area nodes and links. Netbed's primary goals are ease of use, control, and realism, achieved through consistent use of virtualization and abstraction.By providing operating system-like services, such as resource allocation and scheduling, and by virtualizing heterogeneous resources, Netbed acts as a virtual machine for network experimentation. This paper presents Netbed's overall design and implementation and demonstrates its ability to improve experimental automation and efficiency. These, in turn, lead to new methods of experimentation, including automated parameter-space studies within emulation and straightforward comparisons of simulated, emulated, and wide-area scenarios.
From the Publisher:In Managing the Testing Process, you'll examine an integrated approach - the bricks and mortar - of test management, based on the author's extensive, from-the-field experience with computer hardware and software test projects." "Simple and effective, the tools and tactics in this book comply with industry standards and reflect the best test-management practices of leading hardware and software vendors." "You'll find all the book's templates, test plans, spreadsheets, and tracking tools on the companion CD-ROM - where they're ready to help you organize your testing strategy, and focus on delivering the best possible product to your customers.
One way of responding to a keynote speaker is to put the expressed views into context, pointing to highlights in the address, suggesting areas where alternative viewpoints might have been presented, exposing any chinks in the armour of the otherwise ...
Software engineering comprehends several disciplines devoted to prevent and remedy malfunctions and to warrant adequate behaviour. Testing, the subject of this paper, is a widespread validation approach in industry, but it is still largely ad hoc, expensive, and unpredictably effective. Indeed, software testing is a broad term encompassing a variety of activities along the development cycle and beyond, aimed at different goals. Hence, software testing research faces a collection of challenges. A consistent roadmap of the most relevant challenges to be addressed is here proposed. In it, the starting point is constituted by some important past achievements, while the destination consists of four identified goals to which research ultimately tends, but which remain as unreachable as dreams. The routes from the achievements to the dreams are paved by the outstanding research challenges, which are discussed in the paper along with interesting ongoing work.
The draft IEEE 802.11 wireless local area network (WLAN)
specification is approaching completion. In this article, the IEEE
802.11 protocol is explained, with particular emphasis on the medium
access control sublayer. Performance results are provided for packetized
data and a combination of packetized data and voice over the WLAN. Our
performance investigation reveals that an IEEE 802.11 network may be
able to carry traffic with time-bounded requirements using the point
coordination function. However, our findings suggest that packetized
voice traffic must be handled in conjunction with an echo canceler