APPENDIX 1 A STUDY ON EXPLORING THE IMPACT OF RELEASE MANAGEMENT TO ENHANCE THE QUALITY OF OPEN SOURCE SOFTWARE PROJECT MANAGEMENT

Transcription

1 177 APPENDIX 1 A STUDY ON EXPLORING THE IMPACT OF RELEASE MANAGEMENT TO ENHANCE THE QUALITY OF OPEN SOURCE SOFTWARE PROJECT MANAGEMENT QUESTIONNAIRE I. Personal and Socio-Economic Profile 1. Located in: A. Chennai B. Coimbatore 2. Gender: A. Female B. Male 3. Age Group: A. Below 30 years B years C. Above 40 years. 4. Marital status: A. Married B. Unmarried 5. Type of Family: A. Nuclear Family B. Joint family 6. Your highest formal Education level: A. Certificate/Diploma B. Bachelor C. Master

2 Working Industry segment: A. IT Enabled industry B. Software Development C. Consultant D. Others (Education, training, hardware, etc.) 8. State your position in the organization: A. Team Leader/ project Manager B. Software support engineers C. Software progrmmers 9. Experience In IT Sector: A. Below 5 years B years C years D. Above 15 years 10. The need for participating in Open Source Software Community: A. Personal needs B. Company needs C. Personal & Company needs D. Community needs 11. Usage of Open Source Software in your work environment: A. Yes B. Uncertain C. No 12. The extent of using Open Source Software in your work environment: A. Office Automation Tool B. Communication Tool C. Testing Tool D. Development Tool E. Version Control Tool 13. Your level of involvement in Open Source Software Development: A. Fully B. Partially C. Seldom D. Passive. 14. Experience in Open Source Software activity: A. Below 2 years B. 2-5 years C years D years E. above 15years

3 Annual salary income rupees in Lakhs: A. Less than 5 Lakhs B. 5-7 Lakhs C Lakhs E. Above 10 Lakhs 16. Income from Open Source Software Development activities: A. Yes B. No 17. If yes, in the range of A. Less than 3 Lakhs B. 3-5 Lakhs C. 5-7 Lakhs D. Above 7 Lakhs 18. Your Name : 19. Your personal address: II: Extent of Utilizing the Open Source Software No. Statement U CU PU F Un 20. Operating System(e.g. Linux) 21. Browser (e.g. Firefox) 22. Office Productivity Suite (e.g. OpenOffice,) 23. Communication Tool (e.g. IP Messenger) 24. clients (e.g. Thunderbird) 25. Web servers (e.g. Apache) 26. Database Application (e.g. MySQL) 27. Content Management (e.g. Drupal) 28. Learning Management Systems (e.g. Moodle) 29. File Sharing (e.g. File Zilla) 30. Mobility Applications (e.g. Symbian) 31. Software Development tools (e.g. CVS) 32. Financial and Accounting Software (e.g. GnuCash) 33. Security and Network Infrastructure(e.g. IP Firwall) 34. Enterprise Resource Planning or ERP (e.g. OFBiz) A. Used B. Currently Using C. Planning to use D. May be in future E. Uncertain

4 180 III: Significance of Open Source Software & Volunteer Community 35. Have the rights to see the source code of the program 36. Know more about how a particular program works 37. Liberty to modify the OSS we use 38. Provide alternatives to proprietary software 39. Quality software product 40. Ease of Use 41. Interface support with proprietary software applications 42. Hardware compatibility 43. Support for mobile applications 44. Main infrastructure for Cloud Computing 45. Documentation Guidance 46. Global Volunteer Community 47. Geographical Virtual Support 48. OSS Community Develops Innovative Software 49. OSSD is a way to become a better programmer 50. OSSPM is the most efficient way to develop software 51. OSS Technologies empowers individuals and communities 52. Opportunity to interact with like-minded programmers 53. As a user of OSS, want to give something back to the Community 54. Public Secure Network Communication

5 181 IV - Release Management Activities (A) Testing Process 55. Testing approach is followed before release 56. Adopting strategy in choosing your test cases 57. The code is tested by the user before release 58. Formal process exists for source code testing 59. Formal process exists for integration testing 60. User acceptance testing process are followed 61. Comparing the quality of Testing with proprietary software 62. Using peer review Testing to improve code quality 63. Quality process recommends preventive actions resulting from testing that affect the product 64. Quality Assurance activities are performed within the OSS project

6 182 (B) Defect Handling 65. Defect handling process is introduced in OSS project 66. Different kind of defects are recoded 67. The defect reporting effectiveness with priority and majority are assessed 68. The defect handling process in the project are regularly managed 69. Defect handling response time are rated 70. Security critical defects are solved on time before release 71. Status of rectified defects in source code are tracked 72. The documentation of the pre-release processes are assessed 73. The feedback between developers and users is direct and efficient 74. We assess the end user documentation (C) Release Activities 75. Release approach is followed by developers 76. Developers follow Time based release approach 77. Developers follow Feature based release approach 78. Post release review is adopted in OSS projects 79. Release check list is followed during release process 80. Changes are often made on a released version 81. Evolution of releases are referred version numbers 82. Critical issues of source code are determined before release 83. There is a inconsistency in developers and users requirements 84. The deadlines and Milestones are defined during release process

7 183 (D) Release Management Statement 85. Effective collaboration among volunteer community is needed for release management activities 86. High level of interdependency is a key factor in integrating source code during release activities. 87. Social and economic benefits motivates volunteers to evolve OSS project release 88. The Role efficacy of release management improves through collective work performance 89. Conformity and changeability in release schedule is possible through effective communication. 90. Electronic mode of communication bridges geographical distance among volunteers for effective functioning of release management 91. Effective interaction and feedback mechanism between developers and users leads to release of quality OSS products. 92. Time is an influential factor in project release phases as well as implementation of release schedule 93. Time management strategy promotes better planning for quality improvement of release activities 94. Benchmarking of release activities with other OSS projects is carried out SA A N DA SDA

8 184 PART-V (A) Quality Metrics in OSSPM 95. Quality is first learnt in your release process 96. Benchmarking is followed while planning quality in OSSPM 97. Document is maintained to record quality assurance Plans 98. Quality metrics is used in release processes 99. Quality baseline is used for measuring and reporting quality performance 100. Setting quality related standards, measures and procedures are determined for effective release management 101. Organizational quality policies, procedures and guidelines are used as inputs while designing the Quality Assurance Plan in release management 102. The Cost of Quality is significant 103. Quality control is performed before the source code is committed to the release repository 104. During project release, fault tolerance helps in maintaining performance of the product quality

9 185 (B) Quality Attributes of OSS 105. Software runs in multi Operating System environments 106. Software is written in a known programming language 107. Software should be modular 108. Software should be secure and reliable 109. Software application should be used in known native language 110. Software project has large and active developer community 111. Software project has large and active user/support community 112. Software development is supported by a Business Enterprise 113. Please specify, if any problems have been experiences in release management of OSS 114. Please write your opinion on improving the Open Source Software Projects with reference to Release Management Activities?