Home » Archived » EPF » Problems when exporting data (WBS, actors) from EPF composer
| Problems when exporting data (WBS, actors) from EPF composer [message #30861] |
Tue, 20 March 2007 19:37  |
Eclipse User |
|
|
|
Originally posted by: schierlm-usenet.gmx.de
Hi all,
I'd like to export data from a process which is modeled in EPF composer so
that I can use them in another program. I am especially interested in the
WBS of one delivery process and for each breakdown step the list of
involved actors (but getting more data never hurts).
Exporting to XML seemed to be a good idea, but there are a few problems.
First, the format is good for process developers since you can see all the
method plugins and how which one changed the content, but it seems to be
not so easy to parse it to a "unified" view of one delivery process.
My biggest problem currenlty: there are several <ReferencedMethodPlugin>
or <MethodPackageSelection> referencing an ID that does not occur anywhere
else in the XML file. How to parse them? Is there some "master file" where
those should be resolved from?
For example, in the exported OpenUP XML file there is a
<MethodPackageSelection>_0UCrYMlgEdmt3adZL5Dmdw</MethodPackageSelection >
but no method package of that ID.
So, how would you solve this problem? Use the published HTML and try to
parse that? (I have some experience in collecting structured data from
unstructured HTML pages, but I don't like to do that since it will break
whenever someone of the EPF developers changes the HTML format) Or try to
parse the original method plugin files before they have been exported?
Are there any (free or commercial) libraries available that can parse those
exported XML files and extract the information I need?
Thanks in advance,
Michael
|
|
|
| Re: Problems when exporting data (WBS, actors) from EPF composer [message #30897 is a reply to message #30861] |
Wed, 21 March 2007 01:25  |
 Peter Haumer
Messages: 228
Registered: July 2009 |
Senior Member |
|
|
Hello Michael.
If you are only interested in the WBS then you do not need to resolve the
MethodPackageSelection values (looks like a problem with the OpenUP
configuration, though; it might have some inconsistencies as we are using
that since the earliest prototypes of EPF Composer and OpenUP).
If you are really just interested in the WBS what about parsing the MS
Project XML file that we export? The involved roles (not actors) are
exported there as well as resources and linked to tasks via the assignment
tags.
Another solution for you would be to create your own export plug-in for EPF
Composer that creates exactly the XML that you want, doing a copy and modify
of our code.
Peter.
"Michael Schierl" <schierlm-usenet@gmx.de> wrote in message
news:etpd68$eu6$1@utils.eclipse.org...
> Hi all,
>
> I'd like to export data from a process which is modeled in EPF composer so
> that I can use them in another program. I am especially interested in the
> WBS of one delivery process and for each breakdown step the list of
> involved actors (but getting more data never hurts).
>
> Exporting to XML seemed to be a good idea, but there are a few problems.
> First, the format is good for process developers since you can see all the
> method plugins and how which one changed the content, but it seems to be
> not so easy to parse it to a "unified" view of one delivery process.
>
> My biggest problem currenlty: there are several <ReferencedMethodPlugin>
> or <MethodPackageSelection> referencing an ID that does not occur anywhere
> else in the XML file. How to parse them? Is there some "master file" where
> those should be resolved from?
>
> For example, in the exported OpenUP XML file there is a
> <MethodPackageSelection>_0UCrYMlgEdmt3adZL5Dmdw</MethodPackageSelection >
> but no method package of that ID.
>
> So, how would you solve this problem? Use the published HTML and try to
> parse that? (I have some experience in collecting structured data from
> unstructured HTML pages, but I don't like to do that since it will break
> whenever someone of the EPF developers changes the HTML format) Or try to
> parse the original method plugin files before they have been exported?
>
> Are there any (free or commercial) libraries available that can parse
> those
> exported XML files and extract the information I need?
>
> Thanks in advance,
>
> Michael
|
|
|
| Re: Problems when exporting data (WBS, actors) from EPF composer [message #30932 is a reply to message #30897] |
Wed, 21 March 2007 19:19 |
| Eclipse User |
|
|
|
Originally posted by: schierlm-usenet.gmx.de
Hello Peter,
Thank you for your answer.
On Tue, 20 Mar 2007 18:25:23 -0700, Peter Haumer wrote:
> If you are only interested in the WBS then you do not need to resolve the
> MethodPackageSelection values
And the ReferencedMethodPlugin references not either? Could you please tell
me quickly how to do that (in a general case)? When looking at the XML, the
WBS looks splitted over several method plugins and I don't really know how
to combine them. I had a look at the current SPEM 2.0 draft (or whatever it
is currently called on its way from draft to standard) and understand
concepts in there like variability kinds, but am not really sure how to
look up the object which is "variated" by that variability kind and where
to start so that I get the "final" delivery process.
> (looks like a problem with the OpenUP
> configuration, though; it might have some inconsistencies as we are using
> that since the earliest prototypes of EPF Composer and OpenUP).
The same problem (even worse) occurs in my "real world" example. It is a
process customized by a customer which is created using RMC (IBM Rational
Method Composer 7.1) and is based on the Rational Unified Process shipped
with RMC. And it appears to me that these inconsistencies are in the
original plugins and not in the added ones.
> If you are really just interested in the WBS what about parsing the MS
> Project XML file that we export? The involved roles (not actors) are
> exported there as well as resources and linked to tasks via the assignment
> tags.
Thank you, that helped me. Now i have the WBS and the roles, but only all
roles together and not split up in Main/Additional/Assisting (which is my
largest problem) and I do not get the Role Sets or the short description on
top of each role. But the latter is not that much a problem: Although there
are more roles than in OpenUP, they are still few enough so that I can look
them up by hand.
> Another solution for you would be to create your own export plug-in for EPF
> Composer that creates exactly the XML that you want, doing a copy and modify
> of our code.
I'll have a look at that solution as well. Does the license of Eclipse
require me to make the source code public if we want to distribute that to
our customers? And will it work in RMC as well as in EPF composer?
Michael
|
|
| |
| Re: Problems when exporting data (WBS, actors) from EPF composer [message #577136 is a reply to message #30861] |
Wed, 21 March 2007 01:25 |
Peter Haumer
Messages: 228
Registered: July 2009 |
Senior Member |
|
|
Hello Michael.
If you are only interested in the WBS then you do not need to resolve the
MethodPackageSelection values (looks like a problem with the OpenUP
configuration, though; it might have some inconsistencies as we are using
that since the earliest prototypes of EPF Composer and OpenUP).
If you are really just interested in the WBS what about parsing the MS
Project XML file that we export? The involved roles (not actors) are
exported there as well as resources and linked to tasks via the assignment
tags.
Another solution for you would be to create your own export plug-in for EPF
Composer that creates exactly the XML that you want, doing a copy and modify
of our code.
Peter.
"Michael Schierl" <schierlm-usenet@gmx.de> wrote in message
news:etpd68$eu6$1@utils.eclipse.org...
> Hi all,
>
> I'd like to export data from a process which is modeled in EPF composer so
> that I can use them in another program. I am especially interested in the
> WBS of one delivery process and for each breakdown step the list of
> involved actors (but getting more data never hurts).
>
> Exporting to XML seemed to be a good idea, but there are a few problems.
> First, the format is good for process developers since you can see all the
> method plugins and how which one changed the content, but it seems to be
> not so easy to parse it to a "unified" view of one delivery process.
>
> My biggest problem currenlty: there are several <ReferencedMethodPlugin>
> or <MethodPackageSelection> referencing an ID that does not occur anywhere
> else in the XML file. How to parse them? Is there some "master file" where
> those should be resolved from?
>
> For example, in the exported OpenUP XML file there is a
> <MethodPackageSelection>_0UCrYMlgEdmt3adZL5Dmdw</MethodPackageSelection >
> but no method package of that ID.
>
> So, how would you solve this problem? Use the published HTML and try to
> parse that? (I have some experience in collecting structured data from
> unstructured HTML pages, but I don't like to do that since it will break
> whenever someone of the EPF developers changes the HTML format) Or try to
> parse the original method plugin files before they have been exported?
>
> Are there any (free or commercial) libraries available that can parse
> those
> exported XML files and extract the information I need?
>
> Thanks in advance,
>
> Michael
|
|
|
| Re: Problems when exporting data (WBS, actors) from EPF composer [message #577152 is a reply to message #30897] |
Wed, 21 March 2007 19:19 |
Michael Schierl
Messages: 2
Registered: July 2009 |
Junior Member |
|
|
Hello Peter,
Thank you for your answer.
On Tue, 20 Mar 2007 18:25:23 -0700, Peter Haumer wrote:
> If you are only interested in the WBS then you do not need to resolve the
> MethodPackageSelection values
And the ReferencedMethodPlugin references not either? Could you please tell
me quickly how to do that (in a general case)? When looking at the XML, the
WBS looks splitted over several method plugins and I don't really know how
to combine them. I had a look at the current SPEM 2.0 draft (or whatever it
is currently called on its way from draft to standard) and understand
concepts in there like variability kinds, but am not really sure how to
look up the object which is "variated" by that variability kind and where
to start so that I get the "final" delivery process.
> (looks like a problem with the OpenUP
> configuration, though; it might have some inconsistencies as we are using
> that since the earliest prototypes of EPF Composer and OpenUP).
The same problem (even worse) occurs in my "real world" example. It is a
process customized by a customer which is created using RMC (IBM Rational
Method Composer 7.1) and is based on the Rational Unified Process shipped
with RMC. And it appears to me that these inconsistencies are in the
original plugins and not in the added ones.
> If you are really just interested in the WBS what about parsing the MS
> Project XML file that we export? The involved roles (not actors) are
> exported there as well as resources and linked to tasks via the assignment
> tags.
Thank you, that helped me. Now i have the WBS and the roles, but only all
roles together and not split up in Main/Additional/Assisting (which is my
largest problem) and I do not get the Role Sets or the short description on
top of each role. But the latter is not that much a problem: Although there
are more roles than in OpenUP, they are still few enough so that I can look
them up by hand.
> Another solution for you would be to create your own export plug-in for EPF
> Composer that creates exactly the XML that you want, doing a copy and modify
> of our code.
I'll have a look at that solution as well. Does the license of Eclipse
require me to make the source code public if we want to distribute that to
our customers? And will it work in RMC as well as in EPF composer?
Michael
|
|
| |
Goto Forum:
Current Time: Tue Apr 23 07:51:50 GMT 2024
Powered by FUDForum. Page generated in 0.03053 seconds |
] 
Search
Help
Register
Login
Home
