Key Factors for Improving Software Ecosystems Practice - KDE Community
This questionnaire is part of my thesis whose goal is to investigate and understand Improvement in Software Ecosystems Practices. This thesis is being conducted at Federal University of Bahia, Brazil. We are investigating how changes affect the quality of the ecosystem through practices to meet the needs of the organizations for the ecosystem to achieve its full potential.

We aim to identify key factors for software ecosystem improvement based on community opinion. These key factors were defined based on a literature review. The questionnaire has two parts. In part 1, considering KDE ecosystem, please select key factors that you consider to contain practices that facilitate the improvement of a software ecosystem.  In part 2, considering KDE ecosystem, please analyze the graph and choose the weight among the relationships of the key factors. The results of this survey will be used in an evaluation study of Software Ecosystems Practice Improvement. Your opinion is very important to the success of our research. All information you provide will be kept confidential.
Sign in to Google to save your progress. Learn more
Name *
Select your work area. *
On which projects of KDE do you work? *
What are your activities in the KDE community? *
Programmer, Reviewer, Designer, Tester, Evangelist, etc.
Part 1
Select the importance of the key factors to the improvement of the ecosystem.
1. Communication *
The imparting or interchange of ideas, opinions, or information among the members of community.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
2. Experience of Developers *
Knowledge or practical wisdom of the developers
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
3. Interactions *
Interactions and working together among developers.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
4. Rewards *
Compensation for working in the ecosystem.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
5. Responsibilities *
A particular burden of obligation for each person. Roles and tasks defined in the community.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
6. Cost Management *
Control and Directions of cost in the software ecosystem.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
7. Market Share *
Control and directions of market actions in the shared environment of the ecosystem.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
8. Return on Investment *
Return on investment from effort contributed to the ecosystem.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
9. Risk Management *
Control and direction of risks on the software ecosystem.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
10. Making Decisions *
Management of decision making with regard to the software ecosystem.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
11. Technology Forecasting *
Making predictions about technology usefulness to the software ecosystem.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
12. Understanding Relevant Domains *
Understanding relevant domains within which the ecosystem works.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
13. Automation Tools *
Use of automation tools in several tasks of the ecosystem.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
14. Backward Compatibility *
Keep backward compatibility among versions developed in the ecosystem.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
15. Change Management *
Control and direction of changes performed in the software.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
16. Documentation *
Documentation existing about the processes and products.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
17. Quality Attributes *
Quality attributes of the software ecosystem architecture.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
18. Refactoring *
Actions intended to improve the software ecosystem architecture.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
19. Testing *
Processes to assess the software in the ecosystem environment.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
20. Human Conflict Management *
Control and direction of human conflicts in the ecosystem environment.
Definitely Unimportant
Probably Unimportant
Relative
Probably Important
Definitely Important
21. Do you consider any other key factors important? What are their significance/influence?
Another key factor not cited above.
Part 2
Select the influence of the relationships in the graph.
Relationship among key factors
Relationship A *
Risk Management - Human Conflict Management
Relationship B *
Risk Management - Communication
Relationship C *
Risk Management - Responsibilities
Relationship D *
Risk Management - Change Management
Relationship E *
Risk Management - Backward Compatibility
Relationship F *
Risk Management - Testing
Relationship G *
Cost Management - Experience of Developers
Relationship H *
Cost Management - Rewards
Relationship I *
Making Decisions - Automation Tools
Relationship J *
Making Decisions - Experience of Developers
Relationship K *
Making Decisions - Responsibilities
Relationship L *
Making Decisions - Interactions
Relationship M *
Making Decisions - Documentation
Relationship N *
Making Decisions - Refactoring
Relationship O *
Quality Attributes - Understanding Relevant Domains
Relationship P *
Experience of Developers - Technology Forecasting
Relationship Q *
Technology Forecasting - Change Management
Relationship R *
Documentation - Cost Management
Relationship S *
Return on Investments - Communication
Relationship T *
Return on Investments - Refactoring
Relationship U *
Quality Attributes - Making Decisions
Relationship V *
Backward Compatibility - Cost Management
Relationship W *
Communication - Market Share
Relationship X *
Experience of Developers - Understanding Relevant Domains
Relationship Y *
Interactions - Market Share
Relationship Z *
Backward Compatibility - Technology Forecasting
Do you consider any other relationship among key factors important?
Another relationship not cited above.
Do you have any additional suggestion or comment?
Submit
Clear form
Never submit passwords through Google Forms.
This content is neither created nor endorsed by Google. - Terms of Service - Privacy Policy

Does this form look suspicious? Report

Google Forms