We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Design Goals Sample Clauses

Design Goals. We seek a protocol with the following characteristics: — Security: No one other than the participants may have access to the generated key. — PFS: It must approach Perfect Forward Secrecy. — Privacy: It must preserve the privacy of the initiator and/or responder, insofar as possible. — Memory-DoS: It must resist memory exhaustion attacks. — Computation-DoS: It must resist CPU exhaustion attacks on the responder. — Availability: It must protect against easy to mount protocol-specific DoS at- tacks, for example, in a wireless environment where an attacker can observe everyone’s transmissions but cannot interfere with the transmitted packets themselves. — Efficiency: It must be efficient with respect to computation, bandwidth, and number of rounds. — Non-negotiated: It must avoid complex negotiations over capabilities. — Simplicity: The resulting protocol must be as simple as possible, within the constraints of the requirements. The Security requirement is obvious enough (we use the security model of Xxxxxxx and Xxxxxxxx [2001; 2002a]). The rest, however, require some discussion. The PFS property is perhaps the most controversial. (PFS is an attribute of encrypted communications allowing for a long-term key to be compromised without affecting the security of past session keys.) Rather than assert that “we must have PFS at all costs,” we treat the amount of forward secrecy as an engineering parameter that can be traded off against other necessary functions, such as efficiency or resistance to DoS attacks. In fact, this corresponds quite nicely to the reality of today’s Internet systems, where a compromise during the existence of a security association (SA) will reveal the plaintext of any ongoing transmissions. Our protocol has a forward secrecy interval; SAs are protected against compromises that occur outside of that interval. Specifically, we allow a party to reuse the same secret Diffie–Xxxxxxx (DH) exponents for multiple exchanges within a given time period; this may save a large number of costly modular exponentiations. The Privacy property means that the protocol must not reveal the identity of a participant to any unauthorized party, including an active attacker that attempts to act as the peer. Clearly, it is not possible for a protocol to pro- tect both the initator and the responder against an active attacker; one of the participants must always “go first.” In general, we believe that the most ap- propriate choice is to protect the initator, since t...
Design GoalsBased on existing literatures, a secure protocol should satisfy the following security requirements and functions:
Design Goals. Our two main design goals in this study were:
Design Goals. To design an AKA protocol, we need to consider three aspects at the same time, which are the network environment, security goals and privacy goals. This subsection will consider them one by one. IoT offers numerous advantages and services to the users. An important aspect of pervasive IoT devices is its constrained resources. So, various energy efficient lightweight mechanisms should be designed to store, process and transfer the data as per application requirements and with an optimized resource management. AKA-Goal 1: Lightweight property: Given the constraints of IoT environment, it is desirable that the AKA protocol should be lightweight in computation and communication. AKA protocol primitives should consume fewer resources without compromising the required level of security and privacy.
Design Goals. The Task Assistance Framework provides a simple, flexible, and configurable layer that demonstrates the following characteristics: • The Task Assistance Framework uses the Script as a model to provide visual assistance and navigation control to the User that is performing the Script. • The Script model is used as a structure on which many different types of Task Assistance can be built. Thus a new Task Assistance Framework can be added without affecting the Script model. • The Script description can be persisted in a number of forms (for example, flat file, relational database table, class with an instance variable holding onto a collection of Activities). It can be changed without changing the Task Assistance Framework that utilizes it. • The Task Assistance Framework implements a clear separation of responsibilities between the visual representation of the Script model and the Task Assistance services. This allows transparent additions of new forms of Task Assistance (visual "task lists," CueCards, "wizards"). • The Task Assistance Framework is an optional extension to the User Interface Control Framework.
Design Goals. The goal for the design review process will be for there to be two distinct facilities, with separately identifiable spaces, and functions. The Parties may wish to create common areas that can be jointly managed and/or made available to others as needed.
Design GoalsThe building shall create an icon for New York City and have a memorable presence on the skyline.

Related to Design Goals

  • Project Goals The schedule, budget, physical, technical and other objectives for the Project shall be defined.

  • Contract Goals A. For purposes of this procurement, OGS conducted a comprehensive search and determined that the Contract does not offer sufficient opportunities to set goals for participation by MWBEs as subcontractors, service providers, or suppliers to Contractor. Contractor is, however, encouraged to make every good faith effort to promote and assist the participation of MWBEs on this Contract for the provision of services and materials. The directory of New York State Certified MWBEs can be viewed at: xxxxx://xx.xxxxxxxxxxxxxx.xxx/FrontEnd/VendorSearchPublic.asp?TN=ny&XID=2528. Additionally, following Contract execution, Contractor is encouraged to contact the Division of Minority and Women’s Business Development ((000) 000-0000; (000) 000-0000; or (000) 000-0000) to discuss additional methods of maximizing participation by MWBEs on the Contract. B. Good Faith Efforts Pursuant to 5 NYCRR § 142.8, evidence of good faith efforts shall include, but not be limited to, the following: 1. A list of the general circulation, trade, and MWBE-oriented publications and dates of publications in which the Contractor solicited the participation of certified MWBEs as subcontractors/suppliers, copies of such solicitations, and any responses thereto. 2. A list of the certified MWBEs appearing in the Empire State Development (“ESD”) MWBE directory that were solicited for this Contract. Provide proof of dates or copies of the solicitations and copies of the responses made by the certified MWBEs. Describe specific reasons that responding certified MWBEs were not selected. 3. Descriptions of the Contract documents/plans/specifications made available to certified MWBEs by the Contractor when soliciting their participation and steps taken to structure the scope of work for the purpose of subcontracting with, or obtaining supplies from, certified MWBEs. 4. A description of the negotiations between the Contractor and certified MWBEs for the purposes of complying with the MWBE goals of this Contract. 5. Dates of any pre-bid, pre-award, or other meetings attended by Contractor, if any, scheduled by OGS with certified MWBEs whom OGS determined were capable of fulfilling the MWBE goals set in the Contract. 6. Other information deemed relevant to the request.

  • Design Criteria A/E shall prepare all work in accordance with the latest version of applicable County’s procedures, specifications, manuals, guidelines, standard drawings, and standard specifications. A/E shall prepare each Plans, Specifications, and Estimates (PS&E) package in a form suitable for letting through County’s construction contract bidding and awarding process.

  • Goals Goals define availability, performance and other objectives of Service provisioning and delivery. Goals do not include remedies and failure to meet any Service Goal does not entitle Customer to a Service credit.

  • Program Goals CalHFA MAC envisions that these monies would be used to complement other federal or lender programs designed specifically to stabilize communities by providing assistance to homeowners who have suffered a financial hardship and as a result are no longer financially able to afford their first-lien mortgage loan payments or their Property Expenses when associated with a Federal Housing Administration (“FHA”) Home Equity Conversion Mortgages (“HECM”) loan, only.

  • Acceptance Criteria The Services and Deliverables must meet the following acceptance criteria or the JBE may reject the applicable Services or Deliverables. The JBE may use the attached Acceptance and Signoff Form to notify Contractor of the acceptance or rejection of the Services and Deliverables. Contractor will not be paid for any rejected Services or Deliverables.

  • Design Development Phase 1.3.1 Based on the approved Schematic Design Documents, model(s) and any adjustments to the Program of Requirements, BIM Execution Plan or Amount Available for the Construction Contract authorized by the Owner, the Architect/Engineer shall prepare, for approval by the Owner and review by the Construction Manager, Design Development Documents derived from the model(s) in accordance with Owner’s written requirements to further define and finalize the size and character of the Project in accordance with the BIM Execution Plan, “Facility Design Guidelines” and any additional requirements set forth in Article 15. The Architect/Engineer shall review the Design Development documents as they are being modeled at intervals appropriate to the progress of the Project with the Owner and Construction Manager at the Project site or other location specified by Owner in the State of Texas. The Architect/Engineer shall utilize the model(s) to support the review process during Design Development. The Architect/Engineer shall allow the Construction Manager to utilize the information uploaded into Owner’s PMIS to assist the Construction Manager in fulfilling its responsibilities to the Owner. 1.3.2 As a part of Design Development Phase, Architect/Engineer shall accomplish model coordination, aggregation and “clash detection” to remove conflicts in design between systems, structures and components. Architect/Engineer shall utilize Owner’s PMIS to accomplish model coordination and collaborate with Construction Manager in the resolution of critical clashes identified by the Construction Manager. Architect/Engineer shall demonstrate and provide written assurance to Owner that conflicts/collisions between models have been resolved. 1.3.3 The Architect/Engineer shall review the Estimated Construction Cost prepared by the Construction Manager, and shall provide written comments. 1.3.4 Before proceeding into the Construction Document Phase, the Architect/Engineer shall obtain Owner’s written acceptance of the Design Development documents and approval of the mutually established Amount Available for the Construction Contract and schedule. 1.3.5 The Architect/Engineer shall prepare presentation materials including an animation derived from the model(s) as defined in “Facility Design Guidelines” at completion of Design Development and if so requested shall present same to the Board of Regents at a regular meeting where scheduled within the state. 1.3.6 The Architect/Engineer shall prepare preliminary recommended furniture layouts for all spaces where it is deemed important to substantiate the fulfillment of program space requirements, or to coordinate with specific architectural, mechanical and electrical elements. 1.3.7 Architect/Engineer shall assist the Owner, if requested, with seeking approval of the Project by the Texas Higher Education Coordinating Board (THECB). Such assistance shall include (i) the preparation of a listing of the rooms and square footages in the Project, and (ii) the preparation of project cost information, in accordance with THECB Guidelines. This information shall be provided at the completion of the Design Development Phase when requested by the Owner. The listing of rooms and square footages shall then be updated to reflect any changes occurring during construction and provided to the Owner at Substantial Completion. 1.3.8 At the completion of the Design Development Phase, or such other time as Owner may specify to Architect/Engineer, at Owner’s sole option and discretion, Owner will furnish Architect/Engineer with a Guaranteed Maximum Price proposal prepared by Construction Manager based upon the Design Development documents prepared by the Architect/Engineer and approved by the Owner. The Architect/Engineer shall assist the Owner and endeavor to further and advocate the Owner’s interests in Owner’s communications with the Construction Manager in an effort to develop a Guaranteed Maximum Price proposal acceptable to Owner, in Owner’s sole option and discretion. If the Owner does not accept the Construction Manager’s Guaranteed Maximum Price proposal, the Architect/Engineer shall participate with the Owner and Construction Manager in constructability reviews and shall revise the documents as necessary in order to reach an agreement. If the Construction Manager’s Guaranteed Maximum Price proposal exceeds the Schematic Design Phase Estimated Construction Cost prepared by, or otherwise accepted by the Construction Manager due to an increase in the scope of the Project caused by further development of the design documents by the Architect/Engineer to the extent that such could not be reasonably inferred by the Construction Manager from the Schematic Design documents, and Owner directs Architect/Engineer to revise the documents, the Architect/Engineer shall revise the documents at its own expense so that the Guaranteed Maximum Price proposal for constructing the Project shall not exceed the Owner’s Amount Available for the Construction Contract and any previously approved Estimated Construction Costs. If it is determined to be in the Owner’s best interest, instead of requiring the Architect/Engineer to revise the Drawings and Specifications, the Owner reserves the right to accept a Guaranteed Maximum Price proposal that exceeds the stipulated Amount Available for the Construction Contract. The Architect/Engineer shall analyze the final Guaranteed Maximum Price proposal document, together with its supporting assumptions, clarifications, and contingencies, and shall submit a detailed written analysis of the document to the Owner. Such analysis shall include, without limitation, reference to and explanation of any inaccurate or improper assumptions and clarifications. The A/E will not be required to make revisions to the documents at its own expense under the provisions of this paragraph if the Owner’s rejection of the Guaranteed Maximum Price proposal is not due to a failure of the A/E to provide the services otherwise required herein. 1.3.9 After the Guaranteed Maximum Price has been accepted, the Architect/Engineer shall incorporate necessary revisions into the Design Development documents. The A/E will not be required to make revisions to the documents at its own expense under the provisions of this paragraph if the revisions are required as the result of inaccurate assumptions and clarifications made in the development of the Guaranteed Maximum Price proposal that are not due to a failure of the A/E to provide the services otherwise required herein.

  • PERFORMANCE OBJECTIVES 4.1 The Performance Plan (Annexure A) sets out- 4.1.1 the performance objectives and targets that must be met by the Employee; and 4.1.2 the time frames within which those performance objectives and targets must be met. 4.2 The performance objectives and targets reflected in Annexure A are set by the Employer in consultation with the Employee and based on the Integrated Development Plan, Service Delivery and Budget Implementation Plan (SDBIP) and the Budget of the Employer, and shall include key objectives; key performance indicators; target dates and weightings. 4.2.1 The key objectives describe the main tasks that need to be done. 4.2.2 The key performance indicators provide the details of the evidence that must be provided to show that a key objective has been achieved. 4.2.3 The target dates describe the timeframe in which the work must be achieved. 4.2.4 The weightings show the relative importance of the key objectives to each other. 4.3 The Employee’s performance will, in addition, be measured in terms of contributions to the goals and strategies set out in the Employer’s Integrated Development Plan.

  • Goals & Objectives The purpose of this Agreement is to ensure that the proper elements and commitments are in place to provide consistent IT service support and delivery to the Customer by the Service Provider. The goal of this Agreement is to obtain mutual agreement for IT service provision between the Service Provider(s) and Customer(s). The objectives of this Agreement are to: • Provide clear reference to service ownership, accountability, roles and/or responsibilities. • Present a clear, concise and measurable description of service provision to the customer. • Match perceptions of expected service provision with actual service support & delivery.

  • Project Objectives 1.1 (Type the Project objectives)