3 ms·
Actual question from a software engineering newcomer: What would you consider "business logic" and where would said programs be running?
by Meegul 10y ago
Actual question from a software engineering newcomer: What would you consider "business logic" and where would said programs be running?
- paulrpotts 10y agoWell, I was using the term a little sarcastically since it is (I think) usually applied to multi-tier web service architectures. In my case I have an embedded system with a touch screen display, running a bunch of tasks to drive peripherals. There is a task that handles communication with the touch screen (serial). Then there is a set of slow tasks that handles states and modes, for example the runtime representation of a modulator or an RF amplifier. This got extended because we are adding "remote control" support over RS-232 and USB and so this runtime representation has to support more of a multiple model-view-controller. This can be done with queues and a lot of functions but it was simpler to represent it as a tree of stateful values that can be updated via remote commands or via the touch screen and have "downstream" updates. So that's what I mean by the "business logic" -- higher-level than, say, a driver and task for talking to a digital potentiometer or a DAC.