Form over Substance

Beware of the colleague or supplier who spends large amounts of time in meetings discussing the format, sequence, and wording of documents they will deliver and very little time on the actual content. Strategically, substance is what counts. In this issue of Strategic Software Engineering I will point to some common problems when form becomes a higher priority than substance and what value is added when these problems are addressed.

[1]  Julie Johnson.  What is the Rational Unified Process ? , 1999 .

[2]  G. I. Kustova,et al.  From the author , 2019, Automatic Documentation and Mathematical Linguistics.

[3]  John D. McGregor,et al.  The Year 2000 Crisis and the Search for Absolute Truth. , 1998 .

[4]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[5]  Mary Shaw,et al.  Software architecture: the next step for object technology (panel) , 1993, OOPSLA '93.

[6]  John D. McGregor,et al.  A Software Development Process for Small Projects , 2000, IEEE Software.

[7]  John D. McGregor,et al.  The Fifty-Foot Look at Analysis and Design Models , 1998, J. Object Oriented Program..

[8]  Flavio Oquendo,et al.  Software Architecture , 2004, Lecture Notes in Computer Science.