We use it to build the physical/logical domains to hold requirements, specifications, use cases, and all the way down to class definitions.

We're using version 19 or 20. I have a version of MagicDraw installed on my local PC, but all of our models are centrally located.

I use CAE software to support my consulting practice.  I'm an independent consultant and I use it with my clients primarily for business transformation projects - define, assess and re-design business architecture to either prepare for ERP projects or to improve existing business practices. When I use the term business architecture, I'm primarily talking about looking at corporate strategy, business organizational structure, business process designs, and IT & Software architecture.  

We are using it to implement a modern approach in our company's engineering processes. We function as a working group, employing it for a pilot project to establish a model-based engineering process within our company.

I used Magic MagicDraw for structured refrigeration systems.

Our primary use for this solution is enterprise modeling, providing integration between program management and systems engineering.  For several years now, I have focused on building a model for continuous improvement that integrates strategy planning, project management, analytics, process design, and change management that I can implement for clients. Magic Draw provides, I would say, an eighty-percent solution for this capability. More so than any other product that I've evaluated.

We use No Magic MagicDraw for modeling systems.

We use it for model based system engineering (MDSE).

I use No Magic MagicDraw, but Cameo is the system engineering tool. I'm a system engineer, and I use No Magic MagicDraw for system architecture, requirement management, system simulation, and threat studies.

We use a framework related to system engineering called MagicGrid.

Model-driven documentation including project architecture management, system architecture modeling, reverse engineering of salesforce data model, and providing method & tooling for whole project for modeling all other concepts plus output management to Sharepoint, Confluence, HP ALM

It's now called Cameo Enterprise Architect 19. It is my system engineering tool.

I do systems engineering. If you go to my website, www.simtrs.com, there are simulation and training for this solution. You will see the benefits of MagicDraw and how I use it.

I use it for systems engineering and life cycle systems engineering, and even for deployment. The beauty of MagicDraw is that it has a simulation part, so you can simulate your model to validate it. The simulation allows you to bring in code off of an external code that you can write to set up the simulation and execute the code.

We use MagicDraw for model-based systems engineering. It differs from standard systems engineering applications by using models, as opposed to words or sheets. We define our system or subsystems via models and interfaces and then define the relationships between them.

It is used mostly during the design phase of all of our projects. After the production and testing phases, it is no longer used.

The primary use case of this solution is for modeling and collaboration.

I use it for model-based system engineering. We are customers of No Magic and I'm the principal system engineer.

I am using MagicDraw as part of my research project.

Used for Business and Systems Engineering modeling. Its role is to support a defense program that consists of multiple product lines.

We use MagicDraw for software design from scratch. We redesigned an electric signature in the last year. It is a good tool. It's a little better than Enterprise Architect. But we cannot delegate the final processes to the user client. I need to export the results to Confluence where the client can check it.