Schemer - cs428TAs/w2023 GitHub Wiki

Schemer – A tool for Fiction writers

Team Members

Jacob Christensen, Emma Harrington, Drew Moss, Adam Ryan, Eric Spencer, Marcus Tracy

Status Reports

Project Description

Build a website that helps authors of Fiction novels organize their plots, characters, and settings.

Org Chart

PERT & GANTT Charts

Architecture Sheet

The above image outlines the general control flow of the products intended functionality. On the left is the portion describing the basic necessary functions of the front end, and the right side describes the overall structure of the back end. Front end/Back end communication is represented by the pointed shapes. The above image outlines the schema of our model objects in UML format. While this is primarily used to describe how things are stored in the back end, it also disambiguates the overall structure and format on both front and back end, serving as a glossary of sorts. Though this exact format won't necessarily be used in every part of the implementation, it informs us what format data is available in.

Testing & Q/A Plan

https://docs.google.com/document/d/11yjB0h8u28Fo1phL7POPVrE4A64O2WXGwI_DzLdrFPA/edit?usp=sharing

Team Roles and Responsibilities

Emma H

Front-end Engineer

Front-end development with Vue JS framework
Implementing pages of the website using components and HTML
Text-editor development - linking Keywords in the text to Bio pages UX Designer
Figma Mock-ups for the look and flow of the website
Final say on UX design decisions

Eric Spencer

Chief Architect

Final say on Software Design decisions
Coordinate between FE / BE development to make sure models are consistent
Merge and review changes on Github - handle version control
Communicate with PM about project progress and requirements
Working with BE engineers on how to store data

Marcus Tracy & Drew Moss

Back-end Engineer

Discovering the best method for saving data in the database
Database design - best representation for models
Developing back-end controllers to handle front-end requests for: ** Fetching data for a Character or Setting (entity) ** Saving changes to the text

Jake Christensen

Full-stack Engineer - Bridging FE/BE

Discovering how to send JavaScript requests to the backend
Verifying requests and responses are correct and consistent

Adam Ryan

Project Manager

Manage communication across FE / BE development
Forecast which tasks need to be done first
Coordinate with Chief architect for design
Keep team on track for MVP

Project Requirements

https://docs.google.com/document/d/1nbCtUuAhij6mwy1ZGqzFQB1Upp7zr68KqJEHFjCcw_M/edit#