I seriously need to come up with a name for this soon, so I can stop referring to it as ‘flight logger thing’.
Anyway, it’s been a few weeks, but today’s post will focus on identifying inputs, processing, outputs and storage (hence the IPOS acronym). This is vital so I know what needs to be on the UI, which I intend to start designing soon! Without further ado, here’s the table. If you think I’ve missed anything, be sure to drop a comment and let me know!
| Inputs Flight number Origin airport code Destination airport code Date Class Seat Aircraft registration Departure time Arrival time Airline Aircraft Add flight Remove flight Edit flight | Outputs Map of flights Charts of relevant statistics Table of complete flights (filterable) User profiles |
| Process Computation of statistics Database manipulation | Storage Database for details User profiles |
Not much to this post I know, but next up will either be specification or UI designing, depending on what I feel like! Let me know your opinions in the comments.
