Re: [epf-dev] Challenge - Five words for why architecture in OpenUP

["VAIDYA Kirti" <KVAIDYA@xxxxxxxxxxxx>]

Say, that'd translate to:

Risk - the architecture will soon be obsolete

Opportunity - let's move to SOA

Sounds good!

--------------------------
Sent from my BlackBerry Wireless Handheld


-----Original Message-----
From: epf-dev-bounces@xxxxxxxxxxx
To: Eclipse Process Framework Project Developers List
CC: Eclipse Process Framework Project Developers List
Sent: Fri Mar 16 12:23:41 2007
Subject: Re: [epf-dev] Challenge - Five words for why architecture in OpenUP

Great. Thank you Scott. I'll add your proposal to the list.

I'll take a chance to propose two ideas:

Focus on architecture to exploit risk as an opportunity to advance current
capabilities in the project.

or

Focus on capitalizing on risk as an opportunity to advance current
capabilities.

Generally, people seem to forget about the positive side of risk. Risk and
opportunity go hand in hand. Risk taking is essential to progress.
However, the trick is to find balance. What if we try to formulate our
core principle along these lines ... ?

Have a great weekend!
/Jaana Nyfjord



> Explore/articulate the architecture to address technical risks early?????
>
> - Scott
> On Wed, March 14, 2007 11:52 am, Jaana Nyfjord said:
>> Hi everyone!
>>
>> I need to collect some proposals and then get a vote on the best
>> proposal
>> to be able to close the bug concerning the formulation of the
>> architecture
>> principle in OpenUp.
>>
>> A summary of the discussion so far, shows that
>>
>> - this principle needs be formulated in the same way as the other three
>> principles, i.e. “focus on … to …” ?
>>
>> But, we have NOT agreed on:
>>  - what the fundamental purpose and meaning of architecture and
>> architecture-centric is and why this must be focused on in OpenUp
>>
>> There are currently four different suggestions of how to present this
>> principle:
>>
>> 1. "Focus on articulating the architecture"
>> 2. "Focus on the architecture to promote a shared view of the solution"
>> 3. "Focus on articulating the architecture to retire risks early in the
>> project lifecycle."
>> 4. "Focus on the architecture to retire risks early."
>>
>> To resolve this bug, please consider the existing suggestions and let us
>> know with which proposal you agree, or propose a new core principle.
>>
>> I expect to have your proposals by Tuesday next week (March 20) to set
>> up
>> a vote and then resolve this bug before the end of M6.
>>
>> Looking forward to some challenging creativity,
>> Jaana Nyfjord
>>
>>
>> _______________________________________________
>> epf-dev mailing list
>> epf-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/epf-dev
>>
>
>
> Practice Leader Agile Development, IBM Rational
> http://www-306.ibm.com/software/rational/bios/ambler.html
>
> Refactoring Databases (
> http://www.ambysoft.com/books/refactoringDatabases.html ) is now
> available.
>
> _______________________________________________
> epf-dev mailing list
> epf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/epf-dev
>


_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
 
Confidentiality Statement:
 
This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by return email.
-----------------------------