Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  BRD: existing functionality requirements
Previous Previous
 
Next Next
New Post 3/20/2015 9:21 AM
User is offline Leyla
1 posts
No Ranking


BRD: existing functionality requirements 

If you work on the project that leverages the existing functionality how do you document the existing requirements pertaining to your project because they are part of the overall workflow? For example, you develop requirements for a new screen of the existing process. How much of the existing requirements you need to specify in your BRD so it will be helpful for testers to read a full story and see all workflows to write accurate and complete test cases. This question applies to a waterfall environment.

Thank you.

 
New Post 3/23/2015 7:51 AM
User is offline NitWitNick
259 posts
5th Level Poster


Re: BRD: existing functionality requirements 
"develop requirements for a new screen of the existing process"

When you say the screen is new for an existing process ... are you just adding some new fields to the screen using current programs without any changes to a process but just want to display some extra data (ie: building a car ... the process stays the same, but you want to now display the name of a tire or radio manufacturer and the cost of those items ... but no changes to the actual building process).


If So ...

I would probably just create an "AS-IS" and "TO-BE" Process Improvement document.


"AS-IS" - The understanding of the current screen operations and performance.

"TO-BE" - The Goal, What do we want the new screen to do.


I'd make prints of the old screen and drawings of the new screen so the changes could be seen by your stakeholders and approved.


For your developers, You could identify the current screen fields that would be used from the old system (the same data from current programs could be used to populate those fields) ... and then the requirements for the New Fields you want to add to the screen and the detail you need to specify for developer understanding if a calculation needs to be performed (if I use this stereo FM radio, the cost of the car would be $25 higher or just AM, no additional cost ... but remember, the building process remains the same ... just a part change.).


If Possible (it should be with a test environment), I would run testing in parallel (old screen / new screen) with test scenarios and validate the answers between the two to make sure the old fields were still correct and any new fields you added worked, calculated and displayed as needed.


Let me know if I'm Right, Close or You're Fired ... 
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  BRD: existing functionality requirements

Community Blog - Latest Posts

Ashish Adike
Ashish Adike
As a Business Analyst, very often we get into a situation where the Project requires multiple IT Products to be evaluated before implementation and might seek Business Analyst’s recommendation for the same. With the ever-growing range of Products in the market and the marketing promotions associated with some of the products, it’s very ...
0 Responses
m_anst
m_anst
What Does Success Look Like? I challenge Business Analysts to view requestors’ requirements as an opportunity to define success. Too often, teams fall into a trap focused on requestors’ prescriptive requirements that are meant to serve as roadmaps for developers and testers. When you limit your view of requirements to this prescripti...
0 Responses
Mariya Kotsupalova
Mariya Kotsupalova
They say the best criteria of Business Analyst’s success are a happy customer (business) and a happy engineering team. But what does it mean? How can we break down happiness and measure it? These are precisely the questions my 8 BAs team and I tried to answer this year. The result was a surprisingly efficient pair of surveys we developed and ...
0 Responses






Copyright 2006-2020 by Modern Analyst Media LLC