¶ … coding, testing, and installation? The deliverables from coding are that the "physical design specifications" of a particular system have been converted to code; the deliverables from testing include passing various industry-validated, accepted tests and finally for installation the ultimate deliverable is when "the current system is replaced with the new system" successfully (Gadish 7).

Explain the testing process for code.

The testing specifications are established during the design and analysis phase. The "master plan" of testing is constructed and the actual testing itself is conducted during the implementation phase (Gadish 9). Testing can be either static (the code is not actually executed) or dynamic (the code is executed). Some testing is automated and performed by the computer while other tests are manual and are performed by the system designers in a hands-on fashion (Gadish 10). In these manual tests, users may inspect code for likely, predictable errors (static testing) or...

Testing may be conducted as units, and then tested in an integrated form, followed by overall, holistic systems testing (Gadish 12-13).
Q3. What is the difference between system documentation and user documentation?

There is a fundamental difference between system and user documentation. Usually, the users of a particular system are not technical personnel, but rather are laypersons. User documentation is designed to enable them to effectively use the system. Systems documentation informs IT personnel how the system works and enables them to fix it or to make changes.

User documentation is included for every software system, in the workplace as well as systems sold for private home use. This may include the hardware needed to run the system; installation instructions; general use instructions; screenshots to guide the user in everyday processes; lists of common errors and troubleshooting, and…