Formalization in systems development

  • Lars Mathiassen
  • Andreas Munk-Madsen
Colloquium On Software Engineering Concepts And Methods In Software Development
Part of the Lecture Notes in Computer Science book series (LNCS, volume 186)


Formalizations are related both to types of expression and to types of behaviour. The limits to applying formalizations in these two senses are discussed and illustrated by examples from practical systems development. It will be established that formalizations are valuable in some situations, but insufficient in others. The alternative to uncritically using formalizations is that system developers analyse the situations in which they find themselves, and from there choose a combination of a formal and an informal approach.


System Development System Developer Work Process Production Planner Throughput Time 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. Boehm, B.W. (1981). Software Engineering Economics. Prentice-Hall.Google Scholar
  2. Brooks, F.P. jr. (1982). The Mythical Man-Month. Addison-Wesley.Google Scholar
  3. Davis, G.B. (1982). Strategies for Information Requirements Determination. IBM Systems Journal, 21. pp. 4–30.Google Scholar
  4. Floyd, C. (1984). A Systematic Look at Prototyping. In Budde,R. et al (Eds.) Approaches to Prototyping. Springer-Verlag.Google Scholar
  5. Freedman, D.P., Weinberg, G.M. (1982). Handbook of Walkthroughs, Inspections, and Technical Reviews. Little, Brown and Co.Google Scholar
  6. Jackson, M.A. (1975). Principles of Program Design. Academic Press.Google Scholar
  7. Jackson, M.A. (1983). System Development. Prentice-Hall.Google Scholar
  8. Kraft, P. (1977). Programmers and Managers. Springer-Verlag.Google Scholar
  9. Lanzara, G.F., Mathiassen, L. (1984). Mapping Situations within a System Development Project. University of Aarhus, DAIMI PB-179.Google Scholar
  10. March, J.G., Simon, H.A. (1958). Organizations. Wiley.Google Scholar
  11. Mathiassen, L. (1981). Systems Development and Systems Development Method. University of Aarhus, DAIMI PB-136 (in Danish).Google Scholar
  12. Munk-Madsen, A. (1984). Practical Problems of System Development Projects. In Sääksjärvi, M. (Eds.). Proceedings of the Seventh Scandinavian Research Seminar on Systemeering. (To appear).Google Scholar
  13. Naur, P., (1982). Formalization in Program Development. BIT, 22, pp. 437–453.Google Scholar
  14. Polya, G. (1957). How to Solve It. Doubleday and Company.Google Scholar
  15. Weinberg, G.M. (1982). Overstructured Management of Software Engineering. Course notes for Problem Solving Leadership Workshop.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1985

Authors and Affiliations

  • Lars Mathiassen
    • 1
  • Andreas Munk-Madsen
    • 1
  1. 1.Computer Science DepartmentUniversity of AarhusDenmark

Personalised recommendations