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. Italicized in UML.






2. Set of all pending changes.






3. Ignores files when pushing.






4. Makes a copy of your repository.






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






6. CONSTANT






7. When a class is defined within another class.






8. Downloads without merging.






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






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






11. Breaks encapsulation boundaries.






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






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






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






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






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






17. Input






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






19. Removes files from the repository.






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






21. Are what function classes should include.






22. Application






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






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






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






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






27. One of the linking methods (pragma comment)






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






29. No more than 40 hours to stop burnouts.






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






31. Simply a value.






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






33. A collection of memory addresses for all virtual functions in an objects class hierarchy.






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






35. Adds files to the repository.






36. Use only through the interface of the object.






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






38. When doing a - precise task.






39. Downloads your changes and then merges.






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






41. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






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






43. Puts all headers into a master header.






44. When GIT cannot merge your data.






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






46. Undo changes made since your last commit.






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






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






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






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