Journal: IEEE Software

Volume 14, Issue 6

4 -- 6Alan M. Davis. From the Editor: Making a Mark on the World
19 -- 21Kent Sandoe. Soapbox: Split Ends: Labor Shortage and the CS-IS Divide
22 -- 25Nancy R. Mead, David Carter, Michael J. Lutz. Guest Editors Introduction: The State of Software Engineering Education and Training
26 -- 28James Bach. Point: SE Education: We re on Our Own
26 -- 29W. Michael McCracken. Counterpoint: SE Education: What Academia Can Do
31 -- 36Stephen R. Tockey. A Missing Link in Software Engineering
37 -- 43Ray Dawson, Ron W. Newsham. Introducing Software Engineers to the Real World
44 -- 48Thomas B. Hilburn. SE Education: A Modest Proposal
49 -- 57Kathy Beckman, Neal S. Coulter, Soheil Khajenoori, Nancy R. Mead. Collaborations: Closing the Industry-Academia Gap
58 -- 65Gerald M. Powell, Jorge L. Díaz-Herrera, Dennis J. Turner. Achieving Synergy in Collaborative Education
66 -- 70Philip W. Dart, Lorraine Johnston, Cameron Schmidt, Liz Sonenberg. Developing an Accredited Software Engineering Program
71 -- 76Les Hatton. ::::N::::-Version Design vs. One Good Version
77 -- 82Christof Ebert, Tomoo Matsubara, Todd Webb, Mauro Pezzè, Olav W. Bertelsen. The Road to Maturity: Navigating Between Craft and Science
89 -- 91Robin Jeffries. Interface: Designing Interfaces for Programmers
92 -- 98Jess Thompson. Toolbox: Avoiding a Middleware Muddle
99 -- 102Adam A. Porter, Lawrence G. Votta. Quality Time: What Makes Inspections Work?
105 -- 108Lawrence H. Putnam, Ware Myers. Manager: How Solved is the Cost-Estimation Problem?
127 -- 128Steve McConnell. Best Practices: Achieving Leaner Software

Volume 14, Issue 5

5 -- 6Alan M. Davis. From The Editor: Between Scylla and Charybdis
19 -- 21Carlo Pescio. Soapbox: When Past Solutions Cause Future Problems
22 -- 25Erika Kindlund. Interface: Navigating The Applet-Browser Divide
26 -- 0Robert Cochran. Insider: The Mousetrap Paradigm
27 -- 32Charles P. Pfleeger, Deborah M. Cooper. Guest Editors Introduction: Security and Privacy: Promising Advances
35 -- 42Andrew P. Kosoresow, Steven A. Hofmeyr. Intrusion Detection via System Call Traces
43 -- 51Nicholas J. Puketza, Mandy Chung, Ronald A. Olsson, Biswanath Mukherjee. A Software Platform for Testing Intrusion Detection Systems
52 -- 59Nayeem Islam, Rangachari Anand, Trent Jaeger, Josyula R. Rao. A Flexible Security System for Using Internet Content
60 -- 66James P. Anderson, Sheila Brand, Li Gong, Thomas Haigh, Steven B. Lipner, Teresa F. Lunt, Ruth Nelson, William Neugent, Hilarie K. Orman, Marcus J. Ranum, Roger R. Schell, Eugene H. Spafford. Firewalls: An Expert Roundtable
67 -- 74Joachim Karlsson, Kevin Ryan. A Cost-Value Approach for Prioritizing Requirements
75 -- 81Michael Diaz, Joseph Sligo. How Software Process Improvement Helped Motorola
83 -- 92Martin R. Stytz, Terry Adams, Brian Garcia, Steven M. Sheasby, Brian Zurita. Rapid Prototyping for Distributed Virtual Environments
93 -- 100Bo Sanden. Modeling Concurrent Software
101 -- 105Robert V. Binder. Quality Time: Can A Manufacturing Quality Model Work for Software?
103 -- 105Christopher M. Lott. Manager: Breathing New Life Into The Waterfall Model
119 -- 120Steve McConnell. Best Practices: Tool Support for Project Tracking

Volume 14, Issue 4

4 -- 0Alan M. Davis. From the Editor: Software s Future Is in the Cards
15 -- 17Robert L. Glass. Soapbox: Telling Good Numbers from Bad Ones
18 -- 0Maarten Boasson. Insider: The Foolishness of Fashion
21 -- 24Andrew Sears, Arnold M. Lund. Guest Editors Introduction: Creating Effective User Interfaces
26 -- 28Wayne D. Gray. Discount Usability - Point: Who Ya Gonna Call? You re on Your Own
27 -- 28Jakob Nielsen. Discount Usability - Counterpoint: Something Is Better than Nothing
29 -- 39Laura A. Valaer, Robert G. Babb II. Choosing A User Interface Development Tool
40 -- 47Angel R. Puerta. A Model-Based Interface Development Environment
51 -- 57Dave Roberts, Dick Berry, Scott Isensee, John Mullaly. Developing Software Using OVID
58 -- 65Michael G. Morris, Andrew Dillon. How User Perceptions Influence Software Use
66 -- 72Catherine Plaisant, Anne Rose, Ben Shneiderman, Ajit J. Vanniamparampil. Low-Effort, High-Payoff User Interface Reengineering
73 -- 83Jeffrey M. Voas, Frank Charron, Gary McGraw, Keith W. Miller, Michael Friedman. Predicting How Badly Good Software Can Behave
84 -- 92Wilhelm Rossak, Vassilka Kirova, Leon Jololian, Harold W. Lawson, Tamar Zemel. A Generic Model for Software Architectures
93 -- 95Jeffrey M. Voas. Quality Time: Can Clean Pipes Produce Dirty Water?
96 -- 97Brian Henderson-Sellers. Manager: OO Project Management: The Need for Process
98 -- 99Jakob Nielsen. Interface: Learning from the Real World
107 -- 113David Sharon. Toolbox: Year 2000 Tool Classification Scheme
119 -- 120Steve McConnell. Best Practices: The Programmer Writing

Volume 14, Issue 3

4 -- 6Alan M. Davis. From The Editor: Words of Wisdom
15 -- 16Bashar Nuseibeh. Soapbox: Ariane 5: Who Dunnit?
17 -- 19Barry W. Boehm, Tom DeMarco. Guest Editors Introduction: Software Risk Management
20 -- 22Tim Lister. Point: Risk Management Is Project Management for Adults
21 -- 24Marvin J. Carr. Counterpoint: Risk Management May Not Be for Everyone
25 -- 34Paul R. Garvey, Douglas J. Phair, John A. Wilson. An Information Architecture for Risk Assessment and Management
35 -- 41Tony Moynihan. How Experienced Project Managers Assess Risk
43 -- 50Robert N. Charette, Kevin MacG. Adams, Mary B. White. Managing Risk in Software Maintenance
51 -- 59Raymond J. Madachy. Heuristic Risk Assessment Using Cost Factors
61 -- 68Kari Känsälä. Integrating Risk Assessment with Cost Estimation
69 -- 74Barbara A. Kitchenham, Stephen G. Linkman. Estimates, Uncertainty, and Risk
75 -- 82Raymond C. Williams, Julie A. Walker, Audrey J. Dorofee. Putting Risk Management Into Practice
83 -- 89Edmund H. Conrow, Patricia S. Shishido. Implementing Risk Management on Software Intensive Projects
90 -- 101Igor Tartalja, Veljko M. Milutinovic. Classifying Software-Based Cache Coherence Solutions
102 -- 104Shari Lawrence Pfleeger. Quality Time: Guidelines for Applying Research Results
105 -- 106Karl Dakin. Softlaw: Software Engineer ? Time Will Tell
107 -- 109Brian Lawrence, Bob Johnson. Manager: The Project Scoping Gamble
110 -- 111Jakob Nielsen. Interface: Let s Ask the Users
135 -- 136Steve McConnell. Best Practices: Gauging Software Readiness with Defect Tracking

Volume 14, Issue 2

6 -- 8James Sanders. From the Editor: Product, Not Process: A Parable
14 -- 16Boris Beizer. Soapbox: Cleanroom Process Model: A Critical Examination
18 -- 20Ben Shneiderman. Interface: A Framework for Search Interfaces
25 -- 26Shari Lawrence Pfleeger. Guest Editor s Introduction: Assessing Measurement
28 -- 30Sean Furey. Point: Why We Should Use Function Points
29 -- 31Barbara A. Kitchenham. Counterpoint: The Problem with Function Points
33 -- 44Shari Lawrence Pfleeger, D. Ross Jeffery, Bill Curtis, Barbara A. Kitchenham. Status Report on Software Measurement
45 -- 53Raymond J. Offen, D. Ross Jeffery. Establishing Software Measurement Programs
55 -- 65Tracy Hall, Norman E. Fenton. Implementing Effective Software Metrics Programs
67 -- 75Dik Lun Lee, Huei Chuang, Kent E. Seamons. Document Ranking and the Vector-Space Model
77 -- 87Karama Kanoun, Mohamed Kaâniche, Jean-Claude Laprie. Qualitative and Quantitative Reliability Assessment
89 -- 97Les Hatton. Reexamining the Fault Density-Component Size Connection
99 -- 106Colin J. Fidge, Peter Kearney, Mark Utting. A Formal Method for Building Concurrent Real-Time Software
107 -- 117Xiping Song. Systematic Integration of Design Methods
118 -- 122Jeffrey M. Voas. Quality Time: How Assertions Can Increase Test Effectiveness
120 -- 122Gene Forte. Manager: Managing Change for Rapid Development
123 -- 127David Sharon, Tracey Anderson. Toolbox: A Complete Software Engineering Environment; Top Drawer
139 -- 142Cem Kaner, Brian Lawrence. Softlaw: UCC Changes Pose Problems for Developers
143 -- 144Steve McConnell. Best Practices: Software s Ten Essentials

Volume 14, Issue 1

4 -- 5Alan M. Davis. From the Editor: Why Build Software?
15 -- 17Charles P. Pfleger. Quality Time: The Fundamentals of Information Security
18 -- 19Don O Neil. Soapbox: Issues in Software Inspection
20 -- 21Karl Dakin. Softlaw: What If There Were No Software Piracy?
22 -- 24Brad Cox. Manager: Superdistribution and the Economics of Bits
26 -- 0Sadakazu Watanabe. Insider: Professionalism through OO and Reuse
27 -- 30Stephen J. Mellor, Ralph E. Johnson. Guest Editor s Introduction: Why Explore Object Methods, Patterns, and Architectures?
31 -- 35William M. Tepfenhart, James J. Cusick. A Unified Object Topology
36 -- 42James Coplien. Idioms And Patterns As Architectural Literature
43 -- 52Robert T. Monroe, Andrew Kompanek, Ralph E. Melton, David Garlan. Architectural Styles, Design Patterns, And Objects
53 -- 59Norman L. Kerth, Ward Cunningham. Using Patterns To Improve Our Architectural Vision
61 -- 72Sally Shlaer, Stephen J. Mellor. Recursive Design of an Application-Independent Architecture
73 -- 85Luqi, Joseph A. Goguen. Formal Methods: Promises And Problems
94 -- 95Jakob Nielsen. Interface: The Use and Misuse of Focus Groups
98 -- 102Alan Schamp, Heidi Schamp. Toolbox: Successfully Implementing Configuration Management; Top Drawer
103 -- 104Steve McConnell. Best Practices: Annualized Software Delivery