Scribd
Upload
73 views

RCA List

This document lists 23 root causes for issues in a system. The root causes include environmental issues, configuration and data issues, deployment errors, developer errors, testing issues, browser compatibility problems, system limitations, and issues with master data, mailboxes, milestones, reports, design, missing implementations, operations, intended system behavior, Actuate servers, unknown causes, non-reproducible issues, and legacy code. The root causes cover a wide range of potential issues that could arise in software systems, including issues related to deployments, configurations, data, testing, designs, implementations, operations, and legacy code.

Uploaded by

Akash Srivastava
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
73 views

RCA List

This document lists 23 root causes for issues in a system. The root causes include environmental issues, configuration and data issues, deployment errors, developer errors, testing issues, browser compatibility problems, system limitations, and issues with master data, mailboxes, milestones, reports, design, missing implementations, operations, intended system behavior, Actuate servers, unknown causes, non-reproducible issues, and legacy code. The root causes cover a wide range of potential issues that could arise in software systems, including issues related to deployments, configurations, data, testing, designs, implementations, operations, and legacy code.

Uploaded by

Akash Srivastava
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Changepoint RCA

S.
No.
1.

Root Cause

Description

Environmental Issue

2.

4.

Configuration Migration
Issue
Configuration Setup
Issue
Data Issue

Anything related with the environment like server down or deployment


going on.
When you find that some template/instance got missed during
deployment
If configuration setup is wrong

5.
6.

Database Issue
Deployment Issue

7.

Duplicate Issue

3.

8.

Developer Error

9.

Testing Issue

10.

Browser Compatibility
Issue
System Limitation

11.

12.

13.

Master Data Setup


Issue
Mailbox Setup Issue

14.
15.
16.
17.

Milestone Setup Issue


Report Setup Issue
Design Error
Missing Implementation

18.

Operations Issue/User
Error
Working as Designed
Actuate Server Issue
Unknown Issue
Not Reproducible
Legacy Code

19.
20.
21.
22.
23.

Any other data related issue. It is applicable to transaction data only.


Like shipment, milestone instance, MTI are not available.
Transaction log is full, Too slow, invalid database restore etc
If deployment team missed something. Like recently, we found that
some of the objects were not deployed in Prod support, while those
were available in production
If a ticket is a duplicate of another ticket. Put more details in the
resolution tab (e.g. other ticket number)
If there was a recent change in one of the functionality,
but because of the lack of impact analysis this area was missed out
and cause this ticket.
If the fix we did is not working for another set of data
If initiator has attached a design document, which was supposed to
be implemented, but functionality doesnt exist.
When you find that it is the result of another fix, we did
E.g. one page is too slow, getting timeout during peak time etc/Unit
testing/Integration testing issue. It will also cover those production
issues that could be caught during testing.
Because we are now supporting multiple browsers, we can get issue that
works in one browser but not in other.
Issue raised by user that cannot be implemented or something that is
infra or framework limitation. E.g. if HONDA drops a multiple GB
demand file and system fails with memory overflow and halts the eden
service.
If the master data is not setup properly. like ODPath, Part, entity
If something is related with mailbox setup. Like mailbox location was not
enabled etc.
Milestone was not setup properly.
Anything related with report setup.
If the issue was due to a gap in original design.
Issue came due the implementation was missing even it was mentioned in
the design document.
Operations/User is not aware about test case and logged the issue due
to bad test case.
If user has reported a problem, but that is system behaviour.
If report issue is because of the actuate server issue
If we do not have any explanation about an issue.
If the issue is not reproducible.
Old code which was never tested but now user is using the functionality
and reported some issue.

Changepoint RCA

You might also like