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. Ask questions and obtain the details and requirements given.






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






3. Removes files from the repository.






4. What is part of the current scope.






5. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






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






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






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






9. No more than 40 hours to stop burnouts.






10. Current line that is executing.






11. When doing a - precise task.






12. CONSTANT






13. Default branch within your repository.






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






15. Do not optimize until the very end.






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






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






18. Link multiple projects together






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






20. Whats displayed to the screen






21. Formatted code standards.






22. Will execute all code paths and boundary conditions.






23. Set of all pending changes.






24. Uploads changes to your current branch.






25. The default nickname for the remote repository.






26. Application






27. One of the linking methods (pragma comment)






28. Input






29. You have to tell it to link






30. Makes a copy of your repository.






31. Code whatever it is you need to code.






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






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






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






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






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






37. Initialized stack memory.






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






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






40. Functionality Tests.






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






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






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






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






45. When a class is defined within another class.






46. Variable doesn't exist.






47. Undo changes made since your last commit.






48. Creates a copy of your current branch into a remote branch.






49. Breaks encapsulation boundaries.






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







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