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. Use only through the interface of the object.






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






3. Whats displayed to the screen






4. Link multiple projects together






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






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






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






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






9. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






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






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






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






13. When a class is defined within another class.






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






15. Default branch within your repository.






16. Simply a value.






17. NULL memory.






18. When a conflict is fixed.






19. Fix any problems and then repeat the process.






20. 2 Eyes + 2 Minds = AWESOME!






21. Helps to eliminate unnecessary "include chaining."






22. What is part of the current scope.






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






24. Puts all headers into a master header.






25. A measure of logical dependency.






26. Symbols that can not be accessed by code in other units have __________. These symbols are usually static non-member functions/variables defined within.c/.cpp or defined in an anonymous namespace.






27. Freed heap memory.






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






29. Functionality Tests.






30. Function doesn't exist.






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






32. Application






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






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






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






36. Initialized stack memory.






37. Formatted code standards.






38. The default nickname for the remote repository.






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






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






41. Uploads changes to your current branch.






42. Weak relationship between two classes. Almost always results in a #include.






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






44. Breaks encapsulation boundaries.






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






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






47. CONSTANT






48. Input






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






50. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere