2009 17th IEEE International Requirements Engineering Conference 2009
DOI: 10.1109/re.2009.22
|View full text |Cite
|
Sign up to set email alerts
|

Intellectual Property Rights Requirements for Heterogeneously-Licensed Systems

Abstract: Heterogeneously-licensed systems pose new challenges to analysts and system architects. Appropriate intellectual property rights must be available for the installed system, but without unnecessarily restricting other requirements, the system architecture, and the choice of components both initially and as it evolves. Such systems are increasingly common and important in e-business, game development, and other domains. Our semantic parameterization analysis of open-source licenses confirms that while most licen… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
35
0

Year Published

2011
2011
2017
2017

Publication Types

Select...
5
2

Relationship

5
2

Authors

Journals

citations
Cited by 38 publications
(35 citation statements)
references
References 9 publications
0
35
0
Order By: Relevance
“…Similarly, it suggests the possibility of developing computational tools or interactive architecture development environments that can be used to specify, model, and analyze a software system's security architecture at different times in its developmentdesign-time, build-time, and run-time. The approach we have been developing for the past few years for modeling and analyzing software system IP license architectures for OA systems (Alspaugh, Asuncion, & Scacchi, 2009bScacchi & Alspaugh, 2008) may therefore be extendable to also being able to address OA systems with heterogeneous "software security license" rights and obligations. Furthermore, the idea of common or reusable software security licenses may be analogous to the reusable security requirements templates proposed by Firesmith (2004) at the Software Engineering Institute.…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…Similarly, it suggests the possibility of developing computational tools or interactive architecture development environments that can be used to specify, model, and analyze a software system's security architecture at different times in its developmentdesign-time, build-time, and run-time. The approach we have been developing for the past few years for modeling and analyzing software system IP license architectures for OA systems (Alspaugh, Asuncion, & Scacchi, 2009bScacchi & Alspaugh, 2008) may therefore be extendable to also being able to address OA systems with heterogeneous "software security license" rights and obligations. Furthermore, the idea of common or reusable software security licenses may be analogous to the reusable security requirements templates proposed by Firesmith (2004) at the Software Engineering Institute.…”
Section: Related Workmentioning
confidence: 99%
“…With this information and definitions of the licenses involved, we believe it is possible to automatically calculate rights and obligations for individual components or for the entire system, as well as guide/assess system design and evolution, using an automated environment of the kind that we have previously demonstrated (Alspaugh, 2009a(Alspaugh, , 2009b.…”
Section: Security License Architecturesmentioning
confidence: 99%
See 1 more Smart Citation
“…Mods tend to be licensed using OSS or freeware licenses that allow for access, study, modification, and redistribution, rather than using free software licenses (e.g., GPLv2 or GPLv3). Software extensions that might be subject to a reciprocal GPL style license require that the base/original software system incorporate an explicit software architectural design that requires the propagation of reciprocal rights across an open interface, except through an LGPL software shim [1]. Otherwise, the scope of effectiveness and copyright protections of either free or nonfree software (or related media assets) cannot be readily determined, and thus may be subject to copyright infringement or licenses non-compliance allegations.…”
Section: Opportunities and Constraints For Moddingmentioning
confidence: 99%
“…The approach we have been developing for the past few years for modeling and analyzing software system license architectures for OA systems (Alspaugh et al, 2009, August/September;Alspaugh et al, 2009b, May;Scacchi & Alspaugh, 2008), may therefore be extendable to also being able to address OA systems with heterogeneous "software security license" rights and obligations. Furthermore, the idea of common or reusable software security licenses may be analogous to the reusable security requirements templates proposed by Firesmith (2004) at the Software Engineering Institute.…”
Section: Discussionmentioning
confidence: 99%