[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[epf-dev] Re: Define/Refine the Architecture
|
For Elaboration, I'd consider "Prove the Architecture".
- Scott
On Tue, July 18, 2006 6:23 pm, Mark.Dickson@xxxxxxxxx said:
> Hi Scott
>
> Good question.
>
> This got discussed in the Architecture conference call today. I think the
> naming of Define/Refine should stay for the Tasks. But I agree that there
> is room to review the names of the Activities in Inception & Elaboration.
> At the moment, the Inception Activity is "Determine Architecture
> Feasibility" and the Elaboration Activity is "Define the Architecture."
> These are (IMHO) a bit confusing when seen in context of both the Phases
> and the existing Task names.
>
> The idea of "Identify the Candidate Architecture" in Inception and
> something like "Design the Architecture" or "Specifiy the Architecture" in
> Elaboration seems more appropriate. I have to produce capability patterns
> for these soon, so it's a good time to discuss if you have any thoughts.
>
> cheers
>
> Mark
>
> Mark Dickson
> Principal Solution Architect
> SAE Practice
> m 0780 1917480
> w www.xansa.com
> e mark.dickson@xxxxxxxxx
>
Practice Leader Agile Development, IBM Rational
http://www.ambysoft.com/scottAmbler.html
Refactoring Databases (
http://www.ambysoft.com/books/refactoringDatabases.html ) is now
available.
