Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  General  Solution Testing Methodologies
Previous Previous
 
Next Next
New Post 6/2/2014 6:18 PM
Unresolved
User is offline Mark Wears Glasses
4 posts
No Ranking


Solution Testing Methodologies 
Modified By Mark Wears Glasses  on 6/2/2014 7:48:47 PM)

Hi all

I'm part of a small project that has been assigned to deliver a change to an existing software system. We've gathered requirements and produced a requirements document that was signed off by the customer, and we've also developed a solution document that has also been signed off by the customer. 

Once the development is complete, I'm in charge of testing. My question to you is, should I be testing against the requirements, the solution, or both? 

Thanks in advance. 

Mark

 
New Post 6/18/2014 3:19 PM
User is offline Chris Adams
319 posts
5th Level Poster






Re: Solution Testing Methodologies 

Hey Mark,

You should at least test against the Solution but potentially both.  A project transitions from Requirements Elicitation to Solutioning to Development/Coding.

When first gathering requirements, the solution is left undefined since there exists many ways to satisfy a requirement.  However, once the solutioning begins and the client signs off then that is what the coders should be working towards.

In an ideal world you would only test against the signed off solution.  The assumption is that before the sign-off of the Solution Document someone (client, analyst, whoever) has ensured that it met all  requirements. But this step may not have occurred.  A good analyst will determine if a requirement was missed, work to assess whether it was intentional (e.g., conversations occurred and it was deemed unnecessary), and if it was missed in error then take the necessary steps to figure out what should be done.


Chris Adams
Core Member – ModernAnalyst.com
LinkedIn Profile
 
New Post 6/19/2014 4:01 AM
User is offline Kimbo
453 posts
5th Level Poster


Re: Solution Testing Methodologies 
Modified By Kimbo  on 6/19/2014 5:05:16 AM)

Hi Mark,

Definitely test against both the requirements and the design in my opinion. Don't assume anyone has mapped the solution to the design and if they did that they did it correctly.

Kimbo

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  General  Solution Testing Methodologies

Community Blog - Latest Posts

Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...
The cloud-native application development has helped enterprises all around the globe reduce time-to-market, enhance performance, and develop agility and flexibility. Several enterprises are achieving these results by migrating their systems or traditional monolithic applications to the cloud. But to gain from the real benefits of cloud technology, ...
So you’ve found the perfect time and place to study and you’re ready to finally get some work done. You’ve pulled out your laptop, your textbook, and your notes, and four different highlighters. After five minutes of reading your textbook, you start zoning out and thinking about puppies. Then, you go on Tumblr and look at cut...

 



Upcoming Live Webinars




 

Copyright 2006-2021 by Modern Analyst Media LLC