|
Maurizio,
I have written an ALL-IN-1 application which is an interface to CMS,
we use it to develop ALL-IN-1.
It is a SCM+ application but is not as such integrated with it, but I
guess it would be easy to integrate it.
What kind of capabilities do you want?
The application can replace,replace,unreserve,fetch and delete.
It wouldn't be difficult to add show hist for example.
You could use the application for the CMS stuff then use SCM+ to
develop it. Afterwards using the application to replace again.
Are the VMS applications for ALL-IN-1?
What is their development process, have they got one yet?
Let me know what they're trying to do and I'll see how we can help
Ta,
Mike
|
| Or just come on down the road to Turin and visit the Office IST there
(CM+ development team), and we'll outline our thoughts on how a truly
integrated CM+/CMS application could be built. If your customer is
willing to pay for this, we are willing to develop the application.
Tony
|
| Hi,
thanks for your answers.
What we are doing is to define guidelines and prototypes of develpment
environments for this customer.
Then, the customer will put in place those environments, based on our design.
One on the most important functionalities that should be implemented is the
versioning of elements and application (configuration management).
The current status is that they have not in place a methodology to develop
application nor adequate environments.
They have ALL-IN-1 applications and they will write new ALL-IN-1 application.
---------
CMS is seens as the tools that can handle versioning and will be adopted for
non ALL-IN-1 development.
CM will be the ALL-IN-1 development environment.
We have just presented it to customer, and they like it.
However they raised the question about versioning.
Since CM doesn't provide per se versioning capabilities some kind of
integration with CMS would help.
There sould be 2 kind of integration :
o Loose coupling
CMS is used just to keep track of the events.
e.g. When a module is moved from development to live area,
a copy is loaded in CMS with comments.
It will be possible later on to in CMS look at the
elemnt history and differences.
(something like Mike application)
o Tighth coupling
CMS is used as the source library manager within CM
When a progammer needs to modify a muodule, from a CM
menu he can 'Reserve' the module from CMS, work on it
test it, and then 'Replace' a new version in CMS.
What are you comments about that ? Does it make sense ?
Is the Loose Coupling solution a good input for future versions of CM ?
Tony, at the moment I have no idea if the customer will be willing to pay
for a customization; in general they wants to use standard products.
I'll keep you informed for any furhter development of this work,
regards, �onfi
|
| It makes sense to use CMS for version controls. What you are looking
for is easy enough to do, it's the level of integration which will
determine the added cost and/or complexity.
For example, it would be easy enough to modify the scripts which move
an element into the live area so that they automatically update CMS at
the same time. The complexity arise when you decide:
o To support multi-node activity
o To support multiple CMS libraries
o To integrate CMS with ALL-IN-1 rather than calling CMS from DCL
Clearly calling CMS from DCL (from ALL-IN-1) to deal with a single CMS
library on a single node with little regard for multiple concurrent
accesses to the CMS library would be very simple indeed. However, this
approach may not be practical, especially in a very heavily used
development environment.
We (the CM team) would like to have a closer integration with CMS. But
we need to get some money to do the work. Let us know if the customer
would like to take this discussion any further.
Tony
|