Systems Development. Systems Development" shall mean the systems development and integration matters contemplated in the Systems Integration Agreement.
Systems Development. Service Provider will identify and develop an Idaho based and state compliant school information system to be used in connection with the administration and reporting system for the School. This includes, but is not limited to, accounting documentation filing systems, student records systems, computer systems, and telecommunications services. TERM OF AGREEMENT
Systems Development. 3 4.1 Development of Joint Date Base...................................... 3 4.2
Systems Development. (a) Priceline, with the advice and guidance of Alliance, shall develop the required screen flows and customer interfaces needed to capture consumer data, obtain an automated underwriting decision and deliver this decision to the consumer. Priceline will structure the screen flow and marketing efforts with the intent of generating closed loan volume in accordance with the projected closed loan volumes agreed to by the Parties from time to time; provided, however, that by performing its obligations pursuant to this Section 6.3(a), Priceline does not make any guaranty that the projected closed loan volumes agreed to by the Parties from time to time will be achieved.
Systems Development. Following the execution of this Agreement, Vitex shall continue to work diligently and use its best efforts to (i) develop, including conducting research and development and clinical work, and obtain Regulatory Approval for a System or Systems, and (ii) thereafter, market, sell and distribute, or cause to be marketed, sold and distributed Systems for the Inactivation of Red Blood Cells or Platelets. From the Date of this Agreement and unless and until Pall exercises its right to reacquire marketing rights pursuant to the terms of Section 3.01(c) below, Vitex shall be solely responsible for all aspects relating to the production, manufacturing, assembly, sterilization, packaging, warehousing, marketing and distribution of Systems and Pall shall have no further rights or obligations with respect to the Systems or such activities, except as otherwise expressly provided in this Agreement. All activities of Vitex set forth in this Section 3.01 shall be conducted in compliance with all pertinent regulatory requirements of the FDA and other relevant Governmental Authorities.
Systems Development. As requested by the Chief Executive Officer, in consultation with the Company's programming and systems engineers and/or accounting and finance personnel, assist with the design and development of data, accounting and financial systems that will support the sale, servicing, and financial and regulatory reporting as related to new products and services.
Systems Development. It is proposed that the PATHS system is developed via an agile, user-centred model of systems development, in line with the majority of recent projects in the area of digital cultural heritage (see, for example: Europeana, EuropeanaConnect, Multimatch, and others). Broadly, what this entails is an iterative process of requirements gathering, systems development, implementation (and/or prototyping), testing and evaluation, with test and evaluation results driving refinements and successive prototypes of the system (see Multimatch, 2006 for a comprehensive discussion). In the case of PATHS, there are two planned prototypes; one each in the second and third years of the project. The novel combination of digital library exploration and path-creation functionality, matched with adaptivity via personalisation and recommendation, means that the PATHS system is designed to extend the state-of-the-art in information access in cultural heritage, and there is therefore little available for direct comparison at the outset. At this initial phase of the project then, we are tasked with gathering requirements for the first prototype, ostensibly working from the PATHS vision (summarised in Section 1.2) as the main framework for identifying users and determining the scope for requirements elicitation. This means that there is undoubtedly a strong conceptual element to the first phase of user requirements gathering, but as we progress onto the second prototype this work will be focussed on evaluating users‟ interactions with and responses to a working system (PATHS first prototype), and we will therefore have more concrete results based upon actual user experience. In the remainder of Section 2 we will describe how we have approached the initial requirements gathering for the PATHS project, and outline the specific methods we have used. Further details about the actual design and implementation of the selected methods are presented in Sections 3-5 and 7.
Systems Development. (a) Company ensures that source code and similar configuration changes are properly authorized and tracked via standard source code management practices.
(b) Company uses a documented, repeatable practice for testing, requesting, approving, and implementing system changes.
(c) Company performs system, user, and acceptance testing of content and infrastructure for the BMC hosted applications in a development and testing environment separately from production.
(d) Confidential BMC test data are adequately protected, controlled and removed from environments used for development and testing.
(e) Company supervises and monitors outsourced software development. Third parties meet the same code management practices applied by Company to protect infrastructure and applications used to host BMC Data or provide Services to BMC.
(f) Company ensures that all code deployed in support of a BMC application or managed service is free of back doors, malware, or any other inappropriate content.
Systems Development. 16.1 The Parties agree that they will involve and work closely with the WCE Systems Division in relation to any proposed developments in the AG Group's Corporate Systems.
Systems Development. The Supplier must ensure all systems development is carried out and documented to industry accepted standards. The Supplier must make available any system documentation for inspection by DfE, including documentation on the progress of development. The Supplier must provide and agree a system development strategy at the start of each call-off to cover all system developments for that call-off. In addition the Supplier must agree with DfE the changes that are to be made to any system before any development work is carried out.
