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. NULL memory.






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






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






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






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






6. Treating a derived class's data members like it's base class's.






7. Uploads changes to your current branch.






8. Function doesn't exist.






9. Link multiple projects together






10. When GIT cannot merge your data.






11. You have to tell it to link






12. What is part of the current scope.






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






14. Helps to eliminate unnecessary "include chaining."






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






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






17. Functionality Tests.






18. Quick program.






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






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






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






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






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






24. Inheritance between object.






25. Create a test and then create a function.






26. When a class is defined within another class.






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






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






29. Stops when memory changes.






30. Use only through the interface of the object.






31. Formatted code standards.






32. Code generation in a lib






33. Downloads your changes and then merges.






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






35. STOP!!






36. Makes a copy of your repository.






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






38. Default branch within your repository.






39. Breaks encapsulation boundaries.






40. Initialized stack memory.






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






42. Italicized in UML.






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






44. Variable doesn't exist.






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






46. No more than 40 hours to stop burnouts.






47. Puts all headers into a master header.






48. A measure of logical dependency.






49. Set of all pending changes.






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