System Development Lifecycle Sample Clauses

System Development Lifecycle. AGENCY2 shall manage the information system using an SDLC that incorporates information security considerations and integrates the agency information security risk management process into SDLC activities. AGENCY2 shall define and document information security roles and responsibilities throughout the SDLC and identify individuals having information security roles and responsibilities

System Development Lifecycle. Manage the Provider Systems incorporating information security and privacy considerations; define and document information security and privacy roles and responsibilities throughout the system development life cycle; and identify individuals having information security and privacy roles and responsibilities; and integrate the organizational information security and privacy risk management process into system development life cycle activities.

System Development Lifecycle. Callback Some batch processes require callback in the event that a batch process does not run to completion and requires attention to resolve. Unless otherwise noted, WaTech monitors these systems and if intervention is required, will execute the appropriate callback as outlined in their service agreements. The following systems require callback: BPS: L&I’s Operations supports BPS system processing M-F 6am-3pm. Otherwise, WaTech monitors processing. EAS: System 14, System 15, System 22, System 21, System RR, and System RA – Xxx Xxxxxx (NEWW235), Xxxx Xxxxxxxxxx (SCHI235) MIPS: System 33, System 34, and any other MIPS-related processes – Xxxxxxx Xxxxxx (TURS235) Developer Preparedness Add stuff here Agreement Review Process An initial review of this agreement will be conducted three months from the effective date with all parties. Subsequent reviews will be performed annually. A representative of any of the parties may initiate a review at any time by submitting a written request for review of the Agreement to the Service Desk representative, who will arrange a meeting of the parties. In the absence of the completion of a review, the current Agreement will remain in effect. The Service Desk representative will incorporate revisions into the Agreement if all parties agree to the proposed changes. Initial Review: October 2016 Next Review: October 2017 Term and Review Cycle This Agreement is valid from March 1, 2017 and remains in effect until revoked or modified. OLA Change Review Triggers When one of the following occurs or is anticipated contact Information Services Applications & Data Management Office to initiate the review process: Any change to availability of any component (see Technology above). The addition or removal of a role, or changes to role definitions. Technical or Business Owner changes Completion or changes to the service including addition and removal of components and dependent systems/technology. Consistent or regular outages causing business interruption. Agreement Acceptance The project phase for MPN will end on June 30, 2013. At this point, any changes to the MPN applications will need to be done through the appropriate IS Core Teams. At project closure, all knowledge transfer will be completed and TFS code-base, artifacts, and environments will be turned over to the appropriate IS Core teams.