1. NTNU activities in Open Source Software (OSS): ideas for cooperation?
Reidar Conradi, Daniela S. Cruzes et al.
Institutt for datateknikk og informasjonsvitenskap (IDI) / Department of Computer and Information Science, NTNU, NO-7491 Trondheim
Simula-NTNU Contact Meeting, 7 Dec 2009 (w/ rev. slides)
Simula Research Labs, Fornebu near Oslo
Attn/ Leon Moonen, Aiko Fallas Yamashita et al.,
Telenor-NTNU OSS contact meeting, 18 Dec 2008

2. Table of contents IDI and NTNU: who, what, … Software reuse and CBSE
The Open Source Software (OSS) phenomenon
OSS activites at NTNU
Ideas for activities in company YYY on OSS
YYY + NTNU = true?
Telenor-NTNU OSS contact meeting, 18 Dec 2008

3. 1. IDI Department at NTNU
IDI (2009): 140 employees, NTNU’s largest – 31 nationalities!
45+ teachers (faculty w/ six women), 22 tech./adm., 52 PhD fellows, 20 temporary researchers/postdocs/teachers incl. 8 adjunct teachers (II”ere).
6000 individual exams per year, 800 full-time students, participating in 7 study programs.
150 master candidates and 10 PhD candidates per year.
Important value chain: teachers – postdocs – PhD students – master students – bachelor students – IT industry.
11 research groups, incl. SE group below.
Counting ”Frida” publications: 196 in 2007, 184 in 2008, 223 in 2009
Budgets 2008: 74.8 MNOK from NTNU MNOK in external projects.
Budgets 2009: 80.1 MNOK from NTNU MNOK in external projects.
Software engineering (SE) group in 2009:
5,2 teachers, 2 researchers, 17 PhD fellows – 13 nationalities!!
Papers: 44/61 of 196/274 (2007), 40/47 of 184/255 (2008), 45/56 of 223/241 (2009);
i.e. 25 % of IDI total, ca. 20 each year w/ foreign colleagues; 500 papers in last 10 years.
Ca. 25 master candidates/year; 3 PhDs in 2009, 4? In 2010.
7 MNOK in external projects (40% of IDI total.)
Telenor-NTNU OSS contact meeting, 18 Dec 2008

4. Research fields of the SU group (1)
Distributed
Software Engin.
Software
and Art; Computer games
CBSE: COTS/OSS,
Evolution, SCM
Reliability,
safety, maintainability
Co-operative
work
SPI, learning organisations, SE education
quality
Mobile
Tech. for Learning
Software reuse and
architecture
Telenor-NTNU OSS contact meeting, 18 Dec 2008

5. Research profile of SE group (2)
Empirical research methods (all members)
Quality, QA, SPI, knowledge management (Conradi, Stålhane)
Reliability and safety, testing (Stålhane)
Software reuse, component-based development, open source / digital content (Conradi, Jaccheri)
Cooperation technologies, learning. awareness, virtual 3D (Divitini, Prasolova-Førland)
Mobile and ambient technology (Divitini, Wang)
Computer games for higher learning (Wang)
Software and art (Jaccheri)
Telenor-NTNU OSS contact meeting, 18 Dec 2008

6. Research profile of SE group (3)
Reidar Conradi (NTH, IDB since 1975): Empirical research, CBSE, OSS, SPI/KM – COSI, EVISOFT.
Tor Stålhane (NTH-statistics/SINTEF, 2000): QA/SPI, safety, reliability, testing – EU:CAESAR, EVISOFT.
Letizia Jaccheri (Pisa/Torino,1997): OSS, sw and art, EU:ArTe.
Monica Divitini (Milano, 1999): CSCW, ambience, awareness – EU:ASTRA, FABULA, NTNU:-LIKT:MOTUS.
Alf Inge Wang (NTNU, 2003): mobility, computer games – GameNet,Telenor:MOSS.
Ekaterina Prasolova-Førland (NTNU, 2003, 20%): mobile 3D-enabled learning – EU:TARGET, NTNU-LIKT
Telenor-NTNU OSS contact meeting, 18 Dec 2008

7. Research projects in SE group (4)
25++ NFR and EU projects in last 20 years, most with industry:
INCO, MOWAHS, BUCS, SEVO, WebSys: basic SE (NFR IKT2010)
NorskCOSI: inner and open source (ITEA2)
SPIQ, SPIKE, PROFIT, INTER-PROFIT, EVISOFT: empirical SPI in Norwegian software-intensive industry (NFR BiA)
MOSS: Computer games (Telenor, NTNU)
MOTUS-1, MOTUS-2: ICT & learning (NTNU, Telenor)
FABULA: mobile technology and learning (NFR VERDIKT)
ArTe: Computer art: dissemination to youth (NFR regional, 2009)
ASTRA: awareness (EU FET)
TARGET: virtual 3D in learning (EU IP)
Travel in Europe (EU, subcontractor)
CESAR: safety in transport sector (EU IP, ”Airbus” w/ 53 partners)
under evaluation by NFR and EU
Telenor-NTNU OSS contact meeting, 18 Dec 2008

8. 2. Software reuse and CBSE (1)
Systematic software reuse (from 1970): making shared code for internal (re)use across projects and departments in an organization.
CBSE – Component Based Software Engineering, like hw plugins?
Independent of programming language and OO paradigm.
Cost of reuse: % to generalize, break-even after 1-2 reuses.
Assumes stable domain and architectural knowledge – reusable software is ”discovered”, not ”pre-designed”!
Huge potential benefits: cost, time, quality, predictability, standardization of architecture and processes/tools (XML, UML, Java, Eclipse) – a gradual modernization of products with ”best practise” processes.
But not widely adopted: assumes adjusted company processes and culture; new roles/responsibilities, need cost/benefit analyses with uniform investment rate, ROI? with upfront investments and unclear later advantages, too small internal component market, implies new dependencies, must handle risks with ad-hoc tradeoffs, Need incremental approach – c.f. OSS later!!
Telenor-NTNU OSS contact meeting, 18 Dec 2008

9. 2. Software reuse of components, OTS = Off-The-Shelf (COTS or OSS) (2)
Software reuse: assets often as class libraries in repositories (as Hibernate)
Develop “for” reuse: make generalized assets / components
Develop “with” reuse: CBSE, using these assets
Advantages of CBSE, either with internal or external OTS components:
Cheaper, earlier, better, … software
Spread novel work practices & software architectures, leading to standardization
Re-user communities for experience mgmt/support
I.e. software development gets ”modernized”
Mainly non-technical obstacles: price/licensing, ROI, (re)negotiate requirements, less “control”, too “radical”
Reidar
Telenor-NTNU OSS contact meeting, 18 Dec 2008

10. 2. Industrial examples of internal software reuse (3)
IBM Federal Systems: empty, low quality garbage, too general.
HP: two systems, 1.5 times later reuse (2nd to 3rd system) to break even (see Wayne Lim 1994)
Ericsson in Grimstad: 60% reuse between GPRS and UMTS
Statoil IT: JEF framework
Need … …
Reidar
Telenor-NTNU OSS contact meeting, 18 Dec 2008

11. 3. The OSS phenomenon (1)
Since 1995: OSS as a benign tsunami; enabled by Internet and web. Part of “social computing”, cf. Facebook.
Generalized into Creative Commons for global development and sharing of “free” digital artefacts in any domain.
Over OSS components, as in
Infrastructure (ex. Linux, Apache, MySQL, PhP – the LAMP platform)
libraries (Hibernate)
shelfware (Acrobat, OpenOffice, SVN versioning tool)
Based on launched (“gone open”) OSS projects, each with a community of developers, co-developers and integrators/users.
Many licensing models:
GPL: “contagious” openness by using OSS – so-called “copyleft”.
BSD: any use is OK, as long as name of originator follows the OSS copy.
eCos v1.1: all local changes to a down-loaded OSS must be reported back to originator, but impractical even via SVN.
Telenor-NTNU OSS contact meeting, 18 Dec 2008 11

12. 3. The OSS phenomenon (2)
OSS: attracted much attention from industrial and public policy makers: e.g., IBM and Sun Microsystems; Skattedirektoratet, Kommunenes Sentralforbund, Bærum kommune.
St.meld. 17 (2006/2007) by Norwegian Government recommends promoting OSS and open standards, new competence center. Also (NFR).
OSS phenomena is changing the whole paradigm of software development and associated economic patterns and interactions – by cooperative, distributed innovation.
To stay competitive and innovative, Norwegian software-intensive companies and public institutions must undergo this economic and cultural revolution:
novel Business Models
novel Innovation Models
Ex. Often shared/free code w/ surrounding paid service providers – as for Apache, but who is “responsible owner” setting the course and revising requirements?
Solution by a social innovation: professional partnership communities to establish and evolve their needed software, itself being OSS. I.e. move away from “unpredictable” volonteers working for free.
Telenor-NTNU OSS contact meeting, 18 Dec 2008 12

13. Open Source Software: origin and now (3)
1650?: free flow of ideas begins in emerging scientific community.
: DoD/DARPA’s development of Arpanet / Internet TCP/IP protocols -- open and distributed development, anti-authoritarian “counter culture”.
: Openness spreads via Univ.Berkeley’s adaptation of Unix, with built-in Internet protocols and generous BSD licenses with all source provided.
1985: Free Software Foundation: by Richard Stallman from MIT AI Lab; ideological ”CopyLeft”-inspired licenses.
1998: Open Software Initiative: by Eric Raymond from IT industry in US, pragmatic BSD-inspired licenses. ”The Cathedral and the Bazaar”:
2000: FLOSS = FSF +OSI; IFIP WG2.13 uses OSS as common denominator.
2005: Social computing and creative commons for knowledge work – standardized formats for “zero-cost” digital information, the world is ”flat”.
2008: 1,5 billion Internet users, 3 billion w/ mobile phones.
2009: Ex. Wikipedia: 55 mill. “gratis” personhours.
Reidar
Telenor-NTNU OSS contact meeting, 18 Dec 2008

14. OSS issues (4)
OSS “projects”, each w/ net community lead by original provider, co-developers, code integrators, users, ...
Ex. eZ has had 2.3 mill. downloads, over 100 plugins made by community.
Ex. Adobe Acrobat similarly over 500 mill. downloads.
COTS and OSS: many similarities, mostly used as black box.
Over 30 portals with domain-specific COTS/OSS software.
New way of making open ICT standards: rough consensus and (two implementations of) running code.
Over 50 licensing schemes.
Ex. Business models:
Apache: open and shared source supported by a cooperative foundation (“IBM”); separate payable services.
eZ: dual model with free previous version, payable current version plus services and support.
Success criteria??: for provider in “going open”, for future co-developers, for code integrators, …
Reidar
Telenor-NTNU OSS contact meeting, 18 Dec 2008

15. OSS roles (5)
OSS (component) provider: Leads a “gone-open” software project, ex. Linus Thorvald w/ Linux
OSS co-developer or participant: assists the provider in more technical work – the OSS “idea” of joint, altruistic work
OSS integrator: makes new software system by re-using OSS software/components
OSS pre-co-developer: reports bugs and wishes for new features, sometimes changing the code.
OSS user: may download “free” (not open) binary software on a private computer, e.g. Acrobat
OSS customer: specifies and finances new software, later published as OSS?
OSS skills: technical, commercial, organizational, creative, …
Reidar
Telenor-NTNU OSS contact meeting, 18 Dec 2008

16. OSS Business Models (6)
In general, to enter in the OSS field, companies have to manage Intellectual Property (IP) differently and to innovate more:
Sale/
divestiture
Revenues
New revenues
Spin-off
License
Own market
revenue
Own market
revenue
Internal and
external
development
costs
Internal
development
costs
Cost and time savings
from leveraging
external development
Costs
[Chesbrough2006]
Telenor-NTNU OSS contact meeting, 18 Dec 2008 16

17. OSS Business Models (7) From COSI ITEA2-project: 12.11.2018
Telenor-NTNU OSS contact meeting, 18 Dec 2008 17

18. Novel Innovation Models (8)
Traditional innovation models are based on the “egoistic” protection of Intellectual Property, i.e. cannot capture value from OSS for companies. So your cards lie with “face down” and contents hidden, as a private and short-term sub-optimalization.
Novel innovation models leave your cards “face open” and contents acessible for everyone. This paradoxical altruism promotes maximum combinatorics and future innovation, by a public and long-term exchange for societies and companies to reap the full benefits of OSS:
The guidelines for revised development processes from “private investment” to “collectively action” hardly exist.
Telenor-NTNU OSS contact meeting, 18 Dec 2008 18

19. Novel Innovation Models (9)
Several issues need to be addressed:
How to succeed in attracting co-developers when “going open”?
How can traditional (i.e. paid software development by software companies), coexist and even amplify the benefits for both the “old” and “new” work mode?
So rely less on classic OSS idealism, rather refine and commercialize more cooperative work modes.
Friprog’s learning ecosystem to systematize the (meta-) services that might be needed (next slide):
How to establish such an ecosystem? Roles?
How to build competence?
How to offer legal or economic advise?
How to make decisions about changes in old vs. new systems?
How to build and maintain expert communities?
How to manage experience bases (avoid the “white elephants”)?
Practically: if (most of) the code is shared and “free”, where is the profit coming from?
[Chesbrough2006] Henry Chesbrough: “OPEN Business Models”, Harvard Business School Press, 2006.
[Browning2008] L. D. Browning, A. S. Sætre, K. Stephens and J.-O. Sørnes: ”Information and Communication Technologies in Action: Linking Theory and Narratives of Practice”. New York: Routledge.
Telenor-NTNU OSS contact meeting, 18 Dec 2008 19

20. Telenor-NTNU OSS contact meeting, 18 Dec 2008
Telenor-NTNU OSS contact meeting, 18 Dec 2008 20

21. 4. OSS research at NTNU (1) Why is this interesting for you?
Experience from industry-related research
What should we focus on in future research?
Experience from theory-driven research
How to validate in practise?
Experience from education
What should students know about OSS?
Letizia 21
Telenor-NTNU OSS contact meeting, 18 Dec 2008

22. 4. Multi-faceted OSS research (2)…
political
social
sciences
software
engineering
learning
psychology
juridical &
economical (not yet)
Letizia
focus on company based software engineering, reuse, and COTS (Reidar will present in an historical perspective he will mention Thomas’s work on gentoo )
ITEA COSI project (Øyvind will present)
Companies
processes
Open source survey
intersects both with 1) and 2)
Open standards (case at ARM, Eskil will present)
Education (Letizia will present)
Open source and Art (Letizia will present) 22
Telenor-NTNU OSS contact meeting, 18 Dec 2008 22

23. 4. research activities (3)
OTS surveys
Focus on company based software engineering, reuse, and OTS
ITEA COSI project
Open source survey
Open source and Art
Case Open standards (ARM)
Letizia
Education
Case
Gentoo 23
Telenor-NTNU OSS contact meeting, 18 Dec 2008

24. 4. NTNU: CBSE and OTS studies (4)
: EU projects (e.g. REBOOT) on internal software reuse; hard!
1995-: New global “bazaar” of COTS/OSS, through web
: Industrial surveys on OTS reuse Norway, Germany, Italia, China Developer panels and follow-up interviews with qualitative data to give insight
Research instruments and raw data: “gone open” – please repeat our studies!!
Reidar
Telenor-NTNU OSS contact meeting, 18 Dec 2008

25. NTNU: Roles in OTS-based reuse
From forthcoming paper by Jingyue Li et al., IEEE Software 2008
Reidar
Telenor-NTNU OSS contact meeting, 18 Dec 2008

26. NTNU: gained insights on OTS reuse
1a. Ask colleagues to find “right” component, e.g. Hibernate, Spring, … (there are very common ones).
1b. Otherwise search the net, download 3-6 candidates for further evaluation and possible selection, record the outcome for later use.
1c: If no close match is found, either:
– 1c.1 Issue a “bookmark” for the future in an OSS portal.
– 1c.2 Consider renegotiate requirements: iterate 1b-1c.2.
– 1c.3: Develop new, own software (with OSS parts),
post it as OSS and try create project/community.
Summary: no formal selection method, selection can be hosted by most lifecycle processes, need component “uncle” for maintenance, “quality“ not a problem
Problems: effort estimation, integration, debugging, customer non-participation, licensing, company policies, what classification framework (ontologies) for what properties and how to reliably classify components?
Reidar
Telenor-NTNU OSS contact meeting, 18 Dec 2008

27. Industrial examples of OSS reuse:
Bouvet: measure power consumption in trains (GoOpen’08).
Norwegian Air: travel booking system summer 2002 (GoOpen’08),
Acando: reimbursements for travel for medical treatment (GoOpen’09)
Telenor IS: mapping attitudes to OSS in coop. with NTNU (GoOpen’09).
YYY
Reidar
Telenor-NTNU OSS contact meeting, 18 Dec 2008

28. Action Research on Gentoo OSS
PhD by Thomas Østerlie
Gentoo: OSS release management tool, scripts, 300 co-developers in 40 countries
Worked as co-developer for two years; distributed, participative, “in-process” field study
Remote debugging: mutual guesswork, as “sense-making”, informal processes
Data: diaries, s, IRC/version logs
Reidar
Telenor-NTNU OSS contact meeting, 18 Dec 2008

29. research activities OTS surveys Open source survey ITEA COSI project
Focus on company based software engineering, reuse, and OTS
ITEA COSI project
Open source survey
Open source and Art
Case Open standards (ARM)
Letizia
Education
Case
Gentoo 29
Telenor-NTNU OSS contact meeting, 18 Dec 2008

30. ITEA COSI project (2006-2008) Industry and academia
Finland, Netherlands (coord.), Norway, Spain, Sweden
Understand and benefit from Open source software and development practices
Shared internal development
Norwegian COSI
IKT Norway
eZ Systems, Keymind, Linpro, e??farm, Oslo Børs, Friprog, NTNU
Budget about 18 MNOK
Sponsored by NFR: 8.5 MNOK totally
Øyvind
Effective and efficient heterogeneous distributed concurrent development addressing business & process improvement with open and inner source.
Agile developments in distributed settings using open and inner source.
Trust and understanding of open collaborations involving open source community and software intensive system producers.
Understanding & strategic use of the software shift moving from differentiating to commodity software.
Telenor-NTNU OSS contact meeting, 18 Dec 2008

31. Adoption of OSS in the Software Industry
About 70% (50%) are reusing and integrating OTS (OSS) components
Into all kinds of products
To all kinds of customers
Large companies more often than small
Consultancy companies more often than software houses
15-20% participate in OSS co-development
Means huge, global and dedicated cooperation communities
About 5% provide their own OSS products (”going open”)
Of these ?? % are attracting other co-developers
Øyvind
Telenor-NTNU OSS contact meeting, 18 Dec 2008

32. Motivations for adoption of OSS
Simplify developer’s job
High availability of information, components and their source code
Simple procurement
Membership of community for support and future influence
Reusable software assets
Increase productivity
Increase quality (reliability, ..)
Increased focus on architecture and even product line
Increase compliance with standards
Reduced costs
Reduced development effort
No license fees
Øyvind
Telenor-NTNU OSS contact meeting, 18 Dec 2008

33. Selection: Identification, Evaluation and choosing of wanted OSS-component(s)
Evaluation until something ”good enough” is found
Tested further through test integration and prototyping
Informal knowledge driven process based on:
Previous experience
Recommendations
Informal searches
“Surveillance” of the OSS community
Øyvind
Previous experience
Recommendations
Colleagues, friends, customers, competitors
Successful implementations
Informal searches
The Internet, OSS portals, Internal knowledge bases
“Surveillance” of the OSS community
News letters, Portals, Forums, Mailing lists, Magazines
Telenor-NTNU OSS contact meeting, 18 Dec 2008

34. research activities OTS surveys Open source survey ITEA COSI project
Focus on company based software engineering, reuse, and OTS
ITEA COSI project
Open source survey
Open source and Art
Case Open standards (ARM)
Letizia
Education
Case
Gentoo 34
Telenor-NTNU OSS contact meeting, 18 Dec 2008

35. Open standards and
Cooperation between ARM Norway (ex-Falanx with Reodor Felgen innovation award in 2006) and NTNU (with half a dozen master’s theses since 2002)
Describing a master’s project (single person one year):
development of a multi-platform graphics application.
Used ARM’s platform for embedded graphics.
Telenor-NTNU OSS contact meeting, 18 Dec 2008

36. Open standards and ARM Open Vector Graphics (OpenVG)
OpenVG is a standard for embedded systems
Targets: Map applications, scalable user interfaces, e-book readers, games and SVG viewers
Scalable Vector Graphics (SVG)
Open format for describing vector graphics in XML which provides uniform representation of 2D graphics.
SVG Tiny – A mobile profile targeting light weight mobile devices
Telenor-NTNU OSS contact meeting, 18 Dec 2008

37. Open standards and the application
PC platform
SVG Tiny application Application size ~ LOC
Open Standards
SMIL
XML11
DOM3
XLINK
Other W3C standards...
PNG
JPEG
ARM platform
Telenor-NTNU OSS contact meeting, 18 Dec 2008

38. Results from application development and porting
Ease of adoption
OpenVG is an open standard, thus royalty-free.
Specification and reference implementation publicly available. No project expenses.
Performance
OpenVG allows for efficient and creative implementations.
Efficient SVG Tiny viewer achievable on a regular PC and ARM platform.
Conformance
OpenVG conformance tests assure correct implementations.
Consistent and correct behaviour of application on PC and ARM platform.
Portability
OpenVG API abstracts and de-couples application from hardware .
High degree of application portability. Less effort
Telenor-NTNU OSS contact meeting, 18 Dec 2008

39. Research activities OTS surveys Open source survey ITEA COSI project
Focus on company based software engineering, reuse, and OTS
ITEA COSI project
Open source survey
Open source and Art
Case Open standards (ARM)
Letizia
Education
Case
Gentoo 39
Telenor-NTNU OSS contact meeting, 18 Dec 2008

40. Cases: Art and open source software = SArt
Main objective of SArt
to propose, and assess, and improve methods, models, and tools for software development in art context
Cases (in sourceforge portal)
The Open Digital Canvas Project
Sonic Onyx Project (mobile phones)
The Flyndre Project
Letizia 40
Telenor-NTNU OSS contact meeting, 18 Dec 2008

41. SArt: art and open source software
Letizia 41
Telenor-NTNU OSS contact meeting, 18 Dec 2008

42. Premiered art competition The Open Wall Open Contest
Deadline 15th September 2009
The prize award will take place at this year’s festival for art and technology in Trondheim, Trondheim Matchmaking, the 16th – 18th of October.
1st prize 2000 €, 2nd prize 1500 €, 3rd prize 1000 €
Letizia
Telenor-NTNU OSS contact meeting, 18 Dec 2008

43. 5. OSS ideas for Telenor etc. (1)
Map existing use of and interest in OSS? – done spring 2009 by two master students.0
Establish teams/fora/communities for OSS at Telenor?
Success criteria and ROI models for GoOpen?
Alliances with other business units/companies?
How to control or influence (OSS) software, that we have come to depend on – like for most purchased products?
New business/innovation models?
Cooperate with FriProg and NTNU on OSS ecosystem?
Letizia
Telenor-NTNU OSS contact meeting, 18 Dec 2008

44. 5. OSS ideas for software development at Telenor/XX (2)
When new software is built:
Make “modular” structure to enable reuse of “middle layers” from elsewhere.
Try reuse OSS, COTS, or existing internal components.
(Re)negotiate requirements vs. functionality from available components.
Make incentives to promote “lean code”? A any new code line will later consume 2X of initial cost, so aim for “negative” productivity!
Use incremental or agile lifecycle models, e.g. with 4-week increments.
Apply aSVN-like versioning tool for distributed software development.
But inevitably “software rot” of legacy code creeps in, as implicit assumptions made at start will increasingly hinder further changes.
Letizia
Telenor-NTNU OSS contact meeting, 18 Dec 2008

45. 5. OSS ideas for software maintenance at Company XX (3)
Maintenance: Any change after first release, 2/3 of costs.
To extend, perfect, correct – and restructure the given software. Need tools to analyze such legacy code.
Time pressure to prefer ”simple” changes, e.g. to copy and paste from existing code, just ameliorating the chaos.
Rather generalize existing code into product lines, and/or try to contribute to OSS, for both code and communities.
Possible link to Telenor’s EVISOFT activity with UiO on software maintenance, using e.g. complexity/cost analysis
More?? – all this depends on you at Telenor
Letizia
Telenor-NTNU OSS contact meeting, 18 Dec 2008

46. 6. Further cooperation berween XX and NTNU: some ideas? (1)
Possible cooperation activities
Subset of previous slide for Telenor activities
Possible work modes
Just NTNU internal
Informal by master and PhD students from NTNU: collect and analyze emirical data from case studies and field work
XX only, or XX + NTNU
Norwegian Research Council
Verdikt, BiA (three possible project types: FP, BP, and CP)
Postdocs, industri-stipendiater (50% coverage), other possibilities
EU’s FP7, ITEA2, Nordisk Råd, ….
Letizia
Telenor-NTNU OSS contact meeting, 18 Dec 2008

47. 6. NTNU Resources (2) Software engineering group (SU in Norwegian)
publications, student reports, and courses
(SU group homepage)
(publ. list)
(SU on OSS)
Wiki on open source research at NTNU
The ITEA2 COSI Project ( )
Norwegian partner IKT-Norge w/ subcontrcator NTNU
The Nordic OSS Network, Nordisk råd ( )
Seven partners incl. NTNU, coord. by Bjørn Lundell at U. Skøvde
Letizia
Telenor-NTNU OSS contact meeting, 18 Dec 2008

48. 6. Possible NTNU Resources (3)
NFR-VERDIKT proposal by R. Conradi and Alf Steinar Sætre (IØK): “Open Source Software & Industrial innovation Success factors (OSSIS), 15 Oct
NFR-VERDIKT proposal by R. Conradi, Daniela S. Cruzes (both NTNU), and Tonje Osmundsen (NTNU Samfunns-forskning (Eds.): “Maintaining Software Systems with an evolving network of open source providers (MAIN-SOFT), 25. Nov
Revised education plans
National research school
International master in OSS
Letizia
Telenor-NTNU OSS contact meeting, 18 Dec 2008

49. 6. NTNU resources: master students spring 2010 (4)
Proposed list of topics:
…??
Letizia
Telenor-NTNU OSS contact meeting, 18 Dec 2008