This article is intended for any Carto-SI user who wishes to know the best practices in the representation of his IS through Carto-SI
Are there application naming conventions?
For example, prefix with APP-bbb
Applications must be named in the same way as they are commonly named by IS actors.
It is important that the operational staff who use Carto-SI find their elements easily.
For the notion of API of an application how can we represent it? just like Legacy Web Services?
If the API or the Web Services in question meet the Carto-SI definition of an Application (i.e. an element which is deployed on its own and which renders a service to at least two other Applications of the IS or to at least one user), then this API must be represented by an Application type element in Carto-SI.
In our Carto-SI application we have REST APIs; these APIs are integrated into our software and cannot be modified without redeploying all of Carto-SI.
These APIs must not be represented at the risk of having a mapping of our IS with too small a granularity.
A client wishes to represent an ERP with a module that offers an invoice editing Web Service.
In this case, this module (which we will call Webservice EDITION) can be deployed and modified without affecting the ERP application.
We can therefore represent them as follows:
I’m starting to work on the Application Objects, which work well, and whose operation I understand on the dependencies, and therefore the objects exchanged.
However, I do not see how to model the master Data in the reference applications?
Carto-SI is an operational mapping tool.
Carto-SI therefore aims to meet the needs of IS players (business, dev’, infra) without carrying out modeling.
We therefore wish to respond to the problem of data monitoring in an equally operational way.
Our vision and our needs are therefore different; in this new paradigm of “operational mapping”, we want to follow the way in which the data circulates.
Our data management is as follows:
Once these tasks have been completed, you will be able to meet the following needs:
Finally, the concept of Master Data is part of a modeling framework which, just like the realization of the MCD, BPMN or TOGAF can rely on information from Carto-SI to be carried out elsewhere in tools accessible by experts. in their respective fields.
We are testing Carto-Si we are trying to find out the best practice to represent an existing ALPHA application on two environments (1 VM PROD BDD / 1 VM PREPROD BDD / 1 VM PROD TOMCAT / 1 VM PREPROD TOMCAT / 1 PREPROD database / 1 DB PROD)
Good practice is to represent an ALPHA application. This unique Application will have dependencies with the various technical components mentioned above.
Once a year I would like the application managers to be able to recertify the names of the software as well as the activities/business tasks related to their service (add/modify/delete dependencies)
After inviting each application manager in Carto-SI and associating it with the applications it manages, you can use the “Send a reminder email” feature (Administration -> Configuration page) to invite, at the desired frequency, the makers of each application to update the information.