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
Monday 2002-08-05 Policy, Process, MechanismEverything'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. [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 Youre not logged in ... Login
about short notes home topics: Development Policy, Process, Mechanism Software Web of Services World
|