Ba 6

Business Analyst-6
Q: Is Legacy Environment the same as the sandbox?
No Legacy Environment is not the same as Sandbox.
What we know:
1)The Sandbox Environment is also called the Testing Environment.
2) The Production Environment is also called a Live Environment/System.
Sandbox Environment:
It is something that has all the dummy data and System/Environment Created the
same as the Live/Production System/Environment to be tested and checked by a Team
of Developers and QAs, to apply various USE Cases and make changes.
Sandbox Environment is the Internal System that only employees have access to.
Staging Environment:
The Staging Environment is the replica of the Production Environment, but

for the fact of the matter it is not live running on the server and it has all the Original
Data same as the Production Environment and the User has no access to the Staging
Environment.
Midnight any appointed employee has to upload data from the live or production
Environment to the Staging Environment in bits and pieces and not all together.
Also, Staging Environment is performed or made in use before a few days or weeks
of final deployment on the server.
Also Staging Environment is something that gives you an exact idea that if
everything is okay when it comes to making use of the Live Data and Audience, so when
the final deployment is done on the live server side, it will not blow up the system
directly and everything checked enough properly to make it in use. So a backfire stage
could be handled by the Staging Environment.
Legacy System:
Legacy System is nothing but the Old Very First System back in Old Days called Legacy
System and it will still have all three different Stages, the same as Sandbox, Staging, and
Production.
IMPs:
Every Requirement has basically 3 parts in General:
1)Unique Number that should be followed in sequence or series.

2)Title or Goal.
3)Description of the requirement.
6.1.1 (Unique Number)

Display Online Banking Hyperlink: Goal or Title.
Description: The Given One.
FRD(Functional Requirement Document):
So Basically We take one Page at a time and we are writing all the changes that we want
to make for that particular page.
“What to write for what”
Others:
So every time I add the wireframe below the requirement, I want an annotation that will
Highlight the UI requirement, also known as UI Specifications.
Q: What are the characteristics of a good requirement?
A: A good requirement has the following three characteristics:
1)Is Documented Using simple verbiage and business jargon so that it gets easy to
understand the developers and other teams that come in contact with business matters.
2)Is Technically feasible.
3)Is Testable.
Technically feasible means Developers should be able to code that and understand the
documented requirement.
Testable means every requirement you write, it has to be specific to the point and should
not be using any vague verbiage.
Extras:
- "FRD Functional Requirement Document is something that is the first

deliverable of/from Business Analyst side to Developers Team".
- BA Role is not to complicate the requirement understanding, instead, it is to break

down in such a broader aspect that it possibly hovers over every minute detail and shall
pass it in a simple understandable human language and expression through their
documentation.
Q: Explain a bit about the Requirement Gathering and Analyzing phase of

SDLC?
A: In Requirement Gathering, we will have:
- Understand ‘As-is- Business’

- Read Existing Documents.
- Understand the current System either in the Sandbox Environment or in the Legacy
System.
In Analyzing(Analysis) we will have:
1) Business Rules
2) Functional Requirements (FRDs/Use Case/User Story)
3) UI requirements
Q: What does FRD contain?
A: 1) Scope
2) System(s) Impacted
3) Assumption
4) As-Is-Business(Via Activity/State/Use Case Diagram)
5) To-Be-Business(Via Activity/State/Use Case Diagram)
6) Business Rules
7) Functional Requirements
8) Wireframes
9) UI Requirements

Ba 6

Uploaded by

Copyright:

Available Formats

Ba 6

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ba 6

Uploaded by

Copyright:

Available Formats

Business Analyst-6

Q: Is Legacy Environment the same as the sandbox?

No Legacy Environment is not the same as Sandbox.

1)The Sandbox Environment is also called the Testing Environment.

2) The Production Environment is also called a Live Environment/System.

The Staging Environment is the replica of the Production Environment, but

Every Requirement has basically 3 parts in General:

1)Unique Number that should be followed in sequence or series.

6.1.1 (Unique Number)

FRD(Functional Requirement Document):

“What to write for what”

Q: What are the characteristics of a good requirement?

A: A good requirement has the following three characteristics:

- "FRD Functional Requirement Document is something that is the first

- BA Role is not to complicate the requirement understanding, instead, it is to break

Q: Explain a bit about the Requirement Gathering and Analyzing phase of

A: In Requirement Gathering, we will have:

- Understand ‘As-is- Business’

In Analyzing(Analysis) we will have:

Q: What does FRD contain?

You might also like