參考文獻 |
[1] https://msdn.microsoft.com/zh-tw/library/5t6z562c(v=vs.90).aspx
[2] Archibald, R. D. (2003). Managing high-technology programs and projects. John Wiley & Sons.
[3] Ardis, M., Budgen, D., Hislop, G. W., Offutt, J., Sebern, M., & Visser, W. (2015). SE 2014: Curriculum Guidelines for Undergraduate Degree Programs in Software Engineering. Computer, 48(11), 106-109.
[4] Arnold, R. S., & Bohner, S. A. (1993, September). Impact Analysis-Towards a Framework for Comparison. In ICSM (Vol. 93, pp. 292-301).
[5] Artto, K., Martinsuo, M., Gemünden, H. G., & Murtoaro, J. (2009). Foundations of program management: A bibliometric view. International journal of project management, 27(1), 1-18.
[6] Belknap, J. K., Mitchell, S. R., O′Toole, L. A., Helms, M. L., & Crabbe, J. C. (1996). Type I and type II error rates for quantitative trait loci (QTL) mapping studies using recombinant inbred mouse strains. Behavior genetics, 26(2), 149-160.
[7] Breech, B., Danalis, A., Shindo, S., & Pollock, L. (2004, September). Online impact analysis via dynamic compilation technology. In Software Maintenance, 2004. Proceedings. 20th IEEE International Conference on (pp. 453-457). IEEE.
[8] Briand, L. C., Labiche, Y., O’Sullivan, L., & Sówka, M. M. (2006). Automated impact analysis of UML models. Journal of Systems and Software, 79(3), 339-352.
[9] Chen, C. Y., & Chen, P. C. (2009). A holistic approach to managing software change impact. Journal of Systems and Software, 82(12), 2051-2067.
[10] Chen, C. Y., Liao, G. Y., & Lin, K. S. (2015). An attribute-based and object-oriented approach with system implementation for change impact analysis in variant product design. Computer-Aided Design, 62, 203-217.
[11] Christensen, E., Curbera, F., Meredith, G., & Weerawarana, S. (2001). Web services description language (WSDL) 1.1.
[12] Conradi, R., & Westfechtel, B. (1998). Version models for software configuration management. ACM Computing Surveys (CSUR), 30(2), 232-282.
[13] Dart, S. (1991, May). Concepts in configuration management systems. InProceedings of the 3rd international workshop on Software configuration management (pp. 1-18). ACM.
[14] Dallal, G. V. (2007). The little handbook of statistical practice. Gerard V. Dallal.
[15] Estublier, J. (2000, May). Software configuration management: a roadmap. InProceedings of the Conference on the Future of Software Engineering (pp. 279-289). ACM.
[16] Fensel, D., & Bussler, C. (2002). The web service modeling framework WSMF.Electronic Commerce Research and Applications, 1(2), 113-137.
[17] Ferns, D. C. (1991). Developments in programme management. International Journal of Project Management, 9(3), 148-156.
[18] Fisher, S. R. A. (1956). Mathematics of a Lady T4sting Tea.
[19] Great Britain. Office of Government Commerce. (2007). Managing successful programmes. The Stationery Office.
[20] Hassine, J., Rilling, J., Hewitt, J., & Dssouli, R. (2005, September). Change impact analysis for requirement evolution using use case maps. In Principles of Software Evolution, Eighth International Workshop on (pp. 81-90). IEEE.
[21] Hardion, V., Spruce, D. P., Lindberg, M., Otero, A. M., Lidon-Simon, J., Jamroz, J. J., & Persson, A. (2013). Configuration Management of the control system. THPPC013.
[22] ICM. (1999). Configuration Management II: Change Effectivities, Forms and Traceability. Institute of Configuration Management.
[23] Jammes, F., & Smit, H. (2005). Service-oriented paradigms in industrial automation. IEEE Transactions on Industrial Informatics, 1(1), 62-70.
[24] Jung, H. W., Kim, S. G., & Chung, C. S. (2004). Measuring software product quality: A survey of ISO/IEC 9126. IEEE software, (5), 88-92.
[25] Kögel, M. (2008, May). Towards software configuration management for unified models. In Proceedings of the 2008 international workshop on Comparison and versioning of software models (pp. 19-24). ACM.
[26] Law, J., & Rothermel, G. (2003, November). Incremental dynamic impact analysis for evolving software systems. In Software Reliability Engineering, 2003. ISSRE 2003. 14th International Symposium on (pp. 430-441). IEEE.
[27] Leon, A. (2015). Software configuration management handbook. Artech House.
[28] Li, B., Sun, X., Leung, H., & Zhang, S. (2013). A survey of code‐based change impact analysis techniques. Software Testing, Verification and Reliability, 23(8), 613-646.
[29] Loya, S. R., Kawamoto, K., Chatwin, C., & Huser, V. (2014). Service oriented architecture for clinical decision support: A systematic review and future directions. Journal of medical systems, 38(12), 1-22.
[30] Lycett, M., Rassau, A., & Danson, J. (2004). Programme management: a critical review. International Journal of Project Management, 22(4), 289-299.
[31] Morris, P., & Pinto, J. K. (2010). The Wiley guide to project, program, and portfolio management (Vol. 10). John Wiley & Sons.
[32] OGC. (2003) Managing successful programmes. UK: Office of Government Commerce OGC, The Stationery Office.
[33] Pellegrinelli, S. (1997). Programme management: organising project-based change. International Journal of Project Management, 15(3), 141-149.
[34] Pine, B. J. (2000). Markets of one: Creating customer-unique value through mass customization. Harvard Business Press.
[35] Project Management Institute [PMI]. (2013). A Guide to the Project Management Body of Knowledge(PMBOK Guide), 5th Edition, Newtown Square, PA, USA.
[36] Quigley, J. M., & Robertson, K. L. (2015). Configuration Management: Theory, Practice, and Application. CRC Press.
[37] Robertson, S., & Robertson, J. (2012). Mastering the requirements process: Getting requirements right. Addison-wesley.
[38] Stellingwerf, R., & Zandhuis, A. (2013). ISO 21500 Guidance on project management-A Pocket Guide. Van Haren.
[39] Sun, X., Leung, H., Li, B., & Li, B. (2014). Change impact analysis and changeability assessment for a change proposal: An empirical study☆☆.Journal of Systems and Software, 96, 51-60.
[40] Team, C. P. (2010). CMMI® for Development, Version 1.3.
[41] Zhao, J. (2002, May). Change impact analysis for aspect-oriented software evolution. In Proceedings of the International Workshop on Principles of Software Evolution (pp. 108-112). ACM. |