Home|News

When Design Matters

CoreLinux++

CoreLinux Consortium

CoreLinux++ Home News Download Project Summary Public surveys Report a Defect Goals What are we Why are we What is our Intent What is not our Intent Developer's Corner C++ Coding Standards Developer's guide Draft Papers FAQ Functional Requirements OO Coding Standards Process Details CL Classes Reference CLFW Classes Reference CVS repository Patch manager Bibliography Open Publication License Adds On Contacts Forums Mailing Lists

Mediator Use Case Report Generated at: Fri, May 05, 2000 21:59:37 TABLE OF CONTENTS REPORT BODY Use case report Class report Data package Component View package libcorelinux package Colleague class Mediator class Event class Identifier class Use Cases package Roles package Developer class Implementor class Model dictionary SUMMARY REPORT BODY Use case report use case Subclass Mediator Documentation: The Mediator on it's own, from libcorelinux, knows nothing about the inter-relationships of Colleagues in the solution space. The Implementor must subclass and define. use case Subclass Colleague Documentation: The Colleagues on their own, from libcorelinux, know nothing about the interface requirements of the solution space. The Implementor must subclass and define. use case Define Relationships between Colleagues to Mediator Documentation: As with the Mediator and Colleagues, the solution space defines the inter-relationship of the domain behavior. It is up to the implementor to define the cause and action relationship between colleagues via the mediator. actor Developer Documentation: Developer actor Implementor Superclasses: Data::Use Cases::Roles::Developer Documentation: Implementor is a developer that uses either the corelinux or extension types into solution space applications. Class report package Data package Data::Component View package Data::libcorelinux abstract class Colleague Documentation: Colleague declares a type that is used in the Mediator pattern. It hides the default constructor as there is a specific relationship to a Mediator instance. abstract class Mediator Documentation: Mediator mediates activity between colleagues. class Event Documentation: Event (borrowed from Subject Observer) describes actions communicated between colleagues via the mediator. class Identifier package Data::Use Cases package Data::Use Cases::Roles class Developer Stereotype:   <<actor>> Documentation: Developer class Implementor Superclasses: Data::Use Cases::Roles::Developer Stereotype:   <<actor>> Documentation: Implementor is a developer that uses either the corelinux or extension types into solution space applications. Model dictionary C   D   E   I   L   M   R   S   U    C Colleague class from package libcorelinux Colleague declares a type that is used in the Mediator pattern. It hides the default constructor as there is a specific relationship to a Mediator instance. Component View package D Data package Define Relationships between Colleagues to Mediator use case from package Use Cases As with the Mediator and Colleagues, the solution space defines the inter-relationship of the domain behavior. It is up to the implementor to define the cause and action relationship between colleagues via the mediator. Developer actor from package Use Cases.Roles Developer Developer class from package Use Cases.Roles Developer E Event class from package libcorelinux Event (borrowed from Subject Observer) describes actions communicated between colleagues via the mediator. I Identifier class from package libcorelinux Implementor actor from package Use Cases.Roles Implementor is a developer that uses either the corelinux or extension types into solution space applications. Implementor class from package Use Cases.Roles Implementor is a developer that uses either the corelinux or extension types into solution space applications. L libcorelinux package M Mediator class from package libcorelinux Mediator mediates activity between colleagues. R Roles package from package Use Cases S Subclass Colleague use case from package Use Cases The Colleagues on their own, from libcorelinux, know nothing about the interface requirements of the solution space. The Implementor must subclass and define. Subclass Mediator use case from package Use Cases The Mediator on it's own, from libcorelinux, knows nothing about the inter-relationships of Colleagues in the solution space. The Implementor must subclass and define. U Use Cases package SUMMARY Total packages reported:     5 Total classes reported:      6 Total use cases reported:    3 Copyright © 1999, 2000 by CoreLinux Consortium This material may be distributed only subject to the terms and conditions set forth in the Open Publication License

Contacts - contact the webmaster News [06/03/01] libclfw++ 0.2.8 [05/12/01] libclfll++ 0.1.1 [04/28/01] libclfw++ 0.2.7 [04/15/01] libcorelinux++ 0.4.32 Powered / Hosted by SourceForge.net Contributor NoMagic, inc. thanks Gary! Cool OO Sites cetus corba omg patterns

Made with xemacs / php

Comments to webmaster