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. Static in C++. Can span all instances of a class.






2. Ignores files when pushing.






3. Having power over inheritance with the flexibility of composition.






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






5. Puts all headers into a master header.






6. Functionality Tests.






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






8. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






9. A function that can load a library






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






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






12. STOP!!






13. Italicized in UML.






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






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






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






17. Application






18. Initialized stack memory.






19. Undo changes made since your last commit.






20. When a class is defined within another class.






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






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






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






24. Makes a copy of your repository.






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






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






27. Helps to eliminate unnecessary "include chaining."






28. Code generation in a lib






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






30. Are what function classes should include.






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






32. Initialized heap memory.






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






34. Create a test and then create a function.






35. When doing a - precise task.






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






37. Fix any problems and then repeat the process.






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






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






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






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






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






43. Removes files from the repository.






44. 2 Eyes + 2 Minds = AWESOME!






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






46. No more than 40 hours to stop burnouts.






47. Classes build off of each other.






48. What is part of the current scope.






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






50. Use only through the interface of the object.







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests