Home tabAssessment & Training tabDownload tab
Abelia logo
INDEX
 

A "Whole Product"Approach to Requirements Identification, by Lewis Gray. Apr 03

An OSSP Architecture Based on IEEE/EIA 12207 and CMMI-SE/SW/IPPD/SS, by Lewis Gray. Feb 03
Seat Belt Buckles or Elections? Achieving Successful Technology Deployment, by Lewis Gray. May 00
Why Projects Need Process Standards: It's the Biology! by Lewis Gray. Mar 00
A Comparison of IEEE/EIA 12207, ISO/IEC 12207, J-STD-016, and MIL-STD-498 for Acquirers and Developers, by Lewis Gray. 4 May 99
No Hypoxic Heroes, Please! Biological Limits on Cowboy Programmers, by Lewis Gray. Dec 98
Why Coaches are Needed in Software Process Improvement, by Lewis Gray. Sep 98
International Standard ISO/IEC 12207 Software Life Cycle Processes, by Raghu Singh. 23 June 98
ISO/IEC 12207 Software Lifecycle Processes, by Lewis Gray. Aug 96
Using MIL-STD-498 and ISO/IEC 12207 for OOD and RAD, by Lewis Gray. 24 April 96
MIL-STD-498, Software Development and Documentation, United States Department of Defense. 5 Dec 94
Should A Level-1 Organization Buy or Build Level-2 Procedures? by Lewis Gray. 28 Apr 93
Link to Guidebook
Link to training
link to Adobe Acrobat Reader
PDF files require the Adobe® Acrobat® Reader which is a FREE DOWNLOAD from Adobe®
A "Whole Product" Approach to Requirements Identification, by Lewis Gray. 30 Apr 03. (290K - PDF file) File Name: <stc_03.pdf>. It is still notoriously difficult to identify accurate, complete requirements for software systems. An approach based on the comprehensive strategy of identifying a whole product would be an improvement. These slides explain whole products, and argue for the value of basing a requirements identification approach on them. The slides were presented in Track 1 of the Software Technology Conference in Salt Lake City, UT  on Wednesday, April 30, 2003. Back to Top

An OSSP Architecture Based on IEEE/EIA 12207 and CMMI-SE/SW/IPPD/SS, by Lewis Gray. 26 Feb 03. (328K - PDF file) File Name: <OSSP.pdf>. What is an SEPG to do when its organization's customers demand compliance both with the 12207 standard and with a CMMI model? How is the SEPG to model its organization's set of standard processes (OSSP)? These slides were presented in the Level 3 Track at SEPG 2003 on Wednesday, February 26, 2003. The slides describe 27 elements of a framework for an OSSP architecture based on IEEE/EIA 12207 and the CMMI-SE/SW/IPPD/SS v1.1. If your organization is developing or evaluating its OSSP, this framework is worth a look. Also, this file corrects a few, small typos in the original presentation. Back to Top

Seat Belt Buckles or Elections? Achieving Successful Technology Deployment, by Lewis Gray. 2 May 00. (711K - PDF file) File Name: <seatbelts.pdf>. These are the slides for a presentation in Track 4 of the Software Technology Conference in Salt Lake City, UT  on Tuesday, May 2, 2000. The presentation offers metaphors for two familiar situations when new technology is deployed. In one, technologists are in charge. In the other, users are in charge. Many failures to deploy technology successfully result when managers and technologists confuse the two situations. The metaphors clarify why. Back to Top

Why Projects Need Process Standards: It's the Biology! by Lewis Gray. 22 Mar 00. (758K - PDF file) File Name: <biology.pdf>. This presentation attracted hundreds of people on Wednesday, March 22, 2000, at SEPG 2000. The slides clarify and extend the theme in "No Hypoxic Heroes, Please!" (see below). In summary, process standards are needed to avoid ad-hoc software processes. Ad-hoc software processes are bad because they are created at just the time when people's ability to create good ones is most impaired. Without standard processes to help them, impaired people create poor ad-hoc processes, and then poor software. Back to Top

A Comparison of IEEE/EIA 12207, ISO/IEC 12207, J-STD-016, and MIL-STD-498 for Acquirers and Developers, by Lewis Gray. 4 May 99. (537K - PDF file) File Name: <122_016.pdf>. These are the slides for a standing-room-only presentation in Track 8 of the Software Technology Conference in Salt Lake City, UT  on Tuesday, May 4, 1999. The presentation compares IEEE/EIA 12207 to the ISO standard on which it is based and to J-STD-016 (the demilitarized version of MIL-STD-498) which might be adopted by the U.S. DoD. The presentation also examines key differences in the acquirer-supplier relationships suggested by the different standards. Back to Top

No Hypoxic Heroes, Please! Biological Limits on Cowboy Programmers, by Lewis Gray. Dec 98. (45K - PDF file) File Name: <gray.pdf>. This article in the December 1998 issue of CrossTalk rebuts a collection of arguments against the use of process standards. The article presents a strong case for the use of software life cycle standards such as ISO/IEC 12207 (and IEEE/EIA 12207) and process standards such as the Capability Maturity Models(SM). The article has sparked debates about process within the software engineering and the systems engineering communities. An earlier version of the article (273K - PDF file, File name: <cowboys.pdf>) was popular at SEPG '98 and STC '98. It appeared in IEEE Computer, April 1998 in reply to a February 1998 column by James Bach. The April article was printed in Bach's April column, and includes a reply by Bach. Back to Top

Why Coaches are Needed in Software Process Improvement, by Lewis Gray. Sep 98. File Name: <gray.pdf>. (86K - PDF file) This technical paper appeared in the September 1998 issue of CrossTalk. Transparencies and a more detailed paper on the same topic are also available separately here: File name: <cchslid.pdf>. (514K - PDF file) - these transparencies were a popular presentation at the European SEPG '98 in London, Track B, on June 10, 1998. They describe the Coach role in detail, and compare it to the more familiar roles of Sponsor, Champion, and Change Agent. If you don't understand these roles, if you don't have personnel filling them, these are risks to your process improvement project that you should be tracking; File name: <cchpapr.pdf> (236K - PDF file) is an updated version of the technical paper that accompanied the transparencies in the conference proceedings -- the same technical paper accompanied an earlier version of the presentation in the conference proceedings of  the Software Technology Conference, Salt Lake City, UT, Track 10: Process Improvement, on Wednesday April 22, 1998, and an edited version of the paper is available above from CrossTalk. Back to Top

International Standard ISO/IEC 12207 Software Life Cycle Processes, by Raghu Singh. From the editor of ISO/IEC 12207:1995, two authoritative explanations of this early standard that lies at the heart of IEEE/EIA 12207. The first is an interesting paper that describes the basic concepts, the requirements, and the application of the 1995 standard. There is also a tutorial that presents the topics in the paper in over 140 detailed, useful slides. The paper, dated August 23, 1996, is File name: <12207cpt.pdf> (78K - PDF file). The tutorial, dated April 26, 1999, is File name: <12207tut.pdf> (794K - PDF file).   ISO/IEC 12207 Software Lifecycle Processes, by Lewis Gray, from August 1996 (see below) comparing ISO/IEC 12207 to MIL-STD-498 is an excellent technical supplement to both of these. Back to Top

ISO/IEC 12207 Software Lifecycle Processes, by Lewis Gray. Aug 96. (110K - HTML) File name: <isoiec.html>. This technical report in the August 1996 issue of CrossTalk describes the 1995 ISO/IEC standard for software life cycle processes and compares it to MIL-STD-498. The ISO standard became more familiar and important in the United States in May 1998 when the Department of Defense adopted IEEE/EIA 12207 as the replacement for MIL-STD-498 for software development. IEEE/EIA 12207 is the industry implementation of ISO/IEC 12207:1995. Back to Top

Using MIL-STD-498 & ISO/IEC 12207 for OOD and RAD, by Lewis Gray. 24 April 96. (265K - PDF file) File name: <498ood.pdf>. These slides were presented on Wednesday, April 24, 1996, in Track 6 at the Software Technology Conference, Salt Lake City, UT. The slides focus on using the standards for OOD. However, the accompanying 38-page technical paper addresses RAD also. The technical paper appears in the proceedings of the conference on CD-ROM. As a convenience to those who might find it difficult to obtain the '96 conference proceedings, the paper may be downloaded from here also (1423K - PDF file). File name: <use_498.pdf>. Back to Top

MIL-STD-498, Software Development and Documentation, United States Department of Defense. 5 Dec 94. (595K - ZIP file) File name: <498-zip.exe>. Since MIL-STD-498 was canceled by the Department of Defense in 1998, copies of it have become harder to locate on the web. In response to inquiries about how to obtain the standard, Abelia Corp. has posted a complete copy on this site. The copy is the original electronic version of MIL-STD-498 prepared by Logicon in San Diego in 1994. It is a self-extracting ZIP archive that contains the standard, its 22 Data Item Descriptions (DIDs), and a DIDs cover sheet, all in WordPerfect 5.1 format for DOS. For an explanation of the contents of the ZIP file, and for guidance on printing, see File name: <readme.txt> (3K - text file).  

Finally, for those who may prefer it, Abelia has posted what we believe to be a complete and accurate collection of PDF versions of the standard, its DIDs, and its two subsequent guidebooks. They can be browsed online. These documents (5.8MB - PDF files) were prepared by Logicon for the Joint Logistics Commanders in 1996. For a road map of the thirty five interlinked PDF documents, and to read or download the individual documents, see File name: <roadmap.pdf> (50K - PDF file). For more information about these documents, see File name: <readme.txt> (3K - text file), which explains File name: <498_WIN3.EXE> (3.9MB - executable file). Back to Top


Should A Level-1 Organization Buy or Build Level-2 Procedures? by Lewis Gray. 28 Apr 93. This report is a slightly reconstructed version of a presentation at the 5th SEPG National Meeting in April 1993. File name: <buy_rpt.pdf> (24K - PDF). The slides used for the presentation in 1993 are in File name: <buy_sld.pdf> (168K - PDF). This short report argues from process improvement data that for many organizations it would be better to obtain software development procedures externally than to develop them in house. The report describes two important discriminators between the two sources of procedures. They are cost and morale. Skeptics in 1993 claimed that externally-developed procedures would not achieve organizational buy-in because of the “not-invented-here” syndrome. However, the basic conclusions and reasoning in the report are accepted widely now. Back to Top
 
 
©2005 Abelia Corporation. All rights reserved worldwide.