I Gusti Bagus Dharma Mahardika | 13414032

TUGAS APSI
Rangkuman Bab 19 Systems Construction and Implementation

Definition
Systems construction is the development, installation, and testing of system components.
Systems implementation is the delivery of the system into production (meaning day-to-day operation).
System implementation and construction is from the perspective of system builder.

System Construction
The purpose of the construction phase is 10 develop and test a functional system that fulfills business and design
requirements and to implement the interfaces between the new system and existing production systems.

The construction phase consists of four tasks:

1. Build and test networks

In this phase, data and process models produced from the previous phase of IS development is used to
implement the network architecture.
Before building databases, it is needed to build and test the network
Roles:
o Designer:
Design of local and wide area network
o Network Admin:
Building and testing network design
o Analyst:
Facilitator to ensure the business requirements arent compromised during the building process
2. Build and test databases
Implement database schema, test with sample data, and deliver unpopulated database structure

Roles:

o System users
Provide and/or approve test data
o Database designer/programmer
Build tables, views, stored procedures (if relational database)
o Database administrator
Tune database for optimum performance
Security
Backup and recovery
o Systems Analyst
Build non-corporate, applications-oriented database
 I Gusti Bagus Dharma Mahardika | 13414032

Ensures business requirements compliance

3. Install and test new software packages
The activity of implementing software packages after the network and databases have been built.
This phase involves:
o System Analyst: Clarifying the software package according to business requirement
o Designer: Clarifying integration requirement and program documentation
o Network Administrator: Installing software package into the network
o Software vendor: Assist in the installation of the software

Input: New software packages from vendor

Output: Installed and tested software package

4. Write and test new programs

The process of developing new or modified software in the new system
This phase involves:
o System Analyst: Clarifying business requirement
o System Builder: Writing and testing the new programs

Input: Technical design statement, plan for programming, and test data

Output: Usable new programs and reusable software components that are placed in the software library.

Three levels of testing are performed on new programs:

1. Stub testing is testing performed on individual modules, whether they be main program, subroutine,
subprogram, block, or paragraph.
2. Unit or program testing is testing in which all the modules that have been coded and stub tested are
tested as an integrated unit.
3. System testing ensures that application programs written in isolation work property when they are
integrated into the total system

System Implementation
The purpose of the Implementation phase is to smoothly convert from the old system to the new system.

The systems implementation consists of the following activities:

o Conducting a system test
Test network, databases, purchased software, new in-house software, and existing software to make sure
it all works together.
Roles
o Systems analyst
Develops system test data
Communicates problems and issues
o System builders (database, network, programmers)
 I Gusti Bagus Dharma Mahardika | 13414032

Resolve problems revealed during testing

o System owners and users
Verify whether or not system operates correctly
May result in return to construction phase

Iterate until successful system test

o Preparing a systems conversion plan

After successfully testing, in this phase the system analyst will develop a detailed.
The principle deliverable is conversion plan that will identify database to be installed, end-user training and
documentation, and a strategy to converting the old to the new system.

There are several commonly used strategies for converting from an existing to a new production
information system, including:
Abrupt cut-over- On a specific date, the old system ls terminated and the new system is placed into
operation.
Parallel conversion- Both the old and the new systems are operated for some time period to ensure
that all major problems in the new system are solved before the old system is discarded.
Location conversion-When the same system will be used in numerous geographical locations, it is
usually converted at one location and, following approval, farmed to the other sites
Staged conversion- Each successive version of the new system is converted as it is developed. Each
version may be converted using the abrupt, parallel, or location strategies.

The systems acceptance test is the final opportunity for end users, management, and information systems
operations management to accept or reject the system. A systems acceptance test is a final system test
performed by end users using real data cover an extended period. It ls an extensive test that addresses
three levels of acceptance testing-verification testing, validation testing, and audit testing:
Verification testing runs the system in a simulated environment using simulated data.
Validation testing runs the system in a live environment using real data. This is sometimes called beta
testing.
Audit testing certifies that the system is free of errors and is ready to be placed into operation

o Installing databases
Populate new system databases with existing data from old system
o Generally have to restructure data as it is populated
o Must confirm that data is translated correctly
Roles
o Application programmers
Write (or use) special programs to extract data from existing databases and populate new
databases
o Systems analyst/designer
 I Gusti Bagus Dharma Mahardika | 13414032

Calculate database sizes and estimate time for installation

o Training system users

System users trained and provided with documentation
Roles:
o System analyst
Plan trainings
Conduct trainings
Write documentation
Help users through the learning period
o System owners
Approve release time for training
o System users
Attend training
Accept system

o Converting from the old system to the new system.

Ownership transfers from analysts and builders to end users.
Roles:
Systems analyst/Project manager
Carries out conversion plan
Correct shortcomings
Measure system acceptance
System owners
Provide feedback
System users
Provide feedback

Reference:
Whitten, Jeffry L. 2007. Systems Analysis & Design Methods 7th Ed. New York: McGraw-Hill