25-03-2020 Assignment 13

Winter-2020 Semester
CIS 270 (Analysis and Design)
System Implementation
Assignment: 13

Submitted to:
Prof. Siddhartha Shyam Vyas

Submitted by:
Gurkirpal Singh (300167280)
BCIS, 2

Due Date of Submission:

25 March 2020.
Date of Submission:
25 March 2020.
Assignment 11

Table of contents

Certificate of originality……………………………………….……………………………………..i

Acknowledgement………………………………………………….……………...………………..ii

Introduction……………………………………….……………………………………………….....1

Summary………………………………………………………………………………………….......7

References
25-03-2020 Assignment 13

CERTIFICATE OF ORIGINALITY

I hereby declare that:

• I have used my own words

• I have not copied
• I have not plagiarized
• I have cited all the sources from where I have adapted / sourced.

Gurkirpal Singh (300167280)

(i)
25-03-2020 Assignment 13

ACKNOWLEDGEMENT

I want to express our profound gratefulness to our Prof. Siddhartha Shyam Vyas,
Ph.D. for giving me a good guideline for assignment throughout numerous
consultations. I am very grateful to my teacher who helped me a lot in class to
understand the basic information of analysis and design. He gave me many
necessary details about the chapter and he explained me the procedure to
accomplish the respective work. Therefore, I would like to thanks a lot to my
teacher.

Gurkirpal Singh (300167280)

(ii)
25-03-2020 Assignment 13

INTRODUCTION
Implementation is expensive because so many people are involved in the process; it is
time consuming because of all the work that has to be completed. In a traditional plan-
driven systems development project, physical design specifications must be turned into
working computer code, and the code must be tested until most of the errors have been
detected and corrected. Implementing a new information system into an organizational
context is not a mechanical process. The organizational context has been shaped and
reshaped by the people who work in the organization.

SYSTEM IMPLEMENTATION
System implementation is made up of many activities. The six major activities we are
concerned with in this chapter are coding, testing, installation, documentation, training,
and support.

Coding, testing, and Installation processes

Coding: the process whereby the physical design specifications created by the analysis
team are turned into working computer code by the programming team. Planning
involves determining what needs to be tested and collecting test data. Installation is the
process during which the current system is replaced by the new system. This includes
conversion of existing data, software, documentation, and work procedures to those
consistent with the new system.

Deliverables and outcomes from Coding, testing, and Installation

The Deliverables for Coding, Testing, and Installation:

1. Coding
a. Code
b. Program documentation
2. Testing
a. Test scenarios (test plan) and test data
b. Results of program and system testing

1|CIS 270
Assignment 11

3. Installation
a. User guides
b. User training plan
c. Installation and conversion plan
i. Software and hardware installation
schedule
ii. Data conversion plan
iii. Site and facility remodeling plan
The Deliverables for Documenting the System, Training, and Supporting Users:
1. Documentation
a. System documentation
b. User documentation
2. User Training Plan
a. Classes
b. Tutorials
3. User Training Modules
a. Training materials
b. Computer-based training aids
4. User Support Plan
a. Help desk
b. Online help
c. Bulletin boards and other support mechanisms
SOFTWARE APPLICATION TESTING
Seven different types of tests. Software application testing is an umbrella term that
covers several types of tests. It organizes the types of tests according to whether they
employ static or dynamic techniques and whether the test is automated or manual.
Static testing Dynamic testing Automated testing Manual testing
code being tested is involves execution of computer conducts people
not executed the code the test complete the
test

2|CIS 270
Assignment 11

A testing technique in which participants examine program code for predictable

language-specific errors.
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 the programs that a system comprises for
testing purposes. Programs are typically integrated in a top-down, incremental fashion.
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 two important things to remember about testing information systems:
1. The purpose of testing is to confirm that the system satisfies requirements.
2. Testing must be planned.
Testing harness: An automated testing environment used to review code for errors,
standards violations, and other design flaws.
Combining Coding and testing
Refactoring: Making a program simpler after adding a new feature.
Refactoring is nothing more than simplifying a system, typically after a new feature or
set of features has been added.

Acceptance testing by users

Acceptance testing: The process whereby actual users test a completed information
system, the 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.
The types of tests performed during alpha testing include the following:
• Recovery testing—forces the software to fail in order to verify
that recovery is properly performed.

3|CIS 270
Assignment 11

• 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 the range of
possible environments in which it may be used.

INSTALLATION
The organizational process of changing over from the current information system to a
new one.

Direct Installation
It is changing over from the old information system to a new one by turning off the old
system when the new one 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 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.
Planning Installation
Each installation strategy involves converting not only software, but also data and
(potentially) hardware, documentation, work methods, job descriptions, offices and other
facilities, training materials, business forms, and other aspects of the system.

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.

4|CIS 270
Assignment 11

TRAINING AND SUPPORTING USERS

Training and support are critical for the success of an information system.
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.
Training Information Systems Users
The Computer use requires skills, and training people to use computer applications can
be expensive for organizations. The list of potential topics from which you will determine
if training will be useful includes the following:
• Use of the system (e.g., how to enter a class registration request)
• General computer concepts (e.g., computer files and how to copy them)
• Information system concepts (e.g., batch processing)
• Organizational concepts (e.g., FIFO inventory accounting)
• System management (e.g., how to request changes to a system)
• System installation (e.g., how to reconcile current and new systems during
phased installation)
Supporting Information System Users
Automating Support: To cut the costs of providing support and to catch up with the
demand for additional support services, vendors have automated many of their support
offerings.
Providing Support through a Help Desk: Whether assisted by vendors or going it alone,
the center of support activities for a specific information system in many organizations is
the help desk.
Help Desk: A single point of contact for all user inquiries and problems about a
information system or for all users in a particular department.
Support Issues for the analyst to Consider
The Support is more than just answering user questions about how to use a system to
perform a particular task or about the system’s functionality.

ORGANIZATIONAL ISSUES IN SYSTEMS IMPLEMENTATION

Despite the best efforts of the systems development team to design and build a quality
system and to manage the change process in the organization, the implementation
effort sometimes fails.

5|CIS 270
Assignment 11

Why Implementation Sometimes fails?

The six factors that influence the extent to which a system is used:
1. User’s personal stake. How important the domain of the system is for the user; in
other words, how relevant the system is to the work the user performs.
2. System characteristics. Includes aspects of the system’s design such as ease of
use, reliability, and relevance to the task the system supports.
3. User demographics. Characteristics of the user, such as age and degree of
computer experience.
4. Organizational support. The better the system support, the more likely an
individual will be to use the system.
5. Performance. What individuals can do with a system to support their work will
have an impact on extent of system use.
6. Satisfaction. Use and satisfaction also represent a two-way relationship. The
more satisfied the users are with the system, the more they will use it.
Security Issues
The security of information systems has become an increasingly important issue for
organizations and their management. A firewall is often installed in a specially
designated computer separate from the rest of the network so that no incoming request
can get directly at private network resources.

ELECTRONIC COMMERCE APPLICATIONS

The system implementation and operation of an Internet-based electronic commerce
application is no different than the processes followed for other types of applications.
The programmers have extensively tested each unique module, and it is now time to
perform a systemwide test of the Web Store.

PROJECT CLOSEDOWN
The first task involves from dealing with project personnel to planning a celebration of
the project’s ending.
The second task is to conduct post-project reviews with both your management and
your customers.
The third major task in project closedown is closing out the customer contract.

SUMMARY
The different types of testing: (1) code inspections, in which the code is examined for
wellknown errors; (2) walkthroughs, when a group manually examines what the code is
supposed to do; (3) desk checking, when an individual mentally executes the computer
instructions; (4) syntax checking, typically done by a compiler; (5) unit or module testing;
(6) integration testing, in which modules are combined and tested together until the
entire program has been tested as a whole; and (7) system testing, in which programs
are

6|CIS 270
Assignment 11

combined to be tested as a system and where the system’s meeting of its objectives is
examined. The four types of installation: (1) direct, when the old system is shut off just
as the new one is turned on; (2) parallel, when both old and new systems are run
together until it is clear the new system is ready to be used exclusively; (3) single-
location, when one site is selected to test the new system; and (4) phased, when the
system is installed bit by bit. The two types of documentation: (1) system
documentation, which describes in detail the design of a system and its specifications;
and (2) user documentation, which describes a system and how to use it for the
system’s users. Computer training has typically been provided in classes and tutorials.
A help desk provides aid to users in a department or for a particular system. The first
step in a successful implementation effort may be realizing just that fact. In many ways,
the implementation of an Internet-based system is no different. Just as much careful
attention, if not more, must be paid to the details of an Internet implementation as to a
traditional system. Successful implementation for an Internet-based system is not an
accident either. (The systems development environment, 2014)

7|CIS 270
Assignment 11

REFERENCES

❖ A, G. (2011). Systems Analysis and Design Paperback – 2011. PHI.

❖ Arjun. (2015). User interfaces. Retrieved from bbc.co.uk: https://bbc.in/2Ug06FZ Access Date:
17-03-2020

❖ Award, E. M. (18 Mar 1993). Systems Analysis and Design. GALGOTILAS.

❖ Chand, K. (2016). tedwi.com. Retrieved from Techniques: https://bit.ly/2TTroCZ Access Date: 17-
03-2020

❖ Hoffer. (2011). Modern Systems Analysis and Design-6th Edition. Pearson.

❖ Jaint, K. (2012). Feedback for Users (Human-Computer Interaction). Retrieved from

w3computing.com: https://bit.ly/2TXsOfC

❖ The systems development environment. (2014). In J. F. Valacich, Modern Systems Analysis And
Design.

7|CIS 270