RE: Requirement 2.1.1.3

["Danielson, Debra J" <Debra.Danielson@ca.com>]

Current:

 

2.1.1.3    The SDD specification must support the ability for the author to define deployment lifecycle operations on common or shared components, regardless of the packaging that contains it.

 

Proposed:

2.1.1.3  The SDD specification must support the ability for the author to define sufficient information to support lifecycle operations on common or shared components.

2.1.1.3.1        The SDD specification must allow the definition of lifecycle operations on common or shared components from any package.

 

Regards,

Debra

 

 

---

From: Danielson, Debra J
Sent: Tuesday, February 21, 2006 9:34 AM
To: 'Randy George'
Subject: RE: TC Action Item

Hi Randy,

 

The objective of this requirement was to insure that information necessary to install, configure, upgrade, update, and uninstall shared common components could be included with any package, not just the one that delivered it.

 

So there are two points in this requirement:

 

1. That shared common components can be acted upon by any solution that needs to, not just the one that delivered the component.
2. That the operations that can be defined are any / all of the lifecycle operations.

 

 

Regards,

Debra

 

 

---

From: Randy George [mailto:randyg@us.ibm.com]
Sent: Friday, February 17, 2006 10:50 AM
To: Danielson, Debra J
Subject: TC Action Item

Debra,
I have a work item to follow-up with you on clarification about the following requirement:

2.1.1.3 The SDD specification must support the ability for the author to define deployment lifecycle operations on common or shared components, regardless of the packaging that contains it.

The issue that came up with this definition was that the SDD does not define the “lifecycle operation(s)” on a common or shared component.  Was the “spirit” of this requirement to state that the SDD must support the ability to define content that is appropriate for various lifecycle operations?  For example, you can have content that is provided to “upgrade” something vs other content that is provided to install a fresh copy.    Or, is there a different spirit that you were trying to describe?

Regards,
Randy George

Senior Technical Staff Member
Provisioning Architecture
Tivoli Software, IBM Software Group
Austin, TX  
(512) 838-0752     T/L 678-0752