Difference between revisions of "Derived Requirement (glossary)"

From SEBoK
Jump to navigation Jump to search
Line 1: Line 1:
''<blockquote>Constraint stated during the design activities which arise as a result of the selected solution (for example, a necessary mean or resource related to a technology, or an interface between two components of different sub-systems).  (Faisandier 2011 (expected--not yet published)) </blockquote>''
+
''<blockquote>Constraint stated during the design activities which arise as a result of the selected solution (for example, a necessary mean or resource related to a technology, or an interface between two components of different sub-systems).  (Faisandier 2012) </blockquote>''
  
 
====Source====
 
====Source====

Revision as of 02:29, 11 September 2012

Constraint stated during the design activities which arise as a result of the selected solution (for example, a necessary mean or resource related to a technology, or an interface between two components of different sub-systems). (Faisandier 2012)

Source

Faisandier, A. 2012. Systems Architecture and Design. Belberaud, France: Sinergy'Com.

Discussion

Scott Jackson comments:

This definition is not wrong: it is just a very narrow definition of derived requirements. I suggest the following two:

"Those characteristics typically identified during synthesis of preliminary product or process solutions and during related trade studies and verifications." (INCOSE Glosssary of terms -1998)

However the best definitions have to to with the hierarchical nature of systems. The following is adapted from Wasson (2006):

"a lower level performance based sibling action decomposed from an abstract parent requirement. The decomposed sibling action constitutes satisfactory accomplishments of the parent action."

In short a derived requirement is any requirement that occurs at one level below the parent requirement on the system hierarchy. The derived requirement may be mathematically determined from the parent requirement. For example, the energy that a brake must absorb in a car can be determined from the weight of the car, the speed of the car, and the required stopping distance.



SEBoK v. 1.9.1 released 30 September 2018

SEBoK Discussion

Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.

If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.

blog comments powered by Disqus