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 ... 7
16
General Board / Re: sizing a DBMS server
« on: February 25, 2014, 06:11:07 pm »
Thanks guys, just need something to keep the admins happy.

Robert

17
General Board / sizing a DBMS server
« on: February 24, 2014, 10:42:34 pm »
Hi,
We want to get a DBMS server set up, the admins are wanting sizing information and the answer 'do not worry, wont use a huge amount of space' is not good enough. The model will start as just being busines architectue.

The data I have to gleaned to date is the following:
Network latency no greater than 100 m/s
200 Mb RAM should be sufficient for even a large repository

Can anyone give me any figures on the amount of disc space used by their repositories and a guess at whether their repository is small, medium or large.  this will also help us estimate how much disc space might be needed in the future.

Thanks
Robert

18
General Board / Re: Roadmaps, anyone successfully used EA to roadm
« on: July 25, 2012, 12:38:08 am »
I did a roadmap using component diagrams.  You have 2 options: a diagram for each stage (which is what I did as it was a number of years ago) or a single diagram with each element having its phase set and you can use the diagram filters to show how things evolve.

19
General Board / Re: Productivity gains from using a modelling appr
« on: June 28, 2013, 05:40:43 pm »
Rather than re-running a project how about re-running a workshop modelling some requirements using just Visio and Word and then using EA or an equivalent.  

I have had to use Visio and MS Office recently after years using EA and every simple frustration we encountered we would not have encountered using EA, and that did not include having to manually do traceability.

20
General Board / Re: Multiple projects in a single Oracle Repositor
« on: May 01, 2013, 11:08:40 pm »
One way to do it is to have a node which contains the master elements and then separate nodes for each project which are then able to include links to the master elements.  The project nodes would then have a as a top level folder structure your standard approach, for example: Conceptual, Logical and Physical models under which in turn you would have your model views e.g Classes, Business Processes, Requirements, Components

21
General Board / Re: tagged value of type memo?
« on: March 27, 2013, 08:54:54 pm »
I found that using <memo> in the tagged value of the stereotype meant that I did not have to set up a tagged value type via UML types which meant that the profile was portable (important if the users will be creating their own repositories and are not technically savvy).  The downside is that the 'details' of a new element created using the stereotype contains '<memo>' etc. as the default value; the only work around to this I have found is that if you are doing an import via the automation interface you can add a step to check for and delete the default value if the details field should be empty.

22
General Board / Re: tagged value of type memo?
« on: March 22, 2013, 08:29:02 pm »
Way back when I got it to work in a profile by adding <memo> as the stereotype and initial value, I had to put the <> in for it to work; are these no longer needed?

23
General Board / Re: Traceability Window contents in Reports
« on: March 22, 2013, 08:31:37 pm »
Have you tried using the connector sections in the report?

24
General Board / Re: Report Level numbering
« on: March 22, 2013, 08:09:27 pm »
Am I correct in thinking that you want the report generator to create hierarchical numbers for packages where they heading levels? There was a thread on this a while back.  It is a pain to do but once you have done it it does work.

If this is the case then the report templates do support it but to achieve it you have to do (in summary) the following:
1. start from scratch with a clean template
2. load your windows styles in to the template
3. follow the procedure in the manual *exactly* to set up lists and and overrides
4. save this template as a base template and use it to create all your subsequent templates.
5. create a new template from the base template you just created with  headings applied to the relevant sections
6. follow the procedure in the manual *exactly* to set up paragraph list numbering.

The key is the base template as the list overrides you create in it are the basis for everything else.  It is critical that you have the same list override in each template you use in a virtual document as otherwise the numbering will be out of sequence.

25
General Board / Re: Multi value/selection tagged value
« on: March 15, 2013, 06:42:22 am »
I do not have access at the moment to the relevant profiles, but I am pretty sure I created a tagged value with a lookup on another stereotype which allowed multiple selections by using the link mechanism described in the EA help and, I think, setting multiplicity of the end of the link to 0...*.  I set this up to enable us to select which conceptual components a change would have an impact on.

26
General Board / Re: Creating/importing relationships
« on: March 06, 2013, 10:43:56 pm »
I successfully imported a matrix spreadsheet containing a list of functions (grouped under higher level functions) cross referenced to a list of services (grouped by regions) using the automation interface.  I used Geert's spreadsheet from the community forum to get me started.

The automation interface enable me to create package hierarchies to group the the services and functions as well as create elements for the actual services and functions.  I created the services first and then as I created each function I parsed the spreadsheet to see which services it was associated with and created a dependency relationship.

27
General Board / Re: RTF templates...
« on: March 06, 2013, 02:48:30 am »
In the package notes.  I have a model document called Preamble which uses a RTF template that just outputs package names and notes and I drag the packages I create (introduction, scope, etc.) into this model document.

28
General Board / Re: RTF templates...
« on: February 28, 2013, 12:03:49 am »
I do something very similar to this using a virtual document.  I use packages within the virtual document package hierarchy to hold static data for the document, these are then dragged on to a model document element to output them.  The title is generated in the master document template and hence is the root package of the virtual document. The only problem I have run into is getting the table of contents to generate automatically.

29
General Board / Re: Complex Documentation in EA
« on: February 06, 2013, 12:06:05 am »
I am not sure exactly what you are wanting to do.  Are you trying to report on elements that only exist in diagrams in the package scope?  If this is the case then you need to configure the diagrams and the report accordingly.

You can also set up report layouts so that only one end of a connector is output in the report, or you could just output connectors and ignore the element section of the reports.

You can also add filter conditions so that you only output particular types of connectors and elements; however, if you do this you need to consider whether or not you want to output children of filtered out elements (there is an option to control this in the generator).

This approach assumes a diagram centric output.  If you want to find all instances of a particular element and process them together then I suspect the only way to do that would be via some form of query, script or addin or a tool such as eaDocx or getting a list of all the elements and then running for each element the same report filtered for that element and manually collating the output in a document.

30
General Board / Re: Document a package reference
« on: January 25, 2013, 04:14:54 am »
Thanks for the pointer to the diagram flag, had not occurred to me to look for it!

Pages: 1 [2] 3 4 ... 7