Application Lifecycle Management Sample Clauses

The Application Lifecycle Management clause defines the processes and responsibilities for managing an application's development, deployment, maintenance, and eventual retirement. It typically outlines the stages an application will go through, such as initial design, testing, updates, and decommissioning, and assigns roles for each phase to ensure accountability. This clause ensures that all parties understand how the application will be handled throughout its life, promoting consistency, minimizing risks, and supporting long-term operational stability.
Application Lifecycle Management. The Contractor shall ensure that any open source licenses which apply to components used in the solution confer no obligations upon an Authorized User, or that in the event of such obligation, an Authorized User is aware of and agrees to same.
View SourceView Similar (54)
Application Lifecycle Management. Feature SAP Enterprise Support, cloud editions SAP Preferred Success
View Source
Application Lifecycle Management. 3.3.1 Change management of released apps 3.3.2 Release management of released apps
View Source
Application Lifecycle Management. 16.9.2.1. The Contractor shall ensure that any open-source licenses that apply to components used in the solution confer no obligations upon OPWDD, or that in the event of such obligation, OPWDD is aware of and agrees to same. 16.9.2.2. All applications released by the Contractor to OPWDD shall be signed by a publicly trusted code signing certificate so that OPWDD may verify the authenticity and integrity of the release. This code signing certificate shall be rotated on at least an annual basis. 16.9.2.3. The Contractor shall ensure that all implementation services and/or guides comprehensively address security hardening for the solution. Such hardening shall include, but not be limited to, the disabling of unnecessary features based on the SoW and the implementation of a "least privilege" access model for all users and service accounts. 16.9.2.4. The Contractor shall implement processes to ensure that all changes to the solution: 16.9.2.5. The Contractor shall provide ample notice, and in no case less than six months, should the solution version used by OPWDD reach End of Life, such that it will no longer receive security updates to address vulnerabilities.
View Source

Related to Application Lifecycle Management

  • SITE MANAGEMENT We reserve the right, but not the obligation, to: (1) monitor the Site for violations of these Terms of Use; (2) take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms of Use, including without limitation, reporting such user to law enforcement authorities; (3) in our sole discretion and without limitation, refuse, restrict access to, limit the availability of, or disable (to the extent technologically feasible) any of your Contributions or any portion thereof; (4) in our sole discretion and without limitation, notice, or liability, to remove from the Site or otherwise disable all files and content that are excessive in size or are in any way burdensome to our systems; and (5) otherwise manage the Site in a manner designed to protect our rights and property and to facilitate the proper functioning of the Site.

  • Project Management Plan Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan and

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;

  • Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.