Use Cases Describing Business Processes

Document Sample
Use Cases Describing Business Processes Powered By Docstoc
					Requirement   Description                                   Use Cases
1.1.1         The SDD must provide the                      1, 2, 3, 27, 58, 72, 110,
              information required to plan and              133, 183,
              execute the installation and
              configuration of the contents of a
              solution package into a set of target
              environments which may span
              multiple machines and may consist of
              servers and resources of multiple
              different types.
1.1.1.1       The SDD must not require knowledge            72,
              of each resource type in order to
              process the descriptor.
1.1.1.2       The SDD should separate the install           97,
              and install-configuration phases
1.1.1.3       The SDD should not mandate a                  133,
              specific ordering or grouping of UI or
              execution, other than what is required
              by dependencies
1.1.1.4       The SDD must support installation             85, 97, 176,
              packages which contain configuration
              content in addition to install artifacts.
1.1.2         The SDD should also support the               30, 57, 136, 181,
              information needed to rollback or
              undo a change, or to determine in
              advance that this is not possible.
1.1.2.1       The SDD needs to provide                      141,
              information necessary to support
              granular rollback for error recovery
              processes.
1.1.3         The SDD must also provide the                 35, 131,
              information needed to uninstall a
              previously installed solution.
1.1.4         The SDD must support not only the             11, 12, 181, 185,
              initial install of a solution, but also the
              maintenance of a solution (i.e. updates
              and fixes - terms to be defined).

1.1.5         The SDD must support an upgrade of 8, 9, 65, 181, 185,
              a solution to a new version, including
              the migration, decomposition or
              obsoletion of existing components.
1.1.5.1      This may include coexistence of old 9,
             and new versions for a period of time.

1.1.6        The SDD must support the addition         4, 5,
             and removal of optional content
             (features) from an already-installed
             solution, subject to content selection
             rules.
1.1.7.       The SDD should support the                26, 46, 186,
             verification of an installed solution
1.1.8        The SDD should support the repair of      6,
             an installed solution.
1.1.9        The SDD should support the                28,
             reconfiguration of an installed
             solution.
1.1.10.      The SDD should support the                162, 163,
             application and undo of fixes             164,165,166,167,168,
1.1.11       (99.18a) SDD must be able to              134,
             encapsulate a snapshotted
             configuration for subsequent
             installation.
1.1.12       (99.22) All of the requirements for       162, 163,164, 166, 167,
             initial install also apply to update.     168,169,
1.2
Configura
tion
1.3.1         Determine superseded fixes               145,
1.3.2         Upgrade using a different package        146,
1.3.3         (99.30) Element Update – SDD             188,
              should permit individual component
              update, specifically System Firmware,
              BIOS, peripheral firmware
          2.1 The SDD must describe the                55, 68, 87, 110, 126,
              requirements on the target               127, 177, 184, 190, 191,
              environments that must be satisfied
              before a particular change operation
              (install, configuration, uninstall) is
              performed, to allow these
              requirements to be checked or a plan
              for satisfying them to be constrted.
2.1.1         This includes requirements on            34, 36, 56, 102,
              software and other resource instances
              installed in the environment.
2.1.2         This includes requirements on the        61, 74, 92,
              state of run-able resources (started,
              stopped), and the need for a restart
              (reboot) to activate a change.
2.1.3         This includes the need for               69, 39, 138,
              administrative user privileges. SDD
              Must be able to define system
              privileges required for lifecycle
              management when necessary.
2.1.4         This includes dependencies between       74, 102, 179,
              internal components of the solution
2.1.5         This includes relationships and          173, 174, 178,
              connectivity requirements
2.2.          The SDD should describe the              26, 173, 184,
              requirements on the target
              environments that must be satisfied
              for the solution to be usable, after
              installation and configuration
        2.3   The required target environments may     13, 55, 183, 113, 114,
              span multiple distributed machines       150, 151,
              and may consist of servers and
              resources of multiple different types.
        2.4   The requirements on the environment      13,
              may vary based on the selectable
              contents of the solution.
        2.5   The requirements for an update           40, 45,
              include the solution or component
              instance being updated.
        2.6   The SDD should provide description       36, 37, 44, 53, 136,
              information for components and
              checks where needed, to allow a
              management application to constrt a
              relevant message to assist a user in
              understanding errors and other
              messages, including dependency
              check failures, progress messages and
              change execution failures.
2.7 (99.5) The SDD should be able to            39,
    specify user privileges/ownership
    appropriate for the installed content
2.8 (99.9) SDD requirements should be           68,
    consumable by third party tooling to
    analyze consistency, etc.
2.9 (99.29) New                                 147,
    installations/updates/uninstalls should
    not impact existing installed
    components.
3.1 The SDD should describe what will           47, 59, 64, 100, 102,
    be the results of installing the solution   110, 173, 174, 180, 190,
    package, to allow a Provisioning            191,
    Application to determine the package
    or set of packages needed to satisfy
    the requirements for a change request.
    In addition, this information should
    provide the appropriate information to
    allow a Provisioning Application to
    detect that a solution or components
    of that solution have already been
    installed through an alternative means
    (“out-of-band” install of existing
    packages).
3.2 The SDD should describe what will           47, 59, 64, 100, 102,
    be the results of installing the package    173, 174, 190,
    to allow for the Solution Integrator to
    determine the package or set of
    packages needed to satisfy the
    requirements of an application. The
    Solution Integrator can integrate the
    appropriate packages into a single
    solution ensuring that the composition
    is whole.
        3.3 The SDD needs to provide a               29, 151,
            Provisioning Application with the
            ability to create a change plan for only
            part of a solution, or to generate a
            change plan that will involve some
            parts of the change plan being
            performed manually or by a different
            application. This is to allow for
            different domains of
            responsibility/security. The
            implication on the SDD is that it must
            be possible to understand the
            requirements and results of installing
            individual components of the solution,
            and to identify separately installable,
            updateable and uninstallable parts of a
            solution.
        3.4 The SDD needs to describe the           131, 143, 148,
            relationships and dependencies
            between the resulting resources to
            enable better management of shared
            components or other dependencies
            during update and uninstall
        3.5 The SDD should provide the              147,
            appropriate information to enable one
            to ensure that new
            installations/updates/uninstalls will
            not impact existing installed
4.1.        components support defining
            The SDD must                            1, 21, 42, 43, 44, 48, 49,
            permitted configuration and             50, 54, 71, 111,
            environment variability
4.1.1       The SDD should allow constraints to     43, 44, 88,
            be specified on the valid values of
            parameters(?)
4.1.2       The selections should be readily        48,49,50, 111, 112, 116,
            collected into a “response file” for    187, 194,
            reuse.
4.2 The parameterization supported by the       40, 56,
    SDD must allow multiple instances of
    the same solution to be deployed to
    the same environment(s). The SDD
    should indicate where this is not
    supported.
4.3 The SDD should support defaults for         2, 3, 21, 42,
    selectable content (e.g. features and
    parameters), to minimize the
    decisions that need to be made by
    different categories of user (role-
    based, novice/expert) or for different
    intended modes of use (evaluation,
    express, …).
4.4 The SDD must allow parameters to            35, 125,
    other change management operations
    as well as to install, e.g. whether to
    leave data behind after an uninstall, or
    to delete everything.
4.5 The SDD should allow different
    packagings of the same solution
4.6 The SDD needs to allow a                    2, 126,
    management application to determine
    up-front what user input is needed in
    order to perform a particular change
    management operation.
4.7 The SDD must support installation           65, 67, 70,
    packages which contain localization
    content in addition to install artifacts.
4.8 The SDD needs to provide a                  4, 5, 6, 117, 120, 121,
    management application with the             125,
    information needed to store or
    reacquire the values of relevant
    parameters and selections, for use
    during subsequent maintenance or
    repair. The SDD must indicate when
    a parameter may be changed by “out-
    of-band” configuration.
4.9 (99.13b) Licensing and registration -       103, 115,
    passing usage key(s) during
    installation.
       4.1 (99.28a) SDD must be able to indicate    144,
           that parameter values are sensitive
           data.
       5.1 The SDD must support the ability to      68, 73, 85, 98, 99,
           compose solutions from multiple
           components, whether these are
           individual install artifacts, or other
           solution packages.
       5.2 The SDD must support a solution          43, 59, 68, 76, 78, 132,
           composition which: Defines the           127,
           features and parameters that are
           exposed to the user, and maps these
           into the features and parameters of
           composed solutions and artifacts;
           Places additional restrictions on the
           configuration and environment of the
           composed solutions; Composes
           solutions where one solution will
           contribute to meeting the
           requirements of another; Composes
           both initial install and maintenance
           packages into a single package;
           Describes packaging layout
           restrictions.
       5.3 The SDD should indicate when             23, 32, 73, 89, 131,
           components may be shared between
           multiple solutions and must provide
           the information needed to determine
           whether a change to a shared
           component is compatible with other
           solutions sharing that component
5.4.       The SDD must support the ability to      75, 132,
           reason about the aggregated
           dependencies of a solution or set of
           solution. This includes aggregating
           consumption requirements
       5.5 The SDD must indicate whether the        86, 136, 188,
           solution or solution component may
           be installed, uninstalled or updated
           independently.
 5.6 The SDD must support installation           65, 67, 70,
     packages which contain localization
     content in addition to install artifacts.
 5.7 The SDD should also support                 16, 70, 96, 165, 194,
     packages which contain:
     Configuration instrtions (only);
     Localization content (only); A bundle
     of maintenance, potentially for
     multiple solutions; A bundle of
     solution packages that are only loosely
     related; Other contents TBD
 5.8 (99.11) Aggregating content and             93, 95,
     overriding existing content, for
     example, documentation
 5.9 (99.21c) Must allow for diverse             150,
     content
 5.1 (99.21e) SDD should not preclude            152,
     including any information required for
     application execution to be logically
     bundled in a package
5.11 (99.21m2) The SDD must support the          160,
     composition of a solution in which
     some content is encrypted.
5.12 (99.36) Selective update                    195,
5.13 (99.40) SDD does not preclude update        199,
     packages to be self-contained
5.14 (99.43) Update packages can be              202,
     integrated into larger customer
     solutions
6.1      The SDD must provide identity          25, 45, 51, 60, 93, 94,
         information for the solution package 103, 104, 110, 105, 190,
         which provides a basis for: Asset      201,
         management – e.g. identifies the
         purchased entity; License
         management ; e.g. identifies the
         licensed entity; Support/update
         entitlement – e.g. determining
         intended updates/refreshes;
         Component reuse during development
         – e.g. identity to lookup legal,
         licensing terms; Reporting and queries
         on package repository – e.g.
         maintenance types; Identifying
         associated documentation - e.g.
         readmes
      6.2 The SDD must provide identity             12, 25, 38, 60, 62, 63,
          information for the solution and          77, 79,
          solution components which provides a      103,104,105,106,107,10
          basis for: Solution lifecycle             8,109, 110, 124, 135,
          management – e.g. identifies a            137, 167,
          meaningful entity to update or
          uninstall; Traceability to
          build/development environment, e.g.
          for problem diagnosis; Traceability to
          problem management systems e.g. to
          identify the problems fixed in a new
          release; License management – e.g.
          identifies what is actually installed
          (?); Correlation into the hosting
          environment – e.g. native install error
          logs; Component reuse – e.g.
          capabilities; Reporting and queries –
          e.g. visibility of subcomponents;
          maintenance types; Maintenance
          history
      6.3 The SDD should provide identity        1, 2, 41, 88, 110,
          (description) information to assist a
          user in making correct decisions about
          the selectable variability, including
          optional features, parameters and
          targeting decisions.
6.4:         The SDD should provide information         62,
             that uniquely identifies the SDD
             descriptor, and allows it to be updated
             with a more recent version if the
             information it contains becomes out-
             of-date (due to an error in the original
             or due to new versions of
             dependencies).
6.5:         Identify the version of the SDD.           none
       6.6   (99.38) Consistent identity                197, 201,
       7.1   Physical packaging information
             should be contained in a separate
             media descriptor. The SDD for a
             solution package should be unaffected
             by physical packaging.
       7.2   The media descriptor should allow a        14, 15, 52, 139, 149,
             solution package or some of the            157, 192, 201,
             content to be accessed from: A local
             filesystem; An archive (e.g. ZIP); A
             network URL; Multiple removable
             media
       7.3   The media descriptor should allow          14, 140, 157, 159,
             files to be repositioned and/or
             renamed on the media for optimal
             access and to remove duplication.
7.4.         The media descriptor should allow a
             single file to span multiple removable
             media
       7.5   Composition or copying of packages         15,
             should not require modification of the
             original media descriptors unless the
             physical file packaging is changed.
       7.6   The descriptors must allow the             46, 149,
             integrity or authenticity of a package,
             including content and metadata, to be
             verified
       7.7   The package descriptor and contents        53, 95, 96,
             should be separable from any
             provided front-end install program.
 7.8 The SDD needs to provide a                16, 113, 114, 158,
     management application with the
     information to determine which files
     are needed for life cycle operations on
     which components of the solution, on
     which target, and at which stage
     during change execution, to allow
     optimization of file distribution.
 7.9 (99.21g) SDD should not preclude          154, 155,
     editing in place in which mgmt
     tooling expands SDD package,
     replaces content, and creates a new
     SDD package in place. This should
     permit incremental updates.
 7.1 (99.21i) Content layout format shall      156,
     be defined by SDD. In addition, SDD
     shall specify a set of standardized
     formats that may be used for
     packaging.
7.11 (99.21m1) SDD Package spec should         160,
     not preclude encryption or other
     means used to control content access.

7.12 (99.21n) Package contents can be any      161,
     opaque entries that are required for
     execution of application
 8.1 The SDD must support the ability to       64, 85, 100, 128, 175,
     compose solutions from existing
     software packages which were not
     created with an SDD. This means the
     SDD should be able to describe
     existing software packages, including
     those which: Provide content
     variability.; Are composed solutions.;
     Are manageable through
     existing/native install capabilities
10.1 (99.1) SDD should not preclude            17, 170,
     accessibility requirements.
10.2 (99.6) Schema should support queries,     53,
     unique identification of key elements,
     and consumption by a variety of
     automated tools.
10.3 (99.8) Automated build process. Link       62, 63,
     to devt source control.
10.4 (99.16) Mgmt app interoperability          129, 130, 189, 142 ,
     with existing package formats
10.5 (99.13c) Licensing and registration –      104, 106,
     SDD must not preclude the end user
     providing this information.
11.1 (99.2a) The SDD may need to provide
     information to assist in (automated)
     decision making (e.g. preferred
     alternatives for meeting
     dependencies).
11.2 (99.21d) Distributed and                   151,
     Administratively separated locations
12.1 Since there are various types of           91, 130,
     proders and consumers of this
     specification, e.g. optimized for a
     specific use, the TC should define the
     levels of conformance to the
     published specification. These
     conformance levels enable the
     standard to be more consumable
     across a broader set of consumers and
     proders, i.e. they do not need to
     provide the full standard.
13.1 (99.4a) Information related to             38, 141, 171,
     potential failure conditions and
     recovery steps should be able to be
     included in the SDD.
13.2 (99.4b) Error information should be        38, 141, 171,
     able to specify error level or severity.
     This may include informational
     messages required for development
     debug
13.3 (99.11a) Categorizing payload files        93,
     into canonical categories
13.4 (99.21f) SDD must provide an               153,
     extension point for adding sh things as
     ACS archive descriptors, for example.
14.1 (99.24a): The SDD displayable             19, 20, 53,
     content must be localizable.
14.2 (99.24b) The SDD should not               19, 20,
     preclude the user doing the install in
     one language, which may be different
     than the language of the installed
     component, and may also be different
     than the locale of the target platform.
15.1 (99.4) Error logs… link to HE-            38,
     specific logs
15.2 (99.7.1 & 99.7) Need a set of standard    92,
     interfaces to resources to permit a
     management application to be able to
     dede how to make changes to the
     existing environment in order to
     satisfy stated requirements. This
     includes starting or stopping resources
     and environments (“reboot”);
     installing other software packages;
     provisioning new servers.
15.3 (99.16a) Mgmt app interoperability        129, 130, 189, 142,
     that consume SDDs
15.4 (99.18) Management interfaces must        134,
     exist to permit snapshotting of an
     installed configuration.
15.5 (99.13a) Licensing and registration –     25,
     for auditing purposes
15.6 (99.13d) Licensing and registration –     105,
     must be able to determine that
     licensed software has been installed.
15.7 (99.34) Provide inventory of installed    193,
     components
15.8 (99.37) Need ability to determine         196,
     installed firmware and standardized
     means to update
15.9 (99.39) Stdized installation interfaces   198,
     and formats
15.1 (99.41) Management tools use the          200,
     information
16.1 (99.2) Management applications need none
     to implement appropriate policies to
     allow automated decision making
     (e.g. for novice users, evaluation
     installs). Many of these decisions can
     only be made in a specific context and
     so the primary requirement is on the
     applications. However, the SDD or
     some additional supporting source of
     knowledge may need to provide
     information to assist in automated
     decision making (e.g. preferred
     alternatives for meeting
     dependencies).

16.2 (99.3) Interactive install applications    37,
     need to be able to communicate to the
     user what tasks are being performed,
     and approximately how long they
     might take. The implication on the
     SDD might be (1) description of
     components (2) enough identity
     information to link to additional
     information about time to perform?
16.3 (99.5a) Installers/Managers should         39,
     examine the user privileges in the
     SDD prior to beginning installation to
     determine if the privilege is at correct
     level.
16.4 (99.14) Silent/unattended install          112, 116, 169,
16.5 (99.15) Remote install                     113, 114,
16.6 (99.17a) Mgmt and Install tools            131, 143, 148,
     should adhere to relationships and
     dependencies in handling of shared
     components or other dependencies
     (e.g. hosting env) during update and
     uninstall
16.7 (99.13a) Licensing and registration –      25,
     for auditing purposes
16.8 (99.39) Stdized installation interfaces    198,
     and formats
          17.1 (99.25) Component Granularity             123,
17.2.          (99.26b) Layout of components             127,
               should permit relocation when
               aggregating packages into larger
               packages
17.3.          (99.28b) Sensitive data should be         144,
               marked as sensitive
          17.4 (99.29) New                               147,
               installations/updates/uninstalls should
               not impact existing installed
               components.
         99.44 Unclassified                              203,
                                                         204,205,206,207,208,20
                                                         9,210
99.13z         Licensing and registration (OMS)          107, 108,109, 172,
99.13e         Licensing and registration                122,
Category 20: Conformance to Standards
Ref # Use Case       Category of Use Use Case                               Description                                                       Origin   Id    Requirement / Notes   Related
      Classification Case                                                                                                                                                          Requirem
                                                                                                                                                                                   ents




1     Install       UI              Select products from suite to install                                                                     CA       UI                          1.1.1
                                                                            In a product suite installation where a number of individual               3.2                         4.1
                                                                            products are bundled into a solution, the user needs to find                                           6.3
                                                                            and select the products he wants to install on a given
                                                                            machine. The user should be able to correctly identify and
                                                                            select the products that the user intends to install on a given
                                                                            machine. Proper description of the products and instructions
                                                                            will help the user decide which ones to select for the current
                                                                            installation.
Ref # Use Case       Category of Use Use Case                                        Description                                                       Origin   Id    Requirement / Notes   Related
      Classification Case                                                                                                                                                                   Requirem
                                                                                                                                                                                            ents




2     Deployment    Types           Locally install product using a manual install                                                                     CA       UI                          1.1.1
                                    program                                           User installs the product on the local machine for use by self            3.3                         4.3
                                                                                     or others.                                                                                             4.6
                                                                                      Users need at least two distinct options:                                                             6.3
                                                                                     1. A smooth, easy setup that does not overwhelm the novice
                                                                                     user with questions and options. The setup includes default
                                                                                     settings that give the user a reasonable configuration with
                                                                                     minimum user interaction.
                                                                                     2. A setup that provides sufficient options to the expert user
                                                                                     so that he can accurately configure all aspects of the product
                                                                                     in accordance with the exact needs of the end user.
                                                                                     3. There should be no input dialogs after the initial set of
                                                                                     questions. The installation should be finished when the user
                                                                                     returns after a long time thinking it would be at the Finish
                                                                                     page. If at all the installation program requires input after a
                                                                                     long time, the user should be informed in advance.


3     Deployment    Types           Evaluation install                               User sets up the product on the local machine for evaluation. CA           UI                          1.1.1
                                                                                     It is very important to make this installation smooth and easy             3.5                         4.3
                                                                                     because this will be the user’s first interaction with the
                                                                                     software.
Ref # Use Case       Category of Use Use Case                                    Description                                                 Origin   Id    Requirement / Notes            Related
      Classification Case                                                                                                                                                                  Requirem
                                                                                                                                                                                           ents




4     Install       UI              Install a new feature to an existing         Occasionally, a user might need to modify feature selections CA      UI    Different cases:               1.1.6
                                    installation (same versions)                 from the first-time installation. The system should display a        3.6   1. A new feature delivered on 4.8
                                                                                 list of components that are already installed and the new                  a new distribution
                                                                                 components that can be installed. User might need a feature                2. add a new feature and
                                                                                 that was initially not installed. So enable the user to add new            upgrade existing
                                                                                 features or components of a product.                                       3. Or a mix of old and new - A
                                                                                                                                                            & B are features from the old
                                                                                                                                                            distribution which the user
                                                                                                                                                            wants to add; feature C is new
                                                                                                                                                            on the distribution and user
                                                                                                                                                            wants to add.


5     Install       UI              remove a feature from an installed product   Occasionally, a user might need to remove feature selections CA      UI                                   1.1.6
                                                                                 from the first-time installation. The system should display a        3.6                                  4.8
                                                                                 list of components that are already installed . User might
                                                                                 need to uninstall a feature that was initially installed but the
                                                                                 user does not need it anymore. So enable the user to remove
                                                                                 already installed features or components of a product.
Ref # Use Case       Category of Use Use Case                                    Description                                                    Origin   Id     Requirement / Notes       Related
      Classification Case                                                                                                                                                                 Requirem
                                                                                                                                                                                          ents




6     Maintenance   Repair          Repair an existing installation (use previous At some point the user may need to repair the installation of a CA     UI     Configuration as well.    1.1.8
                                    settings)                                     product. Sometimes repair is enough to fix a problem hence             3.7    Potential options here.   4.8
                                                                                  preferable to a complete reinstall. Repair silently reinstalls the
                                                                                  missing or corrupt files.
                                                                                  1. The system must automatically detect the files that need to
                                                                                  be reinstalled.
                                                                                  2. The user should not be required to select components that
                                                                                  need to be repaired.
                                                                                  3. The user should not be required to enter any parameters.
                                                                                  4. The user should not be required to reboot immediately.

8     Maintenance   Upgrade         Upgrade to new version - Install over        Some products require that the previous version of that          CA     UI may be undoable               1.1.5
                                    previous version, updating common            product be uninstalled completely before installing a later             3.10
                                    components                                   version. However, uninstalling previous version is not a
                                                                                 preferred way of handling an installation. Instead, common
                                                                                 components between the old and the new installations should
                                                                                 be updated.
9     Deployment    Types           migrate to new version                       Migrating to a newer version is always a better idea than        CA     UI                               1.1.5
                                                                                 uninstalling the older version and then installing the new              3.11                             1.1.5.1
                                                                                 version. Unless there is an incompatibility with the products
                                                                                 you are migrating between, leave the old product installed
                                                                                 during a time of testing and verification. Insure that important
                                                                                 information is not lost while installing a newer version of a
                                                                                 product.
11    Maintenance   Patch           install patches                              Users want to replace faulty existing pieces by installing the CA       UI                               1.1.4
                                                                                 latest fixes and patches. This should be the first step when            3.13
                                                                                 troubleshooting software problems.
Ref # Use Case       Category of Use Use Case                  Description                                                   Origin   Id     Requirement / Notes   Related
      Classification Case                                                                                                                                          Requirem
                                                                                                                                                                   ents




12    Maintenance   Patch           install service packs       Users want to stay up to date by frequently installing interim CA     UI                           1.1.4
                                                               releases that contain a culmination of all fixes and service           3.14                         6.2
                                                               patches since the product was originally released. To improve
                                                               the product performance by fixing the bugs in the previous
                                                               release, or to generally add some feature to the existing
                                                               installation. Timely information should be provided about the
                                                               latest service packs available for installation.

13    Deployment    Types           multi-tier installation     Interrelated components in enterprise software can have      CA       UI                           2.3
                                                               different installation and configuration requirements. User            3.20                         2.4
                                                               installs these components in a distributed application
                                                               topology. Components of an enterprise application need to
                                                               be deployed on multiple machines to function as a single
                                                               solution.
14    Deployment    Types           multiple CD installation   Some product installations are distributed on several         CA       UI                           7.2
                                                               CD/DVD. User needs to swap CD during the installation in               3.21                         7.3
                                                               order to successfully install a product. Try to minimize CD
                                                               swapping and confusing the user. The installation must be
                                                               planned so that the user does not have to attend and watch
                                                               the installation closely.
Ref # Use Case       Category of Use Use Case                         Description                                                       Origin   Id      Requirement / Notes   Related
      Classification Case                                                                                                                                                      Requirem
                                                                                                                                                                               ents




15    Deployment    Types           local network install             The user may wish to copy the install media onto a network        CA                                     7.2
                                                                      location for ease of access for multiple installs. It must be                                            7.5
                                                                      possible to easily identify any related components (like
                                                                      components delivered originally on a separate CD). It should
                                                                      be possible to install from either a write protected or non-write
                                                                      protected media. File and path locations should not be
                                                                      absolute, but should always be relative to the root of the
                                                                      install.
16    Deployment    Types           web download install              Some products, for example the evaluation or retail versions CA            UI                            5.7
                                                                      are made available for download over the internet.                         3.23                          7.8
                                                                      Download time is a key issue.
17    Specialized   Accessibility   accessible installation           Who: Administrator deploying a solution based on SDD who Sun               III.3                         10.1
                                                                      has limited use of eyes, ears, hands,
                                                                      etc.
                                                                      What: A product that uses SDD to describe a bundled
                                                                      product
                                                                      Why: Support of disabilities and "Section 508 compliance"
                                                                      How:
                                                                      1. User deploys SDD-based product in a number of
                                                                      languages
                                                                      2. All interfaces must comply with section 508
                                                                      http://www.section508.gov/

19    Specialized   Globalization   install in non-English language   To provide a localizable user interface, all localization rules   CA       UI                            14.1
                                                                      must be adhered to. The user interface must handle all                     3.25                          14.2
                                                                      target languages gracefully.
Ref # Use Case       Category of Use Use Case                                     Description                                                         Origin   Id     Requirement / Notes          Related
      Classification Case                                                                                                                                                                          Requirem
                                                                                                                                                                                                   ents




20    Specialized   Globalization   install on non-English OS                     International users have their Operating Systems in their local     CA       UI                                  14.1
                                                                                  languages. The installation program should be able to run                    3.26                                14.2
                                                                                  gracefully on their OS.
21    Install       Role            Install customized for different roles        Install customized for different roles. (administrator, end user,   CA       UI How would this be captured in 4.1
                                                                                  developer for example). So the user does not have to make                    3.27 the SDD? How would the       4.3
                                                                                  complex decisions about what components to select for his                         SDD know what roles are on a
                                                                                  needs. The custom options should aim at reducing                                  system?
                                                                                  complexity by providing exactly the set of features a particular
                                                                                  role might need.
23    Maintenance   Basic           Other install updates common components       Multiple solutions rely on common components. A second              CA                                           5.3
                                    depended upon by product                      install (or maintenance to a second install) upgrades or
                                                                                  patches a shared common component. This must not break
                                                                                  the first product.
25    Licensing     Audit           auditing installations, by component and by   Auditing for software compliance with software-license              CA       UI Identity information available   6.1
                                    product                                       agreements including ensuring that what the user has                         3.41                                6.2
                                                                                  installed is legally acquired, and the user has the right                                                        15.5
                                                                                  number of licenses for the product and the components that                                                       16.7
                                                                                  are installed. To ensure compliance to the license
                                                                                  agreement.
26    Install       Validation      validation of completed install               Insure not only that the product is laid down correctly, but also   CA       UI Configurations and/or states to 1.1.7
                                                                                  that it runs correctly.                                                      3.29 validate: integrity, run,     2.2
                                                                                                                                                                    configure
27    Configuration Initial         initial configuration                         Setting initial parameters needed for operation                     Sun                                         1.1.1
28    Configuration Re-config.      Ongoing configuration changes                 modifying initial parameters at any future point in time            Sun                                         1.1.9
Ref # Use Case       Category of Use Use Case                        Description                                                  Origin   Id      Requirement / Notes        Related
      Classification Case                                                                                                                                                     Requirem
                                                                                                                                                                              ents




29    Deployment    Types           Network disconnected operation   Who: Administrator                                            Sun     III.6 How would web-based          3.3
                                                                     What: A product that uses SDD to describe a bundled                         updates to the install be
                                                                     product                                                                     handled in a disconnected
                                                                     Why: Security of network connectivity                                       environment? (use case 45)
                                                                     How:
                                                                     1. User deploys onto a disconnected target, from local media.
                                                                     Any remote dependencies that
                                                                     cannot be detected and/or resolved produce errors/warnings.

30    Install       Cancel          Cancel                           Who: Administrator                                           Sun      III.7                              1.1.2
                                                                     What: A product that uses SDD to describe a bundled
                                                                     product
                                                                     Why: Ability to cancel a deployment and return to previous
                                                                     state.
                                                                     How:
                                                                     1. User begins deployment.
                                                                     2. Deployment detects a state in which it cannot continue.
                                                                     3. User stops deployment, and reverts to previous state.
Ref # Use Case       Category of Use Use Case                                  Description                                                 Origin   Id      Requirement / Notes   Related
      Classification Case                                                                                                                                                         Requirem
                                                                                                                                                                                  ents




32    Deployment    Coexistence     Detection of previously installed components Who: Administrator                                         Sun     III.9                         5.3
                                    / Multiple versions                          What: A product that has previously been installed
                                                                                 Why: Multiple copies of identical products lead to
                                                                                 patching/update complexity.
                                                                                 How:
                                                                                 1. Admin installs product
                                                                                 2. Later, admin installs a later revision of said product.
                                                                                 3. Admin is given a choice to use some previous components
                                                                                 if they are backward compatible,
                                                                                 otherwise the admin is given the choice to install a new
                                                                                 revision of such a component, or stop the
                                                                                 installation.
33    Aggregation   Basic           Detection of remote dependencies             Who: Administrator                                         Sun     III.1
                                                                                 What: A product that has previously been installed                 0
                                                                                 Why: Multiple copies of identical products lead to
                                                                                 patching/update complexity.
                                                                                 How:
                                                                                 1. Admin installs product
                                                                                 2. Later, admin installs a later revision of said product.
                                                                                 3. Admin is given a choice to use some previous components
                                                                                 if they are backward compatible,
                                                                                 otherwise the admin is given the choice to install a new
                                                                                 revision of such a component, or stop the
                                                                                 installation.
Ref # Use Case       Category of Use Use Case                           Description                                                   Origin   Id      Requirement / Notes   Related
      Classification Case                                                                                                                                                    Requirem
                                                                                                                                                                             ents




34    Aggregation   Basic           Detection of compatible 3rd Party   Who: Administrator                                              Sun    III.1                         2.1.1
                                    dependencies                        What: A solution that contains a dependency that can be                1
                                                                        satisfied by an external product.
                                                                        Why: Solutions often adhere to an industry standard.
                                                                        How:
                                                                        1. Admin installs software onto a system.
                                                                        2. software complies with some well-known standard, and
                                                                        can resolve its dependency using an
                                                                        external solution that provides such a standard interface.
35    Uninstall     Uninstall       Uninstall product                   Who: Administrator                                              Sun    III.1                         1.1.3
                                                                        What: A software offering based on SDD.                                3                             4.4
                                                                        Why: Clean uninstalls are often a sign of a robust product.
                                                                        Customers demand that products 'clean
                                                                        up after themselves' in a coherent way.
                                                                        How:
                                                                        1. Admin installs a product
                                                                        2. Product is used in production, re-configured one or more
                                                                        times.
                                                                        3. Admin uninstalls product. An option is given to completely
                                                                        erase the software, or leave behind
                                                                        data files and/or configuration.
                                                                        4. Left-behind data/config can optionally be used in future re-
                                                                        installs to re-configure newly-installed
                                                                        software without intervention.
Ref # Use Case       Category of Use Use Case              Description                                                     Origin   Id      Requirement / Notes   Related
      Classification Case                                                                                                                                         Requirem
                                                                                                                                                                  ents




36    Install       Basic           Environmental Checks   Who: Administrator                                                Sun    III.1                         2.1.1
                                                           What: A software offering based on SDD.                                  5                             2.6
                                                           Why: Environments change often and can sometimes prevent
                                                           a given process from continuing.
                                                           How:
                                                           1. Admin installs a product
                                                           2. Installation detects the presence of some limiting factor
                                                           (lack of disk space, OS patches are
                                                           wrong, processor is too slow, etc).
                                                           3. Admin is given a choice to override, or fail the installation.

37    Install       UI              Status updates         Who: Administrator                                                Sun    III.1                         2.6
                                                           What: A software offering based on SDD.                                  6                             16.2
                                                           Why: Constant user feedback is important for admins to
                                                           estimate required time and whether or not
                                                           something is hung
                                                           How:
                                                           1. Admin installs a product
                                                           2. If, during any installation process (install, update, upgrade,
                                                           uninstall), the local system is required
                                                           to perform a task (ex. environmental checks, moving bits to
                                                           the file system) it is made clear to the
                                                           end user how long the expected task will take, the progress of
                                                           the given task, and a description of
                                                           the task and why it is needed.
Ref # Use Case       Category of Use Use Case                          Description                                                      Origin   Id      Requirement / Notes   Related
      Classification Case                                                                                                                                                      Requirem
                                                                                                                                                                               ents




38    Install       Validation      Diagnosing & Debugging             Who: Administrator                                            Sun         III.1                         6.2
                                                                       What: A software offering based on SDD.                                   7                             13.1
                                                                       Why: Many solutions do not have sufficient capabilities to                                              13.2
                                                                       efficiently detect and diagnose errors in                                                               15.1
                                                                       components.
                                                                       How:
                                                                       1. Admin installs product, in attended or unattended mode
                                                                       2. A (not necessarily fatal) failure occurs
                                                                       3. User examines log files to determine failure, and based on
                                                                       that content, is able to diagnose
                                                                       problem without calling support services.

39    Install       Role            Install without Admin privileges   Who: User who does not have administrator privileges             Sun      III.2                         2.1.3
                                                                       What: A software offering based on SDD.                                   0                             2.7
                                                                       Why: For non-system software, any user should be able to                                                16.3
                                                                       install, configure, and use said software
                                                                       without requiring administrator privileges.
                                                                       How:
                                                                       1. User installs product (into a location into which they have
                                                                       "write access"
                                                                       2. User configures and uses software. Software makes no
                                                                       use of (or disables certain features that
                                                                       require) administrator-only interfaces.
Ref # Use Case       Category of Use Use Case            Description                                                    Origin   Id      Requirement / Notes   Related
      Classification Case                                                                                                                                      Requirem
                                                                                                                                                               ents




40    Deployment    Coexistence     Multiple Instances   Who: Administrator and/or User                               Sun        III.2                         2.5
                                                         What: A software offering based on SDD.                                 1                             4.2
                                                         Why: Software is often used in several different modes, such
                                                         as in an evaluation mode, or testing
                                                         mode, or deployment. Multiple, independent copies allows
                                                         different "domains" to be created that
                                                         can be individually configured, managed, and uninstalled
                                                         without affecting other copies.
                                                         How:
                                                         1. User installs product that already exists on the system.
                                                         2. Rather than configuring multiple runtimes from a single
                                                         install, user installs a complete copy in a
                                                         different location. No dependencies exist between the
                                                         multiple installs.

41    Install       Help            Deployment Help      Who: Administrator                                               Sun    III.2                         4.1
                                                         What: A software offering based on SDD                                  5                             6.3
                                                         Why: Customers might need additional information at the
                                                         time of the install, and do not have
                                                         documentation available.
                                                         How:
                                                         1. user installs product
                                                         2. During install, useful help messages (tooltips, pop-ups, etc)
                                                         are provided describing the products
                                                         to install.
Ref # Use Case       Category of Use Use Case             Description                                                   Origin   Id     Requirement / Notes   Related
      Classification Case                                                                                                                                     Requirem
                                                                                                                                                              ents




42    Configuration Initial         Configuration Modes   Who: Administrator                                              Sun    IV.2                         4.3
                                                          What: A software offering based on SDD                                 6
                                                          Why: Ready-made configurations based on experience go a
                                                          long way toward making the evaluation
                                                          or initial impression experience better.
                                                          How:
                                                          1. user installs product
                                                          2. During install, several configuration templates are provided
                                                          (such as “Evaluation”, “Typical”,
                                                          “Express”, etc).
                                                          3. User selects one of the pre-defined configurations, which
                                                          are known to work. If no such default
                                                          configuration is possible for some components, then an
                                                          informative message is provided and the
                                                          user is required to fill in the custom configuration elements
                                                          that couldn't be applied automatically.
Ref # Use Case       Category of Use Use Case                         Description                                                      Origin   Id     Requirement / Notes   Related
      Classification Case                                                                                                                                                    Requirem
                                                                                                                                                                             ents




43    Configuration Initial         Common configuration parameters   Who: Administrator                                                 Sun    IV.2                         4.1
                                                                      What: A software offering based on SDD                                    7                            4.1.1
                                                                      Why: It is annoying to have to enter the same value multiple                                           5.2
                                                                      times for identical configuration
                                                                      options.
                                                                      How:
                                                                      1. user installs product
                                                                      2. If configuration at install time is selected, user is presented
                                                                      with the minimum number of
                                                                      configurable items. Any duplicate items are reduced to a
                                                                      single query. Any configuration items
                                                                      which have constraints are checked at the time of entry.
44    Configuration Validation      Deployment Validation             Who: Administrator                                                 Sun    IV.2                         2.6
                                                                      What: A software offering based on SDD.                                   9                            4.1
                                                                      Why: Customers are often not aware of invalid configurations                                           4.1.1
                                                                      they supply
                                                                      How:
                                                                      1. Admin installs a product
                                                                      2. Each component selected for deployment has the
                                                                      opportunity to validate its future configuration,
                                                                      and present override-able warnings.
Ref # Use Case       Category of Use Use Case                         Description                                                   Origin   Id     Requirement / Notes   Related
      Classification Case                                                                                                                                                 Requirem
                                                                                                                                                                          ents




45    Maintenance   Web             Automatic detection of upgrades   Who: Administrator                                              Sun    IV.3                         2.5
                                                                      What: A software offering based on SDD                                 0                            6.1
                                                                      Why: Software is often obsolete the minute it leaves the
                                                                      factory
                                                                      How:
                                                                      1. Admin installs a product
                                                                      2. Installation or runtime update interface detects the
                                                                      presence of newer
                                                                      versions of components of installed or about-to-be-installed
                                                                      components or products from dynamically published update
                                                                      metadata.
                                                                      3. Admin is shown a list of the available updates that apply to
                                                                      their
                                                                      product and system and asked to choose which ones they
                                                                      wish to
                                                                      install.
                                                                      4. Admin selects updates to install. Admin is informed if the
                                                                      selected
                                                                      updates will break any inter-system dependencies and
                                                                      chooses whether
                                                                      or not to proceed with the update install.
Ref # Use Case       Category of Use Use Case                              Description                                                       Origin   Id     Requirement / Notes          Related
      Classification Case                                                                                                                                                                 Requirem
                                                                                                                                                                                          ents




46    Install       Validation      Validation of bundled components       Who: User                                                         Sun      V.34                                1.1.7
                                                                           What: A software offering packaged with SDD                                                                    7.6
                                                                           Why: Metadata bundled with the product must enable
                                                                           validation (checksums, signatures, etc) to
                                                                           ensure deployed content is consistent with what the author
                                                                           intended.
                                                                           How:
                                                                           1. SDD-Based solution is deployed onto local and/or remote
                                                                           systems
                                                                           2. Components are compared against their factory-
                                                                           prearranged validation parameters (checksums,
                                                                           signatures, etc).
47    Aggregation   Legacy          Coexistence of wrapped and unwrapped   Product team creates a suite by wrapping an existing install.     CA                                           3.1
                                    versions of the same component         Installs to a system that has already installed the component                                                  3.2
                                                                           using a traditional install. Needs to transition to a managed
                                                                           component.
48    Deployment    Types           Install to Development / Test          Install product in a test or development environment, with the    CA       UI                                  4.1
                                                                           expectation that it will eventually be migrated to a production            3.36                                4.1.2
                                                                           system.
49    Deployment    Types           Install to Production                  Install product in a production environment. Frequently done      CA       UI                                  4.1
                                                                           by migrating a test or development version (including                      3.37                                4.1.2
                                                                           configurations.)
50    Deployment    Types           Migrate from Test to Production        Migrate from test to production, capturing relevant settings      CA       UI The system may have been         4.1
                                                                           and configurations, but able to override target-specific                   3.38 tweaked by the tester/ user.   4.1.2
                                                                           settings.
Ref # Use Case       Category of Use Use Case                              Description                                                   Origin   Id     Requirement / Notes         Related
      Classification Case                                                                                                                                                            Requirem
                                                                                                                                                                                     ents




51    Maintenance   Web             Update/upgrade entitlement awareness   Who: Administrator who subscribes to product updates            Sun    IV.3                               6.1
                                                                           What: A software offering based on SDD                                 0a
                                                                           Why: Companies that provide updates may wish to make
                                                                           them available
                                                                           only to customers who have purchased an update
                                                                           subscription or
                                                                           support contract
                                                                           How:
                                                                           1. Admin installs a product
                                                                           2. Admin registers the product or system
                                                                           3. Installation or runtime update interface detects the
                                                                           presence of newer
                                                                           versions of components.
                                                                           4. Admin is shown a list of the available updates that they are
                                                                           entitled to
                                                                           .
                                                                           5. Admin chooses updates for install.
52    Deployment    General         Physical packaging                     A software vendor needs to package their product on             IBM           map to physical packaging   7.2
                                                                           (potentially multiple) physical media or for download by                      separate from deployment
                                                                           multiple customers.                                                           descriptor
Ref # Use Case       Category of Use Use Case                                     Description                                                    Origin   Id   Requirement / Notes                 Related
      Classification Case                                                                                                                                                                          Requirem
                                                                                                                                                                                                   ents




53    Install       UI              Interactive interview to collect parameters   The product is typically shipped with an interactive install   IBM           : package may optionally            2.6
                                    and requirements for install                  program to guide the user during install.                                    contain interactive install         7.7
                                                                                                                                                               program                             10.2
                                                                                                                                                               Requirement: ability to refer to    14.1
                                                                                                                                                               individual parts of the schema
                                                                                                                                                               (e.g. requirements/checks)
                                                                                                                                                               Requirement: descriptions and
                                                                                                                                                               national language support for
                                                                                                                                                               parts of the schema (IUs,
                                                                                                                                                               features, requirements...)




54    Install       UI              feature selection                             select optional content and specify rules for how it may be    IBM           Features, feature selection,        4.1
                                                                                  selected (features, feature selection rules)                                 ways to categorize/group
                                                                                                                                                               features for different user roles
                                                                                                                                                               or purposes
55    Aggregation   Hosting         dependencies that span multiple hosting                                                                      IBM           Expressing dependencies on          2.1
                    Environment     environments                                                                                                               multiple resources with defined     2.3
                                                                                                                                                               relationships
56    Deployment    Coexistence     Multiple Instances                            handling multiple software instances                           IBM           ability to distinguish instances,   2.1.1
                                                                                                                                                               e.g. when expressing                4.2
                                                                                                                                                               dependencies
57    Install       Cancel          Cancel                                        coordination of install/rollback                               IBM           undo support                        1.1.2
Ref # Use Case       Category of Use Use Case                                 Description                                                     Origin   Id    Requirement / Notes             Related
      Classification Case                                                                                                                                                                    Requirem
                                                                                                                                                                                             ents




58    Deployment    General         Coordinate installation across multiple   This introduces the need to coordinate an installation across   IBM            Requirement: Multiple-          1.1.1
                                    hosting environments                      multiple hosting environments on a single machine. In                          machine target topologies
                                                                              addition, different features of the product may commonly be
                                                                              installed on different machines.
59    Aggregation   Basic           common component or 3rd party             Matching dependencies in one package that are to be             IBM            Requirement: Ability to         3.1
                                    dependencies                              satisfied in another                                                           determine that installing one   3.2
                                                                                                                                                             package will satisfy a          5.2
                                                                                                                                                             dependency in another
60    Development Library of        Library of Components                     Development organizations (or component vendors) may          CA               Would this mean SDD             6.1
                  Components                                                  construct libraries of components which can be selected by                     Naming/Keyword                  6.2
                                                                              development for delivery in a solution. Developers using this                  Management? How does this
                                                                              library need to see information which will allow them to a)                    relate to legal/licensing
                                                                              identify the component b) understand clearly requirements                      (separate requirement)?
                                                                              (including legal or licensing).                                                Possible two requirements
                                                                                                                                                             here.
61    Install       Basic           service start/stop                        Ability to start or stop services                               CA       IS                                    2.1.2
                                                                                                                                                       3.4
62    Development Build Process     Scriptable build process                  During development of Products and Installations it is        CA                                               6.2
                                                                              important to be able to update payloads on packages through                                                    6.4
                                                                              an automated build process. To eliminate the need for a Build                                                  10.3
                                                                              Engineer to be physically involved when it is necessary to
                                                                              deliver updated payload to QA.
Ref # Use Case       Category of Use Use Case                                  Description                                                      Origin   Id      Requirement / Notes            Related
      Classification Case                                                                                                                                                                       Requirem
                                                                                                                                                                                                ents




63    Development Build Process     changes can be tracked by source control   During development of Installations it is important to be able   CA               Does this apply to resources   6.2
                                    systems                                    to manage changes and fixes to the installation through                           pointed to by the SDD? How     10.3
                                                                               source control systems. To reduce the time to develop                             do resources get controlled?
                                                                               installations and to insure high quality implementations. The                     Possible multiple
                                                                               "source" for the installation must be handle-able by common                       requirements.
                                                                               source control systems, and should be able to fit into typical
                                                                               multi-stage models.
64    Aggregation   Legacy          legacy packaging support                   Who: Administrator with native packaging skills                  Sun      III.1                                  3.1
                                                                               What: A product that uses SDD to 'wrap around' existing                                                          3.2
                                                                               packaging                                                                                                        8.1
                                                                               Why: A transition period will exist where products are
                                                                               produced
                                                                               using native packaging systems
                                                                               How:
                                                                               1. Deploy solution based on SDD toolset
                                                                               2. Manage deployed system using native packaging tools
65    Specialized   Globalization   Globalization                              Who: Administrator deploying a solution based on SDD             Sun      III.2                                  1.1.5
                                                                               What: A product that uses SDD to describe a bundled                                                              4.7
                                                                               product                                                                                                          5.6
                                                                               Why: Not everyone speaks a common language
                                                                               How:
                                                                               1. User deploys SDD-based product in a number of
                                                                               languages
                                                                               2. All output from the procedure must be localized, including
                                                                               user interface and log files.
Ref # Use Case       Category of Use Use Case                             Description                                                    Origin   Id     Requirement / Notes                 Related
      Classification Case                                                                                                                                                                    Requirem
                                                                                                                                                                                             ents




66    Development Install Building   Replace an existing install with a   New backwards compatible installation to replace an existing CA
                                     decomposition                        common component - with a more complex component
                                                                          topology. (move from a "black box" to transparent
                                                                          componentization.
67    Specialized   Globalization    localization modes                   Development needs to determine whether the install will be    CA                                                   4.7
                                                                          localized or not, and whether the localization is tied to the                                                      5.6
                                                                          locale.
68    Development Install Building   dependency validation                Development wants to aggregate a number of products and / CA                   In addition to validation, should   2.1
                                                                          or components and would like to validate that the                              the SDD also provide                2.8
                                                                          requirements are not contradictory, and to determine the                       aggregated build constraints?       5.1
                                                                          aggregate of the requirements                                                  I.e., a component requires          5.2
                                                                                                                                                         Oracle, DB2, but not Sybase.

69    Development Aggregation        root / not root privileges           Development needs to specify the privileges required to        CA       IS                                         2.1.3
                  Requirements                                            install a component. There are generally cases in which a               3.27
                                                                          “root” or other administrative level user id is required:
                                                                          • For Windows, creations of product registry information,
                                                                          defining discretionary access control, or setup of services,
                                                                          drivers, etc.
                                                                          • For UNIX/Linux, update of protected directories such as
                                                                          /etc.
Ref # Use Case       Category of Use Use Case                                   Description                                                  Origin   Id   Requirement / Notes             Related
      Classification Case                                                                                                                                                                  Requirem
                                                                                                                                                                                           ents




70    Specialized   Globalization   Separate distribution of resource bundles   Another common requirement is to support localization        IBM           Requirement: localization       4.7
                                                                                packages, which may be distributed separately.                             package support - e.g. defining 5.6
                                                                                                                                                           localization relationships;     5.7
                                                                                                                                                           understanding need to add or
                                                                                                                                                           remove localization content
                                                                                                                                                           when you add/remove product
                                                                                                                                                           content.

71    Deployment    General         Cross-platform development                  A subset of vendors have a requirement to develop cross-      IBM          Platform-neutral (resource      4.1
                                                                                platform install packages. Leaving aside the need for a                    neutral) description
                                                                                common format for the install artifact/actions (outside scope              Requirement: Expressing
                                                                                of this working group), these vendors need a descriptor that               conditions that determine what
72    Deployment    General         Hosting environment                         can specify both cross-platform dependencies (in software
                                                                                Traditionally, product installation means installing a common IBM          content is installed
                                                                                                                                                           Requirement: Pluggable          1.1.1
                                                                                into the operating system environment. Increasingly today,                 mechanism for specifying        1.1.1.1
                                                                                vendors are creating products that include other software,                 target environments and
                                                                                such as J2EE applications, and are recognizing the need to                 artifacts to be installed.
                                                                                treat other content such as database tables and web content                Opaque artifacts. Descriptor is
                                                                                as a formal part of the product that requires lifecycle                    platform/resource-neutral.
                                                                                management.
73    Aggregation   Basic           Agile solution packaging                    Componentization is driven by the desire of vendors to        IBM          Requirement: package            5.1
                                                                                structure their products into components that can readily be               composition. Shared versus      5.3
                                                                                composed into offerings to meet specific market needs.                     dedicated components.
                                                                                                                                                           Restrictions on sharing....
Ref # Use Case       Category of Use Use Case                                      Description                                                    Origin   Id   Requirement / Notes                Related
      Classification Case                                                                                                                                                                          Requirem
                                                                                                                                                                                                   ents




74    Aggregation   Basic            Validation of interdependencies, sequencing The components may be finer-grained than existing products. IBM                Requirement: Internal              2.1.2
                                                                                 A key requirement is the composability of the installation                     dependencies expressed.            2.1.4
                                                                                 packages, including:                                                           Dependencies include state
                                                                                 Installation order driven by dependencies, including on                        (created, installed, running...)
                                                                                 required state

75    Aggregation   Aggregation      Aggregation of consumption dependencies       Aggregation of consumption dependencies (e.g. disk space)      IBM           Requirement: Declarative       5.4
                    Requirements                                                                                                                                dependencies, defined
                                                                                                                                                                semantics ("consumption" of
                                                                                                                                                                what, on what)
76    Development Install Building   passing parameters                            Mapping variables between different components                 IBM           Requirement: descriptor        5.2
                                                                                                                                                                composition (mapping
                                                                                                                                                                variables
77    Development Install Building   Shielding of developers from internal         A particular challenge with fine-grained componentization is   IBM           Requirement: Support different 6.2
                                     dependencies of reusable aggregates           that the user may not be aware (or at least does not want to                 IU categories to distinguish a
                                                                                   be aware) of the individual components in the product                        product from a component

78    Development Install Building   pass-through of user selections in reusable   The composite package needs to reflect the view that the       IBM           Requirement: descriptor            5.2
                                     aggregates                                    user should be aware of (e.g. features, parameters, target                   composition (mapping of
                                                                                   environment for the product), and map that into the                          variables, features, etc.
                                                                                   information needed to install the individual components,                     Identifying input parameters
                                                                                   allowing automated decisions where user input is not                         vs. derived variables vs.
                                                                                   available or expected.                                                       queried properties.)
Ref # Use Case       Category of Use Use Case                                  Description                                                      Origin   Id    Requirement / Notes             Related
      Classification Case                                                                                                                                                                      Requirem
                                                                                                                                                                                               ents




79    Development Install Building   shielding of developers from irrelevant   The install service needs to record and track the details of the IBM            Requirement: Categorization     6.2
                                     information                               component instances and dependencies, but also needs to                         of IUs.
                                                                               be able to hide this detail when it is not required.




85    Aggregation   Legacy           Solution integrations                     Solution integrators will typically be focused on the ability to   IBM          Requirement: Wrappers.          1.1.1.4
                                                                               create wrappers for existing products, and to aggregate                         Requirement: Specifying         5.1
                                                                               descriptors into a composite descriptor. They also need to be                   configuration.                  8.1
                                                                               able to add configuration to the composite, in order to bring
                                                                               the overall solution into a usable state.
86    Aggregation   Basic            Specify Atomicity of install              Identification of components or aggregates that comprise a         CA     IS                                    5.5
                                                                               "complete" installation. Installs or uninstalls must not leave            3.3
                                                                               an "Atomic" component half installed or uninstalled. Including
                                                                               complete suite. Must be definable at low levels but
                                                                               overridable at higher levels of aggregation.
87    Deployment    General          Abstraction of target                     Although these solutions are typically deployed into a more        IBM          Requirement: Declarative        2.1
                                                                               specific environment than a product, it is important to note                    description of logical target
                                                                               that there is still a strong requirement to support the definition              environment.
                                                                               of a logical target environment which can then be mapped to
                                                                               multiple physical environments. This is because a solution will
                                                                               be deployed into multiple different environments, both as part
                                                                               of its lifecycle (development, system test, performance test,
                                                                               acceptance test, production) and because a solution may be
                                                                               deployed to multiple production environments.
Ref # Use Case       Category of Use Use Case                                  Description                                                     Origin       Id   Requirement / Notes             Related
      Classification Case                                                                                                                                                                        Requirem
                                                                                                                                                                                                 ents




88    Development Install Building   parameter descriptions and valid values   install parameter validation constraints and descriptions / help technical                                        4.1.1
                                                                               for use                                                          committe                                         6.3
                                                                                                                                                e Call

89    Development Basic              reuse of common component packages        There are two principal types of Shared components. These CA                 IS   Clarify this item a little more, 5.3
                                                                               are:                                                                         3.30 possibly separate into multiple
                                                                               Single Instance – Multiple products share a single installed                      requirements. How would this
                                                                               instance of the component. These are placed into a standard                       work with uninstallation
                                                                               location for products to share effectively.                                       cleanup?
                                                                               Embedded - These are placed into the product itself. Multiple
                                                                               products that use this component will therefore replicate it as
                                                                               many times as there are products installed.
Ref # Use Case       Category of Use Use Case                                 Description                                                    Origin   Id   Requirement / Notes           Related
      Classification Case                                                                                                                                                                Requirem
                                                                                                                                                                                         ents




91    Deployment    General         Use of components in different management Components and products may be targeted for environments CA                  Also specify in a component   12.1
                                    environments                              with varying levels of manageability. Some features and                      which levels would be
                                                                              dependencies may not be necessary for lower end                              supported.
                                                                              environments. It would be desirable to have SDD-based
                                                                              packages that could be deployed with a) centralized
                                                                              management (Unicenter, Tivoli, grid, for example) b) locally
                                                                              managed systems (desktops and servers in smaller
                                                                              enterprises c) marginally managed or unmanaged systems
                                                                              (retail, consumer). Stratification of features into sets that
                                                                              may be supported by runtime alternatives would allow
                                                                              packaging of components that could be used independently,
                                                                              or aggregated into more complex solutions. (Full runtime
                                                                              support may be too heavyweight for web deployment).
                                                                              Stratification of SDD function support also.

92    Aggregation   Aggregation     aggregation of OS services                aggregation and synchronization of multiple re-boot, service   CA                                          2.1.2
                    Requirements                                              start/stop requests in an aggregate install                                                                15.2
Ref # Use Case       Category of Use Use Case                        Description                                                  Origin   Id   Requirement / Notes           Related
      Classification Case                                                                                                                                                     Requirem
                                                                                                                                                                              ents




93    Development Library of        multiple readme aggregation      Some products are composed of many components that are CA             UI i18n requirements for            5.8
                  Components                                         developed independently then compiled together. These                 3.22 aggregated component           6.1
                                                                     components can also be used separately or with other                       readmes need to be validated. 13.3
                                                                     products. As such, compilation of a single Readme file can                 Related to 66. Product
                                                                     be potentially problematic. So - in the past, some products                components should be able to
                                                                     have had multiple Readme files. Sometimes all of the                       override the need to aggregate
                                                                     different language versions of a product ship on a single CD.              specific readmes. Shared
                                                                     The Readme should be viewable prior to installation.                       components should be able to
                                                                                                                                                declare aggregated readme
                                                                                                                                                constraints.

94    Development Library of        EULAs from multiple components   Products are often aggregates of different components.       CA       UI i18n requirements for            6.1
                  Components                                         Approved license information for any version of a product or          3.44 aggregated component EULAs
                                                                     component included in the distribution media must be                       need to be validated. Related
                                                                     provided to “Top Level Product” development team by the                    to 66. Product components
                                                                     contributing software development groups. Each component                   should be able to override the
                                                                     might have a separate EULA.                                                need to aggregate specific
                                                                                                                                                EULAs. Shared components
                                                                                                                                                should be able to declare
                                                                                                                                                aggregated EULA constraints.


95    Aggregation   Aggregation     Brand-able components            Ability to externalize branding information for components, so CA                                        5.8
                    Requirements                                     that a single package can be re-used by multiple vendors.                                                7.7
Ref # Use Case       Category of Use Use Case                Description                                                        Origin   Id      Requirement / Notes   Related
      Classification Case                                                                                                                                              Requirem
                                                                                                                                                                       ents




96    Aggregation    Basic          Marketing Bundles        Who: Marketing/Product management                               Sun         III.1                         5.7
                                                             What: A software offering containing multiple components                    2                             7.7
                                                             that can be grouped based on marketing
                                                             needs.
                                                             Why: Components of a product are often grouped together
                                                             based on marketing needs, and those
                                                             groupings are not obvious to the solution integration engineer.
                                                             How:
                                                             1. Solution integration (aka Release Engineering) is supplied
                                                             a description of a marketing bundle.
                                                             2. Solution integration produces product that contains a user
                                                             interface element allowing end users to
                                                             'select' such a bundle.

97    Configuration Initial         Optional configuration   Who: ISV/IHV                                                       Sun      IV.2                          1.1.1.2
                                                             What: A product that uses SDD to describe a bundled                         8                             1.1.1.4
                                                             product
                                                             Why: Ability to install without configuration (e.g. factory pre-
                                                             install)
                                                             How:
                                                             1. ISV installs product onto system without configuration
                                                             2. ISV ships system to customer
                                                             3. Customer continues process by configuring pre-installed
                                                             component(s)
Ref # Use Case       Category of Use Use Case                           Description                                                    Origin   Id     Requirement / Notes             Related
      Classification Case                                                                                                                                                              Requirem
                                                                                                                                                                                       ents




98    Aggregation   Legacy          Embedding of 3rd party components   Who: Assembler                                                 Sun      V.33                                   5.1
                                                                        What: A software offering packaged with SDD that fulfills a
                                                                        requirement in a larger, aggregated
                                                                        offering
                                                                        Why: Off-the-shelf components are often cheaper to bundle
                                                                        rather than develop
                                                                        How:
                                                                        1. SDD-Based 3rd-party solution is aggregated into a larger
                                                                        distribution
                                                                        2. When installed, 3rd-party solution appears alongside the
                                                                        'native' components and can be linked to
                                                                        using metadata provided by 3rd-party bundle
99    Aggregation   Basic           aggregation                         Increasingly, the need to compose product offerings from       IBM             Requirement: package             5.1
                                                                        other products and components - including embedding third-                     composition
                                                                        party products - is becoming important. This need to support                   Requirement: package must
                                                                        composition is one of the key drivers for a common                             be installable by third party
                                                                        declarative descriptor.                                                        using information in descriptor.
                                                                                                                                                       Should not require use of
                                                                                                                                                       interactive install program or
                                                                                                                                                       understanding of proprietary
                                                                                                                                                       formats.
Ref # Use Case       Category of Use Use Case             Description                                                    Origin   Id      Requirement / Notes          Related
      Classification Case                                                                                                                                              Requirem
                                                                                                                                                                       ents




100   Deployment    General         Complex Deployments   As vendors increasingly compose individual products into       IBM              Requirement: Wrapper         3.1
                                                          higher-value solution offerings, the need to provide a product                  support.                     3.2
                                                          installation program that can coordinate the installation                       Requirement: Ability to co-  8.1
                                                          across multiple machines increases. This blends into the                        exist and express
                                                          distributed change management scenario, at least in terms of                    dependencies on software
                                                          requirements on the descriptor and on the technology to                         installed through other
                                                          perform the dependency checking and installation. It also                       mechanisms (need to describe
                                                          highlights a requirement to be able to create "wrappers" for                    how to detect the IU in the
                                                          existing products that they want to be able to compose.                         hosting environment).


102   Aggregation   Basic           aggregation           It may also involve installing multiple packages in order to   IBM              Requirement: Ability to      2.1.1
                                                          satisfy dependencies.                                                           understand inter-package     2.1.4
                                                                                                                                          sequencing dependencies.     3.1
                                                                                                                                                                       3.2
103   Licensing     Registration    Licensing             Who: Administrator                                               Sun    III.2                                4.9
                                                          What: A software offering based on SDD                                  3                                    6.1
                                                          Why: Software is not free                                                                                    6.2
                                                          How:
                                                          1. user installs product
104   Licensing     Registration    Registration          2. Product requires activation license (either limited time span Sun
                                                          Who: Administrator                                                      III.2                                6.1
                                                          What: A software offering based on SDD                                  4                                    6.2
                                                          Why: Marketing data                                                                                          10.5
                                                          How:
                                                          1. user installs product
                                                          2. Installer presents registration option, noting what will be
Ref # Use Case       Category of Use Use Case        Description                                                 Origin      Id     Requirement / Notes   Related
      Classification Case                                                                                                                                 Requirem
                                                                                                                                                          ents




105   Licensing     Audit           Auditability     Metering and other types of audit-based licensing schemes   CA          UI                           6.1
                                                     need to be supported. Some way to identify the use of the               3.42                         6.2
                                                     installed component (either existence or scale)                                                      15.6
106   Licensing     Audit           Return receipt                                                               technical                                6.2
                                                                                                                 committe                                 10.5
                                                                                                                 e Call
Ref # Use Case       Category of Use Use Case                               Description                                                  Origin    Id   Requirement / Notes   Related
      Classification Case                                                                                                                                                     Requirem
                                                                                                                                                                              ents




107   Licensing     Audit           Publisher Requirement: Need a revenue   Software publisher wants to deliver a full working version of           1
                                                                                                                                            OMS SafeHarbor                    6.2
                                    recognition event                       their software to a customer that has paid for the software.                                      99.13Z
                                                                            Publisher may not recognize revenue without a positive
                                                                            affirmation of receipt of said software.
                                                                            i. Derivation: publisher pushes content that has not been paid
                                                                            for, but has a price.
                                                                            ii. Derivation: customer pulls content that has not been paid
                                                                            for, but has a price.
                                                                            b. Publisher stages product to file system (source) that is
                                                                            accessible to the customer.
                                                                            c. Publisher pushes file(s) to consumers (target) file system.
                                                                            i. Derivation: Customer pulls file to customer file system.
                                                                            d. An application (installer, an existing application of
                                                                            customers machine, the download manager, or auto run
                                                                            app), confirms to the publisher that 100% of the pushed
                                                                            content has landed on the target.
                                                                            i. Derivation: secondary process such as a pre existing
                                                                            application that utilizes the contents of the download confirms
                                                                            utilization of the new content.
                                                                            ii. Derivation: for Customer that manually pulls the software
                                                                            content, a manual confirmation can be sent back to the
                                                                            publisher.
                                                                            iii. Derivation: Customer needs to close an internal PO for the
                                                                            content that was just received.
                                                                            iv. Derivation: Publisher needs to bill user for files/features
                                                                            take/used and not paid for.
Ref # Use Case       Category of Use Use Case                                 Description                                              Origin    Id   Requirement / Notes   Related
      Classification Case                                                                                                                                                   Requirem
                                                                                                                                                                            ents




108   Licensing     Registration    Consumer Requirement: Need to trigger a   (RECONCILIATION –dual use of confirmation syntax)                   2
                                                                                                                                          OMS SafeHarbor                    6.2
                                    reconciliation event                      Software customer signs a PO for a piece of software.                                         99.13Z
                                                                              Software customer downloads the software listed on the PO.
                                                                              Software customer needs to tell his or her OWN accounting
                                                                              department to close the PO.
109   Licensing     Feature         Publisher/Customer Joint Requirement:                                                                         3
                                                                               (100% of bits, 50% of functions) Publisher makes available OMS SafeHarbor                    6.2
                    Enabling        Recognize additional new business event   software that the customer has paid for, and software (or                                     99.13Z
                                                                              features) that the customer has NOT paid for.
Ref # Use Case       Category of Use Use Case                                     Description                                                       Origin   Id     Requirement / Notes              Related
      Classification Case                                                                                                                                                                            Requirem
                                                                                                                                                                                                     ents




110   Deployment    Types           Prepare for Installation                      Before starting the installation process, the user needs to       CA       UI     The SDD must provide a way       1.1.1
                                                                                  plan and prepare for the installation. The user needs to plan              3.1    for 3rd party tools to use       2.1
                                                                                  the topology and how the whole system is expected to work.                        introspection to determine how   3.1
                                                                                  At this stage, the user needs information such as the                             the installation can bet used,   6.1
                                                                                  installation requirements, prerequisites, support contact                         useful for planning the          6.2
                                                                                  information, training information, and any other information                      installation topology.           6.3
                                                                                  that might help the user efficiently install the product.

                                                                                  1. To fully equip the user with all the required information so
                                                                                  that the user does not spend time making important pre-
                                                                                  installation decisions during the installation.
                                                                                  2. To ensure that the user does not encounter too many
                                                                                  unexpected errors that could have been avoided initially had
                                                                                  the user been given the correct information before the
                                                                                  installation began.

                                                                                  SDD should be able to be interrogated by a 3rd party tool that
                                                                                  could provide modeling information useful for preparing to
                                                                                  install.

111   Deployment    Types           Create response file for silent or unattended The expert user can create a response file for future             CA       UI                                      4.1
                                    installation                                  installations with pre selected options and no interface. The              3.16                                    4.1.2
                                                                                  response file contains setup and configuration information
                                                                                  using the interactive install program. So the user does not
                                                                                  need to manually answer the installation questions every
                                                                                  time.
Ref # Use Case       Category of Use Use Case                              Description                                                       Origin   Id     Requirement / Notes   Related
      Classification Case                                                                                                                                                          Requirem
                                                                                                                                                                                   ents




112   Deployment    Types           Silent installation / uninstallation   The silent installation will be driven using a response file. The CA       UI                           4.1.2
                                                                           response file provided can be edited by the end user but will              3.17                         16.4
                                                                           initially contain default setup information similar to that which          IS
                                                                           an end user would submit as responses to dialog boxes when                 3.92
                                                                           running the interactive install. No interface is involved in this
                                                                           type to installation.
                                                                           Purpose: To enable an expert user to quickly perform
                                                                           unattended installations without having to answer installation
                                                                           questions every time.

                                                                           o This should be a completely silent installation with no error
                                                                           messages and warnings during the installation.
                                                                           o The program should create a success/failure log after the
                                                                           program has run. A return code should indicate success or
                                                                           failure. No ui or dialog should appear in a silent install.
                                                                           o There should be a prompt if the user tries to shut down
                                                                           before the silent installation is finished.
Ref # Use Case       Category of Use Use Case                                  Description                                                    Origin   Id     Requirement / Notes   Related
      Classification Case                                                                                                                                                           Requirem
                                                                                                                                                                                    ents




113   Management Customer           Remote installation using central          System administrators frequently distribute, install, verify, CA        UI                           2.3
                 Environment        management software                        update, and uninstall software from a central location on               3.18                         7.8
                                                                               multiple computers throughout a network using management                                             16.5
                                                                               software. To simplify enterprise wide deployment by
                                                                               eliminating the need to physically attend to each computer.

                                                                               1. Reduce the need to manually distribute, install, and
                                                                               administer software
                                                                               2. Consistent configuration throughout the enterprise.

114   Deployment    Types           Remote Installation Using Manual Install   Distribute and install software on multiple computers from a   CA       UI                           2.3
                                    Program                                    central location. To simplify enterprise wide deployment by             3.19                         7.8
                                                                               eliminating the need to physically attend to each computer.                                          16.5

115   Licensing     Registration    License Key / Retail (One Machine)         Single user licensing scheme needs to be supported. User       CA       UI                           4.9
                                                                               should be reminded about information that will be used for              3.43
                                                                               this. For example, where to get the license key from.
Ref # Use Case       Category of Use Use Case                                  Description                                                       Origin   Id     Requirement / Notes   Related
      Classification Case                                                                                                                                                              Requirem
                                                                                                                                                                                       ents




116   Deployment    Types           unattended installation / uninstallation   All products will support a completely unattended install      CA          IS                           4.1.2
                                                                               option. That is, they must provide a means of installation and             3.9.                         16.4
                                                                               upgrade that requires no user intervention whatsoever. The                 1
                                                                               product must be able to accomplish configuration by an
                                                                               outside caller supplying environmental, arguments, or any
                                                                               combination of these. The product must not depend upon a
                                                                               static configuration scheme. That is, it must be capable of
                                                                               having its configuration information written at run time, and
                                                                               then have the setup launched. This is mandatory to support
                                                                               cascaded product dependencies. An unattended installation
                                                                               may provide only the following kinds of visual feedback:

                                                                               o Progress indicator like “progress bars”, “installation
                                                                               percentage” or other means that indicate feedback in the
                                                                               event that a user is present on the target computer at the time
                                                                               of installation.
                                                                               o Final indications of success or failure, log locations, or
                                                                               support directions.
                                                                               o In the case of failure, any high level diagnostic information
                                                                               (eg. No license agreement previously affirmed).

                                                                               All temporary “pop-ups”, windows and other distracting
                                                                               information is prohibited.
Ref # Use Case       Category of Use Use Case                                    Description                                                    Origin   Id     Requirement / Notes   Related
      Classification Case                                                                                                                                                             Requirem
                                                                                                                                                                                      ents




117   Configuration Maintenance     Re-use of existing configuration information Users should not need to know what the settings and              CA     IS                           4.8
                                                                                 configurations are from existing installs or components when            36.a
                                                                                 upgrading a component or product, or using an existing
                                                                                 component or product to satisfy a pre-requisite or co-requisite
                                                                                 for the install. This information should be available at install
                                                                                 time.
118   Aggregation   Aggregation     Visibility of components                     In general embedded components or products should not be CA             IS
                    Requirements                                                 visible to the end user in the install, or in corresponding OS          3.6b
                                                                                 specific functions: start menu, add/remove programs,                    IS
                                                                                 desktop icons, program groups. This behavior should be                  3.6c
                                                                                 overridable by aggregating entities. I.e. a database
                                                                                 component might be individually installable as a product, so
                                                                                 would want to provide levels of visibility; but as an embedded
                                                                                 component that might be hidden.

119   Install       UI              separation of interview from install         the install process should not begin until the interview process CA     IS
                                                                                 is complete. The user should not have to wait and watch the             3.6e
                                                                                 install in order to complete it. The user should not be in a
                                                                                 position where he has invested significant time in the install,
                                                                                 to find that he needs specific information that he doesn't
                                                                                 have, requiring an abort and lengthy rollback.

120   Install       Basic           Respect for user customizations              A product install must not override any user customizations,   CA       UI                           4.8
                                                                                 including those done outside of SDD lifecycle operations.               3.15
Ref # Use Case       Category of Use Use Case             Description                                                     Origin   Id     Requirement / Notes            Related
      Classification Case                                                                                                                                                Requirem
                                                                                                                                                                         ents




121   Maintenance   Basic           reuse of parameters   Parameters and other customizations done by the customer CA              UI parameters that have security 4.8
                                                          in a previous install should be available in a product reinstall,        3.15 requirements
                                                          upgrade or maintenance application; or when the product is a
                                                          pre-requisite or co-requisite of a new installation.

122   Licensing     licensing       EULA Acceptance       Some products/components require that the user read and         CA       IS                                    99.13E
                                                          accept the EULA prior to installation of the product. Silent             3.9.
                                                          installation response files cannot be used to circumvent this            3

123   Development Basic             Component Model       All products are strongly encouraged to divide their products CA         IS   Clarify: is this a best practice? 17.1
                                                          into the smallest components to whatever extent possible. A              3.11 Does the standard need to
                                                          component can be defined as the smallest installable                          provide a way to enforce this.
                                                          independent unit. In other words, it supplies unit(s) of                      What defines the boundaries?
                                                          functionality that can be accessed by another component and                   Will the spec expose some
                                                          provide the advertised services. Products should have a                       specific information?
                                                          concrete specification for what component relationships are,
                                                          what the pre and co-requisite components are, and such
                                                          items as OS and OEM software requirements. The ability to
                                                          share features and components will ultimately depend on our
                                                          ability to make intelligent choices about where the boundaries
                                                          and dependencies are. In the packaging sense, a group of
                                                          components that provide one set of functionality may be part
                                                          of a product feature.
Ref # Use Case       Category of Use Use Case                                  Description                                                    Origin   Id     Requirement / Notes            Related
      Classification Case                                                                                                                                                                    Requirem
                                                                                                                                                                                             ents




124   Maintenance   Basic           component identity                         Version information should not be part of component/ product CA         IS   1. Difference between            6.2
                                                                               identity                                                                3.16 "marketing" identity and
                                                                                                                                                            deployment identity.
                                                                                                                                                            2. identity of Product vs.
                                                                                                                                                            specific Version and level of
                                                                                                                                                            version.
125   Configuration Maintenance     retention of user data / customization     user data / customizations should survive all lifecycle        CA       IS                                    4.4
                                                                               operations (except of course configuration operations that              3.18                                  4.8
                                                                               actively modify such); removal of user configuration and data
                                                                               should be optional at uninstall; default can be either remove
                                                                               or leave on a product by product basis. (Aggregation may
                                                                               override)
126   Install       Basic           requirement checks before install begins   The install process should not begin until the environment     CA       IS     What about backup               2.1
                                                                               and requisites are checked and validated. The user should               3.7    requirements needed for         4.6
                                                                               not have to invest a significant amount of time before finding          IS     updates? Would insufficient
                                                                               out that he cannot complete an install on this system.                  4.11   space for backing up changes
                                                                                                                                                       IS     trigger a failure based on this
                                                                                                                                                       4.12   requirement?

127   Aggregation   Aggregation     Layout of components                       components and products included in a larger aggregate may CA           IS   Across disks also.               2.1
                    Requirements                                               have different requirements about disk organization based on            3.7                                   5.2
                                                                               the level they are in the aggregation.                                  IS                                    17.2
                                                                                                                                                       3.13

128   Management Customer           Artifact Neutrality                        Customers have existing requirements for installations to be   CA       IS                                    8.1
                 Environment                                                   in specific formats, generally to support manageability                 3.8
                                                                               through existing systems.
Ref # Use Case       Category of Use Use Case                                     Description                                                  Origin   Id     Requirement / Notes              Related
      Classification Case                                                                                                                                                                       Requirem
                                                                                                                                                                                                ents




129   Management Customer           Interoperability with existing (and future)   Installations done using SDD must be able to be managed by CA         IS     Ultimately the goal is to use     10.4
                 Environment        management systems                            existing systems: RPM, Unicenter, Tivoli, etc. Information            3.8    SDD as a common core - but it 15.3
                                                                                  about the state of the install must be made available to those               doesn't exist in that pure world.
                                                                                  systems, and vice versa.
130   Management Customer           interoperability with multiple                Interoperability between different SDD runtime                 CA                                             10.4
                 Environment        implementations of a SDD Runtime              implementations is necessary - any runtime should be able to                                                  12.1
                                                                                  satisfy installation pre-requisites, etc from any runtime                                                     15.3
                                                                                  installed in the system
131   Uninstall     Uninstall       uninstall residuals                           All products must accomplish as cleanly as possible an         CA     IS                                      1.1.3
                                                                                  uninstall procedure. Deletions of shared components are               3.19                                    3.4
                                                                                  prohibited when such a deletion would affect the proper               IS                                      5.3
                                                                                  operation of remaining products. This also refers to any other        4.5                                     16.6
                                                                                  modifications to shared components as they affect the proper
                                                                                  installation or removal of new or remaining products. All
                                                                                  product specific resources (directories, registry keys, menu
                                                                                  items, etc) shall be removed with minimal “residual junk”.

132   Aggregation   Aggregation     dependencies and requirements (pre-reqs,      All products must furnish information about dependencies    CA        IS                                      5.2
                    Requirements    co-reqs, ex-reqs) by component                and requirements. These dependencies and requirements                 3.21                                    5.4
                                                                                  are aggregated when components are aggregated to provide
                                                                                  a set of dependencies and reqs for a solution. These
                                                                                  dependencies and requirements may be cumulative across
                                                                                  aggregated components (like disk space required), or may be
                                                                                  satisfied by other elements in an aggregation (like a
                                                                                  dependency on a db, which is a part of the suite)
Ref # Use Case       Category of Use Use Case                           Description                                                   Origin   Id   Requirement / Notes              Related
      Classification Case                                                                                                                                                            Requirem
                                                                                                                                                                                     ents




133   Install       UI              Flexibility in interview ordering   There shouldn't be a mandated sequence for installation UI    CA       IS   1. Also flexibility in grouping. 1.1.1
                                                                        design. The ordering should be flexible enough to provide a            3.28 Should the spec provide          1.1.1.3
                                                                        sensible sequence for the interview process.                                grouping for the install UI or
                                                                                                                                                    should it be simply at the
                                                                                                                                                    discretion of the optimal order.
                                                                                                                                                    2. Optimal order for minimal
                                                                                                                                                    questions specified
                                                                                                                                                    3. Hints on UI elements
Ref # Use Case       Category of Use Use Case                          Description                                                     Origin   Id     Requirement / Notes   Related
      Classification Case                                                                                                                                                    Requirem
                                                                                                                                                                             ents




134   Management Config.            reproducibility of configuration   For some products with many setup options, the number of          CA     IS                           1.1.11
                                                                       steps to fashion a functionally equivalent duplicate of the              3.29                         15.4
                                                                       product with any selected options as previously configured
                                                                       can be very unwieldy, error-prone, and time consuming. For
                                                                       this reason, it is highly recommended that facilities be
                                                                       implemented that allow a product and all of its components to
                                                                       assume the complete profile that they had at a recorded point
                                                                       in time. It is further recommended that the recording or
                                                                       “snapshot” of the product be easily usable. For the purpose of
                                                                       this guideline, “functionally equivalent” does not necessarily
                                                                       mean that a target system be of identical hardware and
                                                                       software configuration. For example, for most products a
                                                                       smaller disk space profile will not affect successful
                                                                       installation. To support reproducibility the product and
                                                                       components would normally need to store option and so forth
                                                                       in some persistent file. This could be a simple text file, XML,
                                                                       or whatever. The rationale for this guideline is to support re-
                                                                       purposing of hardware easily as well as to promote the
                                                                       deployment of products though imaging or other technology.
                                                                       This concept is quite important in large environments where
135   Management Verification       Identification of versions         Management products as well as support personnel would            CA     IS                           2.6
                                                                       like to get a list of all the specific version levels for product        4.3                          6.2
                                                                       and components that comprise a suite (and / or other
                                                                       components / products that may interact) - through non-
                                                                       interactive means
Ref # Use Case       Category of Use Use Case                            Description                                                    Origin   Id    Requirement / Notes            Related
      Classification Case                                                                                                                                                             Requirem
                                                                                                                                                                                      ents




136   Install       Cancel          Rollback from installation failure   Install Failures should make every attempt to revert the         CA     IS    Additional somewhat related    1.1.2
                                                                         system to the state it was in before the install. The reason for        4.8   requirement: The ability to    5.5
                                                                         the failure must be clearly denoted, and must cause                           rollback updates.
                                                                         subsequent installation steps to be automatically suppressed.
                                                                         This may be overridden by aggregations, so that a long and
                                                                         complex multi-product install doesn't need to be totally redone
                                                                         if one product fails.
137   Install       UI              Percolation of Error Information     Errors in low level components need to be percolated to the CA          IS   What types of information       6.2
                                                                         level of visibility to the User, and yet retain the information         4.10 does the user need?
                                                                         necessary to communicate to support.
138   Install       Basic           Reduction of Administrative Manual   Products will make reasonable efforts to define system           CA     IS   Detail how the requirement will 2.1.3
                                    Intervention                         privileges when necessary.                                              4.13 do this… aggregate
                                                                                                                                                      administrative tasks? There
                                                                                                                                                      was some confusion on this
                                                                                                                                                      requirement.
139   Deployment    General         Remote locations for co-requisites   Third party or OEM components may be restricted from the       CA       IS   There is a need to gather user 7.2
                                                                         physical distribution because of licensing or size issues.              4.14 credentials, authentication,
                                                                         They may be dynamically downloaded over the web if they                      licensing and EULA
                                                                         are available.                                                               requirements

                                                                                                                                                       The SDD must be able to
                                                                                                                                                       authenticate a user for any
                                                                                                                                                       OEMs requiring web
                                                                                                                                                       authentication.
Ref # Use Case       Category of Use Use Case                                      Description                                                   Origin   Id     Requirement / Notes           Related
      Classification Case                                                                                                                                                                      Requirem
                                                                                                                                                                                               ents




140   Aggregation   Aggregation     Use of existing managed/unmanaged              many artifacts require installation of technologies not related CA     IS                                   7.3
                    Requirements    components                                     to the running of the installed product, but needed to support         4.15
                                                                                   the installation process and the management process. It                IS
                                                                                   should be possible to streamline the dependencies to reduce            4.17
                                                                                   the size of the footprint (download time). For example if the
                                                                                   installer requires a JRE, and the product requires a JRE, it
                                                                                   should not be necessary to include 2 distinct copies of the
                                                                                   JRE in the packaging.

141   Install       Cancel          Runtime override of errors                     Products should try to make their “best effort” to prepare the CA      IS   Does SDD need support for       1.1.2.1
                                                                                   system for proper operation. Some circumstances are not                4.20 differentiating between 136     13.1
                                                                                   predictable prior to the beginning of installation, and there               and 141? Which one can          13.2
                                                                                   should be a way to intercept a failure and make a necessary                 overrides the other? Should
                                                                                   change without having to roll back the install and restart. Of              that be defined/controlled by
                                                                                   course, the user must be in a position to reject such changes               the SDD?
                                                                                   if they could represent a danger to correct system operation
                                                                                   or have other serious undesirable side effects.

142   Management Customer           Use of other management systems to             Uninstallation or modification of a SDD-based install by other CA      IS                                   10.4
                 Environment        uninstall, reconfigure, upgrade, patch, etc.   management systems (SDD or non-SDD) should be either                   4.21                                 15.3
                                                                                   prevented or supported.
143   Uninstall     Basic           Shared resource inventory control              All products that share any resources including but not limited CA     IS                                   3.4
                                                                                   to registry keys, files, menu items, icons, binaries, and links        4.27                                 16.6
                                                                                   should employ a mechanism that can safely remove these
                                                                                   shared items when the last reference to them has been
                                                                                   released.
Ref # Use Case       Category of Use Use Case                                  Description                                                      Origin   Id     Requirement / Notes             Related
      Classification Case                                                                                                                                                                       Requirem
                                                                                                                                                                                                ents




144   Security      Security        Handling of sensitive data                  All sensitive data items must be encrypted on all storage    CA          IS                                     4.10
                                                                               media, over the network, and on the product image whether                 4.30                                   17.3
                                                                               installed or not. This applies to response files as well. The
                                                                               sole exception is to the licensee’s name and to
                                                                               daemon/service account names where applicable. Sensitive
                                                                               data refers to passwords, personal user information including
                                                                               but not limited to social security, name and address,
                                                                               telephone number etc.
145   Maintenance   Patch           fixes reapplied after service packs        it must be possible for a user to determine whether new       CA                 Need clarification of this. What 1.3.1
                                                                               maintenance (service pack) will supersede any fixes already                      is the best practice? rollback
                                                                               applied; and preferably to roll out the affected fixes before                    of fixes when service packs
                                                                               installation of the service pack and reapply after                               are applied or apply over.

146   Deployment    Types           Upgrade from Evaluation to Licensed        User has previously installed an evaluation or trial version and CA       UI                                     1.3.2
                                                                               now wants to upgrade to a licensed version. This may or may               3.5
                                                                               not include additional features made available.

147   Configuration Maintenance     Management of configuration for multiple   Multiple installations targeted to a single hosting environment CA               Some should and some            2.9
                                    installs                                   must not interfere with configuration of existing installations.                 should not survive across a     3.5
                                                                               Uninstallation of any (regardless of install order) should not                   lifecycle operation.            17.4
                                                                               impact the configuration of remaining installs.

148   Uninstall     Hosting         Hosting environment Uninstall              A hosting environment will only be uninstalled if all targeted   CA                                              3.4
                    Environment                                                installations have previously uninstalled.                                                                       16.6
Ref # Use Case       Category of Use Use Case               Description                                                    Origin   Id     Requirement / Notes           Related
      Classification Case                                                                                                                                                Requirem
                                                                                                                                                                         ents




149   Grid          Grid            Archive                 Application contents must be logically bundled in a single and GGF/     1.1a Clarification on term for        7.2
                                                            consistent archive                                             ACS           archive: for submission of a     7.6
                                                                                                                                         job we are proposing that all
                                                                                                                                         files will be bundled into a
                                                                                                                                         single file. This is the current
                                                                                                                                         discussion in ACS. Proposing
                                                                                                                                         repository in system that
                                                                                                                                         accepts archives and provides
                                                                                                                                         WS manageability.

                                                                                                                                           Other services in Grid can
                                                                                                                                           have access to archive:

                                                                                                                                           - entry point for bundled
                                                                                                                                           application contents.
                                                                                                                                           - policy is specific to the
                                                                                                                                           application.
                                                                                                                                           - could have an envelope
                                                                                                                                           specification and provide a
                                                                                                                                           WS interface
                                                                                                                                           - policy relates to both
                                                                                                                                           deployment and runtime.

150   Grid          Grid            Diversity of contents   ACS should allow a diversity of information as its contents,   GGF/     1.1b                                 2.3
                                                            including application middleware, OS, or firmware              ACS                                           5.9
Ref # Use Case       Category of Use Use Case                                    Description                                                    Origin   Id     Requirement / Notes   Related
      Classification Case                                                                                                                                                             Requirem
                                                                                                                                                                                      ents




151   Grid          Grid            geographically or admistratively separated   ACS should allow bundling a set of applications which are to   GGF/     1.1c                         2.3
                                    topology                                     be deployed and executed in geographically and / or            ACS                                   3.3
                                                                                 administratively separated files.                                                                    11.2
152   Grid          Grid            Archive Information completeness             All information required for Grid Task execution must be       GGF/     1.2a                         5.10
                                                                                 logically bundled in an archive                                ACS
153   Grid          Grid            SDD extensions                               SDD shall be extended by using an extension point              GGF/     1.2b                         13.4
                                                                                 <xsd:ANY> in order to include ACS namespace elements           ACS
                                                                                 such as owner, EPR, access rights, etc.
154   Grid          Grid            Operation granularity                        {Archives must be stored in a repository} Once registered,     GGF/     1.3a                         7.9
                                                                                 operations must be allowed in a smaller unit in the archive    ACS
155   Grid          Grid            Incremental upgrading                        Incremental upgrading of the application archive must be       GGF/     1.3c                         7.9
                                                                                 supported                                                      ACS
156   Grid          Grid            Standard Archive Format                      Standard format of archive and interface to the repository     GGF/     2.1a                         7.10
                                                                                 needs to be defined                                            ACS
157   Grid          Grid            External references to files                 To reduce the size of the archives, reference to external      GGF/     2.4a                         7.2
                                                                                 storage/ files should be allowed in them                       ACS                                   7.3
158   Grid          Grid            differential archives                        ACS must provide mechanisms for minimizing the network         GGF/     2.4b                         7.8
                                                                                 traffic by allowing differential archives                      ACS
159   Grid          Grid            redundancy elimination                       When managing content of archives in the repository,           GGF/     2.4c                         7.3
                                                                                 mechanisms for eliminating redundancy and minimizing disk      ACS
                                                                                 usage should be allowed.
160   Grid          Grid            access control                               Appropriate access control to archives is required             GGF/     3.b                          5.11
                                                                                                                                                ACS                                   7.11

161   Grid          Grid            opacity of contents                          Archive contents can be any opaque entries that are required GGF/       4.d                          7.12
                                                                                 for execution of application                                 ACS
Ref # Use Case       Category of Use Use Case                                  Description                                                       Origin   Id   Requirement / Notes            Related
      Classification Case                                                                                                                                                                     Requirem
                                                                                                                                                                                              ents




162   Maintenance   Patch           Patch Target                               Fix application should verify the fix version and installed       CA                                           1.1.10
                                                                               product version match before any files are replaced.                                                           1.1.12
163   Maintenance   Patch           Insure integrity                           Fix application should verify prereqs/coreqs at the beginning     CA                                           1.1.10
                                                                               of the installation before any files are replaced.                                                             1.1.12
164   Maintenance   Patch           System Requirements                        Fix application should verify necessary free space is available   CA                                           1.1.10
                                                                               before any files are replaced.                                                                                 1.1.12
165   Maintenance                                                              Maintenance should be bundled to allow application to             CA                                           1.1.10
                                                                               different install types of the same product (agent vs. server                                                  5.7
                                                                               vs. admin guy, common components shipped by diff
                                                                               products, embedded components, etc). Fix application should
                                                                               be able to determine what files need to be updated and
                                                                               location of said files for all scenarios.
166   Maintenance   Patch           Reboot / service start/stop management     Fix application should handle any necessary starting/stopping     CA                                           1.1.10
                                                                               of products/components and necessary reboots.                                                                  1.1.12

167   Maintenance   Patch           Diagnosing & Debugging                     Fix application should provide a user viewable record of what CA                                               1.1.10
                                                                               maintenance is applied (history file).                                                                         1.1.12
                                                                                                                                                                                              6.2
168   Maintenance   Patch           uninstall                                  Fix application should allow for uninstall at a later time.       CA            Is there a concept of fixes    1.1.12
                                                                                                                                                               which cannot be undone?
                                                                                                                                                               Need to caution about
                                                                                                                                                               synchronization between this
                                                                                                                                                               and other requirements
                                                                                                                                                               involving rollback.
169   Maintenance   Patch           unattended installation / uninstallation   Fix should provide an “unattended” installation/uninstall mode CA                                              1.1.12
                                                                               (similar to Ref# 116 for install)                                                                              16.4
Ref # Use Case       Category of Use Use Case                              Description                                                    Origin   Id     Requirement / Notes            Related
      Classification Case                                                                                                                                                                Requirem
                                                                                                                                                                                         ents




170   Specialized   Accessibility    accessible installation               The installation program must work well with assistive        CA        UI                                    10.1
                                                                           technologies like screen readers, screen magnifiers, adaptive           3.24
                                                                           keyboards, and other alternative input devices.
171   Development Install Building   Debugging                             Developers need support for problems encountered in the       CA               Detail what specific errors this 13.1
                                                                           development process. This is a different level of error and                    requirement would need to        13.2
                                                                           diagnostics than provided to the install user.                                 provide diagnosis.
                                                                                                                                                          Consistency checking?
                                                                                                                                                          Validation errors? Etc.
172   Management licensing           license events                        A construct in SDD that gives us an ability to use what we've OASIS                                             99.13Z
                                                                           deployed through a separate business event.
173   Development Application        Application modeling                  Application modelers describe the expectation around the         IBM           Requirement: Declaration of    2.1.5
                  Modeling                                                 structure of the application, the resources that it creates, and               created resources,             2.2
                                                                           their target environment for deployment.                                       relationships, requirements    3.1
                                                                                                                                                                                         3.2
174   Development Install Building   Application packaging                 Application packagers refine the deployment information,         IBM           Requirement: Declaration of    2.1.5
                                                                           adding detail about its content, dependencies, target                          created resources,             3.1
                                                                           environment and resulting resources.                                           relationships, requirements    3.2
175   Aggregation   Legacy           solution integration using wrappers   Solution integrators will typically be focused on the ability to IBM           Requirement: Wrappers.         8.1
                                                                           create wrappers for existing products, and to aggregate
                                                                           descriptors into a composite descriptor.
176   Aggregation   Configuration    solution configuration                Solution integrators also need to be able to add configuration IBM             Requirement: Specifying        1.1.1.4
                                                                           to the composite, in order to bring the overall solution into a                configuration.
                                                                           usable state.
Ref # Use Case       Category of Use Use Case                               Description                                                   Origin   Id   Requirement / Notes             Related
      Classification Case                                                                                                                                                               Requirem
                                                                                                                                                                                        ents




177   Deployment    General         end-user deployment process             Although end-user solutions are typically deployed into a       IBM         Requirement: Declarative        2.1
                                                                            more specific environment than a product, it is important to                description of logical target
                                                                            note that there is still a strong requirement to support the                environment.
                                                                            definition of a logical target environment which can then be
                                                                            mapped to multiple physical environments. This is because a
                                                                            solution will be deployed into multiple different environments,
                                                                            both as part of its lifecycle (development, system test,
                                                                            performance test, acceptance test, production) and because
                                                                            a solution may be deployed to multiple production
                                                                            environments.
178   Deployment    Planning        data center environment provisioning    The distributed scenario typically involves the use of general IBM          Requirement: Declaring        2.1.5
                                                                            purpose change management applications that manage the                      requirements, including
                                                                            lifecycle of a set of resources (data center), rather than a                specifying required
                                                                            solution-specific installation program. Planning for a change               connectivity between
                                                                            will involve making a set of decisions such as provisioning                 resources. Requirement:
                                                                            new servers or repurposing existing ones, deciding on a                     Ability to check dependencies
                                                                            network topology, configuring firewalls, etc.                               and plan deployment based on
                                                                                                                                                        descriptor plus resource
                                                                                                                                                        instance information (without
                                                                                                                                                        direct access to target
                                                                                                                                                        environment).

179   Deployment    Planning        multiple package change plan ordering   A distributed scenario may also involve installing multiple   IBM           Requirement: Ability to         2.1.4
                                                                            packages in order to satisfy dependencies.                                  understand inter-package
                                                                                                                                                        sequencing dependencies.
Ref # Use Case       Category of Use Use Case                                 Description                                                       Origin   Id   Requirement / Notes              Related
      Classification Case                                                                                                                                                                      Requirem
                                                                                                                                                                                               ents




180   Deployment    Planning        change list construction                  In a data center scenario, the desire is for automated          IBM             Requirement: Ability to match    3.1
                                                                              assistance to be provided in the planning process, based on                     resulting resources of one
                                                                              information in the descriptor. To support this, the descriptors                 package to requirements of
                                                                              for both the overall solution and the individual products or                    another.
                                                                              applications need to provide information about the resulting
                                                                              resources and relationships that will be established by
                                                                              installing a package, as well as describing the required
                                                                              resources and relationships.
181   Install       Lifecycle       solution lifecycle                        Improved lifecycle management is an important value that the IBM                Requirement: undo support       1.1.2
                                                                              SDD contributes to this scenario, including coordination of                     Requirement: Ability to specify 1.1.4
                                                                              install and rollback, as well as managing maintenance.                          updates to an existing solution 1.1.5

182   Development Build Process     build traceability                        The dependency information establishes a good basis for        IBM              Requirement: Traceability to
                                                                              impact assessment during incident management and change                         build environment.
                                                                              planning, and provides information for problem determination.
                                                                              The latter is assisted by providing traceability back into the
                                                                              development environment (build) as part of the descriptor.

183   Aggregation   Hosting         different environment types               Solutions described with an SDD may involve installing            IBM           Expressing dependencies on 2.3
                    Environment                                               content into environments other than the OS                                     environments other than OS
184   Install       Integrity       integrity checking/lifecycle management   When installing, updating or uninstalling software, the install   ?             Requirement: dependency           2.1
                    checking        based on dependencies                     program should determine whether this will impact other                         information, related to lifecycle 2.2
                                                                              installed software.                                                             operations
Ref # Use Case       Category of Use Use Case                                  Description                                                  Origin   Id   Requirement / Notes                 Related
      Classification Case                                                                                                                                                                     Requirem
                                                                                                                                                                                              ents




185   Maintenance   Basic           relating updates                           Maintenance must come with a descriptor that describes the   ?             provide information needed to 1.1.4
                                                                               maintenance and how it modifies/updates information                        manage maintenance lifecycle 1.1.5
                                                                               provided in descriptors for previous versions                              and define relationships
                                                                                                                                                          between successive
                                                                                                                                                          descriptors
186   Install       Validation      Misbehaving entities in host environment   Misbehaving entities in a hosting environment need to be                   The SDD must be able to        1.1.7
                                                                               identified                                                                 validate a hosting environment
                                                                                                                                                          to determine if an installable
                                                                                                                                                          Unit is not working as
                                                                                                                                                          intended.

                                                                                                                                                          The SDD must be able to
                                                                                                                                                          validate a hosting environment
                                                                                                                                                          to determine if the Hosting
                                                                                                                                                          Environment is not working as
                                                                                                                                                          intended after installation of an
                                                                                                                                                          Installable Unit.

187   Deployment    Types           Modifications between Test & Production    Custom tweaks to the installation by testers should be        OASIS        The installation must provide a 4.1.2
                                                                               captured or recorded by the SDD to perform installations on a              way for user selections made
                                                                               production machine with those same tweaks.                                 during an installation to be
                                                                                                                                                          captured.
                                                                                                                                                          The installation must provide a
                                                                                                                                                          way for user selections
                                                                                                                                                          captured in a previous
                                                                                                                                                          installation to be used in the
                                                                                                                                                          current installation.
Ref # Use Case       Category of Use Use Case                                  Description                                                    Origin   Id    Requirement / Notes            Related
      Classification Case                                                                                                                                                                   Requirem
                                                                                                                                                                                            ents




188   Maintenance   Updating         Element Update                            Element Update capability refers to the functionality to update DELL    2.0   Maintenance of individual      1.3.3
                    Firmware &                                                 a system's individual elements (i.e. software). Elements are                  components of a composite;     5.5
                    Device Drivers                                             indivisible, atomic components that the customer is aware                     specific reference to system   10.4
                                                                               and needs the ability to update individually. Some examples                   firmware, peripheral firmware,
                                                                               of elements include system firmware (BIOS, BMC firmware),                     drivers and OS updates as
                                                                               peripheral firmware, driver, OS component or an application.                  well as application.

189   Management Coexistence         Install into existing change management   Standardized packages to support change management             DELL     2.0   Standardization of packaging   15.3
                                     environment                               solution based on the customer's choices; Customers want                      names; interoperability with
                                                                               packages with a consistent naming and versioning                              existing management
                                                                               convention and behavior. This consistency is required for                     solutions; identity
                                                                               automation and can be integrated into any of the following                    requirements;
                                                                               CM solutions:

                                                                                - OS Vendor - OS vendor supplied software update
                                                                               mechanism (e.g. RedHat up2date or Windows Update)
                                                                                - ISV - 3rd party software change management solution (e.g.
                                                                               Microsoft SMS, Altiris, Novell Zenworks, Symantec CCM)
                                                                                - Customer developed - Customer develops their own in-
                                                                               house solution.
Ref # Use Case       Category of Use Use Case                                   Description                                                    Origin    Id    Requirement / Notes                Related
      Classification Case                                                                                                                                                                         Requirem
                                                                                                                                                                                                  ents




190   Maintenance   Aggregation     Bundle updates                              Facilitate qualified bundle to support system update to update DELL      2.0   composition; maintenance of 2.1
                    Requirements                                                all or a subset of a system's individual elements. Update                      bundles; identity; requirements 3.1
                                                                                package contains following meta data to support the creation                   definitions                     3.2
                                                                                of standardized sets of software bundle:                                                                       6.1

                                                                                 - Name
                                                                                 - Version
                                                                                 - Applicability
                                                                                 - Dependencies
191   Install       Basic           Install to local machine or remote                                                                         DELL       2.0 specfication machines.
                                                                                Update packages must be installable to a local machine, or installed to one or more remote of targets;            2.1
                                                                                                                                                               flexibility in specfification of   3.1
                                                                                                                                                               target;duplicate use case
192   Install       Basic           Install from removable media or network     The update packages must be installable from removable         DELL       2.0 duplicate use case                  7.2
                                                                                media or from a network location
193   Install       General         Identification of firmware and drivers on   Inventory the firmware and driver versions currently installed DELL       1.2 Implementation inference:           15.7
                                    system                                      on the system                                                                  need to manage an inventory
194   Aggregation   Aggregation     selection of elements from update bundles   Compare with a defined set of update packages to determine DELL           1.2 The SDD needs to be able to         4.1.2
                    Requirements    to install                                  which one needs update                                                         compare installable unit           5.7
                                                                                                                                                               versions to IUs in the installed   5.12
                                                                                                                                                               state. A matrix of an IU's
                                                                                                                                                               dependent versions of other
                                                                                                                                                               IUs needs to be exposed by
                                                                                                                                                               the SDD to allow for conflict
                                                                                                                                                               management.; ability to identify
                                                                                                                                                               installed state of component -
                                                                                                                                                               management interfaces
Ref # Use Case       Category of Use Use Case                                  Description                                                    Origin   Id    Requirement / Notes                Related
      Classification Case                                                                                                                                                                       Requirem
                                                                                                                                                                                                ents




195   Aggregation   Aggregation      Selective deployment of elements in update Deploy changes using selected update packages                 DELL     1.2   A matching IU version in the
                    Requirements     bundles                                                                                                                 SDD will need to update an IU;
                                                                                                                                                             composition; maintenance;
                                                                                                                                                             identity
196   Aggregation   Updating         identification of applicable packages     The key to step 2 (item 194) of the change management            DELL   1.2   The SDD needs to allow for a
                    Firmware &                                                 process is to programmatically figure out what packages are                   firmware IU with hardware
                    Device Drivers                                             applicable to what components on the system; as well as the                   Target Host.
                                                                               version superseding of the underlying software components
                                                                               (Firmware/Driver) Some of the problems in this area are:                      Implementation inference:
                                                                                - There are no industry standards on hardware update                         need to provide a pluggable
                                                                               applicability; The applicability of the update package varies                 interface for vendor-specific
                                                                               from component to component and from vendor to vendor.                        low-level routines to facilitate
                                                                                - Hardware applicability rules are defined and implemented                   discovery of installed IUs.
                                                                               through programming which varies from vendor to vendor
                                                                               and is very difficult to maintain.
                                                                                - The update applicability rules are handled differently across
                                                                               different layers of the software stack, e.g. application, device
                                                                               drive and firmware.:


197   Artifacts     Basic            Consistent naming for artifacts           Customers want update packages with a consistent naming DELL            1.2   duplicate use case                 6.6
                                                                               and versioning convention; including drivers, applications and
                                                                               hardware firmware. This consistency is required for
                                                                               automation.
Ref # Use Case       Category of Use Use Case                                 Description                                                      Origin   Id    Requirement / Notes              Related
      Classification Case                                                                                                                                                                      Requirem
                                                                                                                                                                                               ents




198   Deployment    Basic           Consistent update mechanism               Currently there are too many update mechanisms. No               DELL     1.2   requirements against the         15.9
                                                                              standard is defined for updating/installing firmware, BIOS,                     implementation - request for     16.8
                                                                              drivers and applications. This is no standard packaging                         standardization of the install
                                                                              mechanism for updating across the management stack.                             technologies - outside scope.
                                                                              There are so many update utilities including online/ offline                    Standardization for packaging
                                                                              flash utilities. There is a proliferation of update tools from                  schema and interfaces for
                                                                              vendors. Different manufacturers have a different update                        querying state of installed
                                                                              mechanism for the same hardware.                                                software. (version,
                                                                                                                                                              configuration, etc).
199   Deployment    Basic           Self-contained                            Update packages are self-contained (knows how to inventory, DELL          1.3   requirements against the         5.13
                                                                              validate and apply)                                                             implementation.
200   Management Basic              Management-ready                          Update packages must be management-ready (self-             DELL          1.3   SDD must be deployable from      15.10
                                                                              classified, consistent with support site.); provide common                      managed update repository.
                                                                              infrastructure for software provisioning and change                             Some sort of classification ID
                                                                              management solutions.                                                           may be used.

                                                                                                                                                              Implementation inference:
                                                                                                                                                              needs to integrate with or
                                                                                                                                                              provide a pluggable interface
                                                                                                                                                              for vendor-specific
                                                                                                                                                              provisioning functionality.

201   Artifacts     Basic           Standard Package description              Update packages must have a standard package description DELL             1.3   duplicate use case               6.1
                                                                                                                                                                                               6.6
                                                                                                                                                                                               7.2
202   Management Coexistence        Integration with existing solutions and   Update packages must be easily integratable into customers' DELL          1.3   Scripting support                5.14
                                    processes                                 existing solutions and processes.
Ref # Use Case       Category of Use Use Case             Description                                                       Origin   Id    Requirement / Notes               Related
      Classification Case                                                                                                                                                    Requirem
                                                                                                                                                                             ents




203   Deployment    Basic           Stand-alone utility   An update package shall be designed to be a simple stand-     DELL         3.1   requirements against the          99.44
                                                          alone utility that can perform a specific update on a system                     implementation; support for
                                                          directly without any other dependencies other than OS                            interactive user
                                                          dependency. The update procedure can be as simple as                             interfaces;dependency
                                                          getting the desired Update Package and applying it locally by                    validation ; identification of
                                                          launching an interactive user interface. The interactive user                    transient files in the SDD;
                                                          interface will guide the user through the install/update                         definition of atomicity in SDD;
                                                          process. During the update process, dependencies will be
                                                          validated against the current inventory of the system where
                                                          the update package is running. Hardware updates shall be
                                                          fully atomic and transitory; nothing persisted aside from the
                                                          flash or payload. Application update leaves files and may
                                                          also leave environmental changes.

204   Deployment    Basic           scriptability         In addition to the interactive user interface, update packages DELL        3.2   command line interface;         99.44
                                                          shall also support a command-line interface (CLI). This                          standardization of return codes
                                                          allows users to script automated batch install/update. The set                   - out of scope?
                                                          of CLI options and return codes need to be standardized,                         Implementation requirements?
                                                          regardless of what type of package it is.

                                                          The command line interface of the update package is
                                                          designed to enable it script-ability. It could be used to build
                                                          scripted batch install/update in an unattended fashion. This
                                                          provides easy integration into customer's existing change
                                                          management process.
Ref # Use Case       Category of Use Use Case         Description                                                    Origin   Id    Requirement / Notes            Related
      Classification Case                                                                                                                                          Requirem
                                                                                                                                                                   ents




205   Management Basic              Manageability     Update packages shall provide manageability through their      DELL     3.3   SDD needs to expose all       99.44
                                                      meta-data for the payload. It shall contain classification                    metadata needed to provide IU
                                                      information, hardware applicability information, versioning                   management; classification
                                                      information and dependencies information.                                     metadata as well as
                                                                                                                                    requirements (specifically
                                                                                                                                    hardware) and versioning;

206   Artifacts     Basic           Consume-ability   An update package shall package into a well-defined [zipping] DELL      3.4   Artifact format explicitly    99.44
                                                      format for all OS to make it transparent. It could be easily                  excluded from scope in
                                                      extracted by standard program on that OS. The                                 charter; requirements on
                                                      subcomponents of the package could then be used by any                        implementation? Api for list,
                                                      software application to perform inventory, validation and                     update, delete of
                                                      install/update                                                                subcomponents in a package?

207   Security      Security        Security          Package needs to be signed to ensure the content have not      DELL     3.5   Package signing; security of   99.44
                                                      been tampered with before the package is deployed. The                        contents;
                                                      application of change management solution then can verify
                                                      signed packages.
208   Aggregation   Aggregation     Aggregation       A package may aggregate other packages to solve                DELL     3.6   composition                    99.44
                    Requirements                      dependency problems.
209   Specialized   Globalization   Globalization     The user interfaces (GUI/CLI) exposed by update package        DELL     3.7   localization                   99.44
                                                      shall support localization.
210   Deployment    Basic           Logging           A standardized common private log shall be designed. The       DELL     3.8   SDD needs to provide           99.44
                                                      log shall capture success/failure and detailed warning/error                  metadata for logging
                                                      message of each package transaction.                                          messages
Ref # Use Case       Category of Use Use Case             Description                                                    Origin    Id    Requirement / Notes             Related
      Classification Case                                                                                                                                                Requirem
                                                                                                                                                                         ents




211   Specialized   General         Support innovation                                                                   CA                                              2.6.5




                                                                                                                                                           Guidelines need to be defined for chang
                                                          Regardless of how well thought out the use cases and requirements are for the SDD, new use cases and changes in technology and th
212   Maintenance   Maintenance     Maintenance rollups   Support packages that are rollups of previous versions (e.g. base plus maintenance plus patches
                                                                                                                          IBM                                             2.4.6
213   aggregation   Aggregation     Suite construction                                                                    IBM                                             2.4.6
                    Requirements                          Support packages that aggregate multiple products or components into a single artifact or "image".
214   aggregation   Aggregation     Marketing Bundles                                                                     IBM                                             2.4.6
                    Requirements                          Allow multiple alternative packagings of a product (e.g. a customized version of a product that only has a subset of the features, or has
Ref # Use Case       Category of Use Use Case   Description                                                      Origin   Id   Requirement / Notes   Related
      Classification Case                                                                                                                            Requirem
                                                                                                                                                     ents




                                                pecific problems of supporting in-place upgrades:
215   Maintenance   Upgrade         Sidegrade                                                                    Sun                                 2.1.6.1
                                                By only supporting in-place upgrades, ISVs must deliver
                                                complex solutions
                                                to enable customers to enable customers to update/upgrade
                                                in place without
                                                having to force customers to allocation additional systems for
                                                update/upgrade
                                                purposes. The matrix of version combinations required to be
                                                tested and
                                                supported can quickly become extremely complex. It is costly
                                                for ISVs to be
                                                able to certify that many of these combinations of component
                                                versions
                                                will work properly. The pervasive support results in complex
                                                and error
                                                prone technical solutions which often result in corrupted in-
                                                place
                                                installations, forcing a removal/reinstall.

                                                Specific use case of sidegrade:

                                                Customer is running particular customized version of
                                                software, including
                                                custom data that was created after the initial install, and
                                                custom
                                                configuration tuned for their environment. This is running
                                                either
                                                in a production environment or development environment,
                                                with high
                                                availability requirements (i.e. can't be taken down except
                                                during
                                                scheduled maintenance periods).
Confomance Level




2
Confomance Level




1




1
Confomance Level




2




2
Confomance Level




2




1




1




1
Confomance Level




2




2




N/A (Media)
Confomance Level




N/A (Media)




1


N/A (Runtime; SDD does not
preclude in any CL)




1
Confomance Level




N/A (Runtime; SDD does not
preclude in any CL)

2/3 (need to decide which CL
includes
security/roles/privileges)



3



3




3


1
1
Confomance Level




N/A (Runtime; SDD does not
preclude in any CL)




N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




N/A (Runtime; SDD does not
preclude in any CL)




N/A (Runtime; SDD does not
preclude in any CL); related
SDD function would be CL3
Confomance Level




N/A (Runtime; SDD does not
preclude in any CL); related
SDD function would be CL3




1
Confomance Level




1




N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




N/A (Runtime; SDD does not
preclude in any CL)




2/3 (need to decide which CL
includes
security/roles/privileges)
Confomance Level




1




N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




2
Confomance Level




N/A (Runtime; SDD does not
preclude in any CL)




3
Confomance Level




2
Confomance Level




3




1



1


1


1
Confomance Level




1




N/A (Media)
Confomance Level




N/A (Runtime; SDD does not
preclude in any CL)




2



2


1


N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




2



1



2




1

N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




N/A (Runtime; SDD does not
preclude in any CL)




1




2
Confomance Level




3



1


2




2/3 (need to decide which CL
includes
security/roles/privileges)
Confomance Level




1




2




1




2
Confomance Level




1




2



1


1



2
Confomance Level




1




1




2




1
Confomance Level




3



2
Confomance Level




2




2
Confomance Level




2




2




1
Confomance Level




2




1
Confomance Level




1




2
Confomance Level




1




2



N/A (Runtime; SDD does not
preclude in any CL)




N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




1
Confomance Level




N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




N/A (Runtime; SDD does not
preclude in any CL)



N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




1




1
Confomance Level




1
Confomance Level




1




1



N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




1
Confomance Level




1




2




N/A (Runtime; SDD does not
preclude in any CL)




N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




2/3 (need to decide which CL
includes
security/roles/privileges)


N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




1




N/A (Runtime; SDD does not
preclude in any CL)




1




2




1
Confomance Level




1



1, 2, 3



N/A (Runtime; SDD does not
preclude in any CL)




2
Confomance Level




N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




1
Confomance Level




N/A (Runtime; SDD does not
preclude in any CL)




N/A (Runtime; SDD does not
preclude in any CL)

2/3 (need to decide which CL
includes
security/roles/privileges)


N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




2




N/A (Runtime; SDD does not
preclude in any CL)




N/A (Runtime; SDD does not
preclude in any CL)

N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




1




1




1



1




N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




1




1
Confomance Level




1


1

1


1

1

N/A (outside SDD scope)

1

N/A (outside SDD scope)

N/A (outside SDD scope)


2/3 (need to decide which CL
includes
security/roles/privileges)
1
Confomance Level




1

1

1

2




1


N/A (Runtime; SDD does not
preclude in any CL)

N/A (Runtime; SDD does not
preclude in any CL)




N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




N/A (Runtime; SDD does not
preclude in any CL)

N/A (Runtime; SDD does not
preclude in any CL)




1



1


1, 2


1
Confomance Level




1




1




1
Confomance Level




1




1



1




1

1
Confomance Level




1




3




N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




1




1
Confomance Level




2




1


N/A (Media)

N/A (Runtime; SDD does not
preclude in any CL)
2
Confomance Level




2



1




1
Confomance Level




N/A (Runtime; SDD does not
preclude in any CL)




N/A (Runtime; SDD does not
preclude in any CL)
N/A (Runtime; SDD does not
preclude in any CL)




1


1
Confomance Level




1




N/A (Runtime; SDD does not
preclude in any CL)
Confomance Level




1




N/A (Runtime; SDD does not
preclude in any CL)




1



2

1
Confomance Level




1




                   1
2

2
Confomance Level




1
                                         Category of
Ref #        Classification   Use Case   Use Case    Use Case

             Install                     Developer   Administrators /
             Creation                    Types       Release Managers
        82
             Install                     Developer   Application Developers
             Creation                    Types



        80
             Install                     Developer   Application Modelers
             Creation                    Types
        83
             Install                     Developer   Application Packagers
             Creation                    Types
        84
             Install                     Developer   Solution Integrators
             Creation                    Types

        81
Description                                                    Origin   Id

Administrators/release managers who define a set of          IBM
packages to be installed together, but not necessarily for a
single purpose
Application developers who create new application code (e.g. IBM
J2EE apps, web content, .NET apps), which forms a
composite application typically spanning multiple machines
and environments. This role might be split into two - the
application modeler, and the application packager.

Application modelers describe the expectation around the         IBM
structure of the application, the resources that it creates, and
their target environment for deployment.
Application modelers describe the expectation around the         IBM
structure of the application, the resources that it creates, and
their target environment for deployment.
Solution integrators who bring together products from multiple IBM
vendors, plus the composite applications described above,
and configure them into an overall solution.
Requirement                              Notes




Requirement: Declaration of created
resources, relationships, requirements

				
DOCUMENT INFO
Description: Use Cases Describing Business Processes document sample