COMPONENT-LEVEL DESIGN

Component-level design, also called procedural design, occurs after data, architectural, and interface designs have been established

What is it ? Data, architectural, and interface design must be translated into operational software. To accomplish this, the design must be represented at a level of abstraction that is close to code.

Component-level design establishes :-
1- The algorithmic detail required to manipulate data structures,
2- Effect communication between software components via their interfaces, and
3- Implement the processing algorithms allocated to each component.

Who does it ? A software engineer performs component-level design.
Why is it important? You have to be able to determine whether the program will work before you build it. The component-level design represents the software in a way that allows you to review the details of the design for correctness and consistency with earlier design representations (i.e., the data, architectural, and interface designs). It provides a means for assessing whether data structures, interfaces, and algorithms will work.

What are the steps? Design representations of data, architecture, and interfaces form the foundation for component-level design. The processing narrative for each component is translated into a procedural design model using a set of structured programming constructs. Graphical, tabular, or text-based notation is used to represent the design
approach is to represent the procedural design using some intermediate (e.g., graphical, tabular, or text-based) representation that can be translated easily into source code