Author Topic: How test new pluggin/MDG without critical problems (Read 10515 times)

steen.jensen · « **on:** February 07, 2018, 09:15:51 pm »

Hi all EA users.

I was testing the BABOK MDG/Pluggin from Sparx on my daily client/PC.
Normally Im connected to our repository, so this time also.
Then other EA-users couldn't connect to the Repository, They got error msg: " Required MDG BABOK is not available"
I got "Panic" .... WtF.. I have just installed BABOK, not started modeling ...
A day later I got answer from Sparx how to check the Models in repository for BABOK MDG requirement. So there I could remove it.
We lost 1 day of work for 10-15 users when they was not able to use the repository.

My question is how do you test new MDG, funktiones etc in real life??
- An other Sparx EA client-PC just for test?
- An other Test repository?
- Other test stuff?

Arshad · « **Reply #1 on:** February 07, 2018, 09:30:48 pm »

Hi Steen

Thinks to Check:

If Mdg was imported in user level it wont be available for another users.
Please check whether MDG is enabled

HTH
Arshad

Geert Bellekens · « **Reply #2 on:** February 07, 2018, 09:56:16 pm »

I always test my MDG, script, RTF templates, etc... in a separate TEST environment (repository) to make sure I don't break anything in the production environment.

I'm guessing you had configured the required MDG's in the production repository?

Geert

steen.jensen · « **Reply #3 on:** February 07, 2018, 11:55:35 pm »

Hi.
Nope I just installed the BABOK MDG in my client. Then I did some other work in the model in Repository with builtin Archimate 3.x
I did not start any BABOK modeling

But I have learned that I need a Real test environment and process as I requires from other part of the organisation

Steen

steen.jensen · « **Reply #4 on:** February 07, 2018, 11:59:37 pm »

Hi Arshad.
How do I install a MDG in user mode??
And how do I restrict other user to make my mistake again, ie make repository model have requirement of unnecessary MDG:s

Arshad · « **Reply #5 on:** February 08, 2018, 12:01:39 am »

Quote from: [email protected] on February 07, 2018, 11:59:37 pm

Hi Arshad.
How do I install a MDG in user mode??
And how do I restrict other user to make my mistake again, ie make repository model have requirement of unnecessary MDG:s

In the Import MDG Dialog there will be two options

Import to Model
Import to User

HTH
Arshad

steen.jensen · « **Reply #6 on:** February 08, 2018, 01:07:06 am »

Thanks!
Wonder what BABOK-MDG did? as it was a msi packet with no import instruktions.

I be more careful next time I want to test a new MDG,

Uffe · « **Reply #7 on:** February 08, 2018, 02:11:35 am »

Quote from: Arshad on February 08, 2018, 12:01:39 am

Quote from: [email protected] on February 07, 2018, 11:59:37 pm
How do I install a MDG in user mode??
In the Import MDG Dialog there will be two options
Import to Model
Import to User

My recommendation is always to do neither of these. Importing an MDG Technology to a project means it only works there, not in a side project you might want to create. Importing to a user means it only works for that user, not for other users who might be collaborating on the same project.

Instead, deploy MDG Technologies to a shared folder and instruct all users to add that path to their configuration. If you redistribute the software internally, which larger organizations tend to do, you can set this up in the distribution package.

Quote from: [email protected] on February 07, 2018, 11:59:37 pm

And how do I restrict other user to make my mistake again, ie make repository model have requirement of unnecessary MDG:s

In addition to what the others have said about not testing stuff in a production environment, it's good practice to establish which MDG Technologies SHALL / MAY / SHALL NOT be used in each project. But there's no functionality to enforce such rules.

/Uffe

Geert Bellekens · « **Reply #8 on:** February 08, 2018, 02:47:23 am »

I usually import MDG's in the model.
But I also usually have clients who have a single (or a few) central repositories.
In this type of setup, I find importing the MDG into the model the easiest as I don't have to worry about client configurations.
Users of this model have access to the MDG regardless of their local configuration.

Geert

Eve · « **Reply #9 on:** February 09, 2018, 08:27:48 am »

Unfortunately, I don't think any amount of testing this technology would have prevented this issue. What happened was that a user changed the model configuration to add the requirement for that MDG Technology.

Geert Bellekens · « **Reply #10 on:** February 09, 2018, 03:47:37 pm »

Still, would he have used a TEST or DEV environment then this would not have affected the production users.

Geert

steen.jensen · « **Reply #11 on:** February 10, 2018, 09:46:43 am »

Hi all and thanks for all good suggestions.

I have requested a separate test-db as a copy of prod repository and a a separate test-client (Win-PC) where I can test new EA builds & MDG/plugins and let some selected users be the acceptance-test group before production deployment, prod-repository & prod EA-client

I start with some process modeling in EA and some instructions & routines for me and my colleagues to have a documented solution for this.

Sparx Systems Forum

News: