Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAPTER 5: SYSTEM IMPLEMENTATION AND SUPPORT - Coggle Diagram
CHAPTER 5: SYSTEM IMPLEMENTATION AND SUPPORT
5.2 Testing In A Project
5.3 System Implementation
5.1 System Development
5.4 System Support & Security
5.4 SYSTEM SUPPORT & SECURITY
System Support & Security Phase
2) system performance
3) security requirements
1) user expectations
User Support
User Training Package.
Training users about system changes is similar to initial training.
The main objective is to show users how the system can help them perform their jobs.
Help Desks
is a centralized resource staffed by IT professionals who provide users with the support they need to do their jobs
Show people how to use system resources more effectively
Provide answers to technical or operational questions
Make users more productive by teaching them how to meet their own information needs.
Types Of Maintenance
2) Adaptive Maintanance
3) Perfective Maintanance
1) Corrective Maintenance
4) Preventive Maintanance
System Security
System security refers to protecting the system from theft, unauthorized access and changes
System Security Concepts
Confidentiality protects
information from unauthorized disclosure and safeguards privacy.
Integrity prevents unauthorized users from creating, modifying, or deleting information.
Availability ensures that authorized users have timely and reliable access to necessary information.
BACKUP AND RECOVERY
Backup refers to copying data at prescribed intervals, or continuously
Recovery involves restoring the data and restarting the system after an
5.1 System Development
System Development Tools
1) Modeling
Object model = Describes objects, which combine data and
processes.
Network model
=Describes the design and protocols of
telecommunication links
Process model = Describes the logic that programmers use to write
code modules
-
Modeling techniques, including data flow diagrams and entity relationship diagrams, and unified modeling language diagrams.
2) Prototyping
-
Prototyping tests system concepts and provide
an opportunity to examine input, output, and
user interface before final decisions are made.
3) CASE Tools
Also called computer-aided software engineering,
to help systems
analysts develop and maintain information systems.
Coding Process
-
process of turning program logic into specific instructions that the computer system can execute.
Programming Environment
Visual Basic, Python, Ruby, and SQL are examples of commonly used programming languages
Generating Code
Some commercial applications can generate editable program code directly from macros, keystrokes, or mouse actions.
5.2 TESTING IN A PROJECT
Software Quality Assurance
Importance of software quality assurance
Knowing that the quality of your software is up to the mark is extremely important
Types of software testing
Integration testing
Testing two or more programs that depend on Testing two or more programs that depend on each other is called integration testing, or link testing .
System testing
After completing integration testing, you must perform system testing,
A system test includes all typical processing situations and is intended to assure users, developers, and managers that the program meets all specifications
Unit testing
The testing of an individual program or module is called unit testing.
to identify and eliminate execution errors
Documentation
Documentation describes an information system and helps the users, managers, and IT staff who must interact with it.
is essential for successful system
operation and maintenance.
1)program documentation
describes the inputs,outputs, and processing logic for all program modules
2) system documentation
describes the system’s functions and how they are implemented
includes data dictionary includes data dictionary layouts, source documents, and the systems request that initiated the project.
3) operations documentation
Operations documentation contains all the information needed for processing and distributing online and printed output.
4) user documentation
instructions and information to users who will interact with the system and includes user manuals, Help screens, and tutorials.
5.3 SYSTEM IMPLEMENTATION
System Installation & Evaluation
Steps in systems implementation
1) Prepare a separate operational and test environment
2) Provide training for users, managers, and IT staff
3) Perform data conversion and system changeover
4) Carry out post-implementation evaluation of the system
5) Present a final report to management
Operational & test environment
The environment for the actual system operation is called the operational environment or production environment.
The environment that analysts and programmers use to develop and maintain programs is called the test environment.
Training
1) Training plan
The three main groups for training are users managers, and IT staff
You must determine how the company will provide training
2) Vendor Training
If the system includes the purchase of software or hardware, then vendor-supplied training is one of the features you should investigate in the RFPs the features you should investigate in the (requests for proposal) and RFQs (requests for quotation) that you send to potential vendors .
3) Webinars, Podcasts, and Tutorials
is an Internet-based training session that provides an interactive experience.
4) Outside Training Resources
Many training consultants, institutes, and firms are available that provide either standardized or customized training packages
5) Training Tips
Train people in groups, with separate training programs for distinct groups
Select the most effective place to conduct the training
Provide for learning by hearing, seeing, and doing
6) Interactive Training
Online training
= Should include step-by-step instructions
Video tutorials = You don’t have to be a professional video developer to create effective training tutorials
Data conversion
During data conversion, existing data is loaded into the new system.
Depending on the system, data conversion can be done before, during, or after the operational environment is complete
System changeover
process of putting the new information system online and retiring the old system.
four changeover methods are
2) parallel operation
Easier to verify that the new system is working
properly under parallel operation than under direct cutover
3) pilot operation
uses the new system first is called the pilot site
Is a combination of parallel operation and direct cutover methods
4) 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
1) direct cutover
Involves more risk than other changeover methods
Post-implementation task
perform two additional tasks
Prepare a post-implementation evaluation
Deliver a final report to management.
1) Post-Implementation Evaluation
should examine all aspects of the development effort and the end product — the developed information system
2) Final Report to Management