Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Gathering Requirements when nothing is changing in an upgrade
Previous Previous
 
Next Next
New Post 11/30/2018 5:48 AM
User is offline Fizzy 01
2 posts
No Ranking


Gathering Requirements when nothing is changing in an upgrade 

Hello Forum, 

I am a business analyst on a project that has to do with upgrading a software to a new version. The new version has capabilities to connect to the cloud, and mobile app. However, the customer said they have no plans to use any of these features and do not want it configured. They are simply migrating to a new version because the manufacturer told them they will stop supporting the older version. Aside from this, everything worked well in the older version and they will like to keep things the way it is.

I tried to elicit requirements from the stakeholders and asked probing questions but got nothing.  It appears there is no requirement to gather but I might be wrong, can you please tell me what to do as a business analyst in this case?

What requirements do I gather when nothing is intended to change?

Please advise

 
New Post 12/1/2018 1:17 AM
User is offline Mahendra B
1 posts
No Ranking


Re: Gathering Requirements when nothing is changing in an upgrade 

Hi,

I can relate to  your confusion. I had something similar with my earlier customer sometime last year. The customer was upgrading to latest version of Tibco JasperSoft only for the reason that the version in use at present would be no more supported. But once we upgraded to latest Tibco JasperSoft, the product stopped supporting the Java jdk version which was in use. And then, we also needed to upgrade Java jdk and the product worked well as expected.

So, in a nutshell, you may need to check the inter-dependency & impact between the new version and any other application the product may be already using. Generally, a software application is a complex mix of many application working together. So, inter-application support and dependency should be checked.

I agree that the above example is not exactly of business / functional requirements per se, but I believe that a BA must check & catch such holes, if possible.

Just my two cents. Thank you & good luck!

 
New Post 12/14/2018 7:13 AM
User is offline Fizzy 01
2 posts
No Ranking


Re: Gathering Requirements when nothing is changing in an upgrade 

Thanks fro your response Mahendra B

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Gathering Requirements when nothing is changing in an upgrade

Community Blog - Latest Posts

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...
Elicitation involves bringing out or drawing out information. Elicitation is a key task in business analysis as without proper elicitation the requirements for the solution to the business needs cannot be identified. 1. Not understanding underlying business need Organization’s business environment keeps changing with respect to Customer...
TOGAF is a certification that is handed over by The Open Group. It is an open corporate architecture means used to improvise upon the business effectiveness across the world’s leading business set-ups. Aspirants wishing for a successful career in corporate architecture must go for the TOGAF certification in order to explain the...

 



 

Copyright 2006-2021 by Modern Analyst Media LLC