AbstractConnected vehicles have great potential to benefit society, yet create huge challenges. Vehicles, infrastructure and enterprise activities combine to form massively complex systems of systems (SoSs) that are vulnerable to cyber‐attacks. Security is ill‐defined, making it difficult to achieve a consistent, common understanding of security capabilities across the diverse industries that collaborate to develop connected vehicles. Rigorous evaluation is essential for developing strong security assurance cases. This paper contributes a model‐based systems engineering (MBSE) ontology that enables integrated evaluation processes in enterprise SoSs. The Evaluation Ontology allows diverse types of evaluation to be captured in a single integrated model. A connected vehicle security story is presented to demonstrate the value of the approach. Benefits include enhanced business intelligence that can provide a quantifiable, reportable level of confidence in security‐related processes and technologies. Further work will extend the ontology to develop a customisable suite of enabling patterns for security.

This chapter considers two essential enabling concepts for model-based systems engineering: the Architecture and the Architectural Framework (AF). After considering the basic Context for Architectures and Architectural Frameworks, the chapter describes a model-based approach to the definition of an AF. This defines a framework for the definition of an architectural framework, FAF (Framework for Architectural Frameworks). The definition of FAF follows the basic 'Ontology, Framework and Views' approach that is used throughout the book. A set of Processes are also introduced that can be used, along with FAF, to define an Architectural Framework. These Processes are briefly described in this chapter and the full model is given in Appendix F.

This is a book concerned with model-based systems engineering (MBSE), and thus modelling is fundamental to everything that is presented in it. It makes sense, therefore, before we consider MBSE in detail in Parts 3-5, to first consider the modelling aspects. This chapter discusses why modelling is so important in the context of the 'three evils' of engineering, briefly discusses the history of the systems engineering modelling language (SysML), establishes the basic requirements for modelling, introduces the concept of modelling and introduces to the SysML that is used as the modelling language throughout the rest of the book. Only the briefest of syntax will be looked at in this chapter.

One of the problems facing any person trying to implement MBSE into an organisation is one of the biggest issues that the authors have experienced. It is not the technical side, nor is it having the tools in place, nor the training. Perhaps the single biggest hurdle is one that can kill any initiative before it has even begun, and this is selling MBSE or, to put it more accurately, conveying the benefits of MBSE to relevant Stakeholders within the business. A common pitfall at this point is to go to the Internet and to perform a search on `benefits of MBSE' which seems both obvious and intuitive. The downside of this is that, invariably, all of the first hits will be from tool vendors who will essentially state the capabilities of their tools. There is nothing wrong with this per se, but these capabilities will typically excite Systems Engineers, but may not necessarily excite the people who have responsibility for budgets in the organisation. The key thing to bear in mind here is that different Stakeholders will look for different benefits from MBSE because, you have guessed it, they each have their own context. It is essential to understand the “why”of each Stakeholder Role. If we cannot understand their “why”, then we have failed before we have begun. In order to illustrate the benefits of MBSE, we shall be using a simple analogy of “the old lady who swallowed a fly”which is a traditional nursery rhyme in some parts of the world. If you are not familiar with this children's verse, then stop reading, get on the Internet and search it out. The chapter will make a lot more sense if you do this!

This chapter looks at expanding the approach to context-based requirements engineering (ACRE) so that it can be applied to systems of systems. Chapter Contents: 10.1 Introduction 10.1.1 Background 10.1.2 Defining a System of Systems 10.1.3 Types of Systems of Systems 10.2 Approach 10.2.1 The MBSE Ontology (revisited) 10.2.2 The Framework 10.2.3 The Views 10.3 Using the Requirements modelling for Systems of Systems Framework 10.4 Summary References Inspec keywords: formal specification; systems engineering Other keywords: requirements modelling; context-based requirements engineering; ACRE; systems-of-systems Subjects: Formal methods; Software engineering techniques

This chapter considers how the 'seven views' approach may be used as a basis for various model-based systems engineering (MBSE) applications. The definition of the 'seven views' follows the basic 'Ontology, Framework and Views' approach.

This chapter looks at the two aspects of modelling that are necessary in SysML the structural and behavioural aspects of a system. Block definition diagrams are used to discuss structural diagrams, and behavioural modelling is discussed by considering how the various diagrams relate to system hierarchy and engineering activity. A key consideration when modelling is consistency, leading to a good correct, concise and consistent model, which leads directly to confidence in the system. Confidence means that the system is understood and can be communicated to other people. Remember: SysML + consistency = model SysML consistency = pictures. The nine SysML diagrams are briefly introduced, with the five diagrams that are used by ACRE covered in more detail. For each diagram, its notation is introduced along with examples of its usage. These examples are taken from the world of escapology, namely the so-called coffin stunt, which is chosen since it ties in with the example system used in the case study.

This chapter looks at a model-based approach to Process modelling, which, although at first appearances, may seem quite simple; it will be shown that the application of modelling processes has myriad uses in systems engineering. The basic 'seven views' approach that is described in this chapter may be applied to many other areas of systems engineering, such as modelling standards, compliance, life cycle modelling, competence modelling, and project management. The definition of the 'seven views' follows the basic 'Ontology, Framework and Views' approach, which is used throughout this book.