Symbiosis - Universiteit van Amsterdam

More documents

Recommendations

Info

[20] G. Hillenius. Taking the measure of IT. The Economist Intelligence Unit, 13 March, 2006. [21] R. Hirschheim, A. Heinzl, and J. Dibbern, editors. Information systems outsourcing: enduring themes, emergent patterns and future directions. Springer-Verlag, 2002. [22] D. Hosmer and S. Lemeshow. Applied logistic regression. Probability and Statistics. John Wiley & sons, 2rd edition, 2000. [23] ISO/IEC. 14143-1:1998. Software Measurement - Functional Size Measurement - Part 1 Definition of Concepts, 1998. [24] S. Klusener. Source code based function point analysis for enhancement projects. In IEEE International Conference on Software Maintenance (ICSM). IEEE Computer Society Press, 2003. [25] S. Klusener, R. Lämmel, and C. Verhoef. Architectural Modifications to Deployed Software. Science of Computer Programming, 54(2-3):143–211, 2005. [26] R. L. Krikhaar. Software Architecture Reconstruction. PhD thesis, Univ. of Amsterdam, The Netherlands, 1999. [27] M. Lacity and L. Willcocks. An empirical investigation of information technology sourcing practices: lessons from experience. MIS Quarterly, 22:363–408, 1998. [28] D. Nelson. Conditional Heteroskedasticity in Asset Returns: a New Approach. Econometrica, 59(2):347–370, 1991. [29] D. Rijsenbrij and G. Delen. Enterprise-architectuur is een noodzakelijke voorwaarde verantwoorde outsourcing (in dutch). IT Service Management best practices, 1:35–58, 2004. [30] C. Symons. Function point analysis: Difficulties and improvements. IEEE Transactions of Software Engineering, 14(1):2–11, 1998. [31] N. P. Veerman. Revitalizing Modifiability of Legacy Assets. Software Maintenance and Evolution: Research and Practice, Special issue on CSMR 2003, 16(4–5):219–254, 2004. [32] C. Verhoef. Quantitative IT Portfolio Management. Science of Computer Programming, 45(1):1–96, 2002. [33] C. Verhoef. Quantifying the Value of IT-investments. Science of Computer Programming, 56(3), 2005. [34] C. Verhoef. Quantitative Aspects of Outsourcing Deals. Science of Computer Programming, 56(3), 2005. [35] C. Verhoef. Quantifying Software Process Improvement, 2006. Available via www.cs.vu.nl/˜x/spi/spi.pdf. 16
[36] L. Willcocks and M. Lacity. IT outsourcing in insurance services: risk creative contracting and business advantage. Information Systems Journal, 9:163–180, 1999. 9 Budget For an overview of the project costs we refer to Table 4. Each of the industrial partners has committed itself to spend at least 5 person days a year on Symbiosis, 20 person days over 4 years. As discussed earlier in this proposal, the contribution of each industrial partner consists of: • The delivery of appropriate data of their outsourcing projects. This will be a variety of data such as contractual agreements, Service Level Agreements, project administrative data, functional/technical specifications, source code, test cases, acceptance/fail rates, etc. It takes time to select and collect the relevant information, furthermore the Symbiosis researchers will have interviews with various people to obtain the background information that is needed to do their research. • During each case-study the research will be followed closely by the industrial partner and intermediate results will be evaluated. • Each year there will be a plenary session where the Symbiosis researchers present their work to the industrial partners and where the industrial partners will present their questions and problems. Hence, these 5 person days are the absolute minimum, when the project will start (expected at the end of 2006) the case studies will become clear and more detailed agreements can be made. It is to be expected that some of the industrial partners will actually participate many more than the 5 person days a year that we use now in our budget calculation. Some of the industrial partners have already agreed a larger participation, as can be seen in Table 4. Given the large number of industrial partners we have used an average fee of 125,euro per hour for all industrial partners. Note that the names that are given in Table 4 indicate the contact person of each industrial partner. 17
Page 1 and 2: Symbiosis: Synergy of managing busi
Page 3 and 4: 4.2 Component B: Academic researche
Page 5 and 6: decision transition control softwar
Page 7 and 8: Relevance for the industry. In the
Page 9 and 10: Case study: outsourcing a large dep
Page 11 and 12: failure of a sourcing relationship.
Page 13 and 14: software architectures. Similarly w
Page 15: [5] T. Bollerslev, R. Engle, and D.

Symbiosis - Universiteit van Amsterdam

Create successful ePaper yourself

Delete template?

Save as template?