A brief summary of Design Models

This post is just a brief summary of design models, this is a huge topic, and will cover in future posts in parts.

Data Design Model: In order to implement the software we need to convert the analysis class models into the data structures and design classes and this is accomplished using data/class designs. For data design activity we need to have classes and relationships that are defined by CRC index cards and data content depicted by class attributes.

Architectural Design: It defines the relationship between the structural elements, the architectural styles and design patterns, and the constraints that affect the way in which architectural can be implemented.

Interface Design: It describes how the software elements communicate with each other, with other systems and with human users.

Component Level Design: Structural elements of the software architecture need to be converted into a procedural description of software components and this is accomplished through component level design.

These models collectively form the design model, which is represented diagrammatically as a pyramid structure with data design at the base and component level design at the pinnacle. Each level produces its own documentation, which collectively form the design specifications document, along with the guidelines for testing individual modules and the integration of the entire package.