		EventStudio 2.5 Sequence diagram based system design and modeling
Home What's New EventStudio 2.5 Real-time Mantra Thought Projects Contact Us

Object Oriented Design Examples Class List

Here are the classes, structs, unions and interfaces with brief descriptions:

Cold_Resource_Allocator	This class implemented a coldest resource first resource allocator
Datalink_Layer	The Datalink layer class is an example of the Protocol_Layer design pattern
DeregisterRequestMessage	Message used to request deregistration from the status publisher
Hierarchical_State_Machine	This is an example of state machine implementation using Hierarchical State Machines
Hierarchical_State_Machine::Active	This state specifies that the unit is currently in the active plane
Hierarchical_State_Machine::Failed	The unit is known to have failed
Hierarchical_State_Machine::Inservice	Base class for all Inservice states
Hierarchical_State_Machine::Out_Of_Service	Base class for all out of service states
Hierarchical_State_Machine::Standby	The unit is in this state when it is Inservice but it is serving as a standby for the active unit
Hierarchical_State_Machine::Suspect	The unit is suspected to have failed
Hierarchical_State_Machine::Unit_State	Base class for all states of the Unit state machine
Hot_Resource_Allocator	This class implemented a hottest resource first resource allocator
LocalStatusPublisher	Publish subscriber pattern when the publisher and subscriber are objects in the same thread or task
Message_Queue	This class demonstrates the use of the STL queue container adaptor in implementing a message queue
Packet_Queue< Packet >	This class demonstrates the use of the STL queue container adaptor in implementing a message queue
Priority_Message_Queue	This class queues up messages according to the priority assigned to the message at the time of adding it to the queue
Priority_Message_Queue::Compare_Messages	The following structure declares a functor (a function object) for comparing message priorities
Priority_Message_Queue::Entry	The Priority_Message_Queue stores entries defined by this structure
Protocol_Layer	Protocol Layer class serves as the foundation for the Protocol Layer design pattern
Protocol_Packet	The Protocol Packet class supports dynamic addition and extraction of protocol layers without needing multiple copies of the messages when it is exchanged between protocol layers
Protocol_Packet::Region	This structure is used to keep track of different regions of a packet
Protocol_Stack	The Protocol Stack class supports definition of a layered stack of protocol layers
Receive_Protocol_Handler	The Receive Protocol Handler pattern is implemented by just one class
RegisterRequestMessage	Message used to request registration with the status publisher
RemoteStatusPublisher	Publish subscriber pattern when the publisher and subscriber are on different processors and can communicate only via messages
Retransmission_Buffer	The Retransmission Buffer object manages buffers until an acknowledgement is received from the other end
Routing_Table	Routing Table is another pattern that can easily be implemented using map
Subscriber	This is the base class for subscribers of status change information published by the LocalStatusPublisher
Terminal	Terminal class represents a terminal in the real world
Terminal_Manager	Terminal Manager demonstrates the Manager design pattern using the STL map
Transmit_Protocol_Handler	This pattern provides a framework for implementing a sliding window protocol

Generated on Sun Feb 13 21:30:26 2005 for Object Oriented Design Examples by

1.3.4

Home What's New EventStudio 2.5 Real-time Mantra Thought Projects Contact Us
Copyright © 2000-2005 EventHelix.com Inc. All Rights Reserved.