This week after much testing and work our team presented the final working project to the client. Our presentation was in depth and long, and went over the troubles experienced as a result of this global pandemic, but also our triumphs throughout.

Overall, it was a very successful presentation of our work and the client was happy with what we made them. We are all proud of our work, and I am specifically proud of certain group member namely Ben, Cam, Charlie, Ryan for pulling a lot of the weight for this project.

This week the team successfully connected the database and the UI, with some preliminary testing. The meeting with the client went well, changes to the projects schedule were discussed with the changes to all of our lives during this pandemic.

Work on the final presentation of the application has begun, and more testing will follow.

Our team handled this pandemic by being honest with eachother, and what we could deliver to the client. Sizing up what we had as deliverables, and what we could create during this time of turmoil was a main topic of discussion.

We were able to demo a usable UI, that the client enjoyed. Feedback was to create a separate count application for only mobile users.

The team will meet virtually this weekend on saturday to connect the DB UI and facade

This week we completed the core of the facade in node.js and submitted it to our teams github. The database has been completed, so work has begun on connecting the facade to the AWS database. We are waiting for word from the UI team for when they are ready for us to create a hook to their work and begin testing.

The core work can be seen here:

https://github.com/cazerb/Software_Engineering_Red_Team/tree/Chris

This week the facade team did a quick stand up to break apart the basic programming needed to complete a functioning facade to support the UI team and Database team’s work before the first presentation to the client.

Refresher: We decided upon using Javascript, Express, Node.js, and React libraries to create the facade.

This week we whiteboarded our the basic JSON structure for the Rooms data:

The basic core structure of the Node.js will be created, then the hooks for the Databse and UI data will be created by the end of this week.

This week we had a group meeting and decided upon our plan within the facade group. This included learning some libraries most of us had not worked with yet. namely:

Express, Node.js, React

This weekend the group will read through the documentation, find IDE’s most useful for our native OS’s and regroup on sunday to create a usable Facade for the DB and UI.

The group meetings have been extremely useful. The act of getting everyone from all teams in a room to communicate the input and output specifics of their projects has been indispensable.

This week the team met in the library to finalize a presentation for the client based on last weeks standup. The major needs were:

-Focus on a template for a UI entry point for room data and session entry, use that template for all other entry UI

-Focus the ERD on the session as a many entry and the rooms as singular

We met and designed a UI for the room entry design where the room numbers could be defined as well as the presenter and times in a usable manor (dont make me think)

This week the team met with the client to talk over the initial impressions of our presentation of a draft of the ERD (Entity Relation Diagram) and draft of a UI for the application of a counting design to be used for Boston Code Camp. The ERD sketches out a plan for the database to be populated when counting the number of attendees of each lecture.

The client had some useful feedback for both the UI and ERD drafts. The client suggested that the UI should focus less on efficiency on the design and implementation end, and more on the ease of use for the user. Going back to the drawing board and focusing on not “making the user think” is the main take away from this talk.

The ERD was mostly agreed upon, however again it should be more streamlined for ease of entry for populating the room, lecturers, and times for the admin before the event.

Today our team sat down to discuss further the requirements of this program being contracted to us.

keypoints:

-tally of members at a lecture during beginning, middle, end

-avoids human error of counter

-output of this data in an easy to read format (excel?)

-Discussions on specifics of code camp activities and changes in schedule in preparing the program for ease of use

-settled on an app that will be able to enter the room, lecturer, time, and numbers of attendees in one place

This class requires an online course of our choice to supplement the in class group project work. As I have some experience in cybersecurity due to a Coop, I wanted to learn more in a class setting. As a result I have selected this course:

https://www.edx.org/professional-certificate/uwashingtonx-essentials-cybersecurity

The course is titled Essentials of Cybersecurity, and the website lists what I will learn:

• Describe the vast array of roles and sectors within the Cybersecurity industry;
• Explain the relationship between management and technology in cybersecurity protection;
• Identify appropriate types of security controls to the actions of different and evolving threat actors;
• Apply terminology and basic concepts of cybersecurity;
• Assess own knowledge, skill, and abilities toward identifying a career path in cybersecurity.