Software Production A new paradigm for software engineering research

Transcription

1 Software Production A new paradigm for software engineering research Sjaak Brinkkemper Utrecht University SOFSEM

2 Outline Software products Research framework Software types Economic context Software production Software product management, Software delivery Software ecosystems Incremental method evolution Educating software entrepreneurship Challenges for the research community Discussion 2

3 Societal context ICT innovations create new products, services, companies, jobs, economic value, social value International: Twitter Google SAP Oracle Microsoft Sage FaceBook Netherlands: TomTom Planon GX Exact Unit4 Afas Mendix 3

4 What is a Software Product? A Software Product is defined as a packaged configuration of software components, or a software-based service with auxiliary materials, which is released for and traded in a specific market (Xu & Brinkkemper, EJIS 2007) Examples: ERP software Bookkeeping service Operating systems Desk-top publishing Computer-aided design Software development environments Customer-relationship mgmt 4 Essentially all software you are using in daily life and work

5 What is being sold? What is product software? Device Microprogram Embedded software Software Tailor-made software Product software Online software Packaged software 5 Number of copies One Multiple

6 Key differences 1. Market introduction requires precise synchronization of dependable software engineering activities 2. The same product requires installation and usage in different organizations, with different hardware and software platforms 3. The vendor company stays owner of the software and auxiliary materials, while the usage is licensed to the customers 6

7 7 Research Framework for Software Production

8 Software types 1. System infrastructure software Foundation of software stack Security, systems management Not industry or function specific Many in open source Segments Operating systems Network, storage, security Utilities, anti-virus, archiving 2. Tools Development, execution Allow for composition, reuse, optimization Segments Portal and collaboration: user interface infrastructure Information management: data layer Modeling and development: for application logic Execution and Integration platforms: execution of appl. logic 8

9 Software types (2) 3. Applications Used by information workers and end-users Bring some level of automation in business processes Most are industry or function specific Few in open source Segments Office automation Horizontal business apps: finance&accounting, ERP, CRM Vertical business apps for industry specific solutions: billing, banking, travel reservations Technical applications: design and creation of physical products 4. Games and Consumer apps Consumer and professional games Strongest shift from packaged to online Segments Offline: Home consoles, handheld consoles, computers Online: PC and mobile phones Consumer apps: editing of video and photo, hobbies 9

10 Economic context OECD (2008): The product software sector is among the most rapidly growing sectors in OECD countries, with strong increases in value added, employment and R&D investment. EU 2.7 M employees NL Import 1,2 B, Export 1,6 B VS: 78% market share! NL: employees in NL companies 16 % of total ICT employment 10

11 European Software Market Overall market: 229 B in ,7% growth/year 11

12 12 Software revenue model

13 Assecco, Comarch AVG Tech, Avast ESET 13 Country SW revenues 2010 ( M) SW revenues 2011 ( M) % of total # Software companies Germany % 15 UK % 22 France % 17 Netherlands % 8 Sweden % 9 Norway % 4 Finland % 6 Italy % 3 Switzerland % 5 Belgium % 1 Poland % 2 Denmark % 1 Czech Rep % 2 Slovakia % 1 Spain % 2 Austria % 2 Total % 100 Source: Truffle 100, see

15 Deliverable structure Portfolio Product 1 Product 2 Product k Release 1.0 Release 1.1 Release 2.0 Requirement 1 Requirement 2 Requirement n Portfolio: The complete set of products of a company 15

16 Deliverable structure Portfolio Product 1 Product 2 Product k Release 1.0 Release 1.1 Release 2.0 Requirement 1 Requirement 2 Requirement n Product: A packaged configuration targeted to a specific market 16

17 Deliverable structure Portfolio Product 1 Product 2 Product k Release 1.0 Release 1.1 Release 2.0 Requirement 1 Requirement 2 Requirement n Release: A formalized sellable version 17

18 Deliverable structure Portfolio Product 1 Product 2 Product k Release 1.0 Release 1.1 Release 2.0 Requirement 1 Requirement 2 Requirement n Requirement: Wish for a future product feature 18

19 SPM Competence Model 19 Van de Weerd et al., RE 2006

20 Maturity matrix Maturity profile Maturity levels Focus area Requirements gathering A B C D Requirements identification A B C Requirements organizing A B C Requirements prioritization A B C D Requirements selection A B C D Release definition A B C Release validation A B C D Launch preparation A B C Scope change management A B C Theme identification A B C Core asset identification A B C Roadmap construction A B C Market trend identification A B C Partnering & contracting A B C Van de Weerd et al., ICSOB 2010 Product lifecycle management A B C 20

21 Maturity in SPM Focus Area None A B C D E F Portfolio management Market analysis Partnering & contracting Product lifecycle mgmt Release planning Roadmap intelligence Core asset roadmapping Product roadmapping Product planning Requirements prioritization Release definition Release definition validation Scope change management Build validation Launch preparation Requirements management data Requirements gathering Requirements identification Requirements organizing Many organizations have low maturity Percentage of organizations achieving the level Intriguing 21 Bekkers et al., RE 2012

22 Binary Priority Listing in large scale RM 22 Bebensee et al., REFSQ 2010

23 Customer Involvement Factory Reports of questions, complaints or bugs Approximately reports per year Handled by helpdesk and consultancy 85% can be solved by referring to the manual 15% is a bug or shortcoming 23 Kabbedijk et al., RE 2009

24 Scrum extension: Agile Requirements Refinery Requirements Refinery Scope 1 mth 3 mth 6 mth Req. definition Req. definition Req. definition Req. definition Req. definition Req. definition Concept Concept Concept Concept Daily scrum: 24h The Product Backlog contains a prioritized list of all items relevant to a specific product. This list can consist of bugs, customer requested enhancements, competitive product functionality, competitive edge functionality and technology upgrades Product Management Sprint: 2-6 weeks Vision Theme Theme Product Backlog Bugs Product Management Sprint Backlog Retrospective knowledge Updated Product Backlog 24 The Product Management Software Backlog consists of tasks that can be finished by the SPM team within the sprint Vlaanderen et al., IST 2011

25 Alternating Sprints Software Development Sprints Product Backlog Product Backlog Product Backlog time Product Management Sprints Development sprint backlog is always up-to-date and ready for use once the software development sprint starts Reduced time between inception of requirements and realization in the product Information flow-back from development to PM 25

26 Release planning with ILP Mathematical formalization using Integer Linear Programming Given are: Lists of requirements Revenue estimates Resource cost estimates Development teams and capacities Managerial steering mechanisms Team transfers Deadline extension External resources Mandatory requirements 26 Akker et al., REFSQ 2005; Li et al., REJ 2010

27 Development by one pool of developers There are n requirements R j. v j = estimated revenue of R j a j = estimated resources need for R j Q = number of developers in pool. T = development period d(t) = number of working days in planning period 27

28 Team development and transfers a ij = estimated resource need for R j from team i. There are m teams. Q i = number of developers in team i. U cap = atomic transfer capacity unit y ik = number of transfer capacity units from team i deployed in team k. a ki = transfer effectiviness factor (from team k to team i). 28

29 Key decisions in Software Start-ups Released: 17 Jan 2013 See Amazon 29

31 CCU - Customer Configuration Updating Receive Info Uninformed Customer Vendor Advertise Update Informed Customer Vendor Repository Receive Update Remove Product Deliver Update Deploy/Install Update Customer Possesses Update Rollback/ Deinstall Vendor Feedback Configure Installed Customer Jansen et al, ICSE 2006 Activate Update Deactivate 31 Reconfigure Activated Customer

32 32 Multi-tenancy in Product Lines

33 Patterns for Multi-tenancy Example Patterns Kabbedijk et al., WICSA/ECSA LAC2011

34 The Catalogue of Customization Realization Techniques Jansen et al., ICWE

36 36

37 37

38 38 Feedback in Software Supply Chains

39 Software Ecosystem Modeling Developed at Utrecht University Software Supply Network (SSN) Product Deployment Context (PDC) 39 Lucassen et al., ICSOB 2012

40 40 SECO models

41 Software Operation Knowledge Definition: Software Operation Knowledge is knowledge of inthe-field performance, quality and usage of software, and knowledge of in-the-field enduser software experience feedback Vd Schuur et al., CSMR

42 Book on Software Ecosystems Available March

44 The software startup Start-up Start with a simple process 44

45 Incremental Process Capability Product software company Gradual more extensive processen are added dependent on: product development culture internal maturity external stakeholders 45

46 On-line Method Engine Feedback Experiences (case studies) Existing methods (books, articles, online resources) Product software company Process need Need & situation analysis Method administration Selection of process alternatives Method Base Assembly of process advice - situational factors - method fragments - assembly rules - method fragments 46 Advice Van de Weerd et al., CAiSE 2007 Product Software Knowledge Infrastructure

47 Incremental Method Evolution 47 Van de Weerd et al., IST 2010

48 Formalization of Method Incrementation Definition 3.1 The mapping method: T M, where m = method(t) means that the method m M is the valid method at time t. Definition 3.6 A method increment is a method fragment ff such that i contains(f,method(t i )) contains(f,method(t i-1 )) Definition 3.7 The mapping insert F x M M: insert(f,m 1 ) = m 2 means that the method fragment f has been inserted in the method m 1 resulting into method m 2 Rule 3.1 Insertion of concepts insert(c,m i ) = m i+1 concept(c,m i ) concept(c,m i+1 ) Example insert(release TABLE,BaanIncr2) = BaanIncr3 concept(release TABLE,BaanIncr2) concept(release TABLE,BaanIncr3) The release table was not a concept in BaanIncr2 and therefore inserted to get BaanIncr3 48

49 Collaboration patterns 1 Product Mgr 3 Functional Designer 1 Technical Buddy 1 Sub-Team Lead/Architect 3 Developers 1 QA Manager 1 Tester Kristjansson et al., JKE Project Mgr 1 Team Lead/Architect 2 Developers Requirements Management Functional Design Exact Acceptance Testing Programming Deployment 49 Architecture Technical Design Levi9 QA Testing

50 Technical Functional Product Knowledge Center Project Kick Off Ongoing Development Team Transition Tacit focus Explicit focus Functional Collaboration Specification Grooming Knowledge Alignment Technical Assistance Product Knowledge Center Technical Documentation Product Transition 50 Nonaka spiral

52 Educating ICT Entrepreneurship Course ICT Entrepreneurship at Utrecht University, since 2002 Part of MSc in Business Informatics The students develop their own product or service ideas in a self composed team Role play in a virtual company as if there is one year in the company Students play a horizontal role in a staff dept: HRM, Finance, Marketing, Project Office, Technology, Investor Relations Mid review and End review for external Supervisory Board Deliverables as assignments: Product Definition, Market Plan, Project Plan, Business Model, Architecture, Business Plan, Prototype After the course, the students decide for continuation: office in incubator coaching and network company registration 52

53 Course Organization Horizontal teams for company experience Netherware Business Unit BV C CEO Supervisory Board Finance s1 Management Team s2 s4 s1 C HRM s5 Project Office Team 1 P1 Team 2 P2 Team 3 P3 Team n Pn s2 s1 s4 Marketing s4 s3 s2 s3 s5 53 Product teams for own product development

54 Netherware 54

55 Example products Examples 1. Hours accounting and invoicing for law firms 2. Warehousing for the retail industry 3. Utility and website to quit smoking 4. Dancing lessons in a browser 5. Camera placement for movie directors 6. Music distribution channel 7. Scanning with mobile phone 8. Simple multi-authoring tool for publishers 30+ start-ups with more than 100 jobs Permanent Software incubator Office space on campus 55

56 56 Yunoo

57 Course milestones Deliverables as assignments: Product Definition, Market Plan, Project Plan, Business Model, Architecture, Business Plan, Prototype All horizontals report bi-weekly to the lecturers, and prepare sections to the Year-end report Mid review to Supervisory Board (SuB) End review session with SuB The year-end report includes an spin-out plan for the next phase: Which products will be continued: extended, modified, Which products will be discontinued Which products will be nominated for external financing 57

58 Mid and End review All students present their products and business plans to Board of Supervisors 5 M Virtual Venture Capital Members of Board of Supervisors Venture capital fund IT entrepreneur Institutional investment IT journalist Marketing specialist 58

60 Research Challenges What are the fundamental theories of Software Production? How can optimal multi-tenant customizations be deployed in a secure manner? How can high volume requirements selection be performed in techno-economic alignment How can maturity growth in software production be supported by incremental method evolution Can we build fault tolerant components in the software supply chain, both from a technical as well as from an organizational perspective? What are the essential development tools for product development and deployment? 60

61 Discussion and Invitation Questions? Papers see: Contact me in case you are interested in joining a European project for Education in Software Entrepreneurship 61