201701-0-Issue.Pdf
Total Page:16
File Type:pdf, Size:1020Kb
TABLE OF CONTENTS CrossTalk NAVAIR Jeff Schwalb Departments 309 SMXG Kelly Capener 76 SMXG Mike Jennings 3 From the Sponsor Publisher Justin T. Hill 36 Upcoming Events Article Coordinator Heather Giacalone Managing Director David Erickson 38 BackTalk Technical Program Lead Thayne M. Hill Cover Design by Managing Editor Mary Harper Kent Bingham Copy Editor Breanna Olaveson Senior Art Director Kevin Kiernan Software’s Greatest Art Director Mary Harper Phone 801-777-9828 E-mail [email protected] Hits and Misses CrossTalk Online www.crosstalkonline.org Ada: A Failure That Never Happened Ada’s death and failure never occurred. It was — and is — one of the CrossTalk, The Journal of Defense Software Engineering better successes the DoD has produced. is co-sponsored by the U.S. Navy (USN); and U.S. Air Force (USAF). 4 USN co-sponsor: Naval Air Systems Command. USAF co-sponsors: By David Cook and Eugene Bingue Ogden-ALC 309 SMXG and Tinker-ALC 76 SMXG. A Comparison of Medical Diagnoses and The USAF Software Technology Support Center (STSC) is the Software Problem Diagnoses publisher of CrossTalk providing both editorial oversight and 8 Medical diagnoses are based on a number of quantitative measures and technical review of the journal. CrossTalk’s mission is to encour- known values. Diagnosing software problems should also use quantita- age the engineering development of software to improve the reliabil- ity, sustainability, and responsiveness of our warfighting capability. tive data. However, software engineering has close to zero knowledge about the ranges and boundaries of quantitative results that differentiate Subscriptions: Visit <www.crosstalkonline.org/subscribe> to healthy projects from unhealthy projects. receive an e-mail notification when each new issue is published By Capers Jones online or to subscribe to an RSS notification feed. Ada - 20 Years After the Mandate Article Submissions: We welcome articles of interest to the defense If the interoperability and, particularly, the cybersecurity challenges of the software community. Articles must be approved by the CrossTalk 14 21st century had been foreseen in the mid-‘90s, perhaps DoD policymak- editorial board prior to publication. Please follow the Author Guide- ers would have looked at Ada in a different light. Ada changed the conver- lines, available at <www.crosstalkonline.org/submission-guidelines>. sation about defense software engineering and promoted correctness, reli- CrossTalk does not pay for submissions. Published articles remain the property of the authors and may be submitted to other ability, security, interoperability and architecture, among other contributions. publications. Security agency releases, clearances, and public by Drew Hamilton and Patrick Pape affairs office approvals are the sole responsibility of the authors and their organizations. A Retrospective View of the Laws of Software Engineering Software development is now more than 60 years of age. A number of Reprints: Permission to reprint or post articles must be 17 interesting laws and observations have been created by software engineer- requested from the author or the copyright holder and ing researchers and by some academics. This short paper summarizes these coordinated with CrossTalk. laws and makes observations about the data and facts that underlie them. by Capers Jones Trademarks and Endorsements: CrossTalk is an authorized publication for members of the DoD. Contents of CrossTalk are not necessarily the official views Open Forum: Why Agile Projects Sometimes Fail of, or endorsed by, the U.S. government, the DoD, the If you want to succeed with an Agile approach, you need more than co-sponsors, or the STSC. All product names referenced in 24 magic rituals. Not only that, you need to avoid several rather common this issue are trademarks of their companies. mistakes that lead to failure. by Gerald Weinberg CrossTalk Online Services: For questions or concerns about crosstalkonline.org web content Scrum is Simple or functionality contact the CrossTalk webmaster at A brief historical background and includes the basic concepts of Scrum. 801-417-3000 or [email protected]. By Dick Carlson 26 Back Issues Available: Please phone or e-mail us to see if back issues are available free of charge. Generating Actionable Information for Classifier Assessment What constitutes actionable information regarding a classifier’s effect on CrossTalk is published six times a year by the U.S. Air Force 31 mission capability, maps some commonly seen measures to these needs, STSC in concert with Lumin Publishing <luminpublishing.com>. and recommends a means of maximizing the actionable information gener- ISSN 2160-1577 (print); ISSN 2160-1593 (online) ated in classifier evaluations. By Earl Eiland and Lorie Leibrock 2 CrossTalk—January/February 2017 FROM THE SPONSOR CrossTalk would like to thank 309 SMXG for sponsoring this issue. How would you define suc- article, we explore the external factors, such as the exponential cess? On a personal level, you proliferation of programming languages, that led to problems in may state that success is the maintenance and continued support. Continuing with the topic of attainment of happiness or the Ada, we also have a fine article on the topic by Dr. Drew Hamilton completion of an effort you were and Dr. Patrick Pape entitled “Ada — 20 Years After The Mandate” passionate about. In develop- that takes a retrospective look at the Ada mandate and is certain ment, success might be defined to be enlightening from the perspective of an author who is by a set of criteria against stated directly linked to the Ada Joint Program Office (AJPO). objectives. And yet, there is am- We have two articles on the topic of Agile. Dick Carlson has biguity in exactly what success is written an insightful piece entitled “Scrum is Simple” that dis- here as well. For example, from a cusses the cultural shift away from traditional project manage- developer’s point of view, it may be the system’s technical capabil- ment methods and tackles the difficulties of changing the ‘sta- ity. From a user’s perspective, success is generally defined by key tus quo’ and implementing Agile for projects looking to transition performance and functional attributes. A customer’s considerations to Agile methodologies. The second piece on Agile is entitled may be focused toward budget, schedule, quality, and user satisfac- “Why Agile Projects Sometimes Fail” by Gerald Weinberg. This tion. Are success criteria absolute in nature? Do we automatically is an open forum piece that discusses the effective leadership consider a program to have failed if it does not achieve all stated styles and team skills necessary for a productive Agile project. objectives? Or, should success be measured in by increments, In this special issue, we also feature two articles by Capers depending on the observer’s point of view? Jones. The first piece, entitled “A Comparison of Medical Diag- As we turn the page on another year and move steadfastly into noses and Software Problem Diagnoses,” illustrates the need the next, we here at CrossTalk have chosen to dedicate this is- for a higher degree of rigor in empirical data by comparing and sue to looking retrospectively on the evolution of the software engi- contrasting software to the medical field. The second article, en- neering field. The intent is not to simply reflect on the past and cast titled “A Retrospective View of the Laws of Software Engineer- black-and-white judgments on whether something was a ‘hit’ or a ing,” takes laws and observations from other scientific fields and ‘miss,’ but rather to delve deeper into the nature of success and what shows the applications and truisms found within each and how causes the perception of failure to begin with. Truly, some ideas we they apply to the software engineering realm as well. once believed were revolutionary truly were. But in hindsight, others For those of you who wish to have an increasingly techni- missed the mark despite our best efforts. The question is, from what cal read, we have chosen to include a special supporting article point of view did they succeed, and for whom did they fail? entitled “Generating Actionable Information for Classifier Assess- Our desire to simplify topics to black-and-white criteria speaks ment” by E. Earl Eiland and Dr. Lorie M. Liebrock. This article will to the limited perspective and fallibility of mankind, especially arm practitioners with the means to calculate actionable informa- in realms with ever-increasing complexity. We are quick to label tion for their specific mission. Finally, do not forget to read our something a success or a failure, though the truth is most often ever-insightful “BackTalk” column, written by Dr. David Cook. In his somewhere in between. One truism that we can count on is that piece, entitled “Failure IS an Option,” he brings us full circle to the failure is inevitable; how we cope with that failure and progress nature of success and failure and what we can learn from both. beyond it defines who we are. It was Robert F. Kennedy in his As we begin the new year, we are also beginning the 1966 Day of Affirmation address who stated, “We also know that 29th year of CrossTalk, would like to express my sincere only those who dare to fail greatly, can ever achieve greatly.” thanks to everyone for making such an accomplishment Although the emphasis here is on the potential benefits weighed possible. We thank our co-sponsors for your generous s against calculated risks, it is important to note that not all missteps upport and active involvement in providing an informational are necessarily failures — just fundamental steps in the nature of and educational resource to the software industry. To the progress. The culmination of our combined successes and failures, authors, we truly appreciate all of your time and effort in along with our ability to learn from them, enhance possibilities and sharing such valuable information with the software commu- drive technology forward.