Premium
Starting at the Finish Line
Author(s) -
Armstrong James R.
Publication year - 1999
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.1999.tb00296.x
Subject(s) - schedule , computer science , cover (algebra) , risk analysis (engineering) , finish line , engineering , business , mechanical engineering , operating system , race (biology) , botany , biology
The front end of the program is given a lot attention in the world of systems engineering. For instance, requirements writing is a favorite subject. The back end activities are usually included to the extent of making sure the requirements cover them appropriately. Otherwise, the post‐design activities are often left to be addressed in a just‐in‐time fashion. The most critical activity of this period, and indeed the program, has to be customer acceptance. Waiting until the time of acceptance to address the issues is high risk. Even the standards in use and development keep the user at arms length. There are many lessons learned that substantiate this as a high risk approach and provide better approaches. This paper takes a look at the current status and brings these lessons learned together to identify early tasks that should be included in programs to reduce the risk, schedule and cost of non‐acceptance by the customer.