[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [epf-dev] Challenge - Five words for why architecture in OpenUP
|
That's a good call Jim. I really like that approach.
Mark
Mark Dickson
EAS Practice
Xansa
0780 1917480
*** sent from my blackberry ***
----- Original Message -----
From: Jim Ruehlin [jruehlin@xxxxxxxxxx]
Sent: 03/20/2007 04:11 PM
To: epf-dev@xxxxxxxxxxx
Subject: RE: [epf-dev] Challenge - Five words for why architecture in OpenUP
We don't mention any disciplines or practices in the other core
principles. To be consistent, we could remove the reference to
architecture and let the principle guide the reader to the discipline.
Maybe something like:
Focus on eliminating technical risk early to increase stability and
predictability.
- Jim
____________________
Jim Ruehlin, IBM Rational
RUP Content Developer
Eclipse Process Framework (EPF) Committer www.eclipse.org/epf
email: jruehlin@xxxxxxxxxx
phone: 760.505.3232
fax: 949.369.0720
________________________________
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]
On Behalf Of "Jaana Nyfjord" <jaana@xxxxxxxxx>
Sent: Wednesday, March 14, 2007 9:53 AM
To: epf-dev@xxxxxxxxxxx
Subject: [epf-dev] Challenge - Five words for why architecture in OpenUP
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
Whilst this email has been checked for all known viruses, recipients should undertake their own virus checking as Xansa will not accept any liability whatsoever.
This email and any files transmitted with it are confidential and protected by client privilege. It is solely for the use of the intended recipient.
Please delete it and notify the sender if you have received it in
error. Unauthorised use is prohibited.
Any opinions expressed in this email are those of the individual and not
necessarily the organisation.
Xansa, Registered Office: 420 Thames Valley Park Drive,
Thames Valley Park, Reading, RG6 1PU, UK.
Registered in England No.1000954.
t +44 (0)8702 416181
w www.xansa.com
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev