default search action
IEEE Software, Volume 14, 1997
Volume 14, Number 1, January/February 1997
Theme Articles
- Stephen J. Mellor, Ralph E. Johnson:
Guest Editor's Introduction: Why Explore Object Methods, Patterns, and Architectures? 27-30 - William M. Tepfenhart, James J. Cusick:
A Unified Object Topology. 31-35 - James Coplien:
Idioms And Patterns As Architectural Literature. 36-42 - Robert T. Monroe, Andrew Kompanek, Ralph E. Melton, David Garlan:
Architectural Styles, Design Patterns, And Objects. 43-52 - Norman L. Kerth, Ward Cunningham:
Using Patterns To Improve Our Architectural Vision. 53-59 - Sally Shlaer, Stephen J. Mellor:
Recursive Design of an Application-Independent Architecture. 61-72
- Luqi, Joseph A. Goguen:
Formal Methods: Promises And Problems. 73-85
- Alan M. Davis:
From the Editor: Why Build Software? 4-5 - Charles P. Pfleger:
Quality Time: The Fundamentals of Information Security. 15-17 - Don O'Neil:
Soapbox: Issues in Software Inspection. 18-19 - Karl Dakin:
Softlaw: What If There Were No Software Piracy? 20-21 - Brad Cox:
Manager: Superdistribution and the Economics of Bits. 22-24 - Sadakazu Watanabe:
Insider: Professionalism through OO and Reuse. 26 - Jakob Nielsen:
Interface: The Use and Misuse of Focus Groups. 94-95 - Alan Schamp, Heidi Schamp:
Toolbox: Successfully Implementing Configuration Management; Top Drawer. 98-102 - Steve McConnell:
Best Practices: Annualized Software Delivery. 103-104
Volume 14, Number 2, March/April 1997
Theme Articles
- Shari Lawrence Pfleeger:
Guest Editor's Introduction: Assessing Measurement. 25-26 - Sean Furey:
Point: Why We Should Use Function Points. 28-30 - Barbara A. Kitchenham:
Counterpoint: The Problem with Function Points. 29-31 - Shari Lawrence Pfleeger, D. Ross Jeffery, Bill Curtis, Barbara A. Kitchenham:
Status Report on Software Measurement. 33-44 - Raymond J. Offen, D. Ross Jeffery:
Establishing Software Measurement Programs. 45-53 - Tracy Hall, Norman E. Fenton:
Implementing Effective Software Metrics Programs. 55-65 - Dik Lun Lee, Huei Chuang, Kent E. Seamons:
Document Ranking and the Vector-Space Model. 67-75 - Karama Kanoun, Mohamed Kaâniche, Jean-Claude Laprie:
Qualitative and Quantitative Reliability Assessment. 77-87 - Les Hatton:
Reexamining the Fault Density-Component Size Connection. 89-97
- Colin J. Fidge, Peter Kearney, Mark Utting:
A Formal Method for Building Concurrent Real-Time Software. 99-106 - Xiping Song:
Systematic Integration of Design Methods. 107-117
- James Sanders:
From the Editor: Product, Not Process: A Parable. 6-8 - Boris Beizer:
Soapbox: Cleanroom Process Model: A Critical Examination. 14-16 - Ben Shneiderman:
Interface: A Framework for Search Interfaces. 18-20 - Jeffrey M. Voas:
Quality Time: How Assertions Can Increase Test Effectiveness. 118-122 - Gene Forte:
Manager: Managing Change for Rapid Development. 120-122 - David Sharon, Tracey Anderson:
Toolbox: A Complete Software Engineering Environment; Top Drawer. 123-127 - Cem Kaner, Brian Lawrence:
Softlaw: UCC Changes Pose Problems for Developers. 139-142 - Steve McConnell:
Best Practices: Software's Ten Essentials. 143-144
Volume 14, Number 3, May/June 1997
Theme Articles
- Barry W. Boehm, Tom DeMarco:
Guest Editors' Introduction: Software Risk Management. 17-19 - Tim Lister:
Point: Risk Management Is Project Management for Adults. 20-22 - Marvin J. Carr:
Counterpoint: Risk Management May Not Be for Everyone. 21-24 - Paul R. Garvey, Douglas J. Phair, John A. Wilson:
An Information Architecture for Risk Assessment and Management. 25-34 - Tony Moynihan:
How Experienced Project Managers Assess Risk. 35-41 - Robert N. Charette, Kevin MacG. Adams, Mary B. White:
Managing Risk in Software Maintenance. 43-50 - Raymond J. Madachy:
Heuristic Risk Assessment Using Cost Factors. 51-59 - Kari Känsälä:
Integrating Risk Assessment with Cost Estimation. 61-68 - Barbara A. Kitchenham, Stephen G. Linkman:
Estimates, Uncertainty, and Risk. 69-74 - Raymond C. Williams, Julie A. Walker, Audrey J. Dorofee:
Putting Risk Management Into Practice. 75-82 - Edmund H. Conrow, Patricia S. Shishido:
Implementing Risk Management on Software Intensive Projects. 83-89
- Igor Tartalja, Veljko M. Milutinovic:
Classifying Software-Based Cache Coherence Solutions. 90-101
- Alan M. Davis:
From The Editor: Words of Wisdom. 4-8 - Bashar Nuseibeh:
Soapbox: Ariane 5: Who Dunnit? 15-16 - Shari Lawrence Pfleeger:
Quality Time: Guidelines for Applying Research Results. 102-104 - Karl Dakin:
Softlaw: Software "Engineer"? Time Will Tell. 105-106 - Brian Lawrence, Bob Johnson:
Manager: The Project Scoping Gamble. 107-109 - Jakob Nielsen:
Interface: Let's Ask the Users. 110-111 - Michael Feord:
Toolbox: Testing for Millennium Risk Management. 126-133 - Steve McConnell:
Best Practices: Gauging Software Readiness with Defect Tracking. 135-136
Volume 14, Number 4, July/August 1997
Theme Articles
- Andrew Sears, Arnold M. Lund:
Guest Editors' Introduction: Creating Effective User Interfaces. 21-24 - Wayne D. Gray:
Discount Usability - Point: Who Ya Gonna Call? You're on Your Own. 26-28 - Jakob Nielsen:
Discount Usability - Counterpoint: Something Is Better than Nothing. 27-28 - Laura A. Valaer, Robert G. Babb II:
Choosing A User Interface Development Tool. 29-39 - Angel R. Puerta:
A Model-Based Interface Development Environment. 40-47 - Dave Roberts, Dick Berry, Scott Isensee, John Mullaly:
Developing Software Using OVID. 51-57 - Michael G. Morris, Andrew Dillon:
How User Perceptions Influence Software Use. 58-65 - Catherine Plaisant, Anne Rose, Ben Shneiderman, Ajit J. Vanniamparampil:
Low-Effort, High-Payoff User Interface Reengineering. 66-72
- Jeffrey M. Voas, Frank Charron, Gary McGraw, Keith W. Miller, Michael Friedman:
Predicting How Badly "Good" Software Can Behave. 73-83 - Wilhelm R. Rossak, Vassilka Kirova, Leon Jololian, Harold W. Lawson, Tamar Zemel:
A Generic Model for Software Architectures. 84-92
- Alan M. Davis:
From the Editor: Software's Future Is in the Cards. 4 - Robert L. Glass:
Soapbox: Telling Good Numbers from Bad Ones. 15-17 - Maarten Boasson:
Insider: The Foolishness of Fashion. 18 - Jeffrey M. Voas:
Quality Time: Can Clean Pipes Produce Dirty Water? 93-95 - Brian Henderson-Sellers:
Manager: OO Project Management: The Need for Process. 96-97 - Jakob Nielsen:
Interface: Learning from the Real World. 98-99 - David Sharon:
Toolbox: Year 2000 Tool Classification Scheme. 107-113 - Steve McConnell:
Best Practices: The Programmer Writing. 119-120
Volume 14, Number 5, September/October 1997
Theme Articles
- Charles P. Pfleeger, Deborah M. Cooper:
Guest Editors' Introduction: Security and Privacy: Promising Advances. 27-32 - Andrew P. Kosoresow, Steven A. Hofmeyr:
Intrusion Detection via System Call Traces. 35-42 - Nicholas J. Puketza, Mandy Chung, Ronald A. Olsson, Biswanath Mukherjee:
A Software Platform for Testing Intrusion Detection Systems. 43-51 - Nayeem Islam, Rangachari Anand, Trent Jaeger, Josyula R. Rao:
A Flexible Security System for Using Internet Content. 52-59 - James 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. 60-66
- Joachim Karlsson, Kevin Ryan:
A Cost-Value Approach for Prioritizing Requirements. 67-74 - Michael Diaz, Joseph Sligo:
How Software Process Improvement Helped Motorola. 75-81 - Martin R. Stytz, Terry Adams, Brian Garcia, Steven M. Sheasby, Brian Zurita:
Rapid Prototyping for Distributed Virtual Environments. 83-92 - Bo Ingvar Sandén:
Modeling Concurrent Software. 93-100
- Alan M. Davis:
From The Editor: Between Scylla and Charybdis. 5-6 - Carlo Pescio:
Soapbox: When Past Solutions Cause Future Problems. 19-21 - Erika Kindlund:
Interface: Navigating The Applet-Browser Divide. 22-25 - Robert Cochran:
Insider: The Mousetrap Paradigm. 26 - Robert V. Binder:
Quality Time: Can A Manufacturing Quality Model Work for Software? 101-105 - Christopher M. Lott:
Manager: Breathing New Life Into The Waterfall Model. 103-105 - Steve McConnell:
Best Practices: Tool Support for Project Tracking. 119-120
Volume 14, Number 6, November/December 1997
Theme Articles
- Nancy R. Mead, David Carter, Michael J. Lutz:
Guest Editors' Introduction: The State of Software Engineering Education and Training. 22-25 - James Bach:
Point: SE Education: We're on Our Own. 26-28 - W. Michael McCracken:
Counterpoint: SE Education: What Academia Can Do. 26-29 - Stephen R. Tockey:
A Missing Link in Software Engineering. 31-36 - Ray J. Dawson, Ron W. Newsham:
Introducing Software Engineers to the Real World. 37-43 - Thomas B. Hilburn:
SE Education: A Modest Proposal. 44-48 - Kathy Beckman, Neal S. Coulter, Soheil Khajenoori, Nancy R. Mead:
Collaborations: Closing the Industry-Academia Gap. 49-57 - Gerald M. Powell, Jorge L. Díaz-Herrera, Dennis J. Turner:
Achieving Synergy in Collaborative Education. 58-65 - Philip W. Dart, Lorraine Johnston, Cameron Schmidt, Liz Sonenberg:
Developing an Accredited Software Engineering Program. 66-70
- Les Hatton:
N-Version Design vs. One Good Version. 71-76 - Christof Ebert, Tomoo Matsubara, Todd Webb, Mauro Pezzè, Olav W. Bertelsen:
The Road to Maturity: Navigating Between Craft and Science. 77-82
- Alan M. Davis:
From the Editor: Making a Mark on the World. 4-6 - Kent Sandoe:
Soapbox: Split Ends: Labor Shortage and the CS-IS Divide. 19-21 - Robin Jeffries:
Interface: Designing Interfaces for Programmers. 89-91 - Jess Thompson:
Toolbox: Avoiding a Middleware Muddle. 92-98 - Adam A. Porter, Lawrence G. Votta:
Quality Time: What Makes Inspections Work? 99-102 - Lawrence H. Putnam, Ware Myers:
Manager: How Solved is the Cost-Estimation Problem? 105-108 - Steve McConnell:
Best Practices: Achieving Leaner Software. 127-128
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.