short notes is a journal on software, systems, engineering practices among other things.
Copyright © 2002-2006 short notes. All rights reserved.    contact address: email to the editor   ISSN 1543-6489

short notes
 
Monday, 5. August 2002

Everything's explained in SOP


In many organizations, the design process still follows a classical "military" model. A small number of "officers" do the "noble" task of analysis and design, plan the overall work load, and assign implementations and test tasks to the "simple soldiers." This way of working has several drawbacks.
...
But today, even the military no longer works like this, at least in the British SAS or American SEALS and probably other elite military forces as well. ... Most interesting to us is the account of the mission design. After being given a broad view on the mission objective [...] all eight members of the SAS patrol meet to cooperatively design the details of their mission (what, when, where, how, and with which tools). They do not start from scratch but instead identify the problems to be solved and their contexts, and then borrow and customize solutions from the Standard Operational Procedures (SOP) handbook: for example, get to this point behind enemy lines with enough food and ammunition for the mission and without anybody else being aware or have a cover story ready in case of a capture). The very same eight men then "implement" their design, being fully aware of all the implications. The bottom line of this approach is that these special forces consistently rate from five to ten times better than classical ones--and military efficiency measures, albeit somehow macabre, do exist.

[The benifits of this approach are:]

... The most striking point is the team's reliance on patterns of organization and behavior for the big picture and on SOP for the implementation details. These patterns are used as small building blocks that everyone knows and understands: The design activity can proceed at a quite high level, in terms of patterns instead of implementation details. ...

Another interesting point is that, because those who design the mission are also the ones who implement it, they tend to come up with implementable designs and realistic schedules. ...

Finally, because all of the implementers are responsible for the design, a strong team spirit is created to make the implementation possible. ...

From "Design Patterns and Contracts" by Jezequel, Train, Mingins (ISBN 0201309599)


 

 
Published since 2002-04-23
Updated: 2010-10-16
status
Youre not logged in ... Login
menu
November 2024
SunMonTueWedThuFriSat
12
3456789
10111213141516
17181920212223
24252627282930
October
recent
recent

RSS Feed

RSS integration

Made with Antville
powered by
Helma Object Publisher