Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Sunshine

Pages: 1 ... 32 33 [34]
I had a similar problem, it turned out that I'd mistyped the stereotype name in the toolbox so perhaps just double check there is no typos.
Hang in there sounds like you've nearly cracked it. :)

Think you'll find you have some degree of customisation of the information as well as the style. I concur its not as flexible as one would like. There are some tags such as #NAME# and #TYPE# that can be added/removed.
See the following url for more info on the tags that you can use;

I'm afraid that's the degree of customization available with EA at present.

If you want more flexibility then the other alternative is to consider creating your own HTML generator using the automation interface. If you don't have MS visual studio then you can download one of the express editions from Microsoft. Its not hard just a little more time consuming than one would like.

Yes you can customize the HTML using the web style template.
See the following URL;

I create the class model then use the DDL transformation to create the database model. I then create the DDL script and run it on the database to create the schema. I had to modify the default script to add our own custom stuff and it worked fine. The scripting takes a bit of learning but is worth the effort. The one thing that I didn't manage to do was sort out the transformation of relationships with an association class. I had to do a cludge to my class model and replace those types of relationships with simple join classes.  

Once the database has been created I use iron speed to create the rest of the application Its a same that kind of functionality isn't built into Enterprise Architect.

You can see more on the following link about Model Driven Architecture (MDA)

Hope that helps

I've used ArchiMate notation to do some enterprise architecture modelling for around 6 months now so have gained some experience with it. I've read the book 'Enterprise architecture at work" by Marc Lankhorst et al and all the white papers published on along with the ArchiMate standard v1.0 published by the Open Group. I like the simplified metamodel but it does have gaps. I think some of the views that help link the business layer to the application layer and ultimately the technology layer are great. However, I have to concur I do feel BPMN and UML with stereotypes can cover everything that ArchiMate can do.
Also I've found when passing my ArchiMate models on to my colleagues further down the food chain they have to change them to another modelling language. For instance the Business Analysts transpose the ArchiMate models into BPMN to do their swimlane workflows as they add the next level of detail. The solution architects translate the ArchiMate models into UML to add further design detail. So in conclusion there  seems to be more effort involved when using ArchiMate as it does not provide a base from which to add more detail.  

I've also found amongst the various documents published on ArchiMate there are a few inconsistencies which don't really help when trying to learn it.

Finally one thing that might well sink the ArchiMate ship is that the Open Group license states that whilst its free to use for internal purposes there is a charge to organisations who wish to use it for commercial purposes.  Where UML and BPMN are free to use and so in the current financial climate these are likely to be favored over ArchiMate.

I think to sum up I'll be looking at doing my next Enterprise Architect assignment using BPMN and UML to save my colleagues some grief.

Well that's my 2 cents worth.  [smiley=wink.gif]

Pages: 1 ... 32 33 [34]