THE SINGAPORE ENGINEER - Institution of Engineers Singapore

More documents

Recommendations

Info

SYSTEMS COVER ENGINEERING STORY So the V does work! The Systems Engineering V diagram shows all the previously mentioned principles of design verification being differentiated from product verification, iteration equalling the first design verification and definition parameters at one level becoming the requirements at the next level down. These principles easily map onto the traditional Systems Engineering V. Viewed in this way, it is an enhancement of the traditional V and more closely reflects the way a product evolves from requirements, through iterations of definitions, to an eventual product. Any ‘suspicious linkages’ now include the verification evidence that should be interrogated to confirm (or otherwise) the ‘suspicion’ and quantify the non-compliance. The number of links needing maintaining is also potentially reduced. Another major advantage is that the verification evidence is now visually part of the process rather than an ‘addition’. The chosen information model As indicated above, the Requirements Management process within Rolls-Royce was intended to be applicable outside the purely technical domain and thereby embrace business requirements, supply chain requirements etc equally well. It also had to be applicable at all levels from ‘the top’ layer down to the component layer. Inspecting the Systems Engineering V diagram, there is a very clear fractal. This was chosen as the information model - it is simple, completely scaleable between layers and scaleable across a whole enterprise and can be represented by a cluster of documents and/or modules in a formal Requirements Management tool. CODIFICATION IN A FORMAL PROCESS Clearly, the complete process of managing requirements consists of more than just the above information model. However, applying the above information model across a complete enterprise will ‘govern’ the Requirements Engineering aspect. Before the Requirements Engineering starts, requirements will need to be elicited and validated. The lifecycle also has to include the management of non-compliance. All aspects are shown in the process diagram. The process As can be seen, the process is conveniently divided into three distinct phases, all of which are codified in a formal, controlled Rolls-Royce Global Quality Procedure. Stakeholder Analysis and Requirements Capture There are many ‘elegant’, formal Systems Engineering tools that should be used, as appropriate, for this stage. These are not detailed here but merely acknowledged as potentially fundamental to this stage of the process. Requirements Engineering. In terms of the cascade, this is described in detail in the discussion around the Information Model. The method by which new requirements are derived as solutions to complex requirements is again, fundamentally dependent on formal Systems Engineering techniques. Documentation Structure Being pragmatic, it was accepted that it would be a cultural shift too far to manage all requirements only in a formal tool, including sign-off. It was therefore accepted that documentation would be expected. A document structure already existed Diagram showing the fractal cluster at the systems level. 24 THE SINGAPORE ENGINEER April 2012
SYSTEMS ENGINEERING The process diagram. within Programme Management and this was used as the basis for a complete landscape of requirements and definitions documentation. This landscape is seen as the minimum for a project, against which it will be audited. Additional documentation may be used as necessary and indeed, additional layers. Uncertainty, gaps and review The above process will create a landscape of compliant requirements and definitions that, if achieved, will satisfy the stakeholders. However, it is to be expected that, as the project progresses, some solutions will fall short of their requirements, presenting a gap between compliance [requirement] and status. These gaps need managing. Before a strategy for closing a gap April 2012 THE SINGAPORE ENGINEER 25
Page 1: The Magazine Of The Institution Of
Page 4 and 5: IES UPDATE Message from the Preside
Page 6 and 7: IES UPDATE Er. Ho Siong Hin Enginee
Page 8 and 9: IES UPDATE Delegations from three c
Page 10 and 11: IES UPDATE HEAL Simulation 2012 The
Page 12 and 13: COVER STORY Rolls-Royce opens new m
Page 14 and 15: COVER STORY WIDE CHORD FAN BLADE MA
Page 16 and 17: COVER STORY REGIONAL TRAINING CENTR
Page 18 and 19: AEROSPACE COVER ENGINEERING STORY S
Page 20 and 21: AEROSPACE COVER ENGINEERING STORY A
Page 22 and 23: AEROSPACE COVER ENGINEERING STORY d
Page 24 and 25: SYSTEMS COVER ENGINEERING STORY Dep
Page 28 and 29: SYSTEMS COVER ENGINEERING STORY Com
Page 30 and 31: CIVIL & STRUCTURAL ENGINEERING My W
Page 32 and 33: CIVIL & STRUCTURAL ENGINEERING Pung
Page 34 and 35: CIVIL & STRUCTURAL ENGINEERING CONS
Page 36 and 37: CIVIL & STRUCTURAL ENGINEERING The
Page 38 and 39: PROJECT APPLICATION One Central Mac
Page 40 and 41: PROJECT APPLICATION In the club hou
Page 42 and 43: EVENTS Singapore Airshow 2012 attra
Page 44 and 45: NEWS COVER STORY Enhanced suites an
Page 46 and 47: NEWS COVER STORY Environmental biot
Page 48 and 49: NEWS COVER STORY My Waterway@Punggo
Page 50 and 51: NEWS COVER STORY BCA’s plan for i
Page 52: 50 THE SINGAPORE ENGINEER April 201

THE SINGAPORE ENGINEER - Institution of Engineers Singapore

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?