Please enable JavaScript.
Coggle requires JavaScript to display documents.
STORE, Encapsulation, Inheritance, Collections, Using non-concrete methods…
STORE
Model
-
-
-
It makes sense for each of these files to be in the model package. Each set up a type of object that is used to "model" the objects used In the program. Addituinally, in the MVC paradigm it makes sense that the objects would be defined within the model package. My own program looks almost identical to the given Model package.
-
-
*not all classes/files displayed in map for clarity but all connections between packages and concepts still made
View
-
-
-
polymorphism used because program does not know whether it will use the console window or JOptionPane until user specifies.
Controller
-
Store Factory
ProductMap-- interesting that the key is an enum and the value is a list. Very good illustration of combining multiple OOP and Java concepts
-
Controller pulls together everything in the view and model to create the cohesive program. This is especially useful because it shows how the Controller package can be left untouched while the Model or View is changed and the program can still run without throwing errors
Encapsulation
-
-
-
class variables are left private in program and methods are used to allow for interactions between files
-
-
-
-
Overloading
-
Many of the classes within Model overload the constructors to provide multiple ways for the user to create the same objects
-
-
-
-