In terms of using multiple programs and scaling your models appropriately, the tool is pretty large, and you can go in many different directions. It is not straightforward, and it is not intuitive on how to directly scale things because you can make decisions at a low level that affect multiple paths for scaling that aren't readily available. You don't really understand them until you try to scale.

In terms of its users, our software team and our scientists are using it for a couple of different programs. In terms of maintenance, our team doesn't do the maintenance for it. Our company performs maintenance.

The good thing, in terms of scalability, is that you can have multiple people working on the same model through a teamwork server which enables you share models and you can have multiple people interacting on the same model. 

I do know that multiple federal agencies across DoD -- Army, Navy, and Air Force, as well as NASA are beginning to recognize the potential cost and schedule savings that can be achieved using model based systems engineering tools like No Magic's CAE.  I can foresee a future where your product/service concept begins with a digital model than can be tested, verified, validated, and approved or rejected, before the prototype development begins. 

I would rate the scalability a nine out of ten. It is pretty easy to scale. 

Currently, we hold four licenses, and we're employing about sixty of them. Initially, we procured ten licenses, but we plan to scale up to more users in the near future.

Magic MagicDraw is a scalable solution.

On a scale from one to ten, I would give scalability a ten.

We have approximately 300 people using this solution in my large company.

I rate the scalability of No Magic MagicDraw a seven out of ten.

Letting larger teams work with one model concurrently without organizing partitions will highly increase waiting times due to lock & checking cycles.

The way MagicDraw scales is very good. You have the team server which allows a lot of people to use the product for a specific path. I can create different pieces because you don't want to have hundreds of sheets of the same model. Imagine you're flying a plane and you come over a city and see the view from 10,000 feet. But then as you come down you come into more details. When you're on the ground you'll be going to a bathroom, for example. If you want a model of the bathroom you've got to be able to set it up.

MagicDraw will scale that way, but someone has to be able to set it up to give you that granularity. You can get the bird's eye view or you can get the pie in the sky. It's like you are in an aircraft. You can see the city, but as you come down lower, you see the cars start running on the freeways. And as you get lower, you can see the toll booths and the gas stations. That is how it scales, but you have to have the ingenuity to be able to model it so that you can flip from model to model, which it allows. But it would be nice if I could have hyperlinks in there, where I could take the big model, click and see, just like you see Google Earth.

As you click it further up and down, it gets bigger and smaller and smaller and smaller until you get down to the very house that you live in. It'd be nice if they add hyperlinks or something like that so your customer wouldn't have to be an expert in MagicDraw. Because the way it is now, I have to import it to JPEG's or to files and organize it in such a way that it would take me a lot of time to describe what an architecture is. This is especially true for large systems. For small systems it's not a problem but for large systems it can be. For example, if you want to draw an architectural automobile, you start with the basics. But then when you start drilling down into the engine and the carburetor and all those different things, it can get very hairy. So you've got to be able to organize it in such a way and that capability isn't there. You have to do that manually.

We have six users in the company.

This is a scalable tool. It's very flexible and all of the stereotypes that you can select or add, for example, we call it the 80/20 rule, where 20% of the tool usage gets you to 80% of the capabilities you need. 

The solution is scalable. We have six users in the company. 

I am not able to assess the scalability as we have not attempted to scale beyond the initial installation.