lect-9-design2 - 4/26/2011 Today 2 One brief project #1...

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

View Full Document Right Arrow Icon
4/26/2011 1 CSE503: SOFTWARE ENGINEERING DESIGN II David Notkin Spring 2011 Today One brief project #1 description Finish software design introduction Open implementation Layering/uses relation Some consequences of reality in design 503 11sp © UW CSE • D. Notkin 2 Reality: some consequences 503 11sp © UW CSE • D. Notkin 3 One commonly stated objective of good design is the ability to reason about the software system It is not always clear if this means reasoning about the structure, or reasoning about the behavior, or (most likely) both Top-down design, ADT-based design, information hiding, layering all – at least in principle – help to some degree with reasoning One reason is that there is, or there can be, a clear specification of what the system is intended to do Claim 503 11sp © UW CSE • D. Notkin 4 I claim that the basis for reasoning is in large part based on the fact that in these approaches the names relation and the invokes relation are closely related
Background image of page 1

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

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

This note was uploaded on 02/24/2012 for the course CSE 503 taught by Professor Davidnotikin during the Spring '11 term at University of Washington.

Page1 / 3

lect-9-design2 - 4/26/2011 Today 2 One brief project #1...

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

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