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. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






2. What is part of the current scope.






3. Try to find the flaws in your code.






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






5. Code whatever it is you need to code.






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






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






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






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






10. Application






11. Undo changes made since your last commit.






12. Current view/ previous line.






13. When GIT cannot merge your data.






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






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






16. One of the linking methods (pragma comment)






17. Puts all headers into a master header.






18. No more than 40 hours to stop burnouts.






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






20. A function that can load a library






21. Formatted code standards.






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






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






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






25. Variable doesn't exist.






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






27. Will execute all code paths and boundary conditions.






28. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere






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






30. Breaks encapsulation boundaries.






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






32. Whats displayed to the screen






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






34. Concept based on limiting the scope of modules to provide better structures.






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






36. Adds files to the repository.






37. Link multiple projects together






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






39. Removes files from the repository.






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






41. NULL memory.






42. Treating a derived class's data members like it's base class's.






43. Functionality Tests.






44. Function doesn't exist.






45. Create a test and then create a function.






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






47. STOP!!






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






49. Helps to eliminate unnecessary "include chaining."






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