![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Metrics Topic Summary: Created On: 19-Mar-2003 18:05 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Does DOORS provide a tool to collect metrics? I'd like to find the total number of objects in the database and how many contain "shall" statements.
Wayne |
|
![]() |
|
![]() |
|
As far as I know, there is no direct way to do this, but it is easy to do via DXL. See the attached "demo" script.
A few warnings... the script does no error checking, only works for formal modules, does not catch typos in sHall, and runs for a VERY long time without giving the user any feedback. I intentionally did not include a runLim line to give you a way to catch it before it runs for days. Hope this helps, Mark ------------------------- Mark Phillips mark.phillips@swri.org |
|
![]() |
|
![]() |
|
Hi Wayne,
Just a warning about relying on the criteria of searching on a word such as "shall" as a means of counting how many requirements there are - apart from the typo issue that Mark mentions, there are often cases where a paragraph may unfortunately use other potentially mandatory language such as will, must etc. Some para's may not even use any of these words, yet when you read it, it reads very much like a deliverable need or at the very least requires clarification. Suspect paragraphs are those marked as being a "Note", these often contain further criteria and should be tagged as being a requirement. Other suspects are bullet lists - a bullet list may only use the word "shall" once in the lead text, yet each related bullet item is effectively an individual requirement paragraph. It's best to create a column in DOORS where-by you analyse each object and make a decision as to whether the object is: a. A requirement, b. Is not a requirement c. Needs clarification d. Has not been assesed yet eg: Headings and front matter would most likely be assigned as not being requirement statements. The DXL script would then just count up the number of objects that have been assesed as being a requirement. ------------------------------------------ Paul Miller Tenix Specification Practices Project, Nelson House, Williamstown, Victoria, Australia, 3016. Desk Phone: +61 (0)3 9244 4078 Mobile: +61 (0)418 135 103 E-mail: paul.miller@tenix.com ------------------------------------------ ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
Hi Wayne, bearing in mind Paul's comments about what is and is not a requirement, it is worth knowing that any time you define and apply a filter ( from Tools -> Filter) then the right hand side of the screen dispays statistics on how many objects matched the filter criteria.
Regards Andrew. ------------------------- Andrew Tagg Astrium EADS Requirements Management Team Stevenage United Kingdom andrew.tagg@astrium.eads.net www.astrium.eads.net |
|
![]() |
|
![]() |
|
As suggested having a separate attribute that flags an object as a requirement (or not) is much better than relying in "shall" and "will" etc. You can then do metrics on how many "Requirements" do NOT include "shall" or "will", and how many non-requirements do.
|
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Metrics
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.