[Oslc-Automation] Oslc-Automation Digest, Vol 16, Issue 12

[Daniel Berg]

It is fine if the AutomationRequest has a relationship to the
AutomationResult versus the other way around if we want to avoid dangling
references. However, we need to have the request parameter values captured
and stored with the AutomationResult for audit purposes.

Regards,
Daniel Berg
STSM, Master Inventor
IBM Rational, DevOps Lead
1-919-486-0047 | Cell: 1-919-637-8570



From:	oslc-automation-request at open-services.net
To:	oslc-automation at open-services.net,
Date:	06/29/2012 09:02 AM
Subject:	Oslc-Automation Digest, Vol 16, Issue 12
Sent by:	oslc-automation-bounces at open-services.net



Send Oslc-Automation mailing list submissions to
		 oslc-automation at open-services.net

To subscribe or unsubscribe via the World Wide Web, visit

http://open-services.net/mailman/listinfo/oslc-automation_open-services.net

or, via email, send a message with subject or body 'help' to
		 oslc-automation-request at open-services.net

You can reach the person managing the list at
		 oslc-automation-owner at open-services.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Oslc-Automation digest..."


Today's Topics:

   1. Automation Request and Automation Result		 relationship
      (Pramod K Chandoria)


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

Message: 1
Date: Fri, 29 Jun 2012 20:53:28 +0530
From: Pramod K Chandoria <pchandor at in.ibm.com>
To: oslc-automation at open-services.net
Subject: [Oslc-Automation] Automation Request and Automation Result
		 relationship
Message-ID:

<OFA9A8D774.2569045D-ON65257A2C.0053A6C0-65257A2C.00549D69 at in.ibm.com>
Content-Type: text/plain; charset="us-ascii"

Hi All,
I am thinking that most often the lifecyle of Automation Request is
limited and once automation is complete, can be purged from the system any
time.
Whereas the lifecycle of AutomationResult is often longer (if not
forever).
Currently the proposed relationship between AutomationRequest and
AutomationResult is from AutomationResult to AutomationRequest.

This relationship will become dangling reference very soon once request is
deleted. I am thinking rather have reference from Automation Request to
Automation Result.
As long request is in the system, we can track result from it. Result
anyhow have reference to the AutomationPlan and we can always track what
was executed to generate it.

Any thoughts?

-|- Pramod Chandoria
Advisory Software Engineer
Rational Quality Manager
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120629/3962b257/attachment-0001.html
>

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

_______________________________________________
Oslc-Automation mailing list
Oslc-Automation at open-services.net
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net


End of Oslc-Automation Digest, Vol 16, Issue 12
***********************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120629/6e126be5/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120629/6e126be5/attachment.gif>