tag:blogger.com,1999:blog-14732452.post7285465569791289264..comments2023-09-27T11:44:52.898-04:00Comments on Business Analysis by David Wright: Memories of IT - 1990 - IEW vs. IEFDavid Wrighthttp://www.blogger.com/profile/05103379078232846587noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-14732452.post-4914611124318742412009-10-30T10:22:38.929-04:002009-10-30T10:22:38.929-04:00Wikipedia, of course...
A special mouse? Perhaps ...Wikipedia, of course...<br /><br />A special mouse? Perhaps in an earlier version? I recall now that TI showed IEF to our development people a few years earlier, but they rejected it because its didn't generate PL/1(!).<br /><br />I can't remember how IEW did Action Diagrams, but they were certainly the heart of IEF, with every 'line' selected from a list of valid options, especially in using the data as defined in the ERD. And it worked, which I will get to in a few posts.David Wrighthttps://www.blogger.com/profile/05103379078232846587noreply@blogger.comtag:blogger.com,1999:blog-14732452.post-65312520312819976802009-10-28T23:21:46.805-04:002009-10-28T23:21:46.805-04:00Great memories.
Fran founded a software company t...Great memories.<br /><br />Fran founded a software company that merged with KW:<br /><br />http://en.wikipedia.org/wiki/Fran_Tarkenton<br /><br />I believe that both IEW and IEF used Event Diagramming, Process Dependency Diagrams and Action Diagrams (which were mostly text).<br /><br />Also, IEF required a special three button optical mouse that used a special metallic grid mouse pad. People still don't believe me when I tell them I used an optical mouse in the 80s.<br /><br />The real power (and pain) for both tools was their extensive use of matrices (like organizational responsibilities and CRUDs) to tie process to data.Karen Lopez https://www.blogger.com/profile/08744312127015606524noreply@blogger.com