System Implementa' Department of Computer ce & Engineering Hamdard University Bangladesh System Implementation = Six major activities: Coding Testing Installation Documentation Training SupportPurpose of System Implementation 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.System Development Life Cycle The Process of Coding, Te ting, and Installation = Coding Physical design specifications are tured into working computer code. = Testing Tests are performed using various strategies. = Installation ‘The current system is replaced by new systemThe Process of 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.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 conduets the test. Manual means that people complete the tes. © Inspection participants examine pr 1m code for predictable language-specific ™ Desk checking am code is sequentially executed by the reviewer Different types of tests (cont.) ® Unit testing Each module is tested alone in an attempt to discover any errors in its code. © Integration testing Individual software modules are combined and tested as a group. System testing Designed to uncover weaknesses that were not found in earlier tests. Stub testing Performed on individual events or modules of a program,The Testing Process ™ The purpose of testing is to confirm that the system satisfi the requirements. © Testing must be planned. Test case is a specific scenario of transactions, queries or navigation paths. Combining Coding and Testing Test c ™ Test ci es are usually developed by analysts. es should not be created by the programmers. ® Separate people should program and test in order to ensure objectivity © Programmers use symbolic debuggers to isolate causes for errors.Acceptance Testing by Users = Systems acceptance test is a final system test performed by end-users using real data over an extended time period. fication testing + Validation testing + Audit testing Three levels for acceptance test : ‘Verification testing runs the system in a simulated environment using, simulated data Validation testing runs the system in a live environment using real data. ‘Audit testing certifies that the system is free of errors and is ready to be placed into operation.Installation © Process of moving from old system to new system © Conversion of data must be planned Four installation strategies: Direct Installation, Parallel Installation, Single-location installation, Phased Installation. Direct Installation —— Current System Install New System New System =——BTimeParallel Installation — > _ Current System Install New System New System 9——TimePhased Installation Curent Sytem | cue Stem Without Module 1 q] instal in M Module 2 New Module 1 —> m Without Modules 1 82 | New Module 2 —p> Documenting the System © System documentation system’s design specifications, its internal workings, and its functionality © User documentation written or other visual information Internal documentation: program source code or is generated at compile time. © External documentation structured diagramming t diagrams, hniques such as data flow and E-RSupporting the End-user Information Center / Help desk Automating support Resident expert Other things to consider: Providing re ery and backup Disaster recovery PC maintenanc Training Information Systems Users Potential training topies Use of the system. General computer concepts, Information system concepts. Organizational concepts. System management System installation.Developing Test Cases for WebStore Test Case ID ry/Objective of Test iption System Version Completion Date Participants Machine Characteristics Test Result Comments Bug Tracking and System Evolution Bug Number (simple incremental n Test Case ID that Generate the B Is the Bug Replicable? Effects Description Resolution Resolution Date CommentsWebStore Installation = WebStore was ready to go online and development team recommended to top management it was time to “flip the switch’. Project Close-Down Evaluate team Reassign members to other projects. .cted parties that the development project is ending. ® Conduct post project reviews. ™ Close out customer contract. Formal signoff