The Object-Oriented Paradigm

2. The Object-Oriented Paradigm#

Legend

  • Here - found in the module

  • Moved - found in a different module

  • Implicit - covered by the process of completing this or a different module

  • Coming Soon - to be provided at a later date

  • Not Planned - not covered in this book

2.1. Understanding OOP#

Apply the key features of an object-oriented programming (OOP) language

Including

objects
classes
encapsulation
abstraction
inheritance
generalisation
polymorphism
Compare procedural programming with OOP

Implicitly covered by completing the module. Object oriented programming is complementary to procedural programming, not exclusive.

Use data flow diagrams, structure charts and class diagrams to represent a system
Data flow diagrams

Coming at a later date.

Structure charts
Class diagrams

Coming at a later date.

Describe the process of design used to develop code in an OOP language

Including

task definition

Coming at a later date.

top-down and bottom-up

Coming at a later date.

facade pattern

Coming at a later date.

agility

Coming at a later date.

Assess the effectiveness of programming code developed to implement an algorithm

Covered in Algorithms and Code Design.

Investigate how OOP languages handle message-passing between objects

Coming at a later date.

Explain code optimisation in software engineering

Coming at a later date.

Outline the features of OOP that support collaborative code development

Including

consistency

Coming at a later date.

code commenting

Coming at a later date.

version control

Coming at a later date.

feedback

Coming at a later date.

2.2. Programming In OOP#

Design and implement computer programs involving branching, iteration and functions in an OOP language for an identified need or opportunity

Implicitly covered by completing the module.

Implement and modify OOP programming code

Implicitly covered by completing the module.

Including

clear and uncluttered mainline

Coming at a later date.

one logical task per subroutine

Coming at a later date.

use of stubs

Coming at a later date.

use of control structures and data structures

Coming at a later date.

ease of maintenance

Coming at a later date.

version control

Coming at a later date.

regular backup

Coming at a later date.

Apply methodologies to test and evaluate code

Including

unit, subsystem and system testing

Coming at a later date.

black, white and grey box testing

Coming at a later date.

quality assurance

Coming at a later date.