Answer:
I would say the second one
Explanation:
it makes sense cause if you're able to fix the problem that's how. if not then the last one
Answer:
A) True
Explanation:
Objects are known as reference types, meaning that they are always accessed by references, not copied. When a method is called, passing an object to it, Java passes a reference of that object to the method and when that reference is modified, the changes can be seen in the object itself. Therefore a mutable object can be mutated anywhere- either from where it is created or by a method it is passed to. Hence the need to always use privacy modifier keywords such as public, private or protected, to determine the exposure of class properties and methods.
Answer:
Software requirement and estimation.
Explanation:
In this step, the proposals are collected, and best from them is made, and then checked for feasibility, and the SRS document is formulated finally. Now the each developer, designers, writers are being assigned the task, then finally the development phase starts. However, since this is SDLC, you will not find any iteration, and the defects are checked only after testing which is the last phase. And a lot of errors remain even after delivery sometimes. Also, it is time consuming to edit the errors in this manner. Hence, agile methodology is preferred.
No as the higher level just has more abstraction than lower levels. Meaning it's easier to type more complex instructions than in machine code etc, not just more instructions