Thijmen De Gooijer
Heiko Koziolek
ABSTRACT
Agreements for sharing of software between entities in a corporation have to be tailored to fit the situation. Such agreements are not legal documents and must address different issues than traditional software licenses. We found that these agreements should cover what is granted, payment, support, ownership and liability. In a case study we learned that an agreement should list its assumptions on the structure and processes of the software organization. The presented work enables others to create guidelines for software sharing agreements tailored to their organization and shares lessons about the differences between software product lines and corporate software sharing and reuse.
- V. D. Andrea and G. R. Gangadharan. Licensing Web Services : The Rising. In Telecommunications, 2006. AICT-ICIW ’06. International Conference on Internet and Web Applications and Services/Advanced, page 142, 2006. Google Scholar
Digital Library
- A. Chávez, C. Tornabene, and G. Wiederhold. Software Component Licensing: A Primer. IEEE Software, (October 1998):47–53, 1998. Google ScholarDigital Library
- H. Classen. Fundamentals of software licensing. Idea: The Journal of Law and Technology, 37(1), 1996.Google Scholar
- P. Clements and L. Northrop. Software Product Lines: Practices and Patterns. Addison Wesley, Boston, MA, USA, 2002.Google Scholar
- J. Espinosa, S. A. Slaughter, R. Kraut, and J. D. Herbsleb. Team Knowledge and Coordination in Geographically Distributed Software Development. Journal of Management Information Systems, 24(1):135–169, 2007. Google ScholarDigital Library
- D. Ferrante. Software Licensing Models: What’s Out There? IT Professional, 8(December):24–29, 2006. Google ScholarDigital Library
- G. R. Gangadharan and V. D. Andrea. Service Orientation : Licensing Perspectives. Journal of International Commercial Law and Technology, 4(1):1–11, 2009.Google Scholar
- R. Grinter. From local to global coordination: lessons from software reuse. In Proceedings of the 2001 International ACM SIGGROUP Conference on Supporting Group Work, pages 144–153, 2001. Google ScholarDigital Library
- M. Griss. Software reuse: From library to factory. IBM systems journal, pages 548–566, 1993. Google ScholarDigital Library
- H. Kaminski and M. Perry. The Pattern Language of Software Licensing. SSRN Electronic Journal, pages 1–41, 2005.Google ScholarCross Ref
- J. Lindman, M. Rossi, and A. Puustell. Matching Open Source Software Licenses with Corresponding Business Models. IEEE Software, 28(4):31–35, July 2011. Google ScholarDigital Library
- M. Morisio, M. Ezran, and C. Tully. Success and Failure Factors in Software Reuse. IEEE Transactions on Software Engineering, 28(4):340–357, 2002. Google ScholarDigital Library
- L. M. Northrop, P. Clements, et. al. SEI Framework for Software Product Line Practice http://www.sei.cmu.edu/productlines/frame report/, visited 8 January 2013.Google Scholar
- K. Pohl, G. Böckle, and F. van der Linden. Software Product Line Engineering. Foundations, Principles and Techniques. Springer, Berlin / Heidelberg, 2005. Google ScholarDigital Library
Index Terms
- Agreements for software reuse in corporations
Recommendations
Software reuse
Software reuse is the process of creating software systems from existing software rather than building software systems from scratch. This simple yet powerful vision was introduced in 1968. Software reuse has, however, failed to become a standard ...
Software reuse: survey and research directions
Special section: Managing virtual workplaces and teleworking with information technologySoftware reuse is the use of software resources from all stages of the software development process in new applications. Given the high cost and difficulty of developing high-quality software, the idea of capitalizing on previous software investments is ...
Forty years of software reuse
Forty years of software reuseThis paper is an overview of software reuse, its origins, research areas and main historical contributions. Reuse as the process of using existing software artefacts and knowledge has more than 40-year long history, and is ...
Comments