aLec34_GoodDesignPrinciples

aLec34_GoodDesignPrinciples - Introduction to Embedded...

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

View Full Document Right Arrow Icon
Lecture 34.1 Design process • Requirements • Design • Development • Testing Characteristics of Good Design • Ease of understanding • Ease of implementation • Ease of testing • Ease of modification • Satisfies requirements Modularity and Abstraction • Characteristic of all design methods • Components have clearly defined inputs and outputs, and clearly stated purpose • Easy to examine each component separately • Organized so system can be investigated one part at a time client programmers who will use our software develops software that will call our functions coworkers programmers who will debug and upgrade our software develops, tests, and modifies our software. Hierarchical or Layered Design – Components at one level refine those in the level above – More abstract top levels hide detail of lower level Modules In C we equate module with program file Example : TxFifo in project SCIA 1) Collection of functions 2) Data structures and data types Header file is the function prototypes (what it does) Comments written for the user or customer Defines the interface, data types How functions are called What the functions do What values are returned? Code file is the implementation (how it works) Comments written for ourselves or our coworkers Helps to assist in debugging, and extending How the functions were tested? What assumptions were made?
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.

Page1 / 4

aLec34_GoodDesignPrinciples - Introduction to Embedded...

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