3 ms·

I think a lot of posts here completely missed the point of the article, which is NOT about the role of architects in pure software products such as websites. T

I think a lot of posts here completely missed the point of the article, which is NOT about the role of architects in pure software products such as websites. The author is talking about large defense systems like satellite arrays and airplanes. The status quo that the author is responding to is that engineers of the physical systems (missiles, satellites, etc.) make all the decisions with software bolted on after the fact. This is definitely true at places like Boeing. You could replace architect with "senior software engineer" or whatever. Point is, software should have some seat at the table during the design process. The fundamental thesis of the piece is: "If, instead, system acquirers ensure that systems engineers address software concerns at the same time as the physical solution is conceptualized, acquirers can opt for a slightly different physical system, whose software architecture is tuned to optimize the provided capabilities." Which, to me, sounds entirely reasonable. If some system needs an MLOC or so and the software will be doing a complex thing like piloting the aircraft, you better be thinking about the software from the beginning of the project...

kejaed 7y ago
As an aerospace and defence systems engineer & software engineering manager I came here to note exactly the same thing, however it’s not hugely surprising on a SW-centric site like HN. I think this applies to all disciplines “under” systems engineering too, the thing is with software there are often a lot more chances for things to go sideways compared to EE or mech in development. The sooner you get the smart people in each discipline (Software or otherwise) to the table the better off everyone will be. This is why in systems engineering processes like ARP4754 you’ll see the word “preliminary” a lot. Preliminary architecture can be developed along with the system requirements as a basis for discussion with those performing the safety analysis and those implementing the software and hardware items. Having a software architect at the table, someone who can reason about the software architecture and its impact on the systems as a whole and the safety case can only help.
cc81 7y ago
Yes, people seems not to be reading the article at all. Someone should just change words to "hardware people" and "software people" and I think people here would receive it better.
jcurbo 7y ago
Yeah, between this and the MITRE post the other day I wondered if it was suddely Systems Engineering Week at HN. This is not the kind of content you usually find here.
- qznc 7y ago
  Do you know other places where such content does usually get posted?
  - throwawayjava 7y ago
    Professional conferences and the like. For better and worse, it more resembles fields like medicine, law, traditional engineering where most shop talk happens in professional settings and at a specific allotted time, as opposed to online throughout the year during after work hours.

kejaed 7y ago

As an aerospace and defence systems engineer & software engineering manager I came here to note exactly the same thing, however it’s not hugely surprising on a SW-centric site like HN. I think this applies to all disciplines “under” systems engineering too, the thing is with software there are often a lot more chances for things to go sideways compared to EE or mech in development. The sooner you get the smart people in each discipline (Software or otherwise) to the table the better off everyone will be. This is why in systems engineering processes like ARP4754 you’ll see the word “preliminary” a lot. Preliminary architecture can be developed along with the system requirements as a basis for discussion with those performing the safety analysis and those implementing the software and hardware items. Having a software architect at the table, someone who can reason about the software architecture and its impact on the systems as a whole and the safety case can only help.

cc81 7y ago

Yes, people seems not to be reading the article at all. Someone should just change words to "hardware people" and "software people" and I think people here would receive it better.

jcurbo 7y ago

Yeah, between this and the MITRE post the other day I wondered if it was suddely Systems Engineering Week at HN. This is not the kind of content you usually find here.

qznc 7y ago
Do you know other places where such content does usually get posted?
- throwawayjava 7y ago
  Professional conferences and the like. For better and worse, it more resembles fields like medicine, law, traditional engineering where most shop talk happens in professional settings and at a specific allotted time, as opposed to online throughout the year during after work hours.