OMG TECHNICAL MEETING SPECIAL EVENT Consortium for IT Software Quality (CISQ) Seminar
Using Software Measures in Productivity and Quality Improvement Programs Wednesday, 0900 - 1600, June 19, 2013 | Event Home Page | All Special Events | Become A Sponsor | Seminar Objectives: The objectives of the Consortium for IT Software Quality (CISQ) Seminar are to: - Motivate participants to use software sizing and structural quality measures to reduce the risk and cost of software.
- Present the CISQ/OMG measures for Automated Function Points, Reliability, Performance Efficiency, Security, and Maintainability.
- Present best practices for deploying and using software measures in productivity analysis and improvement, vendor management, benchmarking, and structural quality management.
- Identify pitfalls to avoid in analysis and use of measures.
- Describe experiences and lessons learned using software measures in large organizations.
Audience: This full day seminar is intended for IT Executives, application managers, software measurement and improvement specialists, quality assurance professionals, and others interested in using automated software measures. PROGRAM AGENDA | 0900 - 0915 | Welcome and Introduction | | Dr. Bill Curtis, Director, CISQ | | | | 0915 - 10:15 | Introduction to Productivity Analysis | | Dr. Bill Curtis, Director, CISQ | | Dr. Curtis will introduce the uses of productivity analysis with a strong emphasis on continual improvement. He will discuss the three types of measures required for productivity analysis-size, effort, and application demographics-along with how to avoid pitfalls in collecting them. He will describe how Function Points have emerged as a preferred measure of size. | | 1015- 1045 | Morning Refreshments | | | | | 1030 - 1130 | Industrial Experience with Productivity and Quality Analysis | | Mark Standeaven, Vice President, Capgemini | Mr. Standeaven will discuss the importance of OMG’s recent approval of a specification for Automated Function Points and what it means for the future of size and productivity measurement. He will describe how Capgemini is using Function Points in estimating size and benchmarking results. He will then describe how they measure the structural quality of the software they produce. He will discuss the relationship between productivity and quality. He will then present data showing the relationship between improving structural quality in an industrial environment and the business results they achieved.
| | 1130 - 1200 | Best and Worst Practices in Productivity Analysis and Improvement | | Dr. Bill Curtis, Director, CISQ | Dr. Curtis will discuss techniques for conducting productivity analysis and present examples from his extensive consulting background as well as published case studies from major corporations. Best and worst practices will be discussed for analyzing and using productivity data. He will end by discussed best practices for using size and productivity data in contracting relationships.
| | | | 1200 - 1330 | Lunch (Attendees are on their own for lunch, this is not included in the registration fee.) | | | | | 1330 - 1415 | Introduction to Structural Quality Analysis and Management | | Dr. Bill Curtis, Director, CISQ | | Dr. Curtis will discuss the critical importance of measuring the structural quality of applications along with the functional correctness. He will describe three levels of structural analysis-code unit, technology, and system-and why system level structural flaws are the most costly. He will end with a description of the recently released CISQ standards for measuring Reliability, Performance Efficiency, Security, and Maintainability. | | 1415 - 1500 | Measuring and Managing Technical Debt | | Dr. Bill Curtis, Director, CISQ | | Dr. Curtis will describe the concept of technical debt and how it can be used to communicate about the structural quality of software to both IT and non-IT management. He will describe a method for measuring technical debt and how it can be adjusted to the experience of different IT organizations. He will present some examples of how technical debt has been used to control IT quality and costs. | | 1500 - 1515 | Afternoon Refreshments | | | | | 1515 - 1615 | Measuring and Managing Technical Debt | | Bob Martin, Director, Common Weakness Enumeration Project, Mitre Corporation | | Mr. Martin will describe the national effort to identify and eliminate the causes of security breaches through the development of the Common Weakness Enumeration repository. He will describe best practices for using information in the repository for improving the security of software. He will describe how to measure the security of software and how this is done using the CISQ measure for Security, whose definition he led. He will discuss some of the most common security problems and how to avoid them. | | 1615 - 1630 | Open Discussion | | | | | NOTE: If you register for the Technical Meeting Week, you do not have to pay the additional fee(s) to attend any or all of the special events. If you register only for special events, the special fees apply. |
