Page 2 of 2

Re: database and application use cases

PostPosted: Wed Apr 29, 2015 10:52 am
by pa3weg
pa9tv wrote:Space engineering is a quite formal compared to extreme programming. And to be honest, the data problem looks easy to solve. How do you feel about release early, release often?


I agree on the front end of things, but the actual database should be designed to not need much updating of the schema. It is too central to multiple applications, and when we constantly need all developers to use a new schema that's just not going to work...

The interfaces can just have a version number in the URI if we really want to. no problem to do that and serve in one or multiple formats at the same time.


But on the satellite side its release late, release once....unless you have an on-orbit bootloader! ;)

Re: database and application use cases

PostPosted: Mon May 04, 2015 1:08 pm
by pa9tv
Use case: automatic receiver, transmitter, antenna, decoder configuration.

User selects a satellite service from a list, and the receiver and transmitter are automatically configured for voice communication.

User selects a satellite service from a list, and the receiver, antenna, and decoder are automatically configure for decoding.