Penguin
Diff: SoftwareEngineering
EditPageHistoryDiffInfoLikePages

Differences between current version and predecessor to the previous major change of SoftwareEngineering.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 10 Last edited on Friday, March 10, 2006 9:14:30 am by DavidHallett
Older page: version 4 Last edited on Sunday, November 30, 2003 2:35:46 pm by CraigBox Revert
@@ -1,33 +1,41 @@
-The supposed engineering discipline of software creation. 
+The supposed engineering discipline of [Software] creation. 
  
 SoftwareEngineering differs from ComputerScience in that it favours reliability, stability and usefulness over novelty. The general approach is usually to start with a small, working, system and incrementally add features and fix [Bug]s as they arise. 
  
-There are a number of important techniques and approaches in SoftwareEngineering, incluing :  
-!!!Design  
-# FlowDiagram  
-# DataDictionary  
-# [UML]  
-# Specifications  
+There are a number of important techniques and approaches in SoftwareEngineering, including (none of these lists is anywhere near complete)
  
-!!!Testing  
-#RegressionTesting  
-#UnitTesting  
-#  
+!!! Design  
  
-!!!ToolSupport  
-# Code generation tools: [Compiler ]s, [CompilerCompiler]s  
-# BugZilla  
-# ...  
+* Flow Diagram  
+* Data Dictionary  
+* [UML ]  
+* Specifications  
  
+!!! Testing  
+  
+* RegressionTesting  
+* UnitTesting  
+  
+!!! Tool Support  
+  
+* Code generation tools: [Compiler]s, [CompilerCompiler]s  
+* BugZilla  
+  
+!!! Methodologies  
+  
+* [Literate Programming | http://www.literateprogramming.com]  
+* [Elemental Programming | http://www.elemental-programming.org]  
+* [Extreme Programming | http://www.extremeprogramming.org]  
+* Agile Software Development  
  
 ---- 
-A Software Engineer, a Hardware Engineer and a Departmental Manager were on their way to a meeting in Switzerland. They were driving down a steep mountain road when suddenly the brakes on their car failed. The car careened almost out of control down the road, bouncing off the crash barriers, until it miraculously ground to a halt scraping along the mountainside. The car's occupants, shaken but unhurt, now had a problem: they were stuck halfway down a mountain in a car with no rakes . What were they to do? 
+  
+ A Software Engineer, a Hardware Engineer and a Departmental Manager were on their way to a meeting in Switzerland. They were driving down a steep mountain road when suddenly the brakes on their car failed. The car careened almost out of control down the road, bouncing off the crash barriers, until it miraculously ground to a halt, scraping along the mountainside. The car's occupants, shaken but unhurt, now had a problem: they were stuck halfway down a mountain in a car with no brakes . What were they to do? 
  
 "I know", said the Departmental Manager, "Let's have a meeting, propose a Vision, formulate a Mission Statement, define some Goals, and by a process of Continuous Improvement, Change Management, Re-Engineering and Service Integration, find a solution to the Critical Problems, and we can be on our way." 
  
-"No, no", said the Hardware Engineer, "That will take far too long, and besides, that method has never worked before. I've got my Swiss Army knife with me, and in no time at all I can strip  
- down the car's braking system, isolate the fault, fix it, and we can be on our way." 
+"No, no", said the Hardware Engineer, "That will take far too long, and besides, that method has never worked before. I've got my Swiss Army knife with me, and in no time at all I can strip down the car's braking system, isolate the fault, fix it, and we can be on our way." 
  
 "Well", said the Software Engineer, "Before we do anything, I think we should push the car back up the road and see if it happens again." 
  
 -- author unknown