This paper examines system engineering (SE) and object-oriented (OO) methodologies and then shows both that SE is inherently OO and that OO languages such as the Unified Modeling Language (UML) may be used to document the user’s needs in a manner that can be used by developers. The paper also suggests a next generation tool concept that can be used to hold both user and developer representation of the user’s needs as an alternative to, and an improvement on, text mode “requirements”, hence increasing the reliability of the shared meaning of the user’s needs amongst all stakeholders.
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.