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 ... 24 25 [26] 27 28 ... 49
Suggestions and Requests / Re: Merge components
« on: November 07, 2014, 07:34:25 am »
Yes. Though I think it's quite tricky to make it user friendly. Especially replacing occurrences of the replaced element (be it in diagrams or as classifier) is challenging.

Tricky maybe but not impossible. I've seen it implemented on another tool  ;)

Suggestions and Requests / Merge components
« on: October 31, 2014, 01:34:01 pm »
One of the common problem when modelling with a team of many people is that two people sometimes create the same object. It would be a really great feature to be able to merge objects. Something like dragging an object with the ctrl or shft key pressed in the project browser and dropping it onto the another of the same type. A dialog would pop up saying do you want to merge with options of overwrite target or source (for properties and tag values). Sparx EA would then merge the two objects into one, replacing the instances in diagrams and combining relationships with other objects.
This would facilitate rationalisation of objects when working large teams.

Suggestions and Requests / Re: show notes on archimate objects
« on: April 22, 2014, 12:20:04 pm »
Unfortunately the archimate MDG doesn't support that feature. Two options you can consider;
a) Add a note and link it to your archimate shape. Right click on the link and choose "link this note to feature" and choose the notes field. The notes will then be displayed in the newly added note. If you want to hide them and show them the consider using the diagram filters and filter on say phase field by deleting the 1.0 default value in the notes and filter on phase = 1.0.
b) Create your own ArchiMate MDG and add the feature in the scripts for the shapes. This will be a whole lot of work probably more than you are prepared to do.

BTW this is probably the wrong place this post. Should have placed it under the general discussion

Hope that helps

Spreading a little Sunshine to those dark areas of EA.

Suggestions and Requests / Re: EA 11 wishlist
« on: March 27, 2013, 08:17:45 am »
Upgrade of image library would be good. More avatar's and technology items would be cool.
Also the ability to use images on Archimate entities in diagrams. Seems like anything with a shapescript disables using images. I find the IT folk are okay with Archimate but the business folk and CxO's need images. The Archimate folk do talk about representing Archimate with alternative images for different audiences in one of their many papers after all.

Suggestions and Requests / Re: Linked document icon in Project Browser
« on: November 02, 2012, 10:43:02 am »
Good idea - gets my vote.

Suggestions and Requests / Re: Include JPG image on diagram?
« on: April 28, 2011, 06:35:17 am »
Think the only problem with the cut and paste technique is that if you want to use the same image in another diagram the image name isn't very useful when you look at the image manager dialog list. i.e. "image10812" isn't too helpful. You can't change the name of the image either unless you open up the database and change it via a database tool.
Thus that was the reason I was suggesting importing the images first. When you have a large model with a large number of images its important to be able to find that image again rather than trawling through the list one by one. Even worst doing another cut and paste of the same image creating duplicates.
Well there my 2 cents worth  8-)

Suggestions and Requests / Re: Include JPG image on diagram?
« on: April 13, 2011, 08:08:10 am »
Yes there is a way  ;D

First of all you need to add all your JPG screen shots into EA. You can do this via settings>images menu.
Click on the Add New... button and add a JPG image. Repeat until all added making sure your images have understandable names.

Second create a diagram and drag a boundary object on to it.
Right click on the boundary object in the diagram and select appearance>select alternative image. Choose the screen shot you want and click ok. Whala one screen shot. Create new diagrams and repeat for all screen shots.

You can then reference these diagrams via hyperlinks on your business process diagrams or use case diagrams.

Hope that helps  :)

Suggestions and Requests / Re: Archimate 2.0
« on: February 23, 2012, 07:07:37 am »
Me too  ;D

Suggestions and Requests / Re: Web interface into repository
« on: October 28, 2011, 09:49:29 am »
The basic problem with the web report is that it creates pictures of diagrams. Whereas the web client would allow a user to double-click an element and read its notes and look at its properties and know that it is the latest (current) version.
mmh? the last time I generated an HTML report I'm pretty sure I could navigate to the notes of an element by clicking on the element in a diagram. Granted its a snapshot of the model at that time but you could keep it up to date by generating the HTML report on a regular basis. i.e. daily is probably good enough.

Suggestions and Requests / Re: Web interface into repository
« on: October 13, 2011, 08:24:35 am »
Sounds like you want to provide some kind of limited editing capability via the web browser rather than a simply publish the model on the intranet. Presumably this is to have a wider participation by the organisation. At present there isn't really any way to do this unless your prepared to develop it your self.
You might be able to customizes the HTML generated report with some java/.net forms that access the database. If your not a developer you'll probably need to hire one. Perhaps create a batch process that publishes the model everynight with some java/.net forms that update the database. Suggest if you do go along that path you implement version control too so you can undo any changes should they not be desirable.
I publish using the HTML report generator and get people to provide feedback using the feedback mechanism described on the community site. I've added this to element descriptions too. The advantage is I can control what goes into the model. The disadvantage is can get a lot of emails.

So it sounds like a good suggestion. I guess what Sparxs have to consider is it worth going down that path as its a new architecture. For instance a n-tiered web as opposed to a rich client server. It all costs money to do and support.

Suggestions and Requests / Re: EA Start as it was left
« on: June 30, 2011, 08:41:52 am »
To add 1% more try using menu Diagram>make user default just before you close down EA. That way next time you open up EA it will open up the diagram you were last editing.
Hope that helps a little :)

Suggestions and Requests / Re: Update BPMN 1.1
« on: May 05, 2011, 01:06:35 pm »
mmh? Just to make it clear all the hard work is in getting others to use and understand your method/notation as well as maintaining it. Its not in the creating of the method/notation itself.

Suggestions and Requests / Re: Update BPMN 1.1
« on: April 29, 2011, 08:04:18 am »
Okay so you it sound like you want to take the BPMN V1.1 MDG technology and extend it with your own stereotypes.
You can probably achieve this by creating a new model and importing the BPMN Technology File into resources.  The BPMN Technology file can be found in C:\Program Files\Sparx Systems\EA\MDGTechnologies.

Reproduce all the BMPN stereo types and copy the shape scripts into your stereo types so you get the same shapes.
Reproduce the BMPN toolbox
Add you own stuff to the stereotypes and toolbox
Create your own MDG file and copy it to C:\Program Files\Sparx Systems\EA\MDGTechnologies

More info on creating MDG Technology to extend UML can be found here
and in the online help.

Hope that helps :) But be warned that creating your own notation is frought with lots of extra work.
Does BPMN V2.0 not have what you want? Its now in V9.0  8-)

Suggestions and Requests / Re: Parametric RTF report generation
« on: April 29, 2011, 07:48:55 am »
Sorry still think it adds too much complexity for most users to add extra parameters. The simpler thing to do is create the most complex template first then copy it and cut out the attributes/elements you don't need for the simpler template.

As a passing thought if you want to exclude connectors you can do this via the Options tab (on the generate rtf documentation dialog) and select all of the connector types to exclude.

Your derived requirements may be able to be filtered out via the element filters or other filters in the same dialog. Perhaps use one of the existing fields such as key words putting "derived" in the requirements you want to filter out.

So you might be able to achieve your desired result using existing features.  I guess it really depends on how you format your template as to whether you can pull it off :)

Have a play around and let us know how you get on.

Suggestions and Requests / Re: Parametric RTF report generation
« on: April 28, 2011, 06:18:47 am »
Sounds like you want to generate a totally different document so a different template is the logical way to go. In the past I've used search name value tags on model docs and excluded element types via the doc generation dialog and its just caused my colleagues headaches as they didn't understand the intricacies of the those features. If you add parameters to include/exclude sections I think it will make doc generation too complex for most people. It is already too complex for some now. So I'd say its not a good idea from an ease of use point of view.

Sorry to its probably not the answer you were hoping for  [smiley=sad.gif]

Pages: 1 ... 24 25 [26] 27 28 ... 49