Hi Christine,
I think that 1&2 should be included as part of
2.1.8.2, rather than 2.4.5. The implication from my perspective is that
if the requirement is that parameters can be used to do things than the things
that they do may or may not be part of the requirements themselves. So
2.4.5 could be satisfied by allowing parameterization, but not requiring that
the “keep data”, “keep configuration” be part of the
requirements.
I think that the purpose of 2.4.5 is to support
parameterization and that the example is just one of any number of items that
could illustrate it and is therefore distracting from a requirements
perspective. And that 2.1.8.2 is to define that there are in fact
multiple uninstall scenarios which need to be defined. I’m also not
100% confident that the uninstall scenarios that I’ve defined here are in
fact comprehensive.
So I suggest that we do this instead:
2.1.8.2
The SDD specification must support classification of artifacts as user data (end product),
configuration data and program files and uninstall of defined
subsets (e.g. features or classifications) of a solution.
2.4.5 The
SDD specification must support the definition of parameters to be specified on
other deployment lifecycle operations as well as on the initial install.
With an open question as to whether the red highlights
should be in the identity section?
Regards,
Debra
From: Christine
Draper [mailto:cdraper@us.ibm.com]
Sent: Monday, March 20, 2006 6:48
PM
To: sdd@lists.oasis-open.org
Subject: RE: [sdd] Requirement
2.1.8.2
Debra,
I think (3) below is important enough to merit its own requirement - i.e. being
able to uninstall subsets (e.g. features) of a solution.
I had imagined (1) and (2) being covered by parameters on uninstall, although I
might be jumping too much to a conclusion about the solution.
How about:
PROPOSED:
2.1.8.2
The SDD specification must support uninstall of defined subsets
(e.g. features) of a solution.
2.4.5 The
SDD specification must support the definition of parameters to be specified on
other deployment lifecycle operations as well as on the initial install, e.g.
whether to leave data and/or configuration behind after uninstalling the
solution, or to delete everything.
Regards,
Christine
Senior Technical Staff Member
IBM,
1-512-838-3482 tl 678-3482
"Danielson,
Debra J" <Debra.Danielson@ca.com>
|
"Danielson,
Debra J" <Debra.Danielson@ca.com> 03/20/2006 03:48 PM |
|
If we then
eliminate 2.1.8.2, I believe that we will have to expand 2.4.5. 2.4.5 speaks to
removing data only. In alternative uninstall scenarios, I envisioned multiple
levels, for example:
1. Delete only program files, leaving data and
configuration information. (Would be possible to reinstall and retain the
configuration and user data.)
2. Delete program files
and configuration files, leaving only data behind. (I believe that this was the
intent of 2.4.5)
3. Delete some portions of
the program files, leaving behind a fully operational solution, with data and
configuration. (Less of course the deleted functionality). Obviously there
could be multiple scenarios here – defined by the systems integrator or
solution provider.
4. others?
Regards,
Debra
From: Christine Draper [mailto:cdraper@us.ibm.com]
Sent: Saturday, March 18, 2006 7:21 PM
To: sdd@lists.oasis-open.org
Subject: [sdd] Requirement 2.1.8.2
All,
Unless someone can provide concrete use cases for "alternative uninstall
scenarios" which isn't covered by the requirement 2.4.5, I propose
dropping requirement 2.1.8.2.
2.4.5 The SDD specification must support the definition of parameters to be
specified on other deployment lifecycle operations as well as on the initial
install, e.g. whether to leave data behind after uninstalling the solution, or
to delete everything.
ORIGINAL:
2.1.8.2 The SDD specification must support the definition of alternative
uninstall scenarios.
Regards,
Christine
Senior Technical Staff Member
IBM,
1-512-838-3482 tl 678-3482