Assign the following tasking

[lydia-wu]

• [x] investigate https://portal.azure.com/#blade/Microsoft_Azure_Monitoring/AzureMonitoringBrowseBlade/overview
• [x] design Cadence GitHub logo and/or Discord Tile
• [x] compile presentation for DG 01
• [x] compile formal report for DG 01

[lydia-wu]

@michaeld3951 if you happen to have some spare time and a creative itch, feel free to forward any ideas for pics for the Discord or GitHub groups. No due date; don't worry about it if it doesn't come to you naturally. I'm just all for not having my face be the default icon >u<

[lydia-wu]

Critical Design Review:

1. A Final Presentation will take place on the Final Exam
2. Each team must clearly demonstrate that their detailed design solution documented in the system design definition record (SyDD) is traceable to all Wasson Domains.
3. All members will be required participate in the presentation and will be asked questions about the project.
4. Oral presentations must be delivered on-time as dictated by the date and time posted on Syllabus.
5. Presentation documents must be submitted via Bb by the date and time posted on
6. Teams are encouraged to use a mix of multimedia (Adobe CCS) and live demonstration along with formal slides.
7. Each team will have 7 minutes to present and 7 minutes for questions.
8. Submit document as a zip file using the following naming format: ENGR481_FP_Team_0<#>.zip (example: Team 3 would submit document as "ENGR481_FP_Team_03.zip"). The files contained in the zip file should be named in such a manner as to be easily identified by course number, file content, and team number.

Final Report:

1. The Final Report consists of a technical management record of ENGR 481 project related activities.
2. The Final Report must include the following records: Project Status Record, Decision Record, Risk Record, Configuration Management Record, Information Management Record, Measurement Record, and Quality Assurance Evaluation Record.
3. Report documents must be submitted before midnight via Bb as dictated by the date and time posted on Syllabus.
4. Submit document as a zip file using the following naming format: ENGR481_FR_Team_0<#>.zip (example: Team 3 would submit document as "ENGR481_FR_Team_03.zip"). The files contained in the zip file should be named in such a manner as to be easily identified by course number, file content, and team number.

Performance Evaluations:

1. Instructor Evaluation of individual team members at the end of the course.
2. Client Evaluation of individual team members at the end of the course.
3. Team Evaluation of individual team members at the end of the course. This consists of a Peer and Self Evaluation that will be issued to you via online CATME survey and must be completed on-time, as dictated by the date and time specified on the survey. The survey is to be completed and submitted by each student independently. However, your grade will be based on a peer evaluation composite score derived from the survey. Failure to complete your own survey will result in a grade of zero points.
4. 10 Bb Knowledge Quizzes will be issued throughout the semester to verify individual is actively engaged in the course
5. Extra Credit: 5 points extra credit will be awarded to students who complete the EoC Student Evaluation by the university deadline. You are required to send an email notification to the instructor upon completion to receive credit.

[lydia-wu]

note to Lydia:

• need to put BOM (with Nordic thingy, a bunch of stamps, Discord Nitro, GitHub upgrade, etc) by DG-06
• need to get tasking out for the final report and critical design review
• need to confirm that we can do a virtual meeting for the final review (and get that scheduled?)

[lydia-wu]

note to Lydia:

high priority:

• [x] flesh Node ID Lookup table (build from #37)
• [x] flesh Health Schema (build from #36)
• [x] flesh PBI end-to-end (fracture from #39)
• [x] create beefy V2 of data simulator (foundation of #30, #29, #35)
• [x] confirm config in GitHub as working solution

  low priority:

• [ ] revisit BOM (#24)
• [ ] revisit standards alignment (#6)

[lydia-wu]

@hunter-alloway

New Tasking, Milestone 2.0 (Due 2022-02-18 Friday 12PM ET):

• [x] set up weekly sync with @michaeld3951 for Data ingestion on updates/confusion/tasking/progress
• [x] set up weekly sync with @htyuki for data simulator on updates/confusion/tasking/progress
• [x] set up weekly sync with @lydia-wu for PBI
• [x] set up weekly sync with @lydia-wu for high-level tasking
• [ ] RESEARCH: need to find a way to re-route data source when someone new downloads the PBI file and wants to look at the data;
  • [ ] answer this question: how do we streamline adjusting those "source" references?
  • [x] document the process in an instruction manual for someone that has just downloaded a zip with the PBI file and the data files
• [x] Meeting with client: what is the finished product? We need a goal @biosguy

Notes:

• Delegate these tasks out to the team; feel free to delegate any high-level meetings with the client to @lydia-wu
• touch base with each team member on existing issues and new issues at your weekly huddles
• make these tasks GitHub issues, and mark them as "Milestone 2.0"
• feel freedom to adjust deadlines per your judgement

[lydia-wu]

@hunter-alloway

New Tasking, Milestone 2.0 (Due 2022-02-25 Friday 12PM ET):

• [ ] free-form log absorption demo (ft. @lydia-wu)
• [ ] Health Schema cleaning (ft. @michaeld3951 )
  • [ ] align to JSON schema ("XML Schema")
  • [ ] trim down current version to bare bones, no fluff
  • [ ] build a portal that generates the JSON file (a command-line where you type in parameters? a GUI, web-based dashboard? a PBI interactive visualization? Assignee decides)
  • [ ] Diagrams/VISIO (3 total) (ft. @hunter-alloway)
  • [ ] 1: create a diagram that articulates how we are connecting reports to and from email
    • [ ] show how the PBI dashboard PDF/dash/excel gets sent in an automated email
    • [ ] show how the PBI ingests data that has been emailed to the user
  • [ ] 2: show a colored VISIO that maps our current progress as a team
    • [ ] color the existing flow VISIO that we released in DG06, "gray" for "not yet","red" for "behind", "yellow" for "in progress", and "green" for "on track"
  • [ ] 3: show a VISIO that describes connecting to a device in the lab, then flow through CADENCE (very close to what @biosguy talked us through last week with his VISIO diagram)
• [ ] Simulator (ft. @htyuki)
  • [ ] change directions from "1000 rows in one file" to 10 files with 100 rows each
  • [ ] each file should have its terminating or starting timestamp appended to its name (i.e., if you finish generating a file at 3:02:00am on February 21st, then the file name would be AppReport_20220221030200.csv, or something like that)
  • [ ] the files should be contiguous (the next file picks up the timestamp right after where the previous one finished
  • [ ] we want 10 files per file-type (i.e., 10 device Logs ,10 App Reports and 10 Network reports)
  • [ ] continue the same approach bug-wise as your ongoing #48

Notes:

Minimum: “get a good grade!”

• Make sure the requirements are all set up (spreadsheet (RED/YELLOW/GREEN) o pop up at weekly meeting @hunter-alloway
• @Robert Stansell PRIORITY o Want to exit engagement with local fast tools: PBI and MS suite (email functionality) o Want health schema file/form o Want an end-to-end flow functional
• @Robert Stansell BONUSES o Show with an embedded device (don’t care about particulars about data source; Nordic-THINGY? Particular customer from @Robert Stansell?) o Capstone show goal: show both simulator and customer-source data o Spend some time with a cloud instance of ELK: ELK is not easy, and it’s not friendly for “Quick” stuff --> this is meant for a general-purpose, production, cloud-hosted thing

So, what now?

1. MS? Be aggressive. Get “hot” on MS for a while; get this thing done and solid and feeling good for a while. a. Heath Schema: (1) design and (2) portal b. Email linking: (1) send and (2) receive c. Source documentation d. “Reduction, enhancement, transfer”: manipulate the input files: what do we reformat? What do we drop? Wrappers? e. PDF report generation f. Low priority: THINGY ordering
2. ELK? Kill for a little while
3. Dr. Bruce wants a suitcase