Executive Summary
Software development disputes often arise because parties fail to define who owns the source code, object code, UI/UX, database, APIs, documentation, improvements and third-party components.
Payment for software development does not automatically resolve IP ownership unless the agreement expressly provides for assignment.
IP Ownership Structure
Developer Background IP
+
Client Inputs
+
Project Deliverables
+
Third-Party Components
↓
Contract Must Define Ownership Clearly
Case Law Integration
The distinction between copyright ownership and limited licence is supported by the reasoning in Engineering Analysis Centre of Excellence Pvt. Ltd. v. CIT, where the Supreme Court analysed the nature of software rights.
In IPRS v. Eastern Indian Motion Pictures Association, (1977) 2 SCC 820, the Supreme Court examined copyright ownership and assignment principles. The broader lesson is that copyright ownership must be determined by statute and contract; assumptions are unsafe.
Critical Clauses
- scope of work;
- milestones;
- acceptance criteria;
- payment schedule;
- IP assignment;
- source code delivery;
- open-source use;
- confidentiality;
- support;
- warranty;
- limitation of liability;
- termination.
Conclusion
A software development agreement should state whether IP transfers on signing, payment, delivery, acceptance or full settlement. Without clarity, both developer and client face avoidable disputes.