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. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






3. Ignores files when pushing.






4. 2 Eyes + 2 Minds = AWESOME!






5. Functionality Tests.






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






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






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






9. Concept based on limiting the scope of modules to provide better structures.






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






11. Do not optimize until the very end.






12. Code whatever it is you need to code.






13. Input






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






15. Function doesn't exist.






16. Variable doesn't exist.






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






18. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






19. Application






20. Written by the customers as things that the system needs to do for them.






21. Stops when memory changes.






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






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






24. Are what function classes should include.






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






26. A measure of logical dependency.






27. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






28. Removes files from the repository.






29. When GIT cannot merge your data.






30. STOP!!






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






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






33. Use only through the interface of the object.






34. Quick program.






35. Code generation in a lib






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






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






38. Undo changes made since your last commit.






39. When a concrete class inherits from a pure interface.






40. The linking is already done internally






41. Italicized in UML.






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






43. Create a test and then create a function.






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






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






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






47. CONSTANT






48. Breaks encapsulation boundaries.






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






50. Ability to treat a class object as a function by overloading the () operator.







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