[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [epf-dev] Re: [Bug 135698] Add Architecture as an input workproduct to design_solution
|
Mark,
I couldn't agree more with you. Although OPF takes a method engineering
viewpoint, provides a highly complete repository of free and open source
reusable method components to build an endeavor-specific method, and
allows the people playing the process engineer complete freedom as to
which method components they select to rule, I doubt that any
non-trivial system has a non-trivial architecture and therefore the
method constructed should almost always contain the architecture itself,
architectural diagrams, models, and documents, the architect role, the
architecting discipline, and many of its associated tasks. Any method
that ignores architecture is asking for trouble.
Don Firesmith
OPFRO Chair
Mark.Dickson@xxxxxxxxx wrote:
Well, now that's 2 of you. Scott Ambler said the same thing, so I will consider myself out-voted (see my earlier post in reply to Scott on epf-dev).
My view is that there is always an architecture - it's just a matter of how fully anf formally (or informally) defined it is. Architecture will, in some way, always inform or constrain design activities - otherwise, design is happening in some abstract sense, without context. I simple terms, this is just saying that you have some idea of what you're going to do before you do it).
The example I gave previously is that the simple decision to use object technology (including design techniques and principles) is an architecturally significant one, so forms part of the architecture.
Still, it's looks as though this may just be my view :-)
Cheers
Mark
Mark Dickson
Principal Architect
0780 1917480
----- Original Message -----
From: bugzilla-daemon
Sent: 04/09/2006 02:18 AM
To: mark.dickson@xxxxxxxxx
Subject: [Bug 135698] Add Architecture as an input workproduct to design_solution
https://bugs.eclipse.org/bugs/show_bug.cgi?id=135698
Product/Component: EPF / Content
------- Comment #1 from dj@xxxxxxxxxxxxxxxx 2006-04-08 21:25 -------
Agree, but Architecture should be an optional input, as in some cases there may
be no Architecture (described). I can also imagine situations where we may want
to describe the architecture once we have designed and implemented the
solution.
DJ
