Premium
5.1.3 Systems Engineering an INCOSE Chapter
Author(s) -
Davies Paul
Publication year - 2006
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2006.tb02776.x
Subject(s) - capability maturity model integration , stakeholder , process (computing) , point (geometry) , systems engineering , maturity (psychological) , computer science , engineering , identification (biology) , process management , business process , risk analysis (engineering) , management science , operations research , work in process , business , operations management , mathematics , management , economics , software , political science , software development process , botany , geometry , software development , law , biology , programming language , operating system
In this paper, the setup of INCOSE UK is used as a case study ‘infrastructure project’, an example of a ‘peopled system’. To begin with, the ad‐hoc developments in the typical formation stages of an INCOSE chapter are shown, and this is used to point out the relative immaturity of the processes from a systems engineering point of view. Then we look at how we made the Chapter more self‐sustaining, by a strategic overhaul of the ‘system’ using SE principles: Business Case drivers Stakeholder Identification Stakeholder needs (requirements) analysis Architecting the Organisation Allocation of system requirements to organisational responsibilities Decision analysis of likely return on effort invested Validation and Verification via Event Q&A surveys Comparisons are drawn with IEEE1220, EIA632 and CMMI. Finally, the Metrics that we have recently started to examine are presented, as evidence of increasing maturity of the process.