Size Matters: Microservices Research and Applications

In this chapter we offer an overview of microservices providing the introductory information that a reader should know before continuing reading this book. We introduce the idea of microservices and we discuss some of the current research challenges and real-life software applications where the microservice paradigm play a key role. We have identified a set of areas where both researcher and developer can propose new ideas and technical solutions.Comment: arXiv admin note: text overlap with arXiv:1706.0735

Some Findings Concerning Requirements in Agile Methodologies

gile methods have appeared as an attractive alternative to conventional methodologies. These methods try to reduce the time to market and, indirectly, the cost of the product through flexible development and deep customer involvement. The processes related to requirements have been extensively studied in literature, in most cases in the frame of conventional methods. However, conclusions of conventional methodologies could not be necessarily valid for Agile; in some issues, conventional and Agile processes are radically different. As recent surveys report, inadequate project requirements is one of the most conflictive issues in agile approaches and better understanding about this is needed. This paper describes some findings concerning requirements activities in a project developed under an agile methodology. The project intended to evolve an existing product and, therefore, some background information was available. The major difficulties encountered were related to non-functional needs and management of requirements dependencies

Source code repositories and agile methods

Source repositories are a promising database of information about software projects. This paper proposes a tool to extract and summarize information from CVS logs in order to identify whether there are differences in the development approach of Agile and non-Agile teams. The tool aims to improve empirical investigation of the Agile Methods (AMs) without affecting the way developers write code. There are many claims about the benefits of AMs; however, these claims are seldom supported by empirical analysis. Configuration management systems contain a huge amount of quantitative data about a project. The retrieval and part of the analysis can be automated in order to get useful insights about the status and the evolution of the project. However, this task poses formidable challenges because the data source is not designed as a measurement tool. This paper proposes a tool for extracting and summarizing information from CVS (Concurrent Versions System) repositories and a set of analysis that can be useful to identify common or different behaviors

Requirements Engineering for Agile Methods

Collecting, understanding, and managing requirements is a critical aspect in all development methods. This is true for Agile Methods as well. In particular, several agile practices deal with requirements in order to implement them correctly and satisfy the needs of the customer. These practices focus on a continuous interaction with the customer to address the requirements evolution over time, prioritize them, and deliver the most valuable functionalities first. This chapter introduces Agile Methods as the implementation of the principles of the lean production in software development. Therefore, Agile Methods focus on continuous process improvement through the identification and the removal of waste, whatever does not add value for the customer

Ranking and Selecting Services

Service composition is the most recent approach to software reuse. The interactions among services propose many problems already approached in the composition of software components even if introducing more issues related to the run-time composition that is very limited in the components world. One of such problems is the identification of a set of services that can be integrated to build a complete system. This paper proposes an adaptation of a methodology for ranking and selecting components to a service-based environment. In particular, the methodology has been extended to support the peculiarities of services and include the support to the related technologies

Reuse: from Components to Services

In these years, a programming paradigm shift is in progress: researchers and developers are moving from component-based to service-based develop-ment. This shift is deeply affecting the technology, changing the way of ad-dressing old problems and producing new standards and methodologies to address the new ones. However, even with this shift, some old problems are arising again and their complexity is increasing. One of such problems is the identification of a set of components/services that can be integrated to build a system. This paper proposes an adaptation of a methodology for ranking and selecting components to a service-based environment

1st International Workshop on trust in open source software (TOSS)

The 1st International Workshop on Trust in Open Source Software (TOSS) focuses on one of the major factors in the adoption of software solutions: the trustworthiness of OSS, which has influenced the widespread adoption of OSS in industry. Software quality aspects have been investigated for a long time in the academia but the usage/production of OSS is creating new challenges and the points of view of the industry and the academia may differ, especially on the trustworthiness of OSS. The aim of the workshop is to open a communication channel between the industry and the academia focusing on this issue and promote a long lasting discussion on it. The workshop tries to identify the different points of views and the different approaches that can result in benefits for the software industry