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. Default branch within your repository.






2. A type of library that is used by the code






3. Set of all pending changes.






4. When doing a - precise task.






5. Downloads your changes and then merges.






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






7. Input






8. Adds files to the repository.






9. Initialized stack memory.






10. Variable doesn't exist.






11. STOP!!






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






13. A measure of logical dependency.






14. Code whatever it is you need to code.






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






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






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






18. Will execute all code paths and boundary conditions.






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






20. A function that can load a library






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






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






23. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






24. Uploads changes to your current branch.






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






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






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






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






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






30. How many objects that a source object can legitimately reference.






31. NULL memory.






32. Makes a copy of your repository.






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






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






35. Function doesn't exist.






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






37. Create a test and then create a function.






38. When GIT cannot merge your data.






39. Breaks encapsulation boundaries.






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






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






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






43. Initialized heap memory.






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






45. Removes files from the repository.






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






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






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






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






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