Software Engineering in the Academy

Lokesh Khurana

doi:10.26703/jct.v6i2.328

Authors

Lokesh Khurana S.P.C. Degree College, Baghpat

DOI:

https://doi.org/10.26703/jct.v6i2.328

Keywords:

Software Engineering, Academy, Eductation

Abstract

There is no universally accepted definition of software engineering. For some, software engineering is just a glorified name for programming. If you are a programmer, you might put “software engineer” on your business card but never “programmer.” Others have higher expectations. A textbook definition of the term might read something like this: “the body of methods, tools, and techniques intended to produce quality software.” Rather than just emphasizing quality, we could distinguish software engineering from programming by its industrial nature, leading to another definition: “the development of possibly large systems intended for use in production environments, over a possibly long period, worked on by possibly many people, and possibly undergoing many changes,” where “development” includes management, maintenance, validation, documentation, and so forth.

Downloads

Download data is not yet available.

Metrics

Metrics Loading ...

References

D.L. Parnas, “Software Engineering Programmes Are Not Computer Science Programmes,” CRL Report 361, Communication Research Laboratory, McMaster Univ., Apr. 1998; to be published in Annals of Software Eng., 2001.

Information Technology of America, “Major New Study Finds Enormous Demand for IT Workers: Research Pinpoints Hot Jobs and Skills Needed, Offers Insights on Employer Preferred Training Approaches,” http://www.itaa.org/news/pr/PressRelease.cfm?ReleaseID=955379119.

. B.W. Boehm, Software Engineering Economics, Prentice Hall, Upper Saddle River, N.J., 1981.

P.G. Neumann, “Illustrative Risks to the Public in the Use of Computer Systems and Related Technology,” http://www.csl.sri.com/users/neumann/illustrative.html.

D. Tsichritzis, “The Changing Art of Computer Science Research,” in Electronic Commerce Objects, D. Tsichritzis, ed., Centre Universitaire d’Informatique, Université de Genève, 1998.

B. Meyer, Introduction to the Theory of ProgrammingLanguages, Prentice Hall, Upper Saddle River, N.J., 1990.

C. Mingins et al., “How We Teach Software Engineering,” J. Object-Oriented Programming, Feb. 1999, pp. 64-75.

B. Cohen, “The Education of the Information Systems Engineer,” Electronics & Power, Mar. 1987, pp. 203-205.

B. Meyer, Object-Oriented Software Construction, 2nd ed., Prentice Hall, Upper Saddle River, N.J., 1997.

J. Jézéquel and B. Meyer, “Design by Contract: The Lessons of Ariane,” Computer, Jan. 1997, pp. 129-130. Bertrand Meyer is chief technology officer of Interactive Software Engineering, Santa Barbara, Calif.,and an adjunct professor at Monash University, Melbourne.His books include Object-Oriented Software Construction (Prentice Hall, Upper Saddle River, N.J.,1997). Contact him at Bertrand_Meyer@eiffel.com.