Premium
2.1.5 Does Object‐Oriented System Engineering Eliminate the Need for Requirements?
Author(s) -
Kasser Joseph
Publication year - 2002
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2002.tb02443.x
Subject(s) - unified modeling language , computer science , software engineering , user requirements document , meaning (existential) , object oriented programming , user story , programming language , requirements engineering , object oriented analysis and design , representation (politics) , software development , software , psychology , psychotherapist , politics , political science , law
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.