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. Uploads all changes staged in the index list into the repository database.






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






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






4. Makes a copy of your repository.






5. Fix any problems and then repeat the process.






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






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






8. Breaks encapsulation boundaries.






9. When doing a - precise task.






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






11. Quick program.






12. Functionality Tests.






13. Views all previous changes.






14. Function doesn't exist.






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






16. No more than 40 hours to stop burnouts.






17. Default branch within your repository.






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






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






20. Formatted code standards.






21. Classes build off of each other.






22. Helps to eliminate unnecessary "include chaining."






23. Will execute all code paths and boundary conditions.






24. Downloads your changes and then merges.






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






26. When GIT cannot merge your data.






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






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






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






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






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






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






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






34. 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






35. A measure of logical dependency.






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






37. One of the linking methods (pragma comment)






38. Undo changes made since your last commit.






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






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






41. Create a test and then create a function.






42. Application






43. Ignores files when pushing.






44. Italicized in UML.






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






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






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






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






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






50. A set of creation and initialization steps useful for a set of different related tests.