Questions 16-30 and this time I will put them more out of order ;)
A higher level of modular granularity than a Class
The same level of modular granularity as a Statement
The same level of modular granularity as a Class
A lower level of modular granularity than a Class
Rate this question:
Hacking
Test-first development
Factoring
UML
Rate this question:
Reuse
To reduce the overall size of code
because it may turn into a larger operation latter
To improve readability
Rate this question:
Ignore them
Use assertions
Substitute valid values
Throw (raise) exceptions
Rate this question:
providing models that allow you to focus on implementation details
Providing models that allow you to ignore implementation details
The enabler that allows you to look at the details if you want to
The enforcer that prevents you from looking at the details even if you want to
Rate this question:
it reduces complexity
It improves performance
It avoids duplicated code
it improves readability
Rate this question:
Complicated
Pass-through
Accessor
All
Rate this question:
> 500
A screen length
Less than 200 lines
5 pages
Rate this question:
After checking the design (for example with a desk checks)
Before checking the design (for example with a desk checks)
After you have reviewed the code
As you design the routine
Rate this question:
Documenting and verifying preconditions and post conditions
Checking the values of all data from external sources
documenting assumptions made in the code
Checking the values of all routine input parameters
Rate this question:
Initialize each variable before it is declared
initialize each variable close to where it is first used
Initialize each variable at the beginning of the method
Not initialize at all
Rate this question:
Different people writing code in different ways; it really does not matter
Convenience as it speeds the writing of programs
intellectual manageability as it speeds the writing of programs
intellectual manageability as it simplifies the reading of programs
Rate this question:
the reference between variables are easily broken
Variable might end up contain wrong value as they are always changing
New code might be added, inadvertently altering the variable
Variables are difficult to change
Rate this question:
Exceptional cases should be avoided during development
Introduce debugging aids early
Exceptional cases should be handled in such a way that makes them obvious during development and recoverable when production code is running
Exceptional cases should be handled in such a way that makes them rare during development and avoided when production code is running
Rate this question:
Quiz Review Timeline (Updated): Mar 21, 2023 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.