Requirements Brainstorming/Team Communication - Blog 02

This week, my team (now 12 students and I) began to setup and use some tools that not only fulfilled what was required for submission for week 3 of the course, but that will also be used throughout the duration of our project to stay organized and connected.

Since Slack was a common chat service used by multiple students from previous work/coop experience, we decided to use that as the medium through which to share notes, ask questions, and more generally to just communicate to each other. Being a group of 13, it's a little hard to manage the communication between everyone, thankfully Slack makes that easy. Though we've only been setup with Slack for a few days, I can already start to see how competent my fellow classmates are with Slack as well as the topics we are discussing on it. That being said, I'm also starting to see who in the group is coming forward with the intent to be more of a leader. So far, I've noticed that myself, Andrew, and Bhagirath have been the most vocal in our group discussions that we've had on slack, which leads me to infer that we will naturally gravitate to leading the team. I've also seen people contribute here and there, more as supporting or adding input to what has already been said, and they may be others to contribute. Finally there some people that I have noticed have not been commenting at all. These are my observations as of today, so I'm aware that this is likely to change as the semester rolls on. I'm really interested to see how well we work as a team throughout the semester.

Throughout this past week the team has been communicating on Slack in order to submit various things for grades. Andrew set up our shared git repository, and added all 13 of us so we are all able to contribute. We also collected the notes that everyone took regarding the project description and requirements during class last week (see last week's blog) to brainstorm and accumulate a list of requirements that will be revised and edited and added to on Monday to be submitted next week as we transition to investigating what features will be best to fulfill these requirements. The first stages of brainstorming the following features that might be perfect for implementing the solutions to these requirements comes next week so stay tuned!:

Requirements:

How many people are in each session at three different times during each session. (functional)

-counting (non functional)

Need a way to record the number of people in each session and get those requirements to the sponsors

Need an easy way to retrieve counts after recorded

Need labels/identities for counts to differentiate sessions and times during the sessions that counts have been recorded for

-Room

-Capacity

-Count (beginning, middle, and end)

-Speaker

-Content of Talk/ Sessions Name

-Time slot

Use this information to retrieve data at the end and show it

Place to store the data – non functional requirement (place = what)

How to store data - feature

Make it editable

How do they want the data delivered? (hold off when designing solution)