The D-matrix notation can be used to describe the development of a program (since this is detailed design). Here we might consider decisions about the tasks performed by subprograms (procedures,...

The D-matrix notation can be used to describe the development of a program (since this is detailed design). Here we might consider decisions about the tasks performed by subprograms (procedures, methods) as functional design decisions; the choice of the subprograms and any larger packaging units (such as classes) as constructional design decisions; and the choice of data structures as data-modelling design decisions. (Behaviour doesn’t fit quite so well.) When you next write a program, keep a note of the development process and then try to describe this using the D-matrix form. (You may need to group related actions to make this manageable.)