Download PDF
Methods Inf Med 1989; 28(04): 295-303
DOI: 10.1055/s-0038-1636805
Original Article
Schattauer GmbH

Software Engineering Education in Medical Informatics

F. J. Leven
1   Studiengang Medizinische Informatik, Universität Heidelberg/Fachhochschule Heilbronn, Heilbronn, F. R. G.
› Author Affiliations
Further Information

Publication History

Publication Date:
17 February 2018 (online)

    Permissions and Reprints

Abstract:

Requirements and approaches of Software Engineering education in the field of Medical Informatics are described with respect to the impact of (1) experiences characterizing the “software misery”, (2) status and tendencies in software methodology, and (3) educational status and needs in computer science education influenced by the controversy “theoretical versus practical education”. Special attention is directed toward the growing importance of analysis, design methods, and techniques in the professional spectrum of Medical Informatics, the relevance of general principles of systems engineering in health care, the potential of non-procedural programming paradigms, and the intersection of Artificial Intelligence and education. Realizations of and experiences with programs in the field of Software Engineering are reported with respect to special requirements in Medical Informatics.

Key-Words:

Information Systems - Software Engineering - Education - Curriculum
 

  • REFERENCES

  • [1] Blum B. Clinical Information Systems. New York: Springer Verlag 1986
    PubMedGoogle Scholar
  • [2] Boehm BW. Understanding and controlling software costs. In: Kugler HJ, ed. Information Processing 86. Amsterdam: North Holland Publ Comp 1986: 703-714.
    PubMedGoogle Scholar
  • [3] Levy LS. Taming the Tiger: Software Engineering and Software Economics. Berlin: Springer Verlag 1987
    PubMedGoogle Scholar
  • [4] Blum B. The TEDIUM development environment for information systems. IEEE Software 1987; 3: 25-34.
    PubMedGoogle Scholar
  • [5] Biggerstaff T, Richter C. Reusability framework, assessment and directions. IEEE Software 1987; 3: 41-64.
    PubMedGoogle Scholar
  • [6] Cox BJ. Object Oriented Programming. Reading Mass: Addison-Wesley 1986
    PubMedGoogle Scholar
  • [7] Simonsmeier W. Der CASE-Markt im Aufbruch. Computer Magazin 1988; 07/08: 41-44.
    PubMedGoogle Scholar
  • [8] Simon HA. Whether software engineering needs to be artificially intelligent. IEEE Trans Softw Eng 1985; 11: 726-732.
    PubMedGoogle Scholar
  • [9] Reichertz PL. Preparing for change. Comp Meth Progr Biofaed 1987; 25: 89-102.
    PubMedGoogle Scholar
  • [10] Martin J. Computer science education today: a dialogue. Comm ACM 1985; 3: 251-262.
    PubMedGoogle Scholar
  • [11] Van Bemmel JH. Curricula in medical informatics. In: Pages JC, Levy AH, Grémy F, Anderson J, eds. Meeting the Challenge: Informatics and Medical Education. Amsterdam: North Holland Publ Comp 1983: 55-65.
    PubMedGoogle Scholar
  • [12] Wasserman AI, Gutz S. The future of programming. CACM 1982; 3: 196-206.
    PubMedGoogle Scholar
  • [13] Fairley R. Draft Report on MSE-80: A Graduate Program in Software Engineering, Rept IEEE Computer Society Education Committee. 1980
    PubMedGoogle Scholar
  • [14] Cerri SA. The intersection of AI and education. In: Trappl R, ed. Impacts of Artificial Intelligence. Amsterdam: North Holland Publ Comp 1985: 78-88.
    PubMedGoogle Scholar
  • [15] Nunamaker JF, Couger JD, Davis GB. Information systems curriculum recommendations for the 1980’s. Comm ACM 1982; 11: 781-805.
    PubMedGoogle Scholar
  • [16] Protti D. A comparative analysis of the German Informatiker der Medizin Diplom and the Canadian Bachelor of Science in Health Information Science. In: Pagès JC, Levy AH, Grémy F, Anderson J, eds. Meeting the Challenge: Informatics and Medical Education. Amsterdam: North Holland Publ Comp 1983: 135-141.
    PubMedGoogle Scholar
  • [17] Freeman P, Wasserman AI, Fairley RE. Essential elements of software engineering education. Proc 2nd Intern Conf Software Eng 1976
    PubMedGoogle Scholar
  • [18] Freeman P. Essential elements of Software Engineering education revisited. IEEE Trans Softw Eng. 1987 IT. 1143-1148.
    PubMedGoogle Scholar
  • [19] Gibbs NE, Fairley RE. Software Engineering Education. Berlin: Springer Verlag 1987
    PubMedGoogle Scholar
  • [20] Fairley R, Freeman P. Educational Issues in Software Engineering. Berlin: Springer Verlag 1988
    PubMedGoogle Scholar
  • [21] Fairley R. Software engineering education: an idealized scenario. In: Gibbs NE, Fairley RE, eds. Software Engineering Education. Berlin: Springer Verlag 1987: 52-60.
    PubMedGoogle Scholar
  • [22] Werth LH. Software engineering education. A survey of current courses. ACM SIGSOFT Software Eng Notes 1987; 12: 19-26.
    CrossrefPubMedGoogle Scholar
  • [23] Leventhal LM, Mynatt BT. Components of typical undergraduate software engineering courses. IEEE Software 1987; 11: 1193-1198.
    PubMedGoogle Scholar
  • [24] Hoffman D. An undergraduate course in software design. In: Ford G, ed. Lecture Notes in Computer Science (Nr 327). New York: Springer Verlag 1988: 154-168.
    PubMedGoogle Scholar
  • [25] Ardis MA. The evolution of Wang Institute’s Master of Software Engineering Program. IEEE Trans Softw Eng 1987; 11: 1149-1155.
    PubMedGoogle Scholar
  • [26] LeVen EI, Klauck U. A specialized curriculum for education in medical informatics. Victoria BC: Proceedings Conference on Medical Informatics and Education; 1989: 552-557.
    Google Scholar