Premium
7.2.3 Is it only Systems Engineers that do Systems Engineering?
Author(s) -
Hoyle Tim A.
Publication year - 2001
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2001.tb02312.x
Subject(s) - confusion , conjunction (astronomy) , hierarchy , process (computing) , computer science , identification (biology) , requirements engineering , system of systems , software engineering , engineering management , software , systems engineering , engineering , systems design , psychology , physics , botany , astronomy , economics , biology , programming language , operating system , psychoanalysis , market economy
Misunderstanding and confusion surround the use of the words “system” 1 and “systems” in conjunction with engineers and engineering. Some engineers describe themselves as systems engineers but does this tell us what they actually do? Some organisations describe themselves as producing software systems; does this mean they need only software engineers to do this? The words “system” and “systems” are all‐embracing terms which at the corporate level can usefully indicate an ability to take on large complex engineering tasks but when used at a more local level can obscure and confuse an individual's roles and tasks. Such confusion hampers communication, understanding of project responsibilities, allocation of project resources and identification of recruitment needs. This paper summarises how a business formed from many legacy organisations is adopting a common engineering process model and language to describe its engineering activities. It concludes that the use of the qualifier “systems” is not helpful in conjunction with the individual engineer. There are two reasons for this: ‐ i) systems engineers require different skills in their various roles and ii) engineers need to do systems engineering whatever their level in the project hierarchy.