Understanding the role of Communication in Software Engineering
This survey is designed for programmers/developers at various levels to contribute knowledge based on their experience about ways in which the software product and its related artefacts contribute to communication failure or success which in turn affect the quality of the software product.

This research is being conducted by the E-Learning Systems Research Group at The Department of Computing, in the University of The West Indies, Mona. For any questions please contact Dr. Claudine Allen at claudine.allen@uwimona.edu.jm
Sign in to Google to save your progress. Learn more
How many years of software development experience do you have (include your years of software engineering university/college education)? *
Your current software engineering status is: *
Your role is: *
Each of the following represents an aspect of software development that is dependent on clarity in understanding between the stakeholders who create and use it. Based on your experience, specify the risk level associated with a communication breakdown or a lack of clarity in the strategy (e.g. language, style, standard, tool or method) between stakeholders in each of the following areas: *
low risk
medium risk
high risk
code
code comments
technical documentation
commit messages
version control strategy
issue or bug descriptions and tooling
communicating design details
interface descriptions
test plans
code review
Recommended Strategies
In this section you will be asked to specify strategies you would recommend based on your experience.
What strategy(ies) do you use and recommend for improving clarity between stakeholders in relation to programming code:
What strategy(ies) do you use and recommend for improving clarity between stakeholders in relation to documentation:
What strategy(ies) do you use and recommend for improving clarity between stakeholders in relation to version control:
What strategy(ies) do you use and recommend for improving clarity between stakeholders in relation to reporting and management of issues and bugs
What strategy(ies) do you use and recommend for improving clarity between stakeholders in relation to the communication of designs and design decisions
What strategy(ies) do you use and recommend for improving clarity between stakeholders in relation to interface design and description (service interfaces not GUI)
What strategy(ies) do you use and recommend for improving clarity between stakeholders in relation to testing
Please state any other artefacts or aspects of software design hat you believe impact upon stakeholder (especially those involved in the development process) understanding and communication and state any strategies you would recommend for improving or ensuring clarity.
Would you be willing to participate in a focus group geared toward understanding communication issues that affect software quality? *
If you are willing to participate in the focus group please provide us with an email address at which we can reach you with an invitation. The focus group will not exceed 1.5 hours and it will be done online. The results will contribute to our efforts to develop a model for describing communicability requirements and tactics for a software. As a participant you will receive early access to the results of the overall research.
In what country do you do work as a developer? *
Submit
Clear form
Never submit passwords through Google Forms.
GoogleForms
This content is neither created nor endorsed by Google.