The authors propose a formal method for writing behavioral requirements usable by a broad spectrum of system engineers. The method includes a requirement template with specific syntax to include all relevant aspects of a behavioral requirement, a “black box” approach to system analysis and a unique organization for requirements specification.
Members-Only Content
This content is restricted to members only.
You must be logged in with an active membership to access this page.
Please click the link below to log in. If you do not have an account or your membership is inactive, you may need to register or renew it.