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. The Beta testing stage of the SDP






2. A data type used to store whole numbers






3. An evaluation criterion that assesses if the software can be used on a computer other than the one on which it was designed






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






5. Documentation designed for technical personnel that explains how to install software






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






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






8. High Level Code is converted into Machine Code






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






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






11. Testing programs as thoroughly as possible






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






13. A way of describing the design of a program eg. pseudocode or structure diagram






14. Writes code working to a software specification






15. Translates a high level language program into object code






16. Secting part of a string






17. Involves all the possible sets of test data and all of the program pathways






18. Revisiting or repeating steps in the SDP to improve the solution






19. Joining strings together






20. A data type used to store a single character






21. A loop which is carried out a set number of times






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






23. Test data which is on the boundary of what is acceptable by the program






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






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






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






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






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






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






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






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






32. How easy it is for your program to be read by anyone else






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






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






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






36. A data structure in which data items of the same type are grouped together






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






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






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






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






41. Used to enter and edit high level language code






42. Interviews company personnel and observes current procedures looking for ways to improve the system






43. A programmung language that uses english like statements. Must be translated into machine code






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






45. Variables defined only for use in one subprogram






46. Legally binding document defining the problem






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






48. Changing the software in response to changes in the client's hardware






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






50. In charge of the whole software development process