15th slide: Another type of programming language is the Object-Oriented

Languages.
- Central to achieving the benefits of the object-oriented approach, is
developing software using an object-oriented programming (OOP)
language such as C++ or Java.
- Many examples of OOP languages exist that offer various features…
(dagdagan pa further explanation, ang panget kasi pag eto last
sentence, parang putol yung thought.) Next slide please.

16th slide: However, a computer language is said to be object-oriented only if

it supports the following:

Object - Objects are real-world phenomena that possess two

characteristics: They have state and they have
behavior.
- An automobile is an example of object. It has state
(brand, color, horsepower) and behavior (how fast
it starts when you turn the engine on, its changing
speed, the opening of its window, and how fast it
stops when you step on the breaks).
- Software objects are conceptually similar to real-
world objects in such senses that:
1. The object’s state is represented by stored
attributes (variables or fields).
2. Object behavior is displayed through
methods, which are functions or procedures
that are performed on or by the object to
change the state of its attributes.
Next slide please.
17th slide: - A class is a blueprint that defines the attributes and
Class and the methods common to all objects of a certain
Instance type.
- An instance is a single occurrence of an object
within a class.
 - For example, Inventory is a class: refrigerator,
washing machine and dryer are instances of the
inventory class. Next slide please.
18th slide: - Encapsulation is the act of placing data and
Encapsulation methods in the same class and thus restricting
access to the object’s components.
- In this way, the internal representation of an object
is hidden from outside view.
- This protects object integrity by preventing users
from corrupting its internal data by accidentally or
intentionally setting it to an invalid state.
Next slide please.
th
19 slide: - Inheritance basically means na iniinherit ng bawat
Inheritance object instance yung attributes and methods of
each class to which it belongs.
th
20 slide: - Polymorphism allows multiple and different objects
Polymorphism to respond to the same message.
- Each object may contain the same method name,
but act upon the method differently because the
programming code behind it is different in each
class.
st
21 slide:
- An example of polymorphism is the function of
printing documents. Every object that can be
printed (text, graphics, or spreadsheet) must know
how to print itself.
- The “Print” message sent to these different objects
is the same, but the implementation to accomplish
the print function within the object is different for
each class because their programming code varies.
Next slide please.
nd
22 slide: We now move forward to programming the system, still under the
6th phase of the SDLC. Regardless of the programming language used, modern
programs should follow a modular approach. (dagdagan pa further
explanation). Next slide please.
23rd slide: In modular approach, small programs are produced to perform
narrowly defined tasks. On the next slides we will go over the benefits
associated with modular programming. Next slide please.
24th slide: Next pa po.
25th slide: So, the first benefit is the program efficiency. Nagiging efficient siya
kasi under modular approach pwedeng i-code at i-test independently yung
mga modules, which of course reduces programming time. A firm can assign
several programmers to a single system, working in parallel, these
programmers can each design a few modules. Afterwards, these modules
may now be assembled into the completed system. Next slide please.
26th slide: The second benefit of modular programming is the maintenance
efficiency. Small modules are much easier to analyze and change, which
reduces the start-up time during program maintenance. Extensive changes
can be divided to several programmers simultaneously to shorten
maintenance time. Next slide please.
27th slide: The last benefit would be control. By keeping modules small, they
are less likely to contain material errors of fraudulent logic. Since each module
is independent of the others, errors are contained within the module only.
28th slide: Naturally, bago pa maimplement yung program modules, they must
be thoroughly tested first. Some proven concepts are the testing
methodology, testing offline before deploying online, and test data. Yung
mga concept na ito should be followed by the system developers and must
be considered by auditors in conducting their audit.
29th slide: The first concept is the testing methodology. A program-testing
procedure involves the creation of hypothetical master files and transaction
files that are processed by the modules being tested. The results of the tests
are then compared against predetermined results to identify programming
and logic errors. Next slide please.
30th slide: The process of testing methodology itself has structured steps to
follow.
For instance, in testing the logic of the accounts receivable update module
illustrated in this figure, the programmer might create an accounts receivable
master file record for John Smith with a current balance of $1,000 and a sales
order transaction record for $100. Before performing the update test, the
programmer concludes that a new balance of $1,100 should be created.
So, to verify the module’s internal logic, the programmer compares the actual
results obtained from the run with the predetermined results. This is an
example of a simple program test. Actual testing would be extensive and
would involve many transactions that test all aspects of the module’s logic.
Next slide please.

31st slide: The next concept is the Testing Offline before Deploying Online.
- The first point that is critical in testing is to never underestimate the
principle of testing offline before deploying a system online.
- Implementing a system without testing offline is an invitation to
disaster.
- For instance, may isang e-commerce firm that went out of business
because nag-implement sila ng system online w/o testing it first.
What happened was, it accidentally left a vulnerable Web server
open to attacks from crackers. So, the cracker stole thousands of
credit card numbers and eventually, the online business failed. As I
 mentioned, we should never underestimate this concept. Next slide
please.
32nd slide: For the last concept we have the Test Data.
- Creating a meaningful test data is an extremely time-consuming
aspect of program testing. But this activity can provide future
benefits.
- Application auditing sometimes involves program testing. So, to
facilitate future testing, test data prepared during the
implementation phase should be retained for reuse. This test data
will give the auditor a frame of reference for designing and
evaluating future audit tests.
- For example, if yung program never pa nag-undergo ng maintenance
changes since its original implementation, the test results from the
audit should be identical to the original test results. Having a basis
for comparison, the auditor can verify the integrity of the program
code.
- However, if changes have occurred in the program, the original test
data can provide evidence regarding these changes. The auditor can
just focus his/her attention upon those areas.
- Maintaining test data and its results is also a significant control
feature, as future systems development can use the test data and
results to test future changes to the application software.