Answer Posted / mike jr.

Large scale changes in requirements may require a separate
engineering study to understand the costs and benefits of
the proposed change. But by the wording of the question, a
decision has already been made to change the requirements.

As a requirements analyst, the first thing that I would do
is to call together the immediately impacted stakeholders in
development and test to discuss the change. I would present
the proposed change and allow for negotiation of wording.
Then I would enter a change request (CR) to document the
change and to gain approval. Once approved, I would change
the requirements document and check the changes into a
source control tool like DOORS, VSS, or ClearCase. I would
then change the status of the CR to resolved or closed.

Where can I get excellent free Business Analyst training online?

2450

---

What is your project about? What stage or phase is it currently in? What is your current role in your project?

4092

---

Explain what are the purposes of a requirements document?

676

---

Tell me difference between sap bi & business object dw/ reporting?

663

---

How do internal quality audits cover requirements management activities in the project?

2248

---

---

You run a technical support website where members post questions and answers to problems experienced and general know how. You have to provide explanations to recently posted questions. Some opf these questions need reasearch.

2269

---

Explain falls method?

642

---

Explain the contract review process followed in your project?

4143

---

How do you handle any risk that might arise due to changes in requirements?

5863

---

What and where are the policy statements for requirement management?

4976

---

How do you ensure that you are consistently meeting the requirements during various stages in the life cycle of the software product?

4275

---