T-Way Testing Strategies

In line with the advancement of hardware technology and increasing consumer demands for new functionalities and innovations, software applications grew tremendously in term of size over the last decade. This sudden increase in size has a profound impact as far as testing is concerned. Here, more and more unwanted interactions among software systems components, hardware, and operating system are to be expected, rendering increased possibility of faults. To address this issue, many useful interaction-based testing techniques (termed t-way strategies) have been developed in the literature. As an effort to promote awareness and encourage its usage, this chapter surveys the current state-of-the-art and reviews the state-of-practices in the field. In particular, unlike earlier work, this chapter also highlights the different possible adoptions of t-way strategies including uniform interaction, variable strength interaction, and input-output-based relation, that is, to help test engineers make informed decision on the actual use of t-way strategies.

Is Modeling a Treatment for the Weakness of Software Engineering?

Experts' opinions exist that the way software is built is primitive. The role of modeling as a treatment for Software Engineering (SE) became more important after the appearance of Model-Driven Architecture (MDA). The main advantage of MDA is architectural separation of concerns that showed the necessity of modeling and opened the way for Software Development (SD) to become engineering. However, this principle does not demonstrate its whole potential power in practice, because of a lack of mathematical accuracy in the initial steps of SD. The question about the sufficiency of modeling in SD is still open. The authors believe that SD, in general, and modeling, in particular, based on mathematical formalism in all its stages together with the implemented principle of architectural separation of concerns can become an important part of SE in its real sense. They introduce such mathematical formalism by means of topological modeling of system functioning.

Critical Issues in Requirements Engineering Education

Requirements Engineering (RE) is the most crucial process within software development projects. In order to prepare skilled requirements engineers, Requirements Engineering Education (REE) needs to be provided to students at the university level before they become software engineers and part of the workforce. However, RE is considered the most difficult subject within the software engineering curriculum for students to learn and for lecturers to teach due to its uncertain nature. This chapter examines the current and potential areas for research within REE. It first presents the current status of REE provided in universities and the REE problems reported in the literature that lead us to the potential research problems in REE. The REE teaching approaches proposed by researchers are then elaborated. The proposed approaches are mapped back to address the REE problems. The chapter closes with recommended directions for future REE research.

Open Source Software Adaptation in Africa

The African continent has long benefited from adopting OSS in its private and public organizations that have changed their way of development, the use and how to acquire proprietary software. This frequency of adaptation does not appear to be in balance with the contribution to the OSS community. Using views from experienced software practitioners working in different organizations across two African countries it has been observed that neglected infrastructure, a wide availability of proprietary software and misconceptions of a clear meaning of Open Source Software across Africa have been an obstacle towards the participation in the OSS technology in the global network.

Managing Tacit Knowledge to Improve Software Processes

In general, software process improvement entails significant benefits such as increased software product quality, decreased time and development cost, and decreased risks. To obtain these, organizations must apply knowledge management because the identification of new knowledge is considered key to success when improving software processes. Existing knowledge is, however, difficult to find, and when found, it is often difficult to reuse in practice. This is due to the fact that a considerable part of the knowledge that is useful for executing software processes is tacit and not all of it can be captured and made explicit. The purpose of this chapter is to present a framework for software process improvement based on the enrichment of organizational knowledge by means of the acquisition of tacit knowledge from individuals working in different teams and environments. The framework includes the specification of roles, processes, and tools, and is based on a process asset library and the introduction of configuration and change management mechanisms.

Reverse Engineering of Object-Oriented Code

Software modernization is a new research area in the software industry that is intended to provide support for transforming an existing software system to a new one that satisfies new demands. Software modernization requires technical frameworks for information integration and tool interoperability that allow managing new platform technologies, design techniques, and processes. To meet these demands, Architecture-Driven Modernization (ADM) has emerged as the new OMG (Object Management Group) initiative for modernization. Reverse engineering techniques play a crucial role in system modernization. This chapter describes the state of the art in the model-driven modernization area, reverse engineering in particular. A framework to reverse engineering models from object-oriented code that distinguishes three different abstraction levels linked to models, metamodels, and formal specification is described. The chapter includes an analysis of technologies that support ADM standards and provides a summary of the principles that can be used to govern current modernization efforts.

Digital Home

While many Software Engineering (SE) and Computer Science (CS) textbooks make use of case studies to introduce difference concepts and methods, the case studies introduced by these texts focus on a specific life-development phase or a particular topic within software engineering object-oriented design and implementation or requirements analysis and specification. Moreover, these case studies usually do not come with instructor guidelines on how to adopt the introduced material to the instructor's teaching style or to the particular level of the class or students in the class. The DigitalHome Case Study aims at addressing these shortcomings by providing a comprehensive set of artifacts associated with the full software development life-cycle. The project provides an extensive set of case study modules with exercises for teaching different topics in software engineering and computer science, as well as guidance for instructors on how to use these case modules. In this chapter, the authors motivate the use of the case study approach in teaching SE and CS concepts. They provide a description of the DigitalHome case study and the associated artifacts and case modules. The authors also report on the use of the developed material.

Underpinning EISB With Enterprise Interoperability Neighboring Scientific Domains

Over the last decade, interoperability appeared as a key enabler towards unlocking the full potential of enterprises, products, processes, and systems. With methods to support their lifecycle, contributing towards removing communication barriers, and fostering a new-networked business culture in industrial domains, Enterprise Interoperability (EI) requires tangible scientific foundations. This chapter recognizes that, in terms of content, any scientific field exists in an ecosystem of neighboring domains and presents a methodology to identify EI's relationship with its neighbors, thus supporting the foundations of EI Science Base (EISB). It can be agreed that formalisms like logic and mathematics are an integrant part of every science, but others also share relationships such as application fields' boundaries, methodologies, techniques, or even tools. With the support of the European Commission, through the Future Internet and Enterprise Systems (FInES) cluster of research projects, the authors have initiated an analysis of comprehensive domains (e.g. complexity and software).

A Method to Design a Software Process Architecture in a Multimodel Environment

In the multimodel improvement context, Software Organizations need to incorporate into their processes different practices from several improvement technologies simultaneously (i.e. CMMI, PSP, ISO 15504, and others). Over the last few years, software process architectures have been considered a means to harmonize these technologies. However, it is unclear how to design a software process architecture supporting a multimodel environment. In this chapter, an overview of the method to design a software process architecture is presented, identifying basic concepts, views, phases, activities, and artifacts. In addition, important aspects in the creation of this method are explained. This method will assist process stakeholders in the design, documentation, and maintenance of their software process architecture.

Object-Oriented Cognitive Complexity Measures

This chapter presents the analysis of ten recently proposed object-oriented metrics based on cognitive informatics. The metrics based on cognitive informatics use cognitive weight. Cognitive weight is the representation of the understandability of the piece of software that evaluates the difficulty experienced in comprehending and/or performing the piece of software. Development of metrics based on Cognitive Informatics (CI) is a new area of research, and from this point of view, for the analysis of these metrics, it is important to know their acceptability from other existing evaluation and validation criteria. This chapter presents a critical review on existing object-oriented cognitive complexity measures. In addition, a comparative study based on some selected attributes is presented.