Our Mission: Enable businesses to customize their products and services for far more clients, more accurately, and at lower cost.

   
Products / Product Line Studio / Extensibility
 
Quick Links
Guided Tour
Online Demo
Technology
Product Line Studio
Software Product Lines
Process Scalability
Terminology
Reference Material
Search
Contact
  EXTENSIBILITY  
 

The Product Line Studio suite is both a set of "tools" and a "toolkit".  That is, while you can use it as a standalone tool, many of our customers benefit from having their tools integrated together in a fashion optimized for their specific needs.  In support of these customers, PLS supports extension through the following mechanisms:

Customization through Configuration

PLS is designed out of the box to be adaptable with no programming.  Following are the kinds of configuration options that are built-in with no programming.

  • Workflow - use Asset Types named and configured for your workflow.
  • Change Policy - configure the conditions under which various types of changes are permitted.
  • Approval Policy - configure what approvals are required on various asset types.
  • Change Notification - configure how email-based notification of changes occurs.
  • Document Formats - configure the format of generated documents.
  • Validation Rules - configure whether and how the built-in validation rules are to be applied.
  • Integrate with LDAP user database - no need for users to maintain yet another password.

Customization through Programming

PLS also allows the customer to extend and modify behavior using the Java programming language. Following are the most common Java extensibility points:

  • Create custom "Services" - a Service is a server-side executable which can perform any task you desire.  Services can traverse the entire asset object graph.
  • Create custom "Transformation Engines" - a Transformation Engine is simply a special type of Service, so you can create your own Transformation Engines.
  • Create custom "Editor Types" - create a Java-based editor type for custom assets.  This is most commonly used for database-oriented assets.
  • Integrate to a custom user database - If you already have a user / password database, you have no need to administer another.
  • Create a custom Storage Provider service - Allows PLS to access and optionally manage Assets stored in a proprietary or 3rd party database.
  • Create custom "Plugins" - Make your own GUI components accessible from the PLS user interface.
  • Create custom Validation Rules for built-in Asset Types or custom Asset Types that you have created.
  • Create custom Change Policy and / or Approval Policy.
  • Many others.