Skip to content

Latest commit

 

History

History
108 lines (68 loc) · 5.11 KB

LearningOutcomes.md

File metadata and controls

108 lines (68 loc) · 5.11 KB
Raw

Learning Outcomes

After studying this code and completing the corresponding exercises, you should be able to,

  1. Utilize User Stories [LO-UserStories]
  2. Utilize use cases [LO-UseCases]
  3. Use Non Functional Requirements [LO-NFR]
  4. Use Polymorphism [LO-Polymorphism]
  5. Use abstract classes/methods [LO-Abstract]
  6. Follow Liskov Substitution Principle [LO-LSP]
  7. Use Java-FX for GUI programming [LO-JavaFx]
  8. Use Dependency Injection [LO-DI]

Utilize User Stories [LO-UserStories]

Exercise: Add more user stories

  • Assume you are planing to expand the functionality of the AddressBook (but keep it as a CLI application). What other user stories do you think AddressBook should support? Add those user stories to the DeveloperGuide.md.

Utilize use cases [LO-UseCases]

Exercise: Add an 'Edit tag' use case

  • Add a use case to the DeveloperGuide.md to cover the case of editing an existing tag.
    e.g. change tag friends to buddies
    Assume that AddressBook confirms the change with the user before carrying out the operation.

Use Non Functional Requirements [LO-NFR]

Exercise: Add more NFRs

  • Add some more NFRs to the DeveloperGuide.md

Use Polymorphism [LO-Polymorphism]

Note how the Command::execute() method shows polymorphic behavior.

Exercise: Add a polymorphic isMutating method

  • Add an abstract method boolean isMutating() to the Command class. This method will return true for command types that mutate the data. e.g. AddCommand
  • Currently, AddressBook data are saved to the file after every command. Take advantage of the the new method you added to limit file saving to only for command types that mutate data.
    i.e. add command should always save the data while list command should never save data to the file.

Note: There may be better ways to limit file saving to commands that mutate data. The above approach, while not optimal, will give you chance to implement a polymorphic behavior.

Use abstract classes/methods [LO-Abstract]

Covered by [LO-Polymorphism]

Follow Liskov Substitution Principle [LO-LSP]

Exercise: Add an exception to an overridden method

  • Add a throws Exception clause to the AddCommand::execute method. Notice how Java compiler will not allow it, unless you add the same throws clause to the parent class method. This is because if a child class throws an exception that is not specified by the Parent's contract, the child class is no longer substitutable in place of the parent class.
  • Also note that while in the above example the compiler enforces LSP, there are other situations where it is up to the programmer to enforce it. For example, if the method in the parent class works for null input, the overridden method in the child class should not reject null inputs. This will not be enforced by the compiler.

Use Java-FX for GUI programming [LO-JavaFx]

Resources

Exercise: Add class-level members

  • If you are new to JavaFX, follow Marco's tutorial given above.
  • Do some enhancements to the AddressBook GUI. e.g. add an application icon, change size/style

Use Dependency Injection [LO-DI]

Exercise: Facilitate injecting a StorageStub

  • Note how Logic class depends on the StorageFile class. This means when testing the Logic class, our test cases executes the StorageFile class as well. What if we want to test the Logic class without getting the StorageFile class involved?
  • Now, change the implementation as follows so that we can inject a StorageStub when testing the Logic class.
  • Implement the StorageStub to ignore calls to the save method. Update the LogicTest to work with the StorageStub instead of the actual StorageFile object.