Systems construction

The development,
installation, and testing of
system components.
SYSTEM CONSTRUCTION, IMPLEMENTATION
AND SUPPORT
ZALDY ADRIANTO

1 2

Systems
implementation

The installation and delivery

of the entire system into
production. !
Day-to-day operation

3 4

Tasks for Completing Construction Phase 1.

The Construction Phase
Build and Test Networks
Often system build around existing
networks.!
If system calls for new network
functionality, must by built and tested
prior to programs that use that it.

5 6
 ROLES Construction Phase 2. Build
and Test Databases
Network designer
Designs LAN and WAN connectivity

Network administrator builds and tests Implement database schema

Network architecture standards

Test with sample data

Security

Systems analyst Deliver unpopulated database

Facilitates
structure
Ensures that business requirements are not
compromised

7 8

ROLES Construction Phase 3.

System users Install and Test New Software
Provide and/or approve test data

Database designer/programmer
Build tables, views, stored procedures (if relational
database)

Database administrator If system requires purchased

Tune database for optimum performance

Security or leased software, must be

Backup and recovery

Systems Analyst
installed and tested.
Build non-corporate, applications-oriented
database

Ensures business requirements compliance

9 10

Roles Construction Phase 4. Write

Systems analyst and Test New Programs
Clarifies business requirements

System designer Develop in-house programs

Clarifies integration requirements

Reuse available software components in

Network administrator library

Install software package

Write new components

Software vendor/consultant
Assist in installation and testing
Test

Applications programmer

Document
Test according to integration requirements

11 12
Roles Tasks for Completing The
Implementation Phase
Systems analyst
Clarifies business requirements!
System designer
Clarifies program design and integration
requirements!
Application programmer (or team)
Writes and tests in-house software

13 14

Implementation Phase - Roles

1. Conduct System Test
Test network, databases, purchased
software, new in-house software, and
existing software to make sure it all
works together.
Systems analyst
Develops system test data!
Communicates problems and issues!
System builders (database, network, programmers)
Resolve problems revealed during testing!
System owners and users
Verify whether or not system operates correctly!
May result in return to construction phase
Iterate until successful system test

15 16

Implementation Phase 2.
Prepare Conversion Plan Roles
Plan for how to convert from old system to new System analyst/Project manager
system.!

How to install and populate databases! Develop a detailed conversion

plan!
How to train users!

Finalize documentation!
Steering committee
Conversion issues Approves plan and timetable

17 18
Implementation Phase
Roles
3. Install Databases
Application programmers
Populate new system databases with existing data Write (or use) special programs to
from old system
extract data from existing databases
Generally have to restructure data as it is and populate new databases

populated

Systems analyst/designer
Must confirm that data is translated correctly
Calculate database sizes and estimate
time for installation

19 20

Implementation Phase Roles

4. Train Users System analyst
Plan trainings

Conduct trainings

Write documentation

System users trained and Help users through the learning period

provided with System owners

Approve release time for training

documentation System users

Attend training

Accept system

21 22

Implementation Phase 5.
Convert to New System Roles
Systems analyst/Project manager
Carries out conversion plan

Correct shortcomings

Ownership transfers from Measure system acceptance

analysts and builders to end System owners

users. Provide feedback

System users
Provide feedback

23 24
Support versus
Operation
Systems support is the on-going
technical support for users, as well as
the maintenance required to fix any
errors, omissions, or new
requirements that may arise.
25
The Context of Systems
Operation and Support
27
Support versus
Operation
Systems operation is the day-to-day, week-to-
week, month-to-month, and year-to-year
execution of an information systems business
processes and application programs.!
An operational system is a system that has been
placed into operation. Frequently called a
production system.
26
?
28