cst-1b-sweng (1)

cst-1b-sweng (1) - Software Engineering CST 1b Ross...

Info iconThis preview shows pages 1–11. Sign up to view the full content.

View Full Document Right Arrow Icon
Software Engineering CST 1b Ross Anderson
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Aims Introduce students to software enginering, and in particular to the problems of building large systems building safety-critical systems building real-time systems Illustrate what goes wrong with case histories Study software engineering practices as a guide to how mistakes can be avoided
Background image of page 2
Objectives At the end of the course you should know how writing programs with tough assurance targets, or in large teams, or both, differs from the programming exercises done so far. You should appreciate the waterfall, spiral and evolutionary models of development and be able to explain which kinds of software development might profitably use them
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Objectives (2) You should appreciate the value of other tools and the difference between incidental and intrinsic complexity You should understand the basic economics of the software development lifecycle You should also be prepared for the organizational aspects of your part 1b group project, for your part 2 project, and for courses in systems, security etc
Background image of page 4
Resources Recommended reading: S Maguire, Debugging the Development Process N Leveson, Safeware (see also her ‘System Safety Engineering’ online) SW Thames RHA, Report of the Inquiry into the London Ambulance Service RS Pressman, Software Engineering Usenet newsgroup comp.risks
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Resources (2) Additional reading: FP Brooks, The Mythical Man Month J Reason, The Human Contribution P Neumann, Computer Related Risks R Anderson, Security Engineering 2e, ch 25–6, or 1e ch 22–23 Also: I recommend wide reading in whichever application areas interest you
Background image of page 6
Outline of Course The ‘Software Crisis’ How to organise software development Guest lecture on current industrial practice Critical software Tools Large systems
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
The ‘Software Crisis’ Software lags far behind the hardware’s potential! Many large projects fail in that they’re late, over budget, don’t work well, or are abandoned (LAS, CAPSA, NPfIT, …) Some failures cost lives (Therac 25) or cause large material losses (Arianne 5) Some cause expensive scares (Y2K, Pentium) Some combine the above (LAS)
Background image of page 8
The London Ambulance Service System Commonly cited example of project failure because it was very thoroughly documented Attempt to automate ambulance dispatch in 1992 failed conspicuously with London being left without service for a day Hard to say how many deaths could have been avoided; estimates ran as high as 20 Led to CEO being sacked, public outrage
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Original System 999 calls written on paper tickets; map reference looked up; conveyor to central point Controller deduplicates and passes to three divisions NW / NW / S Division controller identifies vehicle and puts not in its activation box Ticket passed to radio controller This all takes about 3 minutes and 200 staff of 2700 total. Some errors (esp. deduplication), some queues (esp. radio), call-backs tiresome
Background image of page 10
Image of page 11
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 124

cst-1b-sweng (1) - Software Engineering CST 1b Ross...

This preview shows document pages 1 - 11. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online