Position+Definition

The following definitions will serve as the guidelines for each team member’s major tasks throughout the project lifetime. All team members are expected to help one another out to ensure the best outcomes for the project, not just for the individual’s task completion

Faculty Sponsor
Herbert Detloff Demonstrates previous experience with several successful capstone design projects. Provides feedback and assessment of project definition, plan, and status. Ensures that all team members are aware of the engineering impact of the project on the University of Nebraska - Lincoln and the rest of the world. Teaches standard engineering principals for project management, development, execution, and testing to aid in the project's completion.

Resource Manager
James Gehringer Responsible for promoting collaboration, communicating progress with the faculty sponsor, and procuring resources. Accountable for intellectual property management in solidification of ideas and iterative verification of project objectives. Involved with all phases of design in order to better assure both long and short term goals are met with efficiency by keeping track of the progress of the project by setting deadlines, scheduling tasks, and monitoring progress through tools such as Gantt charts. Oversees documentation and monitors project health to identify issues as soon as possible. Reports to the Faculty Sponsor.

Systems Engineer
Evan Milton In charge of generating the system's requirements and specifications and understanding the project as a whole, including mechanical, electronic, and software components and their interfacing. Works closely with the Hardware and Software Development Engineers to best meet the team objectives, system's requirements, and specifications. Responsible for acceptance testing the prototypes and final project to ensure quality and confirm that all specifications are met. Determines alternate solutions case any solution fails or becomes unfeasible during development. Makes final design decisions when challenges arise that require major modifications. Reports to the Resource Manager and Faculty Sponsor.

Hardware Development Engineer
Chad Staley Accountable for developing the design, layout, construction, and testing of the electrical systems required for this project to create a solid platform for the software. Focused on simplicity and robustness in design, to aid troubleshooting when software is added to the project. Understands and can communicate the software interfacing that must occur to make the hardware function properly. Reports to the Systems Engineer, Resource Manager, and Faculty Sponsor.

Software Development Engineer
Josh Dewitt Responsible for the higher level functionality of the project by writing clean, modular code that can be adapted where hardware changes might be cost-prohibitive. Will communicate with the Hardware Development Engineer to understand the hardware interfacing to meet the requirements set by the Systems Engineer. Performs domain, software element, and requirements analysis to ensure the code produced matches the needs of the users, then develops code in any language necessary, using test­-driven development. Reports to the Systems Engineer, Resource Manager, and Faculty Sponsor.