Your Subtitle text
Ownership of Source Code
Ownership of Source Code:

Ownership of Source Code is an ethical and legal issue...

When you hire a development team to develop software for you, who actually owns the programs and source code?  Your actual programs are owned by you, but what about the hundreds of code snippets and pieces that are compiled to produce your executables?

Entering into an agreement with a programming team, you need to be aware of this issue - or you may find yourself in a position at a later date where you cannot divest yourself of the team unless you negotiate for a princely price on purchasing the source code that makes up your system.

In this case, if you have no pre-set agreement, and code is only in the posession of your programming firm, your negotiating position is extremely weak.

What's your policy on source code backup and exit strategy with your programming team?
 
Source Code is the term for individual modules, class layers, images, and pieces of computer programming that are compiled together to make up your software system. 

Source code is made up of various types of pieces including a software language's runtime and utilities, custom code, third party contributions, and (watch out here:) "proprietary source and class layers" that your software company uses for it's various customers. 

Applause Software's policy is to deliver "all necessary source to recreate your exact software system" (very important language) unless some other legal document is in effect between us.

Applause cuts custom code for you and not only do you OWN your source, you also own "all components necessary to compile your current program": delivered to you by request.  This is our standard policy which is in effect unless otherwise stated.  This includes graphical images.
 
Notice:  This agreement is not in effect for the RoloFlex product offered commercially by Applause Software