CSC/ECE 517 Spring 2023 - E2337. Reimplement node hierarchy: Difference between revisions
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
Testing --> test plan | Testing --> test plan | ||
===Class Hierarchy=== | ===Class Hierarchy=== | ||
[[File:UML_Diagram_nodes.jpg]] | [[File:UML_Diagram_nodes.jpg|500px|]] | ||
Design pattern | Design pattern | ||
Revision as of 00:07, 6 April 2023
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