Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[epf-dev] RE: epf-dev Digest, Vol 4, Issue 24

"The architect" is exactly what causes people to be confused - that's the
problem with roles. So if we could define the *competencies* that make up
what the architect does (or should do) we could hopefully dispel the
misconceptions surrounding this role.

DJ



-----Original Message-----
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On
Behalf Of epf-dev-request@xxxxxxxxxxx
Sent: Monday, April 10, 2006 7:52 AM
To: epf-dev@xxxxxxxxxxx
Subject: epf-dev Digest, Vol 4, Issue 24

Send epf-dev mailing list submissions to
	epf-dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
	https://dev.eclipse.org/mailman/listinfo/epf-dev
or, via email, send a message with subject or body 'help' to
	epf-dev-request@xxxxxxxxxxx

You can reach the person managing the list at
	epf-dev-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific than
"Re: Contents of epf-dev digest..."


Today's Topics:

   1. RE: Re: [Bug 135698] Add Architecture as an input
      workproductto design_solution (steve)
   2. RE: Re: [Bug 135698] Add Architecture as an	input
      workproductto design_solution (Mark.Dickson@xxxxxxxxx)
   3. New Task name for "Create Architectural Proof of Concept"
      (Mark.Dickson@xxxxxxxxx)
   4. Invitation: BUP Architecture SIG Audio Conference,	11 April
      17:00 GMT (Mark.Dickson@xxxxxxxxx)


----------------------------------------------------------------------

Message: 1
Date: Sun, 9 Apr 2006 09:53:30 -0700
From: "steve" <steve@xxxxxxxxxxxxxxxxx>
Subject: RE: [epf-dev] Re: [Bug 135698] Add Architecture as an input
	workproductto design_solution
To: "'Eclipse Process Framework Project Developers List'"
	<epf-dev@xxxxxxxxxxx>
Message-ID: <001101c65bf6$2231f6a0$6401a8c0@STEVESTOSHIBA>
Content-Type: text/plain;	charset="us-ascii"

"An architect is an architect by any other name" - with my apologies to the
Bard...

Whether we officially acknowledge and name an architecture role or not
during development tasks, architectural decisions are still being made.
Someone will partition the system into sub-systems, someone will decide on
the technical deployment, someone will decide on the APIs. There is still an
architectural role whether these decisions are made by coercion or
consensus.  

I know UP is an architecture centric methodology, but I have never been
comfortable with the architecture role because in many projects I have
observed the architecture role lead to a caste system where there were
architects who created lovely UML models and then there were the great
unwashed masses of developers who had to try and somehow implement these
castle in sky. For a lot of projects that I have consulted to we did away
with the architectural role and created a "project engineer" who was charged
with maintaining the vision and served as both the developer of last resort
and arbitrator of disputes. 

So where am I go with this? In my opinion, whether or not we specify the
architecture role as part of the development task in my mind is irrelevant.
However, what I think this discussion brings to the fore front is that we
must emphatically emphasize in the BUP that roles are just that, roles.
Especially in a small project. There may not be one person with the specific
job title of Architect, or project manager, or even developer. People will
move fluidly from roll to roll depending on the task they are performing.
This is something that we should consider building into the collaborative
principles.

Best regards,
Steve

-----Original Message-----
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On
Behalf Of Mark.Dickson@xxxxxxxxx
Sent: Sunday, April 09, 2006 1:12 AM
To: bugzilla-daemon; epf-dev@xxxxxxxxxxx
Cc: dj@xxxxxxxxxxxxxxxx
Subject: [epf-dev] Re: [Bug 135698] Add Architecture as an input
workproductto design_solution

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



-- 
Configure bugzilla e-mail:
https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are a voter for the bug, or are watching someone who is.
You are on the CC list for the bug, or are watching someone who is.
You reported the bug, or are watching the reporter.

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





------------------------------

Message: 2
Date: Sun, 9 Apr 2006 21:17:50 +0100
From: Mark.Dickson@xxxxxxxxx
Subject: RE: [epf-dev] Re: [Bug 135698] Add Architecture as an	input
	workproductto design_solution
To: Eclipse Process Framework Project Developers List
	<epf-dev@xxxxxxxxxxx>
Cc: "'Eclipse Process Framework Project Developers List'"
	<epf-dev@xxxxxxxxxxx>
Message-ID:
	
<OF7E0863D7.623A39AA-ON8025714B.006F7EDF-8025714B.006F7F17@xxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

An HTML attachment was scrubbed...
URL:
http://eclipse.org/pipermail/epf-dev/attachments/20060409/8cafa4b9/attachmen
t.html

------------------------------

Message: 3
Date: Sun, 9 Apr 2006 23:26:29 +0100
From: Mark.Dickson@xxxxxxxxx
Subject: [epf-dev] New Task name for "Create Architectural Proof of
	Concept"
To: epf-dev@xxxxxxxxxxx
Cc: dj@xxxxxxxxxxxxxxxx
Message-ID:
	
<OF9DF3037D.3502E1B5-ON8025714B.007B4618-8025714B.007B467C@xxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

An HTML attachment was scrubbed...
URL:
http://eclipse.org/pipermail/epf-dev/attachments/20060409/cd28e0e5/attachmen
t.html

------------------------------

Message: 4
Date: Sun, 9 Apr 2006 23:51:46 +0100
From: Mark.Dickson@xxxxxxxxx
Subject: [epf-dev] Invitation: BUP Architecture SIG Audio Conference,
	11 April 17:00 GMT
To: epf-dev@xxxxxxxxxxx
Message-ID:
	
<OF1E275533.B16E9627-ON8025714B.007D9681-8025714B.007D96C9@xxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

An HTML attachment was scrubbed...
URL:
http://eclipse.org/pipermail/epf-dev/attachments/20060409/94a0da8d/attachmen
t.html

------------------------------

_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev


End of epf-dev Digest, Vol 4, Issue 24
**************************************





Back to the top