Thank you, Craig! I will check the final version when V2.0 is published.

I just started reading; do not have much thought yet. So far I do have a question in Chapter 1 - Introduction, section 1.3.2. Maybe I have not got the whole meaning yet or I missed something. I think the requirement level is a little confusion and different from what we normally use in our daily business life. Is my understanding correct as follow?

Business Requirement ( in document )  = Project Charter

Stakeholder Requirement ( in document ) = Business Requirement

Functional Requirement ( in document ) = Functional Specifications

Non-functional Requirement ( in document ) = Non-functional Specifications

Thanks,    - Irene

sarbjit wrote I guess Sr. member of this forum can give us clear picture of  difference between Business Requirement and Stakeholder Requirement

Hi Sarbit & Irene,

Let me jump in here with a cuple of comments and questions.

Firstly stakeholder and business requirements are not mutuially exclusive.  Secondly their definition is not fixed.  It depend on the context and you have o go some way to defining that context for your project.  BAs are all about effective communication and just becasue we here at Modern Analyst have a set of agreed terms doesn't mean the people at your workplacce are using the same ones.

Now, what would a stakeholder requirement be?  It begs the question; what is a stakeholder.  Irene, Srabit, anyone else - can you give an answer for us before we continue?

Hi Sarbit,

Yes a stakeholder is someone who has a stake in the project; that is they have some sort of interest in what the project team will do or what it will produce.

An example is a project auditor.  THe auitor wants the project to have followed cerain procedures and fulfilled certain oligations along the way to delivering the outcome.

Another example is a user - who will have to adapt the way they work to accomodate a new IT system.

Different stakeholders have different importances to project teams.  This importance is usually assessed in relation to their ability to help or hinderthe project team achieving the outcomes.

And so to my point: Different stakeholder requirements have different importances, and sometimes they even clash.  An example of this is stakeholders to a sales campaign project.  The manager of sales ants the campaign to generate as many new leads as possible.  The manager of sales fulfilment will want the campaign to only achieve moderate results so that they ability to fulfil orders is not stretched beyond capacity.

Now Sarbit (and Irene) - how do you think stakeholder requirements need to be managed in business requriement documents?