Software engineering, quality assurance and certification Sample Clauses

Software engineering, quality assurance and certification. Most of the software development activities in the grid domain in Europe in the past several years have relied on projects of a very distributed nature, typical of major open source initiatives, where software developers were tasked with developing services and components starting from minimal specifications rapidly changing and evolving in time as the user requirements became clearer and better understood. By their nature, most of these projects employ developers with different degrees of expertise and different technical and cultural backgrounds. Although all grid and distributed middleware development share a strong basis of common principles like the adoption of a Service Oriented Architecture, different projects and even different Institutes within the same project usually adopt software development technologies of their own choice and in some cases develop new processes and methods. Several projects in the past years have devised collaboration processes and techniques suitable for heavily distributed software engineering activities. The first EGEE project in 2004-2006 had a central integration and testing team responsible to define overall guidelines and deploy and maintain common continuous integration tools (originally based on CruiseControl). At the end of EGEE I, the ETICS project was created with the specific objective of defining, implementing and maintaining a collaborative distributed environment for the continuous integration and testing of the software developed by projects like EGEE II (gLite), DILIGENT, OMII-Europe, 18 Open Grid Forum (OGF). Web site: xxxx://xxx.xxx.xxx 19 OASIS Consortium. Web site: xxxx://xxx.xxxxx-xxxx.xxx D4Science, UNICORE, EDGES and others. The ETICS project and its current follow-up, ETICS 2, have established an infrastructure and developed tools that allow developers using different programming languages and different engineering technologies to manage large software system with common APIs, web-based configuration and management tools and share and preserve the software they produce. Currently the use of continuous integration and testing methods is adopted in many cases as an additional activity on top of the actual software development activities, but it is not always considered an integral part of the development process driving the release management criteria. The major issues preventing a more correct adoption of agile methodologies and the use of rapid prototyping methodologies based on continuous integrati...
AutoNDA by SimpleDocs

Related to Software engineering, quality assurance and certification

  • Quality Assurance The parties endorse the underlying principles of the Company’s Quality Management System, which seeks to ensure that its services are provided in a manner which best conforms to the requirements of the contract with its customer. This requires the Company to establish and maintain, implement, train and continuously improve its procedures and processes, and the employees to follow the procedures, document their compliance and participate in the improvement process. In particular, this will require employees to regularly and reliably fill out documentation and checklists to signify that work has been carried out in accordance with the customer’s specific requirements. Where necessary, training will be provided in these activities.

  • Quality Assurance Plan The contractor shall develop and submit to NMFS a contractor Quality Assurance Plan, as referenced in Section F.5.3, which details how the contractor will ensure effectiveness and efficiency of collection efforts as well as the quality of data collected by its At-Sea Monitors. The contractor shall further establish, implement, and maintain a Quality Assurance Management program to ensure consistent quality of all work products and services performed under this contract.

  • COUNTY’S QUALITY ASSURANCE PLAN The County or its agent will evaluate the Contractor’s performance under this Contract on not less than an annual basis. Such evaluation will include assessing the Contractor’s compliance with all Contract terms and conditions and performance standards. Contractor deficiencies which the County determines are severe or continuing and that may place performance of the Contract in jeopardy if not corrected will be reported to the Board of Supervisors. The report will include improvement/corrective action measures taken by the County and the Contractor. If improvement does not occur consistent with the corrective action measures, the County may terminate this Contract or impose other penalties as specified in this Contract.

  • Quality Assurance/Quality Control Contractor shall establish and maintain a quality assurance/quality control program which shall include procedures for continuous control of all construction and comprehensive inspection and testing of all items of Work, including any Work performed by Subcontractors, so as to ensure complete conformance to the Contract with respect to materials, workmanship, construction, finish, functional performance, and identification. The program established by Contractor shall comply with any quality assurance/quality control requirements incorporated in the Contract.

  • Quality Assurance Program An employee shall be entitled to leave of absence without loss of earnings from her or his regularly scheduled working hours for the purpose of writing examinations required by the College of Nurses of Ontario arising out of the Quality Assurance Program.

  • CONSTRUCTION AND RELATED ENGINEERING SERVICES A. General construction work for buildings (CPC 512) 1) Unbound* 2) None 3) None 1) Unbound* 2) None 3) None

  • COMPLIANCE AND CERTIFICATION 25.1 Each Party shall comply at its own expense with all Applicable Laws that relate to that Party’s obligations to the other Party under this Agreement. Nothing in this Agreement shall be construed as requiring or permitting either Party to contravene any mandatory requirement of Applicable Law.

  • Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.

  • Evaluation, Testing, and Monitoring 1. The System Agency may review, test, evaluate and monitor Grantee’s Products and services, as well as associated documentation and technical support for compliance with the Accessibility Standards. Review, testing, evaluation and monitoring may be conducted before and after the award of a contract. Testing and monitoring may include user acceptance testing. Neither the review, testing (including acceptance testing), evaluation or monitoring of any Product or service, nor the absence of review, testing, evaluation or monitoring, will result in a waiver of the State’s right to contest the Grantee’s assertion of compliance with the Accessibility Standards.

  • Drug-Free Workplace Certification As required by Executive Order No. 90-5 dated April 12, 1990, issued by the Governor of Indiana, the Contractor hereby covenants and agrees to make a good faith effort to provide and maintain a drug-free workplace. The Contractor will give written notice to the State within ten (10) days after receiving actual notice that the Contractor, or an employee of the Contractor in the State of Indiana, has been convicted of a criminal drug violation occurring in the workplace. False certification or violation of this certification may result in sanctions including, but not limited to, suspension of contract payments, termination of this Contract and/or debarment of contracting opportunities with the State for up to three (3) years. In addition to the provisions of the above paragraph, if the total amount set forth in this Contract is in excess of $25,000.00, the Contractor certifies and agrees that it will provide a drug-free workplace by:

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