[news.eclipse.technology.epf] Re: Attaching documents to Guidance

["Jan Fincher" <myjunk68@xxxxxxxxx>]

I see the table did not translate well.  Here it is again in plain text:

Checklist can reference:

Concept

Example

Guideline

Reusable Asset

Supporting Material

Whitepaper



Concept can reference:

Checklist

Example

Guideline

Reusable Asset

Supporting Material

Whitepaper

Concept



Example can reference

Checklist

Concept

Guideline

Reusable Asset

Supporting Material

Whitepaper



Practice can reference all other guidance types, but as references, not as 
guidances



Estimating Guideline: haven't done this one yet

Report: haven't done this one yet

Reusable Asset: haven't done this one yet

Supporting Material: haven't done this one yet

Template: haven't done this one yet

Term Definition: haven't done this one yet

Tool Mentor: haven't done this one yet

White Paper: haven't done this one yet



"Jan Fincher" <myjunk68@xxxxxxxxx> wrote in message 
news:ftgdjl$18l$1@xxxxxxxxxxxxxxxxxxxx
> I've had some of the same questions and have found a few answers.
>
> One way you can attach a document to a guidance that doesn't have a field 
> for it is to create a link to the document in the Main Description field.
>
> I don't know if the "rules" for which guidances can be attached to which 
> other guidances or elements can be changed or bent.
>
> I do know that the documentation (online help file) has a page that shows 
> which elements have associations with other elements.  It's the page 
> entitled Associations Impacted by Variability.  It shows both incoming and 
> outgoing associations.
>
> I was not able to find any guidance to guidance documentation, so I 
> decided to test it out myself and see what was possible.  I've not 
> finished, but here's what I've found so far:
>
>      Guidances of type.
>     can reference guidances of type.
>
>      Checklist
>     Concept
>
>      Example
>
>      Guideline
>
>      Reusable Asset
>
>      Supporting Material
>
>      Whitepaper
>
>      Concept
>     Checklist
>
>      Example
>
>      Guideline
>
>      Reusable Asset
>
>      Supporting Material
>
>      Whitepaper
>
>      Concept
>
>      Estimating Guideline
>     <haven't done this one yet>
>
>      Example
>     Checklist
>
>      Concept
>
>      Guideline
>
>      Reusable Asset
>
>      Supporting Material
>
>      Whitepaper
>
>      Practice
>     All other guidance types, but as references, not as guidances
>
>      Report
>     <haven't done this one yet>
>
>      Reusable Asset
>     <haven't done this one yet>
>
>      Supporting Material
>     <haven't done this one yet>
>
>      Template
>     <haven't done this one yet>
>
>      Term Definition
>     <haven't done this one yet>
>
>      Tool Mentor
>     <haven't done this one yet>
>
>      White Paper
>     <haven't done this one yet>
>
>
>
> (If the table doesn't come through very well, let me know and I'll 
> reformat it).
>
> Regards,
>
> J Fincher
>
>
> "Sevon" <sevon.vanbebber@xxxxxxxxxxxxxx> wrote in message 
> news:a8106114ad5ef68e5aaa7d9b2fadf78f$1@xxxxxxxxxxxxxxxxxx
>> How would I go about attaching a document to a checklist, or a concept, 
>> or support material, or any other guidance that doesn't have a field for 
>> attaching documents?
>> I understand that there are templates to fill out, but I am developing 
>> process for a company that has years and years of process documentation, 
>> and I do not have enough time to convert over everything, especially 
>> spreadsheets, and PowerPoints.
>> I also considered making guidance "examples" of checklists, or 
>> "whitepapers" for a concept and attaching those to other guidance's, but 
>> you cannot attach all guidance to all other guidance.
>>
>> Is there a simple way around this?  or maybe can the next release of EPF 
>> allow for attaching documents to all guidance?  Also, are all of these 
>> "rules" of which guidance can be attached to which types of other 
>> guidance, and/or tasks, tools, roles, and work products documented and 
>> available?
>>
>> Thanks for your help,
>> Sevon
>>
>
>