Entry Survey

Please complete the items provided to the best of your ability. This survey is in several parts. The completion of one part should load the next. Click on the submit button at the bottom of each page when you completed the form. To function properly, this form requires the use of a JavaScript enabled browser.

I. Development Activities

Here is a list of the various things that might be done in a software project. Check the appropriate response to indicate how often you do each of these when you develop a program for a class assignment.

ActivityNeverSometimesAlways
1.review the problem given to be sure you understand what the program is expected to do
2.seek clarification from the course instructor about points of confusion and vagueness with regard to the problem statement
3. write the program requirements from the user's perspective
4.write a specification, based on all the inputs and all the outputs, of the expected program behavior
5. create a written plan, based on the specification, for testing the program
6. create a written design for the program before implementation
7. write the pre- and post-conditions for all routines before implementing
8.review the design against the specification before implementing
9.ask a peer to review design against the specification before implementing
10. ask the instructor to review design against the specification before implementing
11. create a written plan, based on the design, for testing the program
12. review the test plan based on the design
13. systematically review the pre- and post-conditions
14.completely develop the code from the design prior to compilation
15.conduct a reading of the code (desk check) prior to compilation
16. code/compile/debug until the program runs
17.modify the design as the program evolves during compilation
18. ask peer to review code against the design before compilation
19. generate test cases from the test plan indicating the intention of each test case and how it relates to the specification or design
20. systematically test using prepared test cases from the test plan summarizing the results versus expectations
21.review the test results and revise the design accordingly
22.review the test results and revise the implementation accordingly
23. ask peer to review code before submitting
24. read and review the program documentation before submission
25.draw a structure chart for the program once it runs correctly
26. reflect upon the activities in developing a program and write an improvement plan