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 changes to your current branch.






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






3. One of the linking methods (pragma comment)






4. Variable doesn't exist.






5. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere






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






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






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






9. Removes files from the repository.






10. When a class is defined within another class.






11. Freed heap memory.






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






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






14. Plan out your code.






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






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






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






18. Classes build off of each other.






19. The default nickname for the remote repository.






20. Quick program.






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






22. No more than 40 hours to stop burnouts.






23. Use only through the interface of the object.






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






25. Adds files to the repository.






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






27. Whats displayed to the screen






28. Current view/ previous line.






29. When a conflict is fixed.






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






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






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






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






34. CONSTANT






35. Current line that is executing.






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






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






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






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






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






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






42. The linking is already done internally






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






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






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






46. 2 Eyes + 2 Minds = AWESOME!






47. Code generation in a lib






48. The process of deciding which function definition to link during run-time.






49. Downloads your changes and then merges.






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