Browsing by Keyword "Assurance case"
Now showing 1 - 2 of 2
Results Per Page
Sort Options
Item Approach for Enabling Security Across PLC Phases: An Industrial Use Case(Springer Verlag, 2018) Larrucea, Xabier; Nanclares, Félix; Santamaria, Izaskun; Nolasco, Ricardo Ruiz; Messnarz, Richard; Larrucea, Xabier; Santamaria, Izaskun; O’Connor, Rory V.; Tecnalia Research & Innovation; SWTSecurity and safety aspects are tightly related between them, and they are two major issues to be tackle during the development of any system, especially safety critical systems. In fact, these systems are framed in highly regulated domains and they involve a huge set of standards which have been focused on safety related issues. However, security issues have been playing a key role until now. In the context of medical devices, the U.S. Food and Drug Administration and The National Institute of Standards and Technology have published special considerations in this sense. This paper extends the assurance cases approach and integrates security aspects. A tool chain is outlined for linking assurance cases and a source code vulnerability analysis tool. This approach is illustrated with an industrial use case.Item A gsn approach to SEooC for an automotive hall sensor(Springer Verlag, 2016) Larrucea, Xabier; Mergen, Silvana; Walker, Alastair; Kreiner, Christian; O’Connor, Rory V.; Messnarz, Richard; Poth, Alexander; Tecnalia Research & InnovationOne of the key challenges for manufacturers of automotive systems, hardware components and software products is not only the process of defining explicit and implicit requirements but also the ability to satisfy safety requirements such as those specified in ISO 26262. From an element point of view, the Safety Element out of Context (SEooC) defined in ISO26262 is becoming a reference for developing systems, elements and components in the automotive sector. Integration teams have limited prior knowledge of how these third party devices have been defined, the assumed requirements used during the validation and verification phases. Goal Structuring Notation (GSN) can be used to define and document the assumed SEooC requirements in a graphical manner. However, development teams are facing several challenges for example how different requirements are implemented in SEooC, or how far GSN is able to represent SEooC definitions. This paper provides a GSN based approach to represent SEooC requirements in a practical example of an automotive hall sensor.