Vous êtes sur la page 1sur 16

IMPLEMENTATING IT SOLUTIONS

Implementation
Systems implementation is made of many
activities. These activities are the ff.

Coding
Testing
Installation
Documentation
Training
Support

The purpose of these steps is to convert the


physical system specification into working and
reliable software.

Deliverables for Coding, Testing and


Installation
Coding
Code
Program documentation

Testing
Test scenarios (test plan) and test data
Results of program and system testing

Installation
User guides
User Training plan
Installation and conversion plan
Software and hardware installation schedule
Data conversion plan
Site and facility remodeling plan

Deliverables for Documenting the


System, Training, and Supporting Users
Documentation
System Documentation
User Documentation

User Training Plan


Classes
Tutorials

User Training modules


Training materials
Computer-based training
aids

User support plan


Help desk
Online help
Bulletin boards and
other support
mechanism

Table of Contents of a Master Test Plan


Introduction
Description of system to
be tested
Objectives of the test
plan
Method of testing
Supporting Documents

Overall Plan
Milestones, schedules
and locations

Test materials

Test plans
Test cases
Test scenarios
Test log

Criteria for passing test

Testing Requirements
Hardware
Software
Personnel

Table of Contents of a Master Test Plan


Procedure

Test initiation
Test execution
Test failure
Access/Change control
Document

Test-specific or
Component-Specific
Test plans
Objectives

Software Description
Method
Milestones, schedules,
progression and
locations
Requirements
Criteria for passing tests
Resulting test materials
Execution control
Attachments

Categorization of Test Types


Manual

Automated

Static

Inspections

Syntax checking

Dynamic

Walkthroughs

Unit test

Desk checking

Integration test
System test

Seven Different Types of Test


1. Inspections a testing technique in which
participants examine program code for predictable
language-specific errors.
2. Walkthrough structured walkthrough can be used
to review many systems deliverables, including logical
and physical design specification as well as the code.
3. Desk Checking a testing technique in which the
program code is sequentially executed manually by
the reviewer.
4. Unit Testing Each module is tested alone in an
attempt to discover any errors in code.
5. Integration Testing the process of bringing together
all the modules that a program compromises for
testing purposes. Programs are typically integrated in
a top-down incremental fashion

Seven Different Types of Tests


6. Systems Testing The bringing together of all
the programs that a system compromises for
testing purposes. Programs are typically
integrated in a top-down, incremental fashion.
7. Sub Testing - A technique used in testing
modules, especially where modules are written
and tested in a top-down fashion, where a few
lines of code are used to substitutes for
subordinate modules.

Acceptance Testing by Users


Acceptance Testing The process whereby
actual users test a completed information
system, the end result of which is the users
acceptance of it.
Alpha Testing User testing of a completed
information system using simulated data
Beta Testing User testing of a completed
information system using real data in the real user
environment

Types of Test Performed during Alpha


Testing
Recovery Testing forces the software or
environment to fail in order to verify that
recovery is properly performed
Security testing verifies that protection
mechanisms built into the system will protect it
from improper penetration.
Stress Testing tries to break the system
Performance Testing determines how the
system performs in a range of possible
environments in which it may be used.

Installation

Installation The organizational process of changing over


from the current information system into a new one.ct
Direct Installation Changing over neold information
system to a new one by turning off old system to a new one
when the old one is turned off.
Parallel Installation Running the old information system
and the new one at the same time until management
decides the old system can be turned off.
Single-location installation Trying out a new information
system at one site and using the experience to decide if
and how the new system should be deployed throughout
the organization.
Phased Installation Changing from the old information
system to the new one incrementally, starting with one or a
few functional components and then gradually extending
the installation to cover the whole new system.

Documentation
System Documentation Detailed information about a
systems design specifications , its internal workings, and
functionality
User Documentation Written or other visual information
about an application system, how it works and how to use
it.
Internal Documentation System documentation that is
part of the program source code or is generated at compile
time.
External Documentation System documentation that
includes the outcome of structured diagramming
techniques such as data-flow annd entity realtionship
diagram

Seven Common Methods for


Computer Training
1.
2.
3.
4.

Tutorial one person taught at a time


Course - several people taught at a time
Computer aided instruction
Interactive training manuals combination of
tutorials and computer aided instructions
5. Resident expert
6. Software help components
7. External sources, such as vendors

Assignment
Research on Obama Care Implementation and
Jolibee SAP implementation.
List down the factors affecting the
unsuccessful implementation of the two
system.