Scribd
Upload
29 views

System Implementation

The document outlines the key activities involved in implementing a new information system, including coding, testing, installation, documentation, training, and support. It discusses testing strategies like unit testing, integration testing, and acceptance testing. Documentation is created for both internal system users and external end users. Training and support activities help users adapt to the new system and help address any issues. The implementation process aims to convert system specifications into a working, reliable software system that is properly documented and users are prepared to adopt.

Uploaded by

Tista Bhaduri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
29 views

System Implementation

The document outlines the key activities involved in implementing a new information system, including coding, testing, installation, documentation, training, and support. It discusses testing strategies like unit testing, integration testing, and acceptance testing. Documentation is created for both internal system users and external end users. Training and support activities help users adapt to the new system and help address any issues. The implementation process aims to convert system specifications into a working, reliable software system that is properly documented and users are prepared to adopt.

Uploaded by

Tista Bhaduri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

 SYSTEM IMPLEMENTATION: 6 Major activities

1. Coding
2. Testing
3. Installation
4. Documentation
5. Training
6. 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.

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


2. Testing:Tests are performed using various strategies.Testing performed in parallel with
coding.
3. 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.

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.
 Test plans provide improved communication among all parties involved in testing.
Seven Different Types of Tests

1.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.
2. Inspection:
a testing technique in which participants examine program code for predictable language-specific
errors.
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 its code.
5. 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.
6. 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.
7. Stub 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 substitute for subordinate modules.

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.
Test cases represent either:
Typical system use.
Critical system use.
Abnormal system use.
Test cases and results should be thoroughly documented so they can be repeated for each revision of
an application.

Combining Coding and Testing


1. Test cases are usually developed by analysts.
2. Test cases should not be created by the programmers.
3. Separate people should program and test in order to ensure objectivity.
4. Programmers use symbolic debuggers to isolate causes for errors.

Acceptance testing BY USERS: 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 ALPHA TESTING


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

INSTALLATION
Installation: the organizational process of changing over from the current information system to a
new one.
Four installation strategies:
1.Direct Installation.
2.Parallel Installation.
3.Single-location installation.
4.Phased Installation.

Direct installation:
changing over from the old system to a new one by turning off the old system when the new system is
turned on.

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 an information system at one site and using the experience to decide if and how the new
system should be deployed throughout the organization.
Also known as location or pilot installation.

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.

PLANNING INSTALLATION: Considerations


 Data conversion.
1.Error correction.
2.Loading from current system.
 Planned system shutdown.
 Business cycle of organization.

DOCUMENTING THE SYSTEM


 System documentation: detailed information about a system’s design specifications, its internal
workings, and its 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 and E-R diagrams.

Preparing User Documentation


1.Traditional source has been information systems department.
2.Application-oriented documentation is now often supplied by vendors and users themselves.
Training and Supporting Users
1.Support: providing ongoing educational and problem-solving assistance to information system
users.
2.For in-house developed systems, support materials and jobs will have to be prepared or designed as
part of the implementation process.
3.Computing infrastructure: all of the resources and practices required to help people and adequately
use computer systems to do their primary work.

Training Information Systems Users


Potential training topics
1. Use of the system.
2. General computer concepts.
3. Information system concepts.
4. Organizational concepts.
5. System management.
6. System installation.
Electronic performance support system (EPSS):
component of a software package or an application in which training and educational information is
embedded.
An EPSS can take several forms, including a tutorial, an expert system shell, and hypertext jumps to
reference materials.

Supporting Information Systems Users


1. Support is extremely important to users.
2. Providing support can be expensive and time-consuming.

Automating Support
One approach is through automation
1. Internet-based online support forums.
2. On-demand fax.
3. Voice response systems.
4. Knowledge bases.

*Help desk:
a single point of contact for all user inquiries and problems about a particular information system or
for all users in a particular department.
Requires:
Technical skills: extensive knowledge about how to use the system and typical problems that can be
encountered.
People skills: good listening and communication, dealing with complaints and frustrations.

Support Issues for the Analyst to Consider


 User questions and problems.
 Recovery and backup.
 Disaster recovery.
 PC maintenance.
 Writing newsletters.
 Setting up user groups.

Organizational Issues in Systems Implementation


1.Biggest measure of success: Will it be used?
2.Major factors influencing likelihood of use:
 Personal stake of users
 System characteristics
 User demographics
 Organizational support
 Performance
 Satisfaction

Security Issues
1. Increasing important issue for organizations and their management.
2. Malicious software (malware): includes Trojan horses, worms, viruses, and other kinds.
3. External sources of threats include laptop theft, system penetration, and denial of service.

Electronic Commerce Application: System Implementation for Pine Valley Furniture’s WebStore
Developing test cases for the WebStore include testing categories as follows:
1) Simple functionality.
2) Multiple functionality.
3) Function chains.
4) Elective functions.
5) Emergency/crisis

Developing Test Cases for WebStore


Test case forms had the following sections:
1. Test Case ID
2. Category/Objective of Test
3. Description
4. System Version
5. Completion Date
6. Participants
7. Machine Characteristics (processor, operating system, memory, browser, etc.)
8. Test Result
9. Comments

Bug Tracking and System Evolution


Bug-tracking form has the following categories:
1) Bug Number (simple incremental number)
2) Test Case ID that Generate the Bug
3) Is the Bug Replicable?
4) Effects
5) Description
6) Resolution
7) Resolution Date
8) Comments
As batches of bugs are fixed, the version number of the software is incremented (i.e. 1.0, 2.0, 3.0,
etc.).

Alpha and Beta Testing the WebStore


Alpha Testing:
1.PVF employees who actively participated received in received a t-shirt, $100 to shop.
2.Development team conducted extensive recovery, security, stress, and performance testing.
Beta Testing:
PVF recruited several of their established customers to help in beta testing.
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.
 Notify all affected parties that the development project is ending and that you are switching to
operation and maintenance mode.
 Conduct post project reviews.
 Close out customer contract:Formal signoff.

*COTS
Software which is not pirated. A legal tender purchased from the store.
Commercial, off-the-shelf (COTS) or simply off the shelf (OTS) technology is ready-made and available
for sale, lease, or license to the general public. The term often refers to computer software or
hardware systems and may also include free software with commercial support.

You might also like