Software process and software testing tool survey
This survey collects information on the software processes and applied software tools of your organization. Answering to these questions is strictly voluntary. All the data will be handled anonymously, and no information will be delivered "as-is" to any third party. Partial summaries and anonymized quotes might be published as a part of academic publication, but with all references to names, locations, or any identifying information removed. Additionally, we encourage you to answer to all of the questions, but you are allowed skip questions, which you prefer not to answer.

The custodian of the collected data is School of Business and Management, Lappeenranta University of Technology, Finland. Please contact Dr. Jussi Kasurinen (jussi.kasurinen@lut.fi) for more information.

General information

1. Please estimate the size of your organization:
Including all full-time and part-time employees, trainees and external contractors working on your projects.

2. Please select the attributes, which describe you and your organization:

Software and Quality Assurance Processes

3. Please, estimate how the following claims describe your software development.
Scale: 1=fully disagree, 3=neutral, 5=fully agree
1
2
3
4
5
We like to transfer knowledge more by face-to-face conversation than by documents as the primary method of knowledge transfer.
Progress of the software is more important than thorough documentation.
Business people and developers work daily together in the projects.
Our process is able to cope with late changes in requirements, design, and technical platform.
We prefer more individuals, collaboration, and interaction than processes and tools.

4. Faults in your products can cause (please, select all suitable points)

5. Please, estimate following claims concerning your software testing. When the claim is not applicable leave the scale empty.
Scale: 1=fully disagree, 3=neutral, 5=fully agree
1
2
3
4
5
Our software correctly implements a specific function. We are building the product right.
Our software is built traceable to customer requirements. We are building the right product.
Our formal inspections are OK.
We go through checklists.
We keep code reviews.
Our unit testing (modules or procedures) is excellent.
Our integration testing (multiple components together) is excellent.
Our usability testing (adapt software to users' work styles) is excellent.
Our function testing (detect discrepancies between a program's functional specification and its actual behavior) is excellent.
Our system testing (system does not meet requirements specification) is excellent.
Our acceptance testing (users run the system in production) is excellent.
We keep our testing schedules.
Last testing phases are kept regardless of the project deadline.
We allocate enough testing time.

6. Do you follow a systematic method or process in the software testing (e.g. TPI, or ISO/IEC 29119-standard, or your own specified process)?

Testing and Quality Assurance Tools

7. Please select all of the applicable categories. Our organization has a dedicated tool, which manages the following testing aspect:
"Tool" can be an application, framework, web service, extra library, feature of your development environment etc. whichever supports completing the mentioned task. The options are roughly in order from very common to rare, as identified in one earlier survey.

8. Do you have a quality system certificate or a capability-maturity classification (e.g. CMM, SPICE, ISO-9001)?

9. Please, estimate following claims concerning problems.
Scale: 1=fully disagree, 3=neutral, 5=fully agree
1
2
3
4
5
Complicated testing tools cause test configuration errors.
Commercial testing tools do not offer enough support for our development platforms.
It is difficult to automate testing because of low reuse and high price.
Insufficient communication slows the bug-fixing and causes misunderstanding between testers and developers.
Defining detailed test cases is inefficient due to large amount of revisions needed during the development work.
Feature development in the late phases of the product development shortens testing schedule.
Testing personnel do not have expertise in certain testing applications.
Our testing tools do not support our software process model.
Existing testing environments restrict testing.
Software maintenance costs are constantly growing.
We do not have the necessary tools to extract enough information for efficient maintenance.

10. What actions does your organization take to manage the costs related to software maintenance? What actions has your organization taken recently (within 5 years) to manage maintenance costs?

Feedback

11. If you think that you need to emphasize some point, or add information we did not think to ask, or want to leave open feedback; please write it here.

12. If you wish to hear more concerning this study or its results, you can leave your contact information here. (You will receive max. 1 email /6 months)
If you prefer not to tell us your company/organization name but are interested in this study, you can always use your personal email and leave the company name blank.
Name
Email
Country
Company/Organization name
 
This button will submit the answers. Please press the button only once.