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 class is defined within another class.






2. Static in C++. Can span all instances of a class.






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






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






5. Puts all headers into a master header.






6. Try to find the flaws in your code.






7. Link multiple projects together






8. Uploads changes to your current branch.






9. Code generation in a lib






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






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






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






13. Breaks encapsulation boundaries.






14. Stops when memory changes.






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






16. When GIT cannot merge your data.






17. Create a test and then create a function.






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






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






20. Ignores files when pushing.






21. Formatted code standards.






22. Use only through the interface of the object.






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






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






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






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






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






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






29. Are what function classes should include.






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






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






32. What is part of the current scope.






33. One of the linking methods (pragma comment)






34. Italicized in UML.






35. Function doesn't exist.






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






37. The default nickname for the remote repository.






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






39. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






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






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






42. When doing a - precise task.






43. Fix any problems and then repeat the process.






44. Input






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






46. Initialized heap memory.






47. Simply a value.






48. A measure of logical dependency.






49. Code whatever it is you need to code.






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