Paradigm Shift International 1-575-770-7101 |
OtherWise |
Features: Home | Library |
A new guest appears frequently, and the prior wisdom is
archived in the Library. |
Featured Guest Speaker Posted: February, 26, 2005 Jack Ring
Requirements Management Obscures Systems Engineering
The reason people do not see the need for Systems Engineering (SE) is because they are being told, and apparently believe, that Requirements Elicitation/ Engineering/Management, hereinafter called RM, is a viable way to traverse rapidly from ‘Project Day One’ to ‘Start of Development.’ Such siren song is powerful, indeed. It isn’t as if SE and RM were compared and SE lost. It isn’t as if RM is portrayed as the adequate, accurate and timely documentation of SE decisions. The problem is that SE is not mentioned or is misrepresented as a UML activity, while RM is portrayed as the key to initializing and ensuring development. This paper seeks to alert the reader about how a preoccupation with requirements can suppress the appreciation of any perceived need for the due process of systems engineering. Further, this paper recommends ways for embedding the RM into SE practices. Although important today, these ideas become critical to success in the forthcoming era of model-based systems engineering. |
Would you like to offer some advice or add to the dialog
on this subject? Your sending of a comment automatically grants us permission to edit and
post at our discretion. Comments will be forwarded to the author. Send your
comment to
and indicate which Guest Speaker article your comment addresses. ========= Reply =========================
|
Features: Home | Library Rick Dove, |