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 you to switch your working copy to another branch.






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






3. You have to tell it to link






4. Function doesn't exist.






5. When a class is defined within another class.






6. Variable doesn't exist.






7. Breaks encapsulation boundaries.






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






9. Makes a copy of your repository.






10. Stops when memory changes.






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






12. Current line that is executing.






13. Current view/ previous line.






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






15. Try to find the flaws in your code.






16. Code generation in a lib






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






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






19. Do not optimize until the very end.






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






21. No more than 40 hours to stop burnouts.






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






23. Plan out your code.






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






25. Create a test and then create a function.






26. Undo changes made since your last commit.






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






28. Removes files from the repository.






29. Italicized in UML.






30. Puts all headers into a master header.






31. When doing a - precise task.






32. CONSTANT






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






34. Initialized heap memory.






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






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






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






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






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






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






41. Ability to accept different types of parameters to bind to different implementations at run-time.






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






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






44. Inheritance between object.






45. 2 Eyes + 2 Minds = AWESOME!






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






47. The default nickname for the remote repository.






48. When a conflict is fixed.






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






50. Bookmark of a revised set with a title. For easy checkouts.







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests