Eclipse Community Forums: EPF » EPF 1.2 Released!

Help

Home

Home » Archived » EPF » EPF 1.2 Released!

Show: Today's Messages :: Show Polls :: Message Navigator

EPF 1.2 Released! [message #36349]

Thu, 02 August 2007 15:53

Per Kroll

Messages: 60
Registered: July 2009

Member

Hi,

I want to congratulate the team to yesterday's release of EPF 1.2, which you
can download on
http://www.eclipse.org/epf/downloads/tool/epf1.2.0_downloads .php
and invite the broader community to leverage all of the hard work.

- EPF 1.2 contains 2 components: OpenUP 1.0 and EPF Composer 1.2.
- 29 committers and 13 contributors built the product.
- 631 bugs and enhancements were done to EPF Composer, and 416 bugs and
enhancements to OpenUP.

EPF Composer 1.2 - New Features and Key Improvements
- Improved Diagram Editor
- Diagram editor has been completely reimplemented.
- Provides swimlanes, control flow labels, free-form drawing, and font
styles.
- Files can be saved in GIF, JPG, or BMP format.
Improved Rich Text Editor
- Font family and size can be changed.
- Content cut from Microsoft Word can be pasted as plain text.
- Links and images can be added in the HTML view.
- Improved HTML error markers and correction features.
Improved Configuration Editor
- Processes can be fine-tuned by adding or removing categorized
elements.
- Improved configuration error reporting for Method Configurations and
Method Libraries.
- Current view is highlighted in configuration editor.
- Configuration views can be ordered.
Improved Process Editor
- Activities are displayed with indented and outdented elements.
- All tasks at any level can be suppressed.
- Activities can have multiple descriptors.
Additional platform support
- Vista
- Internet Explorer 7
- Mozilla FireFox 2
- Subversion
- Eclipse 3.3
Other Improvements
- New plug-in naming convention allows plug-ins to be displayed in
hierarchical lists.
- Published sites on application servers can implement server-based
search.
- GUIDs are no longer present in published filenames.
- A new variability type is provided: Extends and Replaces.
- Elements in categories can be ordered alphabetically, manually, or by
type.

OpenUP 1.0 - Key Characteristics
- Scope: OpenUP aims at being minimal and complete, focusing on only
fundamental content required for a development process that can be used
as-is for specific contexts. This means that we have on purpose de-scoped
many content areas, including environment, advanced configuration
management, GUI prototyping, database refactoring, and model-driven
development, among others. Those and many other content areas may later be
added as plug-ins extending OpenUP. While de-scoping we have ensured that
the resulting process is complete enough to be applied by a team to build a
software application.
- Field testing: OpenUP captures the vast experience of its authors on real
projects and borrows from many different processes, including IBM Rational
Unified Process, other variants of the Unified Process, DSDM, XP, Scrum,
Eclipse Way, Agile Model-Driven Development, and the experience of
contributors from a broad cross-section of environments. The content of
OpenUP 1.0 has been written from scratch to provide a concise and well
integrated process that takes an integrated, team-based and stakeholder
focused approach that provides a fresh perspective on software development.
OpenUP is stable enough to be used as is by project teams, and it will
continue to evolve as teams adopt it and provide feedback.
- Extensibility: Customizations via extensibility (plug-ins) are encouraged
to ease maintenance when new versions of OpenUP are released. However, we
expect to change the structure of process elements in OpenUP for the next
release to address scalability. This could mean that some restructuring of
your plug-in may be required after OpenUP has been refactored.
- Consistency: OpenUP has been collectively written by many people from a
dozen or so organizations. However, we have firmly pursued consistency in
style of writing and depth of content through copy-editing, published
authoring guidelines and extensive reviews.

This is a major step forward for the EPF project. We have something to be
very proud over!

Looking forward, we brainstormed yesterday about future potential
enhancements, and it is obvious that we have many potential exciting things
to work on, including:
- Leverage Wiki technology
- Release Scrum 1.0
- Release XP 1.0
- Refactoring and broadening of OpenUP content
We invite you and your friends and colleagues to work on these and many
other exciting capabilities moving forward.

Again, we hope you will enjoy the hard work of the team!

Per Kroll
Project Lead: Eclipse Process Framework

Report message to a moderator

Re: EPF 1.2 Released! [message #37267 is a reply to message #36349]

Thu, 09 August 2007 16:24

Eclipse User

Originally posted by: kamal.osellus.com

This is a multi-part message in MIME format.

------=_NextPart_000_000D_01C7DA80.4A2D2490
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I would like congratulate the EPF team for their effort in coming up =
with EPF 1.2. We are excited to see this focus on software process =
modeling.=20

We are working on solutions that would move any content developed using =
EPF Composer to a collaborative development environment of choice for =
enactment in live projects. The first version of this is Content Bridge =
for VSTS, a tool for moving processes from EPF Composer to Microsoft's =
Visual Studio Team System. This would enable teams that are using VSTS =
as the development environment of choice to use a methodology developed =
using EPF Composer v1.2 such as OpenUP. I believe that users will now =
have a choice that results in significant cost saving while ensuring =
wider inter-operatibility between processes and execution environments. =
Content Bridge for VSTS also offers an easy low-overhead way to move RUP =
content into VSTS.

Thanks

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

Kamal Ahluwalia

Lead System Analyst, Osellus Inc.

144 Front Street West, Suite 750

Toronto, Ontario M5J 3L7 CANADA

Tel: +1 (416) 603-6667 Ext 5063

Email: kamal@osellus.com

Blog: http://www.osellus.com/blogs/author/kamal

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

"Per Kroll" <pkroll@us.ibm.com> wrote in message =
news:f8sumd$lf7$2@build.eclipse.org...
> Hi,
>=20
> I want to congratulate the team to yesterday's release of EPF 1.2, =
which you=20
> can download on
> http://www.eclipse.org/epf/downloads/tool/epf1.2.0_downloads .php
> and invite the broader community to leverage all of the hard work.
>=20
> - EPF 1.2 contains 2 components: OpenUP 1.0 and EPF Composer 1.2.
> - 29 committers and 13 contributors built the product.
> - 631 bugs and enhancements were done to EPF Composer, and 416 bugs =
and=20
> enhancements to OpenUP.
>=20
> EPF Composer 1.2 - New Features and Key Improvements
> - Improved Diagram Editor
> - Diagram editor has been completely reimplemented.
> - Provides swimlanes, control flow labels, free-form drawing, and =
font=20
> styles.
> - Files can be saved in GIF, JPG, or BMP format.
> Improved Rich Text Editor
> - Font family and size can be changed.
> - Content cut from Microsoft Word can be pasted as plain text.
> - Links and images can be added in the HTML view.
> - Improved HTML error markers and correction features.
> Improved Configuration Editor
> - Processes can be fine-tuned by adding or removing categorized=20
> elements.
> - Improved configuration error reporting for Method Configurations =
and=20
> Method Libraries.
> - Current view is highlighted in configuration editor.
> - Configuration views can be ordered.
> Improved Process Editor
> - Activities are displayed with indented and outdented elements.
> - All tasks at any level can be suppressed.
> - Activities can have multiple descriptors.
> Additional platform support
> - Vista
> - Internet Explorer 7
> - Mozilla FireFox 2
> - Subversion
> - Eclipse 3.3
> Other Improvements
> - New plug-in naming convention allows plug-ins to be displayed in=20
> hierarchical lists.
> - Published sites on application servers can implement server-based =

> search.
> - GUIDs are no longer present in published filenames.
> - A new variability type is provided: Extends and Replaces.
> - Elements in categories can be ordered alphabetically, manually, =
or by=20
> type.
>=20
> OpenUP 1.0 - Key Characteristics
> - Scope: OpenUP aims at being minimal and complete, focusing on only=20
> fundamental content required for a development process that can be =
used=20
> as-is for specific contexts. This means that we have on purpose =
de-scoped=20
> many content areas, including environment, advanced configuration=20
> management, GUI prototyping, database refactoring, and model-driven=20
> development, among others. Those and many other content areas may =
later be=20
> added as plug-ins extending OpenUP. While de-scoping we have ensured =
that=20
> the resulting process is complete enough to be applied by a team to =
build a=20
> software application.
> - Field testing: OpenUP captures the vast experience of its authors on =
real=20
> projects and borrows from many different processes, including IBM =
Rational=20
> Unified Process, other variants of the Unified Process, DSDM, XP, =
Scrum,=20
> Eclipse Way, Agile Model-Driven Development, and the experience of=20
> contributors from a broad cross-section of environments. The content =
of=20
> OpenUP 1.0 has been written from scratch to provide a concise and well =

> integrated process that takes an integrated, team-based and =
stakeholder=20
> focused approach that provides a fresh perspective on software =
development.=20
> OpenUP is stable enough to be used as is by project teams, and it will =

> continue to evolve as teams adopt it and provide feedback.
> - Extensibility: Customizations via extensibility (plug-ins) are =
encouraged=20
> to ease maintenance when new versions of OpenUP are released. However, =
we=20
> expect to change the structure of process elements in OpenUP for the =
next=20
> release to address scalability. This could mean that some =
restructuring of=20
> your plug-in may be required after OpenUP has been refactored.
> - Consistency: OpenUP has been collectively written by many people =
from a=20
> dozen or so organizations. However, we have firmly pursued consistency =
in=20
> style of writing and depth of content through copy-editing, published=20
> authoring guidelines and extensive reviews.
>=20
> This is a major step forward for the EPF project. We have something to =
be=20
> very proud over!
>=20
> Looking forward, we brainstormed yesterday about future potential=20
> enhancements, and it is obvious that we have many potential exciting =
things=20
> to work on, including:
> - Leverage Wiki technology
> - Release Scrum 1.0
> - Release XP 1.0
> - Refactoring and broadening of OpenUP content
> We invite you and your friends and colleagues to work on these and =
many=20
> other exciting capabilities moving forward.
>=20
> Again, we hope you will enjoy the hard work of the team!
>=20
> Per Kroll
> Project Lead: Eclipse Process Framework
>=20
>=20
>
------=_NextPart_000_000D_01C7DA80.4A2D2490
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16481" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff background=3D"">
<DIV>
I =
would like=20
congratulate the EPF team for their effort in coming up with EPF 1.2. We =
are=20
excited to see this focus on software process modeling. <?xml:namespace =
prefix =3D=20
o ns =3D "urn:schemas-microsoft-com:office:office" =
/><o:p></o:p>
We =
are=20
working on solutions that would move any content developed using EPF =
Composer to=20
a collaborative development environment of choice for enactment in live=20
projects. The first version of this is <A=20
href=3D" http://www.osellus.com/products/contentbridge/contentbridge_ for_v=
sts.html">Content=20
Bridge for VSTS</A>, a tool for moving processes from EPF =
Composer to=20
Microsoft=92s <A=20
href=3D"http://msdn2.microsoft.com/en-us/teamsystem/default.aspx">Visual =
Studio=20
Team System</A>. This would enable teams that are using VSTS as the=20
development environment of choice to use a methodology =
developed using=20
EPF Composer v1.2 such as OpenUP. I believe that users will now have a=20
choice that results in significant cost saving while ensuring wider =

inter-operatibility between processes and execution environments. =
Content Bridge=20
for VSTS also offers an easy low-overhead way to move RUP content into=20
VSTS.<o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Arial','sans-serif'">Thanks<o:p></o:p>
-------------------------------------------- <SPAN=20
lang=3DEN-US style=3D"mso-ansi-language: EN-US"><o:p></o:p>
Kamal=20
Ahluwalia<o:p></o:p>
Lead=20
System Analyst,=20
Osellus Inc.<o:p></o:p>
144=20
Front Street West, Suite 750<o:p></o:p>
Toronto,=20
Ontario M5J 3L7  CANADA<o:p></o:p>
Tel:=20
+1 (416) 603-6667 Ext 5063<o:p></o:p>
Email:=20
<A =
title=3D"blocked::mailto:kamal@osellus.com
mailto:kamal@osellus.com" =

href=3D"mailto:kamal@osellus.com"><FONT=20
color=3D#0000ff>kamal@osellus.com</A><o:p></o:p>
Blog:=20
<A title=3Dblocked::http://www.osellus.com/blogs/author/kamal=20
href=3D"http://www.osellus.com/blogs/author/kamal"><FONT=20
color=3D#0000ff>http://www.osellus.com/blogs/author/kamal</A><o:p>=
</o:p>
----------------------------------------------<SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'; =
mso-ansi-language: EN-US"><o:p></o:p><FONT=20
face=3DArial size=3D2> "Per Kroll" <pkroll@us.ibm.com> =
wrote in message=20
news:f8sumd$lf7$2@build.eclipse.org... > Hi, > > I =
want to=20
congratulate the team to yesterday's release of EPF 1.2, which you =
 > can=20
download on >=20
http://www.eclipse.org/epf/downloads/tool/epf1.2.0_downloads .php > =
and=20
invite the broader community to leverage all of the hard work. > =
 >=20
- EPF 1.2 contains 2 components: OpenUP 1.0 and EPF Composer =
1.2. > - 29=20
committers and 13 contributors built the product. > - 631 bugs and =

enhancements were done to EPF Composer, and 416 bugs and > =
enhancements=20
to OpenUP. > > EPF Composer 1.2 - New Features and Key=20
Improvements > - Improved Diagram Editor >    =
-=20
Diagram editor has been completely =
reimplemented. >    -=20
Provides swimlanes, control flow labels, free-form drawing, and font =
 >=20
styles. >    - Files can be saved in GIF, JPG, or =
BMP=20
format. > Improved Rich Text Editor >    - =
Font=20
family and size can be changed. >    - Content cut =
from=20
Microsoft Word can be pasted as plain text. >    - =
Links=20
and images can be added in the HTML view. >    - =
Improved=20
HTML error markers and correction features. > Improved =
Configuration=20
Editor >    - Processes can be fine-tuned by adding =
or=20
removing categorized > elements. >    - =
Improved=20
configuration error reporting for Method Configurations and > =
Method=20
Libraries. >    - Current view is highlighted in=20
configuration editor. >    - Configuration views =
can be=20
ordered. > Improved Process Editor >    - =
Activities=20
are displayed with indented and outdented =
elements. >    -=20
All tasks at any level can be suppressed. >    - =
Activities=20
can have multiple descriptors. > Additional platform=20
support >    - Vista >    - =
Internet=20
Explorer 7 >    - Mozilla FireFox=20
2 >    - Subversion >    - =
Eclipse=20
3.3 > Other Improvements >    - New plug-in =
naming=20
convention allows plug-ins to be displayed in > hierarchical=20
lists. >    - Published sites on application =
servers can=20
implement server-based > search. >    - =
GUIDs are no=20
longer present in published filenames. >    - A new =

variability type is provided: Extends and =
Replaces. >    -=20
Elements in categories can be ordered alphabetically, manually, or by =
 >=20
type. > > OpenUP 1.0 - Key Characteristics > - Scope: =
OpenUP=20
aims at being minimal and complete, focusing on only > =
fundamental=20
content required for a development process that can be used > =
as-is for=20
specific contexts. This means that we have on purpose de-scoped > =
many=20
content areas, including environment, advanced configuration >=20
management, GUI prototyping, database refactoring, and model-driven =
 >=20
development, among others. Those and many other content areas may later =
be=20
 > added as plug-ins extending OpenUP. While de-scoping we have =
ensured=20
that > the resulting process is complete enough to be applied by =
a team=20
to build a > software application. > - Field testing: =
OpenUP=20
captures the vast experience of its authors on real > projects =
and=20
borrows from many different processes, including IBM Rational > =
Unified=20
Process, other variants of the Unified Process, DSDM, XP, Scrum, =
 >=20
Eclipse Way, Agile Model-Driven Development, and the experience of =
 >=20
contributors from a broad cross-section of environments. The content of =
 >=20
OpenUP 1.0 has been written from scratch to provide a concise and well =
 >=20
integrated process that takes an integrated, team-based and stakeholder =
 >=20
focused approach that provides a fresh perspective on software =
development.=20
 > OpenUP is stable enough to be used as is by project teams, and =
it will=20
 > continue to evolve as teams adopt it and provide =
feedback. > -=20
Extensibility: Customizations via extensibility (plug-ins) are =
encouraged=20
 > to ease maintenance when new versions of OpenUP are released. =
However,=20
we > expect to change the structure of process elements in OpenUP =
for the=20
next > release to address scalability. This could mean that some=20
restructuring of > your plug-in may be required after OpenUP has =
been=20
refactored. > - Consistency: OpenUP has been collectively written =
by many=20
people from a > dozen or so organizations. However, we have =
firmly=20
pursued consistency in > style of writing and depth of content =
through=20
copy-editing, published > authoring guidelines and extensive=20
reviews. > > This is a major step forward for the EPF =
project. We=20
have something to be > very proud over! > > Looking =
forward,=20
we brainstormed yesterday about future potential > enhancements, =
and it=20
is obvious that we have many potential exciting things > to work =
on,=20
including: > - Leverage Wiki technology > - Release Scrum=20
1.0 > - Release XP 1.0 > - Refactoring and broadening of =
OpenUP=20
content > We invite you and your friends and colleagues to work on =
these=20
and many > other exciting capabilities moving forward. > =
 >=20
Again, we hope you will enjoy the hard work of the team! > =
 > Per=20
Kroll > Project Lead: Eclipse Process Framework > >=20
 ></DIV></BODY></HTML>

------=_NextPart_000_000D_01C7DA80.4A2D2490--

Report message to a moderator

Re: EPF 1.2 Released! [message #581462 is a reply to message #36349]

Thu, 09 August 2007 16:24

Eclipse User

Report message to a moderator

Previous Topic:	extends relation
Next Topic:	OpenUP/DSDM

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 23 06:07:47 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter