Authors

Goudham Suresh, Alan Robinson, Erin Heath, Hazel Fulton, Robert Ranson, Steven Ferguson

Table of Contents

• Project Description
• App Functionality
• Architecture
  • Benefits & Challenges
  • Class Diagrams
  • Retrospective
    • Actions Taken

Project Purpose & Description

• Purpose
  • Allows customers to purchase Derek Somerville Merch.
• Description
  • A standalone GUI Java application for SomervilleSwag, founded by Global Influencer Derek Somerville. Having won many awards from his time working at J.P Morgan, he decided to pursue the Instagram Influencer Lifestyle and founded his own merch store "SomervilleSwag"

App Functionality

• Sign Up
• Log In
• Browse Products
• Add & Remove Products To/From Cart
• Purchase Somerville Goodies

Architecture

• Data
  • SQLite Database Used
• Engine
  • Design Patterns Used - Singleton, State, Adapter, Builder
• Display
  • JavaX.Swing (JFrames/JPanels)
  • Logging Information Exported to File

Benefits & Challenges

• Benefits

  1. SQLite Database is incredibly beneficial as it is a flat-file relational database using SQL. It's incredibly lightweight and blazingly fast, providing speed as well as reliability. Therefore, perfect for our small GUI application that will not store large amounts of data.

  2. • Mixture of Singleton/State/Adapter patterns have been used. This adheres to clean coding standards and principles while also making this application maintainable for any future features / bug fixes.

     • Singletons allow us to ensure only 1 instance of an object is available throughout the entire program, such as the LoggingService.

     • States allow us to remove lots of conditional logic from the main engine and distribute through classes and methods.

     • Builder classes improve the readability of code through providing clear, easy to read methods when instantiating/building new objects.

     • Adapters are used here to stub out classes in order to achieve more test coverage and enforce the Single Responsibility principle, in which functions should only perform one action.

  3. JFrames/JPanels will be used for the display, allowing users to interact with the application with ease.

• Challenges

  1. Implementing State Design Patterns is quite difficult when dealing with asynchronous event listeners of the JFrames/JPanels.

  2. Unit Testing of the UI is virtually impossible through only common libraries of JUnit5 and Mockito. To work around this, we are only unit testing the core business logic.

  3. Displaying product images within the UI and using the built-in Intellij Swing Designer for the UI is unforgiving as our team has no prior experience using Intellij to develop using JFrames.

Class Diagram

Retrospective

We held our retrospective on MetroRetro using the Sailboat method. As a direct result of this, actions were taken to improve our teams workflow and processes.

Actions Taken

1. Project has gotten larger and increased in complexity with group members working on different aspects of the program, in order for all group members to reacquaint themselves with the whole project. A meeting will be scheduled to walk through the project in its entirety, focusing on all classes and the dataflow. - Owned By Goudham Suresh
2. All group members have time constraints, whether it be real life, work commitments or other University coursework / reports. To boost productivity and promote more collaboration between group members, regular meetings will be scheduled at times agreed upon by everyone. Attendance will be optional but allows for group members to collaborate at specific times and provide more structure for working on the group project. - Owned By Robert Ranson
3. All skill levels are present in our group, varying from beginner/intermediate to experienced/advanced. Pair programming sessions are incredibly valuable as they provide the lesser experienced person with more knowledge while also reinforcing concepts/knowledge for the more experienced programmer. More pair programming sessions will be scheduled and advocated for within the group. A Microsoft Teams call should always be up if someone is working on the project, encouraging other group members to join in and pick up new concepts. - Owned By Alan Robinson