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. Whats displayed to the screen






2. Breaks encapsulation boundaries.






3. Ignores files when pushing.






4. STOP!!






5. Valid input that the program is designed to process.






6. CONSTANT






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






8. Current line that is executing.






9. When doing a - precise task.






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






11. Formatted code standards.






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






13. Initialized heap memory.






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






15. How many objects that a source object can legitimately reference.






16. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






17. Application






18. Put this before a function name in a dll - and the function name will avoid name mangling






19. Code whatever it is you need to code.






20. Portioning your changes to commit by inserting them into the index.






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






22. Keeps a team using a similar naming convention for things.






23. Set of all pending changes.






24. Italicized in UML.






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






26. Uploads changes to your current branch.






27. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






28. About the interface to an object. Data contained within.






29. Try to find the flaws in your code.






30. Puts all headers into a master header.






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






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






33. Allows you to switch your working copy to another branch.






34. Undo changes made since your last commit.






35. When a concrete class inherits from a pure interface.






36. Classes build off of each other.






37. The default nickname for the remote repository.






38. What is part of the current scope.






39. Stand up meetings show who will be valuable and needed.






40. When a conflict is fixed.






41. Will execute all code paths and boundary conditions.






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






43. Copies all changes from one branch into another branch.






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






45. Freed heap memory.






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






47. A function that can load a library






48. Views all previous changes.






49. Separating out a section of code into a reusable function or class.






50. Written by the customers as things that the system needs to do for them.