Systems Project Management, Implementation, Operation, Control

Systems Project Management,
Implementation, Operation, Control
Chapter 12
12– 1
 2013 Pearson Education, Inc. Publishing as Prentice Hall, AIS, 11/e, by Bodnar/Hopwood
Learning Objectives 1, 2 & 3
Describe the major phases of
systems implementation.
Recognize significant human factors

involved in systems implementation.
Detail the types of documentation

involved in the implementation of a new
system.
12 – 2
Systems Implementation
 Formal plans and controls should be
established to address the problems that can
occur during systems implementation.
 Three major steps in systems
implementation:
1. Establish plans and controls
2. Execute activities as planned
3. Follow up and evaluate the new system
12– 3
Systems Implementation
12– 4
Step 1: Establish Plans and
Controls for Implementation
 In order to manage the implementation
project adequately, specific plans need to be
developed:
1. a breakdown of the project into various
phases,
2. specific budgets applicable to each phase, and
3. specific timetables applicable to each project
phase.
12– 5
Step 1: Establish Plans and
Controls for Implementation
Scheduling Techniques:
 Gantt chart
 Network diagram
 Critical path
12– 6
Gantt Chart Example
12– 7
Simple Network Diagram
12– 8
Other Metrics
 Software Process Improvement and Capability
(SPICE) is a process-based development
approach that focuses on the “maturity” of the
process being developed.
 Other project management methods:
 V-Model
 PRINCE2 (Projects IN Controlled
Environments)
 Total Cost Management Methods
12– 9
Step 2: Executing
Implementation Activities
 Typical activities during execution include:
 Selecting and training personnel
 Installing new computer equipment
 Detailed systems design
 Writing and testing computer programs
 System testing
 Standards development
 Documentation
 File conversion
12– 10
Step 2: Executing
Implementation Activities
 In order to provide a smooth transition,
management and the system team should
make a formal announcement regarding the
execution of the project.
 Reassure employees
 Minimize rumors
 Organization of a Special Project Team
12– 11
Employee Training
 Outside training consultants
 Training manuals
 Videotape presentations
 Audiotape presentations
 Training seminars
 Individualized hands-on instruction
 Computer-assisted training
12– 12
Acquiring and Installing New
Computer Equipment
 Engineers and other personnel may be
required to assist in the installation.
 Adequate facilities must be available.
 Controlled environments are required.
 Specialized security measures:
 Fire extinguishing systems
 Video monitoring systems
 Specialized door locks
12– 13
Detailed Systems Design
 Additional design work
 Last minute fine-tuning of the systems design
plan
 Computer programming and/or customization
 Computer applications carefully tested
 Computer applications documented adequately
 Test related computer programs as a group
12– 14
Documenting the New System
 Documentation is one of the most important parts of
systems implementation.
 Good documentation can serve a wide range of
useful purposes:
1) training new employees,
2) providing programmers and analysts with useful
information for future program evaluation and
modification activities,
3) providing auditors with useful information for
evaluating internal controls, and
4) assisting in ensuring that systems design specifications
are met.
12– 15
File Conversion
 A typical problem in systems implementation
is that of data conversion:
 In some cases, files maintained manually must
be converted to computer format.
 Conversion can be an expensive, time-
consuming process.
 Data screening may be necessary after entering
the information into the computer due to errors
in the data input process.
12– 16
Test Operations
 There are three basic approaches to the final
testing of the system:
1) Direct approach - involves switching to the
new system and abandoning the old system at
a fixed point in time (cutover point).
2) Parallel approach – involves running the new
and old systems simultaneously.
3) Modular conversion – involves phasing in the
new system in segments.
12– 17
Step 3: Evaluating the
New System
 Approaches to follow-up and
evaluation:
 Observation
 Questionnaires
 Performance measures
 Benchmarks
12– 18
Learning Objectives 4 & 5
Understand how to plan and control

a systems project.
Be aware of tools and technologies

used in the project development
environment.
12 – 19
Planning and Organizing a
Systems Project
 Organizational resources should be
allocated to projects that yield the
greatest benefits to an organization.
 Project selection
 The project team
 Project leader responsibilities
 Project uncertainty
12– 20
Project Team Organization
12– 21
Project Leader Responsibilities
12– 22
Factoring a Project into
Phases and Tasks
12– 23
Work Measurement Techniques
 Identify the tasks to be estimated.
 Estimate the total size or volume for each
task.
 Convert the size or volume estimate into a
time estimate.
 Adjust the estimated processing rate to
include circumstantial considerations.
12– 24
Accuracy of Estimates
 Estimates made during the early phase of a
project can be expected to be inaccurate.
 Initial estimates are frequently made too low.
 Lowballing – purposely or inadvertently
submitting unreasonably low time or cost
estimates to obtain a contract.
 Cost overruns are a frequent problem.
12– 25
Project Accounting
 Project control is established by setting
measureable goals for each phase and task in
the overall project.
 A project accounting system is a cost
accounting system in which costs are assigned
to individual projects as they proceed through
development.
 The appropriate level of detail must be
determined by project management.
12– 26
Project Accounting
12– 27
Project Development Environment
 Project collaboration platform
 Software application framework
 Integrated development environment
 Software versioning system
 Application solution stacks
12– 28
Software Application Framework
 Software application framework provides a
structured environment in which to develop
software.
 Web application frameworks
 Client-side
 JavaScript
 Server-side
 Mainstay of most Web 2.0 applications
12– 29
All-in-One and Integrated
Platforms
 There is a trend toward integrating IT
governance, enterprise architecture,
business process modeling, and
management into application suites.
 These platforms can work in conjunction
with the components of the development
environment.
12– 30
Learning Objective 6
Describe several approaches for

control over nonfinancial system
resources.
12 – 31
Control Over Nonfinancial
Information Systems Resources
 A number of factors relating to information
systems are important to management from
a control point of view but are not
measured in terms of dollars. Performance
measures for:
 Hardware
 Software
 Personnel
12– 32
 Measuring hardware performance
involves:
 Systems utilization
 Ratios such as server CPU time used to time
available
 Systems downtime
 Percentage of time that the application is
unavailable for use.
 Systems responsiveness
12– 33
 Evaluating software performance:
 Survey system users
 Constantly monitor software
performance
12– 34
 Controls relating to personnel
involve preparing performance
reports for:
 Software technicians
 Hardware repair persons
12– 35
Auditing the Information System
 The audit’s focus should be on the
information system itself and on the
validity and accuracy of data as
processed by the system.
 Accountant’s interest tends to focus on
internal control
 Tests of compliance
 Tests of specific transactions
12– 36
Maintaining and Modifying
the System
 In all operational systems, it becomes
necessary to make changes.
 It is not possible to foresee all contingencies
during the design phase.
 Environmental conditions and information
needs change.
 Computer applications may contain bugs or
customization problems.
 Bugs – computer programming errors that might
not be detected until the system actually begins
operation.
12– 37
Maintaining and Modifying
the System
 Control of system modifications:
 All modifications should be formally
reviewed and approved.
 Modifications are applied to the original copy
of the software; programmers do not have
access to the operational copy.
 Modifications are reviewed and
independently installed.
 Modifications should be documented
including the reason and approval.
12– 38
End of Chapter 12
12 – 39

Systems Project Management, Implementation, Operation, Control

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Systems Project Management, Implementation, Operation, Control

Uploaded by

Copyright:

Available Formats

Systems Project Management,

Implementation, Operation, Control

Recognize significant human factors

Detail the types of documentation

Understand how to plan and control

Be aware of tools and technologies

Describe several approaches for

You might also like