Goal-oriented modelling overview Sample Clauses

Goal-oriented modelling overview. This section give a short overview of goal-oriented requirements engineering, what it could provide in the scope of the Deploy project and which experi- ments have been carried out so far. For a more extended overview the reader can look at [vL01] and for a complete reference at [vL09] Goal-Oriented Requirements Engineering (XXXX) is concerned with the use of goals for eliciting, elaborating, structuring, specifying, analyzing, nego- tiating, documenting, and modifying requirements. Goals capture, at differ- ent levels of abstraction, the various objectives that the system under consid- eration should achieve. Goal formulations thus refer to intended properties to be ensured: they prescribe statements of intent about the system-to-be. They can range from high level strategic goals to low level technical con- cerns. Reasoning on goals can occur at two levels: semi-formal (UML-like modelling with some model constraints) and formal (with formal semantics and reasoning, generally based on some form of temporal logic). The main approaches supporting XXXX are KAOS [DFvL91, vL09], NFR [CNYM00], i* [Yu97] and Tropos [BPG+04]. Beside goals, they share com- mon concepts such as: the refinement/contribution between sub-goals: a set of child goals log- ically entails or, less formally, contributes to the satisfaction of the parent goal — enabling the modelling of system-wide collaborations to reach some goal the conflict/negative contributions between goals: if under some cir- cumstances, two (or more) goals cannot be enforced together the assignment of a goal to an agent which is responsible for its real- isation and must have the capability to realise it. Such goals are also called requirements. Intrinsically, XXXX provides a number of guarantees on the requirements engineering process such as: goals provide a precise criterion for sufficient completeness of a requirements specification [Yue87]. Hence they also mo- tivate the pertinency of all requirements (the specification doesn’t provide for more than what is asked for). By providing means to detect and resolve inconsistencies between requirements they help achieving consistency. They also support dependability by the identification of unexpected conditions and the elaboration of robust requirements that take them into account. At this stage of Deploy, XXXX was investigated in the following ways, mainly based on the KAOS methodology: Practical and small scale experimentation were conducted on two mini- pilots des...
AutoNDA by SimpleDocs

Related to Goal-oriented modelling overview

  • Program Overview Microsoft extends to eligible partners the opportunity to participate in the Program referenced above subject to these Program Terms & Conditions (“Program Terms”). Each entity participating in the Program is hereinafter referred to as a “Participant.” Participation in the Program is voluntary. The Program is governed by the Program Terms, which incorporate by reference the Microsoft Partner Network Agreement (as in effect between Microsoft and Participant, the “MPN Agreement”). Capitalized terms used but not defined in these Program Terms have the meanings assigned to them in the MPN Agreement. These Program Terms are subject to local requirements and may vary by jurisdiction, and Participant retains sole discretion to set pricing for sales of applicable products.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Your Billing Rights: Keep this Document for Future Use This notice tells you about your rights and our responsibilities under the Fair Credit Billing Act.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Alignment with Modernization Foundational Programs and Foundational Capabilities The activities and services that the LPHA has agreed to deliver under this Program Element align with Foundational Programs and Foundational Capabilities and the public health accountability metrics (if applicable), as follows (see Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf): a. Foundational Programs and Capabilities (As specified in Public Health Modernization Manual) b. The work in this Program Element helps Oregon’s governmental public health system achieve the following Public Health Accountability Metric: c. The work in this Program Element helps Oregon’s governmental public health system achieve the following Public Health Modernization Process Measure:

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

  • Interim Measures Notwithstanding any requirements for alternative dispute resolution procedures as set forth in Articles 18(B), any party to the Dispute may apply to a court for interim measures (i) prior to the constitution of the arbitral tribunal (and thereafter as necessary to enforce the arbitral tribunal’s rulings); or (ii) in the absence of the jurisdiction of the arbitral tribunal to rule on interim measures in a given jurisdiction. The Parties agree that seeking and obtaining such interim measures shall not waive the right to arbitration. The arbitrators (or in an emergency the presiding arbitrator acting alone in the event one or more of the other arbitrators is unable to be involved in a timely fashion) may grant interim measures including injunctions, attachments and conservation orders in appropriate circumstances, which measures may be immediately enforced by court order. Hearings on requests for interim measures may be held in person, by telephone, by video conference or by other means that permit the parties to the Dispute to present evidence and arguments.

  • CONTRACTOR NAME CHANGE An amendment is required to change the Contractor's name as listed on this Agreement. Upon receipt of legal documentation of the name change the State will process the amendment. Payment of invoices presented with a new name cannot be paid prior to approval of said amendment.

  • RE-WEIGHING PRODUCT Deliveries are subject to re- weighing at the point of destination by the Authorized User. If shrinkage occurs which exceeds that normally allowable in the trade, the Authorized User shall have the option to require delivery of the difference in quantity or to reduce the payment accordingly. Such option shall be exercised in writing by the Authorized User.

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

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