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 conflict is fixed.






2. Fix any problems and then repeat the process.






3. One of the linking methods (pragma comment)






4. Input






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






6. Plan out your code.






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






8. Downloads without merging.






9. Downloads your changes and then merges.






10. Breaks encapsulation boundaries.






11. Use only through the interface of the object.






12. Link multiple projects together






13. Classes build off of each other.






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






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






16. STOP!!






17. Undo changes made since your last commit.






18. Adds files to the repository.






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






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






21. Code whatever it is you need to code.






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






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






24. CONSTANT






25. Makes a copy of your repository.






26. Removes files from the repository.






27. Formatted code standards.






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






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






30. The linking is already done internally






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






32. Helps to eliminate unnecessary "include chaining."






33. Freed heap memory.






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






35. The default nickname for the remote repository.






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






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






38. Encapsulates a request as an object - thereby letting you parameterize clients with different requests - queue or log requests - and support undoable operations.






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






40. Views all previous changes.






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






42. No more than 40 hours to stop burnouts.






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






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






45. Puts all headers into a master header.






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






47. Are what function classes should include.






48. Inheritance between object.






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






50. Functionality Tests.