![]() |
Telelogic Rhapsody (steve huntington) | ![]() |
Topic Title: Modelling non-functional requirements? Topic Summary: Created On: 14-Sep-2005 14:30 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I don't know whether this forum is really being used, so I've posted a question that might have been better here at [url]http://www.ilogix.com/forum/showthread.php?t=831[/url] in the hope that it may attract a reply.
|
|
![]() |
|
![]() |
|
Hi Charlie,
The primary goal of the Harmony-SE process is the analysis of functional requirements. My observation is, that often people focus too early on the non-functional requirements, without exactly knowing what the required functionality will entail. Part of the requirements analysis is the identification of non-functional requirements ? especially the design-relevant quality of service (QoS) requirements ( Note: timing may be a functional or a QoS requirement). Typically, the non-functional requirements are marked as such in the requirements taceability tool. You may also enter these in requirements diagrams, but I personally question the value of these diagrams in the case of large systems. An alternative would be to capture non-functional requirements as constraints in sequence diagrams or add them to the associated operational contracts as tags. The advantage of the latter approach is, that it allows easy traceability when it comes to the architectural design. Let me know, if you have further questions Thanks Peter |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.