logoC-SPIN / Meetings and Events / Next Meeting
Updated 5 May 1999

The Orthogonal Defect Classification Methodology as Employed in the Motorola GSM Organization
Thursday, May 6, 1999

Description
Presenters
Agenda
Further Information
Back to C-SPIN Homepage

Thursday, May 6, 1999
6:00-9:00 p.m.
William Rainey Harper College
Algonquin and Roselle Roads
Palatine, Illinois


Domain Modeling and Software Process Management

The extent to which software processes are not actually managed by software is quite odd. The spare application of software systems development methods to the construction of software construction processes could also be viewed as rather ironic. When the most popular capability model for software organizations prescribes an "approved documented process", perhaps something is missing.

There have been a number of attempts to systematize and even automate the "production" of software "products". But apart from a hodgepodge of coding tools, passive documentation environments, drawing tools, CASE tools, CM tools and the like, not a lot of software is actually used in the production of software. The bulk of the code work is done in program editors and most design and documentation is done in word processors. The tools that are used tend to be quite disconnected. When it could reasonably be argued that the job of the software developer is automate things, then the fact that key elements of the job of software development are not "automated" implies that something is missing.

Domain Modeling has a simple premise: a "domain" is some area of human or machine (or other) activity that contains knowledge, this knowledge can best be effected by modeling it. Software development and its associated disciplines (e.g., Project Management) qualify as domains. While many models have been built of or about these domains, most of them are passive-they describe the domain knowledge, they do not execute the domain knowledge. Some recently developed Model-Based Software Engineering (MBSE) tools employ a different approach and goal. They add three things to classical modeling:

  1. The nature or structure of the domain knowledge is first identified. This is known as a meta-model.
  2. The domain knowledge structure is used to develop domain-based tools employing knowledge models based on the meta-model rules.
  3. These models and tools can be made active in that they either interact with their environment or can dynamically produce outputs that are executable.

Presenters

Rob Bleck
Rob Bleck is a system test manager for Motorola's GSM Systems Division. He has 10 years of software engineering experience. He has focused on software verification and validation activities for the last seven years. He created and currently manages GSD's System Assurance organization, an elite system test group whose charter is to eliminate defects that escape traditional system test and performance test methodologies. In addition to advance testing and reliability engineering techniques, this also includes driving continuous improvement activities throughout the entire system test department, as well as actively participating in process improvement teams throughout GSD.
Barbara Hirsh
Barbara Hirsh is the Metrics Manager for the GSM BSS organization. She has 15 years of experience in the areas of software development, system testing, quality, process improvement and metrics. She has played a process improvement role in the GSM BSS organization as they climbed from Level 1 to Level 5. Barbara has been involved in metrics development at the corporate level at Motorola. Barbara received the Motorola Best Practice award in 1994. Barbara has presented at international conferences. She recently was a speaker on the SEPG 99 SPC panel led by Mark Paulk and Anita Carleton.
Corinne Miller
Corinne Miller is the Director of Quality for Motorola's GSM Systems Division. She has over 20 years of experience primarily in engineering and most recently in quality. At Motorola, Corinne is responsible for leading customer satisfaction and continuous improvement strategies for a global organization of 3000 including engineering, manufacturing, and product management spread across North America, Europe and Asia. She led the SEI initiative for the GSM Base Station team who achieved SEI SW CMM Level 5 in 1997.
Paul Norkus
Paul Norkus is a Section Manager for the Terrestrial Resource Management group in Motorola's GSM BSS software development organization. Paul has 10 years software development experience. In addition to managing software development activities, Paul is the current leader of the Process Improvement and Technology Team (PIT). The PIT team provides continuous process and technology improvements by examining recommendations from all groups in the GSM BSS community, analyzing deficiencies seen in the current process and technologies and analysis of metrics data and institutionalizing those changes in the organization.
Steve Wood
Steve Wood is an Engineering Manager for the Operations and Maintenance software group for Motorola's GSM BSS software development organization. He has over 11 years of experience at Motorola including six years with GSM BSS software development. Prior to joining the GSM organization he was a software developer for the portable and mobile radio products. He is a member of the Software Engineering Technology Steering Committee and is a SEI assessor.

Agenda

C-SPIN is made possible through the efforts of its Steering Committee. The Steering Committee is composed of Fred Ballard, David Carter, Pat Ferguson, Bob Ferguson, Dean Fritz, George Gatsis, Hamid Ghezavat, Ken Goncharoff, Venkatesh Kalakkad, Linnea Kountz, Margaret Lakins, Robert Pauwels, Roman Sikaczowski, and Scott Stribrny.

If you are interested in participating on the Steering Committee contact Scott Stribrny at atlantic@mcs.net (e-mail), 630 954-2218 (voice), or 630 954-2259 (fax).

C-SPIN is a leadership forum for the free and open exchange of software process improvement experiences and practical ideas. We promote achieving higher levels of process maturity, software quality and mutual respect. Companies, academic institutions, government organizations and individuals are invited.

There is no need to register before the evening of the meeting, but please check in at the registration table at the meeting.

For more information regarding this meeting or C-SPIN, contact Scott Stribrny at atlantic@mcs.net (e-mail), 630 954-2218 (voice), or 630 954-2259 (fax) or Dean Fritz at fritz@cig.mot.com (e-mail), 847 632-2950 (voice), or 847 632-7521 (fax).

To receive future announcements electronically, send your email address (include name, address, company, phone) to George Gatsis.

Back to C-SPIN Homepage


C-SPIN: Chicago Software Process Improvement Network
1