Tutorials - Tuesday November 11, 2008

Tutorial on IEEE\AIAA Recommended Practice on Software Reliability Applied to Mobile Devices - Tuesday November 11, 2008

- Norman Schneidewind, Mike Hinchey

Objectives

This tutorial serves to elaborate key software reliability process practices that are included in the IEEE\AIAA Recommended Practice on Software Reliability. The objectives are achieved by first discussing the issues in achieving high reliability in software and how the recommended practice supports achieving that result, followed by examples of applying the recommended practice to the reliability of mobile devices. Given the prevalence of mobile devices in contemporary society and the workplace, it is important to address not only their reliability, but their maintainability and availability, as well.

Due to the prevalence of software-based systems, the focus is on learning how to produce high reliability software. However, since hardware faults and failures can cause the highest quality software to fail to meet user expectations, considerable coverage of hardware reliability is provided. Practice problems with solutions are included to provide the engineer with real-world applications of the principles that are discussed.

Software-based systems have become the dominant player in the computer systems world. Since it is imperative that computer systems operate reliably, considering the criticality of software, the IEEE and AIAA commissioned the development of a new standard called, the Recommended Practice on Software Reliability, IEEE P1633 [IEE08]. While the focus of the IEEE P1633 Standard is software reliability, software and hardware do not operate independent of one another, therefore, both software and hardware are addressed in this tutorial in an integrated fashion.

What you can expect to take away from this tutorial is oriented to the key reliability issues described below. Audience participation is encouraged to bring to the tutorial the experience, knowledge, and opinions of the participants.

More Info...

General Software Product Quality Modeling and Controlling - Tuesday November 11, 2008

Speakers : Stefan Wagner, Florian Deissenboeck, Elmar Juergens

Quality is a highly complex but equally important issue in software engineering. This tutorial gives an overview of how to model software quality and how to control it using an appropriate process and corresponding tools. In particular, problems arising in many existing general quality models and ways of confronting them are discussed. Furthermore, tool support for quality control and best practices regarding application and process integration are treated. Hands-on experience can be made in building an own small quality model and in analysing a software project using a dashboard.

Contact : Stefan Wagner ( w a g n e r s t @ i n . t u m . d e )
More information: Tutorial Website

More Reliable Software Faster and Cheaper - Tuesday November 11, 2008

Speakers : Laurie Williams
Duration : Full Day

This tutorial will teach you the essentials of how to apply the proven best practice of software reliability engineering (SRE) to the next release of any system/component that uses software. The tutorial breaks down the practice of SRE into six major activities. The procedure for each of these steps is presented step by step, with a real example given for each step. There are three workshops in which participants apply what they have just learned to a realistic project.

The tutorial provides an introduction to SRE, providing background that will help you understand the rest of the ISSRE conference.

Contact :Laurie Williams (w i l l i a m s AT c s c . n c s u . e d u )
More Info

Quality of Service (QoS) - Measuring and Improving User Experience the Right Way - Tuesday November 11, 2008

Speakers : Mukesh Jain

Today, the global competitive marketplace demands the best of everything - the best quality, high reliability, fast, secure software and services anytime, anywhere on any device. An feature rich product exceeding expectations, delivered on time at minimal cost is the new standard that demanding customers expect globally, and good suppliers continually strive to meet. It is not an easy task to meet these challenges without compromising high quality levels OR agility OR the cost. There is no silver bullet we can meet all these goals by having a disciplined process and managing with the right set of matrices. The Quality of Service (QoS) program's framework guides service-quality processes, consistent and accurate measurement, analysis, and drives improvements for to online services globally. It leverages Six Sigma and Poka-Yoke based approach for breakthrough improvement.

In this tutorial Mukesh Jain will present how the Quality of Service (QoS) program have helped deliver globally superior reliability, availability and performance for Microsoft's major online services like Hotmail, Messenger, Search, MSN, Spaces, etc.

Contact : Mukesh Jain (m u k e s h . j a i n AT m i c r o s o f t . c o m )

Applying Design for Six Sigma (DFSS) to Develop and Assure Reliable Software - Tuesday November 11, 2008

Speakers : Sam Keene

Six Sigma has been widely adopted for improving and developing better products. This tutorial focuses on teaching the fundamentals of Six Sigma and Design for Six Sigma (DFSS) that potentially apply to software development. Most system problems come from "System Management Deficiencies", so labeled by Branden Murphy, or requirements defects, interface problems, and change management. The chief focus will be to demonstrate those six sigma tools that focus on developing and managing a fullness of product requirements. Six sigma uses collaborative tools such as "Mind Map" or Quality Functional Deployment (QFD) to brainstorm, link ideas together, and establish design traceability. The students will actually use these tools during the tutorial and gain fundamental competency with them. This training will help developers to build more robust products the first time. These tools will also aid any quality or reliability specialists to analyze new designs, make suggestions for improvement, and establish enduring artifacts that will help make later design changes less disruptive.

Contact : Sam Keene (k e e n e s a m AT g m a i l . c o m)