Alloway, Hunter; Last Edited: 2021-09-03

ENGR 481: Meeting Notes for the week of August 30th

08/30/2021

Meeting Introduction: Getting to know Bruce Stansell and an introduction of team members Targeted Software: Microsoft Office, Azure, Github or any Open-Source Platform Team roles were assigned by Lydia Wu

09/01/2021 Project “cadence” as described by our client

Scope of Client’s Organization: The goal of the project is to transfer/transcribe data from and to a server or data cloud application End-to-end communication between the product and user (open source software) Performance measurement will be evaluated on data aggregation for generic events where our product will augment their services Main Client/Customer: Twisthink→ an industrial+tech design business strategic platform striving to generate products that solve a consumers need

Goal Define “normal” such that a program/network architecture can identify abnormality in a devised system Deviations and Devised Terms: Team is set out to define a terms list (agreed upon language that will define the systems/products team 3 is working with)

Recommended Microsoft Open Source Platforms Azure SDKs, Blazor, Bond, CCF, and CNAB are all plausible alternatives to use to streamline our work and software architecture whether it be code, or other documentation LibreOffice is a potential alternative to Office 365 that supports office applications, microsoft files and includes many templates Github was mentioned by Lydia as a potential alternative to store shared code Links for the software: https://opensource.microsoft.com/projects

09/03/2021 Team members briefed each other on what they had found from their previous tasks Bruce Stansell Informed the group what the goal of the project is and the application it would be used for (example: water data analytics) Definitions were described and Lydia Wu briefed the team on timeline and agreed upon applications for documentation allocation and task assignment.

Hunter Alloway-Open Source Software Heyley Yukihiro-Inquiring a healthy pattern of data that tracks abnormality Michael DiGirolamo- What are the GENESYS requirements and how do they impact the scope of this project Lydia Wu-Organization of assigned member tasks and creation of a requirements checklist.

A terminology list was developed by Hunter Alloway to give team members more insight regarding how data analytics works: Elements of a Successful Open-Source: Jargon Github Glossary

Serialization/Deserialization: The state of one object, be it code, documentation, analytics, etc. and translating this data into a format that can be stored/updated for a future modification

Repository: Central location where data is collected, stored and manipulated

Dependency: Project, software code, task, criteria relying on another aspect of the project before it is capable of being modified

Commit: A commit is a change or modification made to a file. Similar to Microsoft Word’s edit suggestion, team members involved in a project who make changes will leave a “hash” which is essentially a tag, letting other users know who made the change.

Public Repository: Accessible to anyone in the world willing to use developed code on Github

Private Repository: Only accessible to team members and others added to join the repository

Stack: Layered system applied to software using a fixed number of outputs. It is a structured method to organize conceptual elements into a LIFO (last in first out) that influence push and pull operations. Push = adding an element to the stack and a pull takes data from the first position