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. Whats displayed to the screen






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






4. Fix any problems and then repeat the process.






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






6. When a conflict is fixed.






7. The linking is already done internally






8. A pointer or reference. One object needs to know about the other object to work.






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






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






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






12. Application






13. Plan out your code.






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






15. Puts all headers into a master header.






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






17. Try to find the flaws in your code.






18. When a class is defined within another class.






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






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






21. Trying to access a location in memory that your computer cannot access.






22. Will execute all code paths and boundary conditions.






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






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






25. Initialized heap memory.






26. No more than 40 hours to stop burnouts.






27. Freed heap memory.






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






29. Set of all pending changes.






30. Breaks encapsulation boundaries.






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






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






33. Ignores files when pushing.






34. Initialized stack memory.






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






36. Adds files to the repository.






37. Views all previous changes.






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






39. Italicized in UML.






40. STOP!!






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






42. When GIT cannot merge your data.






43. Function doesn't exist.






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






45. Downloads your changes and then merges.






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






47. Downloads without merging.






48. You have to tell it to link






49. Code generation in a lib






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