Will UML 2.0 Be Agile or Awkward?

Saved in:
Bibliographic Details
Title: Will UML 2.0 Be Agile or Awkward?
Authors: Kobryn, Cris1,2 Cris.Kobryn@telelogic.com
Source: Communications of the ACM. Jan2002, Vol. 45 Issue 1, p107-110. 4p.
Subjects: Unified modeling language, Object Management Group Inc., Application software, Computer programming, Programming languages, Computer software development
Abstract: The Unified Modeling Language (UML) has been widely accepted throughout the software industry and successfully applied to diverse domains ever since it was adopted by Object Management Group Inc. (OMG) in 1997. In those four years, UML has become the de facto standard for specifying software architectures that increase in value as one progress from simple design models to multi view enterprise blueprints. Indeed, it is becoming difficult to find a software project with more than 10 developers that does not employ UML in some way to specific part of the software architecture. While UML has been growing in popularity among software developers, the software methods and practices it supports have also been evolving steadily. Considering these trends, as well as numerous requests for UML improvements, it should not be surprising that OMG has decided that UML 1 is ready for a major revision. The UML 2.0 major revision represents both an excellent opportunity and a serious responsibility for its language designers. It is a chance for them to resolve the shortcomings of UML 1 and make the language more current and precise. At the same time, it charges them with the responsibility for improving the language without succumbing to scope creep and design-by-committee compromises. For reasons to be discussed, discharging this responsibility for UML 2.0 will likely be challenging.
Database: Engineering Source
FullText Links:
  – Type: pdflink
Text:
  Availability: 0
Header DbId: egs
DbLabel: Engineering Source
An: 11934595
AccessLevel: 6
PubType: Periodical
PubTypeId: serialPeriodical
PreciseRelevancyScore: 0
IllustrationInfo
Items – Name: Title
  Label: Title
  Group: Ti
  Data: Will UML 2.0 Be Agile or Awkward?
– Name: Author
  Label: Authors
  Group: Au
  Data: <searchLink fieldCode="AR" term="%22Kobryn%2C+Cris%22">Kobryn, Cris</searchLink><relatesTo>1,2</relatesTo><i> Cris.Kobryn@telelogic.com</i>
– Name: TitleSource
  Label: Source
  Group: Src
  Data: <searchLink fieldCode="JN" term="%22Communications+of+the+ACM%22">Communications of the ACM</searchLink>. Jan2002, Vol. 45 Issue 1, p107-110. 4p.
– Name: Subject
  Label: Subjects
  Group: Su
  Data: <searchLink fieldCode="DE" term="%22Unified+modeling+language%22">Unified modeling language</searchLink><br /><searchLink fieldCode="DE" term="%22Object+Management+Group+Inc%2E%22">Object Management Group Inc.</searchLink><br /><searchLink fieldCode="DE" term="%22Application+software%22">Application software</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+programming%22">Computer programming</searchLink><br /><searchLink fieldCode="DE" term="%22Programming+languages%22">Programming languages</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+software+development%22">Computer software development</searchLink>
– Name: Abstract
  Label: Abstract
  Group: Ab
  Data: The Unified Modeling Language (UML) has been widely accepted throughout the software industry and successfully applied to diverse domains ever since it was adopted by Object Management Group Inc. (OMG) in 1997. In those four years, UML has become the de facto standard for specifying software architectures that increase in value as one progress from simple design models to multi view enterprise blueprints. Indeed, it is becoming difficult to find a software project with more than 10 developers that does not employ UML in some way to specific part of the software architecture. While UML has been growing in popularity among software developers, the software methods and practices it supports have also been evolving steadily. Considering these trends, as well as numerous requests for UML improvements, it should not be surprising that OMG has decided that UML 1 is ready for a major revision. The UML 2.0 major revision represents both an excellent opportunity and a serious responsibility for its language designers. It is a chance for them to resolve the shortcomings of UML 1 and make the language more current and precise. At the same time, it charges them with the responsibility for improving the language without succumbing to scope creep and design-by-committee compromises. For reasons to be discussed, discharging this responsibility for UML 2.0 will likely be challenging.
PLink https://search.ebscohost.com/login.aspx?direct=true&site=eds-live&db=egs&AN=11934595
RecordInfo BibRecord:
  BibEntity:
    Identifiers:
      – Type: doi
        Value: 10.1145/502269.502306
    Languages:
      – Code: eng
        Text: English
    PhysicalDescription:
      Pagination:
        PageCount: 4
        StartPage: 107
    Subjects:
      – SubjectFull: Unified modeling language
        Type: general
      – SubjectFull: Object Management Group Inc.
        Type: general
      – SubjectFull: Application software
        Type: general
      – SubjectFull: Computer programming
        Type: general
      – SubjectFull: Programming languages
        Type: general
      – SubjectFull: Computer software development
        Type: general
    Titles:
      – TitleFull: Will UML 2.0 Be Agile or Awkward?
        Type: main
  BibRelationships:
    HasContributorRelationships:
      – PersonEntity:
          Name:
            NameFull: Kobryn, Cris
    IsPartOfRelationships:
      – BibEntity:
          Dates:
            – D: 01
              M: 01
              Text: Jan2002
              Type: published
              Y: 2002
          Identifiers:
            – Type: issn-print
              Value: 00010782
          Numbering:
            – Type: volume
              Value: 45
            – Type: issue
              Value: 1
          Titles:
            – TitleFull: Communications of the ACM
              Type: main
ResultId 1