Industry Workgroup

Executive Summary

This year we created an Industry Workgroup drawing representatives from across industry segments. Each of the companies was approached for a senior person to represent the company’s interest and be a champion within the company. These ~ 20 major software companies represent a few hundred thousand software engineers in India. As we build on the success of ISSRE workshops in recent years, we also need help to address the faltering Tutorials and Tools Fair programs. This process is new to ISSRE and will help us develop a more relevant program. The objectvies of this meeting were:

1. Attract practice contributions from the local areas
2. Define workshops that are most relevant
3. Help identify tutorial topics most needed
4. Examine the possibility of a tools fair
5. Identify initiatives that provide value to the community

26 items were identified by the team. These are listed in the Table below, and then mapped into Workshops, Tutorials, Panels and Papers. The tutorial needs were identified by this group, which for the first time in ISSRE helps us gain insight into market demand. This can hopefully change our tutorial issues from a demand generation problem into an instructor staffing problem. These workshops and tutorials still need to be developed and the ownership assigned. We will do this soon after we include input from the worldwide community. We will post these findings on the web and advertise through our mail list to remind the community to submit their inputs. We then need to narrow down the selections and get them owned and executed. We have enrolled a few past ISSRE workshop organizers to help new organizers with their knowledge and experience.

The recommendations of the Industry Workgroup have been posted on our bulletin board and are open to comment by the community. These area available at: under the Workshops and Tutorials forums.

The idea of a Tools Fair had good reception. This task has been assigned and a small team (Pavithra Krishnamurthy, Naresh Choudhary and Nina Fazio) are already running this ball. We have space identified at the conference venue and there seems to be considerable interest expressed by a few tool vendors.

This Industry Workgroup in Bengaluru has expressed significant interest to continue to meet on a regular basis. This forum is unique in that it cuts across several industries and verticals. We will figure out the next steps once we get the current tasks launched.


Sitting [L-R]: Narendara Babu/Aithal?, Chandra Kitala, S.V. Sankaran, Rinku Dubey, Sheenam Ohrie, Madhu Kumar
Standing [L-R]: Ram Chillarege, Subu Goparaju, Ashish Mathur, K. Prasad, R. Krishnan, Sridhar, Narashima Bhatta, Ganesan Ramalingam, Anand, Santonu Sarkar, Raghu Nambiar, B. Ashok, Srinivas Padmanabhuni, Sachin Garg
Not in the picture, but at the meeting: Rajeev Shorey, Kalyani, Shiv Vasanand, Kalyani Sekhar, Sridhar Venkateswaran, Shyam Vasudev ??

Chair: Ram Chillarege, Chillarege Inc.
Host: Sachin Garg, Chandra Kintala, Yahoo
Industry Committeee: Mod Marathe, Veena Mendiratta

Members of the Industry Workgroup

This is a developing list. We have identified several people and continue to fill out areas. Please contact either: Mod Marathe, Veena Mendiratta or Ram Chillarege if you would like to serve on this workgroup. This team has senior management and senior technical people who can help develop our strategy and reach out to into their organizations.

Company . . . . . Name . . . . . . . . . Responsibility . . . . . Meeting Attendance
Accenture Santonu Sarkar Senior Manager, ATL Labs Confirmed
Alcatel-Lucent Shivani Arora . Confirmed
Bosch R. Sankarn Confirmed
CAT Sridhar Venkateswaran . Confirmed
Cisco Shyam Suri Director Confirmed
Cognizant Kalyani Sekhar . Confirming
EMC Shiv Vasanad Sr. Manager Software Engineering Confirmed
GE Health Care Madhu Kumar Manager Verification and Validation Confirmed
GM Rajeev Shorey Lab Group Manager Confirmed
Google Narendra Babu . Confirmed
HP Srinivas Desikan . Confirmed
IBM Nataraj (Raj) Nagaratnam CTO for Software Brands Confirmed
Infosys Subu Goparaju VP and Head - SETLabs Confirmed
Infosys M.P. Ravindara Advisor Education and Research Confirmed
Microsoft Ganesan Ramalingam . Confirmed
Microsoft B. Ashok . Confirmed
Motorola K. Prasad . Confirmed
Philips Health Care Shyam Vasudevarao Director Technology Confirmed
Philips Health Care Ajit Ashok Quality Manager, Health Care Confirmed
SAP S.V. Sankaran . Confirmed
Rinku Dubey . Confirmed
Shenam Ohrie . Confirmed
Siemens Raghu Nambiar . Confirmed
TCS Ramesh Tumuluru Heads Testing Traveling
TCS TBD . Being Identified
Wipro . CTO Contacted
Yahoo Chandra Kintala Director Confirmed
Yahoo Sachin Garg Director Confirmed

Bengaluru Meeting - May 28, 2009

LOCATION: Yahoo! On Airport Road, Bengaluru
DATE: Thursday May 28
TIME: 12:30pm Lunch. Meeting will follow in the afternoon till the end of the day
HOST: Sachin Garg and Chandra Kintala
CHAIR: Ram Chillarege

Directions to Yahoo Software Development Pvt. Ltd.

Torrey Pines
Embassy Golf Links Business Park (also called EGL Tech Park)
Off Indiranagar – Koramangala intermediate Ring Road,
Bangalore - 560071

“From the intersection of old-airport road and inner-ring road, go on the inner-ring road towards Koramangala – within a kilometer, the tech park entrance will come on your left. After the security check-point of the tech-park, ask for the Y! building or follow the signs for Torre Pines, which is the name of the building. At the reception – ask for Sachin Garg”. Sachin’s mobile number is 97419 70733.

Brainstorming Items - Table

Descriptions of consolidated Items

They are further described on the ISSRE bulletin board under the workshop forum. along with the report and is open for comment.


  • Whatever that is delivered with a web front end, has several “ities” that are vital to this platform. Predominantly: reliability, scalability, availability, and security.
  • Every 5 minutes there is a crash of the Amazon server, but as far as the users are concerned there is total availability.
  • What are the methods, tools, techniques, and bag of tricks to achieve higher reliability?
  • What are the data available to gain an understanding of the current state of the practice? Given a spread in the back end reliability and performance how can we articulate the experience in quantitative terms?
  • Interested Parties: Srinivas.


  • The bread and butter of Indian software development is Services.
  • Note: While there are several product development captive units, Services attracts mind space. Regardless, these discussions will apply to Products and Services.
  • What does it take to carry out a testing service?
  • What does it take to establish quality processes?
  • What uniformity of tools and processes do we need to ensure globally?
  • Service centers naturally focus on functionality since that is what builds the business proposition.
  • What are the issues that are not related to functionality but equally vital to the business proposition? Reliability and Scalability certainly grab attention, therefore what are the issues specifically related to them?
  • SEPG is a popular forum in India. There is synergy between the discussions in that forum and what we have here.
  • There is a marked shift toward a greater focus on product development these days. For instance we see at least 100 product company start-ups in the past six months.
  • Sun iPlanet server was developed here.
  • How does the shift towards product development impact these “ities”
  • Interested Parties: Srinivas + Madhu + Rinku


  • Organizations such as NASA and ISRO have near zero tolerance for failure.
  • Many embedded systems have similar requirements
  • What are the methods used to achieve these low failure rates?
  • To what extent are fault-tolerant techniques currently in use?
  • Many zero tolerance systems are run with little or no fault-tolerance? They depend entirely on testing to ensure that the failure probabilities are low. What is the future of this design point?
  • Is robustness in design only present when it is warranted by law for safety?
  • What are the tradeoffs in the design point? To what extent does the legacy of our systems still dictate development methods and practices?
  • What are examples of a system re-design in recent years, that helped reduce development cost and cycle time?
  • Interested Parties: Bhatta + Sridhar


  • What are the needs for reliability in cloud computing?
  • The shift in paradigm where hardware and software are time sliced, provides an intrinsic model for redundancy. How can this be leveraged for reliability and scalability of applications?
  • What are the business models for startup companies where this changes the game for offering services?
  • How can we leverage these resources for development and test in ways that were not possible before?
  • What are some case-studies that illustrated the exploitation of cloud computing? What are the costs and infrastructure needs necessary to get started? Where does it not provide value?
  • Interested Parties:

  • We have had to very successful workshops in embedded software reliability in the past two years – Sweden and Seattle. Each had around 30-35 participants and there is considerable documentation on the program, talks, structure and feedback on these workshops.
  • A substantial amount of information on organizing this workshop is available in the previous year’s websites.
  • The past workshops had two inter-twined themes. (1) Process Management (2) Model based development
  • The past workshops also list a series of some 30-40 issues of interests, and discussions are often centered among this subset of issues.
  • Interested Parties: Several


  • What are the in-process measures that are in common use?
  • Are there specific measures that are pertinent to reliability that can be used early in the development cycle?
  • A number of reliability measures are after the fact that only yield a report card. Are there predictive measures that are valuable earlier in the development cycle?
  • What are the major groups of product measures and how can we relate them to process measures?


  • We have several process improvement methods, models and practices. CMMi, Six Sigma, TL, ISO, being the prominent ones.
  • What is common among them, and what is different?
  • What are the experiences in using one over the other?
  • Did some institutions begin with one and find it too hard to sell and then switch to another?
  • Are there some specific advantages of one over the other based on industry or market segment?
  • Some industries require compliance with a specific practice. Are there lessons learnt in the use of another model that make it more effective to implement?
  • Some institutions have modified the original models or extended them so that they provide value in more than one business or technical realm. For instance, ROI analysis is particularly valuable when margins erode and we need to survive business cycles. What are the insights gained?
  • There is resistance to use of these models across different product companies? What are the major arguments in favor for or against a model?
  • The services businesses have been the ones that gave the CMM a big boost. The product company pickup has been slower. What are the lessons learnt from this experience?


  • What are the metrics that are commonly used for reliability?
  • The use of execution time measures has for long been hailed as better for reliability measurement. However, the collection of execution time is not as easy and not as widespread. What are the experience and best practices in the collection of execution time?
  • What are the product measures that help improve reliability? There have been papers at ISSRE that use code analysis metrics that help guide the enhancement of specific sections of code. Experience reports in this area are welcome. Is this something that is gaining traction in our community or are the one-off instances?



  • What does reliability mean in different market segments or industries? For instance the notion of failure or the promise of a service is different by markets. A failure in aerospace and its consequences is quite different from the notion of failure in a desktop application. Thus, we need to separate the notions of failures, and associate with them the consequences.
  • Financial impacts, by industry, market segment, application is valuable to document.
  • Responses to failures and techniques of reliability are valuable to document.
  • Practices for manual intervention and recovery.


  • What is the business value of reliability?
  • Value or Impact of reliability need to be measured in dollars, market opportunity, competitive advantage or safety and security impact that can be related directly to customer experienced value.
  • Interested Party: Subu

They are further described on the ISSRE bulletin board under the tutorials forum.