CSCE 3612 ch9-1

CSCE 3612 ch9-1 - System design techniques Design...

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

View Full Document Right Arrow Icon
© 2008 Wayne Wolf Overheads for Computers as Components 2 nd ed. System design techniques Design methodologies. Requirements and specification.
Background image of page 1

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

View Full DocumentRight Arrow Icon
© 2008 Wayne Wolf Overheads for Computers as Components 2 nd ed. Design methodologies Process for creating a system. Many systems are complex: large specifications; multiple designers; interface to manufacturing. Proper processes improve: quality; cost of design and manufacture.
Background image of page 2
© 2008 Wayne Wolf Overheads for Computers as Components 2 nd ed. Product metrics Time-to-market: beat competitors to market; meet marketing window (back-to-school). Design cost. Manufacturing cost. Quality.
Background image of page 3

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

View Full DocumentRight Arrow Icon
© 2008 Wayne Wolf Overheads for Computers as Components 2 nd ed. Mars Climate Observer Lost on Mars in September 1999. Requirements problem: Requirements did not specify units.  Lockheed Martin used English; JPL wanted  metric. Not caught by manual inspections.
Background image of page 4
© 2008 Wayne Wolf Overheads for Computers as Components 2 nd ed. Design flow Design flow : sequence of steps in a  design methodology. May be partially or fully automated. Use tools to transform, verify design. Design flow is one component of  methodology. Methodology also includes  management organization, etc.
Background image of page 5

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

View Full DocumentRight Arrow Icon
© 2008 Wayne Wolf Overheads for Computers as Components 2 nd ed. Waterfall model Early model for software development: requirements architecture coding testing maintenance
Background image of page 6
© 2008 Wayne Wolf Overheads for Computers as Components 2 nd ed. Waterfall model steps Requirements: determine basic  characteristics. Architecture: decompose into basic  modules. Coding: implement and integrate. Testing: exercise and uncover bugs. Maintenance: deploy, fix bugs, upgrade.
Background image of page 7

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

View Full DocumentRight Arrow Icon
© 2008 Wayne Wolf Overheads for Computers as Components 2 nd ed. Waterfall model critique Only local feedback---may need iterations  between coding and requirements, for  example. Doesn’t integrate top-down and bottom-up  design. Assumes hardware is given.
Background image of page 8
© 2008 Wayne Wolf Overheads for Computers as Components 2 nd ed. Spiral model requirements design test system feasibility specification prototype initial system enhanced system
Background image of page 9

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

View Full DocumentRight Arrow Icon
© 2008 Wayne Wolf Overheads for Computers as Components 2 nd ed. Spiral model critique Successive refinement of system.
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.

This note was uploaded on 09/30/2008 for the course CSCE 3612 taught by Professor Goodrum during the Fall '08 term at North Texas.

Page1 / 39

CSCE 3612 ch9-1 - System design techniques Design...

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