Skip to content

Glossary

Depreciation

In the field of software development, deprecation is the situation where an existing feature of a product is considered obsolete in light of a new standard or new use, but is nevertheless maintained in more recent versions of the product while being made inaccessible to new customers (for compatibility reasons, and to give existing customers time to prepare to do without this feature) and is therefore expected to disappear in the future.

The deprecation of a Systancia feature means that the feature in question

  • will no longer be included in product versions that will be available in GA after the end-of-life date communicated for On Client Infrastructure products;
  • will be removed from Systancia's SaaS production platforms upon the feature's end-of-life date.

When Systancia decides to deprecate a feature, an information note is sent to customers specifying the official date of withdrawal of this feature and any alternatives to replace the feature, where available.

Concepts of deliverables

Systancia distinguishes between three types of deliverables associated with its software products:

The Product

  • Available for download from the Systancia Marketplace.
  • Maintained and supported in accordance with Systancia's Terms and Conditions of Use (TCU).
  • Upward compatibility of all programmatic interfaces (API, CLI, web service, others) that are “visible to the customer” and “documented”. A document detailing this upward compatibility is available on the Systancia Marketplace.

The “Service Deliverable”

  • Delivered to a customer by Systancia's professional services teams or its integration partners as part of a project.
  • May be maintained and/or supported by Systancia or its partners as part of an additional service (Third-Party Application Maintenance, TMA).
  • The customer becomes the owner of the deliverable upon delivery and is responsible for its maintenance and support unless they have signed an additional support or TMA contract.
  • A transfer of skills must be carried out upon delivery of the service deliverable to the customer.

The “Accessory” / “Accelerator”

  • This is a non-versioned product deliverable (single version) that allows the customer to speed up their implementation project, or to reuse a “product-related” component already used by other customers.
  • Compatibility with one or more versions of the product: compatibility specified in the “accelerator” documentation.
  • Not delivered with the product. To be deployed in an environment with a compatible version of the product concerned.
  • Each version is unique and considered a new accessory. Any update requires a new version and must be requested from the “accelerator” publisher.