Some questions are non applicable.
The purpose of this questionnaire is to collect data for an empirical research
on software quality estimation. We aim at building an effective model based on
historical project information, in order to reveal the quality factors in
software engineering and help obtain high quality software in the future.
We would appreciate if you kindly provide us the information of your project by
filling the questionnaire. A few minutes out of your busy schedule will enable
us to achieve our research objectives.
Simply reply this email and put ‘X’s in the brackets besides your choices.
1. Is there a specific plan/schedule for the project?
( )A. Very clear schedule
( )B. Somehow clear schedule
( X)C. No schedule
2. How often will the project publish new releases (on average)?
( )A. Every week
( )B. Every month
( X)C. Every quarter
( )D. Every six months
( )E. Every year
( )F. Other _______
3. What is the average related software development experience of the
developers? (language, application and platform)
( )A. <1 year
( )B. 1-3 years
(X)C. 3-5 years
( )D. >5 years
4. What is the percentage of personnel change during the development?
( )A. <10%
( )B. 10% - 20%
( )C. 20% - 30%
( )D. 30% - 40%
( )E. >40%
5. Is there any similar project (functionality and implementation)?
( )A. None
(X)B. A few
( )C. Many
6. Is there any reliability requirement for the project?
(X)A. Low: Slight inconvenience or very small losses when fails;
( )B. Nominal: Moderate losses when fails;
( )C. High: High financial losses, or risk to life when fails.
7. Is there any response time constraint?
(X)A. Low: No or loose time constraint;
( )B. Nominal: Common time constraints, no special request;
( )C. High: Strict time limit or real time system.
8. How do you deal with modularity in the project?
( )A. Clearly designed during the design stage
( )B. Prepared at the beginning of the development phase
(X)C. Redesigned during the development stage
( )D. No consideration of modularity
9. What is the complexity of data management in the project?
(X)A. Very low: Simple arrays in main memory. Simple DB queries, updates;
( )B. Low: Single file subsetting with no data structure changes, no edits, no
intermediate files. Moderately complex DB queries, updates;
( )C. Nominal: Multi-file input and single file output. Simple structural
changes, simple edits. Complex DB queries, updates;
( )D. High: Simple triggers activated by data stream contents. Complex data
restructuring;
( )E. Very high: Distributed database coordination. Complex triggers. Search
optimization.
10. What is the computational requirement in the project?
(X)A. Very low: Only basic math expressions involved;
( )B. Low: Standard math/statistical routines needed;
( )C. Nominal: Basic numerical data analysis like ordinary differential
equations and regular calculation accuracy required;
( )D. High: Complex data analysis such as partial differential equations;
( )E. Very high: Accurate numerical analysis with noisy, stochastic data.
11. What is the level of control flow in the project?
(X)A. Very low: Straightforward nesting structured programming with simple
decision conditions;
( )B. Low: Basic nesting with decision tables; Simple callback and message
exchange;
( )C. Nominal: Highly structured programming with complicated predicates;
Queue and stack control; Basic distributed processing;
( )D. High: Reentrant and recursive coding. Simple interrupt handling. Task
synchronization, complex callbacks, heterogeneous distributed processing; Soft
real time control;
( )E. Very high: Complex interrupt handling with changing priorities; Hard
real time control.
12. What is the requirement of user interface management?
( )A. Low: Simple forms;
( )B. Nominal: Graphic user interface;
( )C. High: 2D/3D, dynamic graphics; multimedia.
13. Do you have test plan for the project?
(X)A.. Very clear test plan (test phases, test cases)
( )B. Somehow clear plan (basic requirements)
( )C. No test plan
14. Do you use any tool for testing?
(X)A.Yes (Name JUnit)
( )B. No
15. What percentage of source code is covered during testing?
( )A. < 20%
( )B. 20% - 40%
( )C. 40% - 60%
(X)D. 60% - 80%
( )E. > 80%
16. The previous coverage information is derived from:
(X)A.. Coverage tool (Name Cobertura)
( )B. Rough estimation
17. Is the total number of bugs recorded correctly in the Bug Tracking
System?(If not, please give a number)
(X)A.Yes
( )B. No (Number ________)
18. How many users are involved in the project?
( )A. < 5
( )B. 5 - 10
( )C. 10 - 50
( )D. 50 – 100
(X)E. > 100
19. What percentage of defects/bugs do users report?
( )A. < 20%
( )B. 20% - 40%
( )C. 40% - 60%
( )D. 60% - 80%
(X)E. > 80%
20. What percentage of total development effort is used for testing?
( )A. < 20%
(X)B. 20% - 40%
( )C. 40% - 60%
( )D. 60% - 80%
( )E. > 80%
21. What documentation is used to help new developers get onboard?
( )A. Detailed definition of processes and development guidelines available
(X)B. Major guidelines available
( )C. No particular documentation
22. How is the user documentation prepared?
( )A. Detailed and comprehensive
(X)B. Important parts covered
( )C. Only draft and incomplete version
( )D. No particular documentation
End of the questionnaire
Department of Electrical and Computer Engineering
University of Western Ontario
London, ON. CANADA
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
JWebUnit-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jwebunit-development
