Premium
4.3.3 How Do I Keep Track of This Study
Author(s) -
Bedocs Jozsef
Publication year - 1995
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.1995.tb01897.x
Subject(s) - work (physics) , procurement , commercialization , engineering management , requirements engineering , requirements analysis , track (disk drive) , requirements management , configuration management (itsm) , computer science , risk analysis (engineering) , process management , engineering , systems engineering , business , software , marketing , mechanical engineering , programming language , operating system
The commercialization of Systems Engineering is causing us to rethink some of the more labor intensive activities such as requirements management. Commercial engineers are already involved in cost, testing, program planning, procurement, configuration management and other activities. Relatively few organizations exist only to perform selective functions (such as CAD/CAM, computer support, facilities, etc.) Requirements management is likely to become the responsibility of the every day design engineer and therefore cannot be a massive effort. For requirements management to be used by commercial engineers, the effort must be perceived to have added value and be an overall time saver. Most engineers are extremely busy supporting currently mandated processes. More work is a hindrance, a more efficient way of doing the work already required is most helpful. We have been fairly successful in making a sound case for doing requirements management. However, the way requirements management is traditionally done is just an incredible amount of work. To become commercially palatable, requirements management must become more efficient in use of time and resources to be effectively used by design engineers.