SCM Design Patterns: Paper Forms

Part 1

spent. Another output of this Design Pattern is to get all the stakeholders to agree on how you are going to run your SCM system in support of your development processes.

This Design Pattern is simple in comparison to today’s SCM systems/tools, but it has the foundational elements of what any good SCM system/tool must accomplish. However the lack of automation makes this Design Pattern rather cumbersome to use in a production environment. With the computer resources we have today we can improve on this Design Pattern substantially by automating its functions.

Read Part 2 at  SCM Design Patterns: Version Control & Multiple States

Read Part 3 at  SCM Design Patterns: Build and Deployment

Read Part 4 at  SCM Design Patterns: Parallel Development and Content Management

About the Author

Jim Johnston has worked in the IT industry for over 20 years. He has held multiple positions including CAD/CAM programming, applications integration coordinator, manager of a application launch center for testing and integration verification of PC applications, and testing architect for major web systems. Jim has been involved with SCM for over 6 years primarily in the areas of enterprise web applications, retail web sites, SCM process development and J2EE build and deployment methodologies.   

About the author

TechWell Contributor's picture TechWell Contributor

The opinions and positions expressed within these guest posts are those of the author alone and do not represent those of the TechWell Community Sites. Guest authors represent that they have the right to distribute this content and that such content is not violating the legal rights of others. If you would like to contribute content to a TechWell Community Site, email

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, is the place to go for what is happening in software development and delivery.  Join the conversation now!