The format
that I suggest is IEEE 1016. This could supplemented by software reviews
1028. Both these could be made of. The techniques that are often used are
scenario building, design walkthrough, design reviews, inspection, correlation
with requirements. When we talk about it, the design has to be correlated
to the requirement that we have identified earlier. Some of the interesting
techniques are prototyping and simulation. The prototyping is very important.
The simulation is also an important one. However it is expensive, it is
useful in some cases. The team is basically the test team and system designers. And finally we have the formal descriptions. For instance flow diagrams, or data diagrams, these are all the formal descriptions that we have been using all this time. | ![]() |