Features/Phase One - Blog 03

This week, the group and I began to determine the features that are going to be needed to make our software system work and meet the requirements. More specifically, we are looking into the features we need to implement for "Phase One" of the functionality of the app. Phase two will be where the volunteers will be able to enter the number of people in each session of presentations at the beginning, middle, and end, but before they can do that, we need the head of the code camp to be able to enter the information about the sessions that the volunteers will be counting for. We have determined that for phase one, we will need a user interface (UI) that will allow the user to enter the metadata for all the room IDs (Room + time), room capacity, speaker names, and presentation titles (content of session.) We also need a database to store all this data, and finally some "interactors" to get the data to travel from the user to the UI to the database. We'll end up using something involving SQL for our database, and the UI will most likely have multiple tabs since there is a lot of data to enter, so one page may get pretty cluttered.

At the beginning of the week, the team met for the first time in person to discuss the features that we might think to implement for fulfilling our solidified requirements. While doing so, we introduced ourselves with our names along with the potential skills each team member can contribute to the project. About half of our team have admitted to be lacking in coding skills and would rather work on the front end/UI, while others are more excited to use what they've learned in class and work experiences to use tech tools to develop a nicely working app from the back end. I myself have had two coops at which I've developed back end code, so that's the area I will most likely step into, but I've also told the team that my skills should allow me to be flixible enough to migrate to whichever dev team needs more numbers to solve the currently highest prioritized issues.

Our team needs to have the solution to phase one deployed in two weeks, so as a check point, the following requirements are what we will be working on next week, before we can begin coding the implementation starting the week after. Stay tuned for next week, where I'll most likely be sharing our solutions for:

1. Decision for what Database we'll use

2. Decision on what Environment we'll work in. Web app?

3. Sketches of UI

4. ERD for the Database

5. Class Diagrams