>>92 >>93
As I stated at the fore; this is just for the piece of paper.
The bits I dislike are use case diagrams and component diagrams. At the level I've been taught, the systems I've designed and built can justify the inclusion of design, but not drawing a stickman for every input and expected output.
Component diagrams can be worked together by using the class diagram tables, adding some flow chart style links and choosing a method of identifying child parent relationships and interaction.
Using clean room development style on your pseudo code and actual code after these designs have been done is all I feel you require.