1. Unit 17 System Implementation
Six major activities are done during system implementation
1-coding 2-testing 3-installation 4-training
5-documentation 6- support
The purpose of these activities:
A-to convert the physical specification into working and reliable software and hardware.
B-to document the work that has been done

2. C- to provide help for current and future users and caretakers of the system.
The following an explanation of these activities.
1- Coding : is the process of turning the physical design into working computer code by the programming team.
2-Testing: is the process of making sure that

3. programs do what they are designed to do.
Testing can go in parallel with coding, it should be done for each individual program, then as part of the system.
3- Installation: is the process during which the current system is replaced by the new system, converting the existing data, software, documentation, and work procedures to the new system.

4. Two important outcomes of coding, testing, and installation are the programs (code) and documentation which be done in detail and as clear as possible to be used for future development.
The installation outcomes are:
1- user guide : provide information on how to use the new system.
2-Training plan for users so they can quickly

5. learn how to operate the new system.
4-Documentation: writing on paper every thing concerning the new system, starting from the main goals of the system, the logical and physical designs, methods of collecting information, forms and reports of the existing system, and all important information you have learned about the system. It can be paper-based or online.

6. Documentation audiences:
1- the information system personnel who will maintain the system throughout its productive life.
2-the people who will use the system as part of their daily lives.
5- Training and support: train users how to use the new system, make special training for those who have no or little computer knowledge. Decide who should be trained

7. How much training is needed
How much training is needed? What do different types of users need to learn during training?

8. Types of Tests
Testing may be static or dynamic, it could be manual or automated.
Static testing means that the code being tested is not executed.
Dynamic testing involves execution of the code.
Automated testing means that the computer does the testing.
Manual testing is what is done by people.

9. Seven different tests
1-Inspection: a testing technique in which participants manually examine program code for well-known errors, syntax, grammar. Walkthrough the code to discover errors, review the code to find errors and inform programmers to correct them. (refer to page 577 for guideline for conduction a code walkthrough)
2-Desk checking: a testing technique in which the program code is sequentially executed manually by the reviewers using paper and pencil.

10. Testing (cont)
3-syntax checking: testing that is usually done by computers which checks the structure of instructions, and the punctuation that the programming language requires.
4- Unit testing: each program or module is tested alone in order to discover any errors in its code.

11. 5- Integration testing: the process of testing a group of modules together. A bottom up approach could be used
6- System testing: bringing all programs that make up the entire system and test it all at once. A up-down approach could be used.
7- stub testing: a testing technique for modules where few line are written in a module then the module is called.

12. The data used during testing is not real, it is artificial data NONLIVE data

13. Testing Process
There are two thing to remember about testing information system:
1- the purpose of testing is confirming that the system satisfies requirements.
2- Testing must be planned.
Many different aspects of a system must be cared for, such as:
1- response time 2- response to boundary data response to no input.

14. 4-response to heavy volumes of input.
Issues to remember during testing planning:
*You must test every thing that you input to the system as many times as you can.
*the people who create the test cases should NOT be the same people as those who coded and tested the system.
* You must know what the correct result must be in order to decide whether the system output is right or wrong.

15. You must test the system with wrong and out of range data and watch how the system behaves ( does it alerts the user or not).

16. eXtreme programming
The programmers who write the code also write the tests. The emphasis is on testing those things that can break or go wrong not everything. The philosophy behind extreme programming is that code will be integrated into the system and tested within hours after it has been written.
Pair programming: two programmers write coding and testing together, it does not mean that one person types and the other watches, it

17. Means the two programmers work together on the problem they are trying to solve, exchanging information and insights and sharing skills.
Advantages of pair programming:
1- better communication among developers.
2-higher levels of productivity.
3-higher quality code
4-reinforcement of other practices of extreme programming such as code and test efforts.

18. Acceptance Testing
Testing the system in the environment where it will be used, users accept the work of the new system and they are satisfied with it.
Alpha testing: user testing of a complete information system using simulated data.
During alpha testing the entire system is implemented to discover whether or not the system is overtly destructive to it self or to the rest of environment.

19. Alpha tests types 1-recovery 2-security 3-stress 4- performance
Beta testing: user testing of a completed information system using real data in the real user environment. It is to determine whether the software, documentation, technical support, and training activities work properly or not. It is a try and fix process until the system is accepted.

20. Installation
Transferring the new system to the working and real area, changing from the old (current system) to the new one.
Methods :
1- Direct 2-Parallel 3-Single location
4-phased (refer to text book for details)

21. Planning installation
Several issues to consider when converting the old to the new system:
1-all old data must be loaded and converted to the proper format of the new system.
2-plan for emergency staff to be available in case of system failure so business operation stay operational.
3- choose the correct time for installation

22. Avoid holiday times, fiscal year time, you should understand the cyclical nature of the business you are working with.
Installation is an organizational change process.

23. Documenting the system
Types
1-system documentation which is a detailed information about a system’s design specification, its internal workings, and its functionality. It divided into two parts:
A-internal documentation which writing remarks regarding the program source codes, table of abbreviations for field names that are used in the program.

24. B-external documentation includes the outcome of structured diagramming techniques such as data flow and entity- relationship diagrams, system flowcharts, and program flowcharts.

25. 2- user documentation which is a written or visual information about an application system, how it works, and to use it.
It is a reference guide to the users, (user guide ) which includes:
A-minimal hardware requirements for the new system.
B-a detailed explanation of how to use the system and handle compilation errors.

26. C- it uses screens displayed by the system to show users how to use the new system.

27. Training and supporting users
Support: providing ongoing educational and problem-solving assistance to information system users. For in-house developed systems, support materials and jobs will have to be prepared or designed as part of the implementation process.
Computing infrastructure : all the resources and practices required to help

28. People properly use computer systems to do their work.
Training information system users
Computer user requires skills, training vary by the type of system and the knowledge of users (expertise).
Training methods:
1- tutorial- one person taught at a time, a written user guide is given to each user

29. Read and learn how to use the system.
2-courses : training sessions for a period of time, a group of users are taught at the same time.
3-computer aided instruction like on-line help or menu hints
4-interactive training manuals.
5-resident expert: an on-line expert ready to

30. answer users questions and help solve the difficulties they face
answer users questions and help solve the difficulties they face. (information center explained below)
6- software help components.
7-external sources, such as venders.
8-electronic performance support system: components of software packages or application in which training and educational information is included. It can include tutorials, expert system, and hypertext jumps to reference material,

31. Information center duties
Install new hardware or software
Consult with users writing programs
Extract data from organizational database onto personal computers.
Answer basic on-demand questions.
Provide a demonstration of viewing hardware and software.
Work with users to submit system change requests.

32. Automating support Methods
1-on-line support forums allows users to access information on new releases of bugs, and tips for more effective usage.
2-Bulletin board systems.
3-on-demand fax allows users to order support information.
4-voice-response system allows users to navigate option menus that lead to prerecorded messages about usage, problems, and workaround.

33. 5- help disk which is a single point of contact for all user inquiries and problems about a particular information system or for all users in a particular department.

34. Why implementation sometimes fails
Two conditions necessary for successful implementation:
1-management support of the system under development.
2- user involvement in the development process.
3-commitment to the project involves well understanding of the system and problems it is designed to solve.
4-commitment to change: be ready to change behaviors, procedures.

35. 5-extent of project definition and planning, more planning efforts more chances for success.
6- users expectations: the more realistic users are in their expectation the more chances for success, how are they satisfied.

36. Factors influencing system use
1-user’s personal stake: how important the system is to the user, how relevant is it to their work.
2-system characteristics : ease of design, reliability, and relevance to the task the system support.
3-user demographics: age, degree, and computer experince.

37. 4-organization support: the better the system support infrastructure, the more it will be used.
5-performance: the more users can easily do using the system, the more usage it gets. The higher levels of performance, the more use. The more use the greater the performance.
6-satisfaction: more satisfaction produce more usage and more usage produces more satisfaction.