Presentation is loading. Please wait.

Presentation is loading. Please wait.

Has Brian Kernighan’s thoughts on prototype vs. production programming.

Similar presentations


Presentation on theme: "Has Brian Kernighan’s thoughts on prototype vs. production programming."— Presentation transcript:

1 Has Brian Kernighan’s thoughts on prototype vs. production programming

2 M.Tech. Research Project Programming IInd. M.Tech. (CS) Research Oriented Project Scenario Research is Crucial Study research papers, innovate, try to publish paper(s) (usually conference paper) Prototype level software is enough to produce results needed for publications Prototype to Production quality software typically not concern of Academics

3 M.Tech. Software Development Project Programming IInd. M.Tech. (CS) Software Development Project Scenario Nowadays academics look down upon such projects at Masters level (M.Tech. level) as it does not have research component. However, AICTE guidelines seem to allow for such projects if significant design & programming work suitable for a Masters project is involved

4 M.Tech. Software Development Project Programming - 2 IInd. M.Tech. (CS) Software Development Project Scenario (Contd.) Design & Programming can be of higher quality than M.Tech. research project but still will not match industry (production) quality.

5 Industry Software Development and Research Scenarios Industry Software Development Scenario Production Quality Software Required Important to get Design of Software done well. Very important to get program working properly Industry Software Research Scenario May not need production quality software I don’t have enough exposure to Industry Research field to comment further

6 Brian Kernighan says From interview with Brian Kernighan in July 2003. (http://www.linuxjournal.com/article/7035) Research programming might mean software written as a prototype or [used] to verify that some concept can be made to work. There, the difference is that one can cut lots of corners : don't worry about errors, ignore potential hazards, provide no user interface, skip documentation and, of course, do no maintenance.

7 Brian Kernighan says … In that sense, research programming is vastly easier than writing a program that will be used by many people over a long period of time. Someone (Fred Brooks, in The Mythical Man Month, perhaps) once said that it is at least an order of magnitude more work to do production software than a prototype. I think he's wrong ……

8 Brian Kernighan says …. Someone (…) once said that it is at least an order of magnitude more work to do production software than a prototype. I think he's wrong by at least an order of magnitude.

9 Bug Impact on F-22 Raptor F-22 ‘Raptor’ Stealth Fighter plane reportedly had, sometime in Feb. 2007 (http://it.slashdot.org/story/07/02/25/2038217/sof tware-bug-halts-f-22-flight): A Software Glitch on crossing International Date Line On-board computers crashed Completely lost all navigation and communications Had to follow tankers by visual contact back to Hawaii


Download ppt "Has Brian Kernighan’s thoughts on prototype vs. production programming."

Similar presentations


Ads by Google