Artifact: Signal









var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_QV4x0AISEdqTna4sZVFRow", "_kjFBYN7HEdm8G6yT7-Wdqw", "{8CDAEAD4-5E84-4F50-87FD-3240ED047DE7}", "{8CA124DA-A80C-45D7-BC65-BA6B4247FF11}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_EOvXUN7HEdm8G6yT7-Wdqw", "_kjFBYN7HEdm8G6yT7-Wdqw", "{8CDAEAD4-5E84-4F50-87FD-3240ED047DE7}", "{8CA124DA-A80C-45D7-BC65-BA6B4247FF11}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_mTMIkN7REdmjRZts2c4ZjQ", "{8CDAEAD4-5E84-4F50-87FD-3240ED047DE7}", "{8CA124DA-A80C-45D7-BC65-BA6B4247FF11}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_n7ZcgN7REdmjRZts2c4ZjQ", "{8CA124DA-A80C-45D7-BC65-BA6B4247FF11}"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);










Artifact: Signal















This work product specifies an asynchronous stimulus from one object or instance to another.


Work Product Kinds: Model Element






Purpose



The purpose of a signal is to provide one-way asynchronous communication from one object or instance to another. Signals are a specialization of Artifact: Event that can have operations, attributes, and relationships.



Relationships



Container Artifact


Design Model





RolesResponsible:



Software Architect


Modified By:



Software Architect





TasksInput To:



Class Design


Output From:



Identify Design Elements





Process Usage


Analysis & Design
 > 
Refine the Architecture
 > 
Signal


Analysis & Design
 > 
Refine the Architecture
 > 
Signal


Analysis & Design
 > 
Design the Database
 > 
Signal


Analysis & Design
 > 
Analyze Behavior
 > 
Signal


Analysis & Design
 > 
Analyze Behavior
 > 
Signal


Analysis & Design
 > 
Design Components
 > 
Signal






Tailoring



Representation OptionsUML Representation: Signal. Also commonly represented as a class stereotyped <<signal>>.  Signals are used to define entities for asynchronous messaging. They are suitable for communication in distributed and concurrent systems. Avoid naming signals in a 'receiver-specific' manner - this limits their generality and usefulness, bearing in mind that signals may be broadcasted to a set of objects. The important thing is to communicate the interesting occurrence the sender has detected (which prompted it to send the signal). A signal may also have a list of parameters which are represented as its attributes. Operations may be provided on a signal to access these attributes. Since Signals are a specialization of Work product: Event, signal tailoring is dependent on the tailoring for Work product: Event. For example, the Work product: Event information can be captured in textual form (such as a table in the Software Architecture Document), while the Signal-specific properties are captured in a visual model.



More Information



Checklists


Signal





Concepts


Events and Signals








©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.







contentPage.onload();