Use Case Diagram Sample Clauses

Use Case Diagram. Diagrams of Use Cases represent the functionality of the system from a black box perspective. For the scope of the GENERIS project, this diagram type was only used to constrain interface events to particular users (Actors in the UML terminology, which can be considered as a special type of class). The distinction between whether or not the event can be raised on a particular object and who is authorised to raise it is an important one, worth describing in an example. Both a signaller and an local operator in the field have permission to move a set of points, but not at the same time; as this permission is carefully allocated. However by allocating each an event with which they can move the point and defining that the event is accessible to an actor via a particular use case, the signaller will not have access to the local operator’s event and vice versa. Thus the system’s core does not need to know about the allocation of external permissions (which are anyway beyond its scope), as it is dealt with at the system interface. The net effect of this is that certain written requirements can be implemented at the boundary to the system by simply allocating the use of certain commands to certain users. Thus desired functionality can be achieved while also safeguarding certain model invariants – i.e. that given functionality should only be available to a given user in certain circumstances, or indeed not at all, without the use of any textual constraint. However, it should be noted that merely having the event available does not necessarily mean it will be executed and that brings us to the next diagram type, which has been used to capture most of the complex functionality of the system.
Sample 1
AutoNDA by SimpleDocs
Use Case Diagram. Participating Organization immunization query (QBP) history/ forecast (RSP) PO Participant Source System immunization query (QBP) HIN immunization query (QBP) history/ forecast (RSP) State Data Hub immunization query (QBP) history/ forecast (RSP) history/ forecast (RSP) IIS
Sample 1
Use Case Diagram immunization query (VXQ) Participating immunization query (VXQ) immunization query (VXQ) NJHHS immunization query (VXQ) history/ forecast (VXR) PO Participant Source System Organization NJHIN history/ forecast (VXR) history/ forecast (VXR) Data Hub (PO) history/ forecast (VXR) NJ Immunizatio
Sample 1

Related to Use Case Diagram

  • Use Cases Subscription Services are provided for Software only when used for its supported purpose (“Use Case”). The Use Case determines which Subscription is required and what fees are charged. If you use or deploy the Software in a manner contrary to a supported Use Case, you are responsible for purchasing the appropriate Subscription(s) to cover such usage. For example, if you are using a Red Hat Enterprise Linux Desktop Subscription as a server, you are obligated to purchase a Red Hat Enterprise Linux Server Subscription.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Construction Progress Schedule; Overall Project Schedule The Contractor shall submit for review by the Design Professional and approval by the Owner a Construction Progress Schedule based upon the Design Professional’s Preliminary Design and Construction Schedule and prepared using a CPM (Critical Path Method) process within sixty days after the Effective Date of the Contract, utilizing a full-featured software package in a form satisfactory to the Design Professional and Owner, showing the dates for commencement and completion of the Work required by the Contract Documents, including coordination of mechanical, plumbing, and electrical disciplines, as well as coordination of the various subdivisions of the Work within the Contract. Milestones must be clearly indicated and sequentially organized to identify the critical path of the Project. The Construction Schedule will be developed to represent the CSI specification divisions. It shall have the minimum number of activities required to adequately represent to the Owner the complete scope of Work and define the Project’s (and each Phase’s if phased) critical path and associated activities. The format of the Construction Progress Schedule will have dependencies indicated on a monthly grid identifying milestone dates such as construction start, phase construction, structural top out, dry-in, rough-in completion, metal stud and drywall completion, equipment installation, systems operational, inspections for Material Completion and Occupancy Date, and Final Completion Date. The Contractor shall submit, along with the Construction Progress Schedule, the Submittal Schedule for approval by the Design Professional, correlating the associated approval dates for the documents with the Construction Progress Schedule. Upon recommendation by the Design Professional and approval by the Owner, the Construction Progress Schedule shall become the Overall Project Schedule, which shall be utilized by the Design Professional, Owner and Contractor. The Contractor must provide the Design Professional and the Owner with monthly updates of the Overall Project Schedule indicating completed activities and any changes in sequencing or activity durations, including approved change orders. See also Article 3.3.5.

  • Project Location & Description The Project, for which the provision of financial assistance is the subject of this Agreement, is hereby described as follows:

  • Service Description The Parties will provide Common Channel Signaling (CCS) to one another via Signaling System 7 (SS7) network Interconnection, in accordance with prevailing industry standards. Use of a third party provider of SS7 trunks is permitted.

  • Project Description In two or three brief sentences, provide a concise description of your exhibition. Include the subject matter, type of objects to be included (paintings, sculpture, manuscripts, etc.), those responsible for organizing the exhibition, and catalogue author(s).

  • Equipment List 1. All items of equipment to be purchased with funds under this Contract must be itemized in Grantee’s equipment list as finally approved by the System Agency in the executed Contract. The equipment list must include:

  • Construction Schedule The progress schedule of construction of the Project as provided by Developer and approved by District.

  • Developer Attachment Facilities Developer shall design, procure, construct, install, own and/or control the Developer Attachment Facilities described in Appendix A hereto, at its sole expense.

  • Supported Use Cases Subscription Services are provided for Red Hat Satellite Server, Red Hat Satellite Capsule and Red Hat Satellite Proxy Management Subscriptions only when used for their supported purposes (“Use Case”) in accordance with the terms of this Exhibit and Table 2 below.

Time is Money Join Law Insider Premium to draft better contracts faster.