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. Initialized heap memory.






2. Do not optimize until the very end.






3. Keeps a team using a similar naming convention for things.






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






5. Fix any problems and then repeat the process.






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






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






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






9. Whats displayed to the screen






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






11. When a class is defined within another class.






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






13. The linking is already done internally






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






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






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






17. Freed heap memory.






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






19. CONSTANT






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






21. No more than 40 hours to stop burnouts.






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






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






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






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






26. Helps to eliminate unnecessary "include chaining."






27. Are what function classes should include.






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






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






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






31. Classes build off of each other.






32. Makes a copy of your repository.






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






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






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






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






37. What is part of the current scope.






38. Initialized stack memory.






39. When doing a - precise task.






40. Simply a value.






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






42. Downloads your changes and then merges.






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






44. Ignores files when pushing.






45. Italicized in UML.






46. When GIT cannot merge your data.






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






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






49. Use this to find a memory address or signiture in a dll






50. STOP!!