SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 3 of 3
  1. #1
    Junior Member
    Join Date
    Jun 2004
    Posts
    7
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Requirement Numbering.

    Please provide information on the details of numbering a Functional Requirement.

    I am particulalry concerned about maintaining the requirements document when numerical numbers are assigned and when deletions or additions of requirements are made to the document how to handle those changes.

    Ex, REQ-1, REQ-2...REQ-n etc.

    If there is a standard approach to do this please let me know.

    Thanks.

  2. #2
    Senior Member
    Join Date
    May 2003
    Location
    New Zealand
    Posts
    232
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Requirement Numbering.

    Number them how you like but ensure they are unique, consistent and that you have catered for being able to insert new requirements amongst existing ones...
    If you delete a requirement,do not reuse the number. Leave it allocated to the deleted requirement.(otherwise you will upset the testers who reference their tests by the requirement number)
    Always inform all necessary parties when changes have been made to published requirements.

  3. #3
    Member
    Join Date
    Sep 2001
    Posts
    52
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Requirement Numbering.

    1. If you use a requirement management tool, it maintains the IDs for you automatically.

    2. If you do it manually, you can use hierarchical IDs. Save deleted IDs somewhere in the document.

    R-001 Section 1
    R-001-001 Sub-section/Requirement
    R-001-001-001 Requirement 1
    R-001-001-002 Requirement 2

    It will be easier for you to maintain IDs in a small number of requirements than in the whole document.

    3. Do it in Word, write a macro to generate non-hierarchical ID. Save the last used ID somewhere in the document.

    4. Do it in a text format, write a script that generates non-hierarchical ID. Save the last used ID somewhere in the document.


    The main idea is to not use the same ID for different requirements, that is ID should be unique for the whole life of the document.

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 10.71%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 04:18 PM.

Copyright BetaSoft Inc.