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. Code generation in a lib






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






3. Initialized heap memory.






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






5. Functionality Tests.






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






7. Inheritance between object.






8. Link multiple projects together






9. Are what function classes should include.






10. 2 Eyes + 2 Minds = AWESOME!






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






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






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






14. Uploads changes to your current branch.






15. Whats displayed to the screen






16. Undo changes made since your last commit.






17. No more than 40 hours to stop burnouts.






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






19. When GIT cannot merge your data.






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






21. Views all previous changes.






22. When doing a - precise task.






23. A function that can load a library






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






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






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






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






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






29. Breaks encapsulation boundaries.






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






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






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






33. Create a test and then create a function.






34. Ignores files when pushing.






35. Set of all pending changes.






36. Makes a copy of your repository.






37. Connection between a local brand and a remote branch.






38. Plan out your code.






39. What is part of the current scope.






40. Helps to eliminate unnecessary "include chaining."






41. Current view/ previous line.






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






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






44. Removes files from the repository.






45. Downloads your changes and then merges.






46. Stops when memory changes.






47. CONSTANT






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






49. Try to find the flaws in your code.






50. When a conflict is fixed.







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