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. Allows consumers to try a system earlier and give early feedback.






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






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






4. Current line that is executing.






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






6. NULL memory.






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






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






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






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






11. Create a test and then create a function.






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






13. Puts all headers into a master header.






14. Are what function classes should include.






15. Try to find the flaws in your code.






16. Removes files from the repository.






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






18. When a class is defined within another class.






19. Plan out your code.






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






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






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






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






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






25. One of the linking methods (pragma comment)






26. Put this before a function name in a dll - and the function name will avoid name mangling






27. Makes a copy of your repository.






28. Initialized stack memory.






29. Downloads your changes and then merges.






30. Initialized heap memory.






31. Quick program.






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






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






34. Code whatever it is you need to code.






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






36. Simply a value.






37. When a conflict is fixed.






38. Whats displayed to the screen






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






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






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






42. A measure of logical dependency.






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






44. When doing a - precise task.






45. Use only through the interface of the object.






46. Valid input that the program is designed to process.






47. When GIT cannot merge your data.






48. The default nickname for the remote repository.






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






50. No more than 40 hours to stop burnouts.