Home > Archive > Software Engineering > August 2006 > RUP "Business Vision Document" and "Vision Document"
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
RUP "Business Vision Document" and "Vision Document"
|
|
| mlittle84@hotmail.com 2006-08-08, 9:59 pm |
| Hello,
I am a bit  , but could some-one explain what is the difference
between the RUP "Business Vision Document" and "Vision Document"? How
are they used, and what audience are they aimed at?
Best Regards,
Mike Little
| |
| Mister UML 2006-08-14, 9:59 pm |
|
mlittle84@hotmail.com wrote:
> Hello,
> I am a bit , but could some-one explain what is the difference
> between the RUP "Business Vision Document" and "Vision Document"? How
> are they used, and what audience are they aimed at?
>
> Best Regards,
>
> Mike Little
Mike--
Looking at it one way, these are interchangeable terms. Strictly
speaking, a business vision statement reflects the vision of a project
that doesn't reflect any system awareness, whereas a vision statement
contains some kind of overall vision of system architecture and such.
Hope this helps.
Kendall Scott
kendallvscott@optonline.net
| |
| mlittle84@hotmail.com 2006-08-30, 7:00 pm |
| Thanks Kendal,
My understanding is the 'Business Vision' document encapsulates the
stakeholder needs of the business, a statement of the Business Problem,
that the Business wants to solve, without bias to a particular
soluation; whereas, the 'Vision document', is the next iteration after
the 'Business Vision' document, and that it contains the solution
features. Is that correct? If so, should the 'Vision document', be
biased towards a particular solution, or should be design detail
agnostic? Do you need both a Business Vision document, and a Vision
document, or could just get by with a Business Vision document?
Best Regards,
Mike Little
Mister UML wrote:
> mlittle84@hotmail.com wrote:
>
> Mike--
>
> Looking at it one way, these are interchangeable terms. Strictly
> speaking, a business vision statement reflects the vision of a project
> that doesn't reflect any system awareness, whereas a vision statement
> contains some kind of overall vision of system architecture and such.
>
> Hope this helps.
>
> Kendall Scott
> kendallvscott@optonline.net
| |
|
| mlittle84 wrote:
> My understanding is the 'Business Vision' document encapsulates the
> stakeholder needs of the business, a statement of the Business Problem,
> that the Business wants to solve, without bias to a particular
> soluation; whereas, the 'Vision document', is the next iteration after
> the 'Business Vision' document, and that it contains the solution
> features. Is that correct? If so, should the 'Vision document', be
> biased towards a particular solution, or should be design detail
> agnostic? Do you need both a Business Vision document, and a Vision
> document, or could just get by with a Business Vision document?
You are reminding me of the Dilbert episode where the boss complains about
all the Dilbert comics hung on the walls of cubicles.
Wally points to one and says, "Look! It's our Mission Statement!"
--
Phlip
[url]http://c2.com/cgi/wiki?Z Land[/url] <-- NOT a blog!!!
|
|
|
|
|