Article by: Jorg Largent

A challenge to introducing systems engineering into established enterprises might be embedded in the uncodified manner in which the enterprises have been doing systems engineering. The development of one system is illustrative. A Virginia-based railroad developed a system using the spiral life cycle model. This development took 35 years and 10 cycles. This particular railroad was a recognized leader in developing the system in question. In and of itself, there is nothing wrong with spiral development. Part of the point of the codified (a.k.a. “classical”) systems engineering process is that an enterprise should consider the various models (or views, i.e., spiral, waterfall, incremental, prototype development, etc.) and proactively choose the one that best meets the need of the project.

A conjunctive part of this challenge might well be a culture that is “satisfied” with a 35-year process in the face of changes in the technology and in the needs that make such satisfaction unacceptable.

It should be noted that the citation of one particular history is illustrative of a challenge systems engineering professionals need to appreciate — a challenge that might well be proportional to the superiority of the engineering tradition of the enterprise.