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






2. Uploads changes to your current branch.






3. Functionality Tests.






4. Stops when memory changes.






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






6. Do not optimize until the very end.






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






8. Plan out your code.






9. Link multiple projects together






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






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






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






13. Freed heap memory.






14. Breaks encapsulation boundaries.






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






16. STOP!!






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






18. Puts all headers into a master header.






19. Application






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






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






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






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






24. Ignores files when pushing.






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






26. Helps to eliminate unnecessary "include chaining."






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






28. Whats displayed to the screen






29. Current line that is executing.






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






31. Downloads your changes and then merges.






32. Simply a value.






33. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






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






35. Downloads without merging.






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






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






38. A measure of logical dependency.






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






40. Views all previous changes.






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






42. Create a test and then create a function.






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






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






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






46. One of the linking methods (pragma comment)






47. Use only through the interface of the object.






48. Quick program.






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests