![]() |
Telelogic Rhapsody (steve huntington) | ![]() |
Topic Title: Modelling non-functional requirements? Topic Summary: Created On: 14-Sep-2005 14:28 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Those interested in the use of Rhapsody for Systems Engineering will probably have read the white papers and viewed the webinars on this site -- these deal in some detail with relating requirements to use cases, modelling the interactions, flowing down the functional requirements, etc.
But Quality of Service requirements, though alluded to in a few places, do not seem to get the attention that has been given to functional requirements. Counting requirements on a new system being designed just now, I find that the specification contains over 40% non-functional requirements -- these cover timing, frequencies, size, weight, safety, reliability etc. They are generally not the sort of thing that is appropriately covered in use cases. Of course, we can start entering these in requirements diagrams (and hope to use v6.1 parametric diagrams soon), but they are not really considered in the process presentations. We might, for example show flow-down of system requirements to requirements anchored to the subsystems and, left to myself, I could probably invent some model structure that would accomodate this. But I'd rather follow some accepted way of doing it than make it up as I go. Does anyone know of any guidance on modelling of the non-functional requirements? |
|
![]() |
Telelogic Rhapsody
» Rhapsody Category » Rhapsody
»
Modelling non-functional requirements?
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.