Creating the Business Context Models Sample Clauses

Creating the Business Context Models. The diagrams below have been built using REA modeling elements, here expressed as UML stereotypes. (NOTE: they present only a subset of the full diagram! E.g. there should be a Resource:Payload and Resource:Labor which is transformed or used by the Events…) Figure 1 presents the business context diagram for the shipping agency. Here are the key elements of that diagram: • The agency expects the payment first, and only then delivers the service • The roles of ShippingAgent and Cashier are split into two different entities (persons, divisions …) • ShippingAgent and Cashier collaborate with each other in order to satisfy the business rules (payment needs to be fulfilled first, and only then the shipment takes place) • Both ShippingAgent and Cashier collaborate with the Customer. 2 - GIVE «Commitment» Shipment collaboration executes collaboration role custody role «Event» Shipment stock-flow «Resource» {use} Car «Agreement» «Agent» ShippingContract Customer Uses {when, how long, etc …} Gives {when, where to, etc …} «Event» CashRcpt «Resource» Cash «Commitment» Payment collaboration «Agent» Cashier 1 - TAKE «Agent» ShippingAgent labor cars cash used cars Figure 12 Business Context model as seen by the shipping agency. cash payload 2 - TAKE «Commitment» Shipment collaboration executes role role «Event» Shipment custody stock-flow «Resource» {use} Truck «Agreement» «Agent» ShippingContract Customer Uses {when, how long, etc …} Gives {when, where to, etc …} «Event» CashRcpt «Resource» Cash $1000 «Commitment» Payment collaboration «Agent» ShippingAgent 1 - GIVE «Agent» ShippingAgent shipped payload Figure 13 Business Context model as seen by the customer. Now, for the customer the business context can be represented as shown on the next Figure. The key elements are: • Customer expects first to give cash, then receive a service • Customer wants to deal with the same entity for both events • Customer has some specific demands on the kind of car, and the amount of cash.
Sample 1
AutoNDA by SimpleDocs
Creating the Business Context Models. The diagrams below have been built using REA modeling elements, here expressed as UML stereotypes. (NOTE: they present only a subset of the full diagram! E.g. there should be a Resource:Payload and Resource:Labor which is transformed or used by the Events…) Figure 1 presents the business context diagram for the shipping agency. Here are the key elements of that diagram: • The agency expects the payment first, and only then delivers the service • The roles of ShippingAgent and Cashier are split into two different entities (persons, divisions …) • ShippingAgent and Cashier collaborate with each other in order to satisfy the business rules (payment needs to be fulfilled first, and only then the shipment takes place) • Both ShippingAgent and Cashier collaborate with the Customer.
Sample 1

Related to Creating the Business Context Models

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Vendor’s Specific Warranties, Terms, and License Agreements Because TIPS serves public entities and non-profits throughout the nation all of which are subject to specific laws and policies of their jurisdiction, as a matter of standard practice, TIPS does not typically accept a Vendor’s specific “Sale Terms” (warranties, license agreements, master agreements, terms and conditions, etc.) on behalf of all TIPS Members. TIPS may permit Vendor to attach those to this Agreement to display to interested customers what terms may apply to their Supplemental Agreement with Vendor (if submitted by Vendor for that purpose). However, unless this term of the Agreement is negotiated and modified to state otherwise, those specific Sale Terms are not accepted by TIPS on behalf of all TIPS Members and each Member may choose whether to accept, negotiate, or reject those specific Sale Terms, which must be reflected in a separate agreement between Vendor and the Member in order to be effective.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Solicitations for Subcontracts, Including Procurement of Materials and Equipment In all solicitation, either by competitive bidding or negotiation, made by the Contractor for work to be performed under a subcontract, including procurement of materials or leases of equipment, each potential Subcontractor or supplier shall be notified by the Contractor of the Contractor’s obligations under this Agreement and the Regulations relative to non-discrimination on the grounds of race, color, or national origin.

  • Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2003) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2003 Expiration Date: 06/30/2006 PERB ID Number: 10699 Unit Size: Number of Pages: 23 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT BETWEEN WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION AND THE WHITESVILLE CENTRAL SCHOOL DISTRICT JULY 1, 2003 THROUGH JUNE 30, 2006 TABLE OF CONTENTS ARTICLE TITLE PAGE Preamble 1 I Recognition 1 II Collective Bargaining U n i t 1 III Dues/Agency Fee Ckoffand Payroll Deduction 1 IV Rights of Employees 2 V Rights of Employer ------------- 2 VI Personnel F i l e 2 VII Employee Definitions 3 VIII Permanent Status/Seniority 4 IX Wages 5 X Overtime 7 XI Vacation 7 XII Holidays 8 XIII Sick Leave and Leavesof A b s e n c e 8 XIV Conference, Workshops,Required Courses 10 XV Meal Allowance and M i l e a g e 11 XVI Retirement 11 XVII Insurance 12 XVIII Cafeteria P l a n 14 .XIX Uniform Allowance------------------ 14 XX Hours of W o r k 14 XXI Transfers/Promotions 15 XXII Job Descriptions 15 XXIII Grievance Procedure 15 XIV Copies of the Contract 18 XV Zipper C x x x x x 18 XXVI Legislative Clause 18 XXVII Duration 19 SIGNATURES 19 APPENDIX A Grievance F o r m 20 APPENDIX B Dues Authorization F o r m 21

  • Modification of Licensed Materials The Participating Institutions or the Authorized Users shall not modify or manipulate the Licensed Materials without the prior written permission of the Licensor.

  • Exclusions and Limitations for Third Party Software SUBJECT TO THE EXCLUSION OF DAMAGES STATED IN SECTION 9.2 AND WITH RESPECT TO THIRD PARTY SOFTWARE, UNDER NO CIRCUMSTANCES AND REGARDLESS OF THE NATURE OF ANY CLAIM SHALL SAP OR ITS LICENSORS’ BE LIABLE FOR AN AMOUNT IN EXCESS OF THE PAID LICENSE FEES FOR THE THIRD PARTY SOFTWARE DIRECTLY CAUSING THE DAMAGES.

  • Access to Software Access Rights to Software which is Results shall comprise: Access to the Object Code; and, where normal use of such an Object Code requires an Application Programming Interface (hereafter API), Access to the Object Code and such an API; and, if a Party can show that the execution of its tasks under the Project or the Exploitation of its own Results is technically or legally impossible without Access to the Source Code, Access to the Source Code to the extent necessary. Background shall only be provided in Object Code unless otherwise agreed between the Parties concerned.

  • Use of Interconnection Facilities by Third Parties 6551 Error! Hyperlink reference not valid.9.9.1 Purpose of Interconnection Facilities. 6551

  • Intellectual Property Rights in Construction Documents, Drawings, and Models The drawings, Specifications and other documents prepared by the Design Professional pursuant to this Contract (including, without limitation, the Construction Documents), are the property of the Owner, whether or not the Project for which they are made commences or completes construction. Neither the Contractor nor any Subcontractor or material or equipment supplier shall own or claim a copyright in such drawings, Specifications, and other similar or related documents; Owner shall retain all common law, statutory, and other intellectual property rights with respect thereto. The Contractor must deliver remaining copies of such documents to the Owner upon request or upon completion of the Work, except that the Contractor may keep one copy of such documents for its files. The Contractor shall only use such drawings, Specifications and other documents for this Project. Neither the Contractor nor any Subcontractor or material or equipment supplier may use such drawings, Specifications, and other documents on other projects without the specific written consent of the Owner. All models are the property of the Owner.

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