Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAPTER 5 SYSTEM IMPLEMENTATION AND SUPPORT - Coggle Diagram
CHAPTER 5
SYSTEM IMPLEMENTATION AND SUPPORT
TOPIC 5.1
SYSTEM DEVELOPMENT
SYSTEM DEVELOPMENT TOOLS
1.c. CASE TOOLS
maintain information systems and help systems analysts develop
1.a. MODELING
analyze, test and modify
1.a.b NETWORK MODEL
1.a.c PROCESS MODEL
1.a.a OBJECT MODEL
1.b. PROTOTYPING
examine input, output and user interface
1.2. CODING PROCESS
transform program logic into code statement
1.2.a. PROGRAMMING ENVIRONMENT
Visual basic, Python, Ruby and SQL
1.2.b GENERATING CODE
application generator, report writers, screen generators,
fourth-generation languages and other CASE tools
TOPIC 5.2
TESTING IN A PROJECT
2.1 SOFTWARE QUALITY ASSURANCE
its important as it define and measures the adequacy of the software(SW) process, providing evidence that establishes confidence to produce SW product of suitable quality for their intended purpose
2.2 TYPES OF SOFTWARE TESTING
2.2.a UNIT TESTING
testing a program to fix errors
2.2.b INTEGRATION TESTING
testing two or more program that depend on each other
2.2.c SYSTEM TESTING
to know that all necessary features have been included in the program
2.2.c.i objective
demonstrate that users can interact with the system successfully
verify that all system components are integrated properly and that actual processing situations will be handled correctly
confirm that the information systems can hanle predicted volumes of data in a timely and efficient manner
2.3 DOCUMENTATION
describes an information system and helps the users, manager and IT staff who must interact with it
2.3.a PROGRAM DOCUMENTATION
describe the inputs, outputs, and processing logic for all program modules.
2.3.b SYSTEM DOCUMENTATION
describe the system's function and how they are implemented.
its include data dictionary entries, data flow diagrams, object models, screen layout, source document and the systems request that initiated the project.
2.3.c OPERATIONS DOCUMENTATION
contains all the information needed for processing and distributing online and printed output
a. Program, system analyst, programmer and system identification
b. Scheduling information for printed output such as report run frequency and deadline
c. Input files and where they originate and output files and destinations
d. E-mail and report distribution list
e. Special form required, including online forms
f. Erro and informational messages to operaors and restart procedures
g. Special instructions such as security requirements
2.3.d USER DOCUMENTATION
consists of instructions and onformation to users who will interact with the system and includes user manuals, Help screen and tutorials
a. A system overview that cleary describes all major system features, capibalities and limitations
b. Description of source document content, preparation, processing and samples
j. Explanation of how to get help and procedures for updating the user manual
c. Overview of menu and data entry screen options, contents and processing instructions
d. Examples of reports that are produces regularly or available at the user's request including samples
e. Security and audit trail informations
f. Explanation of reponsibility for specific input, output or processing requirements
g. Procedures for requestiong changes ad reporting problems
h. Examples of exceptions and erro situations
i. Frequently asked questions (FAQs)
TOPIC 5.3
SYSTEM IMPLEMENTATION
3.1 System implementation
involves applications development, testing ,documentation, training, data conversion, system changover and post-implementation evaluation of the results
3.2 System installation & evaluation
new system is ready to go to work
3.2.1 Prepair a separate operational and test environment
a separate test invironment to maintain system security and integrity and protect the operational environment
3.2.2 Provide training for users, manager and IT staff
3.2.2.c. Webinars, Podcasts and Tutorials
3.2.2.d. Outside Training Resources
3.2.2.b. Vendor Training
3.2.2.e. Training tips
3.2.2.a. Training plan
3.2.2.f. Interactive Training
3.2.5 Present a final report to management
Planned modifications and enchancements to the system that have been identified
Recap of all systems development costa and schedules
Final versions of all system documentation
Comparison of actual costs and schedules to the original estimates
Post-implementation evaluations, if it has been performed
3.2.3 Perform data conversion and sytem changeover
existing data is loaded into the new system(Data Conversion)
3.2.3 System changeover
3.2.3.b. Parallel Operation
easier to verify new system is working properly
3.2.3.c. Pilot Operation
combination parallel and direct cutover
3.2.3.a. Direct Cutover
involves more risk
3.2.3.d. Phased Operation
risk of erro is limited to the implemented module only
3.2.4 Carry out post-implementation evaluation of the system
Prepair a post-implementation evaluation
Deliver a final report to management
TOPIC 5.4
SYSTEM SUPPORT & SECURITY
5.4.1 System Support & Security Phase
system performance
security requirements
user expectations
5.4.2 User Support
5.4.3 User Training
5.4.4 Help Desks
5.4.5 Types of Maintenance
adapting the system to changing requirements and making the system operate more efficiently
Changing prorams, procedures or documentation to ensure correct system performance
5.4.6 System Maintenance Tools
5.4.7 System Security
protecting the system from theft, unauthorized access and harm
5.4.8 Backup and Recovery
5.4.8.a Backup
copying data at prescribed intervals
5.4.8.b Recovery
restoring the data and restarting system after an interruption