System Analysis and Design

BAem 414
Programming, Testing,
Implementation & Documentation
 Coding
 Programming Environments
◦ Examples of commonly used programming languages
 Visual Basic, Python, and Java
 Web-centric languages - HTML/XML, Java, and Swift
◦ Integrated development environment (IDE) makes it
easier to program interactive software products
 Generating Code
◦ Application generators and other CASE tools produce code
directly from program design specifications
◦ Some commercial applications can generate editable code

2
 Testing The System
 Each program is tested to ensure that it functions
correctly
◦ Program is compiled using a CASE tool or language
compiler, which helps detect syntax errors
◦ Desk checking helps spot logic errors
◦ Organizations require a structured walkthrough or code
review
 Groups of three to five IT staff members participate
 A design walkthrough is held to review the interface along
with people who will work with the new system and ensure that
all necessary features have been included

3
 Testing The System (Cont. 1)

• Unit testing
• Testing of an individual
program or module
• Aims to identify and eliminate:
• Execution errors
• Logic errors
• Test data should contain both
accurate and erroneous data

4
 Testing The System (Cont. 2)

• Stub testing is required

• The programmer:
• Simulates each program outcome or result
• Displays a message to indicate whether the program has executed
successfully
• A test plan is created during the systems design phase
• Contains details regarding testing procedures

• Integration Testing
• Testing two or more programs that depend on each other to make sure
that the programs work together properly
5
 Testing The System (Cont. 3)

• System Testing (Acceptance Tests)

• Objectives
• Perform a final test of all programs
• Verify that the system will handle all data properly
• Ensure that the IT staff has the documentation and instructions
needed to operate the system properly
• Demonstrate that users can interact with the system successfully
• Verify that all system components are integrated properly
• Confirm that the information system can handle predicted volumes
of data in a timely and efficient manner
6
 Documentation

 Program Documentation
◦ Describes the inputs, outputs, and processing logic for all
program modules
◦ Process starts in the systems analysis phase and continues
during systems implementation
◦ Overall documentation is prepared early in the SDLC
◦ Defect tracking software or bug tracking software
 Used to document and track program defects, code changes,
and patches

7
 Documentation (Cont. 1)

• System Documentation
• Describes the system’s functions and how they are implemented

• Operations Documentation
• Contains the information needed for processing and distributing online
and printed output
• User Documentation
• Consists of instructions and information for users who will interact with
the system

8
 Documentation (Cont. 2)

• Online Documentation
• Provides immediate help when users have questions or encounter
problems

9
 Documentation (Cont. 3)

A sample page from a user

manual. The instructions
explain how to add a new
task to the system.

10
 Management Approval

 After system testing is complete, the results are

presented to the management
◦ Test results should be described
◦ Status of all required documentation should be
updated
◦ Input from users who participated in system testing
should be summarized
◦ Detailed time schedules, cost estimates, and staffing
requirements for making the system fully operational
should be provided

11
 System Installation and Evaluation

 Prepare a separate operational and test environment

 Provide training for users, managers, and IT staff
 Perform data conversion and system changeover
 Carry out a post-implementation evaluation of the
system
 Present a final report to management

12
 Operational and Test Environments

 Operational or production environment

◦ Environment for the actual system operation
 Test environment
◦ Environment that analysts and programmers use to
develop and maintain programs
◦ A separate test environment is necessary to maintain
system security and integrity and protect the
operational environment

13
Operational and Test Environments
(Cont.)

The test environment versus the operational environment.

Notice that access to the test environment is limited to IT
staff, while the operational environment is restricted to
users.
14
 Training

 Training Plan
◦ Identify who should receive training and what training is
required
 Organization should be observed carefully to determine how the
system will support business operations, and who will be involved
or affected
◦ Main groups for training
 Users
 Managers
 IT staff

15
 Training (Cont. 1)

Examples of training topics for

three different groups. Users,
managers, and IT staff members
have different training needs.

16
 Training (Cont. 2)

• Vendor Training
• Required if the system includes the purchase of hardware or software
• Scope is limited to a standard version of the vendor’s software or hardware

• Webinars, Podcasts, and Tutorials

• Web-based training options

• Outside Training
• Viable alternative if vendor training is not practical

17
 Training (Cont. 3)

• 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
• Rely on previous trainees

• Interactive Training
• Effective training is interactive, self-paced, and multimedia-based

18
 Training (Cont. 4)

• Online training
• Effective when it is more realistic
• Sophisticated training systems offer interactive sessions
• Training material should include a reference section that summarizes
all options and commands, lists all possible error messages, and what
actions the user should take when a problem arises
• A full-scale test, or simulation must be conducted after the training is
complete

19
 Data Conversion

 Process in which existing data is loaded on to a new

system
 Data Conversion Strategies
◦ Automate the data conversion process if possible
◦ Old systems may be able to export data in ASCII or ODBC
(Open Database Connectivity) formats
 ODBC drivers are a form of middleware
◦ If a standard format is not available, develop a program
to extract the data and convert it to an acceptable
format
20
 Data Conversion (Cont.)

• Data Conversion Security and Controls

• Maintain strict input controls during the conversion
process
• Ensure that all system control measures are in place
and operational to protect data from unauthorized
access and to help prevent erroneous input
• Ensure that error-free data is fed into the new system

21
 Summary

• Programmers perform desk checking, code review, and unit

testing tasks during application development
• In addition to system documentation, analysts and technical
writers also prepare operations documentation and user
documentation
• During the installation process, an operational environment
for the new information system is established separate from
the test environment

22
 Q/A

Thanks