Curiousity Question about Software Engineers

[JC0133]

I just want to know if anyone knows the difference(if there is one) of a software engineer and a real time software engineer(or a software engineer for real time systems)?

 

[Crusty]

One works with real time systems and the other doesn't.

 

[Leros]

Real time software engineers have to be more stringent about timing. They're probably better programmers in that sense. They're also more limited.

Its the same set of skills for the most part.

 

[tatteredpotato]

Probably a Real Time Software Engineer is a Software Engineer who understands and works with the concepts required to build real-time systems. Things like RT scheduling algorithms and priority inheritance protocols, etc.

 

[KIAman]

Job title.

This is synonymous to comparing "Jazz Drummer" to "Blues Drummer." They can both play the drums within a wide variety musical styles. One just happens to have a more focused title.

Nobody better say that Real Time Software Engineers are better than Software Engineers.

If a company uses that distinction to provide metrics of compensation, that is fine but in the end, it is just a title.

 

[EagleKeeper]

A realtime S/W Engineer will usually work with embedded systems. The requirements are more stringent. The user can not perform a reset when the app locks up. Testing is usually many times more detailed.

Timing constraints are not in user expectations (20Hz), but driven by data constraints.

 

[the182guy]

Agree with KIAman, it's really just a variation. Software engineering covers a wide range jobs, much like in the transport industry you get bus, taxi and van drivers.

 

[Gibson486]

Realtime is usually a fixed operation. It has to be coded to do the stuff it is made for and that's it. In real time operating systems, you know how long it will take for that code to get from start to finish. There is no interaction with other software like antivirus and you usually can only edit it by downloading the code, resetting the system, then uploading the new code to the target.

It's, essentially, a subset of a software engineer. Just because someone is a software engineer does not mean they can program an embedded system. In that sense, it is more specialized. That said, I wouldn't be quick to call an embedded engineer a full fledged software engineer. Lots of them are EEs who know the hardware well enough to code to it.

 

[Leros]

Realtime is usually a fixed operation. It has to be coded to do the stuff it is made for and that's it. In real time operating systems, you know how long it will take for that code to get from start to finish. There is no interaction with other software like antivirus and you usually can only edit it by downloading the code, resetting the system, then uploading the new code to the target.

You don't know always know how long it will take, but you need to be able to prove an upper bound that meets your time restrictions.

 

[Evadman]

A realtime S/W Engineer will usually work with embedded systems. The requirements are more stringent. The user can not perform a reset when the app locks up. Testing is usually many times more detailed.

Timing constraints are not in user expectations (20Hz), but driven by data constraints.

This.