This week we did a practice run of our PDR presentation along with several other groups: Cemantics, Verify, and Loyalty. Each of these teams peer reviewed our presentation and gave us useful feedback for our actual PDR presentation on the 17th. Our coaches were there as well to provide support and advice. We wore our RTX t-shirts for the presentation and took a picture with Dr. Resch, attached below.
This week we began working on our preliminary design architecture, pictured above. It outlines the technologies that we plan to use and how they fit together to form a cohesive application. We spent a lot of time researching the best solutions for our needs, and we believe that this design will give rise to a quality product. With that said, the design is still tentative, and it may be subject to change in the future.
Additionally, our sponsor, RTX, was present at this week’s career fair. Pictured below is an airplane that was gifted to Andy by the RTX representatives. Tragically, it seems to have some kind of defect that prevents it from flying. We are still investigating this problem, and we have high hopes that we will be able to fix it.
Finally, we also decided to switch the team roles around, since we want everyone to experience a variety of ways to contribute to the team. Our new roles are as so:
Elijah Johnson – Scribe (documentation and meeting notes)
Kaitlyn Kilner – Finance (budget management, cost tracking)
Daniel Melendez – Leader (coordination, sponsor communication)
Nicholas Tayag – Template (report formatting and consistency)
Joshua Rushlow – Blog (progress updates and communications)
Andrew Goodson – Travel (logistics and scheduling)
Colin Wishart – Research (literature review and technical exploration)
This week we began preparing for our upcoming Preliminary Design Review. We started writing a draft for the report and working out possible dates to visit their headquarters in Largo next month. Additionally, our liaisons will be shipping us our RTX T-shirts soon.
We have also gotten in contact with the Gator Hatchery, where we will be developing our project. The Gator Hatchery provides resources for students working on business projects, and they should be able to set us up with a machine to run Windows Server in a closed network. It should also be possible to access this machine remotely for development.
This week, we started our draft for the Project Roadmap and the Project Risk Table. We discussed with our coach and liaison what items can be added and removed from the Risk Table. This allows us to be better prepared for any possible roadblocks our team may face.
Additionally, we began discussing which specific technologies we plan to use for our project design with our liaison. So far, we are planning on using Angular with .NET, which will greatly assist us when developing the UI. We also considered which database we want to use and how we plan to transfer the project to RTX. One of our team’s major questions was how we can test the effectiveness of our UI design with the user base; during the meeting, we learned that we can make a survey for the users to take, which will be distributed by our liaison.
During the weekend, our team attended the Six Sigma training workshop where we learned about how to improve processes and got our white belt certification! Our team had one of the highest rates of improvement from the first time we attempted the exercise to the last.
Hello everyone, this was an exciting week for Credential Core!
This week we meet for the first time with our liaison engineer, Alex Good. Together, we delved further into our project specifications and technical aspects. We reviewed and altered the requirement priorities for the Product Design Specifications and got clarification on the SOW. We also brought up our upcoming in-person visit to Raytheon in Largo, FL!
In our second coach meeting, we spent time discussing our Product Design Speficiation. We got a better understanding of what target measurements are best for our project since software projects don’t have traditional measurements. Currently, we have decided on percentage of unit tests passed along with static analysis to determine the number of vulnerabilities in the code.
Additionally, we have finalized our logo for Credential Core and unveiled it to our liaison engineer. It’s simple, sleek, and illustrates security. The imagery of the lock and key embedded into our name signifies our commitment to delivering a secure and dependable final product!
Hello and welcome to the Team 20 Blog! We are excited to design and implement SECURE – System for Employee Certification and User Record Expiration for RTX.
This week we had our first team meeting with our coach, Dr. Cheryl Resch. We discussed meeting schedules, setting up our first meeting with the liaison, and reviewed our first team memo. Additionally, we started working on our team name and logo. Currently, our team name is tentatively Credential Core.
Meet our team: