Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [epf-dev] Agenda for February F2F

I'll volunteer to take the lead on the three items I suggested:

*	Simplify explanation of use cases -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=168275
*	Redefine relationship between design and implementation -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=168725
*	Redefine architectural approach -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=165258

 

I'll set up meetings this week to have early discussions about these. We
can probably use the regular Tuesday architecture meeting to talk about
that item, if it's OK with Mark.

 

Thanks,

Jim

____________________

Jim Ruehlin, IBM Rational

RUP Content Developer

Eclipse Process Framework (EPF) Committer www.eclipse.org/epf

email:   jruehlin@xxxxxxxxxx

phone:  760.505.3232

fax:      949.369.0720

 

________________________________

From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Per Kroll/Cupertino/IBM
Sent: Sunday, January 28, 2007 11:12 AM
To: Eclipse Process Framework Project Developers List
Cc: Eclipse Process Framework Project Developers List;
epf-dev-bounces@xxxxxxxxxxx
Subject: [epf-dev] Agenda for February F2F

 


Hi, 

I consolidated all suggestions for agenda items in the attached, and
added info from Chris on attendance, etc. 

This meeting has a promis to be one of the most well-attended of our
meetings so far. I would also like to make it the most productive by
having somebody to lead and prepare in advance each topic so we have a
succinct articulation of the 
a) Problem at hand 
b) Dicussions so far 
c)  Alternatives to choose from 

I would also like us to have some prep meetings before the F2F. I do not
want to start every discussion from the beginning, but rather e.g.
assume that people are familar with what has been done so far in each
domain. 

We will also need to divide into groups, and have each group solve some
of the problems and report back. Otherwise, we will not be able to
handle all issues. 

I suggest that as a next step, you all review the agenda, and add things
missing. Please offer to lead (and prepapre for) a discussion. I
suggested some names on several of the issues, but feel free to
volunteer for anything you are passionate about. 

Please also indicate if there are topics you are more or less interested
in discussing. I will later in the week propose some further
refinements, and potentially breakouts, etc., 

Cheers 

Per Kroll
STSM, Manager Methods: RUP / RMC
Project Lead: Eclipse Process Framework
Rational Software, IBM Corp
(M) 408-219-2963 



"Scott W. Ambler" <swa@xxxxxxxxxxxx> 
Sent by: epf-dev-bounces@xxxxxxxxxxx 

01/27/2007 08:09 AM 

Please respond to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx>

To

"Eclipse Process Framework Project Developers List"
<epf-dev@xxxxxxxxxxx> 

cc

 

Subject

Re: [epf-dev] Some proposed agenda items for February F2F

 

 

 





I would add:
1. Resolve the relationship between Test , acceptance tests within
Requirements, and developer tests within Implementation
2. Confirm the overall vision of OpenUP within the team.  I suspect that
we've strayed a bit.
3. Discuss status of all plug-in work (agile data techniques, agile
modeling, scrum, ....).

- Scott

On Sat, January 27, 2007 7:23 am, Ana Valente Pereira said:
> And also:
>
> * brainstorming the OpenUP lifecycle diagram ( 171152)
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=171152>
> * review what goes into OpenUP basic deployment ...(167904 and 140074)
> ... and where does it fit on the lifecycle
>
> Ana
>
> Jim Ruehlin wrote:
>
>>Hello all,
>>
>>
>>
>>I don't know if there's an agenda yet for the February EPF F2F, so
here
>>are a few topic recommendations:
>>
>>
>>
>>*                 Redefining the architectural approach in OpenUP
>>(https://bugs.eclipse.org/bugs/show_bug.cgi?id=165258). We've been
>>having some small-group discussions about this and it would be useful
to
>>report on progress so far. There are still issues to be resolved so
this
>>may be a good opportunity for a breakout.
>>*                 Redefining the relationship between design and
implementation
>>(https://bugs.eclipse.org/bugs/show_bug.cgi?id=168725). Brian and I
have
>>had a couple of informal discussions but there's still a lot to do in
>>defining this. It may be useful to discuss the intent of this issue in
>>the main meeting, and have a breakout to make further progress. It may
>>also be useful to have a joint breakout with the architecture and
>>design/implementation groups to discuss interlocked issues.
>>*                 Simplify the explanation and description of use
cases
>>(https://bugs.eclipse.org/bugs/show_bug.cgi?id=168275).  The problem
is
>>that use cases require a learning curve that many developers,
>>particularly in small teams, are not willing to dedicate themselves
to.
>>User stories try to address this issue, but they can be ambiguous, and
>>they can define solutions rather than requirements. Can we come up
with
>>a simpler way of doing use cases, and what would be the cost of doing
>>so? Should we move to user stories instead, or leave things as is?
>>
>>
>>
>>-        Jim
>>
>>
>>
>>____________________
>>
>>Jim Ruehlin, IBM Rational
>>
>>RUP Content Developer
>>
>>Eclipse Process Framework (EPF) Committer www.eclipse.org/epf
>>
>>email:   jruehlin@xxxxxxxxxx
>>
>>phone:  760.505.3232
>>
>>fax:      949.369.0720
>>
>>
>>
>>
>>
>>----------------------------------------------------------------------
--
>>
>>_______________________________________________
>>epf-dev mailing list
>>epf-dev@xxxxxxxxxxx
>>https://dev.eclipse.org/mailman/listinfo/epf-dev
>>
>>
> _______________________________________________
> epf-dev mailing list
> epf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/epf-dev
>


Practice Leader Agile Development, IBM Rational
http://www-306.ibm.com/software/rational/bios/ambler.html

Refactoring Databases (
http://www.ambysoft.com/books/refactoringDatabases.html ) is now
available.

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

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

Back to the top