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. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






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






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






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






5. A function that can load a library






6. Current line that is executing.






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






8. Taking code and moving it to a function that usually returns an object. They are always virtual functions.






9. Current view/ previous line.






10. 2 Eyes + 2 Minds = AWESOME!






11. Invalid or unexpected input that the program is not designed to process.






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






13. Inheritance between object.






14. Try to find the flaws in your code.






15. A reference. Has and delete dynamic memory. implies ownership (Association does not).






16. Italicized in UML.






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






18. When GIT cannot merge your data.






19. A collection of memory addresses for all virtual functions in an objects class hierarchy.






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






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






22. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






23. Downloads without merging.






24. Breaks encapsulation boundaries.






25. Creates a copy of your current branch into a remote branch.






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






27. Function doesn't exist.






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






29. Trying to access a location in memory that your computer cannot access.






30. No more than 40 hours to stop burnouts.






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






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






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






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






35. Ignores files when pushing.






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






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






38. Helps to eliminate unnecessary "include chaining."






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






40. When we remove redundant or obsolete designs and replace them with a new.






41. Code generation in a lib






42. Variable doesn't exist.






43. Meetings used to create a release plan - which will lay out the overall project.






44. A measure of logical dependency.






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






46. What is part of the current scope.






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






48. Functionality Tests.






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






50. Input