4 Think about the following regarding deployment: § Could someone download the latest version from the GitHub release and know how to run it? § Consider using a JMenuBar, JPopupMenu § Consider making your JAR file executable (see next) Deployment
6 § Could someone know how to use it? § Where to start? § What the project is about? § Take advantage of your README.md (beautify it) @see https://docs.github.com/en/repositories/ Usability
7 § Stories should be INVEST. § Do not forget Estimation Points § Tasks are the technical ones - stories are mostly features. § It is OK to have some bug fixing (technical debt payment), knowledge acquisition, or IT Requirements | INVEST
9 § Do NOT be afraid of showing your class diagram! § Use colors for the newly added classes) § All classes must be connected. § Any opportunity for an Abstract Class or an Interface? Software Design | Blueprint
10 § “Any fool can write code that a computer can understand. Good programmers write code that humans can understand”. -Martin Fowler Coding Take care of Clean Coding (Readability) And Clean Design
11 What are you testing? Consider the following: § Sockets and Services (network connection failure) § User Interface (apply Robot Class for instance) § Features (algorithms, e.g. , moving disk in Hanoi) Test Cases
16 Let’s Work • User Stories Report From Taiga • Self-Evaluation. Does it Look Good? • What can be improved? • Full Class Diagram • Self-Evaluation. Does it Look Good? • What can be improved?
Winter 2023 Copyright. These slides can only be used as study material for the class CSC308 at Cal Poly. They cannot be distributed or used for another purpose.