I wrote up an answer and apparently forgot to post it! Sigh.
From an academic standpoint, I believe what your teacher is getting at is to show how you use some (preferably all) of those corollaries. I believe what I would do is simply write notes to show where you apply them. For example, if you use a design pattern, write up a little note that explains the pattern and why you used it. Create a class diagram, and explain why you used inheritance in it. Talk about cohesion and coupling. That sort of thing.
<Corrolories are things that follow from them, but are not necessarily essential.
To give one example of this: a "design pattern" is a way of doing some particular thing that has evolved over time as a best practice. An important point about such a pattern is that, since it evolved over time, it was not the first solution that was tried; rather, it's a result of incremental trial and error. Its use is non-essential, since if it were essential, none of the designs leading up to it would work, and there is ample evidence to the contrary. However, it is the most efficient way to accomplish the problem it is designed to address.
A good simple example of a pattern is the Singleton pattern. This pattern is a way of having one and only one instance of a class in existence in a client domain. The bare bones would be something like this (this is pseudocode):
class mySingleton
private theInstance : mySingleton
public mySingleton()
[if theInstance is null then
theInstance = New mySingleton]
[return theInstance]
public getInstance(): mySingleton
[return theInstance]
end class
All we're doing is, in the class's constructor, checking to see if an instance of mySingleton already exists, and creating one if it doesn't. Of course, you would add other methods and properties to accomplish your work. A good example of a simple Singleton application is an incrementor for, say, new account numbers. Any client needing a new account number has to make sure that no other client has taken that number. So, they all create an instance of your singleton, and they all have a pointer to the same object. You have a property called NextNumber that increments a private variable and returns the result.
So, in your project, you might use something like this, or another design pattern, and then document the fact that you used it and why, explaining that it's an example of the "standardization corollary."
By the way. I once had the very great pleasure of running into the poet Maya Angelou in a hotel lobby and speaking with her for two or three hours. A young woman who was with me at the time mentioned her dislike of a professor of hers. Maya responded "Now ....., a brilliant student can make a mediocre professor look brilliant, so it is your job to make that professor look brilliant." Very good advice, I would say.
HTH
Bob
