Fw: Summary of my proposed changes to SDD Reqts

[Christine Draper <cdraper@us.ibm.com>]

All,

I'm afraid I may not be able to make the standards call. I'd appreciate it if I could get a yes or no on the proposals to resolve my action items. The only one that there is active discussion on is 2.1.8.2 (Debra in particular, please see if my rewording is OK).

Regards,
Christine


Reqt 2.1.1.6.1

Replace ORIGINAL

2.1.1.6.1 The SDD specification must support the definition of whether a component of their package should be rolled back if later components fail, and whether a particular component should cause an overall rollback if it fails to install.

with DEBRA's PROPOSAL

2.1.1.6.1 The SDD specification must support identification of components that should be rolled back if later components fail, and identification of components that should cause an overall rollback if that component fails to install.

Reqt 2.1.2.1.1

Replace ORIGINAL:

2.1.2.1.1 The SDD specification must support the definition of prioritization of alternative topologies.


with PROPOSED:

2.1.2.1.1 The SDD specification must support the definition of alternative target environments.


Reqt 2.1.4.1

Replace ORIGINAL:

2.1.4.1 The SDD specification must support the definition of alternative configuration and identify a default and/or prioritizing of those alternatives.

with PROPOSED:

2.1.4.1 The SDD specification must support the definition of alternative configurations.

Reqt 2.1.8.2

Replace ORIGINAL:

2.1.8.2 The SDD specification must support the definition of alternative uninstall scenarios.

with PROPOSED:

2.1.8.2 The SDD specification must support the following uninstall scenarios:

1. Uninstall of a defined subset (e.g. features) of a solution
2. Uninstall of installed resources, configuration data and user data
3. Uninstall of the installed resources keeping either configuration data or user data, or both

Reqt 2.2.1.1

Replace ORIGINAL: 

2.2.1.1 Operational state of required entities: The SDD specification must support the ability to specify that a required entity must be operational at various points.  Specifically identified as operational prior to start of the deployment lifecycle operation on the overall solution, or a component of the solution; or operational by the end of the deployment lifecycle operation. UC: 117, 123


with PROPOSED:

2.2.1.1 Operational state of required entities: The SDD specification must support the ability to specify that a required entity must be operational at various points during the operation.  Specifically identified as operational prior to start of the deployment lifecycle operation; operational prior to an identified step in the deployment lifecycle operation; or operational by the end of the deployment lifecycle operation.UC: 117, 123


Reqt 2.2.1.12

Drop ORIGINAL:

2.2.1.12 Installed component privileges: The SDD specification must support the definition of user privileges/ownership appropriate for the installed content. Where certain level of privileges are required, it is RECOMMENDED, as a best practice, to use the minimal level of required privileges in any environmental requirement.UC: 39

as use cases covered by 2.2.1.4


Reqt 2.3.3.1

Replace ORIGINAL:

2.3.3.1 The SDD specification must support definition of information that can be used by a provisioning application or installation program to generate a change plan for parts of a solution that outlines steps that can be performed manually or by an external application. 

with PROPOSED:

2.3.3.1 The SDD specification must support definition of information that can be used to generate a plan to execute a deployment lifecycle operation, where some of the steps of the plan may be executed manually or by more than one provisioning application or installation program in different administrative domains.

Drop 2.10.2:

2.10.2 The SDD specification must support the definition of requirements for deploying and configuring solution resources even across distributed and administratively separated locations.UC 151

Reqt 2.9.1

Move and replace ORIGINAL:

2.9.1 The SDD specification must not preclude the ability for the author to define accessibility requirements according to Section 508 (www.section508.gov). UC: 17, 170


with PROPOSED:

2.15.12  The SDD specification must not preclude the ability for management tools to meet accessibility requirements according to Section 508 (www.section508.gov). UC: 17, 170

Reqt 2.10.1


Drop ORIGINAL (and whole of section 2.10, given also drop 2.10.2):

2.10.1 The SDD specification must support the definition of information to assist a provisioning application or installation program in decision making when external dependencies are not met (e.g. preferred alternatives for meeting dependencies).

as covered by 2.3.1 (pending reword from Josh).

Senior Technical Staff Member
IBM, 11501 Burnet Road, Mail Point 901-6B10
Austin, TX 78758
1-512-838-3482 tl 678-3482