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. Takes information in the index and pushes it onto the stack.






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






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






4. Linking to dynamic libraries is usually handled by linking to an ____________.






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






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






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






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






9. Use only through the interface of the object.






10. A measure of logical dependency.






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






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






13. Code whatever it is you need to code.






14. Fix any problems and then repeat the process.






15. Do not optimize until the very end.






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






17. Current view/ previous line.






18. Connection between a local brand and a remote branch.






19. Initialized stack memory.






20. Freed heap memory.






21. Ignores files when pushing.






22. Adds files to the repository.






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






24. Uploads changes to your current branch.






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






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






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






28. Quick program.






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






30. When doing a - precise task.






31. Whats displayed to the screen






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






33. Variable doesn't exist.






34. Current line that is executing.






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






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






37. Initialized heap memory.






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






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






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






41. What is part of the current scope.






42. Having power over inheritance with the flexibility of composition.






43. Ability to accept different types of parameters to bind to different implementations at run-time.






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






45. When GIT cannot merge your data.






46. A function that can load a library






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






48. CONSTANT






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






50. Will execute all code paths and boundary conditions.