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
• 5.2 Testing In A Project
• 5.3 System Implementation
• 5.4 System Support & Security
5.1 SYSTEM DEVELOPMENT
3 System Development Tools
Modeling
Prototyping
CASE Tools
Also called computer-aided software engineering, is a technique that uses powerful software,called CASE tools ,to help systems analyst develop and maintain information system.
Prototyping tests system concepts and provide an opportunity to examine input,output and user interface before final decisions are made
Modeling produces a graphical representation of concept or process that system developers can analyze,test and modify.
Modeling Used to
describe and simplify an information system:
Object model
Network model
2.Data model
Process model
1.Business model or Requirements model
Coding Process
Working from a specific design, a programmer uses a programming language to transform program logic into code statement.
2 TYPES:
1.Programming Environment
To simplify the integration of system components and reduce code development time ,many programmers use an integrated development environment (IDE).
IBM WebSphere and Microsoft .NET are popular
IDEs.
Generating Code
Some commercial applications can generate editable program code directly from macros,keystroke or mouse actions.
5.2 TESTING IN A PROJECT
3 Types Of Software Testing
Unit testing
Integration testing
System testing
All processing options and outputs are verified by users and the IT project development team to ensure that the system functions correctly.
Regardless of how the system was developed, system testing has the following major:
Perform a final test of all programs
Verify that the system will handle all input data
properly, both valid and invalid
Ensure that the IT staff has the documentation and instructions needed to operate the system properly and that backup and restart capabilities of the system are adequate
1 more item...
Testing two or more programs that depend on each other is called integration testing ,or link testing.
Systems analysts usually develop the data they
use in integration testing.
The testing of an individual program or module is
called unit testing.
During testing, programmers can use software tools to determine the location and potential causes of program errors.
4 Documentation
system documentation
System documentation describes the system’s
functions and how they are implemented
System documentation includes data dictionary entries,data flow diagrams,object models,screen layout,source documents,and the systems request that initiated the project.
operations documentation
Operations documentation contains all the information needed for processing and distributing online and printed output.
7 Typical operations documentation includes the
following information:
Program, systems analyst, programmer, and
system identification
Scheduling information for printed output, such
as report run frequency and deadlines
Input files and where they originate; and output
files and destinations
E-mail and report distribution lists
1 more item...
program documentation
Program documentation describes the inputs,output and processing logic for all program modules.
user documentation
User documentation consists of instructions and information to users who will interact with the system and includes user manuals,help screens and tutorials.
10 User documentation includes the following:
1.A system overview that clearly describes all major
system features, capabilities, and limitations
Description of source document content,
preparation, processing, and samples
Overview of menu and data entry screen options,
contents, and processing instructions
Examples of reports that are produced regularly or available at the user's request ,including samples
1 more item...
5.3 SYSTEM IMPLEMENTATION
5 Managing systems implementation
training
data conversion
documentation
system changeover
application development
post-implementation
evaluation of the results.
2.testing
System Installation & Evaluation
5 steps in systems implementation:
1.Prepare a separate operational and 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
Provide training for users, managers, and IT
staff
6 TYPES OF TRAINIING:
Webinars, Podcasts, and Tutorials
Outside Training Resources
Vendor Training
Training Tips
Training plan
Interactive Training
– Perform data conversion and system
changeover
During data conversion, existing data is loaded
into the new system.
System changeover is the process of putting the new information system online and retiring the old system.
4 changeover methods:
direct cutover
parallel operation
1 more item...
Carry out post-implementation evaluation of
the system
A post-implementation evaluation should examine all aspects of the development effort and the end product- the developed information system.
2 additional tasks:
Present a final report to management