Software Engineering Optimization


What is ODC? sticky icon

What ODC brings to software engineering can be captured in two words: INSIGHT and SPEED. One leads to the other. But, they are not the only things that cause our eyes to light up and the organization hum with excitement. It's the power we gain through practical knowlege to affect the right engineering and process change that makes the difference.

Join us and learn about ODC. And we will begin a journey that is exciting, profitable, and immensely satisfying. We will help your organization apply ODC at the most appropriate level given your business priorities. We will train your staff, help you with your tools and processes, and empower your leadership with insight.

5 Differences between Classical and ODC Root Cause Analysis in Software sticky icon

Ram Chillarege, October 2013

Transcript of video clip.

"Hi. My name is Ram and what I'd like to share with you is a comparison between the classical root cause analysis and the ODC style of root cause analysis in software. What's different between the two? What are the advantages? And so forth. There are several differences, but there are five principle difference that I'd like to focus on".

ODC Tutorial at IEEE International Symposium on Software Reliability Engineering 2013, Pasadena CA

Topics:

  • ODC Concepts
  • ODC Classification and Information Extraction

  • How to gain 10x in Software Root Cause Analysis

  • How to tune up the Test Process using ODC
  • In-process Measurement and Prediction with ODC
  • Case Studies of ODC based Process Diagnosis
  • What is required to support ODC?
  • How does one plan an ODC Rollout ?

Target Audience:
This tutorial is for the practicing engineer and manager in software engineering. One must have a reasonable experience with the software development lifecycle, process improvement methods, tools, and practices. Knowledge of CMMi and Six Sigma are useful but not necessary. Typical roles are: Software engineering project leads, first and second line managers, those with delivery responsibility, QA responsibility, architects, program management, and service management. The SEPG department as a whole would also be interested.

Visualising the unobservable in software processes & products

ODC is a concept that enables software developers to derive in-process feedback by extracting semantics from data that is already tracked in most organizations. The data and analytics assists in visualizing a process that typically evades visibility.

This is analogous to the way magnetic resonance imaging (MRI) equipment aids a physician to have a rough idea of how a human being looks on the inside without knowing anything about the specific patient.

ODC creates a new order of capability to gain insight and clarity. It can be used to profile market segments, evaluate processes and tools, and factor the impact of legacy code. Security bugs can be profiled to understand their circumstances and characteristics. Today many of the networks in mobile telephone have used ODC to improve their reliability and availability. Similarly, ODC has helped manage the process and quality of software in diesel engine controllers that ply on our roads.

IPA SEC Special Seminar, Japan - Software Dependability

Theme: Approaches on realizing software dependability. Understanding development for highly dependable software. Workshop discussion.
Sponsor: IPA, Japan
Location: Bunkyo Green Court, Bunkyo-ku, Tokyo, Japan.
Date: December 5, 2011