AP CSA COURSE Into FOR Trimester 2

• PBL - Look for a real need, Teacher/Student need, Educational Study or Simulation, Campus Club, Campus Interest, Business Interest, Charitable Organization, etc
  • Starting Objective is to begin a code base.  Longer term vision is to  build skills for a final project in Trimester 3.   
  • IMO, it is much more interesting to work on something that has 3rd party interest and that you can ultimately acquire a sponsor.  This Trimester is to get us ready.  
  • Designs are required and must meet Teacher Approval (Brain Write, Wire Frame, Concept).   It would be great if you tried to use the GitHub Wiki to record these items.   
  • Be sure to pick something that you don't burn out on after a couple of weeks.

Teacher Project Interests

• Highlight all 10 Units from CB.
• Remake CB site to be Student Friendly, More Code, and less Video.
• The Web Site covers key topics from CB, also include PBL, should be interactive.  The visuals should teach as much as the code behind the visuals.
• FRQs could be challenges or hack-a-thon activities that would enhance TPT sessions. 

• Build data for a series of classroom needs
  • User Table and Passwords, single source for all projects to minimize duplication of data
  • Access through accounts RESTful API
• User Setting and Attributes for students
  • GitHUB ID
  • All GitHub location for user through Year (Tri 1,2,3)
  • All Slack channels through Year (Tri 1,2,3)Period through year
  • Roles for User through Year
• Association of Users to work (TODO and resolution)
  • Scrum Teams (build off my example)
  • User to Canvas assignments (lookup)
  • Canvas assignments to Tangibles
    • GitHub commits
    • Runtime
    • Ability to Comment on assignments
  • Backup of Data to JSON
  • Restore Data from JSON

• React frontend with Java Backend
• Key is to build RESTful API, database and all persistent services in Java
• Admin Web application to should be in Java, Spring, Thymeleaf
• In 20 minutes... https://www.split.io/blog/tutorial-spring-boot-react/
• How to... https://medium.com/bb-tutorials-and-thoughts/how-to-develop-and-build-react-app-with-java-backend-c1e6c5c93ae
• Intense, but from authority... https://spring.io/guides/tutorials/react-and-spring-data-rest/

• Swift project with Java Backend
• XCode IDE for Swift IPhone project
• Java and IntelliJ for Backend project
• Key is to build RESTful API, database and all persistent services in Java
• Admin Web application to mimic phone services perform maintenance should be in Java, Spring, Thymeleaf
• Getting started ... https://medium.com/@nutanbhogendrasharma/consume-rest-api-in-swiftui-ios-mobile-app-b3c5d6ecf401
• Comparing backend frameworks ... https://medium.com/comsystoreply/https-medium-com-max-comsysto-comparing-backend-frameworks-written-in-java-swift-and-go-70acd07d3a8a

Organization Sprint 0
Week 0

• Pick Teams
• Slack Channel
• Brain Writes
• Wire Frames
• Start GitHub
• README
• Scrum Board
• Running Project
• Individual Home Pages
• Journal and TPT work

• Scrum Boards and Issue for each individual (.5 to seed)
• GitHub plan and commits by each individual (.5 to seed) 
• Distraction policy in effect immediately (-1 point from seed)

AP CSA Roles FOR Trimester 2

• Two to Three TOs/OOs in class to Facilitate TPT, TT events.  Coordinating across Team TOs/OOs
• Serve as Project Owners in Agile Development, process.   Essentially acting as Sponsor of projects.
• Help in setting up and approve projects and ideas.  
• Assist in planning common or shared code across all Scrum Teams, ie User Database and APIs
• Coordination for Unit #1-#10 FRQ reviews.  Trying to make things interesting with individual challenges, engagements, hacks, kahoots, etc.  (very little lecture)

• Scrum Master.  Ensure roles are assigned.  Build Scrum Board.  
• GitHub Admin.  Setup Project in Git.  Integrate any starter code from Trimester 1.  Build policies for Fork and Pull requests.
• Primary Designer.  Primary Designer and Layout manager.  Organize Thymeleaf Enabled Templates, ensure usage of Bootstrap (minimize CSS customization per page).  Establish plan for overrides on each of the User Pages.
• Deployment Manager (RPi or AWS).  Deploy Web site.  Establish policy and frequency for updates.  Ensure site is not broken and always alive for reviews.
• Technical Officer from Scrum Team.  Works with Teacher, Classroom TOs, and BOF TO's to form TPT lessons and Tech Talk Topics for Trimester.  Also, facilitates learning of Technical Concepts within Scrum Team.

• README. You will hav a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.  Also, README will continue having  Individual quick links and Time Boxed changes per Canvas assignment.  Your project could have other *.md files to cover specific topics, however, for these kind of items you may consider WIKI.
• WIKIS.  Wikis provide a place in your repository to lay out the design and high level roadmap of your project.     WIKIS should be capture longer "stories".  Most of the presentations we had in Trimester 1 could be authored in WIKIS. Think about how wikipedia is organized.
• Issues.  Use GitHub Issues to track assignment within team, feedback from other teams, or bugs.  There is integration between Issues and Pull requests, when you want to manage you code base more effectively.
• Project Board.  Beta Project Board.   There needs to be a view into your Issues that easily identifies status.  Kanban is the Scrum Board style we used.  There are other presentations, your README should present the presentation you use and is comfortable with your team.

• What are your Scrum Board likes/challenges?  
• What are Friday/Monday Delivery likes/challenges?   
• What style will you use when start your Scrum Board
• How will you handle issues that come up on you Scrum Board?  Issues from Teacher or Crossover?
• Do you know of great examples of improvement you have observed from Twitter posts?  Scrum Team you observed?  Comment that were made on your former projects?
• What actions should we take in Tri 2 to get better at management of Issues?

• Units #2-#10, due on Weeks #2-#10 respectively
• The FRQ Unit for the week is DUE at the beginning of class on TPT day.  For instance, Unit #2 is due on Tue of Week #2.
• FRQs need to be incorporated into Web Site and be Online at each due date.  Code needs to run and a link to GitHub should be on the runtime screen.  How we grade is TBD and can change week to week.
• Grading will NOT be occur on CB website.  There is NO reason to submit these on CB.  FRQs will be reviewed through your PBL project.  "This may cause github and deploy challenges, WORK IT OUT!
• Each FRQ Unit is considered as an individuals homework.  Tuesday in class is the only time that your FRQ should take priority over your PBL.
• Student led TPT will continue, but we will have more involvement, activities and rotation.  Activities should be interactive, very little lecture.  Rotations will be graded.

• 2014 FRQ, it is really important to understand FRQ style of questions.  Their are 4 questions of 4 types, you need to know this in order to PREP effectively. Technical Officers need to look this up ASAP! This information should be discussed at BOF and then shared with teams.

Model Sprint 4, 5
Week 5

sqlite> .tables
hibernate_sequence  person              scrum_team        
sqlite> select * from scrum_team;
62|Team 1|5|7|11|15|3

• Page must use a Layout and have special customization (color pallet, background, etc)
• Picture with Mask that toggles to Picture of Choice (ie pic without mask). Perhaps ASCII art.
• Pull or show data (Web API) with information of interest
• Establish link(s) to journal and other key indicators of your work and progress on your home page (remember Tri 1 pop quiz)
• Store and Retrieve Data, ie simple comment database OR add links from previous bullet dynamically.

• Background Processes, keeping page updated
• Navbar updates (weather, stock)
• Navbar actions (search)

• “Talk is cheap. Show me the code.”
• “Most good programmers do programming not because they expect to get paid or get adulation by the public, but because it is fun to program.”
• Microsoft isn't evil; they just make really crappy operating systems.

• "git clone" makes a local repository (decentralized) from the cloud server (GitHub).   
• A .git directory contains a local database (see illustration) that keeps track of local changes, "git commit" makes a child of the original parent on the local directory.  Git commits over time are a series of SHA's.
• A .gitignore file tells .git to ignore certain files in directory tree (ie .idea)
• The "git push" command moves files from local system back to cloud server (GitHub)
• Often a merge is required as a decentralized system has many simultaneous contributors.
• Git branches and/or forks can be used to push code to  isolated locations to on the server/cloud.  This simply delays the inevitable merge, but has benefit of keeping main branch of project stable.
• Pull requests is common process used to merge code from isolated branches to main branch.

• Pull Requests and Branches.  
• An alternative to branches is Forks.
• IntelliJ Branch Creation
• IntelliJ Apply Branches
• IntelliJ and Pull Request Video

• How have you started you GitHub project?  Did you create a .gitignore to avoid committing files that don't belong in version control?  Did you make sure NO .idea files are in your GitHub repository.
• How do you manage commits to avoid problems?  
• Have you considered branching techniques with pull requests?  
• What actions will you  take this Trimester to get better at managing merge or commit problems?

• Obtain equipment (RPi or AWS).
• Git.  Setting up an environment on deployment host to synchronize changes.
• Java.  Building and running the Web Application on the deployment host.  This involves resolving any dependencies for Web Application.
• Service File.  This involves starting and keeping Java Web Application  running.
• Nginx File.  This is the Reverse Proxy configuration setup directing HTTP(S) requests to Web Application. This setup can support multiple Web Applications.
• DNS routing.  This involves having a friendly domain name to route to the server hosting the Web Application proxy.   Note, port forwarding is required when server has private IP and is behind a router.
• Certbot (certbot --ngiinx).  This is certificate setup to enable your Web Application to be secure.

• Pull from GitHub
• Rebuild Java Application
• Restart Service File

• M - Planning meeting between now and week after Tree.  Stand Up meetings (Scrum Team and BOF).  Form TPT from Student Led OO's and TOs
• Tu - Student Led TPT
• W - CCC, Design manager BOF Tech Talk 1.1
• Th - CCC, Technical Officer BOF, Tech Talk 1.2, Async Search Project
• Th & F - Conduct Scrum Master / Teacher Project Reviews
• F - CCC.  Review ticket Crossover score and TPT and score, focus on fellow BOF.  MOtD: Designers & TOs need to share their Tech Talks with the rest of the team.  Common themes should be built into Home Pages next Friday.

• see Canvas Week 1 - Project Approval

Innovation Sprint 1,2
Week 2

• M - Stand Up meetings (Scrum Team 10 minutes and BOF 10 minutes)
• Tu - See TPT schedule.  After TPT Designer BOF to instruct on layout guidelines within Scrum Team.
• W - CCC, Deployment Manager BOF, Tech Talk 2.1
• Th - CCC,  Technical Officer BOF, Tech Talk 2.. Scrum Team (Scrum Master, GitHub Admin, Deployment Manager) perform release day policy training.
• F - CCC, About Pages 1.0 Due via Deployed Server due, details on Canvas (Live reviews by Teacher, OOs, TOs

• see Canvas

1. Model , Model Part 2 is where we gather data. (Java/SQLite).  This includes Filtering and returning LIST a custom JPA query.  Like type query requires special syntax.
2. View is where we display the data (HTML/JavaScript).  This includes sending data from User to Backend.  BootStrap infused HTML, JavaScript Fetch, and dynamically building result Container.
3. Control is where we set up routes and direct traffic between Model and View.   Receiving request entity, handling success/errors and returning response entity are responsibilities of control.

• Pressing Search button and leaving search box is empty will return all the data.
• Entering a string and pressing Search button will look for partial match in database, filter is looking for result in either  name and email.  
• Result area is under Search Box.  This area is cleared between each search.

• Bootstrap starter template
• layout.html
• Establishing consistent style across HTML, review starter templates
• Containers, Grids , Cards,  Navbars
• head, style, script, body
• binary.html example and demo

• The Society standard requires Light and Dark design considerations for each page, review runtime menu
• Introduction to Sassy CSS (SCCS), this is used to support Dark Mode independent color overrides of Bootstrap, custom.sccs
• Local storage and Java Script

• Install node.js
• From Terminal in IntelliJ, MacOs requires "sudo" on 1st two commands
  • npm install -g sass
  • npm install --global less
  • npm install bootstrap
• In .gitignore add lines

  • node_modules
    /node_modules/.package-lock.json
    /package.json
    /package-lock.json

• In IntelliJ Plugins add "File Watcher"
• In IntelliJ Settings Tools-File-Watcher. configure SCSS
  • See Visual with Page

• M - Stand Up Meetings (Scrum Team and BOF)
• Tu - TPT 3, After TPT TO's to train teams on Database and Search.
• W - CCC, Deployment Manager Runtime Reviews and Questions
• Th - PBL 1.0 Live Reviews
• F - PBL 1.0 Live Reviews cont.  Elephant Gift or Potluck?  , AP Practice Test Due

• see Canvas Week 3
  • All 5 BOFs illustrate deliverables