kylemcmullin / cs3450-group7 Goto Github PK

Generic issue for system's Frontend UI

Parent - #17
Tool stack description and setup procedure

one of two prototypes for the purpose of improving the understanding of two or three high-priority features.

#9 Use case for account look from employee perspective. Includes perspectives from cashier, barista, and manager.

Create the initial Android Studio Project and push it up for everybody to duplicate!

Parent - #10

Parent - #51
Updated for sprint if needed

Master ticket for Project Plan documentation

Parent - #3
Policies, procedures, or tools for communication

#9 Use case for buying drink on app, barista makes, gives order to customer

#9 Use case of a customer walking in to purchase a drink

Parent - #17
Build instructions

Parent - #3
A summary of the project being built

#9 Use case of barista receiving, making and distributing drinks. Takes inventory out of stock.

Parent - #51
Updated for sprint if needed

Parent - #17
An explanation of the organization and name scheme for the workspace

Parent - #10
Introduction and Context

8 use case diagrams

Parent - #10

Parent - #3
Risky analysis

Parent - #17
System testing instructions

Parent - #17
Unit testing instructions

Parent #50
We need to define a color basis for material design since all our components will use the basic configs we setup for material design

Jetpack Compose Library integrated with Material Design 3.
https://developer.android.com/jetpack/androidx/releases/compose-material3

Child of #43
Would like to use the project structure from CS 3200, section 3.1 "Better Project Setup"
Basic layout folder structure for android studio

DansFrappesRaps
    utils (package)
        Database use files
    ui (package)
        components(package)
            All components
        navigation(package)
            Routes
            RootNavigation
        screens(package)
            Login
            Cart
            Profile
            Menu
            Item
            Manage
            Loading
        theme(package)
        App.kt(Kotlin file)

link to #49

Parent - #10
Duplicate of #9

Class, Activity, and Use Case diagrams for sprint 2

#9 Employee side of payroll. Enter hours and receive paycheck.

Parent - #3
A description of the overall software development process

Parent - #50
Master ticket for figma screen designs, can be split into subtasks

Parent - #51
Use Case Diagrams that document the actors and their goals

one of two prototypes for the purpose of improving the understanding of two or three high-priority features.

Project milestone completion with Milestone_1 git tag

#9 Use case on how payroll will happen

Master ticket for the README.md

Parent - #10

Master ticket for Requirements Definition

We will need a persisting Scaffold component to manage our always available top bar with the drawer to access user profile
make a composable in the "components" folder for this, using the material design colors
Settings
Hours (Employees only)
Pay (Manager only)
Inventory (Manager only)
Adjust Menu (Manager only) [maybe not needed?]
Manage Users (Manager only)

Signout

Parent - #55
Class Diagram that document the classes of object in the system and their relationships

Parent - #17

#9 Customers view of app

Revisions of README, Project Plan, and Requirements Definition for this sprint

Parent - #51
Updated for sprint if needed

#9 Use case for inventory tracking and purchasing

Parent - #10

Parent - #3
A description of team organization