Explore the vast range of titles available.

Over the last decade, software development has seen a substantial growth in the use of agile techniques. Agile emerged as an alternative way to develop software and manage projects. Unlike traditional methods that focus on modelling and analysis, agile encourages communication and collaboration with end users to develop software without the need for modelling. Documentation that is large, paper-based, and difficult-to-read becomes the enemy because it empedes effective communication among people in projects.

Developers are increasingly using service-oriented middleware to develop distributed systems. This middleware raises the abstraction level for software so that distributed-system developers can focus more on application-level concerns (for instance, business logic) rather than wrestle with infrastructure-level concerns (such as software adaptation, context-awareness, and life-cycle management). Service-oriented middleware also promotes reuse of business logic and services across heterogeneous application domains, thus facilitating the development of larger, more complex systems.

Organizations face the need to adapt themselves to a complex business environment, in continuous change and transformation. Under these circumstances, organization agility is a key element in gaining strategic advantages and market success. Achieving and maintaining agility requires agile architectures, techniques, methods and tools, able to react in real time to change requirements. This paper proposes an incursion in the software development, from traditional to agile. [PUBLICATION ABSTRACT]

This chapter introduces the three implementation options: full Agile, pilot Agile, and Agile lite. It provides helpful tips and ideas to increase auditors' chances of Agile auditing success, so their organization can experience the full benefits of this approach to completing audit projects. The full Agile strategy is the most aggressive of the three because it involves evolving existing audit systems and procedures to create efficient processes and add more value to the organization. The Agile lite strategy selects specific Agile techniques and tools that are helpful to any audit team. The chapter also provide examples of teams using Agile principles. The Product Owner will stay informed of the audit's progress by attending the daily meetings. The following skills are essential for Product Owners to have, to increase their effectiveness and the project's success: provide leadership, allow flexibility, listen attentively, present articulately, communicate effectively, influence positively, and demonstrate empathy.

This chapter contains sections titled: OFDM Implementation Synchronization Channel Estimation Peak Power Problem Adaptive Transmission Spectrum Shaping Orthogonal Frequency Division Multiple Access MIMO OFDM OFDM Cognitive Radio Network Summary

This chapter contains sections titled: Benefits of MIMO Space Time Coding Multi‐User MIMO MIMO Network MIMO Cognitive Radio Network Summary

With the emergence of fog and edge computing, new possibilities arise regarding the data-driven management of citizens’ mobility in smart cities. Internet of Things (IoT) analytics refers to the use of these technologies, data, and analytical models to describe the current status of the city traffic, to predict its evolution over the coming hours, and to make decisions that increase the efficiency of the transportation system. It involves many challenges such as how to deal and manage real and huge amounts of data, and improving security, privacy, scalability, reliability, and quality of services in the cloud and vehicular network. In this paper, we review the state of the art of IoT in intelligent transportation systems (ITS), identify challenges posed by cloud, fog, and edge computing in ITS, and develop a methodology based on agile optimization algorithms for solving a dynamic ride-sharing problem (DRSP) in the context of edge/fog computing. These algorithms allow us to process, in real time, the data gathered from IoT systems in order to optimize automatic decisions in the city transportation system, including: optimizing the vehicle routing, recommending customized transportation modes to the citizens, generating efficient ride-sharing and car-sharing strategies, create optimal charging station for electric vehicles and different services within urban and interurban areas. A numerical example considering a DRSP is provided, in which the potential of employing edge/fog computing, open data, and agile algorithms is illustrated.

The Brazilian General Data Protection Law (LGPD) implementation has impacted activities carried out by the software development teams. Due to it, developers had to become aware of the existing techniques and tools to carry out privacy requirements elicitation. Extending our previous work, we have investigated the actions taken by organizations regarding the LGPD, specifically in software development, considering the perception of agile development teams after two years of the LGPD implementation. In addition, we also investigated the perception of an agile team regarding the practices, techniques, and tools previously cited by practitioners as potential solutions for use in this context, along with techniques already in use in the current context. We have conducted a systematic literature review (SLR) and selected 36 primary studies. Furthermore, we have conducted a survey with 53 IT practitioners and semi-structured interviews with ten practitioners. The LGPD principles are known by most agile teams and are being implemented by the organizations, although the existing tools to support privacy requirements elicitation are still underused by agile teams. Moreover, agile teams consider that software requirements and software construction are the most impacted areas of knowledge by the LGPD, and most of them use user stories in privacy requirements elicitation. Our findings reveal that agile teams and Brazilian organizations are more concerned with user data privacy issues after the LGPD became effective. However, agile teams still face challenges in privacy requirements elicitation.

Worldwide, industries are emphasizing the development of an agile system to sustain higher productivity, which can be applied to ensure improvements in all production conditions in industry 4.0. In the present scenario, several methods are used for improvements in production, such as value stream mapping, kaizen, just in time, Kanban, and total productive maintenance, etc., The objective of the present research article is to produce an agile system to sustain improvements in productivity through a methodology coupled with value stream mapping in industry 4.0. Value stream mapping is a lean-based method and is used for the maximization of productivity by the elimination of non-value-added activities. The proposed methodology has been validated by productivity enhancements achieved in a case study of the earthmoving machinery manufacturing sector. The study establishes that the proposed methodology would encourage industry personnel during decision-making processes, which would lead to improvements in production in industry 4.0.

Agile is often associated with a lack of architectural thinking causing technical debt but has the advantage of user centricity and a strong focus on value. Model-driven software engineering (MDSE) strongly performs for building a quality architecture and code, but lacks focus on user requirements and tends to consider development as a monolithic whole. The combination of Agile and MDSE has been explored, but a convincing integrated method has not been proposed yet. This paper addresses this gap by exploring the specific combination of MERODE—as an example of a proven MDSE method—with Scrum, a reference agile method offering a concrete (sprint-based) life cycle management on the basis of user stories. The method resulting of this integration is called Agile MERODE; it is driven by user stories, themselves associated with behavior-driven development scenarios. It allows for domain-driven design and permits fast development from domain models by means of code generation. An illustrative example further clarifies the practical application of Agile MERODE, while a case study shows the planning game application in the case’s context. While the approach, in its entirety, allows reducing technical debt by building the architecture in a logical, consistent and complete manner, introducing MDSE involves a trade-off with pure value-driven development. Agile MERODE contributes to the state of the art by showing how to increase user centricity in MDSE, how to align model-driven engineering with the Scrum cycle, and how to reduce the technical debt of agile developments yet remaining value-focused.