It's my understanding that the people that started VMark came from Prime and thus had a Prime Information background. Pete Simmons, one of the principle architects of UniVerse, was a software engineer at Prime Computers. I am sure they came away from Prime with more that a few tricks in their bag. They basically took the Prime Information concept and enhanced it to create UniVerse. They really didn't have the chance or the necessity to start all over and, in your terms, do it right.
I'm not trying to start the hated "which is better" argument, just the statement that starting with a blank sheet of paper, after some years of experience with Pick/PI/PI Open, maybe some Rev and Arev, etc, is more likely to come up with a similar, but quite different product. I would also suggest that if the UniData folks were satisfied with PI/PI Open/UniVerse, they would not have gone to the trouble of creating UniData. I know from my own experience in helping to write the "Prime" Information System, after 5-6 years of experience with Reality, created a product that was significantly different from Reality, but still very similar. Each iteration is a step up, hopefully. In my humble or sometime not so humble opinion. Tom Dodds -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stevenson, Charles Sent: Monday, April 30, 2007 9:48 AM To: [email protected] Subject: RE: [U2] Differences between UV and UD I've always thought that there was a difference of philosophy from Day 1 that underlied the 2 organizations that manifests itself in the software: Vmark/UV: "All things to all men, that I might by all means sell to some." (If you'll allow me to misquote St. Paul.) UniData: "Do it right." They took the opportunity to recreate MV & PI "in their own image." (I'm continuing to bastardize the Bible.) There are pluses & minuses to each approach. I am NOT arguing which is better, just that some differences in the products can be explained in terms of the respective philosophies of the organizations. Examples: 1. Conversions from other MVs: UV: inherently easier. Baskin&Robbins 31 Flavours. UD: supplies conversion tools to help you, since it is more extensive. 2. UV tends to resolve ambiguities and go on, where UD tends to abort. That means you might get up and running with UV sooner, but UD aborts on bugs that need to be resolved. That can be characterized in terms of rigidity/flexibility. Those EACH have positive AND negative connotations, with respect to Software Quality Attributes, both inherent within UV & UD itself, and in your ability to build quality into your ap using each environment. Consider the implications on: Correctness Dependability Learnability Efficiency Portability Robustness What is important to you would influence your preference of UV or UD. By the way, I've worked in UV much more than UD, which is fine by me. But take that as circumstance of history, more than personal bias. Chuck Stevenson ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
