Abstract
ABSTRACTStating the requirements for systems or business processes as a hierarchical collection of English text that can only be analyzed/ verified by human inspection has proven time and again to be labor intensive and generally, inadequate. Projects employing a traditional document‐centered system engineering approach have experienced significant numbers of mis‐interpretations of the customer's requirements, or late‐detected design errors results in increased costs, schedule slips, reduced capability, or canceled programs. We have historically fixed requirements problems, that should have been understood and resolved early, during integration and test where it is more costly to identify and fix. Now that computerized system engineering support tools are available on the engineer's desktop, the leading edge aerospace/commercial corporations are transitioning from a document‐centered to a model‐driven system engineering approach to developing, analyzing, and managing explicit system/process specifications. Information and operational models (of varying levels of detail) not only aid in the understanding and communication of intentions such that incorrect assumptions can be eliminated early, they directly support the development of system verification plans.
Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
