Single Point Failure: The case study of RBS CS/SE 6361 FINAL TERM PAPER Shahed Shuman.

Slides:



Advertisements
Similar presentations
3.02H Publishing a Website 3.02 Develop webpages..
Advertisements

Test process essentials Riitta Viitamäki,
Single Point Failure: The case study of RBS CS/SE 6361 Advanced Requirements Engineering Shahed Shuman.
A A A N C N U I N F O R M A T I O N T E C H N O L O G Y : IT OPERATIONS 1 Problem Management Jim Heronime, Manager, ITSM Program Tanya Friehauf-Dungca,
Software Delivery. Software Delivery Management  Managing Requirements and Changes  Managing Resources  Managing Configuration  Managing Defects 
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa INSTALLATIONS Software installation accommodates software.
Information systems Integrity Protection. Facts on fraud  UK computer fraud 400 Million £  on companies  avg case £  France.
Software Configuration Management
Chapter 10 Systems Operation, Support, and Security
CS 501: Software Engineering Fall 2000 Lecture 14 System Architecture I Data Intensive Systems.
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Managing the Information Technology Resource Jerry N. Luftman
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
What Happens after You Sign with Missouri Health Information Technology Assistance Center?
Implementation/Acceptance Testing / 1 Implementation and Acceptance Testing Physical Implementation Criteria: 1. Data availability 2. Data reliability.
Oracle Database Administration. Rana Almurshed 2 course objective After completing this course you should be able to: install, create and administrate.
Stoimen Stoimenov QA Engineer QA Engineer SitefinityLeads,SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
System Implementation
THE SYSTEMS LIFE CYCLE ANALYSE DESIGN IMPLEMENT MAINTENANCE IDENTIFY/INVESTIGATE.
Air Traffic Control Software System Failure Case Study – As-is Scenario Presented by Stanley Dam For SE 6361 Advanced Requirement Engineering 10/25/2013.
LCG Milestones for Deployment, Fabric, & Grid Technology Ian Bird LCG Deployment Area Manager PEB 3-Dec-2002.
Lesson 14: Installing and Uninstalling Programs how to install a new program what to do if the new program doesn’t work how to uninstall a program © CCI.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
ERP. What is ERP?  ERP stands for: Enterprise Resource Planning systems  This is what it does: attempts to integrate all data and processes of an organization.
A Review by Raghu Rangan WPI CS525 September 19, 2012 An Early Warning System Based on Reputation for Energy Control Systems.
Information Systems Security Operational Control for Information Security.
A networking group dedicated to improving infrastructure, workflows, and support across the Entertainment Industry.
ITPD PRODUCTION SUPPORT PROCESS OCTOBER 8, /23/2015 Guiding Principles 1.Resolve production issues in a timely and effective manner 2.Manage.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
A Networked Machine Management System 16, 1999.
Chapter 1 The Product. 2 Product  What is it?  Who does it?  Why is it important?  How to ensure it be done right?
Week 3 Outline Post-Mortem By: Jamaral Johnson. 2 After Actions Review In this presentation I will do my best to highlight what went wrong. This is just.
Service Level Agreements Service Level Statements NO YES The process of negotiating and defining the levels of user service (service levels) required.
Texas SET Version 3.0 Production Implementation Plan.
 Load balancing is the process of distributing a workload evenly throughout a group or cluster of computers to maximize throughput.  This means that.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Program Development Cycle
Assoc. Prof. Dr. Ahmet Turan ÖZCERİT.  System and Software  System Engineering  Software Engineering  Software Engineering Standards  Software Development.
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
Objectives Understand Corrective, Perfective and Preventive maintenance Discuss the general concepts of software configuration management.
Chapter 12 The Network Development Life Cycle
High Availability Technologies for Tier2 Services June 16 th 2006 Tim Bell CERN IT/FIO/TSI.
Automated tests CustomWare.Net. Goals Quality Finding problems before delivering Stability Upgrade projects Downgrade Refactoring Deacreasing of manual.
Data Management and Troubleshooting CareTracker Forum 2003 Brad Miller Technical Support B.J. Boyle Implementation Consultant.
Information Technology Service Availability Metrics March 2008.
Information Technology Update Aaron Smallwood Manager, IT Business & Customer Services.
Staff Assessment Technology Services Department Palmyra Area School District.
 Software reliability is the probability that software will work properly in a specified environment and for a given amount of time. Using the following.
ow some steps given below.
Software Configuration Management
Speaker’s Name, SAP Month 00, 2017
Oracle Database Administration
What, When, Why, Where and How SCC maintains your Oracle database
If you are not able to implement the solutions offered by tutorial both written and video, you can contact quicken customer support team. You can get plenty.
Software Engineering (CSI 321)
Some Important Techniques For Regression Testing That You Must Know.
Garmin outdoor maps Support Call for
Get ATM Replenishment & Maintenance Services from VIP 360.
Brother Printer Technical Support Number
Across the entire value chain
Amendment Invoice Task Force Progress Report
Software Testing and Maintenance Maintenance and Evolution Overview
Amendment Invoice Task Force Progress Report
Amendment Invoice Task Force Progress Report
Amendment Invoice Task Force Progress Report
Amendment Invoice Task Force Progress Report
The Troubleshooting theory
Capitalize on Your Business’s Technology
OU BATTLECARD: WebLogic Server 12c
Presentation transcript:

Single Point Failure: The case study of RBS CS/SE 6361 FINAL TERM PAPER Shahed Shuman

What was the issue? On the day of June The RBS payment processing system suddenly stopped, None of the overnight job running the Bank balance calculation happend, all of the transactions processing were disrupted, ATM machines were not operational, online bank balance was showing incorrect balance! The day before the Incident, an incorrect upgrade was Installed to the RBS CA-7 Software, CA-7 is a job scheduling / workflow automation software package sold by CA technologies. Resulting in total stoppage of Payment processing jobs. RBS moved the CA7 maintenance and support to offshore.RBS also cut down their onshore CA-7 resources As a result,no CA-7 expert was left in RBS who were experienced enough to diagnose the issue and revert the corrupted updates

Root cause 1.Proper CA-7 update requirements were not followed by the offshore team. 2.Systems upgrade happened on a weekday without proper testing, it caused major business disruption 3.The issue was not found until it was already in the RBS production server. 4.RBS didn’t have any requirement available to tackle these kinds of technical emergency 5.RBS did not have resources to implement any corrective measure 6.The delay to implement the fix and subsequent media coverage caused the issue to be longer as CA technologies took longer time to avoid another blunder. the error was made when backing out of an upgrade from CA-7 v11.1 to v11.3. The CA-7 upgrade took place at the weekend of 16/17th June and a problem was noticed on Monday which prompted a back-out from the upgrade on Tuesday night. In the back-out, an "inexperienced operator" made the wrong move and the day's data was wiped from the system. This created the backlog(

Problem Interdependency Graph

Solutions – FRNFR R1)Programmer must follow the update procedure who shall keep track if the proper procedure was followed R2)New Programmers will not make any updates to mission critical systems Who maintains and validates the programmer capabilities R3) A response team should have fixed this issue How fast it must be done? R4) There must be backups to mission critical systems How will the Reliability, security and performance must be maintained

Requirements Prioritization AHP R1R2R3R4 R111/342 R23135 R31/41/314 R41/21/51/41 R1R2R3R4 R R R R Normalized Requirement Priority SUMSUM/4 R R R R

Questions?