Task: Specify Package Configuration
This task focuses on specifying the package configuration.
Disciplines: Architecture
Purpose
  • To identify and specify configuration parameters for the global settings and other business organization structure and hierarchy elements inherent in the package
  • To establish and document a set of rules and standards for setting configuration parameters
  • To obtain agreement from the stakeholders that the configuration parameter settings fulfill the business processes and organizational requirements as specified in the solution
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
  • None
Optional:
    Outputs
      Steps
      Create Package Configuration Specification

      A package configuration describes the selection and setting of values and options that customize a COTS package for installation.

      The customization rules and standards for configuration parameters are key elements that should be well known, agreed to, and documented with the stakeholders so that the package can be can be correctly configured with the appropriate settings to support the intended business processes and organization. There might have to be compromises made in the business processes and organization to accommodate the limitations of the chosen package. The selected package might provide some assistance with configuration tools and techniques.

      Building on the rules and standards and the package characteristics, the COTS Configuration Specification artifact identifies and describes the parameters for a solution-specific version of a package. A variety of means such as configuration scripts or files containing lists of parameters may be used to identify and describe the parameters that typically include the following:

      • Global settings.
      • Country settings.
      • Languages.
      • Currencies (such as exchange rates, decimal places, and rounding rules).
      • Units of measurement.
      • Calendar.
      • Chart of accounts.
      • Company codes.
      • Organization structure and hierarchy elements.

      While it is essential to configure the package parameters themselves correctly to allow the intended business processes and organization to operate, it is vital to document the background decisions made in choosing the parameter settings. This documentation should include:

      • Who performed the configuration
      • Change management history
      • Who approved the changes and the configuration
      • Scenarios required to test the configuration
      • How the configuration meets the stakeholder's business process and organizational requirements
      Validate and Verify Package Configuration

      An instance of an Executing System might be required to assist stakeholders in the verification and validation of the configuration parameters. Validation and verification of the configuration parameters comes through the successful execution of the Test Plan defined for the project. The critical use cases and critical nonfunctional requirements will guide in the stakeholder validation and verification of the configuration during testing.

      Review and record the agreement between the project team and the stakeholders concerning the configuration parameters contained in the baselined Package Configuration Specification.