Info: Zenodo’s user support line is staffed on regular business days between Dec 23 and Jan 5. Response times may be slightly longer than normal.

Published October 2, 2018 | Version v1
Conference paper Open

Systems Engineering – The Hard Way

  • 1. BAE SYSTEMS Maritime - Submarines, UK
  • 2. Rolls Royce, UK

Description

Ship designers, builders, owners, insurers and class societies are becoming ever more aware of the complex interactions of the various systems found on all types of marine vessels. Therefore a design process that acknowledges these demands and assesses the risks posed, and manages them becomes ever more important. This paper seeks to explore some of the, sometimes apparently, conflicting requirements that are placed on designs of new marine platforms and looks at methods that enable these elements to be
expressed, understood and managed in the context of an integrated ship design.
The demands placed on new vessels include a range of requirements that move away from being solely based around the traditional functional requirements; including the ideas of designing for ease of shipbuilders, operators and maintainers; and now acknowledging the need of a through life safety case, cyber security case, and full obsolescence planning. This becomes ever more complex when consideration is given to how these through life elements are practically managed, with a range of methods, none of
which are without their own challenges.
It is important to note as these demands are discussed that often a ‘solution’ in the truest sense does not exist and the management of risk becomes a balance between the expected risk, the practicable solution, along with the potential compromises to both programmes and cost.
While these demands place huge constraints and drive complexity into design processes, the issues can, and regularly have, been further exacerbated when some of these, or other requirements, are introduced into the design or build phases of projects. Introduction of design drivers should not be undertaken lightly or without expected, and accepted, increases in required resources, both financial and calendrical.

Files

INEC 2018 Paper 009 Edmondson FINAL.pdf

Files (4.4 MB)

Name Size Download all
md5:ebb750a5c6e9d607b6e9550562e99cc4
4.4 MB Preview Download

Additional details

References

  • Safety Assessment Principles for Nuclear Facilities, Office for Nuclear Regulation, 2014 Edition, Revision 0
  • Security Assessment Principles for the Civil nuclear Industry, Office for Nuclear Regulation, 2017 Edition, Version 0
  • Management of Risk when Planning Work: The right Priorities, Health and Safety Executive, HSE 11/11
  • Pohl and Rupp - Requirements Engineering Fundamentals ISBN 9781937538774
  • B. Schar, Requirements Engineering Process HERMES 5 and SCRUM, University of Applied Sciences and Arts, Northwestern Switzerland, 2015.
  • Aldekhail, Chikh, Ziani - (IJACSA) International Journal of Advanced Computer Science and Applications, Vol. 7, No. 10, 2016
  • M. Kim, S. Park, V. Sugumaran, and H. Yang, Managing requirements conflicts in software product lines: A goal and scenario based approach, Data Knowl. Eng., vol. 61, no. 3, pp. 417-432, Jun. 2007.
  • W. N. Robinson, S. D. Pawlowski, and V. Volkov, Requirements Interaction Management, ACM Comput Surv, vol. 35, no. 2, pp. 132-190, Jun. 2003.
  • L.E.Hart - INCOSE SE Vision 2020 (INCOSE-TP-2004-004-02, Sep 2007) https://www.incose.org/docs/default-source/delaware-valley/mbse-overview-incose-30-july-2015.pdf