Definition

synchronize-and-stabilize (sync-and-stabilize)

Synchronize-and-stabilize (sometimes just called sync-and-stabilize) is a systems development life cycle model in which teams work in parallel on individual application modules, frequently synchronizing their code with that of other teams, and debugging (stabilizing) code regularly throughout the development process. The sync-and-stabilize model offers advantages over the older waterfall model, which is strictly sequential in nature. Because sync-and-stabilize development allows for changes at any point in the process, it can be flexible, and more easily able to respond to market requirement changes.

The sync-and-stabilize approach was created by David Yoffie of Harvard University and Michael Cusumano of MIT. Cusumano and Yoffie studied commonalities between processes Microsoft used in developing Internet Explorer and those Netscape Communications Corp. used in developing Netscape Communicator. The researchers found that, among other similarities, both companies compiled all the project code nightly. They both also brought together all the components and tried to stabilize code before it was released. Cusumano and Yoffie integrated the successful common strategies of the two projects into the sync-and-stabilize model.

At a recent XML Web Services One conference, Cusumano cited as-yet unpublished research findings indicating that a majority of development projects follow the sync-and-stabilize approach.

This was last updated in September 2005
Posted by: Margaret Rouse

Email Alerts

Register now to receive SearchSOA.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

More News and Tutorials

  • SOA, semantics and services combine in DoD intelligence sharing effort

    Using textual analytics and natural language processing, Modus Operandi developed a service that analyzes and parses unstructured data and pulls out events or information. Article includes tips on SOA and semantics, SOA and data models, and an SOA recipe for stone soup.Among highlights: Recognize that not everything can be or should be shared.

  • Q&A: Messaging middleware with Apache projects

    In this Q&A, Rob Davies discusses messaging middleware and the hurdles that many developers face as they first approach the subject. Davis is CTO of FuseSource and coauthor of the book "ActiveMQ in Action."

  • An SOA practices checklist for implementation roadmaps

    This article provides a master list of common practices, field proven by a number of SOA projects. Also supplied is a template that can be used as a checklist for developing SOA implementation roadmaps specific to an organization's transition project requirements.

Do you have something to add to this definition? Let us know.

Send your comments to techterms@whatis.com

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: