Abstract
AbstractOn complex rail projects involving a step change in technology or capability, it is important to understand what functionality is required from the system, especially if such changes are new or novel. This paper details a case study (Deep Tube Upgrade Programme) where a structured functional breakdown approach was developed to provide stakeholders (including non‐Systems Engineering practitioners such as operators and maintainers) with an accessible means of checking their life‐cycle concepts and stakeholder requirements for completeness. The approach also enabled the decomposition of those needs into system design requirements for allocation to one or more of the 20 delivery projects, to ensure they will deliver the required emergent properties.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
