Issue 14934: Simplify by Making UML More Consistent: Apply class and composite structure diagram rules to behavior modeling (uml2-rtf) Source: Change Vision (Mr. Michael Jesse Chonoles, mjchonoles(at)yahoo.com) Nature: Uncategorized Issue Severity: Summary: Simplify by Making UML More Consistent: Apply class and composite structure diagram rules to behavior modeling. One problem with UML now is that the ability to simplify by applying more consistency is not taken advantage of. By being consistent – eliminating special cases, the specification becomes smaller, the modelers have to learn less, the tools can reuse code, and UML becomes easier to understand and use. As behaviors (e.g., operations, activities) are classifiers, there is no good reason why the class and composite structure diagrams cannot be used to model them. This would allow for diagrams showing inheritance, composition, associations, dependencies, etc. While this may not be “OO”, it would support functional decomposition/programming approaches, simplify, and make more regular the specification. See the RFI response ad/2009-08-05. Resolution: Revised Text: Actions taken: January 11, 2010: received issue Discussion: End of Annotations:===== te: Mon, 11 Jan 2010 00:02:49 -0500 From: "Chonoles, Michael J" Subject: UML Issue: Simplify by Making UML More Consistent: Apply class and composite structure diagram rules to behavior modeling To: "issues@omg.org" Thread-Topic: UML Issue: Simplify by Making UML More Consistent: Apply class and composite structure diagram rules to behavior modeling Thread-Index: AcqSe1DIaU5l9n3zTYy72pF5CSScZQ== Accept-Language: en-US acceptlanguage: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Simplify by Making UML More Consistent: Apply class and composite structure diagram rules to behavior modeling. One problem with UML now is that the ability to simplify by applying more consistency is not taken advantage of. By being consistent . eliminating special cases, the specification becomes smaller, the modelers have to learn less, the tools can reuse code, and UML becomes easier to understand and use. As behaviors (e.g., operations, activities) are classifiers, there is no good reason why the class and composite structure diagrams cannot be used to model them. This would allow for diagrams showing inheritance, composition, associations, dependencies, etc. While this may not be .OO., it would support functional decomposition/programming approaches, simplify, and make more regular the specification. See the RFI response ad/2009-08-05. Michael Jesse Chonoles LMCO/SE-DSIG