Open Nordic 2008 NTNU

Embed Size (px)

DESCRIPTION

A presentation held at Open Nordic (http://conference.ez.no/) 2008.

Citation preview

  • 1. Software Engineering group Norwegian University of Science and Technology Reidar Conradi, yvind Hauge,Letizia Jaccheri, Eskil Sund www.idi.ntnu.no/grupper/su / www.research.idi.ntnu.no/oss Open Source Research at NTNU

2. Why is this interesting for you?

  • Experience from industry related research
    • What should we focus on in future research?
  • Experience from education
    • What should students know about Open source?

3. multi-faceted OS research political socialsciences software engineering learning psychology juridical & economical 4. research activities Focus on company based software engineering, reuse, and OTSITEA COSI projectCase Gentoo Education Open source and ArtCase Open standards (ARM) Open source surveyOTS surveys 5. Open Source Software (OSS):origin and now

  • 1650?:free flow of ideas begins inscientific community.

6. 1967-1977:DoD/DARPAs development ofArpanet / Internet TCP/IPprotocols -- open and distributed development, anti-authoritarian counter culture . 7. 1978-85:Openness spread throughBerkeleysadaptation ofUnix,with built-in Internet protocols and generous BSD licenses with all source provided. 8. 1985: Free / Open software:intl movements (Stallman). 9. 2000: Social computingandcreative commonsfor knowledge work standardized formats for zero-cost,digital information: Wikipedia, the world is flat, ... 10. 2008:1,5 billion Internet users, 3 billion w/ mobile phones. 11. OSS issues

  • 200.000 OSS projects,each w/net communitylead by original provider, co-developers, code integrators, users, ...

eZ has had 2.3 mill. downloads, Adobe Acrobat 500 mill.

  • COTS and OSS: many similarities.

12. Over 30 portals with domain-specific COTS/OSS software. 13. New way of makingopen ICT standards :rough consensus and (two implementations of) running code. 14. Over 50 licensing schemes. 15. Business model:open and shared source supported by a cooperative foundation; separate payable services.Ex. Apache web server. 16. Success criteria:for provider, for code integrator 17. OSS roles

  • OSS (component) provider:Leads a gone-open software project, ex. Linus Thorvald & Linux

18. OSS participant:assists the provider in more technical work the OSS idea of joint, altruistic work 19. OSS integrator:makes new software system byre-usingOSS software/components 20. OSS user:may download free (not open) binary software on a private computer, e.g. Acrobat 21. OSS customer:specifies and finances new software, later as OSS?

  • OSS skills:technical, commercial, organizational, creative

22. Software reuse, components,OTS = Off-The-Shelf (COTS, OSS)

  • Software reuse:by code libraries in repositories

23. Developfor reuse:make assets / components 24. Developwith reuse:CBSE using these assets 25. Advantagesof CBSE, own or OTS components:

    • Cheaper, earlier & better software
  • 26. Spread novel work practices & software architectures

27. Re-user communities for experience mgmt/support

  • Non-technicalobstacles:price/licensing, ROI, (re)negotiate rqmnts, less control, too radical

28. NTNU: CBSE and OTS studies

  • 1990-98: EU projects (e.g. REBOOT) oninternal software reuse ; hard!

29. 2000-: New global bazaar of COTS/OSS 30. 2003-08:Industrial surveyson OTS reuse Norway, Germany, Italia, China Developer panels and follow-up interviews with qualitative data to give insight 31. Research instruments and raw data: gone open please repeat our studies!! 32. NTNU: Roles in OTS-based reuse

  • From forthcoming paper by Jingyue Li et al., IEEE Software 2008

33. NTNU: learnings on OTS reuse

  • 1a. Ask colleagues to find right component;

1b. Otherwise search the net, download 3-6 candidates for evaluation and selection

  • Summary:no formal selection method, selection can be hosted by most lifecycle processes, need component uncle for maintenance, quality not a problem

34. Problems:effort estimation, integration, debugging, customer non-participation, licensing, company policies, how to classify components (ontologies) 35. Action Research on Gentoo OSS

  • PhD by Thomas sterlie

36. Gentoo: OSS release management tool, scripts, 300 co-developers in 40 countries 37. Worked as co-developer for two years; distributed, participative, in-process field study 38. Remote debugging: mutual guesswork, as sense-making, informal processes 39. Data: diaries, emails, IRC/version logs 40. research activities Focus on company based software engineering, reuse, and OTSITEA COSI projectCase Gentoo Education Open source and ArtCase Open standards (ARM) Open source surveyOTS surveys 41. ITEA COSI project

  • Industry and academia
    • Finland, Netherlands, Norway, Spain, Sweden
  • 2006-2008

42. Understand and benefit from Open source software and development practices

    • Shared internal development
  • Norwegian COSI
    • ICT Norway
    • eZ Systems, Keymind, Linpro, NTNU

Budget about 18 MNOK

  • Sponsored by NFR: about 8 MNOK

43. Adoption of OSS inthe Software Industry

  • About 50% reuse and integrate OSS components
    • Into all kinds of products
  • 44. To all kinds of customers

45. Large companies more often than small 46. Consultancy companies more often than software houses

  • 15-20% participate in OSS development
  • About 5% provide their own OSS products

47. Motivations for adoption of OSS

  • Simplify developers job
    • High availability of information, components and their source code
  • 48. Simple procurement
  • Reusable software assets
    • Increase productivity
  • 49. Increase quality
  • Reduced costs
    • Reduced development effort
  • 50. No licenses fees

51. Identification, Evaluation and Selection of OSS

  • Evaluation until something good enough is found

52. Tested further through test integration and prototyping

  • Informal knowledge driven process based on:
    • Previous experience
  • 53. Recommendations

54. Informal searches 55. Surveillance of the OSS community 56. research activities Focus on company based software engineering, reuse, and OTSITEA COSI projectCase Gentoo Education Open source and ArtCase Open standards (ARM) Open source surveyOTS surveys 57. Open standards and ARM

  • Cooperation between ARM Norway and NTNU (half dozen masters since 2002)
  • A masters project (single person one year)
    • development of a multi-platformgraphics application.
  • 58. Used ARMs platform forembedded graphics.

59. Open standards and ARM

  • Open Vector Graphics (OpenVG)
    • OpenVG is a standardfor embedded systems
  • 60. 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 providesuniform representation of 2D graphics.
  • 61. SVG Tiny A mobile profile targeting light weight mobile devices

62. Open standards and the application SVG Tiny application Application size ~20.000 LOC Open Standards PNG JPEG XML11 SMIL XLINK DOM3 Other W3C standards... PC platform ARM platform 63. Results from application development and porting

  • Ease of adoption
    • OpenVG is an open standard, thus royalty-free.
  • 64. Specification and reference implementation publicly available. No project expenses.
  • Performance
    • OpenVG allows for efficient and creative implementations.
  • 65. Efficient SVG Tiny viewer achievable on a regular PC and ARM platform.
  • Conformance
    • OpenVG conformance tests assure correct implementations.
  • 66. Consistent and correct behaviour of application on PC and ARM platform.
  • Portability
    • OpenVG API abstracts and de-couples application from hardware .
  • 67. High degree of application portability. Less effort

68. research activities Focus on company based software engineering, reuse, and OTSITEA COSI projectCase Gentoo Education Open source and ArtCase Open standards (ARM) Open source surveyOTS surveys 69. Cases: Art and open source software

  • Main objective SArt
    • to propose, and assess, and improve methods, models, and tools for software development in art context
  • Cases (sourceforge)
    • The Open Digital Canvas Project
  • 70. Sonic Onyx Project (mobile phones)

71. The Flyndre Project 72. SArt: art and open source software 73. Premiered art competitionThe Open Wall Open Contest

  • http:// mediawiki.idi.ntnu.no/wiki/sart /
  • Deadline 15th September

74. The prize award will take place at this years festival for art and technology in Trondheim, Trondheim Matchmaking, the 16th - 18th of October. 75. 1st prize 2000 , 2nd prize 1500 , 3rd prize 1000 76. NTNU Resources

  • Software engineering group
    • publications, student reports, and courses
    • http://www.idi.ntnu.no/grupper/su
  • Wiki on open source research
    • http:// research.idi.ntnu.no/oss
  • The ITEA COSI Project
    • http://www.itea-cosi.org/

77. Further work with NTNU: ideas?

  • We want feedback
    • What should we focus on in future research?
  • 78. What should students know about Open source?
  • Cooperation
    • National research school
  • 79. International master

80. Norwegian Research Council

  • Verdikt and other possibilities