Test your basic knowledge |

SWA - Software Architecture

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. Undo changes made since your last commit.






2. Ability to treat a class object as a function by overloading the () operator.






3. When a class is defined within another class.






4. Quick program.






5. Ensure a class only has one instance - and provide a global point of access to it






6. Developers should be integrated and releasing code into the code repository every few hours.






7. Allows consumers to try a system earlier and give early feedback.






8. Current line that is executing.






9. Set of all pending changes.






10. Code generation in a lib






11. A type of library that is used by the code






12. The linking is already done internally






13. Bad! Don't ever use these types of variables!






14. Meetings at the beginning of each iteration to produce a plan of programming tasks.






15. No man's land. Guard bytes before the after allocated heap memory.






16. Helps to eliminate unnecessary "include chaining."






17. Uploads all changes staged in the index list into the repository database.






18. Link multiple projects together






19. Uploads changes to your current branch.






20. Takes information in the index and pushes it onto the stack.






21. A pointer or reference. One object needs to know about the other object to work.






22. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






23. Downloads without merging.






24. Stops when memory changes.






25. Puts all headers into a master header.






26. Do not optimize until the very end.






27. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






28. Initialized stack memory.






29. Creates a spin-off of a repository for concurrent development.






30. Variable doesn't exist.






31. Concept based on limiting the scope of modules to provide better structures.






32. Black Box - The way the program works is internally unknown.






33. Removes files from the repository.






34. Makes a project compile in order of who is dependent on what






35. Static in C++. Can span all instances of a class.






36. Try to find the flaws in your code.






37. Fix any problems and then repeat the process.






38. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






39. Create a test and then create a function.






40. Ask questions and obtain the details and requirements given.






41. Having power over inheritance with the flexibility of composition.






42. Use this to find a memory address or signiture in a dll






43. Figure out what is feasible. Decide whether to use API's or to write from scratch.






44. Always do the simplest design that could possibly work.






45. When doing a - precise task.






46. Ability to accept different types of parameters to bind to different implementations at run-time.






47. Use only through the interface of the object.






48. Ability to withstand change and what the effects are.






49. Current view/ previous line.






50. When you type in an object - you can see its attributes.