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 - Pat Yearick

Pages: [1]
General Board / Re: Tie database field to text in requirement
« on: September 18, 2018, 10:15:37 pm »
My brain isn't up to getting the full story. But from the stomach it feels like you can just add a note. Attach one to the table and use Advanced/Link Element Feature from the context of the Note link. Then choose Attributes from the list and select one. The note from that will be filled in the Note element.


Thank you! This works perfectly!

General Board / Tie database field to text in requirement
« on: September 14, 2018, 05:58:19 am »

I am importing a table from a SQL database. It has a large number of fields, some have similar names and I'd like to show the user the particular field in the database model table. I'd prefer that the pointer to the field ends up as a hyperlink and updates automatically or if I just didn't need to type and maintain all them by hand.

Req: 002 The periodic report will include the following data elements:

Client name <<column>> Profit Center Name
PC Organization Value <<column>> Profit Center
PC Organization Name <<column>> Legal Entity
Location code (L-Code) <<column>> LCode

Does anyone know of a way to do that?



You are correct. I was just using the normal document template. I found a template for the specifications manager and now I get the requirements In my document.

 I'm sure I don't understand this properly, but this makes me think that requirements entered in the specifications manager are not the same as requirements in other sections of EA. Is that correct?  I was actually thinking that using this specifications manager was just another method to enter requirements to the same data structures.

Thanks again,


I'm sure my requirements are somewhere but ...

1. I made a new Requirements Model
2. I opened the Business Logic diagram and added a few requirements graphically
3. I came back later and used the Specification Manager (ctrl-shift-X) to add some more
4. When I document the package or go to the Business Logic diagram - only the graphically added ones are there
5. When I try to drag or copy the object it's not the same (it doesn't look the same) as the ones already in the Business Logic diagram - which makes me think that is not the right way to get them all on the same diagram.
6. All of my requirements under Business Rules are there in the Model tree diagram and they are all the "same": <<Functional>> Req001 .. Req021 all with the same selected attributes just different titles

Thanks for any suggestions!!


General Board / Link DFD data store to SQL Server Table
« on: October 21, 2016, 10:38:37 am »
Hi all,

I want to link a DFD datastore to a table that I imported via Package->Database Engineering-> Import DB schema from ODBC. When I right click the datastore and select New Child Diagram -> Select Composite Diagram that I saw suggested in a post by Sparx, I am able to link all the tables I imported but I can't pick a specific table. I was hoping to tie each table to a data store.

Is there a way to do what I want?



General Board / Re: Document Excel Workbook in Specification Manag
« on: November 14, 2015, 02:30:16 am »
Thanks for your reply. That makes more sense than what I had in mind.

General Board / Document Excel Workbook in Specification Manager
« on: November 13, 2015, 08:46:11 am »
I'm tasked to document the formulas and functionality of an Excel workbook so we can enhance it and tie it in with models and data brought in from other systems. The application is going to be completely rewritten and extended but I need to capture cell by cell and sheet by sheet what the current workbook does if you enter this or enter that.

I am thinking that it ends up being a large number of user stories but that seems a little too wordy for this. I wanted to ask first if there was a better, more automatic or standardized way. Of course, I'd like to then use EA to track these requirements and later be used to develop the solution.

The workbook has VBA macros but they are very simple. The cell formulas ... can go on forever in some cases.

Thank-you for any suggestions,


Pages: [1]