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. Stops when memory changes.






2. Code generation in a lib






3. Ignores files when pushing.






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






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






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






7. A function that can load a library






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






9. Variable doesn't exist.






10. Adds files to the repository.






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






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






13. Quick program.






14. Create a test and then create a function.






15. Formatted code standards.






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






17. When doing a - precise task.






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






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






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






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






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






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






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






25. A measure of logical dependency.






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






27. Puts all headers into a master header.






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






29. Application






30. Set of all pending changes.






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






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






33. Makes a copy of your repository.






34. Simply a value.






35. Freed heap memory.






36. Classes build off of each other.






37. Code whatever it is you need to code.






38. Functionality Tests.






39. Initialized heap memory.






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






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






42. Function doesn't exist.






43. Downloads without merging.






44. Inheritance between object.






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






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






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






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






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






50. Uploads changes to your current 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