Linguistic continuity in software engineering

ABSTRACT

Many different concerns contribute to the complexity of software development. Some of these concerns are easy to spot. Others are right in front of us all along but not explicitly identified in a way that makes them intellectually accessible. We describe an idea that has always been in the background of awareness for programmers and software designers, but which seldom gets sufficient acknowledgement to be written about on its own. We call this linguistic [dis]continuity.

REFERENCES

• 1: Bertrand Meyer, Object-oriented software construction (2nd ed.), Prentice-Hall, Inc., Upper Saddle River, NJ, 1997
• 2: (KOLL) Kolln, Martha J. and Funk, Robert W., Understanding English Grammar, Longman, 2006
• 3: Donald C. Gause , Gerald M. Weinberg, Exploring Requirements: Quality Before Design, Dorset House Publishing Co., Inc., New York, NY, 1989
• 4: Jim Woodcock , Martin Loomes, Software engineering mathematics, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1990
• 5: Jim Inglis, COBOL 85 for programmers, John Wiley & Sons, Inc., New York, NY, 1989
• 6: Robert W. Sebesta, Concepts of Programming Languages, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2003
• 7: (GAN) Ganguly, Pronab, Rabhi, Fethi, and Ray, Pradeep K, "Bridging the Semantic Gap," Australian Computer Society, http://crpit.com/confpapers/
• 8: (EMP) Empson, William, Seven Types of Ambiguity, W. W. Norton, 1966, Third Edition
• 9: James Rumbaugh , Ivar Jacobson , Grady Booch, Unified Modeling Language Reference Manual, The (2nd Edition), Pearson Higher Education, 2004

INDEX TERMS

Primary Classification:
  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management
          Subjects: Software development

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.9 Management
          Subjects: Programming teams
      D.2.m Miscellaneous

General Terms:
Algorithms, Theory