OMG TECHNICAL MEETING
Consortium for IT
Software Quality (CISQ) Seminar
Using Software Measures in Productivity and
Quality Improvement Programs
0900 - 1630, September 25, 2013
Home Page | All
Special Events |
Become A Sponsor |
Contact Us |
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
- 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
- Describe experiences and lessons learned using software
measures in large organizations.
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.
Dr. Bill Curtis, Director, CISQ
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.
Automated Function Points in Sizing and Estimating
Mike Harris, CEO, The David Consulting Group
Harris will describe how Function Points have emerged as a
preferred measure of size and the importance of OMG’s recent
approval of an Automated Function Point specification. He will
describe how Function Points are used in estimating size before
code exists and how Function Point data can be used in
benchmarking. He will also discuss the importance of using
Enhanced Function Points to analyze the productivity of
maintenance activity. He will use examples from DCG’s Function
Point repository and extensive experience in Function Point
consulting with DCG clients.
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 and government projects. Best
and worst practices will be discussed for analyzing and using productivity
data. He will describe how to match the collection and use of productivity
data to the maturity of the organization. He will end by discussed best
practices for using size and productivity data in SLAs.
(Attendees are on their own for lunch, this is not included
in the registration fee.)
||Introduction to Structural Quality Analysis
Bill Curtis, Director, CISQ
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 discuss the
recently released CISQ standards for measuring Reliability,
Performance Efficiency, Security, and Maintainability.
||Industrial Experience with Productivity and Quality Analysis
|Robert Shay, Capgemini
| Mr. Shay
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 that were achieved.
||Structural Quality Issues in Software Resiliency and Security
|Dr. Bill Curtis, Director, CISQ
| This talk
will begin by discussing the structural quality issues affecting
software resiliency and the practices that are necessary to
control them. Dr. Curtis will then 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. This talk conclude by describing the national
effort to identify and eliminate the causes of security breaches
through such developments as the Common Weakness Enumeration
repository and the practices necessary to use these resources.
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