Deliverable structure Sample Clauses

Deliverable structure. ‌ This deliverable is divided in three main parts: conclusions from the first iteration related to integration and user interface, activities to rectify issues observed in the first iteration and, finally, a description of the installation process and manuals. In chapter 2, we look back at the integration process in the first version and lessons learned from it. This chapter has three distinct parts, first one related to the integration solution itself, second related to the packaging and distribution of ProaSense to the use case partners and the third one, which describes the conclusions about the UI.

Deliverable structure. The deliverable begins with a description of the methodology used to gather information about activities organised by the partners. A brief description of partner activities is presented followed by the analysis and summary of the gathered information. This serves to give an overview of the organisational details and approaches practiced by partners. Experiences from WP1 event organising are also included to give a more in depth perspective. The results not only highlight the most important details of the events and the diversity of approaches but also raise questions about our collective and individual practices in science event planning and facilitation. These questions and insights will be explored further througout phase 2 of the project. Next, a discussion of the analysis findings is presented focusing on three aspects: good practice for public engagement in biodesign, questions that arose during the analysis of each factor, and suggestions to improve the information gathering approach. A tentative template for organising specific types of events based on an information sheet proposed in this deliverable is also presented. Finally, this methodology is discussed in relation to previous results. The report reflects on the pros and cons of this approach in relation to the work package goals and provides suggestions for future improvements.

Deliverable structure. The deliverable starts by giving a short overview on the different soil types and their distribution on the world in Chapter 2. In the subsequent chapter 2.2, the soil types are divided in two categories (displaceable and non – displaceable soil). The two different type of soils has an influence on the design of the components of the underground robot, which is briefly described in this chapter. Focusing on the results of the foregone pre – selection, further selection criteria were elaborated to show, which soil type is feasible for BADGER. After this selection, the selected soil types are described in detail in chapter 3, before the deliverable come to the conclusion in chapter 4.

Deliverable structure. This deliverable report is structured into the following sections:

Deliverable structure. The document will further explain the concepts presented in this introduction. In particular: • Chapter 2 “The importance of the Human Element in Social Engineering 2.0” introduces the motivations that made attacking humans so important in the current digital environment. • Chapter 3 “Social Engineering within the modern Cybercrime” reports an overview of the leading trends in cybercrime, it shows SE 2.0 as the most remunerative tool that is at disposal of cybercriminals today 25 For example Exploit-as-a-service (▇▇▇▇▇://▇▇▇.▇▇/assets/refs/grier2012compromise.pdf) and Pay- per-install (▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/content/en/us/enterprise/media/security_response/whitepapers/pay_p er_install.pdf) 26 For example in the area of RaaS (Ramsonware as a Service) ▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/partner- perspectives/intel/franchising-ransomware/a/d-id/1321148, accessed November 2015. 27 ▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇.▇▇▇/fin4.html, accessed November 2015 28▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/operation-pawn-storm-cyber-espionage-campaign-hits- organizations accessed November 2015 Chapter 4 “Attack Process” describes how attacks are actually performed and which are their most relevant phases • Critical infrastructure and other vulnerable industries” presents a list of the most vulnerable industrial sectors with examples of assets that need to be protected from SE attacks • Chapter 6 “Countermeasures and trends” discusses the plethora of countermeasures that are nowadays either on the market or still in the research area. SE 2.0 is still an open point in security. • Chapter 7 “Foreseen Evolutions” presents the evolutions of this area of security, advances foreseen for the following years.

Deliverable structure. This deliverable report is structured into two main parts. In the first part of the deliverable, hardware functionalities and specifications of the whole BADGER system and every component is described. In the second part of the deliverable, software system functionalities and specifications are shown.

Deliverable structure. Chapter 2 of this report deals with transport policy measures and the context of transport policy making, especially in the European setting. Transport policy can have a wide variety of aims. It may be to seek to change or preserve various elements of the transport systems, transport related behaviours and activities, or transport governing markets, institutions, and organisations. The purpose of such changes can again refer to a broad range of economic, social and/or environmental objectives. To obtain such aims and objectives a large variety of policy instruments and measures can be adopted. It is necessary to consider the types of policy measures and their effects in the context of the policy aims, and the mechanisms that allow the measures to become adapted to fulfil them. It is in the interplay between policy aims, available instruments and real implementation processes that the consequences – desired, as well as possibly undesired ones – of policy measures occur.

Deliverable structure. ‌ In the rest of this deliverable, Section 2 presents an overview of the core TeraFlow OS components that comprise the entire WP3. Sections 3, 4, 5, and 6 highlight the design overview, interfaces, and preliminary results of the various core TeraFlow OS components across the four tasks in WP3 respectively. Section 7 concludes this work, while laying out a development strategy towards the final evaluation of life-cycle automation and high performance SDN components, which will be reported in the context of D3.2. Finally, Section 8 (Annex) reports data models and example RPCs for certain TeraFlow OS device driver plugins.