Use of Software Engineering in Computer Science Research

US Results

Return to the US results page or to the methods page.

*	Country where most of your education has taken place:
*	Country where most of your research has taken place:
*	My position can best be described as:
	If you answered other to the question above, please elaborate:	Data
*	The field I trained in can best described as:
	If you answered other to the question above, please elaborate:	Data
*	I work at (University or Company or Organisation):	Data
*	I am affiliated with the following department(s) / fields:	Data
*	I have been involved in the software development / software research area professionally for:
*	Have you taught a Software Engineering Subject
*	Have you studied SE either as part of a degree or on your own (eg through books or papers) ?
*	Have you used graphical models to design programs ?
*	Which of the following Software Engineering tools / methodologies do you know and / or use?	Functional Specifications Flow Charts Data Flow Diagrams Entity Relationship Diagrams Class / Package Diagrams Interaction Diagrams State Diagrams State Transition Diagrams Booch Notation Use Cases Use Case Diagrams Unified Modeling Language Specification Language Waterfall SDLC Fountain SDLC Spiral SDLC Rapid Application Development Technical Reviews Black Box testing White Box Testing Unit Testing Integration Testing JavaDoc Commenting Systematic Internal Comments Meaningfully named variables
	1) Other SE tool you know:	Data
	2) Other SE tool you know:	Data
	3) Other SE tool you know:	Data
	1) Other SE tool you use:	Data
	2) Other SE tool you use:	Data
	3) Other SE tool you use:	Data
*	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
	Other reasons for using Software Engineering techniques	Data
*	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
	Other reasons for not using other Software Engineering techniques	Data
*	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
*	I expect to use	1. Less in the future 2. The same amount in the future 3. More in the future
	Comment:	The following questions are project related. Please choose 1 project you have been invovled with and answers your questions in relation to this project. Your answers here may as a result need to differ from your answers in the above questions.
*	Project's Name	Not shown due to privacy
*	Institution / Company where it was carried out	Not shown due to privacy
*	The year the project was started
	The year the project was completed (or is scheduled to be completed).
*	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 in it 201. 200 or more people in it
*	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
*	The organisation had:	1. No formal policy for approach to projects 2. A limited amount of formalism eg project applications, interim reports, final reports 3. A large amount of formalism eg specification of design languages and programming languages to be used and types of documentation to be created (eg design, testing, user manuals etc)
*	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
*	Which best describes the projects approach to documentation:	1. Detailed and useful documentation was started before coding (eg Analysis and / or Design documents) and kept 2. Some useful documentation was started before coding (eg 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).
*	The projects development was modelled 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
*	How many different people worked on the project at one point or another (in total)
*	At its peak, how big was the project team
*	Roughly how much funding did the project recieve (in total)
*	Number of complete re-writes of software
*	Time spent in planning the project (in months):
*	Time spent on development (In months):
*	Meeting Frequency:	1. Monthly 2. Fortnightly 3. Weekly 4. Daily
*	Meeting duration on average:	1. 30 minutes 2. 1 hour 3. 2 hours 4. Half day 5. All day
*	Reuse, how many/much code was reused when building this project	1. Standard classes eg 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 (eg from GNU) 5. Largely based on an existing framework 6. Research was a plug in to another piece of software
*	Were you able to get all the resources you asked for ? eg programmers, machine time, hardware etc
*	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
*	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
*	Looking back would you use more Software Engineering (eg analysis, design, documentation, reviews, testing etc) earlier on if you had to redo the project ?
*	Papers published as a result of this project:
*	Number of modification / addition projects to the main research (eg summer vacation, honors, post grad projects)
*	Number of students who continued on with research related to the project after finishing their initial involvement (eg honors students who went on to do further research)
*	Number of Students involved in project as part of a higher degree by research
*	Average papers published per Higher Degree by Research student relating to the project and their work on it
*	Is there a user group for the software produced
*	What grants were attracted	Information Restricted
*	What is/was the value of these grants ($US)
*	How do you rate the success of the project ?	Data
	I would like further communication with this survey:	1. Contact when the results are collated only (a link to summarised results will be provided) 2. Contact me if needed to clarify my answers or if a followup survey is conducted, as well as notifying me when results are collated 3. Do not contact me again regarding this survey
	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	Restricted for Privacy
	Name: This is used only in communication to you by e-mail	Restricted for Privacy

Please report any problems with this questionnaire to the researcher: Andre.Oboler@csse.monash.edu.au.