This week, the team spent most of our time continuing to develop the web portal. After setting up the backend repository with Swagger and Spring Boot we spent this week writing endpoints for file uploads and deletion, and started setting up authentication services that will eventually be integrated with Microsoft Active Directory. On the frontend, we used TypeScript to set up a universal header for the web portal where the user can access search functionality, a help button, and profile subcomponents. We also created a general page template and began development on the dashboard, the first page the user will see when they log onto the web portal. The plan for next week is to continue developing API endpoints for software uploads and page content edits, as well as begin frontend testing with React Testing Library and Jest. We will also integrate a continuous integration/continuous delivery pipeline into our GitHub repositories and start our Final Design Review report outline.

This week, the team presented our QRB1 presentation to a panel of coaches and faculty. At the conclusion of our presentation, the team received very helpful feedback about our project plan. We will use the feedback to adjust our roadmap for this semester to make sure the project is completed on time and of the best quality. We have also started a Kanban board to organize and assign tasks to each team member. After our QRB1 presentation, we met at the Innovation Hatchery to work on the web portal. We set up our project structure for the frontend and began working on the navigation and routing. On the backend, we initialized the project with Spring Boot and added the Swagger configuration for the APIs. In the coming weeks, the team will continue to work on the portal design on the frontend until the Hatchery hardware is returned and we can continue working on the backend.

This week, one of the first tasks on our team’s agenda was to start preparing for our QRB1 presentation next Tuesday. The presentation will be held in front of a panel of staff and is done to ensure that we have a solid plan for this semester and will complete our project in time. During our QRB1 preparation, the team decided to switch from the Waterfall methodology to the Agile methodology, as it should suit our project better and help us develop a better product. We also revamped the layout of the portal from last semester’s prototype. After we have completed our QRB1 presentation next week, we will show our liaisons the new layout and obtain their feedback. Once we have liaison approval we can begin development on the front-end for the final prototype.

This week, team Securix returned back to school and got ready to start working on the final prototype. The main objective for the week was to develop our plan for this semester. We met as a group to determine the deadlines we need to meet to complete the project on time, and refined our project risks and mitigation strategies. We presented the plan during class to get feedback from instructors and peers about our proposed schedule. After presenting our project plan to the class, we compiled the final list of technologies and dependencies that we will need for the web portal and determined the final list of features and requirements for the prototype. Next week we will confirm the final list of features with our liaisons so that we can begin developing the web portal.

This week, we presented our System Level Design Review to our liaison and other teams at SLDR. Prior to SLDR, we had spent the week finalizing the report and practicing for the presentation. After eating some food, chatting with our liaisons, and attending an inspirational speech by the keynote speaker, we gave our SLDR presentation. Overall, we think the presentation went very well and we got some good feedback in the Q&A portion that will help us during the final prototype development next semester. Our last task before winter break is to get the final SLDR report signed by all the liaisons and turned in. After a long semester, we are all happy with the work we have completed so far and are excited to begin the development of the final web portal and put all our ideas to use. Until then, Happy Holidays from Team Securix!

This week was spent preparing for our System Level Design Review (SLDR) presentation next Tuesday. We presented during class to our peers and coach to get feedback before presenting to our liaisons. Most of our feedback revolved around our presentation skills, meaning we need more practice before the actual presentation day. After seeing some of the other group’s presentations we are also adding some more slides to our presentation to give more information about our problem and solution. At the beginning of the week we turned in our SLDR report rough draft. We have updated all of the appropriate figures and tables and, added information about the prototype and other design decisions that we made. After the rough draft is graded, we will fix the problems so that we can get our liaison and coach’s signatures on the final SLDR report next Tuesday. The rest of the week will be spent fixing problems with the presentation and practicing for the big day.

This week, our team presented our prototype at Prototype Inspection Day. We received some very valuable feedback about both the user interface and, our presentation. We are currently in the process of gathering the data that we collected from the survey and during the prototype testing process. Using this data and the feedback, we will be editing and adding certain features to the prototype. We were able to show our liaisons the prototype during the weekly meeting and they seemed pleased with the progress so far. Hopefully, we will be able to get some feedback from the customer before building the official web portal. Our next main focus is the System Level Design Review (SLDR). We will begin working on SLDR next week before Thanksgiving break, then continue after the break. We are all excited about the progress that we have made so far and eager to continue working on the project.

This week, we were able to finally meet our liaisons in person for the first time! On Sunday, team Securix and our liaisons met at the Hatchery to go over the infrastructure and discuss the prototype. The liaisons set up some of the software in the Hatchery and helped us brainstorm more tasks that the users can do when testing the prototype. They also generously took the team out to lunch at MOJO Hogtown Bar-B-Que. We want to give a big thanks to Raytheon and our liaisons, it was great meeting them in person. The rest of the week was spent working on our React prototype. We received some survey results about the old web portal that we used to add features to the UI. The prototype is nearing completion, we just need to add the dashboard and How-To pages. Next week, we will finish up the prototype and present it at prototype inspection day. Using the system usability scale survey, we should be able to gain some valuable feedback during prototype inspection day that we will take into consideration next semester when developing the official web portal.

This week, our team continued to work on our prototype in preparation for the prototype inspection day coming up in about two weeks. We have finally finished our wireframe designs in Figma, which will make the prototyping and developing process much easier. During class we discussed how we want to present our prototype. Our goal is to have users test the prototype but, make it as interactive as possible to keep the user engaged while also obtaining the metrics we need. We have adjusted our technical performance measures to apply to the user interface. After the user tests our prototype, they will fill out a survey about their experience with questions pertaining to the technical performance measures.

This Sunday, we will be meeting our liaisons in person for the first time at the Hatchery. During the meeting, we will learn how to use the technology in the Hatchery so we are prepared when we begin developing the back-end of the web portal. The main focus for next week is to finish developing our prototype so that it is ready to be tested.

This week, team Securix finalized our prototype plans during class. Originally, our prototype was going to consist of just wireframes; however, we have now transitioned to creating a React app for our prototype. The React app will allow users to actually interact with the front-end so that we will be able to retrieve data from the users to determine what changes will need to be made before building the official web portal. We have also started to change our technical performance measures because many of the old ones consisted of measurements that were out of our control. Finally, we have been working on acquiring signatures on our PDR document.

Our plans for next week include starting on our prototype and finalizing our technical performance measures. We hope to generate a survey that users can take after testing the front-end prototype. Along with this, we are also planning to meet with our liaisons in person at some point so that they can walk us through the Hatchery and all of the equipment stored there.