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 - Robert Sheridan

Pages: 1 2 3 [4] 5 6 7
General Board / Re: Copy and Pasting Requirements
« on: September 28, 2012, 09:49:47 pm »
You can also do the export via the API, Geerts spreadsheet in the community site gives a good starting point for using the API.

General Board / Re: Copy and Pasting Requirements
« on: September 25, 2012, 02:28:56 am »
You could try exporting them to Excel, doing the changes you want to make including removing the number and then reimporting them via the API.

General Board / Re: Numbering in reports
« on: September 25, 2012, 02:31:16 am »
I identified a but relating to this a while back (followed all the steps and the numbering still was not sequential) which Sparx accepted, do not know where it is on the Sparx fix list though.

General Board / Re: Add New Tagged Value to the Attribute
« on: September 14, 2012, 02:52:07 am »
There were some earlier posts around this.  Can not remember what the gotcha was off hand but I think the tagged value for an attribute is in a different bit of the object hierarchy (and with a different name) to element tagged values. If you check the help it tells you.

General Board / Re: Unique Requirement IDs
« on: September 19, 2012, 03:34:50 am »
I like to have requirements numbered as then they are uniquely identfied even if you change the name to make it clearer.  I actually prefer the EA autonumbering as I dislike structured numbering and relying on analysts to correctly create a unique number manually results in duplicates.

On one programme we decided that we wanted to use structured requirement numbering to show the project that the requirement was gathered under and acheived that by doing the requirement gathering in a seperate project file using the autonumbering with a suitable prefix and suffix and imported the finalised requirements into the master repository.

General Board / Re: Non visible Packages
« on: September 11, 2012, 08:56:21 pm »
You could export from your master to the other repositories and lock the packages from the master that you do not want the users of the other repositories to use.  This would enable them to reference the elements but not change them.  You would them do the reverse, import from the sub repostories into the master to maintain the master.  All very time consuming  but do able.

If you make the packages invisible then you run the risk of people replicating the functionality or missing dependencies etc.

General Board / Re: Link to artifact that is within another EAP
« on: August 15, 2012, 12:13:21 am »
Have you looked at replication?  Not straight forward but an option.  The only other way I have considered solving a similar problem a few years ago was by import and export of XMI, but it is very labour intensive and would probably only work if you had accounts in each departmetn EAP which you used to lock out the departmental users from the master model.

General Board / Re: Microsoft Word 2007 Import...
« on: July 27, 2012, 11:13:32 pm »
If the requirements are in a table then you can dump it into Excel (whihc handles tables automatically) and then use the automation interface to upload them.

Geert put a starter for the upload spreadsheet in the community forum, you may need to edit it depending on what you want to upload (I modified it to support creating packages and different sorts of tags)

You will also have to clean up the spreadsheet before uploading, for example ensuring that there is no missing data and correcting the layout where an extra row has been created because of a CR in the text.

General Board / Re: ReUse of projects while keeping traceability
« on: July 25, 2012, 12:28:00 am »
I agree with the above: whatever you do do not reuse by copying as if you do you will lose the ability to determine the impact of a change to an element that has been reused.

It also depends on how reuse is going to be implemented: will updates to a reused element be expected to be implemented in all systems that use it?  If you work through your method it may become easier to decide what to do.

A possible workaround is to baseline or do an XMI export when a element that is reused is changed so that you have the previous version stored.  You could also use a tag or a note in models that reuse elements to record which version of an element has been used.

General Board / Re: Profile Stereotype not working
« on: July 25, 2012, 12:40:30 am »
Thanks for that tip, I will bear it in mind.  I am hoping to get time to do my first MDG soon.

General Board / Re: Profile Stereotype not working
« on: July 11, 2012, 01:46:18 am »
Thanks, I guess an just old fashioned.  I will see if that fixes the problem.

Looked at MDG and realised that I would need to do some more work (especially as the only shared space I have is Sharepoint) so I tried reloading the profile and that seems to fix it.

General Board / Profile Stereotype not working
« on: July 10, 2012, 11:31:58 pm »
We are using a profile for modelling.  The profile appears in the resources browser and in the toolbox but you can no longer use it: drag and drop does not work, it does not appear in the element properties stereotypes list and if I manually type in a stereotype name for a new element it is ignored.  Has anyone else experienced this?

I have looked but can not find an option to enable/disable profiles.

I am on the latest version of EA.

General Board / Re: How to only include specific models into RTF r
« on: July 02, 2012, 09:22:17 pm »
You can filter on tagged values in reports.  If you open the 'Add filters' dialogue you can select Tag Value, attribute Tg Value, Method Tag value or method parameter tag value from the 'Search On' drop down

General Board / Re: How to only include specific models into RTF r
« on: June 29, 2012, 11:20:54 pm »
Not sure exactly what you are looking at, I use the term model to refer to something under a root node whilst you seem to be using it to refer to either a specific type of element or a view; however, assuming you are talking about restricting the elements included in generating documentation if you look at the Generate Documentation window you will see a tab called options which allows you to filter on element types (e.g. class or actor) and the there are other tabs which allow you to build custom filters.

General Board / Re: Enterprise Architect for SharePoint
« on: June 27, 2012, 06:40:04 pm »
It is pretty straight forward to write an extract from EA to a spreadsheet using VBA once you get to grips with the automation interface.  Geert made a template available on the community site for importing requirements which I used as the basis for exporting from EA to a spreadsheet.  Once you have the data in the spreadsheet you can then put it into Sharepoint.  I presume VBA to extract to Word would be much the same.

Pages: 1 2 3 [4] 5 6 7