This paper provides a personal view, built from practical experience, that considers and contrasts the approaches of developing a System from a “top down” decomposition of requirements with the historical methods of designing from the “bottom up”. The former follows the purist approach assuming an all-new system development.
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.