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. A design methodology which begins with writing procedures and blocks of code






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






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






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






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






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






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






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






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






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






11. Used to enter and edit high level language code






12. A data type used to store whole numbers






13. In charge of the whole software development process






14. Types of data stored by a program including string and integer and real and single






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






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






17. The Beta testing stage of the SDP






18. A type of maintenance used when a program needs to be updated to run on new hardware or software






19. How well your program operates without stopping due to design faults






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






21. Used to find a target value in a full list






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






23. A stage of the SDP where a user guide and technical guide are produced






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






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






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






27. A data type used to store a single character






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






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






30. A loop contained within another loop






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






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






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






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






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






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






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






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






39. High Level Code is converted into Machine Code






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






41. Testing programs as thoroughly as possible






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






43. A loop that repeats instructions until - or while - a condition is met eg - Repeat / Until X > 0






44. Writes code working to a software specification






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






46. NOT/OR?AND






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






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






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






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