Architecture

Languages/frameworks/libraries/services/APIs:

What package/build manager will you use:

List what each person will work on:

---

1. Deployment How will you deploy? Which hosting provider(s)? Automation? Scripts? Explain.

2. Are you using Virtual Machines (vmware, vbox, etc) or Containers (docker) for development or deployment? Explain.

3. Is it a SPA or traditional? or mix? Explain.

4. List of URLs you will implement. Explain any search arguments in English. Link (actual hyperlink) each URL to the page it shows in your Detailed Design milestone.

• shapeshift.com/
• shapeshift.com/login
  • GET render login page
  • POST getting user from data
• shapeshift.com/signup
  • GET render sign up page
  • POST add user to data
• shapeshift.com/dashboard=id
  • GET display dashboard according to user id
• shapeshift.com/broswer
  • GET render browse page
• shapeshift.com/workout-plan=id
  • GET display workout according to plan id
  • POST add workout plan to user if they choose to with the subscribe button
• shapeshift.com/dashboard=id/my-training
  • GET render the ‘my training page’ according to user id
• shapeshift.com/dashboard=id/profile
  • GET render user profile
• shapeshift.com/dashboard=id/trainer-profile
  • GET render trainer profile
• shapeshift.com/dashboard=id/program-content
  • GET display the trainer’s plans
• shapeshift.com/dashboard=id/program-analysis
  • GET display the trainer’s plan analysis
• shapeshift.com/dashboard=id/create-program
  • GET renders create page
  • POST the new workout created

5. If implementing a REST API, document it. List all methods, parameters, and give English description of what they do.

6. The Views of your app. Embed the images from your Design Milestone. Typically, a webpage includes multiple views. For example, this webpage has a Header, Menu, and Content views (at least).

Welcome Page

Sign In Page

Sign Up Page

User Dashboard Page

User Profile Page

Trainer Profile Page

Browse Page

Trainer 'My Programs' Page

Trainer Analytics Page

Workout Plan Page

Create Program Page

User Training Page

7. The Database schema: set of tables/documents with list of attributes and their types. Describe each table and attribute in English.

1. Users - all the users of the web app
   1. userID - a user ID to identify which user is logged in
      1. VARCHAR(255) PRIMARY KEY
   2. Name - the user’s name
      1. VARCHAR(30)
   3. Email - the user’s email
      1. VARCHAR(255) NOT NULL
   4. Password - a password for the account (might try to hash it)
      1. VARCHAR(255) NOT NULL
   5. Birthday - the user’s birthday
      1. VARCHAR(10)
   6. Trainer - weather or not the user is a trainer
      1. BOOLEAN NOT NULL DEFAULT 0
2. workoutPlanEnrolled - the relationship between the ‘Users’ and WorkoutPlans
   1. user_id - user id from the Users database
      1. INT
   2. workout_course_plan_id - plan id from WorkoutPlans database
      1. INT
   3. progress - where the user is at in the plan
      1. INT DEFAULT 0
   4. Other things in the schema
      1. PRIMARY KEY (user_id, workout_course_plan_id),
      2. FOREIGN KEY (user_id) REFERENCES users(userID),
      3. FOREIGN KEY (workout_course_plan_id) REFERENCES WorkoutPlans(planID)
3. WorkoutPlans - all the workout plans available
   1. planID - the workout plan id to identify which plan it is
      1. VARCHAR(255) PRIMARY KEY
   2. authorID - the id of the user that created this plan
      1. VARCHAR(255) FOREIGN KEY (authorID) REFERENCES users(userID)
   3. Title - the name of the plan
      1. VARCHAR(30) NOT NULL
   4. Description - a little blurb to describe the plan
      1. TEXT
   5. Level - the intensity of the plan
      1. ENUM('Beginner', 'Intermediate', 'Advanced') NOT NULL
   6. Type - what kind of workout is it
      1. VARCHAR(30)
   7. Location - where the workout can be done
      1. ENUM('At-homer', 'Gym') NOT NULL
   8. Schedule - the entire workout plan
      1. JSON (more flexible then a table). Will include week, day number, workout time, equipment, and video URL

8. List of common queries you expect will be needed. Do any of then need to join tables?