Here is the final version of our project design:
- What did we learn about the process of design in this course/project?
During our work on this project, we learned how important the communication with the shareholders is. Through interviews we learned about the requirements the different shareholders set and, almost as important, what they wished for. The requirements and wishes set by the different shareholders might overlap, so that is where our creativity for the design would have to come in. We also learned to extract the absolute necessities for the project from the interviews, which reduced the number of requirements, but also made the design more concrete.
An interview that was particularly interesting was the one with the administrator. She mentioned a lot of things that we had overlooked and that other stakeholders had overlooked. There were 2 key points that we overlooked. First, current systems are in place because they are secure. Grades are sensitive data that must be protected from hackers. Sure, we can have a lot of fancy features, but if the grades are not secure there’s no point. And second, Banner stores so much more than just grades. Banner is like your whole academic history, our project can’t replace that, but it could work together with it. The interview showed how important it is to choose your stakeholders, if chosen incorrectly, you can miss key requirements of your system.
- Our use cases and ER diagram:
- Here we have provided a video explaining the project:
Zeger has a blog 