The History of UML / UML的历史
Identifiable object-oriented modeling languages began to appear between mid-1970 and the late 1980s as various methodologists experimented with different approaches to object-oriented analysis and design.
可识别的面向对象的建模语言开始出现在1970年代中期至80年代末期,因为各种方法学家尝试了不同的面向对象分析和设计方法。
he number of identified modeling languages increased from less than 10 to more than 50 during the period between 1989-1994.
1989年至1994年期间,确定的建模语言从不到10个增加到50个以上。
Many users of OO methods had trouble finding complete satisfaction in any one modeling language, fueling the "method wars."
面向对象方法的许多用户无法在任何一种建模语言中找到完全满意的结果,从而助长了“方法之战”。
By the mid-1990s, new iterations of these methods began to appear and these methods began to incorporate each other’s techniques, and a few clearly prominent methods emerged.
到了20世纪90年代中期,这些方法开始出现新的迭代,并且这些方法开始结合彼此的技术,并且出现了一些明显突出的方法。
The development of UML began in late 1994 when Grady Booch and Jim Rumbaugh of Rational Software Corporation began their work on unifying the Booch and OMT (Object Modeling Technique) methods.
UML的开发始于1994年底,当时Rational软件公司的Grady Booch和Jim Rumbaugh开始着手统一Booch 和 OMT(对象建模技术)方法。
In the Fall of 1995, Ivar Jacobson and his Objectory company joined Rational and this unification effort, merging in the OOSE (Object-Oriented Software Engineering) method.
在1995年秋天,Ivar Jacobson和他的Objectory公司加入了Rational和这个统一工作,并入了OOSE(面向对象的软件工程)方法。
As the primary authors of the Booch, OMT, and OOSE methods, Grady Booch, Jim Rumbaugh, and Ivar Jacobson were motivated to create a unified modeling language for three reasons.
作为Booch,OMT和OOSE方法的主要作者,Grady Booch,Jim Rumbaugh和Ivar Jacobson被激励创建统一建模语言,原因有三。
First, these methods were already evolving toward each other independently. It made sense to continue that evolution together rather than apart, eliminating the potential for any unnecessary and gratuitous differences that would further confuse users.
首先,这些方法已经彼此独立发展。继续进化而不是分开是有意义的,消除了任何不必要的和无理的差异的可能性,这会进一步混淆用户。
Second, by unifying the semantics and notation, they could bring some stability to the object-oriented marketplace, allowing projects to settle on one mature modeling language and letting tool builders focus on delivering more useful features.
其次,通过统一语义和符号,它们可以为面向对象的市场带来一些稳定性,从而使项目能够适应一种成熟的建模语言,并让工具构建者专注于提供更多有用的功能。
Third, they expected that their collaboration would yield improvements in all three earlier methods, helping them to capture lessons learned and to address problems that none of their methods previously handled well.
第三,他们期望他们的合作能够改善早期的三种方法,帮助他们掌握吸取的经验教训,解决他们以前没有任何方法处理好的问题.
The efforts of Booch, Rumbaugh, and Jacobson resulted in the release of the UML 0.9 and 0.91 documents in June and October of 1996.
Booch,Rumbaugh和Jacobson的努力导致1996年6月和10月发布了UML 0.9和0.91文件。
During 1996, the UML authors invited and received feedback from the general community. They incorporated this feedback, but it was clear that additional focused attention was still required.
1996年,UML作者邀请并收到了来自社区的反馈。他们纳入了这些反馈意见,但很明显,仍需要额外的重点关注。
While Rational was bringing UML together, efforts were being made on achieving the broader goal of an industry standard modeling language.
在Rational将UML带到一起时,正在努力实现行业标准建模语言的更广泛目标。
In early 1995, Ivar Jacobson (then Chief Technology Officer of Objectory) and Richard Soley (then Chief Technology Officer of OMG) decided to push harder to achieve standardization in the methods marketplace.
1995年初,Ivar Jacobson(当时的首席技术官)和Richard Soley(当时的OMG首席技术官)决定更加努力地实现方法市场的标准化。
In June 1995, an OMG-hosted meeting of all major methodologists (or their representatives) resulted in the first worldwide agreement to seek methodology standards, under the aegis of the OMG process.
1995年6月,由OMG主持的所有主要方法学家(或其代表)会议在OMG进程的支持下成为第一个寻求方法学标准的全球协议。
During 1996, it became clear that several organizations saw UML as strategic to their business.
在1996年期间,很明显有几个组织认为UML对其业务具有战略意义。
A Request for Proposal (RFP) issued by the Object Management Group (OMG) provided the catalyst for these organizations to join forces around producing a joint RFP response.
由对象管理组织(OMG)发布的征求建议书(RFP)为这些组织联合起来制定RFP联合响应提供了催化剂。
Rational established the UML Partners consortium with several organizations willing to dedicate resources to work toward a strong UML 1.0 definition.
Rational建立了UML Partners联盟与几个愿意投入资源为UML 1.0定义提供强有力支持的组织。
Those contributing most to the UML 1.0 definition included: Digital Equipment Corp., HP, i-Logix, IntelliCorp, IBM, ICON Computing, MCI Systemhouse, Microsoft, Oracle, Rational Software, TI, and Unisys.
那些对UML 1.0定义最为重要的人包括:Digital Equipment Corp.,HP,i-Logix,IntelliCorp,IBM,ICON Computing,MCI Systemhouse,Microsoft,Oracle,Rational Software,TI和Unisys。
This collaboration produced UML 1.0, a modeling language that was well defined, expressive, powerful, and generally applicable. This was submitted to the OMG in January 1997 as an initial RFP response.
这次合作产生了UML 1.0,这是一种定义明确,表达力强大且通用的建模语言。这是作为最初的RFP响应于1997年1月提交给OMG的。
In January 1997 IBM, ObjecTime, Platinum Technology, Ptech, Taskon, Reich Technologies and Softeam also submitted separate RFP responses to the OMG.
1997年1月,IBM,ObjecTime,Platinum Technology,Ptech,Taskon,Reich Technologies和Softeam也向OMG提交了单独的RFP响应。
These companies joined the UML partners to contribute their ideas, and together the partners produced the revised UML 1.1 response.
这些公司加入了UML合作伙伴来贡献他们的想法,并且合作伙伴共同制定了修订的UML 1.1响应。
The focus of the UML 1.1 release was to improve the clarity of the UML 1.0 semantics and to incorporate contributions from the new partners. It was submitted to the OMG for their consideration and adopted in the fall of 1997.
UML 1.1 版本的重点是提高 UML 1.0语义的清晰度并纳入新合作伙伴的贡献。它被提交给OMG供其审议并通过了1997年秋季
Other related article
其他相關文章