Attendees

• Precious
• Dinma
• Onami
• Temi
• Divine
• Kulnoor

Project Timeline and Deliverables

• Project part 3 is due in approximately 10 days
• Deliverables include:
  • Functional code base with implementation of user stories
  • Documentation with Javadocs
  • Test cases (both functionality and UI tests)
  • UML class diagram of all code
  • Sprint documentation in GitHub
  • Record of assigned user stories

Task Division

• Team split the user stories from the halfway checkpoint into four groups per person
• Tasks organized to minimize dependencies between team members
• Groupings organized around feature areas:
  • divinewi: Entrant discover and join functionality
  • kulnoor: Notifications and preferences
  • takindel: Profile and history
  • ajilore: Organizer event creation/editing
  • onamiyeo: Sending notifications and announcements
  • obiokoye: Admin functions (browsing profiles, removing users)

Development Workflow

• Using GitHub with multiple branches
  • Main branch for production-ready code
  • Development branch for testing before merging to main
  • Individual branches for each team member
• Workflow process:
  • Complete work in individual branches
  • Create pull request to dev branch when task is complete
  • At least one other team member reviews the code
  • After approval, merge to dev branch
  • Test in dev branch
  • When stable, merge to main branch
• Using iterations as sprints to track weekly progress

Base Application Structure

• Created basic fragments for key pages:
  • Event fragment (landing page)
  • Profile fragment (user information)
  • Inbox fragment (notifications)
  • History fragment (history/activity)
• Added navigation resource file to connect between pages
• Implementing bottom navigation with buttons for each section

UI Implementation Approach

• Focus on functionality first, then improve UI appearance later
• Using Figma's developer mode to help with UI code generation
• Started adding icons to resources folder

Immediate Next Steps

• Set up the base application structure with navigation
• Each team member needs to:
  • Pull the latest code to ensure everyone has the same base
  • Assign themselves to specific tasks in GitHub
  • Tag tasks with appropriate iteration number (2 or 3)

Action Items

• All team members to pull latest code from GitHub
• All team members to assign themselves to their chosen tasks in GitHub
• All team members to tag tasks with appropriate iteration numbers
• Finish setting up base application with navigation between home, inbox, and profile
• Each team member to document their code and provide Javadoc
• Each team member to provide test cases for their functionality
• Create UML class diagram when code is more developed