Version Control Distribution System (VCDS)

Requirement

1.     Track NETeXPERT Attributes in VCDS:

o      Use Case Scenario: The rule writer should have the ability to take the attributes from one NETeXPERT system, check-in the attributes into version control, and deploy them to other systems through VCDS.

2.     Track NETeXPERT Managed Objects (MO) in VCDS:

o      Use Case Scenario: The rule writer would like the ability to select MO(s) from one NETeXPERT system, check-in MO(s) instance(s) into version control, and deploy the object(s) to other systems through VCDS.

o      Assumption: Not all MO’s need to be tracked initially due to the volume of objects. For example some customers have millions of managed objects. The approach may first allow users to select Manager Objects and/or Control/Policy objects as a start.

3.     Support for Multiple System Deploy:

o      Use Case: The user should be able to deploy object types to multiple systems at a time.

4.     Support for Object Modification:

o      Use Case: While checking the object into VCDS the user should have the ability to modify the events, methods, dialogs, and any object through VCDS without having to use a NETeXPERT rule, dialog, or managed object editor. This saves time for the rule writer.

o      Note: Implementation of this feature will require close coordination with the NETeXPERT business unit in Agilent as rule validation libraries will be required. This may warrant a complete Integrated Development Environment which replaces Editors and VCDS.

5.     Relate Dependent events or methods at deployment.

o      Use Case: The user would like the VCDS application to have the ability when deploying an object that all related objects are also related and tagged or grouped for deployment. For example when deploying an event all related attributes, methods, and dialogs would be related to that event.

o      Another related use case would be allowing a user to select a Rule Method and to implement a “Where Used” to find what event it is called from. Then after it finds where it’s used one could have the ability to add the matches to the package or “Tag” the related objects.

6.     Package by NETeXPERT Manager Class:

o      Packaging object types related to a Manager classes

o      Object Types would include: Events, Methods, and Dialogs

o      Required: Alert Definitions, Attributes,

o      Use Case: User should be able to package up basically a whole rule set (Vendor Specific Adapter).  So if they added a new data source and created a rule set for it, they would want to be able to package the whole thing up and deploy it out to production.

7.     Package a Patch

o      Package object types from different classes into a “patch” to be deployed to facilitate deployment to multiple systems at one time.

8.     Tagging

o      The user would like the tagging feature of CVS surfaced to VCDS users.

o      Tagging is just another label of the user’s choice. This is a CVS concept – if I have a file filename.txt, I could tag versions with filename.txt.tagA, filename.txt.tagB, etc.

9.     Locking and/or tagging object type when checked out.

o      Locking object type when it has been checked out of the repository or have an indicator in the client which indicates that this object has been checked out. CVS does not have a locking feature but does have a tag command. Users can still make changes via NETeXPERT development editors to the their databases. It may be best to provide the user the ability to tag the object that is being worked on with the user who last worked on that object. (T-Mobile)

10.   Support for any type of file

o      Support in deploying any type of file in the OS such as scripts from $OSI_HOME/Custom or any specified directory. 

11.  Authorizations

o      Securing VCDS features through ID and password