Use Computer Science Research

Australian Questionnaire Results

The USE CSR project looked at the application of Software Engineering to Computer Science Research, and whether this gives tangible benefits. Software Engineering was used to refer to the body of knowledge including Analysis, Design, Software Development Life Cycle, Software Process, Software Documentation, Software Metrics, Project Management. The items in bold were covered in this survey.

Return to the extended results page or to the methods page

.

* Country where most of your education has taken place: Australian Results Summary Results
* Country where most of your research has taken place: Australian Results Summary Results
* My position can best be described as: Australian Results Summary Results
  If you answered other to the question above, please elaborate: Australian Results Summary Results
* The field I trained in can best described as: Australian Results Summary Results
  If you answered other to the question above, please elaborate: Australian Results Summary Results
* I work at (name of: University or Company or Organisation): Australian Results Summary Results
* I am affiliated with the following department(s) / fields: Australian Results Summary Results
* I have been involved in the software development / software research area professionally for: Australian Results Summary Results
* Have you taught a Software Engineering Subject Australian Results Summary Results
* Have you studied software engineering either as part of a degree or on your own (e.g. through books or papers) ? Australian Results Summary Results
* Have you used graphical models to design programs ? Australian Results Summary Results
* Which of the following tools / methodologies do you know and / or use?
Functional
Specifications
Australian Results Summary Results
Flow
Charts
Australian Results Summary Results
Data Flow
Diagrams
Australian Results Summary Results
Entity Relationship Diagrams
Australian Results Summary Results
Class / Package Diagrams
Australian Results Summary Results
Interaction
Diagrams
Australian Results Summary Results
State
Diagrams
Australian Results Summary Results
State Transition Diagrams
Australian Results Summary Results
Booch
Notation
Australian Results Summary Results
Use
Cases
Australian Results Summary Results
Use Case
Diagrams
Australian Results Summary Results
Unified Modeling Language
Australian Results Summary Results
Specification Language
Australian Results Summary Results
Waterfall
SDLC
Australian Results Summary Results
Fountain
SDLC
Australian Results Summary Results
Spiral
SDLC
Australian Results Summary Results
Rapid Application Development
Australian Results Summary Results
Technical
Reviews
Australian Results Summary Results
Black Box
testing
Australian Results Summary Results
White Box
Testing
Australian Results Summary Results
Unit
Testing
Australian Results Summary Results
Integration
Testing
Australian Results Summary Results
JavaDoc
Commenting
Australian Results Summary Results
Systematic Internal Comments
Australian Results Summary Results
Meaningfully named variables
Australian Results Summary Results
Rational Rose
Australian Results Summary Results
Structured A&D
Australian Results Summary Results
Design Walk through
Australian Results Summary Results
Code Reviews
Australian Results Summary Results
Requirements Reviews
Australian Results Summary Results
Prototyping
Australian Results Summary Results
Formal Methods
Australian Results Summary Results
MS Project
Australian Results Summary Results
Compiler
Australian Results Summary Results
Debugger
Australian Results Summary Results
  1) Other SE tool you know: Australian Results Summary Results
  2) Other SE tool you know: Australian Results Summary Results
  3) Other SE tool you know: Australian Results Summary Results
  1) Other SE tool you use: Australian Results Summary Results
  2) Other SE tool you use: Australian Results Summary Results
  3) Other SE tool you use: Australian Results Summary Results
* Why do you use the methods you use ?
1. Saves time in the long run
2. Helps me clarify my ideas 3.Makes communicating easier across the team
4. Makes communication easier between projects
5. Assists with producing better quality software
Australian Results Summary Results
  Other reasons for using these techniques / methods / tools Australian Results Summary Results
* Why don't you use (more often) the methods you described as "know but don't use" or "use rarely" in the question above?
1. Never thought about it
2. Don't know about them
3. Cost of learning them is too high
4. They are not appropriate for my work
5. Cost of using them is higher than the pay off
6. Organisational Policy against spending time on them
7. Other
Australian Results Summary Results
  Other reasons for not using other techniques / methods / tools Australian Results Summary Results
* Have your usage patterns changed over time ? 1. Used to use none now use a lot
2. Used to use none, now use a little
3. Used to use some now use more
4. No change
5. Used to use a little but stopped or decreased my use
6. Used to use a lot now use a little
7. Used to use a lot now use none
Australian Results Summary Results
* I expect to use 1. Less in the future
2. The same amount in the future
3. More in the future
Australian Results Summary Results
  Comment: The following questions are project related.
Your answers here may need to differ from your answers in the above questions. Please choose 1 project you have been involved with and answers your questions in relation to this project. After submitting this form you will be given the options of ending the survey or entering another project. If you intend entering more than one project it would be useful for comparison if one of these had significantly better outcomes than the other(s)
* Project's Name WITH HELD
* Institution / Company where it was carried out WITH HELD
* The year the project was started Australian Results Summary Results
  The year the project was completed (or is scheduled to be completed). Australian Results Summary Results
* The department in the organisation you were working in had: 30. Under 30 people in it
50. Under 50 people people in it
100. Under 100 people people in it
200. Under 200 people people in it
201. 200 or more people in it
Australian Results Summary Results
* Project management was controlled by: 1. Individual team members setting their own schedules or delivering goods when they completed them
2. The project group by consensus
3. The project leader with little input from organisational management
4. The project leader with some input from organisational management
5. Organisational management
Australian Results Summary Results
* The organisation had: 1. No formal policy for approach to projects
2. A limited amount of formalism e.g. project applications, interim reports, final reports
3. A large amount of formalism e.g. specification of design languages and programming languages to be used and types of documentation to be created (e.g. design, testing, user manuals etc)
Australian Results Summary Results
* Which best describes the project's approach to Analysis and Design: 1. Analysis & Design was done before coding was started
2. Analysis & Design was done while coding
3. Analysis of the problem took place after the project was completed
4. Analysis & Design was not explicitly done
5. Analysis prior to coding, design not possible (due to the projects nature) (please explain why this was so below)
Australian Results Summary Results
* Given more time and / or money, would you go back and create / update design documents after coding
Australian Results Summary Results
  If you indicated `design not possible' above, please explain why Australian Results Summary Results
* Which best describes the projects approach to documentation: 1. Detailed and useful documentation was started before coding (e.g. Analysis and / or Design documents) and kept 2. Some useful documentation was started before coding (e.g. a useful project proposal) and kept 3. Some useful external documentation was created during coding and kept (design documents, Javadoc, etc) 4. The only documentation on the project code is by way of papers relating to the project (and a users manual / inbuilt help).
Australian Results Summary Results
* The projects development was modeled on a software development life cycle model: 1. Waterfall
2. Fountain
3. Spiral
4. RAD
5. The development was according to some other explicit model
6. The development was not planned or systematic
Australian Results Summary Results
* How many different people worked on the project at one point or another (in total) Australian Results Summary Results
* At its peak, how big was the project team Australian Results Summary Results
* Roughly how much funding did the project receive (in total) Australian Results Summary Results
* Number of complete re-writes of software Australian Results Summary Results
* Time spent in planning the project (in months): Australian Results Summary Results
* Time spent on development (In months): Australian Results Summary Results
* Meeting Frequency: 1. Monthly
2. Fortnightly
3. Weekly
4. Daily
Australian Results Summary Results
* Meeting duration on average: 1. 30 minutes
2. 1 hour
3. 2 hours
4. Half day
5. All day
Australian Results Summary Results
* Reuse, how many/much code was reused when building this project 1. standard classes e.g. template libraries, Java standard library
2. some code of a previous version of the software
3. Some small components that developers already had
4. Some small components that developers found (e.g. from GNU)
5. Largely based on an existing framework
6. Research was a plug in to another piece of software
Australian Results Summary Results
* Were you able to get all the resources you asked for ? e.g. programmers, machine time, hardware etc
Australian Results Summary Results
* Personal satisfaction with project outcomes 1. Much less then other projects
2. Less than other projects
3. about the same
4. More than other projects
5. Much more than other projects
Australian Results Summary Results
* Personal frustration with project process 1. Much less then other projects
2. Less than other projects
3. about the same
4. More than other projects
5. Much more than other projects
Australian Results Summary Results
* Looking back would you use more things (e.g. analysis, design, documentation, reviews, testing etc) earlier on if you had to redo the project ?
Australian Results Summary Results
* Papers published as a result of this project: Australian Results Summary Results
* Number of modification / addition projects to the main research (e.g. summer vacation, honors, post grad projects) Australian Results Summary Results
* Number of students who continued on with research related to the project after finishing their initial involvement (e.g. honors students who went on to do further research) Australian Results Summary Results
* Number of Students involved in project as part of a higher degree by research Australian Results Summary Results
* Average papers published per Higher Degree by Research student relating to the project and their work on it Australian Results Summary Results
* Is there a user group for the software produced
Australian Results Summary Results
* What grants were attracted Australian Results Summary Results
* What is/was the value of these grants ($AUS) Australian Results Summary Results
* How do you rate the success of the project ? Australian Results Summary Results
  I would like further communication with this survey: WITHHELD
  Comment: The following question are to enable further communication in relation to this research.
If you wish to remain anonymous, feel free not to answer them.
  Email Address WITH HELD
  Name: This is used only in communication to you by e-mail WITH HELD