This paper suggests that many system development problems are due to the inadequacies of the mandated notations being used to support systems analysis and design An executable “behavior diagram” notation is proposed for describing system functionality which eliminates the deficiencies of the existing system analysis notations, yet can be displayed in those notations to strengthen the Systems Engineering process. The way in which this notation supports a separation of concerns for attacking large problems is also described.
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.