Software Development Quality Control Report Sample Clauses

Software Development Quality Control Report. This document describes the status and performance of the quality control task with details on the availability and execution of unit, functional and compliance tests for the EMI components. This aggregated data is internally generated every month and reported to the EC every twelve months. [month 3]
AutoNDA by SimpleDocs
Software Development Quality Control Report. This document describes the status and performance of the quality control task with details on the availability and execution of unit, functional and compliance tests for the EMI components. This aggregated data is internally generated every month and reported to the EC every twelve months. [month 36] Schedule of relevant Milestones Milestone number 59 Milestone name Lead benefi- ciary number Delivery date from Annex I 60 Comments MS26 MJRA1.1 - Security Workshop 18 2 Organization of workshop on EMI security strategies and roadmap. MS27 MJRA1.2 - Agreement on common job submission and management methods 10 6 This milestone indicates an agreement in the consortium on which interfaces and protocols we use in order to enable computational job submission and management required across technologies. MS28 MJRA1.3 - Successful implementation of the common job submission and management methods 10 18 This milestone indicates that the computational job submission between different integrated compute technology components is successful and that these solutions can be used in the broader production E MS29 MJRA1.4 - Successful computational usage of emerging computing models 10 30 This milestone indicates a success in using emerging computing models (i.e. clouds) with EMI components. MS30 MJRA1.5 - Agreement on common security methods for data systems 6 5 This milestone indicates the agreement and definition of the common security model to be used in all data services to overcome the current incompatibilities. MS31 MJRA1.6 - File Catalogue common front-ends 1 15 This milestone indicates the availability of a standard interface to access the file catalogue, which simplifies the integration with user Milestone number 59 Milestone name Lead benefi- ciary number Delivery date from Annex I 60 Comments frameworks, portals and third party components. MS32 MJRA1.7 - First implementations of POSIX compliance and HTTP support 1 24 This milestone indicates the successful implementation of initial POSIX support for all SRM-based systems and full support for HTTP(S) protocol. MS33 MJRA1.8 - Full standard compliance and POSIX support 1 30 This milestone refers to availability of fully compliant data services and full support for POSIX. MS34 MJRA1.9 - AAI requirements of DCIs 18 7 This milestone surveys AAI needs in DCIs in order to pick the most relevant ones that have to be supported by the EMI common security infrastructure. MS35 MJRA1.10 - EMI Security Workshop 18 17 Organization...

Related to Software Development Quality Control Report

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Technology Research Analyst Job# 1810 General Characteristics

  • 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. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • COMMERCIAL COMPUTER SOFTWARE If performance involves acquisition of existing computer software, the following Company Exhibit is incorporated by reference: CCS Commercial Computer Software License (Company – July 2010).

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK

  • Project Planning GOVERNMENTAL APPROVALS; ENVIRONMENTAL COMPLIANCE; PUBLIC INFORMATION 30 4.1 Planning and Engineering Activities 30 4.2 Site Conditions 30 4.3 Governmental Approvals 30 4.4 Environmental Compliance 34 4.5 Community Outreach and Public Information 35

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives. C.1. <Title> Deliverable 1

  • Commercialization Reports Throughout the term of this Agreement and during the Sell-Off Period, and within thirty (30) days of December 31st of each year, Company will deliver to University written reports of Company’s and Sublicensees’ efforts and plans to develop and commercialize the innovations covered by the Licensed Rights and to make and sell Licensed Products. Company will have no obligation to prepare commercialization reports in years where (a) Company delivers to University a written Sales Report with active sales, and (b) Company has fulfilled all Performance Milestones. In relation to each of the Performance Milestones each commercialization report will include sufficient information to demonstrate achievement of those Performance Milestones and will set out timeframes and plans for achieving those Performance Milestones which have not yet been met.

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