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.
And as you get lower, you can see the toll booths and the gas stations. You can see the city, but as you come down lower, you see the cars start running on the freeways. You can get the bird's eye view or you can get the pie in the sky. MagicDraw will scale that way, but someone has to be able to set it up to give you that granularity.
If you want a model of the bathroom you've got to be able to set it up. When you're on the ground you'll be going to a bathroom, for example. But then as you come down you come into more details. Imagine you're flying a plane and you come over a city and see the view from 10,000 feet. I can create different pieces because you don't want to have hundreds of sheets of the same model. You have the team server which allows a lot of people to use the product for a specific path. It would be good if we could import those into MagicDraw as components so you don't have to manually do these things.
No magicdraw verification#
For those requirements you allocate them to a component in the architecture and a verification method for that requirement. A lot of folks use DOORS to create a requirement. They could make it very easy to do that because there are a lot requirements management tools like DOORS, D-O-O-R-S, Dynamic Object Oriented Management. It depends on who your customer is and what they want.įor the next releases, I would like to have them import requirements from other sources. So it has the DoDAAC too, because the government likes certain things. When working for the government, they require that you do your architecture using the DoDAAC. System Ellis is the base for everything, but you've got other pieces for the government first. They use what they call a UPDM, that's a DoDAAC standard. You have the system engineering piece, and then you have the DoDAAC, which is the DOD architecture.
No magicdraw manuals#
They have a lot of manuals that you can go through for each plug-in they have. You have to know what your relationships are and MagicDraw allows you to do that really well.īut they do provide manuals. You can say this component influences another component or another component enables integration, etc. You take a picture, an ER diagram, Entity Relationship diagram, which is a diagram that shows all the components and how they relate to each other, not just an arrow. You have to do the correct keystrokes to portray what it is you're really trying to do. So some people can pick it up, but it's a steep learning curve. Then you need to understand the relationships between the processes and activities. For MagicDraw there is a steep learning curve if you don't have the system engineering domain experience because a lot of folks go in there and say, "Okay, I'm going to do model-based system engineering." MagicDraw has a model-based system engineering tool but it only allows you to draw the diagram or the model.
No magicdraw full#
INCOSE is what most people use today for system engineering, for building systems, and deploying and maintaining them in a full life cycle. The steep learning curve applies to two things - system engineering and INCOSE. INCOSE, I-N-C-O-S-E international systems engineering. I wouldn't say anything negative about No Magic MagicDraw.
0 kommentar(er)
