Software Engineering Collaboration 3

When our team met the first time, it was our responsibility to overview the project. I explained to them that we would be using an OSS, Open Room for the library, but there were some changes we wanted to make before we made it available to our patrons. Open Room was designed by Ball State University in 2010 as an online reservation system so that patrons could check out study rooms in the library without interacting with library staff. The product owner often gives the requirements in form of a story: As a <type of user> I want to <do something>, so that <some value is created>.

Since the program was developed 7 years ago, there are some technologies that can be improved on to make some of the setup and admin functionalities. We also would like to make the program "feel" more like a library website so that our patrons have a sense of familiarity when they are making reservations. Our story might be: As the product owners, we want to improve administrative functionality and the look and feel of the website so that both the patrons and the software admin can have a successful experience when using the application.

After the overview, our team talked about what tools we plan to use. Since Queens College has since taken over the maintenance of OpenRooms and has it set up in GitHub, we decided we would use GitHub to track our changes. We also decided to use Slack as our method of communication. Slack will be helpful because it will allow them to share code when needed.