Transition to the New SystemS Y S T E M S A N A LY S I S .docx

Transition to the New
System
S Y S T E M S A N A LY S I S A N D D E S I G N , 6 T H E
D I T I O N
D E N N I S , W I X O M , A N D R O T H
© 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1
Learning Objectives
installation process.
to use them.
Making the Transition
to the New System
S M O O T H I N G T H E PAT H

Key Ideas
from pre-existing norms and habits.
o Unfreezing -- loosening up peoples’ habits and norms
o Moving -- transition from old to new systems
o Refreezing -- institutionalize and make efficient the new
way of doing things
Implementing
Change
Migration Planning
G U I D I N G T H E P R O C E S S
Migration Planning
hen and by whom
o Technical aspects
o Organizational aspects

work
Elements of a Migration Plan
Business Contingency Plan
conversion?
o Technical glitches may occur during the transition
o Is the old system still available?
o If not, how do we keep the business running?
o Can manual procedures be used for a short time?
o Think about the consequences of being unable to operate
normally…lost sales, unhappy customers… could we stay
afloat?
Conversion
Strategies

Conversion Styles
o The new system instantly replaces the old
o For a time both old and new systems are used. The old is
abandoned
when the new is proven fully capable.
Conversion Location
o One or more locations are converted to work out bugs before
extending to other locations
o Locations are converted in sets
o All locations are converted at the same time
Conversion Modules
conversion
o All modules converted in one step
o When modules are loosely associated, they can be converted
one at a

time
Key Factors in Selecting a Conversion
Strategy
o Seriousness of consequences of remaining bugs
o Parallel requires paying for two systems for a period of time
o Simultaneous requires more staff to support all locations
o Parallel, phased, and modular require more time
Determining a Conversion Strategy:
Risk
o Parallel conversion style
o Pilot conversion location
o Conversion by modules
o Direct conversion style
o Simultaneous conversion location
o Conversion of whole system

Determining a conversion strategy:
Cost
o Pilot or phased conversion location
st cost conversion strategy:
o Conversion of modules
Determining a Conversion Strategy:
Time
o Phased conversion location
o Conversion of modules
Summary of Conversion Strategies

Change Management
P R E PA R I N G T H E P E O P L E F O R T H E N E W S
Y S T E M
Key Roles in Change Management
is the business person who initiated the
request for the new system
effort
Steps in Change Management
1. Revise management policies
2. Assess costs and benefits models of potential adopters
3. Motivate adoption
4. Enable people to adopt
Understanding Resistance to Change
nges that benefit an organization do not
necessarily benefit each individual

which there may be no additional compensation
The Costs and
Benefits of
Change
Revising Management Policies
management policies support its adoption
o Standard operating procedures (SOPs)
o Measurements and rewards
o Resource allocation
Change Management Planning
o Informational - aims to convince adopters that change is
better
o Political - uses organizational power to motivate change
o Potential adopters generally are
-30% Ready adopters

-30% Resistant adopters
-60% Reluctant adopters
adopters
and helping them win over the reluctant adopters.
Training
ay be needed to handle the changed business
processes
What to Train
features
rios provide an outline for common activities
and a basis to plan training

Types of Training
-on-one
-based
When Would
You Use Each
Type of
Training?
Postimplementation
Activities
I N S T I T U T I O N A L I Z I N G T H E N E W S Y S T E
M
Institutionalizing the System
o Assistance in using the system
o Repair or fix discovered bugs or errors
o Add minor enhancements to provide added value
o Analyze what was done well

o Discover what activities need improvement in the future
Types of System Support
-demand training at time of user need
o Frequently asked questions (FAQ)
o Phone service for known issues
o Level 1 Support – Broad knowledge
o Unresolved issues passed to Level 2 Support – specialists in
the application
system
Sources of Change Requests
1. Problem reports from the operations group
2. Requests for enhancements from users
3. Requests from other systems development projects
4. Change requests from senior management
Processing a
Change Request

Project Assessment
o Were cost estimates accurate?
o Did expected benefits actually materialize?
o Was this project really worth doing?
quickly
Project Team Review
-3 page document regarding her
or his actions during the project
others
learned
System Review
system are realized
estimating costs and benefits for future projects
Transition to the New SystemLearning ObjectivesMaking the
Transition to the New SystemKey IdeasImplementing
ChangeMigration PlanningMigration PlanningElements of a

Migration PlanBusiness Contingency PlanConversion
StrategiesConversion StylesConversion LocationConversion
ModulesKey Factors in Selecting a Conversion
StrategyDetermining a Conversion Strategy:� RiskDetermining
a conversion strategy:� CostDetermining a Conversion
Strategy:� TimeSummary of Conversion StrategiesChange
ManagementKey Roles in Change ManagementSteps in Change
ManagementUnderstanding Resistance to ChangeThe Costs and
Benefits of ChangeRevising Management PoliciesChange
Management PlanningTrainingWhat to TrainTypes of
TrainingWhen Would You Use Each Type of
Training?Postimplementation ActivitiesInstitutionalizing the
SystemTypes of System SupportSources of Change
RequestsProcessing a Change RequestProject AssessmentProject
Team ReviewSystem Review
Moving into
Implementation
S Y S T E M S A N A LY S I S A N D D E S I G N , 6 T H E
D I T I O N
D E N N I S , W I X O M , A N D R O T H
© 2015 JOHN WILEY & SONS. ALL RIGHTS
RESERVED.Roberta M. Roth 1
Learning Objectives

Key Definitions
system: the software itself, documentation, and new
operating procedures.
Managing the
Programming Process
P R O J E C T M A N A G E M E N T D U R I N G C O N S T
R U C T I O N
Project Manager’s Tasks During
Programming
vities
The Programmer Paradox

programming task, adding more people slows down
rather than speeds up completion of the project.
series of independent, smaller parts.
Assigning Programmers
Two communication
channels
Twelve communication
channels
o Match programming tasks with programmer capabilities
o When skills are deficient, apply mentoring and training
Coordinating Activities
kly (hopefully brief) meetings
o Development area
o Testing area
o Production area

Managing the Schedule
the temptation to lower quality to meet
unreasonable schedule demands
Avoid Classic Mistakes
-oriented development
If you use state-of-the art technology, lengthen planned time
-cost” personnel
If using a significant number of entry level personnel, lengthen
planned time
Use source code library to keep programmers from changing the
same code at the same time
Always allocate sufficient time for formal testing

Testing
E N S U R I N G T H E S Y S T E M F U L F I L L S R E Q
U I R E M E N T S
Testing Philosophy
ensure that the system performs as outlined in
the
specifications.
testing
plan
an
error
nd results documented
carefully
Test Plan
Roberta M. Roth © 2015 JOHN WILEY & SONS. ALL
RIGHTS RESERVED. 13

Categories of Testing
o Tests control structures before all modules are written
o Tests each module – Does it performs its function?
o Tests the interaction of modules - do they work together?
o Tests to assure that the software works well as part of the
overall system
o Tests to assure that the system serves organizational needs
RIGHTS RESERVED. 14
Stub Testing
RIGHTS RESERVED. 15
Unit Testing
ck Box Testing
o Focuses on whether the unit meets requirements stated in
specification
-Box Testing

o Looks inside the module at actual code
Integration Testing
o Tests each interface function
-scenario testing
o Ensures that each use scenario works correctly
o Tests each process in a step-by-step fashion
o Ensures data transfer between systems
System Testing
o Ensures that integration did not cause new errors
o Tests how easy and error-free the system is in use
o Assures that security functions are handled properly
o Assures that the system works under high volumes of
activity (e.g., simultaneous users, peak transaction volume)
o Analysts check the accuracy of documentation

Acceptance Testing
o Performed by users to assure they accept the system;
frequently repeats
earlier tests
o Uses real data, not test data. Actual users monitor for errors
or needed
improvements.
User sign-off following Acceptance Testing indicates the
system is ready to be placed into production.
Developing
Documentation
C R E AT I N G G O O D D O C U M E N TAT I O N
Types of Documentation
easier to use and repair.
o Intended to help programmers and analysts understand and

maintain the
system after it is installed
o Intended to help users operate the system
Producing Documentation
hours per screen.
not be left to the end of the project.
be built into project plan.
-line documentation is predominant today.
Value of Online Documentation
(e.g., tool tips, animated demos, narrated demos).

Types of User Documentation
– includes
manual procedures).
Sources of Documentation Topics
Guidelines for Crafting
Documentation Topics
how to do that step
e steps correctly (as actions)

Samples for
Tune Source
Moving into ImplementationLearning ObjectivesKey
DefinitionsManaging the Programming ProcessProject
Manager’s Tasks During ProgrammingThe Programmer
ParadoxAssigning ProgrammersCoordinating
ActivitiesManaging the ScheduleAvoid Classic
MistakesTestingTesting PhilosophyTest PlanCategories of
TestingStub TestingUnit TestingIntegration TestingSystem
TestingAcceptance TestingDeveloping DocumentationTypes of
DocumentationProducing DocumentationValue of Online
DocumentationTypes of User DocumentationSources of
Documentation TopicsGuidelines for Crafting Documentation
TopicsSamples for Tune Source
Test Plan
Page ___ of ___
Program ID: _
AuthorSearch
____________ Version Number: _
1
____
Tester: _
Johnson
_________ Date Designed : _
2/19
____ Date Conducted : _
2/26
_____

Results: Passed Open Items
Test ID: _6___ Requirement Addressed: _
Verify Author search
___
Objective:
Ensure that the interface retrieves the author name and
retrieves his/her books correctly.
Test Cases
In
terface ID Data Field
Value Entered
1)
REQ43
-
5.5
__
Author text box
_____________________ __
blank
____________
2)
REQ43

-
5.5
__
Author text box
_____________________
__aa
_____
_________
3)
REQ43
-
5.5
__
Author text box
_____________________
__123
_____________
4)
REQ43
-
5.5
__
Author text box
_____________________
__cornwell
_________
5)
REQ43
-
5.5

__
Author text box
_____________________
__CORNWELL
_____
_
6)
REQ43
-
5.5
__
Author text box
_____________________
__Cornwell
_________
Script
Expected Results/Notes
Cases 4, 5, 6 are valid; cases 1, 2, 3 are invalid and should
produce an error message.
Actual Results/Notes
Cases 4, 5, 6 were acc
epted; cases 1, 2, 3 were rejected and produced a correct error
message.

Test Plan Page ___
of ___
Program ID: _AuthorSearch____________ Version Number:
_1____
Tester: _Johnson_________ Date Designed : _2/19____
Date Conducted : _2/26_____
Results: Passed Open Items
Test ID: _6___ Requirement Addressed: _Verify Author
search___
Objective:
Ensure that the interface retrieves the author name and
retrieves his/her books correctly.
Test Cases
Interface ID Data Field
Value Entered
1) REQ43-5.5 __Author text box_____________________
__blank____________
__aa______________
__123_____________

__cornwell_________
__CORNWELL______
__Cornwell_________
Script
Expected Results/Notes
Cases 4, 5, 6 are valid; cases 1, 2, 3 are invalid and should
produce an error message.
Actual Results/Notes
Cases 4, 5, 6 were accepted; cases 1, 2, 3 were rejected and
produced a correct error message.

Transition to the New SystemS Y S T E M S A N A LY S I S .docx

Recommended

Recommended

More Related Content

Similar to Transition to the New SystemS Y S T E M S A N A LY S I S .docx

Similar to Transition to the New SystemS Y S T E M S A N A LY S I S .docx (20)

More from turveycharlyn

More from turveycharlyn (20)

Recently uploaded

Recently uploaded (20)

Transition to the New SystemS Y S T E M S A N A LY S I S .docx