Past Meetings
1999-2000 Season
_________(in reverse chronological order)________
Click here for the Past Meetings Page
______________________________________________________________________
The June SASPIN meeting had to be cancelled at the last minute. Our speaker had a death in the family.
______________________________________________________________________
"Lessons Learned by the CM PAT"
Presented by
MSgt Monte J. Hansen
Chief, Configuration Management
HQ AFPC
One of the most useful techniques of process improvement is the Process Action Team (PAT). Such a team was recently put to the test at the Air Force Personnel Center (AFPC). This presentation gave the highlights of that team’s experiences, and focused on the lessons that were learned. A brief overview of the organization, the teams goals and objectives, and major events was covered.
This is a true tale told by one of the survivors. Names will be withheld to protect the innocent.
You can contact MSgt Monte J. Hansen at (210) 565-4022, or monte.hansen@afpc.randolph.af.mil .
Sgt Hansen has graciously granted us permission to place a copy of his slides on our web site. The slides are in Adobe Acrobat format and can be viewed by clicking the file Saspin_May2000_Hansen.pdf (167 KB). Sgt Hansen has also provided copies of the following files: Blank CM PAT Lesson Learned Form.doc (22 KB), Level 2 KPA Coverage sheets generic.zip (71 KB), and PAT Time Tracking Generic.xls (266 KB).
If you are using Microsoft Internet Explorer 4 or later you must use Adobe Acrobat 3.01 or later to view and print the slides and if you wish to save the file you must have Internet Explorer 5 or later. |
With Netscape 3 or later you may view, save or print the slides with Adobe Acrobat 3 or later. |
If you dont already have the Acrobat Reader click on the image to the left to download the latest version free.
______________________________________________________________________
"Goal - Question - Metric Paradigm"
Presented by
Don & Linda Shafer
Athens Group, Inc.
Don & Linda's presentation discussed a template and plan for the establishment of a set of organizational metrics based on that organization's goals. It follows the Goal Question Metric (GQM) Paradigm developed by Professor Victor Basili and recommendations in the Software Engineering Institute's (SEI) Capability Maturity Model (CMM) for level 2 maturity. The GQM plan describes how to establish measurement methods from quantifiable organization goals. The desired result is having meaningful measurements for a tracking projects, in collecting metrics to support those goals, and in managing to meet those goals. The establishment of the example metric plan was undertaken using the GQM paradigm.
The GQM Template provides a structure for the various measurement activities and recommends ways in which the measurement capability must be structured to support all organizational activities. Unnecessary overhead is eliminated.
This template serves these objectives:
Use Goal/Question/Metric paradigm for quantitative tracking and management of a system and software organization projects.
Use established organization goals for the purpose of tracking and oversight.
Identify metrics to measure achievement of the established goals.
This quote from Professor Basili best sums up why to use GQM: "The GQM paradigm represents a practical approach for bounding the measurement problem. It provides an organization with a great deal of flexibility, allowing it to focus its measurement program on its own particular needs and culture. It is based upon two basic assumptions (1) that a measurement program should not be 'metrics-based' but 'goal-based' and (2) that the definition of goals and measures need to be tailored to the individual organization. However, these assumptions make the process more difficult than just offering people a 'collection of metrics' or a standard predefined set of goals and metrics. It requires that the organization make explicit its own goals and processes..."
In addition to presenting the GQM paradigm, Don and Linda also used real life examples that clearly illustrated the process.
You can contact Don Shafer at (512) 345-0600, ext 117, fax (512) 345-4088, or don.shafer@athensgroup.com and view his web site with more information at www.athensgroup.com.
Don and Linda Shafer have graciously granted us permission to place a copy of their slides on our web site. The slides are in Adobe Acrobat format and can be viewed by clicking the file Saspin_Apr2000_Shafer.pdf (191 KB).
If you are using Microsoft Internet Explorer 4 or later you must use Adobe Acrobat 3.01 or later to view and print the slides and if you wish to save the file you must have Internet Explorer 5 or later. |
With Netscape 3 or later you may view, save or print the slides with Adobe Acrobat 3 or later. |
If you dont already have the Acrobat Reader click on the image to the left to download the latest version free.
______________________________________________________________________
"Quantifying The Qualitative: How to Avoid Vague Requirements by Clear Specification Language"
Presented by
Tom Gilb
Result Planning Limited
Tom Gilb presentation was superb. Generally, the quantification of quality is not mastered by current culture. Qualitative requirements can always be specified with quantitative clarity. Tom's presentation gave pragmatic ideas on how to achieve this. The main concept is to define a 'scale of measure'.
Tom explained how with our current culture there are problems with the general current specification of qualitative requirements. There is insufficient understanding of the importance of these 'quality requirements'. They are crucial because they are our main competitive differentiator for a given functional area, aside from cost. A lack of adequate quality specification tends to limit creativity and prematurely cuts short the system design. Often quality requirements are placed in categories called 'non-functional requirements' or 'intangibles'. People assume that they can limit themselves to describing qualities at a high-level and qualitatively. We have all seen requirements of the type:
Change: {enhance, improve, reduce, increase}
Quality: {performance, ease of use, maintenance
costs, productivity, security, adaptability}For example:
"achieve substantial increase in our products ease of use by the customer"
For certain purposes, such as motivational management speeches or hiding the precise objectives, such requirement statements can find a use. However, within projects, this non-quantified culture is unacceptable because it is too vague to provide clear direction for activities such as contracting, testing, configuration management and engineering design. The large investments of time, people and money, the need for the high impact results and, the high risks involved demand quantitative specification. Quality requirements must be defined as clearly as we define the functionality and cost requirements. They must be stated in an unambiguous and testable manner or we risk not getting design and test carried out for them.
Practical Experience. Many people are initially reluctant to accept that all qualitative requirements can be quantified. However, Tom's experience (over more than thirty years) is that it can always be achieved. Even in cases, where the quantitative scale of measure has to be indirect, it is far better than none. Once people have seen a few examples of quantitative requirements, they are usually quickly won over. In fact, there are several companies which already have clear top management policies about quantifying objectives and quality requirements. For example, Ericsson, Hewlett-Packard and IBM. But most companies have not taken a position on the subject. It is important that top management take the initiative and communicate clearly their requirements. The message needs to be backed up by a pervasive company culture and necessary training. Tom wrapped up his presentation by going through several examples of qualitative requirements and clearly showed each could be quantified.
You can
contact Tom Gilb at (4760) 801697, gilb@acm.org,
or
N-1410 Kolbotn, Norway and view his web site with more information at
www.Result-Planning.com.
Tom Gilb has graciously granted us permission to place a copy of a paper he wrote on the presentation topic along with a copy of his slides. Both the paper and the slides are in Adobe Acrobat format. The paper can be viewed by clicking the file Saspin_Mar2000_Gilb_Paper.pdf (66 KB) and the slides can be viewed by clicking the file Saspin_Mar2000_Gilb_Slides.pdf (252 KB).
If you are using Microsoft Internet Explorer 4 or later you must use Adobe Acrobat 3.01 or later to view and print the slides and if you wish to save the file you must have Internet Explorer 5 or later. |
With Netscape 3 or later you may view, save or print the slides with Adobe Acrobat 3 or later. |
If you dont already have the Acrobat Reader click on the image to the left to download the latest version free.
______________________________________________________________________
"Critical Chain Project Management -
The Next Big Thing?"
Presented by
Bob Futrell
An independent consultant for Project Management Systems
Ever since Eliyahu Goldratt's landmark book "The Goal" appeared in 1984, the concepts of the theory of constraints have been evolving into a controversial approach to managing the critical chain of events that pace every project. In his follow-on books "Theory of Constraints" (1990) and "Critical Chain" (1997), Goldratt expands the concepts further. Others, such as Robert Newbold ("Project Management in the Fast Lane - Applying the Theory of Constraints", 1998) have interpreted Goldratt's ideas and formed them into some practical approaches that seem to make sense for managing projects in today's environment. This presentation briefly introduced the concepts of critical chain project management compared to "standard" project management, and presented some of the issues surrounding this different approach to managing schedules.
You can
contact Bob Futrell at (512) 833-8276, futrell@acm.org,
or
P.O. Box 200148, Austin, TX 78720-0148.
Bob Futrell's has graciously granted us permission to place a copy of his briefing on the web site so SASPIN members may review the slides. The briefing slides in the Adobe Acrobat format can be viewed by clicking the file Saspin_Feb2000_Futrell.pdf (399 KB).
If you are using Microsoft Internet Explorer 4 or later you must use Adobe Acrobat 3.01 or later to view and print the slides and if you wish to save the file you must have Internet Explorer 5 or later. |
With Netscape 3 or later you may view, save or print the slides with Adobe Acrobat 3 or later. |
If you dont already have the Acrobat Reader click on the image to the left to download the latest version free.
______________________________________________________________________
"Disciplined Software Testing Practices"
Presented by
Dr. Magdy Hanna
International Institute for Software Testing
If we are going to call ourselves "test engineers" we better know what the term means. Software testing must be treated as a disciplined process not as an ad hoc activity. In this presentation, Dr. Hanna addressed what testing professionals must do to make software testing a recognized profession and to improve the image of the testing organization. Specifically, Dr. Hanna highlighted the challenges facing testing organizations and the skills needed by testing professionals to meet those challenges. He presented the Ten Essential Software Testing Practices that every testing organization and every testing professional must always exploit in order to establish a more disciplined testing profession. Dr. Hanna concluded with a discussion on the requirements for the Certified Software Testing Professional program.
You can contact Dr. Hanna at mhanna@softdim.com , (651) 552-0791 or view his web site at www.softdim.com .
Dr. Hanna's briefing can be viewed or printed at www.doftdim.com/iist/ and by selecting "View Dr. Hanna's Presentation on Disciplined Software Testing Practices" on this web page.
______________________________________________________________________
SQA - The Implementation of SPI
Major Andrew Boyd
Chief, Software Process Improvement Air Force Personnel Center, Personnel Data Systems, Randolph AFB, TX
A Software Quality Assurance Case Study
USSTRATCOM/J62, Offutt AFB, Nebraska
Have you ever been told your Software Process Improvement
(SPI) program
was nothing but pure "academia?" Well, at the Software Support Division in
USSTRATCOM, they
were absolutely right - until SQA came along.
During this presentation Andy demonstrated how USSTRATCOM took the "academic" work of the SEPG
(aka those
"Big Honkin' Binders"), threw in the experience of an SEI assessor, and put together an SQA shop that
really worked. Specific topics include:
Organizational Standard Software Process (OSSP) assets established by the SEPG
Getting an SQA shop (ala SW-CMM®) off the ground
Organizing for SQA
SQA specific roles, responsibilities, assets, plans, activities, and relationships
Metrics collected and reported
Continuing SPI without an SEPG, and
Some lessons learned
During his presentation Andy provided numerous examples of documentation, plans, guides, processes and lessons learned on implementing software process improvement into an organization.
You can contact Andy at his work number 210-565-3234 or by sending email to Andrew.Boyd@afpc.randolph.af.mil .
Andy Boyd has graciously granted us permission to place a copy of his briefing on the web site so SASPIN members may review the slides. The briefing slides in the Adobe Acrobat format can be viewed by clicking the file saspin_Nov99_boyd.pdf (114 KB).
If you are using Microsoft Internet Explorer 4 or later you must use Adobe Acrobat 3.01 or later to view and print the slides and if you wish to save the file you must have Internet Explorer 5 or later. |
With Netscape 3 or later you may view, save or print the slides with Adobe Acrobat 3 or later. |
If you dont already have the Acrobat Reader click on the image to the left to download the latest version free.
______________________________________________________________________
Effective Software Quality Assurance
Randy Folck, Process Innovation, Inc.
Randy's presentation provided insight on what it takes to define, design and implement a practical software quality assurance strategy using proven techniques for your chosen quality system model, including obtaining and maintaining management support. Specifics included:
Tailoring software quality assurance activities for projects of any size
Assessing and reporting process and quality system effectiveness
Selecting effective quality assurance techniques and methods
Initiating and facilitating lasting corrective action
Selling the benefits of software quality assurance to the organization
During his presentation Randy provided numerous examples of how to initiate the different activities of a software quality assurance program.
You can find out more about Process Innovation, Inc. by calling 210-558-4236 or sending email to rfolck@satx.rr.com .
Randy Folck has graciously granted us permission to place a copy of his briefing on the web site so SASPIN members may review the slides. The briefing slides in the Adobe Acrobat format can be viewed by clicking the file saspin_Oct99_folck.pdf (216 KB).
If you are using Microsoft Internet Explorer 4 or later you must use Adobe Acrobat 3.01 or later to view and print the slides and if you wish to save the file you must have Internet Explorer 5 or later. |
With Netscape 3 or later you may view, save or print the slides with Adobe Acrobat 3 or later. |
Webmasters Reminder: The briefing is copyrighted. Please handle accordingly so we can get other individuals that present to the SASPIN to allow us the same permission to post their slides.
If you dont already have the Acrobat Reader click on the image to the left to download the latest version free.
______________________________________________________________________
Using the Cost of Quality Approach for Software
Herb Krasner
Herb Krasner’s presentation on Using the Cost of Quality Approach for Software answered the following questions:
what does good software quality cost?
what does poor software quality cost?
what is the difference (by CMM level) ?
how do process improvement costs/benefits get measured?
During his presentation, Herb Krasner explained the Cost of Software Quality (CoSQ) which is a simple model and measurement technique that enables our understanding of the economic tradeoffs involved in developing, delivering and supporting high quality software. Although its use offers much promise, it has seen only a few implementations by the software community to date. With regard to process improvement, CoSQ has been shown to be a useful technique for justifying and tracking the costs/benefits of an SPI program. This presentation discusses the context, rationale and definition of CoSQ, as well as, implementation issues. Benchmark examples from Honewell BSCE and Ratheon Electronic Systems, two of the industry leaders were presented. The relationship of CoSQ to the CMM-ladder was also discussed.
Herb Krasner has graciously granted us permission to place a copy of his briefing on the web site so SASPIN members may review the slides. The briefing slides in the Adobe Acrobat format can be viewed by clicking the file saspin_Sep99_krasner2.pdf (92 KB).
If you are using Microsoft Internet Explorer 4 or later you must use Adobe Acrobat 3.01 or later to view and print the slides and if you wish to save the file you must have Internet Explorer 5 or later. |
With Netscape 3 or later you may view, save or print the slides with Adobe Acrobat 3 or later. |
Webmaster’s Reminder: The briefing is copyrighted. Please handle accordingly so we can get other individuals that present to the SASPIN to allow us the same permission to post their slides.
If you don’t already have the Acrobat Reader click on the image to the left to download the latest version free.
______________________________________________________________________
______________________________________________________________________