SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 6 of 6
  1. #1
    Member
    Join Date
    Feb 2001
    Location
    Pflugerville, TX, USA
    Posts
    74
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Requirements Test Process

    Hi,

    We all know that we "should" test requirements prior go into development phase.

    Here is my questions:
    (1) How many companies really perform the QA role on requirements prcoess phase? If your company do what's the method you apply?

    (2) In our organization that our project manager work closely with business users. They produce the requirements. From QA point of view, if project management have produce the requirements. Do we still need test their requirements? If yes, how?

    Thanks.

    In advance.

    David

  2. #2
    Moderator Joe Strazzere's Avatar
    Join Date
    May 2000
    Location
    USA
    Posts
    13,170
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    1 Thread(s)
    Total Downloaded
    0

    Re: Requirements Test Process

    <BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by davidchen_00:
    Hi,

    We all know that we "should" test requirements prior go into development phase.

    Here is my questions:
    (1) How many companies really perform the QA role on requirements prcoess phase? If your company do what's the method you apply?

    (2) In our organization that our project manager work closely with business users. They produce the requirements. From QA point of view, if project management have produce the requirements. Do we still need test their requirements? If yes, how?

    Thanks.

    In advance.

    David
    <HR></BLOCKQUOTE>

    In companies I have worked for, we have "tested" requirements by reviewing them in the early stages - before development began.

    We were looking for clarity, internal consistency, conflicts with current architecture, conflicts with other requirements, missing pieces, and testability.

    The requirements were used as input into our testing process, as well as into the developers process. Once we were all in agreement with the requirements, we were able to give our manpower estimates and begin to develop a reasonable schedule.

    The times when we short-cut this process always seemed to end up in missed deadlines, poor alignment between requirements and delivered features, bug-fix releases, and other painful events.

    It doesn't matter who produces the requirements, they still neeed to be reviewed by everyone before an effective release can be planned.

    -joe
    Joe Strazzere
    Visit my website: AllThingsQuality.com to learn more about quality, testing, and QA!

  3. #3
    Senior Member
    Join Date
    Nov 2000
    Location
    pittsburgh,pa..usa
    Posts
    315
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Requirements Test Process

    Here David, read this post:
    http://www.qaforums.com/boards/ubb/F...ML/000528.html

    ------------------
    -- Mike --
    -- Mike --

  4. #4
    Senior Member
    Join Date
    Mar 2000
    Location
    Sweden
    Posts
    252
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Requirements Test Process

    <BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by mracicot:
    Here David, read this post:
    http://www.qaforums.com/boards/ubb/F...ML/000528.html

    <HR></BLOCKQUOTE>

    Mike,

    I can't really see the connection between the thread you pointed out and the questions here.

    But in addition to the good answers earlier here I would like to add one thing.

    To us, requirements are very, very important.
    However, at a starting point the requirements actually is provided by the customer. Unfortunately, it is almost impossible to try to learn the customer how to write good requirements. Therefore, all customer requirements are re-designed into a system requirement specification that are used internally. Our system is then tested against that spec.

    The problem with this is that it takes many, many discussions and questions to actually figure out what the customer really wants.
    Fortunately, many times they simply leave it to us to specify what they mean

    Regards Björn


    ------------------

  5. #5
    Senior Member
    Join Date
    Dec 1999
    Location
    Chicago,Illinois,USA
    Posts
    2,537
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    1 Thread(s)
    Total Downloaded
    0

    Re: Requirements Test Process

    David,

    I highly recommend the book "Software Requirements" by Karl Wiegers and you also might want to check out his Web site: http://www.processimpact.com/

    Also you say that requirements should be tested before going into the development phase. That depends on how your organization does things. Normally the design phase follows the requirements phase and the design is based off of use cases that are generated during requirements. Following the design phase is the functional specification phase which feeds right into the coding.

    Regarding your specific questions:

    <BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>(1) How many companies really perform the QA role on requirements prcoess phase? If your company do what's the method you apply?<HR></BLOCKQUOTE>

    I am not sure how many companies actually do this. Of the many that I have been to this has been a process that I had to institute. As far as the method applied, it is basic analysis of the requirements. Consistency, non-ambiguity, etc. are all important things to check for. Also make sure that the requirements are testable. This does not mean "testable with a tool" necessarily, but rather testable in the sense that the next phase (perhaps design) can begin its work with what is stated in the requirements, meaning a design can be fleshed out from what is required. If you jump right to coding, then your requirements are sort of acting like a functional specification as well which means they should provide enough that development knows what to code.

    <BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>(2) In our organization that our project manager work closely with business users. They produce the requirements. From QA point of view, if project management have produce the requirements. Do we still need test their requirements? If yes, how?<HR></BLOCKQUOTE>

    Just because project management produces them does not mean they are necessarily right. Many times they might not consider certain types of users (for example, users that do not have broadband for Web applications or users that do not have Windows 2000 for 2000-specific applications). Sometimes accessibility issues are not considered - such as making the product available to users with diabilities.

    QA should work very closely with project management in these cases. (This is also the case if you have marketers deriving the requirements or product designers. The titles really do not matter, just the process.) Working closely means that the requirements are not too detailed but also not detailed enough. Again, the criterion I use is that they are testable in some fashion. Meaning that you can test the deliverable (in this case, the finished requirements specification) so as to determine if the next phase in the cycle can use that deliverable to do its job.

  6. #6
    Senior Member
    Join Date
    Feb 2001
    Location
    Arlington, VA, USA
    Posts
    317
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Requirements Test Process

    Most requirements tracking systems also have a "feedback" or "comments" portion that can be used to submit QA feedback on the requirements to the requirements master. In my experience, a meeting is always held to go through each comment and determine a course of action. This meeting usually contained all members of the CCB, plus or minus some additional folks.

    If you don't use a management tool to track requirements, figure out some way to submit the feedback and proceed with the meeting.

    Its seems like its a lot more work, but it actually makes life easier down the road, just like all the books say.

 

 

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 9.09%
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 11:48 AM.

Copyright BetaSoft Inc.