Professional Documents
Culture Documents
CHAPTER 5
SYSTEM IMPLEMENTATION AND
SUPPORT
LEARNING OUTCOMES
Prototyping Purpose:
To tests system concepts and provides an opportunity to examine input,
output, and user interfaces before final decisions are made.
A prototype is an early working version of an information system.
Just as an aircraft manufacturer test a new design in a wind tunnel,
systems analysts construct and study information systems prototypes.
Advantage:
A prototype can serve as an initial model that is used as benchmark to
evaluate the finished system, or the prototype itself can develop into the
final version of the system.
Either way, prototyping speeds up the development process significantly.
Possible Disadvantage:
Important decisions might be made too early, before business or IT issues
are understood thoroughly.
A prototype based on careful fact finding and modelling techniques, however
can be an extremely valuable tool.
5.1.1 Differentiate system development tools CASE Tools
5.1.1 Differentiate system development tools CASE Tools
Computer-aided systems engineering (CASE), also called computer-aided software
engineering
What:
A technique that uses powerful software, called CASE Tools
CASE tools provide an over all framework for systems development and support a wide
variety of design methodologies, including structured analysis and object-oriented
analysis.
Reason: to help system analysts develop and maintain information systems.
How:
Because CASE tools make it easier to build an information system, they boost it
productivity and improved the quality of the finished product.
Traditional CASE tools system developers often use project management tools, such as
Microsoft Project, and special purpose charting tools, such as Microsoft Visio.
a system analysts can use Visio to create many different types of diagrams,
including block diagrams. Building plans, forms and charts, maps, network
diagrams, and organization charts.
Example of CASE software are:
Microsoft Visio
Rational Rose
Three leading CASE tool suppliers: Visible Systems Corporation, Telelogic Software, and
Rational Software
5.1.1 Differentiate system development tools CASE Tools
Introduction:
The system design specification serves as a blueprint for constructing
the new system
The initial task is application development
Before a changeover can occur, the system must be tested and
documented carefully, users must be trained, and existing data must be
converted
A formal evaluation of the results takes place as part of a final report to
management
5.2.1 Explain the importance of software quality assurance.
Software Engineering
Capability Maturity Model (CMM)
Capability Maturity Model
Integration (CMMI)
Process improvement
CMMI tracks an organization's
processes, using five maturity layers
5.2.1 Explain the importance of software quality assurance.
19
5.2.2 Differentiate the types of software testing
Unit Testing:
Unit testing involves individually testing unit of code separately to make
sure that it works on its own, independent of the other units.
Eg: Testing a function; whether loop or statement in a program is working
properly or not than this is called as unit testing
Integration Testing:
Test the modules to ensure whether they are integrating properly or not
by combining the modules and tested as a group.
Eg: Tester have to test the keyboard of a computer than it is a unit testing
but when tester have to combine the keyboard and mouse of a computer
together to see its working or not than it is the integration testing.
It is prerequisite that for performing integration testing a system must be
unit tested before.
5.2.2 Differentiate the types of software testing
System Testing:
Tester test the complete system as a whole to check whether the system is
properly working or vice versa as per the requirements or not. Testers
always have to concentrate on both functional and non-functional testing
like performance, load, stress, security and recovery testing
In summary: in system testing the testers test the complete system as a
whole.
Eg: Test the whole functionality and non functionality of the system
interactions between all module in Laundry Management System as one
single system.
It is prerequisite that for performing system testing a system must be unit
tested and integration tested before.
5.2.3 Differentiate between program, system,
operations, and user documentation.
Program Documentation
System Documentation
Operations Documentation
User Documentation
Systems analysts usually are responsible for preparing
documentation to help users learn the system
22
5.2.3 Differentiate between program, system,
operations, and user documentation.
User Documentation
Effective online documentation is
an important productivity tool
Written documentation material
also is valuable
26
5.3 Explain System Implementation
28
5.3.1 List the main steps in system implementation.
The new system now is ready to go to work. Now, you will carry out the
remaining steps in systems implementation:
1. Prepare a separate operational and test environment
29
5.3.2 System Installation And Evaluation
Vendor Training - Many hardware and software vendors offer training programs free or at a
nominal cost for the products they sell. The training usually is conducted at the vendors site
by experienced trainers who provide valuable hands-on experience. Vendor training often
gives the best return on your training dollars because it is focused on products that the
vendor developed. Many vendors offer Web-based training options, including Webinars,
podcasts, and tutorials.
In-house Training - The IT staff and user departments often share responsibility for
developing and conducting training programs for internally developed software. If your
organization has a help desk, the staff might be able to handle internally user training.
5.3.2 System Installation And Evaluation
3. Data Conversion
Data conversion is an important part of the system installation process. During data conversion,
existing data is loaded into the new system.
Data Conversion Strategy - When a new system replaces an existing system, you should automate
the data conversion process, if possible.
The old system might be capable of exporting data in an acceptable format for the new system or
in a standard format. If a standard format is not available, you must develop a program to extract
the data and convert it to an acceptable format.
5.3.2 System Installation And Evaluation
3. System Changeover
System changeover is the process of putting the new information
system online and retiring the old system.
Changeover can be rapid or slow, depending on the method. The
four changeover methods are :
1. direct cutover
2. parallel operation
3. pilot operation
4. phased operation
System Changeover
34
System Changeover
Direct Cutover
Involves more risk than other
changeover methods
Companies often choose the direct
cutover method for implementing
commercial software packages
Cyclical information systems
usually are converted using the
direct cutover method at the
beginning of a quarter, calendar
year, or fiscal year
35
System Changeover
Parallel Operation
Easier to verify that the new system is
working properly under parallel operation
than under direct cutover
Running both systems might place a burden
on the operating environment and cause
processing delay
Is not practical if the old and new systems are
incompatible technically
Also is inappropriate when the two systems
perform different functions
36
System Changeover
Pilot Operation
The group that uses the new system first is
called the pilot site
The old system continues to operate for
the entire organization
After the system proves successful at the
pilot site, it is implemented in the rest of
the organization, usually using the direct
cutover method
Is a combination of parallel operation and
direct cutover methods
37
System Changeover
Phased Operation
You give a part of the system to all users
The risk of errors or failures is limited to the
implemented module only
Is less expensive than full parallel operation
Is not possible, however, if the system cannot
be separated easily into logical modules or
segments
38
System Changeover summary
risk vs cost
39
5.3.2 System Installation And Evaluation
4. Post-implementation Evaluation
A post-implementation evaluation assesses the overall quality of the information system.
The evaluation verifies that the new system meets specified requirements, complies with
user objectives, and produces the anticipated benefits.
41
5.4 Understand Systems Support and Security
5.4.1 Explain the system support and security phase
5.4.2 Identify user support:
User training
Help desk
5.4.3 Explain various types of maintenance:
Corrective maintenance
Adaptive maintenance
Perfective maintenance
Preventive maintenance
5.4.4 Identify tools for system maintenance
5.4.5 Explain the system security and backup
5.4.6 Identify three elements of system security
5.4.1 Explain the system support and security phase
Systems support and security is the final phase in the systems development
life cycle.
Managing systems support and security involves three main concerns:
1.user expectations
2.system performance
3.security requirements
5.4.2 Identify user support:
Help Desks
User Training To make data more accessible and to empower users,
many IT departments create help desks.
New employees must be trained on the
companys information systems.
A help desk is a centralized resource staffed by IT
The main objective is to show users how professionals who provide users with the support they
the system can help them perform their need to do their jobs.
jobs. A help desk has three main objectives:
The training could include online support 1.Show people how to use system resources more
via e-mail, a special Web site, a revision effectively
to the user guide, a training manual 2.Provide answers to technical or operational questions
supplement, or formal training sessions. 3.Make users more productive by teaching them how to
meet their own information needs
BACKUP TYPES
Backups can be full, differential, incremental, or continuous.
Backup Policies
The cornerstone of business data protection is a backup policy, which contains
detailed
instructions and procedures. An effective backup policy can help a firm continue
5.4.5 Explain the system security and backup
BACKUP TYPES
Backups can be full, differential, incremental, or continuous.
Backup Policies
The cornerstone of business data protection is a backup policy, which contains detailed
instructions and procedures.
An effective backup policy can help a firm continue business operations and survive a
catastrophe.
The backup policy should specify backup media, backup types, and retention periods.
5.4.5 Explain the system security and backup
Backup Types
Very Famous!
49
5.4.5 Explain the system security and backup
To provide system security, you must consider six separate but interrelated
levels:
physical security,
network security,
application security,
file security,
user security, and
procedural security.
Like the chain shown in Figure 12-26, system security is only as strong as the
weakest link.
5.4.6 Identify three elements of system security
51
5.4.6 Identify three elements of system security