You are presented with multiple paper abstracts, alongside the associated literature review and chapter titles. Given the provided information, you are going to do a literature review. Please generate a coherent literature review that synthesizes the content, draws connections between different works, highlights major findings, and identifies any gaps in the existing research.

Literature Review Title: Choreography in the embedded systems domain: A systematic literature review 
Chapter Title:  Introduction 
1. Abstract of Cited Paper (BIB001):  From the Publisher: ::: This technical dictionary will define all of the most-used words in the embedded systems field - over 2,500 terms. Designed to serve both a technical and non-technical audience, this book defines advanced terms in two steps. The first step is a general, contextual definition that will serve the needs of less technical readers. The second step covers information in language that is appropriate to a serious technical reader. Some terms reference an appendix of white papers of even more detail. 
2. Abstract of Cited Paper (BIB002):  As the technology associated to the ?Web Services? trend gains significant adoption, the need for a corresponding design approach becomes increasingly important. This paper introduces a foundational model for designing (composite) services. The innovation of this model lies in the identification of four interrelated viewpoints (interface behaviour, provider behaviour, choreography, and orchestration) and their formalization from a control-flow perspective in terms of Petri nets. By formally capturing the interrelationships between these viewpoints, the proposal enables the static verification of the consistency of composite services designed in a cooperative and incremental manner. A proof-of-concept simulation and verification tool has been developed to test the possibilities of the proposed model. 
3. Abstract of Cited Paper (BIB003):  We discuss the suitability of service-oriented computing for the automotive domain. We present a formal high-level language in which complex automotive activities can be modelled in terms of components and services that can either be provided by the on-board system or procured from external providers (e.g. via the web) through a negotiation process that involves quality of service attributes and constraints. The ability to re-configure activities, in real-time, through service discovery and dynamic binding takes us one step further from current component-based development techniques: it enhances flexibility and adaptability to changes that occur in the environment in which the system operates (driver, automobile, and external circumstances) and, ultimately, leads to improved levels of satisfaction, safety and reliability. 
4. Abstract of Cited Paper (BIB004):  Intelligent systems, composed by devices with embedded computing capability, sensors and actuators interacting with the environment, will enhance and support manufacturing in the future. SOCRADES (Service-oriented cross-layer infrastructure for distributed smart embedded devices) is a European research project that focuses on the development of a platform for next-generation industrial intelligent systems, exploiting SOA paradigm. Within SOCRADES a Technology Roadmap is being developed. Its aim is to provide inputs for the orientation of technological research to achieve the long term objectives required for the enhanced and pervasive exploitation of intelligent systems for manufacturing support. We present the Expected Features of Technology Areas (EFTAs) identified within SOCRADES Technology Roadmap. Then we show how the outcome of SOCRADES Technology Roadmap addresses important needs such as those pointed out by the Strategic Research Agenda developed by ARTEMIS (European Technology Platform for Embedded systems). 
5. Abstract of Cited Paper (BIB005):  Due to the complex system context of embedded-software applications, defects can cause life-threatening situations, delays can create huge costs, and insufficient productivity can impact entire economies. Providing better estimates, setting objectives, and identifying critical hot spots in embedded-software engineering requires adequate benchmarking data. 
6. Abstract of Cited Paper (BIB006):  This article summarizes the results of 25 expert interviews, regarding the value potential and challenges of the Service-oriented Architecture (SoA) paradigm for users and software vendors. On the user side, the SoA value potential most often mentioned by experts was agility, followed by process optimization. Cost reduction, through a more efficient development, or consolidation of redundant IS landscapes are also seen as a value potential. In contrast to the literature, reuse of services seems not that significant and is highly debated among the experts. In order to realize the value potentials, users have to overcome certain challenges. Here, the experts mention the financing of the investments, the setting up of a proper governance and the creation of a common understanding of the SoA paradigm as biggest hurdles. For the software vendors, experts mention that SoA-based solutions create new market opportunities as lock-in-effects are lowered and offerings can be easier enhanced by third-party services. Regarding cost, there is potential to harmonize existing product portfolios or integrate acquisitions more easily. Development cost reduction is less evident at the current stage of adoption. It is assumed that lower lock-in effects also lead to increased competition, which could become a major challenge especially for established vendors. 
7. Abstract of Cited Paper (BIB007):  The development of embedded networks poses several challenges: complexity and size of the network, heterogeneity of nodes, and infrastructure dynamics. From other IT domains it is known that many of these challenges can be met by a Service Oriented Architecture (SOA). In the context of embedded networks, an application can be interpreted as a set of interacting services that produce, consume or manipulate data. However, the hard boundary conditions of embedded networks, such as limited resources and real time requirements, have to be taken into account. This paper discusses an embedded SOA (∈SOA) concept based on the definition of an embedded service (∈Service) term and the differences to traditional Web services based SOAs. The paper describes a middleware platform that supports the execution and development of embedded network applications by employing model based code generation and a pattern based service composition model. The advantages of the approach are showcased using an application from the building automation sector, focusing on the energy management of smart buildings. 
8. Abstract of Cited Paper (BIB008):  Originally coming from the business world, service-oriented architecture (SOA) paradigm is expanding its range of application into several different environments. Industrial automation is increasingly interested on adopting it as a unifying approach with several advantages over traditional automation. In particular, the paradigm is well indicated to support agile and reconfigurable supply chains due to its dynamic nature. In this domain, the main goals are short time-to-market, fast application (re)configurability, more intelligent devices with lifecycle support, technology openness, seamless IT integration, etc. The current research challenges associated to the application of SOA into reconfigurable supply chains are enumerated and detailed with the aim of providing a roadmap into a major adoption of SOA to support agile reconfigurable supply chains. 
9. Abstract of Cited Paper (BIB009):  The initiative AESOP (ArchitecturE for Service-Oriented Process-Monitoring and — Control) envisions a Service-oriented Architecture approach for monitoring and control of Process Control applications (batch and continuous process). Large process industry systems are a complex (potentially very large) set of (frequently) multi-disciplinary, connected, heterogeneous systems that function as a complex system of which the components are themselves systems. The future “Perfect Plant” will be able to seamlessly collaborate and enable monitoring and control information flow in a cross-layer way. As such the different systems will be part of an SCADA/DCS ecosystem, where components can be dynamically added or removed and dynamic discovery enables the on-demand information combination and collaboration. All current and future systems will be able to share information in a timely and open manner, enabling an enterprise-wide system of systems that will dynamically evolve based on business needs. The SOA-based approach proposed by AESOP can, on one hand, simplify the integration of monitoring and control systems on application layer. On the other hand, the networking technologies that are already known to control engineers could also simplify the inclusion of or migration from existing solutions and integration of the next generation SCADA and DCS systems at network layer. 
10. Abstract of Cited Paper (BIB010):  Abstract The European 7 th Framework FP7-ICT-2009-5 project CHOReOS No. 257178 (2010-2013) “Large Scale Choreographies for the Future Internet (IP)” is aimed to elaborate on new methods and tools related to Future Internet ultra-large-scale (ULS) solution development based on the use of choreographies. The purpose of this research is to identify exploitable CHOReOS products and approaches and business market trends that may exploit them. The aim is to collect and assess early market inputs, thereby ensuring that market needs are addressed properly by the CHOReOS project. The market acceptance assessment is done using the Unified Theory of Acceptance and Use of Technology (UTAUT), but the credibility of results is assessed using Cronbach's Alpha, Split-Half Reliability and Spearman–Brown testing methods. 
11. Abstract of Cited Paper (BIB011):  Thank you for downloading enterprise soa service oriented architecture best practices. Maybe you have knowledge that, people have search numerous times for their favorite books like this enterprise soa service oriented architecture best practices, but end up in malicious downloads. Rather than enjoying a good book with a cup of coffee in the afternoon, instead they are facing with some malicious virus inside their desktop computer.

Literature Review:
The growing utilisation of embedded systems (ES) in different application areas, such as automotive, avionics and home appliances, has led to the growth of their software size and complexity BIB006 . As a consequence, ES have become inflexible, thus difficult to maintain, while the associated development costs and time have increased. One approach to addressing these challenges has been the adoption of service-oriented architecture (SOA), which originates from the enterprise systems domain and has been designed to tackle the corresponding challenges. SOA has been successfully applied in enterprise systems development to advance the flexibility and to reduce the costs and time required for development BIB007 [3][4]  . Consequently, SOA is increasingly adopted in the ES domain, BIB008 BIB004 [8] BIB010 . Enterprise systems built following SOA can be seen as a collection of software services built by independent organisations or companies that have common business goals BIB012 . These systems support the realisation of business goals through the service interactions. Since doing so represents the realisation of the organisations' goals, the specification of service interactions has to include sufficient details for its users, and thus it is often specified from different viewpoints BIB003 . Different viewpoints focus on different sets of service interaction details and use their own set of concepts to document those details. Choreography represents a viewpoint on service interactions in SOA-based development BIB001 . In the enterprise domain, choreography specifies the sequence of interactions that realises the organisations' business goals. In an ES domain, choreography is used in the same manner, but instead of focusing on the organisations, it specifies the sequence of interactions among devices in a product of which they are a part. For example, a car includes a number of devices that are responsible for tasks such as fuel control and the braking system. These devices are comparable to organisations in the enterprise domain and thus seen as service providers whose services are interacting to fulfil the goals such as automatic cruise control. A number of studies focusing on choreography in ES have been published. For example, the documentation of the smart embedded devices in manufacturing is expected to include a choreography specification BIB005 . Specifying choreography can also contribute to the agility, and thus to the flexibility, of industry supply chain systems BIB009 . The analysis of the acceptance and use of choreography among practitioners indicated their interest in using choreography and that choreography tools can increase their productivity BIB011 . The results of these studies indicate the growing importance of choreography in ES, however, the results are also scattered and there is neither a common understanding of how to use the choreography in ES nor a consensus on how it affects the ES development process. For this reason, there is a need to gather the existing information in the scientific literature, to analyse it systematically and present a synthesis of the current knowledge of choreography usage in the ES domain. This need motivated the objective of this study and the selection of the research method. The objective of this study is to identify the current features of the use of choreography in the ES domain that are relevant for practitioners and researchers. To accomplish this, the existing scientific literature was systematically analysed considering current developments, strategies for choreography adaption, choreography specification and execution types, and implicit assumptions about choreography. The Beside these constructs, a choreography specification can contain information about other development artefacts, such as the messages that is exchanged between the participants, the events that can occur during interactions and the message exchange patterns  . Interactions can also be specified from the orchestration point of view. Orchestration specifies interactions from the perspective of an individual participant and captures the service interactions needed to achieve a single participant's goal. This differs from choreography, which captures the interactions between participants that realise their common goal and makes orchestration a local view or a projection on choreography from the perspective of a single participant that is engaged in that choreography. Choreography and orchestration therefore represent two complementary viewpoints that specify the interactions from different abstraction levels. Services and interactions, as the fundamental concepts in SOA, are increasingly adopted in the ES domain BIB008 BIB004 [8] BIB010 . ES is seen a software-controlled device designed with a dedicated function in mind, but it can also be seen as a function or service provider within a larger product such as automobiles, trains or aeroplanes BIB002 . Consequently, these products can combine services that are provided by distinct ES according to the goal they aim to fulfil. Our perspective is that with the increase in the number of networked ES, or participants, the need to specify their interaction from a global or choreography viewpoint will increase accordingly, while the need for orchestration will remain unchanged and limited to devices and networks with excessive resources and processing capabilities. Besides the scientific literature, these reasons additionally contribute to our decision to focus on choreography and how it is utilised in the ES domain.