CSC/ECE 517 Spring 2023 - E2337. Reimplement node hierarchy

From Expertiza_Wiki
Revision as of 23:47, 5 April 2023 by Ashon (talk | contribs) (Created page with "==Introduction== Packages of information are distributed based on the context that they are delivered. For courses, information and functionalities are packaged into Course no...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Introduction

Packages of information are distributed based on the context that they are delivered. For courses, information and functionalities are packaged into Course nodes and team information is packaged into Team nodes. These nodes are supplemented by the base node class in order to inherit basic functionality/attributes such as the type of node, the parent id, identifying whether the node is a leaf or not, etc. This hierarchical structure allows for code reuse and custom implementations to exist alongside default implementations in order to keep functionalities modular and isolated, minimizing the risk of breakage.

Problem Statement

Testing --> test plan Class Hierarchy Design pattern