rup signal F91446AD






Work Product (Artifact): Signal








var defaultQueryStr = '?proc={002674F9-6511-4D15-8623-B761D8C48986}&path={002674F9-6511-4D15-8623-B761D8C48986},{DAFB461E-9ADB-4849-8285-B7E3E72BDB43},_uEK_dfRSEdyv-tm4a00cLg';
var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=null;
contentPage.preload(imgPath, backPath, nodeInfo, defaultQueryStr, false, true, false);










Work Product (Artifact): Signal















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






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:




Properties



Optional


Planned



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();
contentPage.processPage.fixDescriptorLinks();




Wyszukiwarka

Podobne podstrony:
rup signal?16C912
rup process engineerQCC276E
rup stakeholder11D446
when signal integrity matters
rup test manager?449E26
rup review record?AA30B5
rup test?signer>A684A0
rup?velopment process?B5F490

więcej podobnych podstron