Issue 8897: OutputPin (uml2-rtf) Source: No Magic, Inc. (Mr. Nerijus Jankevicius, nerijus(at)nomagic.com) Nature: Uncategorized Issue Severity: Summary: OutputPin should hold output value, but there is no way to store it. Should be introduced similar metaclass like ValuePin for InputPin Resolution: Revised Text: Actions taken: June 20, 2005: received issue Discussion: End of Annotations:===== s is issue # 8897 OutputPin Reply-To: From: "Conrad Bock" To: "Nerijus Jankevicius" , , "Juergen Boldt" , Subject: RE: some issues Date: Thu, 23 Jun 2005 20:11:10 -0400 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Nerijus, > 3. ObjectNode is abstract, so CentralBuffer or DataStore should > be always used in Activity diagram. It is normal? > CentralBuffer and DataStore are described as "special cases of > ObjectNodes", but simple ObjectNode can't exist. Pins are also object nodes, see Figure 178. But even apart from Activities, pins can hold values because they are typed elements, see Figure 143. Object nodes add queuing, etc. > 4. The same situation is with abstract Action in Activity > diagram. OpaqueAction also can't be used, because can't have Pins. This was recently filed, will add pins to OpaqueAction. > How to draw "human friendly" action (activity)? The only way is > to use CallBehaviorAction? OpaqueAction isn't actually that friendly, because it isn't reusable. > 5. OutputPin should hold output value, but there is no way to > store it. Should be introduced similar metaclass like ValuePin > for InputPin. Didn't understand this question. From: "Nerijus Jankevicius" To: Cc: Subject: Re: some issues Date: Mon, 27 Jun 2005 20:11:29 +0300 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 Conrad, Thanks for your time, see my comments below. > 3. ObjectNode is abstract, so CentralBuffer or DataStore should > be always used in Activity diagram. It is normal? > CentralBuffer and DataStore are described as "special cases of > ObjectNodes", but simple ObjectNode can't exist. Pins are also object nodes, see Figure 178. But even apart from Activities, pins can hold values because they are typed elements, see Figure 143. Object nodes add queuing, etc. "An object node is an activity node that indicates an instance of a particular classifier. " "A central buffer node accepts tokens from upstream objects nodes and passes them along to downstream object nodes. They act as a buffer for multiple in flows and out flows from other object nodes. They do not connect directly to actions." DataStoreNode is special subclass of CentralBufferNode. So what kind of ObjectNode should be used in regular Activity diagram to represent instance of some type? ObjectNode is abstract, CentralBuffer and DataStore are for different purposes. Pins are parts of actions. What kind of ObjectNode is in all diagram examples in Activity chapter? We decide to use CentralBufferNode by default in our tool, but I think this is not acceptable, ObjectNode should be not abstract. > 5. OutputPin should hold output value, but there is no way to > store it. Should be introduced similar metaclass like ValuePin > for InputPin. Didn't understand this question. OutputPin is described as "An output pin is a pin that holds output values produced by an action." The problem is that OutputPin doesn't have attribute for "holding output values" (some constant value for example). The same situation is with InputPin, but InputPin has subclass ValuePin that holds value as ValueSpecification. Regards, -- Nerijus Jankevicius Senior Programmer & System Analyst OMG-Certified UML Professional No Magic Lithuanian Development Center Savanoriu pr. 363, LT 49425 Kaunas P.O. box 2166, LT- 3000, Kaunas Phone: +370-37-324032 Fax: +370-37-320670 e-mail: nerijus@magicdraw.com WWW: http://www.magicdraw.com ----- Original Message ----- From: "Conrad Bock" To: "Nerijus Jankevicius" ; ; "Juergen Boldt" ; Sent: Monday, June 27, 2005 7:34 PM Subject: RE: some issues Sorry if there are multiple copies of this. Nerijus, > 3. ObjectNode is abstract, so CentralBuffer or DataStore should > be always used in Activity diagram. It is normal? > CentralBuffer and DataStore are described as "special cases of > ObjectNodes", but simple ObjectNode can't exist. Pins are also object nodes, see Figure 178. But even apart from Activities, pins can hold values because they are typed elements, see Figure 143. Object nodes add queuing, etc. > 4. The same situation is with abstract Action in Activity > diagram. OpaqueAction also can't be used, because can't have Pins. This was recently filed, will add pins to OpaqueAction. > How to draw "human friendly" action (activity)? The only way is > to use CallBehaviorAction? OpaqueAction isn't actually that friendly, because it isn't reusable. > 5. OutputPin should hold output value, but there is no way to > store it. Should be introduced similar metaclass like ValuePin > for InputPin. Didn't understand this question. OutputPin should hold output value, but there is no way to store it. Should be introduced similar metaclass like ValuePin for InputPin