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 - only4thefish

Pages: [1]
1
Automation Interface, Add-Ins and Tools / Re: DOORS MDG
« on: February 17, 2017, 07:33:52 am »
Super! Thanks.

2
Definitely of interest...

3
Automation Interface, Add-Ins and Tools / Re: DOORS MDG
« on: February 15, 2017, 08:56:43 am »
Using V12.1... Something I'm not getting trying to read the posts is whether the MDG link connects directly to the DOORS server, or through a local DOORS client.  It seems that I only see reference to connecting to a DOORS "module".  And the instructions for using the MDG don't match with what the menus show: "Extensions | DOORS | Connect External Project", which I select and get a dialog that says,"Please Open DOORS Database".  Yet I remembered the MDG selection leading to a dialog to connect to a database.  I don't get that now. Does using the MDG require a local DOORS client to work?

4
At the risk of sounding stupid, where do I find the EA API, or maybe I should ask what is the EA API?  I've been looking all through the online materials on the website and cannot find any description of API's.

5
Uml Process / Re: Requirements model vs User Stories in scrum tool
« on: September 22, 2016, 04:19:28 am »
Just FYI...
With so many organizations going to user stories and epics, I decided to see if there was anything on user stories vs. use cases.  Ultimately I ended up on Alistair Cockburn's (author of the classic "Writing Effective Use Cases", 2001) website where he had an article discussing it.  I can't access it from here (blocked due to website classification of "none"), but try alistair.cockburn.us and search for it there if you care, or maybe www.usecases.org as an alternative.  Essentially, as I remember it, user stories are really more for scoping and estimating the amount of work required (hence why it goes away with each project), but that use cases ferret out the required functionality, hence functional requirements, of the system.  And those requirements models can obviously remain, if they are created. HTH 

6
Other than that, I'm not sure what you're expecting to get by importing these files. ReqIF is an exchange format. It's intended to work even between non MOF based tools. Importing the XMI won't get you any closer to an import or export of the format.

Well, at the least it allows me to look at the format architecture.  Also, I was curious where it would lead.  Obviously not far. 

7
I've been wondering if there's any real use for the XMI "machine consumable" files from the OMG.  My initial impression was that I could import a set of XMI files and create a profile from them.  Specifically I was attempting to import the ReqIF files, reqif.xmi, reqif.driver.xmi, and reqif.cmof.  While the first two import with out an apparent issue, the .cmof file (also an XMI file) fails to import with EA indicating failure due to errors, but the log file states no errors:

Importing Model from XMI
Root Package:
Resolving Classifiers
Resolving Owners
Resolving Attribute Types
Resolving Parameter Types
Resolving Association-Classes
Resolving Properties for Association Ends
Resolving InteractionOccurences
Fixup external references
Import Complete!

Pages: [1]