The role of abstraction in software engineering

ABSTRACT

This workshop focuses on the concept of abstraction in software engineering. The aim is to explore the role of abstraction in dealing with complexity in the software engineering process, to discuss how the use of different levels of abstraction may facilitate performance of different activities, and to examine whether abstraction skills can be taught.

REFERENCES

• 1: Keith Devlin, Introduction, Communications of the ACM, v.46 n.9, September 2003 [doi>10.1145/903893.903917]
• 2: Orit Hazzan, The reflective practitioner perspective in software engineering education, Journal of Systems and Software, v.63 n.3, p.161-171, 15 September 2002 [doi>10.1016/S0164-1212(02)00012-2]
• 3: Jeff Kramer, Is abstraction the key to computing?, Communications of the ACM, v.50 n.4, p.36-42, April 2007 [doi>10.1145/1232743.1232745]
• 4: Jeff Kramer , Orit Hazzan, The Role of Abstraction in Software Engineering, ACM SIGSOFT Software Engineering Notes, v.31 n.6, p.38-39, November 2006 [doi>10.1145/1218776.1226833]
• 5: Barbara Liskov, Abstraction and specification in program development, MIT Press, Cambridge, MA, 1986

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.0 General

General Terms:
Human Factors, Management

Keywords:
abstraction, cognition, management, organizational learning., software engineering processes