Figure 5 - uploaded by Mike Ryan
Content may be subject to copyright.
![Life cycle processes roles and relationships [3].](profile/Mike-Ryan/publication/270219283/figure/fig2/AS:669521245388813@1536637712448/Life-cycle-processes-roles-and-relationships-3.png)
Source publication
![Figure 5: Life cycle processes roles and relationships [3].](profile/Mike-Ryan/publication/270219283/figure/fig2/AS:669521245388813@1536637712448/Life-cycle-processes-roles-and-relationships-3_Q320.jpg)
The purpose of ISO/IEC 15288:2008(E) (ISO/IEC 15288) is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a system, and to ‘... enable [the] user community to evolve towards fully harmonized standards’. In order to achieve this purpose, the standard is positioned...
Similar publications
![Figure 1: An example of a context diagram from the INCOSE SEHBK [1].](profile/Mike-Ryan/publication/270219287/figure/fig1/AS:646095734587392@1531052635024/An-example-of-a-context-diagram-from-the-INCOSE-SEHBK-1_Q320.jpg)
![Figure 5: N 2 Chart [1]](profile/Mike-Ryan/publication/270219287/figure/fig5/AS:646095734575113@1531052635501/N-2-Chart-1_Q320.jpg)
The INCOSE Systems Engineering Handbook (INCOSE SEHBK) aims to ‘provide a description of key process activities performed by systems engineers’ through providing ‘an authoritative reference to understand the discipline...’ [1]. The target audience includes experienced systems engineers as well as new systems engineers and those from other disciplin...
Citations
... The limited visual aids in ISO/IEC 15288 do have some utility and probably support reasonable transfer of knowledge to experienced practitioners, but the standard is largely text-based which means that it is very hard to visualise how the processes are related to each other.Figure 2 [3] shows a diagram that draws upon the content of ISO/IEC 15288 and supplements it with additional information.Figure 2 This diagram provides a first-level 'map' of the system life cycle processes that acts as a framework or key to develop further understanding. The diagram therefore acts as a summary of how, generically, the system life cycle processes might interact and be applied. ...
Although the rapid increase in communications connectivity between project, program and portfolio decision makers will bring many advantages, the full benefit of such connectivity will not be realised until there is seamless connectivity between all those responsible for the delivery of a project. The seamless integration of effort is seriously hampered by the lack of a universally agreed set of responsibilities for all those involved in project delivery, particularly the domains of business management, project management, systems engineering, and operations. This paper proposes that ISO/IEC 15288:2008(E) (ISO/IEC 15288) [1] provides a very useful framework within which to examine the principal responsibilities of each of the domains for the various activities involved in project delivery. The paper provides a visualisation of ISO/IEC 15288 that assists in illustrating the various responsibilities—in particular, the knowledge areas of the Guide to the Project Management Body of Knowledge (PMBOK® Guide) [2] are mapped on to standard’s processes.
