-
Notifications
You must be signed in to change notification settings - Fork 1
Blog 2016 11 04 Fall
The requirements document was finished this week. GS is the name of our software. I am planning on creating some kind of logo for it that way we can put it up into our web application. I also spoke with a Computer Visualization person, Nik, that Winters introduced me to. He mentioned that we could get the topology and satellite images of the area from Professor Mike Bailey. The texture image can be mapped to the topology and we can use that for our web application. He also mentioned that it would be cool if we could get an PC to actually have the web server on. Kirsten added that there could be possible funding for this as well. We also realized that we pretty much have four months before the test launch. A lot needs to happen before now and then. I think it would be great if we could start coding soon. That short window of time is making me a bit anxious.
Progress
We finished our requirements document this week. I originally had to take care of the availability, reliability, and Design constraints. We came to an understanding that we didn’t need availability and to shorten the reliability to what it’s base of what needs to really do. Natasha came up with a beautiful Gantt chart. We also came up with a name for our software too which we are all really happy about. We used the extra day to proofread our document to make sure we had it in order too.
Plans
Next week we are going to do more research on the software as well as the parts that we are in particular charge of for the technical document.
Problems
I think the biggest issue with the requirement document was trying to choose what was needed and what wasn’t need for our project. Our project is a little different because we get requirements that there one week but then the next week we find out that is not going to work and we have to change it. So we had to generalize what is going to needed.
We've been so busy with the requirements document the last couple weeks, I have no idea what we are going to bring to the meeting on Monday. The current plan is to make a plan.
This week, we finished the requirements document. Because of the amount of work the requirements document needed, we did not progress in any of our other areas.
The requirements document needed extensive revisions, and I think we could have used another week to make it even better. We don't have a customer who dictates exactly what they want, so we had to make a lot of decisions about where to take the software before we could write the requirements for it.
OSU High-Altitude Rocket Team