Development and Code Management of Large Software Systems

• Autorzy: Hubert Zarzycki , Jacek Czerniak
• Języki publikacji: EN

Abstrakty

EN

This paper will help developers and testers understand waterfall software development process of large-scale software products and how to effectively use the approach, tools, and techniques applicable to maintain such systems. The study particularly focuses on code management and code inspection. The software integrity inspection process is described as used in selected departments of Lucent Technologies. The authors present processes and principles that rule software code changes and quality control of performed changes. Key words: software engineering, waterfall model, code management, code inspection, software development process, software quality. (original abstract)

Słowa kluczowe

EN

Management; Control; Software; Software quality

PL

Zarządzanie; Kontrola; Oprogramowanie; Jakość oprogramowania

• Czasopismo: Studia i Materiały Polskiego Stowarzyszenia Zarządzania Wiedzą
• Rocznik: 2010
• Tom: 27
• Strony: 327--339

Twórcy

autor

Hubert Zarzycki

• University of Technology & Life Sciences, Bydgoszcz

autor

Jacek Czerniak

• Kazimierz Wielki University in Bydgoszcz

Bibliografia

• [1]Atkins D., Bali, T., Graves, T., Mockus, A. (2002): Using Version Control Data to Evaluate the Impact of Software Tools: A Case Study of the Version Editor, IEEE Transactions on Software Engineering 28 (7), s. 625-637.
• [2]Atkins, D., Bali, T., Graves, T., Mockups, A. (1999): Using Version Control Data to Evaluate the Effectiveness of Software Tools, in, 1999 International Conference on Software Engineering, Los Angeles, ACM Press.
• [3]Czerniak J., Śpiewak W. (2004): Large-Scale Software Development in a Multinational Software Corporation, Computer Programming and Applications (18), Nakom, Poznań.
• [4]Midha, A. K. (1997): Software Configuration Management for the 21st Century, Bell Labs Technical Journal 2 (1).
• [5]Mockus, A., Eick, S. G., Graves, T. L., Karr, A. F. (1999): On Measurement and Analysis of Software Changes, Technical Report, Bell Laboratories.
• [6]Mockus, A., Weiss, D. M., Zhang, P. (2003): Understanding and Predicting Effort in Software Projects, in: International Conference on Software Engineering, Portland, May 3-10, ACM Press, p. 274-284.
• [7]Perpich, J. M., Perry, D. E., Porter, A. A., Votta, L. G., Wade, M. W. (1998): Anywhere, Anytime Code Inspections: Using the Web to Remove Inspection Bottleneck in Large-Scale Software Development.
• [8]Petersen K., Wohlin C., Baca D. (2009): The Waterfall Model in Large-Scale Development, Lecture Notes in Business Information Processing 32, Springer Berlin Heidelberg, p. 386-400.
• [9]Porter, A. A., Siy, H. P., Votta, L. G. (1997): Understanding the Effects of Developer Activities on Inspection Interval, I9th International Conference on Software Engineering.
• [10]Regner P., Wiesinger T., Kueng J., Wagner R. (2003): Towards a Process Model for Efficient Advertised Bidding in the Field of Software, LNCS Volume 2739/2003, Springer Berlin, pp 1075.
• [11]Raccoon LBS (1997): Fifty years of progress in software engineering. SIGSOFT Softw.
• [12]Eng. Notes 22(1), p. 88-104.
• [13]Rochkind M. (1975): The Source Code Control System, IEEE Transactions on Software Engineering 1(4), p. 364-370.
• [14]Royce W. (1970): Managing the development of large software systems, Proceedings of IEEE Wescon, p. 382-338.