Ricardo
You're absolutely right. This definitely rules out "Define the
Architecture" as a candidate Task name.
I take your point about the Inception/Elaboration emphasis. Maybe we
can discuss at the call tomorrow?
regards
mark
Mark Dickson
SAE Practice
m 0780 1917480
w <https://extranet.xansa.com/,DanaInfo=www.xansa.com+>www.xansa.com
e <mailto:mark.dickson@xxxxxxxxx>mark.dickson@xxxxxxxxx
-----epf-dev-bounces@xxxxxxxxxxx wrote: -----
To: Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx>
From: Ricardo Balduino <balduino@xxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx
Date: 04/10/2006 06:55PM
Subject: Re: [epf-dev] Proposing to rename Task "Analyze the
Architecture" to"Outline the Architecture"
Mark.
There's already an activity in Elaboration called 'Define the
Architecture' which encompasses two tasks (Analyze the Architecture
and Refine the Architecture). How would you rename the task
"Analyze.." in this scenario?
As a matter of fact, the task "Analyze the Architecture" itself is
performed in Inception and Elaboration and does not bring in itself
all the responsibility of defining the architecture. That's why we
have proposed an activity in Inception to deal with architectural PoC
and one in Elaboration to define the baseline of the architecture.
If folks aren't comfortable with the name 'Analyze Architecture',
maybe 'Outline the Architecture' would be an option, but it has to
clarify that when performed in Inception, it relates to outlining the
architectural PoC (or solution shape?) of the system to-be and when
performed in Elaboration, it relates to the actual architecture of
the system being created.
Cheers,
Ricardo Balduino
Senior Software Engineer
IBM | RUP Team | EPF Committer
Phone: 1 (408) 863-5019 (TL: 560-5019)
www.ibm.com
www.eclipse.org/epf
Mark.Dickson@xxxxxxxxx
Sent by: epf-dev-bounces@xxxxxxxxxxx
04/10/2006 02:49 AM
Please respond to
Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>
To
epf-dev@xxxxxxxxxxx
cc
Subject
[epf-dev] Proposing to rename Task "Analyze the Architecture" to
"Outline the Architecture"
Hello again
Another one from the minutes of the architecture SIG meeting of 2/22.
The comment was raised that "Analyse Architecture" might not be a
good name for the activity.
For background, the text from the minutes reads:
"Is the word ?Analyze? too provocative? Should we say ?Define?? We
need to investigate if we can demonstrate that we can align with
?Serendipitous Architecture?. So perhaps we need to make sure our
verb can work with a ?found? architecture that one just stumbles on
while walking through the woods."
The brief description of "Analyze Architecture" reads
"Define a candidate architecture for the system based on experience
gained from similar systems or in similar problem domains. Define the
architectural patterns, key mechanisms, and -- where applicable --
modeling conventions for the system."
I suspect that the name "Analyze the Architecture" comes from the old
RUP activity "Architectural Analysis" - which (IMHO) referred to an
analysis of the *requirements* from an architectural viewpoint so
that the first steps could be taken towards establishing the
architecture. The current BUP name suggests that the architecture is
the subject of the analysis effort, rather than the requirements. Of
course, the brief description makes it plain, but the task name
should also be clear.
So, on this basis, renaming "Analyze the Architecture" to "Define the
Architecture" seems reasonable to me. (But wait! I'm not done yet.
Keep reading...)
However, a problem arises for me in that there is the possibility
that this will be possibly be viewed by some as a
"define-the-complete-architecture-in-precise-detail-in-one-go" Task.
This is definitely not my intention.
The good thing about "Achitectural Analysis" is that it is obviously
*not* a precise or complete activity in this regard. The bad thing is
that it does not conform to the "strong-verb-followed-by-noun" naming
convention.
So how does this relate to "Define the Architecture"?
<https://extranet.xansa.com/,DanaInfo=www.dictionary.com+>www.dictionary.com
gives 3 definitions of "Define";
1.
a. To state the precise meaning of (a word or sense of a
word, for example).
b. To describe the nature or basic qualities of; explain:
define the properties of a new drug; a study that defines people
according to their median incomes.
2.
a. To delineate the outline or form of: gentle hills that
were defined against the sky.
b. To specify distinctly: define the weapons to be used in
limited warfare.
3. To give form or meaning to: ?For him, a life is defined by
action? (Jay Parini).
When considering "Define the Architecture" as the new name for this
Task, I go with definitions 1b and 2a. The concern I have is whether
this will be clearly understood by everyone from just the name of the
Task, without reading the description.
The alternative, for me, is "Outline the Architecture." This is the
name that I propose.
Thanks for making it this far through the email :-)
I'd welcome any comments on this.
regards
Mark
Mark Dickson
SAE Practice
m 0780 1917480
w <https://extranet.xansa.com/,DanaInfo=www.xansa.com+>www.xansa.com
e <mailto:mark.dickson@xxxxxxxxx>mark.dickson@xxxxxxxxx
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
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
<https://extranet.xansa.com/mailman/listinfo/epf-dev,DanaInfo=dev.eclipse.org,SSL+>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
