Is the process whereby the physical design specifications created by the analysis team are turned into working computer code by the programming team?

CHAPTER 13

System Implementation

●Major activities: coding, testing, installation, documentation, training, support

●Purpose:

○To convert final physical system specifications into working and reliable software

○To document work that has been done

○To provide help for current and future users

The Process of Coding, Testing, and Installation

●Coding: Physical design specifications are turned into working computer code.

●Testing: Tests are performed using various strategies. Testing is performed in parallel with coding.

●Installation: The current system is replaced by a new system.

Documenting the System, Training Users, and Supporting Users

●Two audiences for final documentation:

○Information systems personnel who will maintain the system throughout its productive life

○People who will use the system as part of their daily lives

●User Training

○Application-specific

○General for operating system and off-the-shelf software

Software Application Testing

●A master test plan is developed during the analysis phase.

●During the design phase, unit, system and integration test plans are developed.

●The actual testing is done during implementation.

●Written test plans provide improved communication among all parties involved in testing.

Seven Different Types of Tests

●Static or dynamic techniques

○Static testing means that the code being tested is not executed.

○Dynamic testing involves execution of the code.

●Test is automated or manual

○Automated means computer conducts the test.

○Manual means that people complete the test.

●Inspection

○a testing technique in which participants examine program code for predictable language-specific errors

●Walkthrough

○a peer group review of any product created during the systems development process, including code

●Desk checking

○a testing technique in which the program code is sequentially executed manually by the reviewer

●Unit testing:

○each module is tested alone in an attempt to discover any errors in its code

●Integration testing:

○ the process of bringing together all of the modules that a program comprises for testing purposes

○Modules are typically integrated in a top-down incremental fashion.

●System testing:

○the bringing together of all of the programs that a system comprises for testing purposes

○Programs are typically integrated in a top-down, incremental fashion.

The Testing Process

●The purpose of testing is to confirm that the system satisfies the requirements.

●Testing must be planned.

●Test case is a specific scenario of transactions, queries or navigation paths.

What is the type of testing in which the program code is sequentially executed manually by the reviewer?

Which type of plan provides information about when and where the new system will be installed?

Is the user testing of a completed information system using simulated data?