Sequence diagrams Sample Clauses

Sequence diagrams. The timeline in UML is from the top to the bottom. Each arrow is method call. Each vertical line represents a class and its own life line. These diagrams illustrate the different method call available in the class MonitorDaemon and what this produces inside the other classes. Figure 17: Sequence Diagram 1 for the MonitorDaemon class LaunchCapture creates the CaptureController, launches the thread and then adds it to the data stored inside the class. Figure 18: Sequence Diagram 2 for the MonitorDaemon class StopCapture stops the thread, destroys the instance of CaptureController and then removes it from the data stored inside the class. Figure 19: Sequence Diagram 2 for the MonitorDaemon class
Sample 1
AutoNDA by SimpleDocs
Sequence diagrams. 2.1.1 Sender Intent Based Receiver Pull (notified pull) The sequence diagram below depicts the flow for the Sender Intent Based Receiver Pull (SIBR Pull) using OAuth 2.0 and HL7-FHIR, also known as "notified pull". The flow contains the following sections: • Invite the Receiver; • Cancellation by Sender (option), this block is only to be used when the Sender needs to withdraw the pull invitation, e.g., when the Sender invited a wrong Receiver; • Receiver performs pull interaction(s). Each section consists of several steps. The steps correspond to the numbers in the sequence diagram. Section Step Description Invite the Receiver 1 Optional reference to a request-Type resource that produced this event. If a workflow has been initiated, this should be referenced.
Sample 1
Sequence diagrams. A.1.1 Selecting Wetlands User G-A Client + WPS NWI WFS Select wetlands on map Query wetlands Query Wetlands WFS Return wetland features Return wetlands results Display selected wetlands NHD WFS Requirements
Sample 1
Sequence diagrams. ‌ Configuration Phase Before the system can enter normal operations, some setup will be necessary – mostly concerning components registering themselves with the Global Resource Directory, so their IPv6-addresses can be queried on demand. The following manual configuration setup steps will be necessary:
Sample 1

Related to Sequence diagrams

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Outputs 8. The objectives and outcomes of this Agreement will be achieved through a range of outputs. The outputs include the:

  • Contract Changes Changes may not be made in the terms and conditions of this contract without the agreement and written permission of the Director of Residence Life or the Director’s designee.

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • Class Specifications The Human Resources Division shall determine:

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!