Beta Prototype Presentation Posters

Team Awards

The last couple of weeks have been very productive for Team EULER. Last time we finalized our problem statement and started grazing over the solution space. This is a bit premature, but it helped us to have a few proof of concepts that were tangible in our minds. These proof of concepts helped us develop a few more functional requirements that we didn’t really think of to begin with. We then started to develop our posters for the problem space presentation for the Senior Design Poster Session. The team made 3 posters: Problem Discovery, Problem Framing and Definition, and Concept Generation and Project Management. Each of these posters will be presented by 4 group members at the poster session. The team also managed to acquire a fire suit which is shown below.

Over the course of the last 2 weeks, Team EULER has delved even further into the problem space and refined our problem statement even further. The team collectively decided to work on a way to navigate through the thick smoke present in most fires. We learned that most firefighters actually close their eyes while inside of a burning building as they can’t see whatsoever. Alongside this problem statement refinement, input values for our main 13 functional requirements have been generated. Each group member was assigned to their previous functional requirements and had to gather information about how the XX’s should be filled in. The team did this very efficiently by using both stakeholders and research information.

Over the last couple of weeks, Team EULER has started to narrow down our problem space even more. The team has come up with a well-defined problem statement, which is on the front page of the website for viewing. We used stakeholder analysis and other research to complete this process. This was worked along with functional requirements that the team generated together. Each individual team member had to come up with at least one functional requirement to contribute. However, we generated well over 12 requirements with the latter being generated as a team. Overall, 21 functional requirements were generated, but this number may change as we work through the design process even further. The next step is to add numbers to the XX inputs for the functional requirements, which should take up the majority of the next couple of weeks.

Over the past two weeks, the EULER team has reached out and discussed potential problems faced by firefighters. This has been done through various forms of outreach such as interviews, email questionnaires, and google documents. Shareholders were asked to fill these out to allow the team to see which problems they face in their field and how the team can aid in solving it. The team then underwent a selection process, narrowing down the list of problems to one: on site information and planning. To further this goal the team now is narrowing down what information problems are the most relevant and how best to go about finding/prototyping a solution. The shareholders are being communicated with to confirm that this is a worthwhile goal.

Team Euler, having identified the field in which direction the project would go, began to outreach. Many team members began to create dialogs with local fire departments as well as personal connections, asking an agreed upon set of questions to try and get a better handle of the problems firefighters face in the field and problems which they are looking for solutions for. We also updated the website to reflect these achievements.

Over the past two weeks, Team EULER developed a problem space that the team members would be interested in and passionate about. Our main goal was to collect information from stakeholders and begin to narrow down our problem space. Thank you to everyone who returned our calls and emails; we greatly appreciate it! We have also started to work on the website and added our bios. We have begun to contact the gateway center to continue to reach out to other connections. Additionally, we created a charter that states some basic rules/responsibilities we have as a team. As a group, we narrowed down the questions we were going to ask potential stakeholders, drafted a sample email to send to them, and eliminated a few potential stakeholders that either nobody knew or could be grouped with another stakeholder. John Cortazar gave a presentation to the rest of the mechanical engineering student body which summed up what we have been working on so far.