1. Software Supply Networks (SSNs) Software developers need to develop software quicker Reuse is cheap and quick Problems: – How do components integrate? – How are partnerships created? – What should the product architecture look like? – How are partnerships and architectural design decisions related? Possible method development: – Software service composition – Software component composition and COTS evaluation – Software feedback analysis (usage/feedback) – Development of a Domain Specific Language – Partner selection for software partnering – Product placement planning – Feedback redirection in a SSN Software Supplier Third Party Software Supplier Operational Environment n Operational Environment m Operational Environment 1...... Open Source Supplier Software Developers IntegratorsEnd-users A small Software Supply Network

2. Software Supplier Third Party Software Supplier Operational Environment n Operational Environment m Operational Environment 1...... Open Source Supplier Software Developers IntegratorsEnd-users A small Software Supply Network

3. Software Supply Networks (SSNs) Software service composition Software component composition and COTS evaluation Software feedback analysis (usage/feedback) Development of a Domain Specific Language Partner selection for software partnering Product placement planning Feedback redirection in a SSN

4. Service Composition Describe a method on how services from third-party providers are composed to be used in a SSN http://www.zurich.ibm.com/pdf/ebizz/icaps- ws.pdf http://www.zurich.ibm.com/pdf/ebizz/icaps- ws.pdf

5. Software component composition and COTS reuse Develop a method to evaluate and compose COTS to be used in a component system http://www.sei.cmu.edu/pub/documents/03.r eports/pdf/03tr017.pdf http://www.sei.cmu.edu/pub/documents/03.r eports/pdf/03tr017.pdf

6. Software feedback analysis Develop a method that deals with software feedback as it comes in. The method has two levels: a strategic and practical one. Bowring, J., Orso, A., and Harrold, M. 2003. Monitoring deployed software using software tomography. SIGSOFT Softw. Eng. Notes 28, 1 (Jan. 2003), 2-9. DOI= http://doi.acm.org/10.1145/634636.586099

7. Domain Specific Language Development Develop a method that describes howto develop a domain specific language and apply it to software development. A. van Deursen and P. Klint. Domain-Specific Language Design Requires Feature Descriptions. Journal of Computing and Information Technology, 10(1):1-17, 2002. (pdf, bib)P. Klintpdfbib

8. Partner selection in Software Engineering Develop a method to select partners in software development. COTS evaluation is a sub-activity in this method. This method includes a company visit. An approach to partner selection in agile manufacturing - Journal Journal of Intelligent Manufacturing Publisher Springer Netherlands ISSN 0956-5515 (Print) 1572-8145 (Online) - Issue Volume 10, Number 6 / December, 1999 DOI 10.1023/A:1008956620461 Pages 519-529 Subject Collection Business and Economics SpringerLink Date Thursday, October 28, 2004Journal of Intelligent ManufacturingVolume 10, Number 6 / December, 1999 Business and Economics

9. Product Placement Planning for Product Software Develop a method to do product placement planning for product software. Potentially includes a company visit. Providing Transparency In The Business Of Software: A Modeling Technique For Software Supply Networks – Jansen, Brinkkemper, Finkelstein

10. Developing Novel Business Models for Software Products and Platforms Develop a method to design new business models for pre-existing software products and platforms. Includes company visit. Sjaak Brinkkemper, Ivo van Soest, and Slinger Jansen. Modeling of product software businesses: Investigation into industry product and channel typologies. In The Inter-Networked World: ISD Theory, Practice, and Education, proceedings of the Sixteenth International Conference on Information Systems Development (ISD 2007). Springer-verlag, 2007.

11. Making Build-or-Buy decisions Develop a method for making build-or-buy decisions for software services and components. Includes a company visit. A process model of make-vs.-buy decision-making. The case ofmanufacturing software Buchowicz, B.S. Dept. of Manage., Loyola Univ., Chicago, IL; This paper appears in: Engineering Management, IEEE Transactions on, Publication Date: Feb 1991, Volume: 38, Issue: 1, On page(s): 24-32, ISSN: 0018-9391, References Cited: 54, CODEN: IEEMA4 INSPEC Accession Number: 3880014, Engineering Management, IEEE Transactions onIssue: 1 Alternative Entry Paths: The Build or Buy Decision (scholar.google.com)

12. Partner Knowledge Network Development Develop a method for partner knowledge network development, study the processes at a company who has recently begun partnering. http://repub.eur.nl/publications/index/705942770/ Slinger Jansen, Gerco Ballintijn, Sjaak Brinkkemper, Arco van Nieuwland: Integrated development and maintenance for the release, delivery, deployment, and customization of product software: a case study in mass-market ERP software. Journal of Software Maintenance (SMR) 18(2):133-151 (2006) Slinger JansenGerco BallintijnSjaak Brinkkemper Arco van NieuwlandJournal of Software Maintenance (SMR) 18(2):133-151 (2006)

13. Feedback Redirection and Analysis Develop a method that describes how feedback must be redirected in the product software company. Check out papers from Inge, Slinger, and Henk van der Schuur. Slinger Jansen, Sjaak Brinkkemper, and Tijs van der Storm. Living on the cutting edge: Automating continuous customer configuration updating. In Proceedings of the ERCIM Workshop on Software Evolution 2007, ICSM 2007, Paris. Slinger Jansen. Pheme: An infrastructure to enable any type of communication between a software vendor and an end-user. In International Conference on Software Maintenance 2007, tool demonstration, 2007.

14. Implementing C-CCU across mulptiple developing organizations Develop a method that enables C-CCU across different SW developing organisations. C-CCU is Continuous Customer Configuration Updating. See all papers by Jansen in the area of CCU, specifically the ERCIM paper and the Pheme paper. Slinger Jansen, Sjaak Brinkkemper, and Tijs van der Storm. Living on the cutting edge: Automating continuous customer configuration updating. In Proceedings of the ERCIM Workshop on Software Evolution 2007, ICSM 2007, Paris. Slinger Jansen. Pheme: An infrastructure to enable any type of communication between a software vendor and an end-user. In International Conference on Software Maintenance 2007, tool demonstration, 2007.

15. Testing Service Compositions in a SOA Develop a testing method for service compositions in a SOA. Assume that elementary services have already been tested and only the composition of a new service needs to be tested. Bieberstein, N., Bose, S., Fiammante, M., Jones, K., Shah, R. (2005). Service-Oriented Architecture (SOA) Compass: Business Value, Planning, and Enterprise Roadmap. DC: IBM PRESS Hurwitz, J., Bloor, R., Baroudi, C., Kaufman, M. (2007). Service Oriented Architecture For Dummies. Hoboken: John Wiley & Sons, Inc. Find your own literature. http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1628907 http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1342703

16. Business Model development for Services Develop a method that can assist Service oriented organisations in developing a business model. Currently services are being developed but it is hard to sell these services. How can they sell their products? Service-oriented computing: concepts, characteristics and directions Papazoglou, M.P. Dept. of Inf. Syst. & Manage., Tilburg Univ., Netherlands;

17. Making Architectural Changes to create New Business Value Create a method that enables a product software to change portions of their product to approach new markets. Involves company visit, probably. http://www.jillesvangurp.com/publications/06- VanGurpEtAl-position.pdf http://www.jillesvangurp.com/publications/06- VanGurpEtAl-position.pdf Fifth IEEE International Symposium on Requirements Engineering (RE'01) p. 0316 Evolving System Architecture to Meet Changing Business Goals: An Agent and Goal-Oriented Approach Fifth IEEE International Symposium on Requirements Engineering (RE'01) Evolving System Architecture to Meet Changing Business Goals: An Agent and Goal-Oriented Approach