Database Tool for Rockwell Collins
OVERVIEW
During my internship at Rockwell Collins I was tasked with designing a database that would handle all information related to licensing and a GUI to go with it. My team did not do its own licensing, but contracted it out to another company, and needed to keep track of the licenses and orders that we had, independently from but synchronized with the contract company’s data. We also performed licensing for a number of other teams. The database would to be on Microsoft SQL Server and the GUI in C#. |
SKILLS
Software development, UI design, GUI building, database design, information architecture TOOLS C#, MS SQL, SQL, Visual Studio |
I worked mainly off of documentation and raw data. The hardest challenge was determining the program flow, and—possessing no real formal training in HCI—I was tempted to base the GUI off of the database. This result was produced in close collaboration with my team, who were soon-to-be users of the application. When my lead asked for better navigation, I implemented a panel on the left of the screen with “Views” segregating different kinds of data. When there was disagreement between team members about what kind of permissions an admin and a normal user would have, I proposed scrapping admin/user tiers altogether and implementing permissions as a checklist of privileges instead. In both of these cases I listened to user feedback and met their critiques with design answers.