SOFTWARE STRUCTURE Sample Clauses

SOFTWARE STRUCTURE. The DMS-100 family software has a highly modular structure with narrow, well-defined interfaces among modules. The module interfaces are designed around basic operating system functions (scheduling tasks or store allocations), the basic call processing functions, the features required and the hardware supported. 29 Basic modules, held in a common library, can be classified into several layers that are used to build up an office. The main layers are the operating system, the call processing utilities, and the call processing options. The call processing options do not provide direct interfaces for other modules to call. They are specifically designed with no references to them, so that they can be independently selected as options for any given office. When loaded, they make themselves known to the rest of the System. The term "agency" is used for these call processing options. Typically an agency deals with a specific set of call processing features and the terminals (lines or trunks) to which they apply. The modular design concept of the DMS-MSC enables hardware components to be extended to meet future requirements. In the event of traffic growth, the processing capability of the MSC can easily be expanded via faster CPU and memory extensions. Extensions can be classified as either core or peripheral interface. Core extensions cover processor, memory and the switching network.
Sample 1Sample 2
AutoNDA by SimpleDocs
SOFTWARE STRUCTURE. Gigamon follows a best practice implementation for code identification and revision control for field deployments. Gigamon uses a standard W.X.Y.Z. for all of its appliance based products. • W – 1st digit in software naming convention represents code releases containing major architectural and functional changes • X – 2nd digit in software naming convention that represents a feature release • Y – 3rd digit in software naming convention that represents a maintenance release change • Z – 4th digit in the software naming convention that represents hot patch releases associated to maintenance release • Examples:
Sample 1

Related to SOFTWARE STRUCTURE

  • Software Modifications Company may request that BNYM, at Company’s expense, develop modifications to the software constituting a part of the Licensed System that BNYM generally makes available to customers for modification (“Software”) that are required to adapt the Software for Company’s unique business requirements. Such requests, containing the material features and functionalities of all such modifications in reasonable detail, will be submitted by Company in writing to BNYM in accordance with the applicable, commercially reasonable procedures maintained by BNYM at the time of the request. Company shall be solely responsible for preparing, reviewing and verifying the accuracy and completeness of the business specifications and requirements relied upon by BNYM to estimate, design and develop such modifications to the Software. BNYM shall have no obligation to develop modifications to the Licensed System requested by Company, but may in its discretion agree to develop requested modifications which it, in its sole discretion, reasonably determines it can accomplish with existing resources or with readily obtainable resources without disruption of normal business operations provided Company agrees at such time in writing to pay all costs and expenses, including out-of-pocket expenses, associated with the customized modification. BNYM shall be obligated to develop modifications under this Section 2.16 only upon the execution of and in accordance with a writing containing, to BNYM’s reasonable satisfaction, all necessary business and technical terms, specifications and requirements for the modification as determined by BNYM in its sole judgment (“Customization Order”) and Company’s agreement to pay all costs and expenses, including out-of-pocket expenses, associated with the customized modification (“Customization Fee Agreement”). All modifications developed and incorporated into the Licensed System pursuant to a Customization Order are referred to herein as “Company Modifications”. BNYM may make Company Modifications available to all users of the Licensed System, including BNYM, at any time after implementation of the particular Company Modification and any entitlement of Company to reimbursement on account of such action must be contained in the Customization Fee Agreement.

  • Open Source Software The Software product may include certain open source components that are subject to open source licenses (“Open Source Software”), in which case, the embedded Open Source Software is owned by a third party. The Open Source Software is not subject to the terms and conditions of this XXXX. Instead, each item of Open Source Software is licensed under its applicable license terms which accompanies such Open Source Software. Nothing in this XXXX limits your rights under, nor grants you rights that supersede, the terms and conditions of any applicable license terms for the Open Source Software. Any fees charged by GC in connection with the SOFTWARE, do not apply to the Open Source Software for which fees may not be charged under the applicable license terms. The terms and conditions of the applicable license for the Open Source Software are available on the LICENSE.txt file, which is provided with the SOFTWARE.

  • Company Software “Company Software” shall mean any software (including software development tools and software embedded in hardware devices, and all updates, upgrades, releases, enhancements and bug fixes) owned, developed (or currently being developed), used, marketed, distributed, licensed or sold by an Acquired Corporation at any time (other than non-customized third-party software that is not incorporated into any Company Product and is licensed to an Acquired Corporation solely in object code form and solely for internal use on a non-exclusive basis).

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • Software License Subject to the terms of this Agreement, Viasat grants to you a personal, non-exclusive, non-assignable and non-transferable license to use and display the software provided by or on behalf of Viasat (including any updates) only for the purpose of accessing the Service ("Software") on any computer(s) on which you are the primary user or which you are authorized to use. Our Privacy Policies provide important information about the Software applications we utilize. Please read the terms very carefully, as they contain important disclosures about the use and security of data transmitted to and from your computer. Unauthorized copying of the Software, including, without limitation, software that has been modified, merged or included with the Software, or the written materials associated therewith, is expressly forbidden. You may not sublicense, assign, or transfer this license or the Software except as permitted in writing by Viasat. Any attempt to sublicense, assign or transfer any of the rights, duties or obligations under this license is void and may result in termination by Viasat of this Agreement and the license. You agree that you shall not copy or duplicate or permit anyone else to copy or duplicate any part of the Software, or create or attempt to create, or permit others to create or attempt to create, by reverse engineering or otherwise, the source programs or any part thereof from the object programs or from other information made available under this Agreement.

  • Software Title and ownership to Existing Software Product(s) delivered by Contractor under the Contract that is normally commercially distributed on a license basis by the Contractor or other independent software vendor proprietary owner (“Existing Licensed Product”), embedded in the Custom Products, shall remain with Contractor or the proprietary owner of other independent software vendor(s) (ISV). Effective upon acceptance, such Product shall be licensed to Authorized User in accordance with the Contractor or ISV owner’s standard license agreement, provided, however, that such standard license, must, at a minimum: (a) grant Authorized User a non-exclusive, perpetual license to use, execute, reproduce, display, perform, adapt (unless Contractor advises Authorized User as part of Contractor’s proposal that adaptation will violate existing agreements or statutes and Contractor demonstrates such to the Authorized User’s satisfaction) and distribute Existing Licensed Product to the Authorized User up to the license capacity stated in the Purchase Order or work order with all license rights necessary to fully effect the general business purpose(s) stated in the Bid or Authorized User’s Purchase Order or work order, including the financing assignment rights set forth in paragraph (c) below; and (b) recognize the State of New York as the licensee where the Authorized User is a state agency, department, board, commission, office or institution. Where these rights are not otherwise covered by the ISV’s owner’s standard license agreement, the Contractor shall be responsible for obtaining these rights at its sole cost and expense. The Authorized User shall reproduce all copyright notices and any other legend of ownership on any copies authorized under this clause. Open source software is developed independently of Contractor and may be governed by a separate license (“open source software”). If the open source software is governed by a separate License and provided under this Contract, Contractor shall provide a copy of that license in the applicable Documentation and the Authorized User's license rights and obligations with respect to that open source software shall be defined by those separate license terms and subject to the conditions, if any, therein. Nothing in this Contract shall restrict, limit, or otherwise affect any rights or obligations the Authorized User may have, or conditions to which the Authorized User may be subject, under such separate open source license terms.

  • Computer Software The Grantee certifies that it has appropriate systems and controls in place to ensure that state funds will not be used in the performance of this Grant Agreement for the acquisition, operation, or maintenance of computer software in violation of copyright laws.

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times.

  • Software Support During the Term, Seller shall use commercially reasonable efforts to provide all Software updates and qualified Software upgrades in accordance with the terms of the Service Contract as such materials become commercially available for distribution. Purchaser’s use of all Software, updates, and upgrades of Software shall be subject to this Agreement, the Original Terms, and the applicable XXXX.

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