AIS Module 8 - 11

Download as pdf or txt
Download as pdf or txt
You are on page 1of 30

The Development Phase

Proud to be RTUian
Systems Development
- the stage during which the system is
actually built based upon the designs
conceived in the earlier phases.
- heavy support is required from IT or IS
Department (Computer /Systems
Engineer, Programmers) for the
technical requirements or
specifications.
Proud to be RTUian
Systems Development
Deliverables
- the system, ready for implementation, i.e.,
> completed policies and
procedures,
> finalized software whether user-
written or application package,
> hardware is available,
> all tests are completed with the test
results approved and accepted by the users
> personnel who are well-trained to
use the system.
Proud to be RTUian
The Tasks of Systems Development
1. Vendor Selection
Vendor reputation
Vendor experience and training
Vendor maintenance and services
Training and orientation
Manuals and documentation
Convenient service depots
Lead time schedules - the period between
ordering a piece of equipment and its actual
delivery Proud to be RTUian
The Tasks of Systems Development
1. Vendor Selection
Contract terms:
> Purchase price
> Terms of payment
> Delivery date
> Exchange or return privileges
> Warranty terms – terms and
conditions for handling defective goods, period
of coverage, who pays shipping charges:
excludes damages from abuse or misuse, or
equipment operated contrary to the
manufacturer’s instructions.
The Tasks of Systems Development
2. Evaluation of Hardware Performance
CPU/Input/output performance
Storage capacity
Expandability
Multiprocessing
Communications capability
Physical dimensions

Proud to be RTUian
The Tasks of Systems Development
3. Evaluation of Software Performance
Outright purchase or license agreement
Ability to meet users’ requirements
Program documentation
Tutorial and instruction software
Responsibility for debugging
Software revisions and update
Copy protection schemes
Availability of vendor support
Proud to be RTUian
The Tasks of Systems Development
4. Evaluation of Communications
Equipment Performance
Conformance to standards
Data transmission speed
Voice, data, and video integration
Connective arrangements: LANs /
WANs
Traffic volume that can be
accommodated
Proud to be RTUian
The Tasks of Systems Development
5. Installation of Prototype
Hardware and software are put in place in a
limited environment for testing and
evaluation
Benchmark test – test of hardware or
software performance
Program test, string test, system test
(beta test)
Test scripts – for all possible scenarios
Acceptance test – signed off by the
users
The Tasks of Systems Development
6. Finding and Training of Personnel
Primary considerations:
> Education, training, experience
> Attitude
> Adaptability and ability to learn

Proud to be RTUian
The Implementation Phase

Proud to be RTUian
Systems Implementation
- The planned and orderly conversion from
an existing system to a new one.
- Involves fine-tuning elements in order to
maximize efficiency.

Proud to be RTUian
Systems Implementation
Data Conversion
- Consider new coding system
- New field and record length, data
type, etc.
- A translation file is normally used
to control that all codes are converted
and migrated.

Proud to be RTUian
Systems Implementation
Data Migration
- what data – balances, details of
transactions
- manual or one-time migration
programs

Proud to be RTUian
Systems Implementation
Task List
1. Prepare change-over timetable
- All-at-Once Changeover
- Parallel Systems Operations
- Gradual Changeover
2. Notify employees
3. Undertake training and in-service
programs
Proud to be RTUian
1. Prepare Changeover Timetable
All-at-Once Changeover
- The old system is abandoned and the
new system becomes operational on a
specific date.

Proud to be RTUian
1. Prepare Changeover Timetable
Parallel Systems Operation
- Operating both the old and new
concurrently.

Proud to be RTUian
1. Prepare Changeover Timetable
Gradual Changeover
- The new systems is introduced in
steps. As one part of the new system is
tested and perfected, that portion of
the old system is phased out.

Proud to be RTUian
2. Notify Employees
The human element
- resistance to change, uncertainty,
fear, and doubt.
1. Announce new system formally
2. Involve personnel early
3. Stress benefits to be gained from the
new system
4. Report progress periodically
5. Encourage positive support (rewards and
recognition)
Proud to be RTUian
3. Undertake Training and In-service
Programs
1. Prepare a training curriculum
(competency based)
2. Proficiency and the learning curve
- when system is newly installed,
the performance is slow, the error is high,
and output may not be dependable
3. Super-users as consultants

Proud to be RTUian
Systems Evaluation and
Optimization

Proud to be RTUian
Systems Evaluation
- the systematic assessment of system
performance to determine whether
goals have been reached.

Proud to be RTUian
Common Performance Criteria
1. Time element (time delays)
a. Response time
> the time that elapses before a
system responds to a demand placed upon it.
b. Turnaround time
> the period during which a system
carries out a demand placed upon it.
2. Cost element
- excessive costs maintenance, expansion,
training, storage
Proud to be RTUian
Common Performance Criteria
3. Hardware performance
4. Software performance
- productivity, accuracy, security, debugging
of errors
5. Inconvenience to employees
a. user complaints
b. employee morale
6. Inconvenience to customers
- customer reactions
Proud to be RTUian
Systems Optimization
- the redesign and refinement of
systems components to improve their
performance. In general, the result of
the systems evaluation is used.

Proud to be RTUian
Systems Documentation

Proud to be RTUian
Systems Documentation
Documentation are written manuals,
diagrams, narratives, layouts, or
drawings that describes how a system
function

Proud to be RTUian
Systems Documentation
Need for documentation:
a. Communication tool
b. Facilitates troubleshooting
c. Facilitates systems revision
d. Personnel training
e. Consistency
f. Management Tool
g. Elimination of redundancy
h. Auditing
Proud to be RTUian
Systems Documentation
Major systems documentation
a. Policy manuals
b. Procedure manuals
c. Forms manual
d. Training manuals
e. Organization manuals
f. Systems manual
g. Software documentation
h. Systems development documentation
Proud to be RTUian
****** END ******
ACKNOWLEDGEMENT:
The lecture notes used from Module 1 to Module 11
are based largely on the book:
Systems Analysis and Design
by: Gerald Silver and Myrna Silver

and materials available from the internet

Proud to be RTUian

You might also like