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. Valid input that the program is designed to process.






2. Quick program.






3. Current line that is executing.






4. Takes information in the index and pushes it onto the stack.






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






6. Fix any problems and then repeat the process.






7. Use only through the interface of the object.






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






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






10. STOP!!






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






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






13. Italicized in UML.






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






15. Code whatever it is you need to code.






16. Simply a value.






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






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






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






20. Inheritance between object.






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






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






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






24. Input






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






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






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






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






29. Functionality Tests.






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






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






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






33. Downloads your changes and then merges.






34. When doing a - precise task.






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






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






37. When a class is defined within another class.






38. Ability to treat a class object as a function by overloading the () operator.






39. Views all previous changes.






40. When GIT cannot merge your data.






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






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






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






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






45. Removes files from the repository.






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






47. Undo changes made since your last commit.






48. Stops when memory changes.






49. Set of all pending changes.






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