Invitation for a new OSS-USE R&D project OSS-USE: INDUSTRIAL SOFTWARE INNOVATION BY OSS 2 June 2009, Reidar Conradi et al., IDI, NTNU Software Technology Context: 1970: Systematic software reuse – less time & effort, better quality, ”best practises”, modern architectures – but non-technical obstacles like trust, ownership, ROI, updating, culture, policies … : Free Software and Open Software Software (OSS). Since 2005: software technology maturing through OSS: –Massive, global software reuse, i.e. standardization. –Cooperative and distributed work processes. –Ex. Roles: main developer (having ”gone open”), major co-developers, occational contributors, passive developers, and end-users. –Ex. Business models: double licensing, or shared OSS code run by foundations owned by IBM, Sun etc. and which may offer paid services.

Invitation for a new OSS-USE R&D project The OSS ”tsunami” and your company Ongoing software revolution: –One million software components in Linux, OpenOffice, general or specific programming libraries like Hibernate, Spring etc. –Norwegian OFU contractors must now make delivered software ”open”. –Half of 5000 Norwegian software companies use OSS in new code; that have gone open – like Ez Systems w/ 2 mill. downloads. What’s in it for an ICT-intensive company like yours? –All software-intensive companies need to efficiently acquire, use and maintain tailored software systems - costing your company 5%? of revenues per year. –Systematic reuse and OSS: vital to improve such software processes, perhaps in non-competitive communities with related companies (figure p. 4). Try base such efforts on previous R&D projects, like: –SEVO project (SW evolution of component-based systems, NFR, ): 4-year study of defect & change rates being much lower in reused code; recommendations for changed reuse policies and processes. –Also previous REBOOT, INCO, COSI and EVISOFT projects.

Invitation for a new OSS-USE R&D project Project USE-OSS: Innovation by reusing OSS? For your company (CX), consider an internal OSS initiative: –Make a survey of the insight in and attitudes to OSS in CX (human roadmap). –Find out how much and what kind of OSS is now in use in CX (software roadmap). –Coordination: reuse of shared parts between outsourced software (internal reuse). –Import-v1: make new software by reusing existing OSS components (classic reuse). –Import-v2: find ”code” that may be replaced by existing OSS components (post-reuse). –Export: find ”code” that may be upgraded to new, own OSS components (go open). –Establish non-competitive communities with similar companies regarding domain-specific libraries (partner seek), cf. similar alliances in telecom between Nokia, Philips et al. –Adopt an incremental approach for all this. Identify risks and success factors. For NTNU, establish R&D project to piggy-back on such initiative(s): –Study related products and processes. Make research design w/ research goals. –Propose and validate revisions to the actual processes. Advancing state-of-the-art. –Similar for ”open” business models to express CX’s OSS policies and experience.. So, new project with NTNU, CX and similar companies, Friprog?,... : –NTNU: two PhD students: 5 MNOK over 3 years, some master students. prof. Reidar Conradi, postdoc Daniela Cruzes, both IDI; f.aman. Alf Steinar Sætre, IØT; –Full-time industrial coordinator and an action team of 2-3 persons from each company. –As a VERDIKT or UserDriven project at NFR, or an industry-sponsored project?

Invitation for a new OSS-USE R&D project Ex. OSS Business Models - COSI ITEA2 project: New technology in upper-right corner (red), being eroded from lower-left (yellow). Maturing technology, from proprietary to open, towards lower-right corner (arrow on green diagonal).