[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [epf-dev] REG: EPF Query
|
We are always looking for contributor
willing to implement importers for EPF. A Word importer plug-in for
EPF Composer would be of great value. An interest implementing one
for the project?
I understand (2) now: Agreed that
would be a good enhancement.
Btw. I think attachment fields make
sense for template, example, reusable asset, and report.
Thanks and best regards,
Peter Haumer.
______________________________________________________________
PETER HAUMER, Dr. rer. nat.
Rational Method Composer | Eclipse Process Framework
Rational Software | IBM Software Group
Tel.: +1 408 863-8716
______________________________________________________________
"Sankar, Saravanan
(Cognizant)" <Saravanan.Sankar@xxxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx
10/25/2006 00:41
Please respond to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx> |
|
To
| "Eclipse Process Framework Project
Developers List" <epf-dev@xxxxxxxxxxx>
|
cc
| <epf-dev-bounces@xxxxxxxxxxx>
|
Subject
| RE: [epf-dev] REG: EPF Query |
|
Hi Peter,
I agree totally with
you from EPF design perspective. But at the same for organizations like
us which already have rich set of processes in place with large number
of Guidance in form on word documents, power point templates, eLearnings,
etc. Converting all this in to EPF specification is really a huge task
for us. Though we are using the round about solution of giving URL’s in
the content description section of Guidance’s, looks to be a okay solution
now.
For (2) if I give the
URL in the RTE, it does not appear under Template header rather it’s displayed
in the main description header, which is a not right. Whether I upload
an attachment for templates or give an reference URL’s, it should be appearing
under the Template header.
Thanks & Regards
Saravanan.S - Process
& Quality Group
"Quality is not
an act, it's a Habit"
________________________________________________________________________________________________________________
Cognizant Technology
Solutions | Elnet Software City|
LL:+91 044-42284000 |
Vnet: 444524
| Mobile: 98840 80806
From: epf-dev-bounces@xxxxxxxxxxx
[mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of Peter Haumer
Sent: Wednesday, October 25, 2006 1:00 PM
To: Eclipse Process Framework Project Developers List
Cc: Eclipse Process Framework Project Developers List; epf-dev-bounces@xxxxxxxxxxx
Subject: RE: [epf-dev] REG: EPF Query
Hello Saravanan.
(1) is by design. The rationale for our decision to not include such a
field to guidance types such as guideline or concept was to discourage
authors to just attach the documents they have. One goal of EPF Composer
is to manage and provide content in one standard presentation and look
& feel. Attachments have their own templates and styles, cannot
be searched or indexed and required a third party viewer. If people
really need to bring in attachments they can do so as Mark described, but
a field would "say" to users that they should provide an attachment
(which we don't want) as it is the case for templates, which are really
meant to be opened in a specific CASE or WP tool. Not sure I understand
(2), but you can create URLs in the RTE as well as attachments that are
managed in the method library as resources.
Thanks and best regards,
Peter Haumer.
______________________________________________________________
PETER HAUMER, Dr. rer. nat.
Rational Method Composer | Eclipse Process Framework
Rational Software | IBM Software Group
Tel.: +1 408 863-8716
______________________________________________________________
"Sankar, Saravanan
(Cognizant)" <Saravanan.Sankar@xxxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx
10/24/2006 21:15
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] REG: EPF Query |
|
Thanks a lot for the response Mark. Even I am doing the same solution as
you suggested, but it’s not a suitable way to do it. I will raise it in
Bugzilla too…
Thanks & Regards
Saravanan.S - Process
& Quality Group
"Quality is not an act, it's a Habit"
________________________________________________________________________________________________________________
Cognizant Technology Solutions | Elnet Software City|
LL:+91 044-42284000 |
Vnet: 444524
| Mobile: 98840 80806
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Mark.Dickson@xxxxxxxxx
Sent: Tuesday, October 24, 2006 7:39 PM
To: Epf
Subject: Re: [epf-dev] REG: EPF Query
Hi Saravanan
I am working on a similar actvity with my own organisation's quality processes
(as well as working as a Committer on OpenUP).
You are correct in saying that only the Template product type provides
a form field for defining attachments. However, it is also possible to
refer to attachments as content hyperlinks to external files in the content
description. If you do this, Composer will copy the file into the method
Library you are working in, adding it to the overall source set. It is
then possible to version control the file within the cvs or clearcase repository
you may be using.
Although this does not seem as elegant as using a dedicated form field
within Composer, it offers a viable workaround.
Have you considered raising a bugzilla entry to add the functionality you
describe? It sounds like a reasonable request.
I hope this helps.
Kind regards
Mark Dickson
Mark Dickson
SE&E Practice
Xansa
0780 1917480
*** sent from my blackberry ***
----- Original Message -----
From: "Sankar, Saravanan (Cognizant)" [Saravanan.Sankar@xxxxxxxxxxxxx]
Sent: 10/24/2006 10:08 AM
To: Eclipse Process Framework Project Developers List" <epf-dev@xxxxxxxxxxx>
Cc: <epf-dev-bounces@xxxxxxxxxxx>
Subject: [epf-dev] REG: EPF Query
Hi
Can some one answer my following EPF queries?
1. Why
we are not allowing attachments for all guidance types, currently it’s
allowed only for Template Guidance type. For organizations which already
have a stable process and wants to enhance the system with EPF, it looks
to be a bottle neck since it’s not allowing me to upload the existing
guidance’s in the organization. This is more necessary because in larger
organizations guidance are off different formats like, doc, excel, e-learning
materials etc.
2. Similarly
along with attachment option, we should also provide an option to give
the URLS for the guidance’s. So that the end user will have the
freedoms to neither upload the Guidance documents nor give the URL for
the same.
Thanks & Regards
Saravanan.S - Process
& Quality Group
"Quality is not an act, it's a Habit"
________________________________________________________________________________________________________________
Cognizant Technology Solutions | Elnet Software City|
LL:+91 044-42284000 |
Vnet: 444524
| Mobile: 98840 80806
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
This e-mail
and any files transmitted with it are for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply
e-mail and destroy all copies of the original message.
Any unauthorized review, use, disclosure, dissemination, forwarding, printing
or copying of this email or any action taken in reliance on this e-mail
is strictly
prohibited and may be unlawful.
Visit us at http://www.cognizant.com |
This e-mail
and any files transmitted with it are for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply
e-mail and destroy all copies of the original message.
Any unauthorized review, use, disclosure, dissemination, forwarding, printing
or copying of this email or any action taken in reliance on this e-mail
is strictly
prohibited and may be unlawful.
Visit us at http://www.cognizant.com |
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
This e-mail and any files transmitted
with it are for the sole use of the intended recipient(s) and may contain
confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply
e-mail and destroy all copies of the original message.
Any unauthorized review, use, disclosure, dissemination, forwarding, printing
or copying of this email or any action taken in reliance on this e-mail
is strictly
prohibited and may be unlawful.
Visit us at http://www.cognizant.com |
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev