Skip to main content
SpringerLink
Log in

System Implementation

  • Chapter
Clinical Information Systems

  • 34 Accesses

Abstract

The implementation of software systems follows the pattern used in all development and research activities. We go through these steps when setting up a research project, when building a bridge, or when writing computer programs. One begins with a set of needs, goals, or objectives that describes what we intend the system or activity to accomplish. This is followed by analysis that determines how we are to achieve the desired outcome. Next, there is the doing of the task, e.g., collecting laboratory data, building a bridge, or writing computer programs. Finally, there is an evaluation of the product. Naturally, the specifics of the process will differ for each class of activity.

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

Access this chapter

Log in via an institution
Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 44.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 59.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

For Further Reading

  • There are a large number of books that describe the process of software engineering. Two recent texts that cover the field are R. S. Pressman, Software Engineering: A Practitioner s Approach, McGraw-Hill, 1982,

    Google Scholar 

  • and R. W. Jensen and C. C. Tonies, Software Engineering, Prentice-Hall, 1979.

    Google Scholar 

  • The more general works on the subject are the very enjoyable F. P. Brooks Jr., The Mythical Man-Month, Addison-Wesley, 1975,

    Google Scholar 

  • the equally engaging G. M. Weinberg, The Psychology of Computer Programming, Van Nostrand, 1971,

    Google Scholar 

  • the first software psychology text by B. Schneiderman, Software Psychology: Human Factors and Information Systems, Winthrop Press, 1980,

    Google Scholar 

  • the management text by P. J. Metzer, Managing a Programming Project (second edition) Prentice-Hall, 1980

    Google Scholar 

  • and the comprehensive survey by B. W. Boehm, Software Engineering Economics, Prentice Hall, 1981.

    Google Scholar 

  • There are a large number of collections of papers. The IEEE Computer Society has quite a few excellent tutorials on topics such as design methodologies, programming productivity, testing techniques, etc. Each contains introductory material plus reprints of key papers. Some titles of particular interest are: P. Freeman and A. Wasserman, Software Design Techniques, 1980,

    Google Scholar 

  • G. Bergland and R. Gordon, Software Design Strategies, 1979,

    Google Scholar 

  • C. Jones, Programming Productivity, 1981,

    Google Scholar 

  • E. Miller, Automated Tools for Software Engineering, 1979,

    Google Scholar 

  • D. Reifer, Software Management, 1979,

    Google Scholar 

  • E. Miller, Program Testing Techniques, 1977,

    Google Scholar 

  • and G. Parikh and N. Zvegintzov, Software Maintenance, 1982. E. Your-dan also has edited two collections, Classics in Software Engineering and Writings of the Revolution, Yourdan Press, 1979 and 1982.

    Google Scholar 

  • Among the books on design methodologies are M. Jackson, System Development, Prentice Hall 1983,

    Google Scholar 

  • K. Orr, Structured Requirements Definition, Ken Orr and Assoc, 1981,

    Google Scholar 

  • T. DeMarco, Structured Analysis andSystem Specification, Prentice-Hall, 1979,

    Google Scholar 

  • and J. D. Warmer, Logical Construction of Systems, Van-Nostrand, 1981.

    Google Scholar 

  • An excellent book on testing is G. J. Myers, The Art of Software Testing, Wiley, 1979.

    Google Scholar 

  • D. Gries, The Science of Programming, Springer-Verlag, 1981 provides a readable introduction to the concepts of proofs of correctness.

    Book  Google Scholar 

  • The first three volumes of D. Knuth, The Art of Computer Programming, Addison-Wesley, 1969–1973, deal with algorithms.

    Google Scholar 

  • Another, less complete treatment, is in N. Wirth, Algorithms + Data Structures = Programs, Prentice-Hall, 1976.

    Google Scholar 

References

  1. J. E. Sammet, Language Aspects of Software Engineering, in H. Freeman and P. M. Lewis II (eds), Software Engineering, Academic Press, New York, 1980, p 181.

    Google Scholar 

  2. B. Lientz and E. Swanson, Software Maintenance Management, Addison-Wesley Publishing Co., Reading, MA, 1980, pp 151–157.

    Google Scholar 

  3. C. Jones, A Survey of Programming Design and Specification Techniques, Proceedings, Specifications of Reliable Software, IEEE, 1979, p 98.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Applied Physics Laboratory, The Johns Hopkins University, 20707, Laurel, Maryland, USA

    Bruce I. Blum

Authors
  1. Bruce I. Blum
    View author publications

    You can also search for this author in PubMed Google Scholar

Rights and permissions

Reprints and permissions

Copyright information

© 1986 Springer Science+Business Media New York

About this chapter

Cite this chapter

Blum, B.I. (1986). System Implementation. In: Clinical Information Systems. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-662-26537-6_6

Download citation

  • DOI: https://doi.org/10.1007/978-3-662-26537-6_6

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-96190-1

  • Online ISBN: 978-3-662-26537-6

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics

Search

Navigation