Skip to main content
SpringerLink
Log in

Editorial: The Role of Prognostication in Software Design

  • Editorial Introduction
  • Published:
Software Quality Journal Aims and scope Submit manuscript

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

References

  • Bieman, J. 2002. Why good software goes bad, Software Quality Journal 10(3): 201-203.

    Google Scholar 

  • Bieman, J., Jain, D., and Yang, H. 2001. Design patterns, design structure, and program changes: An industrial case study, Proceedings of International Conference on Software Maintenance (ICSM 2001).

  • Bieman, J., Straw, G., Wang, H., and Alexander, R. 2003. Design patterns and change proneness: An examination of five evolving systems, Proceedings of Tenth International Software Metrics Symposium (Metrics 2003), pp. 40-49.

  • Fowler, M. 1999. Refactoring: Improving the Design of Existing Code. Reading, MA, Addison-Wesley.

    Google Scholar 

  • Gamma, E., Helm, R., Johnson, R., and Vlissides, J. 1995. Design Patterns: Elements of Reusable Object-Oriented Software. Reading, MA, Addison-Wesley.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Fort Collins, CO, USA

    James Bieman

Authors
  1. James Bieman
    View author publications

    You can also search for this author in PubMed Google Scholar

Rights and permissions

Reprints and permissions

About this article

Cite this article

Bieman, J. Editorial: The Role of Prognostication in Software Design. Software Quality Journal 12, 7–8 (2004). https://doi.org/10.1023/B:SQJO.0000013408.06186.a6

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1023/B:SQJO.0000013408.06186.a6

Search

Navigation