Issue 18085: Location: 18.1.4 Notation P. 688 - Can Use Cases have attributes and operations? (uml25-ftf) Source: oose Innovative Informatik GmbH (Mr. Axel Scheithauer, axel.scheithauer(at)oose.de) Nature: Clarification Severity: Significant Summary: A UseCase is a BehavioredClassifier, which is a Classifier, which has features of Type Property (Subclasses are Operation and Reception). However "feature" is a derived union and neither BehavioredClassifier nor UseCase define subsets of it. Therefore the features of a UseCase are always an empty set. I heard of one UML-Tool that actually enforces this rule. Resolution: Revised Text: Actions taken: September 28, 2012: received issue Discussion: End of Annotations:===== s is issue # 18085 Problem: 18.056 Severity: Significant Type: Inconsistency Location: 18.1.4 Notation P. 688 Title: Can Use Cases have attributes and operations? Description: A UseCase is a BehavioredClassifier, which is a Classifier, which has features of Type Property (Subclasses are Operation and Reception). However "feature" is a derived union and neither BehavioredClassifier nor UseCase define subsets of it. Therefore the features of a UseCase are always an empty set. I heard of one UML-Tool that actually enforces this rule. Source: Axel Scheithauer From: "BERNARD, Yves" To: "uml25-ftf@omg.org" Date: Thu, 21 Feb 2013 12:24:15 +0100 Subject: [UML 2.5 FTF] Ballot 2 review: #18085 Thread-Topic: [UML 2.5 FTF] Ballot 2 review: #18085 Thread-Index: Ac4QJftZyRiemGAmRIenMC7cJCKBFg== Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US X-Virus-Scanned: amavisd-new at omg.org I think I see what the issue is. My understanding is that Axel says that, since to the current metamodel where UseCase defines no subset for the feature property of its Classifier superclass, a UseCase is not actually able to have any feature. The question is: is it intentional (and then it could be worth to state it explicitly) or unexpected (and then this should be fixed)? Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: "Wendland, Marc-Florian" To: "BERNARD, Yves" , "uml25-ftf@omg.org" Subject: AW: [UML 2.5 FTF] Ballot 2 review: #18085 Thread-Topic: [UML 2.5 FTF] Ballot 2 review: #18085 Thread-Index: Ac4QJftZyRiemGAmRIenMC7cJCKBFgAAsm4A Date: Thu, 21 Feb 2013 11:45:37 +0000 Accept-Language: de-DE, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.147.67.38] x-kse-antivirus-interceptor-info: scan successful x-kse-antivirus-info: Clean X-cloud-security-sender: marc-florian.wendland@fokus.fraunhofer.de X-cloud-security-recipient: uml25-ftf@omg.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mx-gate03-haj2 with 80ACB1D8021 X-cloud-security: scantime:.2587 X-Virus-Scanned: amavisd-new at omg.org Hi all, Maybe interesting in this context is whether it makes sense to allow UseCases to establish InterfaceRealizations (inherited by BehavioralFeature)? What does it mean if a UseCase realizes an Interface? Regards, Marc-Florian Von: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] Gesendet: Donnerstag, 21. Februar 2013 12:24 An: uml25-ftf@omg.org Betreff: [UML 2.5 FTF] Ballot 2 review: #18085 I think I see what the issue is. My understanding is that Axel says that, since to the current metamodel where UseCase defines no subset for the feature property of its Classifier superclass, a UseCase is not actually able to have any feature. The question is: is it intentional (and then it could be worth to state it explicitly) or unexpected (and then this should be fixed)? Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: Steve Cook To: "Wendland, Marc-Florian" , "BERNARD, Yves" , "uml25-ftf@omg.org" Subject: RE: [UML 2.5 FTF] Ballot 2 review: #18085 Thread-Topic: [UML 2.5 FTF] Ballot 2 review: #18085 Thread-Index: Ac4QJftZyRiemGAmRIenMC7cJCKBFgAAsm4AAAAgA5A= Date: Thu, 21 Feb 2013 11:58:31 +0000 Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.166.18.105] X-Forefront-Antispam-Report: CIP:131.107.125.37;CTRY:US;IPV:CAL;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(199002)(189002)(365934001)(512954001)(49866001)(65816001)(33656001)(47976001)(50986001)(55846006)(47736001)(47446002)(63696002)(54316002)(74502001)(76482001)(56776001)(15202345001)(16236675001)(20776003)(53806001)(74662001)(4396001)(46102001)(31966008)(51856001)(54356001)(5343635001)(44976002)(77982001)(5343655001)(59766001)(80022001)(56816002)(79102001)(16406001);DIR:OUT;SFP:;SCL:1;SRVR:BY2FFO11HUB028;H:TK5EX14HUBC104.redmond.corp.microsoft.com;RD:InfoDomainNonexistent;A:1;MX:1;LANG:en; X-OriginatorOrg: microsoft.onmicrosoft.com X-Forefront-PRVS: 0764C4A8CD X-Virus-Scanned: amavisd-new at omg.org This is related to open issue 12942 . .Actors cannot own Operations - a contradiction.. I have no objection to withdrawing 18085 from this ballot and merging it with 12942: which we would then have to discuss. -- Steve From: Wendland, Marc-Florian [mailto:marc-florian.wendland@fokus.fraunhofer.de] Sent: 21 February 2013 11:46 To: BERNARD, Yves; uml25-ftf@omg.org Subject: AW: [UML 2.5 FTF] Ballot 2 review: #18085 Hi all, Maybe interesting in this context is whether it makes sense to allow UseCases to establish InterfaceRealizations (inherited by BehavioralFeature)? What does it mean if a UseCase realizes an Interface? Regards, Marc-Florian Von: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] Gesendet: Donnerstag, 21. Februar 2013 12:24 An: uml25-ftf@omg.org Betreff: [UML 2.5 FTF] Ballot 2 review: #18085 I think I see what the issue is. My understanding is that Axel says that, since to the current metamodel where UseCase defines no subset for the feature property of its Classifier superclass, a UseCase is not actually able to have any feature. The question is: is it intentional (and then it could be worth to state it explicitly) or unexpected (and then this should be fixed)? Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: "BERNARD, Yves" To: Steve Cook , "Wendland, Marc-Florian" , "uml25-ftf@omg.org" Date: Thu, 21 Feb 2013 14:00:19 +0100 Subject: RE: [UML 2.5 FTF] Ballot 2 review: #18085 Thread-Topic: [UML 2.5 FTF] Ballot 2 review: #18085 Thread-Index: Ac4QJftZyRiemGAmRIenMC7cJCKBFgAAsm4AAAAgA5AAAnzR8A== Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US X-Virus-Scanned: amavisd-new at omg.org X-Brightmail-Tracker: AAAAAgr+n5EdGLWY X-Brightmail-Tracker: AAAAAA== I.m fine with that. Thanks, Yves From: Steve Cook [mailto:Steve.Cook@microsoft.com] Sent: jeudi 21 féier 2013 12:59 To: Wendland, Marc-Florian; BERNARD, Yves; uml25-ftf@omg.org Subject: RE: [UML 2.5 FTF] Ballot 2 review: #18085 This is related to open issue 12942 . .Actors cannot own Operations - a contradiction.. I have no objection to withdrawing 18085 from this ballot and merging it with 12942: which we would then have to discuss. -- Steve From: Wendland, Marc-Florian [mailto:marc-florian.wendland@fokus.fraunhofer.de] Sent: 21 February 2013 11:46 To: BERNARD, Yves; uml25-ftf@omg.org Subject: AW: [UML 2.5 FTF] Ballot 2 review: #18085 Hi all, Maybe interesting in this context is whether it makes sense to allow UseCases to establish InterfaceRealizations (inherited by BehavioralFeature)? What does it mean if a UseCase realizes an Interface? Regards, Marc-Florian Von: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] Gesendet: Donnerstag, 21. Februar 2013 12:24 An: uml25-ftf@omg.org Betreff: [UML 2.5 FTF] Ballot 2 review: #18085 I think I see what the issue is. My understanding is that Axel says that, since to the current metamodel where UseCase defines no subset for the feature property of its Classifier superclass, a UseCase is not actually able to have any feature. The question is: is it intentional (and then it could be worth to state it explicitly) or unexpected (and then this should be fixed)? Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.