Re: FW: [epf-dev] Conference Call to Review Development Discipline

[Bruce Macisaac <bmacisaa@xxxxxxxxxx>]

I have added a calendar entry for the
development review at 8amPST Wed May 24

We can use this callin.

Toll-free dial-in: 1-877-421-0014
Toll/International dial-in: 1-770-615-1376
Tie-line dial-in: 421-0014
Participant passcode: 722417

Bruce MacIsaac
Manager - RUP/SUMMIT Method Content
bmacisaa@xxxxxxxxxx
phone: (408)863-8718

"Brian Lyons" <blyons@xxxxxxxxxxxxx>

05/19/2006 11:44 AM

To	Bruce Macisaac/Cupertino/IBM@IBMUS
cc
Subject	FW: [epf-dev] Conference Call to Review Development Discipline

hiho,
 
Can you take a look at the
content and the comments and perhaps add a comment regarding the “Entity-Boundary-Control
Breakdown” item being a
concept or a practice?
 
       
                     
                    -----------
b

---

From: epf-dev-bounces@xxxxxxxxxxx
[mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of Brian Lyons
Sent: Friday, May 19, 2006 2:43 PM
To: Eclipse Process Framework Project Developers List
Subject: [epf-dev] Conference Call to Review Development Discipline
 
hiho,
 
We are going to have a conference call to
review the architecturally-significant updates to the Development discipline
at 8am pacific time on Wednesday, May 24.  (Bruce, can you update
the Yahoo calendar?  Ricardo, can you send out the detailed call logistics?)
 
The open bug for these changes is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=141692.
 Attached to the bug is a plug-in with the latest proposed Development
discipline.
 
This is about identifying the pieces, their
names and brief descriptions, and their relationships.  Any steps
or other content in there is leftover from the IBM donation and not part
of this review.
 
This review does not take into consideration
the issue of reconsidering the breakdown of process elements as being in
Architecture vs. Analysis & Design vs. Development.  Any changes
along those lines can be at the proper discipline level while the Development
method authoring package remains as-is.
 
           
                     
             -------------- b_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev