Matlab forces very little on us in the way of requirements. This is both good and bad. To the good, it means that we have a lot of freedom to make the implementation match our particular need. It also means that we do not have to devote a lot of time toward learning an intricate set of requirements, nor do we have to devote effort toward implementing the requirements with our code. To the bad, it means we must blaze our own trail without the benefit of requirements to keep us on track. Loose requirements provide enough rope to hang ourselves. It is too easy to weave a path that is difficult to maintain. The paper learns how to meet requirements in a way that supports the needs of the group of eight. This helps keep MATLAB object-oriented programming on the straight and narrow.

Chapter Contents:

• 2.1 Variables, Types, Classes, and Objects
• 2.2 What Is a MATLAB Class?
• 2.2.1 Example: Class Requirements
• 2.2.1.1 Class Directory
• 2.2.1.2 Constructor
• 2.2.1.3 The Test Drive
• 2.3 Summary
• 2.4 Independent Investigations

Inspec keywords: object-oriented programming

Other keywords: object-oriented programming; Matlab requirement

Subjects: Object-oriented programming