Test your basic knowledge |

Software Development

Subject : it-skills
Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. How well your program operates without stopping due to design faults






2. Secting part of a string






3. Used to enter and edit high level language code






4. A design notation using different shaped boxes and showing hierarchy






5. Translates and runs a high level language one line at a time






6. Writes code working to a software specification






7. The movement of data between subprograms and implemented using parameters






8. A text-based design notation using ordinary language to define a problem






9. An evaluation criterion that determines how easy it is to maintain a program






10. Instructions that can be understood by the computer without the need for translation






11. A design notation using boxes linked by arrows showing data flow






12. A type of maintenance used to fix errors in a program






13. A data type used to store numbers with a decimal point






14. Software is evaluated for excessive resource use such as memory or backing storage






15. Testing programs as thoroughly as possible






16. A type of maintenance used to add new features to a program






17. Translates a high level language program into object code






18. How easy is the program to read? This is one way to evaluate a program.






19. In charge of the whole software development process






20. The process of finding and correcting errors in a program






21. Test data which should be rejected by the program under test conditions






22. A visual representation of the program design such as a Flowchart or Structure Diagram






23. Allowing users other than the programmers to test the program






24. A type of test data that tests the limits of the expected range of values






25. The ability of software to cope with errors during execution without crashing






26. A design methodology which begins with writing procedures and blocks of code






27. A loop contained within another loop






28. An area of memory used to store data in a program






29. A data type used to store more than one character






30. When a program is divided into smallers sections called subprograms






31. Breaks each step down as far as possible until each step can be turned into a line of code






32. A programming instruction that returns out a numerical task - e.g. LENGTH or RND or DIV






33. A loop that repeats instructions a set number of times eg - Loop 12 times






34. Joining strings together






35. A textual design notation that looks like a list of steps in English






36. Test data which is within a range that the program should accept






37. A stage of SDP that involves the planning of a solution to the problem






38. Documentation that explains how to operate the software once it has been installed






39. Converts high level code into machine code one line at a time and reports errors as they are found






40. Used to check that data input is with an acceptable range






41. Pre-defined and tested subprograms which speed up the SDP






42. A document that is produced at the end of the Analysis stage. It is a legal agreement between the client and developer






43. A data structure used to store a list of information of the same type






44. Does the program do what it was meant to do? This is one way to evaluate a program.






45. A series of actions that you record and then replay to automate tasks.






46. Used to count how many times a value appears in a list






47. Fixing bugs or mistakes which were not discovered at the testing stage






48. Converts high level code into machine code in a single operation and reports all errors at the end






49. How easy is the program to use? This is one way to evaluate a program.






50. The Beta testing stage of the SDP