081015slides_handouts

081015slides_handouts - 1 UVa CS205 Engineering Software...

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

View Full Document Right Arrow Icon

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

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

Unformatted text preview: 1 UVa CS205 Engineering Software 2007 Design UVa CS205 Engineering Software 2007 How should we evaluate designs? UVa CS205 Engineering Software 2007 Design Criteria ¡ Human Understandability ¡ Cost/Time to Implement ¡ Independence of Modules ¢ Decoupled modules can be developed and tested independently ¡ Ability to Change ¢ Requirements for software change, poorly designed software is hard/impossible to change UVa CS205 Engineering Software 2007 How should we document designs? 2 UVa CS205 Engineering Software 2007 Modular Dependency Diagrams ¡ Show the component modules ¢ How is the program organized? ¡ Show the dependencies between them ¢ How do modules depend on each other? ¡ Why do we want to know? UVa CS205 Engineering Software 2007 Using MDDs ¡ Design Time ¢ Consider different designs ¢ If the MDD has lots of cycles, crossings, etc. the design is not decoupled enough ¡ Implementation ¢ Organize the implementation ¡ Testing ¢ Where do you look when a test fails?...
View Full Document

This note was uploaded on 04/05/2010 for the course CS 150 taught by Professor Humphreys,g during the Spring '08 term at UVA.

Page1 / 5

081015slides_handouts - 1 UVa CS205 Engineering Software...

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

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