-
Notifications
You must be signed in to change notification settings - Fork 1
Blog 2016 11 25 Fall
This last Monday we went over what should be in the design document, making to cover what we had already written
Tech Review | Requirements Review | Viewpoints |
---|---|---|
web server | Raspberry Pi | Interaction |
web backend | real-time | Resource Management |
logging | reliability | Interface |
data visualization | corruption | |
UI interaction model | accuracy | |
UI interface organization | redundant sensors | |
retrieval | storage | |
UI toolkit | internet / HAM |
The following was decided upon for the design document:
Interface Viewpoint
- Under review
Interaction Viewpoint
telemetry packet
|
v
collecting/error checking
|
v
log <-------translate json ------>send to client --------> update webpage
| ^
v |
new client-----------------------> read log
Resource Viewpoint
- Graphics on Client (GPU)
- D3?
- 3.js
- jQuery
- additional libraries
Splitting up the work seems like the most difficult thing. Also it being Thanksgiving break it is hard to know when everyone is free or available to work on the assignment.
This week we are going to hammer out the design document, as well as any other things we need to do. We have a pretty good idea of what the design is going to be, but we may change our mind as we start writing it, so it's important here to be flexible.
This week we actually starting working on the design of our software. On Monday we went over, in detail, how we are going to write the design document, and which viewpoints we should use.
Due to the nature of the design document assignment description, I'm still not sure exactly how we are going to divide the work up. It would be fairly trivial to just divide the work evenly, but because we all have to do the sections that we did in the technology review, some elements, such as relationships between two different technologies that were described by two different group members.
###Progress This week we broke down the design document before the Thanksgiving Break. That way we knew which areas of the document we were going to use and could get an early start on it. We did notice that not all components have the same areas. I have started some research and a rough draft on this document. We ran into an issue on the last one and I do not want us to run into the same thing again so I started early.
###Plans As I have started early on the design document and have read the template a little more in detail. It seems that some of the design viewpoints are not fit for certain components and we should talk about this on our Meeting with our TA on Monday as well as our team meeting.
###Problems As I read over our technical document and have read over the IEEE design document I have noticed that some of us are going to be writing more than others. I know that this is supposed to be split up into an individual sections but it does not seem fair that way. I do not think that if I finish early that I should not be able to help my other team members finish there component if they need it. I feel that this is what teams are here for.
OSU High-Altitude Rocket Team