class_17 - Software Engineering 3156 31-Oct-01 #17:...

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

View Full Document Right Arrow Icon
Software Engineering 3156 31-Oct-01 #17: Integration and Crypto Phil Gross
Background image of page 1

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

View Full DocumentRight Arrow Icon
2 Administrivia There will be group reorganization Got a problem? Let us know ASAP Samples coming soon…
Background image of page 2
3 Requirements Tweaking Vision range Portal format Default Actor
Background image of page 3

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

View Full DocumentRight Arrow Icon
5 Implementation needs integration (I) Here, a calls b, c, and d You can’t test a until you attempt to integrate with b, c, and d Code stubs of b, c, and d For b: need driver for a, stub for e
Background image of page 5

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

View Full DocumentRight Arrow Icon
6 Stubs and drivers Essentially empty modules Usually prints debugging info Stubs Get called upon Might return a canned answer Drivers Call others Also prints some debugging
Background image of page 6
7 Implementation needs integration (II) Consider a really complex set of modules Each time you integrate, fault isolation becomes harder Additionally, possibility for faults increase Can’t work completely independently until the last day Even with OO Need to combine module and integration testing
Background image of page 7

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

View Full DocumentRight Arrow Icon
8 Implement and integrate starting from the top Create stubs for subsidiary components Fill in the stubs later Good: major fundamental flaws shown early: better to test logic first
Background image of page 8
Problems with top-down Difficult to test actual low-level functions (reusable components) The top-level gets tested n times Bottom-level gets tested once Defensive programming a liability? if (x >= 0) computeSquareRoot
Background image of page 9

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

View Full DocumentRight Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 27

class_17 - Software Engineering 3156 31-Oct-01 #17:...

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

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